Background and Introduction To 1xEV-DO Technology Background and Introduction To 1xEV-DO Technology To 1xEV-DO Technology To 1xEV-DO Technology

Module 340
Background and Introduction

To 1xEV-DO Technology
10-2008 (c)2008 Scott Baxter and Associates 1

340 Contents
 Wireless Usage Today: Competing Wireless Data Technologies
 Speed: 1xEV-DO’s purpose and differences from 1xRTT
 Key Features and Structure of 1xEV1xEV-DO DO
 EV-DO Technical Details: Channels and Dataflow
 MAC Indices – what they do, and how many are available
 Forward Link Data delivery during an established connection
 C/I instead of Ec/Io
 Managing the AP’s attention to mobiles: “Proportional Fairness”
 Si
Signall Composition
C iti and d HARQ
HARQ: Hybrid
H b id RRepeat-Request
tR tP
Protocol
t l
 Reverse Rate Control
 EV-DO Rev. A Forward and Reverse rate indices
 R
Route U
Update
d and d the
h signal
i l path
h iin b
both
h di
directions
i
 Network Architecture of main manufacturers, Mobile and Simple IP
 Interoperability Basics

Global and US Wireless Subscribers 1Q 2008
Global USA
Total 3,051,659,279 252,018,131
GSM 2,571,563,279 84.3% 102,200,000 40.6%
CDMA 451,400,000 14.8% 132,243,131 52.5%
IDEN 28,696,000 0.9% 17,575,000 7.0%
 Total Worldwide Wireless customers surpassed total worldwide landline

customers at year-end 2002, with 1,00,080,000 of each.
 4/5 of worldwide
orld ide wireless
ireless ccustomers
stomers use
se the GSM technolog
technology
 CDMA is second-most-prevalent with 14.8%
 In the US, CDMA is the most prevalent technology at 52.5% penetration
 Both CDMA and GSM are growing in the US
• IS-136 TDMA systems were converted to GSM + GPRS + EDGE

World Wireless Subs by Technology 2006
World Wireless Subscribers 14.8% 83.1% 2.1%
Top 21 Operators Only 980.77 145.49 814.98 20.30
Operator Country Subscribers CDMA GSM IDEN
China Mobile China 246.65 246.65
China Unicom China 127.79 27.79 100.00
MTS Russia 58.19 58.19
Cingular US 54.1 54.10
Verizon US 51.3 51.30
NTT DoCoMo Japan 50 36
50.36 50 36
50.36
Sprint Nextel US 45.6 25.30 20.30
Telcel Mexico 33.6 33.60
T-Mobile Germany 29.5 29.50
D2 Vodafone Germany 29.16 29.16
Vivo Brazil 28.8 28.80
Turkcell Turkey 27.9 27.90
Telecom Italia Italy 27.25 27.25
T-Mobile USA 21.7 21.70
Orange France 21 67
21.67 21 67
21.67
KDDI Japan 21.57 21.57
Telefonica Moviles Spain 19.6 19.60
SK Telecom South Korea 19.53 19.53
Vodafone Italy Italy 18.2 18.20
T M bil
T-Mobile UK 17 2
17.2 17 20
17.20
Vodafone UK UK 16.325 16.33
Vodafone KK Japan 14.77 14.77

US Wireless Subs by Technology 2006
US Wi
Wireless
l S
Subscribers
b ib 100% 48 4%
48.4% 41.5%
41 5% 10 2%
10.2%
198,444,627 95,963,297 82,336,426 20,144,904
Carrier Subscribers CDMA GSM>WCDMA iDEN
Cingular Wireless 54,100,000 54,100,000
Verizon Wireless 51,300,000 51,300,000
Sprint Nextel 44 304 901
44,304,901 24 459 997
24,459,997 19 844 904
19,844,904
T-Mobile 21,700,000 21,700,000
Alltel 11,040,000 11,040,000
US Cellular 5,500,000 5,500,000
Leap Wireless 1,670,000 1,670,000
Dobson Communications 1,543,000
, , 1,543,000
, ,
SunCom 964,824 964,824
Rural Cellular Corp. 705,602 705,602
Centennial Communications 586,000 586,000
Cincinnati Bell 496,000 496,000
Ntelos 336,300 336,300
SouthernLinc 300,000 300,000
Alaska Communications 117,000 117,000
Cellular South 670,000 670,000
Commnet Wireless 420,000 420,000
West Coast/SureWest Wireless 350,000 350,000
M i th Comms.
Meriwether C 300 000
300,000 300,000
300 000
Airadigm 380,000 380,000
Lewis and Clark 370,000 370,000
Clear Talk 520,000 520,000
Entertainment Unlimited 220,000 220,000
Corr Wireless 127 000
127,000 127 000
127,000
Poplar PCS 190,000 190,000
Edge Wireless 120,000 120,000
Salmon PCS 114,000 114,000

A Quick Survey of Wireless Data Technologies
US CDMA ETSI/GSM MISC/NEW
FOURTH
Flarion OFDM
GENERATION WiMAX LTE 1500 – 900 kb/s
12000 – 6000 kb/s 12000 – 6000 kb/s
WCDMA HSDPA
1xEV-DV 12000 – 6000 kb/s
THIRD 5000 - 1200 DL
307 - 153 UL WCDMA 1
GENERATION 1xEV-DO A
2000 - 800 kb/s
3100 – 800 DL WCDMA 0

1800 – 600 UL
384 – 250 kb/s
1xRTT RC4 EDGE TD-SCDMA

307.2 – 144 kb/s 200 - 90 kb/s DL In Development
“2.5G” 45 kb/s UL
IDEN
1xRTT RC3 GPRS
153.6 – 90 kb/s 40 – 30 kb/s DL CELLULAR 19 2 – 19.2
19.2 19 2 kb/s
15 kb/s UL
IS-95B IS-136 TDMA
GSM HSCSD 19.2 – 9.6 kb/s
SECOND 64 -32 kb/s
32 – 19.2 kb/s
GENERATION IS-95 GSM CSD
CDPD
19.2 – 4.8 kb/s
Mobitex
9.6 – 4.8 kb/s
14.4 – 9.6 kb/s 9.6 – 4.8 kb/s discontinued obsolete
 This summary is a work-in-progress, tracking latest experiences and reports from all the
high-tier (provider-network-oriented) 2G, 3G and 4G wireless data technologies
 Have actual experiences to share, latest announced details, or corrections to the above?
Email to Scott@ScottBaxter.com. Thanks for your comments!

The CDMA Migration Path to 3G
CDMAone CDMA2000 / IS-2000
Generation 1G 2G 2G 2.5G? 3G 3G 3G
IS-95A/ IS-2000: IS-2000: 1xEV-DO
1 EV DO 1xEV-DO
1 EV DO 1xEV-DV
Technology AMPS IS-95B Rev. 0 Rev. A
J-Std008 1xRTT 3xRTT IS-856 IS-856 1xTreme
Spectrum RL FL RL FL RL FL RL FL RL FL RL FL RL FL RL FL
Signal 1250 kHz. F: 3x 1250k 1250 kHz. 1250 kHz. 1250 kHz.
30 kHz. 1250 kHz. 1250 kHz. R: 3687k
Bandwidth, 50-80 voice 120-210 per 59 active 114 active Many packet
1 20-35 25-40 users users users
#Users and data 3 carriers
None,, 153K 2.4 Mb/s 3.1 Mb/s
Data DL
Capabilities 2.4K by 14.4K 64K 307K 1.0 Mb/s 153DL
Kb/s 1.8 Mb/s 5 Mb/s
modem 230K UL UL
High data
First Faster High data Higher
Features: Firstt
Fi •Improve
I •Enhanced
E h d rates
t on
System, data rates rates on data rates
Incremental CDMA, d Access Access Data-Voice
Capacity on shared data-only on data-
Capacity, •Smarter •Channel shared
Progress & 3-carrier CDMA only CDMA
Quality Handoffs Structure CDMA
Handoffs bundle carrier carrier
carrier

Modulation Techniques of 1xEV Technologies
 1xEV, “1x Evolution”, is a family of alternative QPSK

fast-data schemes that can be implemented on a CDMA IS-95,
1x CDMA carrier. IS-2000 1xRTT,
and lower rates
 1xEV
1 EV DO means “1x Evolution, Data Only”, of 1xEV-DO, DV
originally proposed by Qualcomm as “High Data
Rates” (HDR).
• Up to 2.4576 Mbps forward, 153.6 kbps
reverse
• A 1xEV DO carrier holds only packet data,
and does not support circuit-switched voice 16QAM
1xEV-DO
• Commercially available in 2003 at highest
 1xEV DV means “1x 1x Evolution,
Evolution Data and Voice
Voice”. rates
• Max throughput of 5 Mbps forward, 307.2k
reverse
• Backward compatible with IS-95/1xRTT
voice calls on the same carrier as the data
• Not yet commercially available; work
continues 64QAM
1xEV-DV
 All versions of 1xEV use advanced modulation at highest
techniques to achieve high throughputs. rates

GSM Technology Migration Path to 3G
Generation 1G 2G 2.5G or 3? 3G 3G
UMTS
various
Technology GSM GPRS EDGE UTRA
analog
WCDMA
Signal 200 kHz. 200 kHz. 3.84 MHz.
200 kHz.
kH up to
t 200+
200
Bandwidth, various Many fast data voice users
7.5 avg.
#Users Pkt. users many users and data
9-160 Kb/s
Data 384 Kb/s 2Mb/s
various none (conditions mobile user
Capabilities static user
determine)
•Packet IP Integrated
8PSK for voice/data
Features: Europe’s access
3x Faster (Future rates
Incremental various first Digital •Multiple
data rates to 12 MBPS
Progress wireless attached using adv.
than GPRS
users modulation?))

TDMA IS-136 Technology Migration Path to 3G
the familiar GSM path!
Generation 1G 2G 2G 2G 2.5G or 3? 3G 3G
TDMA UMTS
Technology AMPS CDPD IS-54 GSM GPRS EDGE UTRA
IS-136 WCDMA
Signal 30 kHz. 200 kHz. 200 kHz. 3.84 MHz.
30 kHz.
kH 30 kHz.
kH 200 kHz.
kH up to
t 200+
200
Bandwidth, Many Many fast data voice users
1 3 users 7.5 avg.
#Users Pkt Usrs Pkt. users many users and data
None, 9-160 Kb/s
Data 19.2
19 2 384 Kb/s 2Mb/s
2.4K by none none (conditions mobile user
Capabilities kbps static user
modem determine)
First •Packet IP Integrated

US USA s
USA’s Europe’s
Europe s 8PSK for voice/data
Features: System, access
Packet first first 3x Faster (Future rates
Incremental Capacity •Multiple
Data Digital Digital data rates to 12 MBPS
Progress & attached using adv.
Svc. wireless wireless than GPRS
Handoffs users modulation?))

SPEED: 1xEV-DO’s Purpose
Differences from CDMA2000 1xRTT

Why 1xEV-DO?
 To satisfy the ITU 3G vision of four radio environments:

• 9600 bps megacells – met by satellite-based
satellite based systems
• 144 kbps macrocells – met by CDMA2000 1xRTT RC3
• 384 kbps microcells – met by CDMA2000 1xRTT RC4 (307k)
• 2 mbps picocells – met by 1xEV-DO and 1xEV-DV
 To provide new applications for CDMA2000 users
• high
g speed
p data access and web applications
pp in the mobile
environment
• speeds up to 2.4 mbps

Why Can’t 1xRTT do high speeds?
 RF channel conditions change much faster than 1xRTT can track

• this causes 1xRTT to mismis-estimate
estimate the feasible data speed
which can be used for a burst of data
– sometimes conditions are worse than expected at the time
of a burst
burst, and the burst is received with severe errors
– other times the conditions are better than expected at the
time of a burst, and the burst transmitted more slowly than
actually
y could have been received
 Bursts in 1xRTT are so long that substantial latency is introduced
into error correction and packet repetition schemes
 For all these reasons,, something g more nimble is needed

Mobile RF Channel Conditions Change Rapidly
+6
elative dB
+4
Path Loss, re
+2
+0
-2
Path Loss, db
0 0.1 0.2 0.3 0.4 0.5
Time, Seconds
“Fast Fading” due to
“Slow Fading” due to user motion through
obstructions and user multipath
p fading
g
motion
ti standing-wave pattern
 Radio Transmission Technologies must be “nimble” enough to quickly
adapt for best results during changing channel conditions
• in choosing what data rate to transmit
• in power control of the forward and reverse links
1xRTT Data Burst Control Lags RF Conditions
+6
GOOD CONDITIONS DATA BURST
elative dB
ACTUALLY OCCURS
SION
+4 NOW
dB
TE DECIS
Eb/Nt, d
Path Loss, re
+2
+0
DATA RAT
BAD CONDITIONS
-2
Path Loss, db
0 0.1 0.2 0.3 0.4 0.5
D
Time, Seconds
BTS Setup Time Fixed Rate!
F-SCH
F-SCH Burst
F-FCH
SCH-Assignment Msg.
R-FCH
BILE
R-SCH
MOB
T
seconds 0 0.1 0.2 0.3 0.4 0.5
1xEV-DO vs. 1xRTT at the Same Time-Scale
AP 1xEV-DO Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.
Traffic
AT Setup time can be less than 10 ms
ms., depending on traffic loading
loading.
DRC
T
0 0.1 0.2 0.3 0.4 0.5
Time, Seconds
1 RTT
1xRTT
BTS Setup Time Fixed Rate!
F-SCH
F-SCH Burst
F FCH
F-FCH
SCH-Assignment Msg.
R-FCH
SCH-Request Msg.
MOBILE
R SCH
R-SCH
Thoughput: 0.15 or 0.31 Mb/s max, 0.06 Mb/s typ.

1xEV-DO Handles Data at the level of
Packets and Subpackets
AP 1xEV-DO Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.
Traffic
AT Setup time can be less than 10 ms
ms., depending on traffic loading
loading.
DRC
 Each forward traffic channel subpacket is only 1

1.67
67 ms long
• The flow of subpackets is stopped immediately when successful
decoding is achieved.
• The reaction to channel conditions is effectively instantaneous
instantaneous,
with no wasted excess energy!
 Short preambles and embedded MAC bits identify the destination
mobile
• No time is wasted sending layer-3 messages to control packet flow
 Each mobile DRC request is based on latest channel condition
• ACK/NAK commands can stop unneeded subpacket repetitions in
l
less th
than 5 ms.!!

The Key Features
and Structure of 1xEV-DO

Channel Structure of 1xEV-DO vs. 1xRTT
CHANNEL STRUCTURE
 IS-95 and 1xRTT IS-95 AND 1xRTT
Many users’ simultaneous forward
• many simultaneous users, each and reverse traffic channels
with steady forward and reverse PILOT
SYNC
W0
W32
traffic channels PAGING W1
F-FCH1 W17
• transmissions arranged, F-FCH2 W25
requested, confirmed by layer-3 F-FCH3 W41
messages – with some delay

delay…… W3
F-SCH
 1xEV-DO -- Very Different: BTS
F-FCH4 W53
• Forward Link goes to one user at a
time – like TDMA!
• users are rapidly time-multiplexed,
each receives fair share of ATs 1xEV-DO AP
available sector time (Access Terminals) (Access Point)
• instant preference given to user 1xEV-DO
O Forward
o a d Link
with
ith id
ideall receiving
i i conditions,
diti tto
maximize average throughput
• transmissions arranged and
requested via steady MAC-layer AP
walsh streams – very immediate!

Power Management of 1xEV-DO vs. 1xRTT
IS-95: VARIABLE POWER

POWER MANAGEMENT TO MAINTAIN USER FER
Maximum Sector Transmit Power
 IS-95
IS 95 and 1xRTT:
8
• sectors adjust each user’s 6
7
5
channel power to maintain a 5
5
ower
4
preset target FER 3
po
2
User 1
 1xEV-DO IS-856: PAGING
SYNC
PILOT
• sectors always operate at time
maximum power
• sector output is time- 1xEV-DO: MAX POWER ALWAYS,
DATA RATE OPTIMIZED
multiplexed, with only one
user served at any y instant
• The transmission data rate is power
set to the maximum speed
the user can receive at that
moment
time

Some EV-DO Terminology
IS-95, IS-2000, 1xRTT EV-DO
Phone,
Mobile, AT
Handset, or Access
Subscriber T
Terminal
i l
Terminal
Base Station, AP
BTS, Access
Cell Site Point

1xEV-DO Technical Details
Data Flow and Channels

1xEV-DO Transmission Timing
Forward Link
 All members of the CDMA family - IS-95, IS-95B,

1xRTT, 1xEV-DO and 1xEV-DV transmit
“Frames”
One Cycle of PN Short Code
• IS-95, IS-95B, 1xRTT frames are usually 20
ms. long
• 1xEV-DO frames are 26-2/3 ms. long
– same length as the short PN code O 1xEV-DO
One 1 EV DO F Frame
– each 1xEV-DO frame is divided into
1/16ths, called “slots”
 The Slot is the basic timing unit of 1xEV-DO
f
forward d lilink
k ttransmission
i i
• Each slot is directed toward somebody and
holds a subpacket of information for them
• Some slots are used to carryy the control
channel for everyone to hear; most slots are
intended for individual users or private groups
 Users don’t “own” long continuing series of slots One Slot
like in TDMA or GSM; instead, each slot or small
string of slots is dynamically addressed to
whoever needs it at the moment

What’s In a Slot?
½ Slot – 1024 chips ½ Slot – 1024 chips
PILOT
PILOT
MAC
MAC
MAC
MAC
SLOT DATA DATA DATA DATA
400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips
 The main “cargo” in a slot is the DATA being sent to a user

 But
B t allll users need d tto gett continuous
ti timing
ti i and
d administrative
d i i t ti
information, even when all the slots are going to somebody else
 Twice in every slot there is regularly-scheduled burst of timing and
administrative information for everyone to use
• MAC (Media Access Control) information such as power
control bits
• a burst of pure Pilot
– allows new mobiles to acquire the cell and decide to use it
– keeps existing user mobiles exactly on sector time
– mobiles use it to decide which sector should send them
their next forward link packet

What if there’s No Data to Send?
PILOT
PILOT
MAC
MAC
MAC
MAC
SLOT empty empty empty empty
 Sometimes there may be no data waiting to be sent on a sector’s

forward link
• When there’s no data to transmit on a slot, transmitting can be
suspended during the data portions of that slot
• But---the
B t th MAC and d PILOT mustt beb transmitted!!
t itt d!!
• New and existing mobiles on this sector and surrounding
sectors need to monitor the relative strength of all the sectors
and decide which one to use next
next, so they need the pilot
• Mobiles TRANSMITTING data to the sector on the reverse link
need power control bits
• So MAC and PILOT are always transmitted,
transmitted even in an empty
slot
Slots and Frames
PILOT
PILOT
MAC
MAC
MAC
MAC
Slot
FRAME
1 Frame = 16 slots – 32k chips – 26-2/3 ms
 Two Half-Slots make a Slot

 16 Slots make a frame

Frames and Control Channel Cycles
 A Control Channel Cycle is 16 frames (that’s 426-2/3 ms, about 1/2
second)
 The first half of the first frame has all of its slots reserved for possible use
carrying
i C Control
t l Ch
Channell packets
k t
 The last half of the first frame, and all of the remaining 15 frames, have
their slots available for ordinary use transmitting subpackets to users
Slot
FRAME
CONTROL
CHANNEL
USER(S) DATA CHANNEL
16-FRAME
CONTROL CHANNEL
CYCLE 16 Frames – 524k chips – 426-2/3 ms
That’s a lot of slots!

16 x 16 = 256

Forward Link Frame and Slot Structure:
“Big Picture” Summary
PILOT
PILOT
MAC
MAC
MAC
MAC
FRAME
CONTROL
CHANNEL
USER(S) DATA CHANNEL
16-FRAME
CONTROL CHANNEL
CYCLE 16 Frames – 524k chips – 426-2/3 ms
 Slots make Frames and Frames make Control Channel Cycles!

y
 Shorter Control Channel Cycles can be used for fast setup (PTT)

Reverse Link Frame and Slot Structure:
“Big Picture” Summary
SLOT DATA
FRAME
1 Subframe
holds S bf
Subframe S bf
Subframe S bf
Subframe
1 Subpacket
 Reverse Link frames are the same length as forward link frames
 The
Th mobile
bil d
does not iinclude
l d separate MAC and d Pil
Pilot b
bursts
• Its MAC and pilot functions are carried inside its signal by
simultaneous walsh codes
 There is no need for slots for dedicated control purposes since the
mobile can transmit on the access channel whenever it needs to

Rev. A Reverse Channel Sub-Frame Structure
RRI
DATA CHANNEL
DRC CHANNEL
ACK DSC ACK DSC ACK DSC ACK DSC
AUXILIARY PILOT CHANNEL
PILOT CHANNEL
1 Slot 1 Slot 1 Slot 1 Slot
1 Sub-Frame
 The mobile transmits sub

sub-packets
packets occupying four reverse link
slots, called a reverse link “sub-frame”.
 If multiple subpackets are required to deliver a packet, the
additional subpackets
p are spaced
p in every
y third subframe until
done

EV-DO Rev. A Channels
IN THE WORLD OF CODES
FORWARD CHANNELS REVERSE CHANNELS
Long PN
Access Channel
Acce
set W064 Pilot Pilot W016 for session setup
ACCESS
Short PN Offs
N offset
from Idle Mode
ess
W264 Rev Activity Data W24
DRCLock
MAC
W MAC Primary Pilot W016

just like IS-95
64
RPC
ARQ Auxiliary Pilot W2832
Public or Priva
P
ctor has a S
Access
Long PN offsett
RRI W416 Terminal
Wx16 Control (User
MAC DRC W816
Access Terminal)
DSC W1232
Point Wx16 Traffic Traffic Channel
Sec
(AP)
ate
as used during
ACK W1232 a data session
Walsh FORWARD Walsh
code Data W12
code
 The channels are not continuous like ordinary 1xRTT CDMA

 Notice the differences between the MAC channels and the Rev. 0
MAC channels – these are the heart of the Rev. 0/A differences

AP
Functions of Rev. A Forward Channels
FORWARD
•Access terminals watch the Pilot to select
CHANNELS
the strongest sector and choose burst speeds
set W064 Pilot
•The Reverse Activity y Channel tells
Short PN Offs
W264 Rev Activity ATs If the reverse link loading is

DRCLock too high, requiring rate reduction
MAC
W MAC
just like IS-95
64
RPC
ARQ
ctor has a S
Each connected AT has MAC channel:

Wx16 Control • DRCLock indication if sector busy
Access • RPC (Reverse Power Control)
Point Wx16 Traffic • ARQ to halt reverse link subpackets as
Sec
(AP)
soon as complete packet is recovered
Walsh
code
•Traffic channels •The Control channel carries
carry user data to overhead messages for idle ATs
one user at a time but can also carry user traffic
Forward Link Slot Structure (16 slots in a 26-2/3 ms. frame)
LOT
LOT
AC
AC
AC
AC
MA
MA
MA
MA
DATA DATA DATA DATA
PIL
PIL

Functions of Rev. A Reverse Channels
•The
Th Pilot
Pil t is
i used
d as a preamble
bl
during access probes
REVERSE CHANNELS
Long PN
•Data channel during access Access Channel
Acce
Pilot W016 for session setup
carries mobile requests ACCESS
N offset
from Idle Mode
ess
Data W24
• Primary Pilot on traffic channel
allows synchronous detection Primary Pilot W016
and also carries the RRI channel Auxiliary Pilot W2832
Public or Priva
P
Access
• Auxiliary Pilot on traffic channel
Long PN offsett
RRI W416 Terminal
allows synchronous detection (User
during high data rates MAC DRC W816
Terminal)
DSC W1232
Traffic Channel
•RRI
RRI reverse rate indicator tells
ate
as used during
AP what rate is being sent by AT ACK W1232 a data session
Data W12 Walsh
code
•DRC Data Rate Control channel
tells desired downlink speed
•DSC Data Source Control channel

tells which sector will send burst
•DATA channel during traffic
•ACK channel allows AT to signal
g carries the AT’s
AT s traffic bits
successful reception of a packet

Rev. A MAC Index Values and Their Uses
MAC INDEX MAC CHANNEL USE PREAMBLE USE PREAMBLE LENGTH
0, 1 Not Used Not Used N/A
2 Not Used Control 76.8 kbps 512
3 Not Used Control 38
38.4
4 kbps 1024
4 RA Channel Not Used N/A
5 RPC, DRC LOCK, ARQ Fwd TC if no Bcst Variable
64 and 65 Not Used Not Used N/A
66 Not Used Multi-User 128, 256, 512, 1024 256
67 Not Used Multi-User 2048 128
68 Not Used Multi-user 3072 64
71 Not Used Control 19
19.2,
2 38
38.4,
4 76
76.8
8 1024
6-63 and 72-127 RPC, DRC LOCK, ARQ Fwd TC, Single User Variable
 114 MAC indices are available for regular single-user packets

 3 MAC indices are earmarked for control channel packets
 5 MAC indices are reserved for multi-user packets
 1 MAC index is reserved for broadcast packets, or single-users
 4 MAC indices are not used due to conflicts with multiplexing patterns

Rev. A MAC Index and I/Q Channel Contents

The Earlier 1xEV-DO Rev. 0 Channels
IN THE WORLD OF CODES
FORWARD CHANNELS REVERSE CHANNELS
Long PN offset
Access Channel
W064 Pilot
Acc
set
Pilot W016 for session setup
Short PN Offs
cess
from Idle Mode
ACCESS
W264 Rev Activity Data W24
DRCLock MAC
MAC
W
just like IS-95
64
RPC Pilot
W016
RRI
Public or Priva
P
ctor has a S
Access
Wx16 Control
Long PN offsett
W0 W4 Terminal
Wx16 Traffic W1 W5 (User
MAC DRC W2 W6
W816
Access Terminal)
W3 W7
Point FORWARD Traffic Channel
Sec
(AP) Walsh
W l h
ate
as used during
code
ACK W48 a data session
Data W24 Walsh
code
 Th
These channels
h l are NOT CONTINUOUS like lik IS
IS-95
95 or 1
1xRTT!
RTT!
• They are made up of SLOTS carrying data subpackets to individual
users or control channel subpackets for everyone to monitor
g
• Regardless of who “owns” a SLOT,, the slot also carries two small
generic bursts containing PILOT and MAC information everyone can
monitor

AP
Functions of Rev. 0 Forward Channels
•Access terminals watch the Pilot to select
FORWARD CHANNELS the strongest sector and choose burst speeds
set W064 Pilot
Short PN Offs
•The Reverse Activity y Channel tells
W264 Rev Activity ATs If the reverse link loading is
DRCLock MAC too high, requiring rate reduction
MAC
W 64
RPC
•Each AT with open connection has a
ctor has a S
Wx16 Control MAC channel

h l including
i l di DRCLock
DRCL k andd
RPC (Reverse Power Control) muxed
Wx16 Traffic
Access using the same MAC index 5-63.
Point
Sec
(AP) •Traffic channels •The Control channel carries

carry user data to overhead messages for idle ATs
one user at a time but can also carry user traffic
IN THE WORLD OF TIME

Forward Link Slot Structure (16 slots in a 26-2/3 ms. frame)
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA
P
P

Functions of Rev. 0 Reverse Channels
•The Pilot is used as a preamble
during access probes REVERSE CHANNELS
Long PN offset
Acc
Pilot W016
•Data
Data channel during access
cess
ACCESS
carries mobile requests Data W24
•Pilot during traffic channel Pilot

W016
allows synchronous detection TRAFFIC RRI
Public or Priva
P
Access
Long PN offsett
and also carries the RRI channel W0 W4 Terminal
W1 W5 (User
MAC DRC W2 W6
W816
Terminal)
•RRI reverse rate indicator tells W3 W7
the AP the AT’s

AT s desired rate for
ate
ACK W48
reverse link data channel
Data W24
•DRC Data Rate Control channel

asks a specific sector to transmit
to the AT at a specific rate
•ACK channel allows AT to signal •DATA channel during traffic

successful reception of a packet carries the AT’s traffic bits

AP
The Rev. 0 MAC Index
MACIndex MAC Channel Use Preamble Use
0 and 1 Not Used Not Used
2 Not Used 76.8 kbps CCH
ode
ode
ode
ode
ex
ex
ex
ex
3 Not Used 38.4 kbps CCH
MACInde
MACInde
MACInde
MACInde
Walsh Co
Walsh Co
Walsh Co
Walsh Co
Phasee
Phasee
Phasee
Phasee
4 RA Channel Not Used
Available for RPC Available for
and DRCLock Forward
5-63
Channel Traffic Channel
0 0 I 32 16 I 1 32 Q 33 48 Q
Transmissions Transmissions
2 1 I 34 17 I 3 33 Q 35 49 Q
 Each active user on a sector is assigned a 4 2 I 36 18 I 5 34 Q 37 50 Q
unique 7-bit MAC index (64 MACs possible) 6 3 I 38 19 I 7 35 Q 39 51 Q
8 4 I 40 20 I 9 36 Q 41 52 Q
 Each data p packet begins
g with a p
preamble, 10 5 I 42 21 I 11 37 Q 43 53 Q
using the MAC index of the intended recipient
12 6 I 44 22 I 13 38 Q 45 54 Q
 Five values of MAC indices are reserved for 14 7 I 46 23 I 15 39 Q 47 55 Q
“multi-user” packets 16 8 I 48 24 I 17 40 Q 49 56 Q
• packets intended for reception by a group 18
8 9 I 50 25
5 I 19
9 41 Q 51
5 57
5 Q
20 10 I 52 26 I 21 42 Q 53 58 Q
– for example, control channels
22 11 I 54 27 I 23 43 Q 55 59 Q
• mobiles may have individual MAC indices 24 12 I 56 28 I 25 44 Q 57 60 Q
AND be simultaneously in various groups 26 13 I 58 29 I 27 45 Q 59 61 Q
• this “trick”
“ keeps payload size low even 28 14 I 60 30 I 29 46 Q 61 62 Q
for transmissions to groups 30 15 I 62 31 I 31 47 Q 63 63 Q

Forward Link Data Transmission
During an Established Connection
Including Rate Determination

Information Flow Over 1xEV-DO
Data Ready
D t ffrom PDSN ffor th
Data the M
Mobile
bil
DRC: 5
MP3, web page, or other content AP

 The system notifies a mobile when data for it is waiting to be sent
 The mobile chooses which sector it hears best at that instant, and requests
the sector to send it a packet
 there are 16 possible transmission formats the mobile may request, called
“DRC IIndices”.
di ” EEachh DRC IIndex
d value
l iis reallyll a combined
bi d specification
ifi i
including specific values for:
• what data speed will be transmitted
• how big a “chunk”
chunk of waiting data will be sent (that amount of data will be
cut of the front of the waiting data stream and will be the “Packet”
transmitted)
• what kind of encoding will be done to protect the data (3x Turbo, 5x
Turbo,, etc.)) and the symbol
y repetition,
p , if anyy
• after the symbols are formed, how many SUBpackets they will be
divided into
 Then, the sector starts transmitting the SUBpackets in SLOTS on the
forward link
 The first slot will begin with a header that the mobile will recognize so it can
begin the receiving process
Transmission of a Packet over EV-DO
Data the M
Mobile
bil D t R
Data Ready
d
MP3, web page, or other content

AP
A user has initiated a1xEV-DO data session on their AT,
accessing a favorite website.
The requested page has just been received by the PDSN.
The PDSN and Radio Network Controller send a “Data
Ready”
y message g to let the AT know it has data waiting.
g

Data the M
Mobile
bil D t R
Data Ready
d
DRC: 5
AP
A user has initiated a1xEV-DO data session on their AT,
DRC Modu- Preamble Payload Raw C/I
accessing a favorite website. Index Slots lation Chips Bits kb/s db
The requested page has just been received by the PDSN. 0x0 n/a QPSK n/a 0 null rate n/a
The PDSN and Radio Network Controller send a “Data 0x1 16 QPSK 1024 1024 38.4 -11.5
Ready”
y message g to let the AT know it has data waiting.
g 0x2 8 QPSK 512 1024 76.8 -9.2
0 3
0x3 4 QPSK 256 1024 153 6
153.6 -6.5
65
0x4 2 QPSK 128 1024 307.2 -3.5
The AT quickly determines which of its active sectors is the 0x5 4 QPSK 128 2048 307.2 -3.5
strongest. On the AT’s DRC channel it asks that sector to 0x6 1 QPSK 64 1024 614.4 -0.6
send it a packet at speed “DRC Index 5”. 0x7 2 QPSK 64 2048 614.4 -0.5
0x8 2 QPSK 64 3072 921.6 +2.2
0x9 1 QPSK 64 2048 1,228.8
1 228 8 +3 9
+3.9
The mobile’s
Th bil ’ choice,
h i DRC Index
I d 5, 5 determines
d t i everything:
thi
0xa 2 16QAM 64 4096 1,228.8 +4.0
The raw bit speed is 307.2 kb/s. 0xb 1 8PSK 64 3072 1,843.2 +8.0
The packet will have 2048 bits. 0xc 1 16QAM 64 4096 2,457.6 +10.3
There will be 4 subpackets (in slots 4 apart). 0xd 2 16QAM 64 5120 1,536.0 in Rev. A
The first subpacket will begin with a 128 chip preamble. 0xe 1 16QAM 64 5120 3,072.0 in Rev. A

Data the M bil PACKET
Mobile D t R
Data Ready
d
DRC: 5
2048 bits
AP
Using the specifications for Turbo Coder
the mobile’s requested DRC +
+ +
+ +
Index Slots lation Chips Bits kb/s db
index, the correct-size packet + D D D
0x0 n/a QPSK n/a 0 null rate n/a
+
of bits is fed into the turbo +
Interleaver
+
+
+ +
0x1 16 QPSK 1024 1024 38.4 -11.5
coder and the right
g number of + D D D 0x2 8 QPSK 512 1024 76.8 -9.2
+ 0 3
0x3 4 QPSK 256 1024 153 6
153.6 -6.5
65
symbols are created. Symbols 0x4 2 QPSK 128 1024 307.2 -3.5
0x5 4 QPSK 128 2048 307.2 -3.5
0x6 1 QPSK 64 1024 614.4 -0.6
0x7 2 QPSK 64 2048 614.4 -0.5
0x8 2 QPSK 64 3072 921.6 +2.2
0x9 1 QPSK 64 2048 1,228.8
1 228 8 +3 9
+3.9
0xa 2 16QAM 64 4096 1,228.8 +4.0
0xb 1 8PSK 64 3072 1,843.2 +8.0
0xc 1 16QAM 64 4096 2,457.6 +10.3
0xd 2 16QAM 64 5120 1,536.0 in Rev. A
0xe 1 16QAM 64 5120 3,072.0 in Rev. A

Mobile D t R
Data Ready
d
DRC: 5
2048 bits
AP
+ +
+ +
+
Interleaver
+
+
+ +
0x1 16 QPSK 1024 1024 38.4 -11.5
coder and the right
+ 0 3
0x3 4 QPSK 256 1024 153 6
153.6 -6.5
65
0x5 4 QPSK 128 2048 307.2 -3.5
To guard against bursty errors 0x6 1 QPSK 64 1024 614.4 -0.6
in transmission, the symbols 0x7 2 QPSK 64 2048 614.4 -0.5
are completely “stirred up” in Block Interleaver 0x8 2 QPSK 64 3072 921.6 +2.2
0x9 1 QPSK 64 2048 1,228.8
1 228 8 +3 9
+3.9
a block
bl k interleaver.
i t l
0xa 2 16QAM 64 4096 1,228.8 +4.0
0xb 1 8PSK 64 3072 1,843.2 +8.0
0xc 1 16QAM 64 4096 2,457.6 +10.3
0xd 2 16QAM 64 5120 1,536.0 in Rev. A
0xe 1 16QAM 64 5120 3,072.0 in Rev. A

Mobile D t R
Data Ready
d
DRC: 5
2048 bits
AP
+ +
+ +
+
Interleaver
+
+
+ +
0x1 16 QPSK 1024 1024 38.4 -11.5
coder and the right
+ 0 3
0x3 4 QPSK 256 1024 153 6
153.6 -6.5
65
0x5 4 QPSK 128 2048 307.2 -3.5
are completely “stirred up” in Block Interleaver 0x8 2 QPSK 64 3072 921.6 +2.2
0x9 1 QPSK 64 2048 1,228.8
1 228 8 +3 9
+3.9
a block
bl k interleaver.
i t l
0xa 2 16QAM 64 4096 1,228.8 +4.0
0xb 1 8PSK 64 3072 1,843.2 +8.0
The re-ordered stream of 0xc 1 16QAM 64 4096 2,457.6 +10.3
symbols is now ready to 0xd 2 16QAM 64 5120 1,536.0 in Rev. A
transmit. Interleaved Symbols 0xe 1 16QAM 64 5120 3,072.0 in Rev. A

Mobile D t R
Data Ready
d
DRC: 5
2048 bits
AP
+ +
+ +
+
+ +
Interleaver
+ +
0x1 16 QPSK 1024 1024 38.4 -11.5
coder and the right
+ 0 3
0x3 4 QPSK 256 1024 153 6
153.6 -6.5
65
are completely “stirred up” in 0x7 2 QPSK 64 2048 614.4 -0.5
a block interleaver. Block Interleaver 0x8 2 QPSK 64 3072 921.6 +2.2
0x9 1 QPSK 64 2048 1,228.8
1 228 8 +3 9
+3.9
Th re-ordered
The d d stream
t off
0xa 2 16QAM 64 4096 1,228.8 +4.0
symbols is now ready to 0xb 1 8PSK 64 3072 1,843.2 +8.0
transmit. The symbols are 0xc 1 16QAM 64 4096 2,457.6 +10.3
divided into the correct 0xd 2 16QAM 64 5120 1,536.0 in Rev. A
number of subpackets, which Interleaved Symbols 0xe 1 16QAM 64 5120 3,072.0 in Rev. A
will occupy the same number
of transmission slots, spaced
four apart.
acket 1
acket 2
acket 3
acket 4
It’s up to the AP to decide
when it will start transmitting
the stream, taking into account
Subpa
Subpa
Subpa
Subpa
any other pending subpackets

for other users, and
“proportional fairness”.

Mobile D t R
Data Ready
d
DRC: 5
2048 bits
AP
When the AP is ready, the first Turbo Coder
subpacket is actually +
+ +
+ +
transmitted in a slot. + D D D
+
The first subpacket begins with +
Interleaver
+
+
+ +
0x1 16 QPSK 1024 1024 38.4 -11.5
a preamble carrying
y g the + D D D 0x2 8 QPSK 512 1024 76.8 -9.2
+ 0 3
0x3 4 QPSK 256 1024 153 6
153.6 -6.5
65
user’s MAC index, so the Symbols
0x4 2 QPSK 128 1024 307.2 -3.5
user knows this is the 0x5 4 QPSK 128 2048 307.2 -3.5
start of its sequence of 0x6 1 QPSK 64 1024 614.4 -0.6
subpackets, and how 0x7 2 QPSK 64 2048 614.4 -0.5
many subpackets are in Block Interleaver 0x8 2 QPSK 64 3072 921.6 +2.2
0x9 1 QPSK 64 2048 1,228.8
1 228 8 +3 9
+3.9
th sequence..
the
0xa 2 16QAM 64 4096 1,228.8 +4.0
The user keeps collecting 0xb 1 8PSK 64 3072 1,843.2 +8.0
subpackets until either: 0xc 1 16QAM 64 4096 2,457.6 +10.3
1) it has been able to 0xd 2 16QAM 64 5120 1,536.0 in Rev. A
reverse-turbo decode the Interleaved Symbols 0xe 1 16QAM 64 5120 3,072.0 in Rev. A
packet contents early,
early or
2) the whole schedule of
subpackets has been
transmitted.
Subpackets
1 2 3 4
SLOTS

Ec/Io and C/I
 There are two main ways of expressing
signal quality in 1xEV-DO
AP
 C/I is the ratio of serving sector power to
everything else
Relationship of • C/I determines the forward data rate
C/I and Ec/Io • mobiles measure C/I during the pilot
For EV-DO
EV DO Signals burst period, then from it decide what
mobile receive power
data rate to request on the DRC
Power from
 Ec/Io is the ratio of one sector’s pilot power to
C Serving Sector Ec the total received power
Interference Power
• the mobile uses Ec/Io to choose which
I from other cells Io sectors to request for its active set
0
0
 Ec/Io and C/I are related, and one can be
calculated from the other
Ec/Io, db
-10
 EVDO Ec/Io is close to 0 db near a sector,
-20
and ranges down to -10 at a cell’s edge
E
 EVDO C/I can b be above

b +10 db near a
-30
-30 -20 -10 0 +10 +20 sector, and -20 or lower at the edge
C/I, db
Relationship of Ec/Io and C/I in 1xEV-DO Systems
-30 -25 -20 -15 -10 -5 0 5 10 15 20
0
Ec/Io,
C/I,
db
db
-0.04 20
-0.14 15
-0.17 14 -5
-0.21 13
-0.27 12
-0.33 11
-0.41
0 41 10 10
-10
-0.51 9
-0.64 8
c/Io, db
-0.79 7
-0.97 6 -15
1.19
-1.19 5
Ec
-1.46 4
-1.76 3
-2.12 2 -20
-2.54 1
-3.01 0
-3.54 -1
-4.12 -2
-25
-4.76 -3
-5.46 -4
-6.97 -6
-8.64
8 64 -8
8
-10.41 -10 -30
-12.27 -12 C/I, db

A
1xEV-DO Active Set and Forward Bursting
Animation - “Proportional Fairness”
Access
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
Access
Point
(AP)
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access NEIGHBOR
Point Access
(AP) Point
NEIGHBOR
((AP))
Access Route Update
Point
(AP)
NEIGHBOR
Access
Point
(AP)
NEIGHBOR NEIGHBOR
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
These sectors are your ACTIVE SET. Access
You may send DRC requests to any of them anytime. Point
Maybe you’ll get some data in response! (AP)
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Good Signal! Access
PACKET PLEASE! Point
@ x speed (AP)
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
Access
FOR YOU! ((AP))
Point
(AP)
NEIGHBOR
Access
Point
(AP)
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Good Signal!
g Access
(AP)
@ y speed
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
Access
FOR YOU! ((AP))
Point
(AP)
NEIGHBOR
Access
Point
(AP)
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Good Signal! Access
@ z speed (AP)
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
This isn’t one of his
(AP) Point
NEIGHBOR better receiving
moments I think I’ll
moments. I ll ((AP))
Access serve somebody
Point better this time.
(AP)
NEIGHBOR
Access
Point
(AP)
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Nothing… Access
did it forget Point
me? (AP)
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Access
Point
(AP)
DRC
Good Signal!
PACKET PLEASE!
@ x speed
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Access
Point
(AP)
DRC
ACTIVE FOR YOU! ACTIVE

Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

A
ACTIVE
Access ACTIVE
Point Access
(AP) Point
NEIGHBOR
((AP))
Access
Point
(AP)
NEIGHBOR
Good Signal! Access
@ x speed (AP)
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

ACTIVE
Access ACTIVE
Point Access
NEIGHBOR
(AP) THIS IS Point
((AP))
Access FOR YOU!
Point
(AP)
NEIGHBOR
Access
G d Signal!
Good Si l! Point
PACKET PLEASE! (AP)
@ x speed
DRC
ACTIVE ACTIVE
Access Access
Point Point DO-RNC
(AP) (AP)
Access
Node
(User
Terminal)

1xEV-DO Forward Link Details

1xEV-DO Protective Coding
Forward Traffic Channel Packets
or Control Channel Packets
bits symbols Turbo
Encoding Discard Encoder
Data Inter- 6-bit with an Code
and Encoder Internally- Symbols
Packet leaving
Scrambling Tail Field generated
tail
Data Total Bits Bits/Pkt

/ Symbols
Sy
 T
Turbo
b coding
di iis ththe default
d f lt Rate Slots Code per - Tail per
encoding method for 1xEV-DO on (kbps) Used Rate Packet Field Packet
both forward and reverse link 38.4 16 1/5 1,024 1,018 5,120
 The code rate is determined by: y 76.8 8 1/5 1,024
, 1,018
, 5,120
,
153.6 4 1/5 1,024 1,018 5,120
• input bit rate
307.2 2 1/5 1,024 1,018 5,120
• effective turbo coder rate, 614.4 1 1/3 1,024 1,018 3,072
including number of coder 307.2 4 1/3 2,048 2,042 6,144
outputs
t t and d symbol
b l puncturing
t i 614.4 2 1/3 2,048 2,042 6,144
 The data rate and number of slots 1,228.8 8 1/3 2,048 2,042 6,144
used per packet determine the 921.6 2 1/3 3,072 3,066 9,216
other
o e forward
o a d link variables
a ab es as 1,843.2 2 1/3 3,072 3,066 9,216
shown in the table at right 1,228.8 8 1/3 4,096 4,090 12,288
2,457.6 8 1/3 4,096 4,090 12,288

Data Scrambling in 1xEV-DO
Turbo Symbols
Encoding & Data Block
Data Bits ready to
Puncturing Scrambling Interleaving
Transmit
 IS-95 and 1xRTT use data scrambling on the forward link

• the scrambling sequence is a decimated version of the long PN
code
d ffrom th
the previous
i fframe
• the purpose is to randomize the waveforms of multiple users so
that the composite transmitted waveform has a low peak-to-
average ratio and effectively uses power amplifier capability
• a secondary purpose is to provide enhanced privacy
 1xEV-DO uses data scrambling on both links to randomize the
data and avoid unbalanced waveforms
• the scrambling sequence is generic, not unique per user
– security is already provided in a standard-defined layer
• the g
generic scramblingg register
g coefficients are specified
p in the
standard

One Slot on the Forward Traffic Channel
Example Subpacket: 1536 Data Modulation Symbols (1 slot, 614.4 Kb/s)
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA
64 336 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips
Data 1/3 or 1/5 Channel QPSK/8PSK Sequence

Repetition,
Symbol 16-ary Walsh Walsh
I
To
16QAM DEMUX Walsh Channel Chip Level
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
Interleaver Modulator Q
Puncturing 1 to 16 Covers Gain Summer
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
me Division Multiplexer
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal
e Spreading and Modula

els
MAC cover
Signal RPC MAC Index Walsh Cover

MAC RPC bits A Point Channel
Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
MAC channel Repetition Point Channel
I I
Walsh Sequence
DRC Lock symbols (xDRCLlen) Mapping Gain Chip Level Repetition
Summer Q (factor=4) Q
MAC Bit Signal RA
channel Repetition Point channel Walsh Cover 0
(xRAB len) Mapping gain
RA bits Signal
els
ation
I
Walsh Cover W264 Point
Mapping
Pilot Channel (all 0s) 0
Q

A
1. Data SubPacket is Ready to Send
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
2. Send Preamble to Notify Destination Mobile
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
3. Send First 336 Data Symbols
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
4. Send MAC Channel – Part 1
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
5. Send Pilot – First Half Slot
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
6. Send MAC Channel - Second Part
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
7. Send Next 800 Data Symbols
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
8. Send MAC Channel – Third Part
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
9. Send Pilot – Second Half-Slot
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
10. Send MAC Channel – Fourth Part
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
11. Send Last 400 Data Symbols
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

A
One Slot on the Forward Traffic Channel
PRBL
PILOT
PILOT
MAC
MAC
MAC
MAC
DATA DATA DATA DATA

Repetition,
I
To
o Quadrature
(modulation Signal
I Walsh Channe
encoder
d I t l
symbols)
TDM Tim
I
Signal
scrambler Sequence
Preamble Point
Repetition Q
Mapping 0
32-symbol
32 symbol bi
bi-Orthogonal
Orthogonal

els
MAC cover

Mapping Gain
Q Walsh Channe
Bit Signal DRC Lock
M
I I
Walsh Sequence
MAC Bit Signal RA
RA bits Signal
els
ation
I
Mapping
Q

AP
Forward MAC Contents
 RA: Reverse Activity

• The AP must manage its reverse traffic loading to keep the noise
l
levell manageable
bl
• Reverse noise is directly proportional to the speed at which
mobiles transmit on the reverse link
• When noise is too high,
high the AP can throttle back all the ATs
 DRC Lock
• This forward channel contains a stream of bits indicating whether
the network currently will allow the mobile to transmit requests on
the reverse DRC channel; timing and signal quality conditional
parameters are also involved
• The DRC Lock bits and DRC Lock state is independent per
sector A mobile should not transmit DRC requests to a sector
sector.
sending DRC Lock indication, but may transmit DRC requests to
other sectors in its active set
 RPC: Reverse Power Control bits instruct the mobile to increase or
decrease its transmit power by a programmable increment, in much
the same way as in IS-2000. The rate is 600 bps.
Reverse MAC Channel Contents
 The Reverse MAC channel contains two streams of information

 DRC Data Rate Control channel is used by the AT to request the
data rate and desired sector
• Data rate is requested using 8-ary bi-orthogonal coding
• Desired sector is requested
q using
g 8-ary
y Walsh cover
• Each DRC channel slot contains 1024 chips to facilitate reliable
detection
• DRC messages start at the center of a slot to minimize the
d l b
delay between
t C/I estimation
ti ti and d th
the start
t t off AP ttransmission
i i
 RRI Reverse Rate Indicator channel identifies up to 8 different
desired reverse data transmission rates
• 8-ary
8 ary orthogonal code is used to indicate rates
• The RRI symbol is transmitted 32 times in each frame
• RRI symbols are inverted in the last half of the frame to make
synchronization easier

How the DRC Channel Operates
 The AT estimates the forward channel C/I and identifies the

feasible data rate and the requested sector to be used
 The AT sends this information to the AP on the DRC channel
 Only the requested sector will transmit packets to this AT
 The requested sector sends a data packet including preamble to
the AT at the rate requested by the DRC in the immediately
preceding slot
 After the packet transmission is initiated
initiated, it must be continued until
the payload has been fully transmitted

Hybrid ARQ:
Hybrid Repeat-Request Protocol

The Hybrid ARQ Process
CDMA2000 1xEV-DO
AP Access Point AT Access Terminal
Application layer Application layer
CDMA2000 1xRTT
SYSTEM Stream layer Stream layer
Application layer Application layer S

Session
i llayer S
Session
i llayer
Connection layer Connection layer
LAC layer LAC layer
Security layer Security layer
MAC RLP Radio MAC RLP Radio MAC layer MAC layer
layer Link Protocol layer Link Protocol
Physical
Ph i l Physical
Ph i l Physical
Ph i l HARQ Physical
Ph i l HARQ
layer layer layer protocol layer protocol
F-FCH F-TFC repeats

R-FCH R-ACK
 In 1xRTT,
1 RTT retransmission protocols  In 1
1xEV-DO,
EV DO RLP ffunctions
nctions are
typically work at the link layer replicated at the physical layer
• Radio Link Protocol (RLP) • HARQ Hybrid Repeat Request Protocol
– communicates using g – fast p
physical
y layer
y ACK bits
signaling packets – Chase Combining of multiple
– lost data packets aren’t repeats
recognized and are – unneeded repeats pre-empted
discarded at the decoder by positive ACK
 This method is slow and wasteful!  This method is fast and efficient!

The Hybrid ARQ Process
 Each physical layer data packet is encoded into subpackets

• as long as the receiver does not send back an
acknowledgment, the transmitter keeps sending more
subpackets, up to the maximum of the current configuration
• The identity of the subpackets is known by the receiver, so it
can combine the subpackets for better decoding
 each additional subpacket in essence contributes additional signal
power to aid in the detection of its parent packet
• it
it’ss hard to predict the exact power necessary for successful
decoding in systems without HARQ
– the channel changes rapidly during transmission
– various estimation errors ((noise,, bias,, etc.))
– exact needed SNR is stochastic, even on a static channel!
 In effect, HARQ sends progressively more energy until there is just
enough and the packet is successfully decoded

Construction of a Forward Link Packet
bits symbols
Sub- Sub- Sub- Sub- Sub-
Data Inter- packet packet packet packet packet
Encoding
Packet leaving 0 1 2 3 0
 Physical Layer Packets encoded, interleaved, broken into subpackets

• each subpacket is a unique coded representation of the packet
 Each subpacket is sent independently during one slot
• Subpackets are sent in sequential order with a three-slot gap between
successive subpackets
Packet 0 other other other 0 other other other 0 other other other 0 other other other 1
Subpacket 0 pkts pkts pkts. 1 pkts. pkts. pkts. 2 pkts. pkts pkts 3 pkts pkts pkts 0
Forward
Traffic
Channel One Slot
 The receiver combines successive subpackets until it finally decodes the

complete packet contents
• then sends an “ACK”
ACK to cancel any remaining unneeded subpackets
• this Hybrid ARQ (HARQ) process gives “incremental redundancy”
Multislot Packet Timing, Normal Termination
User A A A A A
AP Packet 0
Subpacket 0
diff. diff. diff.
user user user 0
1
diff. diff. diff.
user user user 0
2
diff. diff. diff.
user user user 0
3
diff. diff. diff.
user user user 1
0
F-Traffic
AT R-DRC
1/2 Slot
offset
R-ACK
One Slot NAK NAK NAK AK!
 AT selects
l t sector,
t sends d requestt ffor d
data
t
 AP starts sending next packet, one subpacket at a time
 After each subpacket, AT either NAKs or AKs on ACK channel
 In this example,
• AP transmits all 4 scheduled subpackets of packet #0 before
the AT is finally
y able to decode correctly
y and send AK
• then the AP can begin packet #1, first subpacket

Multislot Packet Timing, Early Termination
User A A A A A
AP Packet 0
Subpacket 0
diff. diff. diff.
user user user 0
1
diff. diff. diff.
user user user 1
0
diff. diff. diff.
user user user 1
1
diff. diff. diff.
user user user 2
0
F-Traffic
AT R-DRC
1/2 Slot
offset
R-ACK
One Slot NAK AK! NAK AK!
 AT selects
l t sector,
t sendsd requestt ffor d
data
t
 AP starts sending next packet, one subpacket at a time
 After each subpacket, AT either NAKs or AKs on ACK channel
 I this
In thi example,l
• AT is able to successfully decode packet #0 after receiving
only the first two subpackets
• AT sends ACK.
ACK AP now continues with first subpacket of
packet #1

A
Multiple ARQ Instances

bits symbols
Packet 0
Encoding
Data
and
Inter- Subpackets
Packets leaving
Scrambling
0 1 2 3
Packet 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3.
p
Subpacket 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3
F
Forward
d
Traffic
Channel One Slot
 Definition: Number of ARQ Instances

• the maximum number of packets that may be in transit simultaneously
• sometimes also called “the number of ARQ channels”
 This figure and the preceding page appear to show 4 ARQ instances
 Packets in the different ARQ instances
• may be for the same user (the most common situation)
• may be for different users (determined by QOS and scheduling)
 Destination mobile knows its packets by their preamble
A

bits symbols
Packet 0 Packet 1
Encoding
Data
and
Inter- Subpackets Subpackets
Packets leaving
Scrambling
0 1 2 3 0 1 2 3
Packet 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3.
p
Subpacket 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3
F
Forward
d
Traffic
Channel One Slot

A

bits symbols
Packet 0 Packet 1 Packet 2
Encoding
Data
and
Inter- Subpackets Subpackets Subpackets
Packets leaving
Scrambling
0 1 2 3 0 1 2 3 0 1 2 3
Packet 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3.
p
Subpacket 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3
F
Forward
d
Traffic
Channel One Slot

bits symbols
Packet 0 Packet 1 Packet 2 Packet 3
Encoding
Data
and
Inter- Subpackets Subpackets Subpackets Subpackets
Packets leaving
Scrambling
0 1 2 3 0 1 2 3 0 1 2 3 0 1 2 3
Packet 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3. 0 1. 2. 3.
p
Subpacket 0 0 0 0 1 1 1 1 2 2 2 2 3 3 3 3
F
Forward
d
Traffic
Channel One Slot

Reverse Power Control
600 bits per second
AP RX RF Digital
Stronger than Reverse
Open
O Closed
Cl d
target SNR? RF Loop Loop
SNR target TX RF Digital
Access Terminal
 1xEV-DO reverse link power control is similar to IS-95/IS-2000
 1xEV
1xEV-DODO power control holds the mobile pilot to a constant S/N
ratio at the Access Point
• The DRC, RRI, and ACK channels are also controlled
• The ideal ratio of reverse ppilot to other channels also depends
p
on the reverse data rate
 Power control bits are sent on the forward MAC channel
• one bit per slot (that’s 600 per second), sent as four symbols --
one in each of the MAC periods of that slot

Reverse Rate Control

Rev. 0 Reverse Rate Control
 The essence is “immediate rate reduction by every sector user when commanded”, then
statistical throttling of rate increases when permissible
 Variables:
V i bl M R t C
MaxRate, CurrentRate,
tR t C CombinedBusyBit,
bi dB Bit and
d CurrentRateLimit.
C tR t Li it
 CurrentRateLimit is set initially to 9.6kbps.
 After the AT receives a BroadcastReverseRateLimit message or a UnicastReverseRateLimit
message it updates the CurrentRateLimit value as follows:
• If RateLimit in the message is < <= CCurrentRateLimit,
rrentRateLimit AT immediatel
immediately sets C CurrentRateLimit
rrentRateLimit
=RateLimit given in the message.
• If RateLimit in the message is > CurrentRateLimit, the AT waits one frame (16 slots) before
setting CurrentRateLimit = RateLimit value in the message.
 If the last received reverse activity bit is set to ‘1’
1 from any sector in the AT’s
AT s active set, the AT
sets CombinedBusyBit to ‘1’. Otherwise, the AT sets CombinedBusyBit to ‘0’.
 CurrentRate is set to rate at the AT was transmitting just prior to new transmission time. If the
AT was not transmitting data just prior, the AT sets CurrentRate to 0.
 The AT sets MaxRate based on current transmission rate, CombinedBusyBit, and a random
numberb uniformly
if l di
distributed
t ib t d x, 0 < x < 11, using
i ththe procedure
d specified
ifi d iin 15
15.5.
5
 The AT evaluates the expression shown in the table, using the values of CurrentRate,
CombinedBusyBit, and Condition.
• If the Condition is true, the AT sets MaxRate to the MaxRateTrue value for the
corresponding row in the Table.
Table
• Otherwise, the AT sets MaxRate to the MaxRateFalse value for the corresponding row in
the Table

Rev. A Reverse Rate Control
 Rev. A Reverse Rate Control is based on a Token Bucket

Algorithm. A user is granted tokens at a system-determined level
based on QOS factors, reverse link loading, and traffic
traffic-to-pilot
to pilot
(T2P) considerations.
 When the Reverse Activity Bit is 0, operation is unrestricted and
users accumulate tokens allowing rapid uplink speeds.
 When the Reverse Activity Bit is 1, token assignment is
substantially reduced and uplink rates rapidly decline.

Available Link Rates in 1xEV-DO Rev. A
FORWARD LINK REVERSE LINK
DRC Modu- Preamble Payload Raw C/I Payload Modu-Effective Rate kbps after: Code Rate (repetition) after
Index Slots lation Chips Bits kb/s db Bits lation 4 slots 8 slots 12 slots16 slots 4 slots 8 slots 12 slots16 slots
0x0 n/a QPSK n/a 0 null rate n/a 128 B4 19.2 9.6 6.4 4.8 1/5 1/5 1/5 1/5
0x1 16 QPSK 1024 1024 38.4 -11.5 256 B4 38 19.2 12.8 9.6 1/5 1/5 1/5 1/5
0 2
0x2 8 QPSK 512 1024 76 8
76.8 -9.2
92 512 B4 76 38.438 4 25.6
25 6 19.2
19 2 1/4 1/5 1/5 1/5
0x3 4 QPSK 256 1024 153.6 -6.5 768 B4 115 57.6 38.4 28.8 3/8 1/5 1/5 1/5
0x4 2 QPSK 128 1024 307.2 -3.5 1024 B4 153 76.8 51.2 38.4 1/2 1/4 1/5 1/5
0x5 4 QPSK 128 2048 307.2 -3.5 1536 Q4 230 115 76.8 57.6 3/8 1/5 1/5 1/5
0x6 1 QPSK 64 1024 614.4 -0.6 2048 Q4 307 153 102.4 76.8 1/2 1/4 1/5 1/5
0x7 2 QPSK 64 2048 614.4 -0.5 3072 Q2 461 230 153.6 115.2 3/8 1/5 1/5 1/5
0x8 2 QPSK 64 3072 921.6 +2.2
2.2 4096 Q2 614 307 204.8 153.6 1/2 1/4 1/5 1/5
0x9 1 QPSK 64 2048 1,228.8 +3.9 6144 Q4Q2 921 461 307 230.4 1/2 1/4 1/5 1/5
0xa 2 16QAM 64 4096 1,228.8 +4.0 8192 Q4Q2 1228 614 409 307.2 2/3 1/3 2/9 1/5
0xb 1 8PSK 64 3072 1,843.2 +8.0 12288 E4E2 1843 921 614 460.8 2/3 1/3 1/3 1/3
0xc 1 16QAM 64 4096 2,457.6 +10.3
0xd 2 16QAM 64 5120 1,536.0 +8.3
0xe 1 16QAM 64 5120 3,072.0 +11.3
 The 1xEV-DO Rev. A reverse link has seven available modes

offering
ff i higher
hi h speedsd than
th available
il bl iin R
Rev. 0
• Modulation formats are hybrids defined in the standard
 The 1xEV-DO Rev. A forward has two available modes offering
hi h speeds
higher d th
than available
il bl iin R
Rev. 00.

Forward Link Enhancements in 1xEV-DO Rev. A
 Forward Link Enhancements

• Peak rates increased from 2.4 Mbps to 3.1 Mbps
• Multi-user
Multi user packet support
• Small payload sizes (128, 256, 512 bits) improve frame fill efficiency
• The DRC channel functions are broken out into two channels
– DRC retains rate control indication
– new Data Source Control (DSC) Channel shows desired serving cell
• Minimizes interruptions due to server switching on FL

Reverse Link Enhancements in 1xEV-DO Rev. A
 Reverse Link Enhancements

• Higher data rates and finer quantization
• Data rates from 4 4.8
8 kbps to 1.8
1 8 Mbps with 48 payload sizes
• 4 slots/sub-packets regardless of payload size (6.66 ms)
• Modulation:
– Low rates: 1 walsh channel, BPSK modulation
– Medium rates: 1 walsh channel, QPSK modulation
– High Rates: 2 walsh channels, QPSK modulation
– Highest Rate: 2 walsh channels, 8PSK modulation
• Hybrid ARQ using fast re-transmission (re-tx) and early termination
• Flexible rate allocation: each AT has autonomous and scheduled mode
• Efficient VOIP support
• 3-channel synchronous stop-and-wait protocol
• The mobile can use higher power and finish earlier when transmitting
packets of applications requiring minimum latency

Basic Access Terminal
Architecture and Operation

How Does an Access Terminal Work?
Digital
Di it l
Rake Receiver Symbols
Chips Traffic Correlator
ming
PN xxx Walsh xx
summ
bits
Traffic Correlator
t 
PN xxx Walsh xx
ontrol
Symbols
Receiver Viterbi Decoder,
Decoder
co
Traffic Correlator
ttime-aligned
d
RF Section Convl. Decoder,
IF, Detector PN xxx Walsh xx Demultiplexer
power
Traffic Correlator Packets
AGC
PN xxx Walsh xx
RF
Open L
Messages
UART
Duplexer Pilot Searcher
CPU
PN xxx Walsh 0
Loop
Conv or
C
RF Transmit Gain Adjust Messages Turbo
Coder
Transmitter
Transmitter Digital Section
RF Section
Long Code Gen.

1xEV-DO Forward Link: AT Rake Receivers
Access Terminal
ONE sector at a time!!
Rake Receiver
PN Walsh
PN Walsh
 user
RF PN Walsh data
AP
PN Walsh
AP
Searcher Pilot Ec/Io
PN W=0
 Burst by burst, the Access Terminal asks for transmission from whichever
Active sector it hears best, at the max speed it can successfully use
 Using latest multipath data from its pilot searcher, the Access Terminal uses
the combined outputs
p of the four traffic correlators ((“rake fingers”)
g )
 Each rake finger can be set to match any multipath component of the signal
 The terminal may be a dual-mode device also capable of 1xRTT voice/data
• fingers could even be targeted on different AP, but in 1xEV-DO mode
only a single AP transmits to usus, never more than one at a time time, so this
capability isn’t needed or helpful in 1xEV-DO mode

1xEV-DO Reverse Link: Soft Handoff
All “Active Set” sectors Access Terminal
can listen to the AT
Rake Receiver
PN Walsh
PN Walsh
 user
RF PN Walsh data
AP
PN Walsh
DO-RNC chooses AP
‘cleanest’ packet PN W=0
 The AT uses the Route Update protocol to frequently update its

preferences of which sectors it wants in its active set
 Frame-by-frame, all the sectors in the Active Set listen for the AT’s
signal
i l
 Each sector collects what it heard from the AT, and sends it back to
the DO-RNC.
 The DO-RNC uses the cleanest (lowest number of errors) packet

1xEV-DO Route Update Mechanics
Access Terminal
Rake Receiver
DO-RNC PN Walsh
? PN Walsh

S l
Sel. ? RF PN Walsh user
ser
data
AP PN Walsh
AP Searcher Pilot Ec/Io

PN W=0
 1xEV-DO Route Update is ‘driven’ by the Access Terminal

• Access Terminal continuously checks available pilots
• Access Terminal tells system pilots it currently sees
• System puts those sectors in the active set, tells Access Terminal
 Access terminal requests data bursts from the sector it likes best
• tells which sector and what burst speed using the DRC channel
• so there is no “Soft Handoff” on the forward link, just fast choices
 All sectors in Active Set try to hear AT, forward packets to the DO-RNC
• so the reverse link does benefit from CDMA soft handoff

Route Update Pilot Management Rules
 The Access Terminal considers pilots in sets PILOT SETS
AT m
• Active: sectors who listen and can transmit Active 6
must supp
• Candidates: sectors AT requested, but not
yet approved by system to be active Candidate 6
• Neighbors: pilots told to AT by system, as Neighbor 20
nearby sectors to check
port
• Remaining: any pilots used by system but Remaining
not already in the other sets (div. by PILOT_INC)
 Access Terminal sends a Route Update HANDOFF
Message to the system whenever: PARAMETERS
• It transmits on the Access Channel PilotAdd PilotDrop
• In idle state, it notices the serving sector is PilotDrop Pilot
far from the sector where last updated Timer Compare
• In connected state, whenever it notices the Dynamic Thresholds?
Handoff Parameters suggest a change Softslope
AddIntercept
DropIntercept
NeighborMaxAge

Format of Traffic Channel Assignment Message
 The Traffic Channel

Assignment Message
assigns all or some of the
sectors the access terminal
requested in its most recent
Route Update request
 The message lists every
Active pilot; if it doesn’t list it,
it’ss not approved as active
it
 Notice the MAC index and
DRC Cover so the access
terminal knows how to
request forward link bursts
on the data rate control
channel
Neighbor Structure Maintained by the AT
Pilot PN Channel SrchWinSize SrchWinOffset

1xEV-DO Network Architecture
Simple IP and Mobile IP

CDMA Network for Circuit-Switched Voice Calls
(C)BSC/Access Manager
Switch
PSTN v SEL CE
t1 t1 t1
BTS
 The first commercial IS

IS-95
95 CDMA systems provided only circuit
circuit-
switched voice calls

CDMA 1xRTT Voice and Data Network
PDSN
Foreign Agent
Backbone
Internet Network
VPNs
PDSN Authentication
Home Agent Authorization AAA (C)BSC/Access Manager
Accounting
Switch
PSTN v SEL CE
t1 t1 t1
BTS
 CDMA2000 1xRTT networks added two new capabilities:

p
• channel elements able to generate and carry independent streams of
symbols on the I and Q channels of the QPSK RF signal
– this roughly doubles capacity compared to IS-95
• a separate IP network implementing packet connections from the mobile
through to the outside internet
– including Packet Data Serving Nodes (PDSNs) and a dedicated direct
data connection (the Packet
Packet-Radio
Radio Interface) to the heart of the BSC
 The overall connection speed was still limited by the 1xRTT air interface

1xEV-DO Overlaid On Existing 1xRTT Network
PDSN
Foreign Agent DO DO-OMC
Backbone
Radio
Internet Network Network
VPNs C t ll
Controller
PDSN Authentication
Accounting
Switch CE
PSTN v SEL CE
t1 t1 t1
BTS
 1xEV-DO requires
q faster resource management
g than 1x BSCs can ggive
• this is provided by the new Data Only Radio Network Controller (DO-RNC)
 A new controller and packet controller software are needed in the BTS to
manage the radio resources for EV sessions
• in some cases dedicated channel elements and even dedicated backhaul is
used for the EV-DO traffic
 The new DO-OMC administers the DO-RNC and BTS PCF addition
 Existing PDSNs and backbone network are used with minor upgrading
 The following sections show Lucent, Motorola, and Nortel’s specific solutions
Simple IP Network Architecture
Simple IP
IP Based
transport to FAST IP PACKET TRAFFIC
data networks PDSN
Internet
Dynamic/static VPNs T
connection Authentication
Authorization R-P Interface
rf
from local AAA Accounting
PDSN (C)BSC/Access Manager Fast!
No mobility Switch BTS
beyond serving PSTN v SEL CE
PDSN t1 t1 t1
CIRCUIT-SWITCHED VOICE TRAFFIC POINT-TO-POINT PACKETS Wireless
Mobile Device
 In a Simple IP network, the mobile is able to connect to the external

packet networks directly through the PDSN attached to the local BSC
 The IP address for the internet connection is assigned
g by
y the local
PDSN from the pool of addresses available to it
 If the mobile moves into a different network, the data session ends
• The mobile can establish an entirely new connection through the
new network,
t k if desired
d i d

Mobile IP in a Multi-Market Network
Private IP
Internet
Networks
Regional
Data Home Home AAA
Center Agent Agent Server
Operator's Private Network

Nortel System Lucent System Motorola System
IP Data IP Data IP Data
PCF
PDSN
PDSN RP Interface FA
FA RP
BSC RP PDSN/FA
Access CBSC
Switch Mgr. Switch
Switch
Voice Voice Voice
PSTN PSTN PSTN

Mobile IP
 Subscriber’s IP routing service is

provided by a public IP network
 Mobile station is assigned a static IP
address belonging to its Home Agent MOBILE IP
 Mobile can maintain the static IP IMPLICATIONS
address even for handoff between •Handoffs possible between
radio networks connected to separate PDSNs
PDSNs! •Mobile can roam in the
 Mobile IP capabilities will be public IP network
especially important for mobiles on •Mobile termination is
possible while Mobile is in
system boundaries dormant or active mode
• Without
With t M Mobile
bil IP roaming
i
capability, data service for border-
area mobiles will be erratic

How the PDSN HA and FA Forward Your Packets
Mobile IP is a packet-
forwarding
arrangement that
allows the mobile user
to send and receive
Just like
Home! packets just as if they 158766 158774 158782 158790
Foreign were physically present

Agent at their home agent Home 158767
158768
158775
158776
158783
158784
158791
158792
location. Agent 158769 158785 158793
158770 158778 158786 158794

Encapsulation
158771 158779 158787 158795
158772 158780 158788 158796
158773 158781 158789 158797

dEx
dEx
Secure Tunneling
g
Fed
Fed
Forward and Reverse This box is the
Mobile mobile user's
User Postal address

1xEV-DO Network Architecture

CDMA Network for Circuit-Switched Voice Calls
(C)BSC/Access Manager
Switch
PSTN v SEL CE
t1 t1 t1
BTS
 The first commercial IS

IS-95
95 CDMA systems provided only circuit
circuit-
switched voice calls

CDMA 1xRTT Voice and Data Network
PDSN
Foreign Agent
Backbone
Internet Network
VPNs
PDSN Authentication
Accounting
Switch
PSTN v SEL CE
t1 t1 t1
BTS
 CDMA2000 1xRTT networks added two new capabilities:

p
• channel elements able to generate and carry independent streams of
symbols on the I and Q channels of the QPSK RF signal
– this roughly doubles capacity compared to IS-95
• a separate IP network implementing packet connections from the mobile
through to the outside internet
– including Packet Data Serving Nodes (PDSNs) and a dedicated direct
data connection (the Packet
Packet-Radio
Radio Interface) to the heart of the BSC
 The overall connection speed was still limited by the 1xRTT air interface

1xEV-DO Overlaid On Existing 1xRTT Network
PDSN
Foreign Agent DO DO-OMC
Backbone
Radio
Internet Network Network
VPNs C t ll
Controller
PDSN Authentication
Accounting
Switch CE
PSTN v SEL CE
t1 t1 t1
BTS
 1xEV-DO requires
q faster resource management
g than 1x BSCs can ggive
• this is provided by the new Data Only Radio Network Controller (DO-RNC)
 A new controller and packet controller software are needed in the BTS to
manage the radio resources for EV sessions
• in some cases dedicated channel elements and even dedicated backhaul is
used for the EV-DO traffic
 The new DO-OMC administers the DO-RNC and BTS PCF addition
 Existing PDSNs and backbone network are used with minor upgrading
 The following sections show Lucent, Motorola, and Nortel’s specific solutions
Lucent 1xEV-DO Architecture

Lucent 1xEV-DO Radio Access Network (RAN)
OMP FX
Element Management
System T-1/E-1
Ethernet
RF
AP Router AAA
Server
Uplink Flexent Downlink

AP Input Mobility Input
Router Server Router Packet
Data
g
Serving Internet
AP Node
Uplink Flexent Downlink (PDSN)
RF Input Mobility Input
Router Server Router
User ATs AP
(Access Terminals)
 A Lucent 1xEV-DO Radio Access Network (RAN) includes

• 1xEV-DO base stations and the
• 1xEV-DO
1 EV DO Flexent®
Fl t® Mobility
M bilit Server
S (FMS).
(FMS)
 The 1xEV-DO equipment may be collocated with IS-95 and/or
1xRTT equipment, creating 1xEV-DO/IS-95 and 1xEVDO/3G-1X
combination base stations
stations.

Details of Lucent RAN Elements
OMP FX
Element Management
System T-1/E-1
Ethernet
RF
AP Router AAA
Server
Uplink Flexent Downlink

AP Input Mobility Input
Router Server Router Packet
Data
g
Serving Internet
AP Node
Uplink Flexent Downlink (PDSN)
RF Input Mobility Input
Router Server Router
User ATs AP
(Access Terminals)
 The PDSN maintains the link layer to the AT

• it terminates the PPP link protocol with mobile
• it serves as the Foreign
g Agentg for Mobile IP functionality
y
 The AAA server does authentication, authorization, and accounting
• it authenticates terminal equipment users when they establish
connections
• it stores and for
forwards
ards billing information of ccustomers’
stomers’ data usage
sage

1xEV-DO in Lucent Flexent Mod Cell Cabinets
 Lucent Mod Cell cabinets can

support up to three IS IS-95
95 or
1xRTT carriers on three
sectors
 1xEV-DO CDMA Digital
Modules (CDM) can be mixed
with conventional CDMs in
the same cabinet
 the
th same RF hardware
h d
(filters, amplifiers, other RF
components) can be used for
IS-95,, 1xRTT,, and 1xEV-DO

Lucent CDMA Digital Module
(CDM) Configurations
 At upper left is a CDM for conventional
IS-95 / 1xRTT service. It includes
• CRC CDMA Radio controller
• up to 6 CCU CDMA Channel Units
• PCU power converter module
• CBR CDMA Baseband Radio
 At lower left is a CDM for 1xEV-DO
• it must be occupy
py the leftmost slot
• all CCU packs are removed and
replaced by a single 1xEV-DO
modem (EVM) occupying 2 slots
• the CRC must be 44WW13D or
later

1xEV-DO in Lucent Mod Cell 4.0 Cabinets
 The Mod Cell 4 cabinet comes in
many variations
 Instead of per-carrier dedicated
CDMs, resources are pooled
 URCs (Universal Radio
Controllers) are used to steer data
f each
for h carrier
i tot EVMs
EVM for
f EVDO
or CMUs for IS-95/1xRTT.
• in a mixed-mode system, a
URC is required for EVDO and
a URC for IS-95/1xRTT
 The modulated signal from a 4.0
Universal Digital Shelf EVM or CMU is upconverted to the
Radio
FMS Controller
(URC) Evolution Carr1 Flow RF carrier frequency by the UCR
Modem
(4.0 EVM)
Universal
CDMA Antenna • each UCR (Universal CDMA
CDMA
Modem
M d
Carr
2 3
2,
Radio
(UCR) Radio)) can handle upp to three
ECP
Universal
Radio
Controller
Unit
(CMU) carriers
(URC)

Lucent 1xEV-DO Flexent Mobility Server (FMS)
 The Flexent Mobility Server is the

heart of the Radio Access Network
 It provides four processors running
the 1xEV-DO Application Processor
(DO-AP), which provides the Packet
Controller Function (PCF)
 The PCF provides air link and radio
resource management to implement
1 EV DO user sessions,
1xEV-DO i including
i l di
the dormant state and other DO-
specific features

Motorola 1xEV-DO Architecture

Motorola 1xEV-DO System Architecture
AAA
MSC OMC-IP OMC-DO
AN-AAA
MM/SDU BSC-DO PDSNs
VPU
AN-DO HAs
Packet Core
OMC-R 1x-AN
Network
Elements 1x-BTS MCC-DO
Existing IS-95 Connections
New 1xEV-DO IS-95/1x
1xEV-DO
Shared IS-95/DO Shared 1x/DO
 New 1xEV-DO carrier appears as a standard carrier addition to

existing
i ti network
t k elements
l t
• new MCC-DO cards and OMC-R database revisions needed
• AAA and PDSN need software upgrades

New Motorola 1xEV-DO Network Elements
AAA
MSC OMC-IP OMC-DO
AN-AAA
MM/SDU BSC-DO PDSNs
VPU
AN-DO HAs
Packet Core
OMC-R 1x-AN
Network
Elements 1x-BTS MCC-DO
Existing IS-95 Connections
New 1xEV-DO IS-95/1x
1xEV-DO
Shared IS-95/DO Shared 1x/DO
 MCC-DO (Multi-Channel Controller - Data Only)
 AN-DO (Access Node - Data only)
• CR ((Consolidation Router)) Similar in function to the 1x-AN MGX
• LSW (Layer 3 Switch) Similar in function to the 1x-AN CATs
 BSC-DO (Base Station Controller-Data Only)
• Mobility functions like 1x MM - Packet Control & Selection – like SDU
 OMC-DO (Operations & Maintenance Center - Data Only)
 LMT (Local Maintenance Terminal)
Motorola 1xEV-DO Block Diagram
and Network Upgrade Summary
BTS
1x BBX
RF Front End
1x Modems
DO BBX BSC-DO
MCC-DO
MCC DO
AN-DO
IS-2000
S 000 1xEV-DOO BTS CR LSW PDSN
Tool LMF LMT
BTS frame & CCP shelf 1x BBX
LPA
RF Front End
BBX-1X 1x Modems
BTS
MCC-1X
MCC-DO DO BBX
T1 or E1
GLI (Traffic)
GLI (Control)
MCC-
AN (MGX8800) CR DO OMC-DO AN-AAA
AN
AN (Catalyst 6509) LSW
BSC CBSC BSC-DO
OMC-R
O&M OMC-DO
UUNOO
IP Network PDSN (Note 1)
Telephone Network MSC/HLR Not Required 
Data Network Not Required AAA

BTS
Motorola MCC-DO Functions
1x BBX
RF Front End
1x Modems
DO BBX BSC-DO  1xEV-DO Modem

MCC-DO
MCC DO • 1 carrier,, 3 sectors per
p
AN-DO MCC-DO card
• Supports 59 channels per
sector
BTS CR LSW PDSN
 Span Interface
1x BBX
• Up to 3 Active Span lines
RF Front End
1x Modems per MCC-DO

DO BBX
T1 or E1 • Most operators will
MCC-DO generally deploy with 2
AN-AAA
OMC-DO spans per BTS
 BTS provides control:
• SCAP messaging
• Redundant BBX Selection
• Enhanced BBX interface
MCC- DO

Motorola 1xEV-DO AN-DO Elements
BTS
1x BBX
RF Front End
1x Modems
DO BBX BSC-  Consolidation Router (CR)
MCC-DO
DO
AN DO
AN-DO • Performs span aggregation
for DO access points –
BTS CR LSW PDSN Similar to 1x MGX
1x BBX
• 1 – 2 CR frames per BSC-DO
BSC DO
nd
RF Front En
1x Modems
d
 Layer 3 Switch (LSW)

DO BBX T1 or E1
MCC-DO
OMC-DO AN-AAA
• Performs IP transport across
DO Core Network – Similar to
1x CAT
CR LSW • Two CAT4006 Cages per
frame
• 1 LSW frame will serve all
1xEV-DO frames in a typical
MTSO

BTS
Motorola BSC-DO Functions
1x BBX
 BSC Functionality:
RF Front End
1x Modems
DO BBX BSC-DO • RF-scheduling, channel,

MCC-DO
connection, mobility management,
AN-DO security
 Access Network Control
• Radio Resource Management
BTS CR LSW PDSN
• Connection Control
1x BBX
• Access control / Collision control
End
RF Front E
1 M
1x Modems
d
DO BBX
T1 or E1 • Handoff control
MCC-DO
AN-AAA
 Packet Control and Session Control
OMC-DO
• Transmission of packet data
between MCC
MCC-DODO and PDSN
• Packet Data Control
• PDSN selection
• Provides Authentication
information to AAA
• Management of Data Session
• Support up to 80 MCC-DO cards
per a BSC-DO
 1 OMC-DO per each BSC-DO

Motorola 1xEV-DO Network Elements: OMC-DO
BTS
1x BBX
RF Front End
1x Modems
BSC-DO
 OMC-DO provides GUI based
DO BBX
MCC-DO
AN-DO
N O O&M functions
• Status Management
BTS CR LSW PDSN
1x BBX
• Fault Management
End
1x Modems
• Configuration Management
RF Front E
DO BBX
T1 or E1
MCC-DO
OMC-DO AN-AAA
• Software Management
• System Parameter
M
Management t
DO network element manager • Performance Monitoring
• Manages BSC-DO and MCC-
DO • CDL collection
• Ethernet interface to BSC- • Diagnostic & System Test
DO
• Supports network
• Logging
management
g applications • Health Check
(fault, alarm, performance,
configuration)

Nortel 1xEV-DO Architecture

A Typical Nortel CDMA2000 System
Providing 1xRTT Voice, Data, and 1xEV-DO

Providing Only 1xRTT Voice, Data

Providing 1xEV-DO Only

Nortel Multiple Backhaul and Configuration
Possibilities

Nortel Univity® Indoor Metrocell
 Univity® Metro Cell can

support:
• up to six CDMA 1.25 MHz
carrier frequencies
• up to three sectors
sectors.
 High Power Amplifiers and
Low Noise Amplifiers are
housed in an external unit
• the Multi-Carrier Flexible
Radio Module (MFRM)
• MFRM may y be mast
mounted to improve AP RF
link budget
Univity® CDMA Metro Cell Indoor

Base Transceiver System (AP)
Nortel DOM: Data-Only Module
 The Data Only Module (DOM) adds 1xEV-DO

capability to a MetroCell AP CEM shelf
• transmits/receives baseband data to/from
the digital control group (DCG) in the CORE
module
• CORE switches baseband to proper carrier
on the MFRM for transmission
• the DOM p performs all encoding/decoding
g g of
IP packets for transport on data-only
network to the Data-Only Radio Network
Controller (DO-RNC)
• One
O DOM supports t up to
t a three-sector,
th t
one-carrier MetroCell AP
• Additional DOMs support additional carriers

Nortel’s DO-RNC
The Data-Only Radio Network Controller
 DO-RNC is the heart of a 1xEV-DO network,

located at the central office (CO) with the BSC
and/or BSS Manager (BSSM)
 DO-RNC is a stand-alone node supporting
1xEV-DO. It manages:
• DOMs at multiplep APs ((even on different
band classes) over IP-based backhaul
network
• access terminal state, both idle and
connected
• handoffs of ATs between cells and carrier
frequencies (reverse); sector selection (fwd).
• connections from airlink to PDSN over Nortel DO-RNC
standard A10-A11
A10 A11 interfaces Data-Only
ata O y
• connects to MetroCell AP via dedicated IP Radio Network Controller
backhaul network
 DO-RNC is the peer of the access terminal for
most over-the-air
over the air signaling protocols
protocols, including
session and connection layers

Nortel DO-RNC Functionality
 DO-RNC functions similar to CDMA-2000 BSC and packet control unit:

• handoff pprocessingg (reverse
( only),
y), sector selection (forward
( only)
y)
• selection of reverse link traffic frames
• data session connected/dormant transition management
• termination of the A10/A11 RP interface to the PDSN
• application, stream, session and connection layer management
• radio link protocol (RLP)
• connection control of access terminals
• resource management, t mobility
bilit managementt
• packet control function (PCF)
• data flow control
 DO-RNC switch-like functions
• service negotiation
• paging and access channel message termination
• forwards MAC-layery p packets to the best-serving g DOM
• data-environment-specific performance logging

The Nortel DO-EMS
(Data-Only Element Management System)
 The DO-EMS consists of
• Hardware (the server) and Software (the client)
 The DO-EMS
DO EMS Provides Operation, Administration,
Maintenance, and Provisioning (OAM&P) for the
1xEV-DO radio access network (RAN)
 The existing BSS Manager (BSSM) continues
management
g of the 1xEV-DO DOM module in a
MetroCell AP
 The DO-EMS is a stand-alone platform providing
OAM&P functionality within the CDMA2000 1xEV-DO
network only. y Its functions include:
• collecting, reporting, and managing DO-RNC and
DOM alarms
• collecting and storing OMs from DO-RNC and
DOM
• administering 1xEV-DO carrier/sector neighbor
lists, including limited diagnostic capabilities
(reciprocal neighbor analysis, etc)
 The DO
DO-EMS,
EMS DO DO-RNC
RNC and DOM provide overload
controls for management of OAM&P messaging traffic
during system events
The Nortel DO-EMS Server and Client
 The DO-EMS server is a Sun Netra20
• normally located in the central office with the
BSC/DO-RNC
 Software modules on the server perform:
• auto-discovery
• configuration management
• security management
• fault management
• performance management
 DO-EMS Client / Management Terminal
• since the Netra20 is a “headless” server, a
terminal is required for monitor, keyboard
and mouse functionality
• The e te
terminal
a co
connects
ects to tthe
e DO-EMS
O S to
perform all required OAM&P functions for
the 1xEV-DO network
• The management terminal is a Sun
Blade150
• alternatively, customers may use a PC
running an “X-Windows” application
The Nortel DO-EMS Client
 The DO-EMS client is web-

based
• runs in
i standard
t d d web b
browsers
• offers network
administrators a familiar,
familiar
easy-to-use interface
• provides robust
configuration fault and
configuration,
performance management
tools

Nortel’s Univity® CDMA PDSN
 PDSN
• The Univityy® CDMA PDSN p provides CDMA radio network p packet data
access to the Public Data Network (PDN) and is integrated on the
Shasta BSN 5000 chassis. With the addition of the AT IP access
model, a Foreign Agent (FA) and Home Agent (HA) are required. The
FA is always integrated onto the Shasta BSN with the Univity® PDSN
resulting in the PDSN/FA.
PDSN/FA
 Component Breakdown
 The Shasta BSN is comprised of several components including the
Subscriber Service Gateway (SSG), the IP Services Operating System
(iSOS) and d the
h Service
S i Creation
C i System
S (SCS) as defined
d fi d below:
b l
• SSG - is the hardware platform (Shasta 5000 chassis)
• iSOS - offers high-touch services scalability and extensibility
• SCS - is a graphical management and provisioning tool allowing the
service provider to quickly and efficiently provision thousands of
subscriber profiles through its GUI. It provides scalable centralized
management for PDSNs covering a large range of geographical
locations.

Nortel Shasta BSN Hardware Description
 Hardware Description
 The Shasta BSN chassis consists of a card cage with 14 slots for cards, a
fan tray for cooling; power entry and distribution and the backplane. The
chassis mounts in a standard 19” 19 rack and requires a -48VDC
48VDC power
source. The fan tray and all cards are all hot-swappable.
 All Shasta BSN components are new in the CDMA network and are
required specifically for the CDMA 3G architecture. The required
components are as follows:
• Line Card (LC)
• Subscriber Service Module (SSM II)
• Subscriber Service Card (SSC)
( )
• Control and Management Card (CMC)
• Switch Fabric Card (SFC)
• Shasta Chassis (BSN)
• Service Creation System (SCS)
– Server and Client
• Shasta BSN Software
• Cabinet
C bi t

Nortel’s Passport 8600 Routing Switch
 Passport 8600 Routing Switch
• delivers high-density Layer 2 and Layer 3 wire-
speed switching and routing over copper and
fiber media
media.
• switching architecture capable of delivering 128
Gbps of capacity, scaling to 256 Gbps in the
future.
 Suppo
Supported
ted interfaces
te aces include
c ude 10/100/1000BaseT
0/ 00/ 000 ase
autosensing and ATM
• Supports up to 384 10/100 TX Ports
• Supports up to 192 100 FX Ports
• Supports up to 64 1000 SX Ports
• STM1/OC3 (up to 32 Ports)
 Redundant power supplies and hot-swappable
modules are also part of the product platform.
• Both 6 and 10 Slot Chassis are available
available. The
price in Appendix A, B is applicable to 6 slot
Chassis.
 Core switching and processing
• Routing g switch fabric/CPU module—High- g
performance Layer 2 and Layer 3 traffic
switching. One per chassis; two if redundancy is
desired
Nortel Passport 8600 Connectivity
 Ethernet/Gigabit Ethernet
• 48-port auto-sensing 10Base-T/100Base-TX Ethernet Routing Switch module (RJ-45)
• Passport Routing Switch Module 8632TX
– 32-port mixed-media module for 10Base-T/100Base-TX switching and routing
– two slots for Gigabit Interface Converters (GBICs), high port density
• 24-port 100Base-FX Fast Ethernet Routing Switch module (MT-RJ) long runs – 2km
multimode
• 16-port 1000Base-SX Gigabit Ethernet Routing Switch module (MT-RJ)
– Up to 128 Gigabit Ethernet ports per 10-slot chassis
• 8-port 1000Base-T Gigabit Ethernet Routing Switch module (RJ-45) – over cat. 5 copper
to 100m
• 8-port 1000Base-SX Gigabit Ethernet Routing Switch module (SC) -for multimode fiber
• 8-port Gigabit Ethernet Routing Switch module
– plug-in GBICs with SC connectors can mix and match interface types on a single
module using multi-mode or single-mode fiber. GBICs available in short distance
(SX), long distance (LX) and extended distance (XD and ZX)
• One
One- and two-port
two port auto sensing 10
10-Gigabit
Gigabit Ethernet Routing Switch modules, full
full-
featured LAN/WAN connectivity with full functionality and intelligence of the Passport
8600
 ATM/SONET/SDH
• 2-slot MDA Baseboard—Supports up to eight OC-3/STM1 for ATM interface
applications such as permanent virtual circuit VLAN bridging and routing, maintaining
QoS prioritization.

Nortel CDMA Univity®
Base Station Controller EBSC
PP15K Breaker Interface
Panel  The Univity® CDMA Base Station Controller
PP15K Fiber Tray
CBRS is a scalable and cost reduced IP
enabled Base Station Controller
 Eliminates the need for separate BIU and
GPSTM GPSTM CIS cabinets in the BSC for 1xEV-DO non-
Cable Trough MTX systems
Cable Consolidation and Multiplexing
Chassis
 Key
K F Features:
t
• Scalable from very low to very high
capacity through module additions
Cable Trough • Multiple frames deployed for
configuration flexibility
0 1 2 3 4 5 6 7
24pBCNW Functional Processor (NTPB11AA)
Cable Trough
11pMSW Functional Processor (NTPB10AA)
CP3 - Control Processor (NTHR06CA)
Optional - 2nd Enhanced BSC Frame Connectivity

8 1 1 1 1 1 1
9
0 1 2 3 4 5
Cable Trough
Cable Consolidation and Multiplexing Chassis (NTPB13AA)
GPSTM - Global Positioning Satellite Timing Module (NTPB15AA)

Nortel CDMA Univity®
Base Station Controller EBSC
 The Univity® CDMA BSC CBRS is built on the Passport 15K and includes
two new Functional Processors (FPs), the 11pMSW FP and the
24pBCNW FP , along with a Cable Consolidation and Multiplexing
Chassis
• The 11pMSW FP contains 3 OC-3/STM-1 ports. One (1) OC-3/STM-1
port is channelized and contains T1/E1/T3/E3 channels to carry AP or
ISSHO traffic. The unchannelized p ports can be configured
g as OC-3c
to support interfaces to the DISCO or BSS Manager. In these
instances they can be configured as OC-3c in North America or STM-
1 for international installations. The 11pMSW FP provides 8 T1s for
connectivity to the LPP.
• The 24pBCNW FP contains 24 LVDS ports for connectivity to the SBS
shelves.
 The Cable Consolidation and Multiplexing Chassis manages connectivity
between the new 24pBCNW FP to current SBS shelves
• GPSTM to the 24WpBCNW FP
• T1s/E1s on the 11pMSW FP to the LPP
• The Univity® CDMA BSC CBRS can be added to current BSCs
allowing for expanding port and Erlang capacity

Pre-EBSC Hardware Required
for Nortel 1xEV-DO Non-MTX Systems

Nortel’s BSS Manager (BSSM)
within the Univity® EBSC
 The BSS Manager consists of quad Ultra Enterprise 450 Servers

• UltraSPARC IV p processor cards
• High Speed Serial Interface card interconnects to the BSC
• 31 Gigabytes of mirrored disk space
• Ethernet and LAN access.
 The BSS Manager is a highly reliable platform, provisioned with an Active
and a Standby unit.
• Constant heartbeat and monitoring are performed between the Active
and Standbyy systems.
y
• System initiated (automatic) SWACT (Switch of activity) occurs from
Active to Standby when the active unit experiences critical
hardware/software fault.
• User or operator SWACT is also supported
supported.
• Redundant Ethernet links are provisioned between the two BSS
Manager servers
• redundant links are also provisioned from BSS Manager to CIS (a
communication component within the Univity® BSC)

Nortel BSSM:
CDMA Base Station Subsystem Manager
 The CDMA BSS Manager provides the Operations, Administration, and Maintenance (OA&M)
interface for the Univity® BSC and Univity® AP. Within the context of TMN’s
((Telecommunication Management
g Network)) functional layer
y approach,
pp , the BSS Manager
g is the
Element Manager and is the operator’s primary interface into Nortel Networks' CDMA RF
network. The BSS Manager platform comprises the operating environment, hardware, and
application interfaces, supporting four areas of the FCAPS model (Fault, Configuration,
Accounting, Performance, and Security).
 Fault management primarily deals with the alarms of the CDMA network. Alarms are generated
b the subsystem
by s bs stem when
hen there is a failure
fail re of the hardware/service
hard are/ser ice or when
hen there is a degradation
of the hardware/service due to certain external environmental factors. The BSS Manager’s
primary responsibility is to log, report, and manage the alarm events from its managed
subsystems.  Configuration management controls the way in which the system provides
service. It allows specification of configuration information, collects data from and provides data
to the various network elements and the connections between those elements. Configuration g
management is primarily responsible for supporting network planning, installing,
interconnecting, and establishing NE equipment, connections, and services.
 Performance management ensures that performance data is sent at regular intervals to the
BSS Manager. Within the BSS Manager, two types of data are logged:
 Performance data, also referred to as Operational
p Measurements ((OM)) – statistical information
about subsystem components
 Diagnostic Data - debugging information on messages among subsystems for troubleshooting
 Security management deals with security breaches (improper use) of network resources.
Security management consists of software applications used to configure, control, create or
delete the resources p
providingg the services. Security y Management
g also includes administration
of security procedures and functions.

EV-DO-Specific Nortel Documentation
1xEV-DO Release 2.0
Document Document
Relevance Number Revision Title
1 411-2133-012 1.11 CDMA2000 1xEV-DO System Overview Guide
CDMA2000 1xEV-DO NBSS Delta MOs, Logs, OMs and
1 411 2133 109
411-2133-109 1 09
1.09 Alarms Reference Manual
CDMA2000 1xEV-DO Element Management Subsystem
1 411-2133-126 1.1 (EMS) Recovery and Upgrade Guide
1 411-2133-529 1.14 (DO-EMS) Administrator's Guide
1 411-2133-532 1.08 1xEV-DO D O-RNC Administration Guide
CDMA2000 11xEV-DO
EV DO Configuration
C fi ti Parameters
P t Reference
R f
1 411-2133-822 1.02 Guide
1 411-2133-917 1.1 1xEV-DO Data Only Module (DOM) User Guide
CDMA2000 1xEV-DO OMs and Performance Measurement
1 411-2133-924 1.1 Reference Guide
CDMA2000 1xEV-DO Command Line Interface (CLI)
1 411-2133-925 1.13 R f
Reference G
Guide
id
1 411-2133-926 1.08 CDMA2000 1xEV-DO Logging Message Reference Guide
1 411-2133-927 1.12 (DO-EMS) User Guide
1 411-2133-929 1.08 1xEV-DO Script Tool User Guide
1 411-2133-932 1.1 1xEV-DO Deployment Guide
CDMA Metro
M t Cell
C ll Deployment
D l t Guidelines
G id li R
Reference
f
Manual
1.00 411-2133-111 04.06
Shasta PDSN/FA and HA Customer Information Guide

1.00 411-2133-802 05.06
BSC Theory of Operations Handbook

1.00 411-2133-101 12.06

1xEV-DO / 1xRTT
Interoperability

1xEV-DO/1xRTT Interoperability
 The CDMA2000 1xEV-DO Standard IS-856 makes no provision for

any kind of handoff to or from any other technology
 Driven by Operator interest, a “Hybrid” mode has been developed
to provide some types of handoff functions to the best extent
possible
 Hybrid Mode
• is a mobile only function – neither the EV nor 1xRTT network
knows anything
y g about it
• is a proprietary feature with vendor-specific implementation
• has no standard-defined RF “triggers”; no “hooks”
 In the 1xEV rev
rev. A standard
standard, some new features will be provided
• the 1xEV control channel will be able to carry 1xRTT pages too
• this and other changes may make the “hybrid” mode
unnecessary and obsolete

What Handoffs are Possible in Hybrid Mode?
 All switching between systems occurs in Idle Mode

• there are no “handoffs”
handoffs in active traffic state in either mode
 Sessions can be transferred from one system to the other, but
NOT in active traffic state
• If there is a connection
connection, it can be closed and then re re-originated
originated
on the other system
• In some cases this can be accomplished automatically without
the end-user’s
end-user s awareness – in other cases,
cases this is not possible

Hybrid Mode Transition Scenarios
1:2 Deployment 1:1 Deployment 1:1 Deployment

EV-DO, F2
1xRTT, F1
 DO systems
y will be Implemented
p in Several Configurations
g
• 1:1 overlays in busy core areas
• 1:1 or 1:N overlays in less dense areas
 Many EV>1x
EV 1x and 1x>EV
1x EV transition events may occur as a user
transitions from area to area
 Initial system acquisition is also involved as a user activates their
AT in different locations
 These
Th transitions
ii are d
dependent
d on the
h HHybrid
b id mode
d
implementation in the AT
 The following pages show some possible transitions assuming
Mobile IP and AT Hybrid Mode are implemented

1xRTT / 1xEV-DO Hybrid Idle Mode
 1xRTT/1xEV-DO Hybrid Mode

• depends
p on beingg able to hear p
pages
g on both
1xEV-DOO
Active
systems – 1xRTT and 1xEV-DO

• is possible because of slotted mode paging
• 1xRTT and 1xEV-DO paging slots do not occur
simultaneously
1xEV-DO
• mobile can monitor both

Idle
Idle
Mode  During 1xEV-DO traffic operation, the hybrid-aware
mobile can still keep monitoring 1xRTT paging
Hybrid
H b id channel
Mode
 During 1xRTT traffic operation, the hybrid-aware
mobile is unable to break away; 1xRTT traffic
1xRTT
Idle
Idle
Mode operation is continuous
• no opportunity to see 1xEV-DO signal
 This hybrid Idle mode capability is the foundation
for all 1xRTT/1xEV mode transfers
RTT
Acttive
• the network does not trigger any transfers

1xR

Hybrid Dual-Mode Idle Operation
1xRTT / 1xEV-DO Paging Interoperability
LONGEST POSSIBLE
16-frame Control Channel Cycle PACKET
16 slots of 26-2/3 ms = 426-2/3 ms
DRC 16 Subpackets
1xRTT Minimum Slot Cycle Index: 16 slots of 80 ms each = 48 26-2./3 ms frames
 A dual-mode 1xRTT/1xEV-DO mobile using slotted-mode paging can

effectively watch the paging channels of both 1xRTT and 1xEV-DO at the
same time
 How is it possible for the mobile to monitor both at the same time?
• The paging timeslots of the two technologies are staggered
 Three of the 16 timeslots in 1xRTT conflict with the control channel slots
of 1xEV-DO
• However, conflicts can be avoided by page repetition, a standard
feature in systems of both technologies
Initial System Acquisition by Hybrid Mobile
when 1xEV-DO is NOT Available
1xEV-DOO
Active
Acquire
1xEV-DO
1xEV-DO
Idle
System
driven by no, can’t see EV
PRL
Acquire After entering this state, the

Register Idle mobile will not search for
1xRTT
1xRTT Mode
Idle
with 1xEV service again

System
1xRTT
driven by
Network
PRL Classical 1
1xRTT
RTT
Idle Mode Voice Idle
Page! Mode
Release
RTT
Acttive
1xRTT
Voice
1xR
Call

Initial System Acquisition by Hybrid Mobile
when 1xEV-DO is Available
Set Up or
1xEV-DOO
iinterrupted
t t d
Active
Re-establish Data
1xEV during 1xEV
1xEVDO Connection
Traffic 1xRTT Traffic
Data Closed
voice call
Session
Ti
Triggers:
Acquire
1xEV-DO
AT Data
1xEV-DO yes, found EV Ready!
Idle
System Idle Idle

driven by Mode Mode
PRL AN Data
Page!
Hybrid
H b id Hybrid
H b id Hybrid
H b id
Mode Mode Mode
Acquire Idle
Register
1xRTT
1xRTT Mode Idle Voice Idle Idle

Idle
with Mode Page! Mode Mode

System
1xRTT
driven by
Network
PRL
Release
RTT
Acttive
1xRTT
Voice
1xR
Call

In-Traffic: EV-DO Fade with 1xRTT Available
Fade
AT data ready
1xEV-DOO
PPP
Active
Traffic Mode, Close Resync Traffic Mode,

Data Transfer Connection MIP Data Transfer
Registr.
AN data ready
Fade
Get New
UATI
1xEV-DO
DO
Idle
no
Dormant System
/Idle Same
Acquired DO
Subnet?
1xRTT
Idle
Idle Dormant
Mode /Idle
RTT
Acttive
PPP
Resync
1xR
Reestablish Resume Transfer

Call MIP Data Transfer Finished
Registr.

Transition In-Traffic: Lost EV-DO and 1xRTT
Fade
Set Up or
1xEV-DOO
Active
Re-establish
Traffic Mode, Close 1xEV
1xEVDO
Data Transfer Connection Traffic
Data
Session
Fade Get New

Found UATI Ti
Triggers:
1xEV-DO
New DO AT Data
Signal!! No
Ready!
Idle
DO PRL,
Idle Same DO Idle Idle
Search for
Mode Subnet? Yes Mode Mode
DO AN Data
Hybrid Page!
Mode
Fade Idle
Mode
1xRTT
Use 1x PRL, Use 1x PRL,

Idle
Idle
Search for Search for
Mode
1xRTT 1xRTT
Lost No No 1x Signal,
Signal!! Signal Continue EV
Found!! Operation
No Signal Found!!
RTT
Acttive
1xR

Dormant Session, EV-DO Lost > 1xRTT > 1xEV-DO
Coverage Fade
Edge
1xEV-DOO
Active
PPP
Traffic Mode, Resync
Data Transfer MIP
Data Finished, Registr.
Call Dormant
Fade Found Get New

New DO UATI
Signal!!
1xEV-DO
No
Idle
DO PRL, DO PRL, DO PRL, DO PRL,

Idle Same DO Idle
Search for DO DO DO
Mode Subnet? Yes Mode
DO Available? Available? Available?
No No No
Signal Signal Signal
Found!! Found!! Found!! Hybrid
H b id
Mode
1xRTT
Idle
Idle Idle Idle

Mode Mode Mode
RTT
Acttive
PPP
Resync
1xR
MIP
Registr.

Module 342
1xEV-DO “Call Processing”

Setting up Sessions and Connections

342 Contents
 Sessions and Connections

 EV-DO Standards and Protocols, Rev. A Protocols and Link Rates
 Basics of EV-DO Operation; Terminal Identifiers
 Channels and Layer-3 Messages in Connection Processing
 System Acquisition and Synchronization
 Access Procedures
 Following a Connection
 Access Terminal Architecture and Route Updates
 Session Interoperability between EV-DO and 1xRTT: Hybrid Mode

EVDO Standard
And Standards Documents

EVDO Standards
 C.S0024-0_v2.0 Oct., 2000

• Original EV-DO standard, derived from Qualcomm’s “HDR”
 C.S0024-0_v3.0 Dec., 2001
• Improvements to stability and throughput
 C.S0024-0_v4.0 Oct., 2002
• Final Rev.
Rev 0 standard; improvements in several layers
 C.S0024-A_v1.0 Mar., 2004
• First Rev. A standard, offering higher speeds on the reverse link and
enhancements to speed applications like VOIP and multi-user/multi-
media
 C.S0024-A_v2.0 July, 2005
• More application-driven enhancements
 C.S0024-A_v3.0 Sep., 2006
• Current
C rrent Re
Rev. A Standard
Standard: More application
application-driven
dri en enhancements
 C.S0024-B_v1.0 May, 2006
• Advanced version providing up to 4.9 mb/s per carrier and the ability
to “gang” multiple carriers for speeds of at least 14 mb/s

Conceptual Framework of the IS-856 Standard
Architecture Reference Model
Air
 IS-856 defines the behavior of Interface
three main entities: Access
Sector
• Access Terminal Terminal Access Network
• Air Interface
Protocol Architecture
• Access Network IS-856
IS 856
Layer Protocol & Function Chapter
 The behavior of the system is
defined in layers Application •Default Signaling Application 2
•Default Packet Application 3
• the layers provide a Stream •Stream 0: Default Signaling
4
•Stream 1, 2, 3: not used by default
simple, logical foundation
for performing functions •Protocol Negotiation •Address Mgt.
Session •Protocol Configuration •State Mtce. 5
and applications
•Air Link Connection Establishment
• Specific applications
applications, Connection •Air Air Link Connection Maintenance 6
functions and protocols •Authentication
exist in each layer Security •Encryption 7
• Each layer is defined in Mac •Defines procedures to transmit
and receive over the physical layer 8
specific chapters of the
Physical •Channel Structure •Modulation.
standard •Frequency, Power •Encoding. 9

Stack Layers and their Default Protocols
Default Signaling Default
Flow Control
Signaling Network Packet Protocol
Application Protocol Application Application
Signaling Link Radio Link Location Update layer
Protocol Protocol Protocol
Stream Protocol Stream

layer
Session Address Session

Management Management Configuration Session
Protocol Protocol Protocol layer
Air Link Initialization Idle State Connected

Management State Protocol State
Protocol Protocol Protocol C
Connection
ti
Packet Route Update Overhead layer
Consolidation Protocol Messages
Protocol Protocol
Security Key Exchange Authentication Encryption Security

Protocol Protocol Protocol Protocol
layer
Forward Reverse
Control Channel Traffic Channel Access Channel Traffic Channel Mac
MAC Protocol MAC Protocol MAC Protocol MAC Protocol layer
Physical Layer Protocol Physical

layer

Non-Default Protocols
Multi-Flow Packet Application CDMA2000 Circuit Services
Notification Application
Flow Control Data over Signal- Application
Protocol Ing Protocol CDMA2000 Circuit Services layer
Radio Link Location Update
p Negotiation Protocol
Protocol Protocol
Generic Virtual Stream Protocol Stream

layer
Generic Multimode Session

Capability Discovery Protocol
layer
Enhanced Connection
Idle State Protocol
l
layer
Generic Security DH Key Exchange SHA-1 Authentication Security

Protocol Protocol Protocol
layer
Enhanced Forward Enhanced Subtype 1 Reverse

Subtype-1
Traffic Channel Access Channel Traffic Channel
MAC Protocol MAC Protocol MAC Protocol Mac
Enhanced Subtype-2 Reverse Subtype 3 Reverse layer
Control Channel Traffic Channel Traffic Channel
MAC Protocol MAC Protocol MAC Protocol
Subtype 1 Physical Layer Protocol Subtype 2 Physical Layer Protocol Physical

layer

1xEV-DO Protocol Layers
and Packet Encapsulation
Application Layer Application Layer Packet
Stream Layer Header Payload
Session Layer Packet Packet
Connection Layer Header Payload Header Payload Pad
Encryption Layer Header Payload Trailer
Authentication Layer Header Payload Trailer
Security Layer Header Payload Trailer Header Payload Trailer
MAC MAC MAC

MAC Layer Header Payload Trailer
Physical Layer Payload

Physical Layer

EV-DO Rev. A Improvements
 Support of enhanced reverse link

• One channel per mobile station
• Mobile
M bil station
t ti iis requiredi d tto ttransmitit att 1
1.84
84 Mb
Mbps peak
k rate
t
• Shorter frames
• Higher capacity
 Forward link enhancements
• – Higher
Hi h peak kd
data
t ratet off 3
3.11 Mb
Mbps
• – Smaller packet sizes (128, 256, and 512 bits)
• – Multi-user packets
 Improved slotted mode
• Shorter
Sh t slot l t cyclel ffor reduced
d d activation
ti ti titime
• Subsynchronous control channel for enhanced standby time
• Slots coordinated with need to listen to 1xRTT paging channel
 1xRTT paging channel content transmitted on EVDO control channel
 Enhanced
E h d multi-flow
lti fl packet
k td data
t application
li ti
 Reverse link MAC enhancements for QoS
 Data Source Control (DSC) for seamless cell selection
 Enhanced Generic Attribute Update protocol

Link Rates and Packet/Subpacket Formats
FORWARD LINK REVERSE LINK
DRC Modu- Preamble Payload Raw C/I Payload Modu-Effective Rate kbps after: Code Rate (repetition) after
Index Slots lation Chips Bits kb/s db Bits lation 4 slots 8 slots 12 slots16 slots 4 slots 8 slots 12 slots16 slots
0x0 n/a QPSK n/a 0 null rate n/a 128 B4 19.2 9.6 6.4 4.8 1/5 1/5 1/5 1/5
0x1 16 QPSK 1024 1024 38.4 -11.5 256 B4 38 19.2 12.8 9.6 1/5 1/5 1/5 1/5
0 2
0x2 8 QPSK 512 1024 76 8
76.8 -9.2
92 512 B4 76 38.438 4 25.6
25 6 19.2
19 2 1/4 1/5 1/5 1/5
0x3 4 QPSK 256 1024 153.6 -6.5 768 B4 115 57.6 38.4 28.8 3/8 1/5 1/5 1/5
0x4 2 QPSK 128 1024 307.2 -3.5 1024 B4 153 76.8 51.2 38.4 1/2 1/4 1/5 1/5
0x5 4 QPSK 128 2048 307.2 -3.5 1536 Q4 230 115 76.8 57.6 3/8 1/5 1/5 1/5
0x6 1 QPSK 64 1024 614.4 -0.6 2048 Q4 307 153 102.4 76.8 1/2 1/4 1/5 1/5
0x7 2 QPSK 64 2048 614.4 -0.5 3072 Q2 461 230 153.6 115.2 3/8 1/5 1/5 1/5
0x8 2 QPSK 64 3072 921.6 +2.2
2.2 4096 Q2 614 307 204.8 153.6 1/2 1/4 1/5 1/5
0x9 1 QPSK 64 2048 1,228.8 +3.9 6144 Q4Q2 921 461 307 230.4 1/2 1/4 1/5 1/5
0xa 2 16QAM 64 4096 1,228.8 +4.0 8192 Q4Q2 1228 614 409 307.2 2/3 1/3 2/9 1/5
0xb 1 8PSK 64 3072 1,843.2 +8.0 12288 E4E2 1843 921 614 460.8 2/3 1/3 1/3 1/3
0xc 1 16QAM 64 4096 2,457.6 +10.3
0xd 2 16QAM 64 5120 1,536.0 +8.3
0xe 1 16QAM 64 5120 3,072.0 +11.3
 The 1xEV-DO Rev. A reverse link has seven available modes

offering
ff i higher
hi h speedsd than
th available
il bl iin R
Rev. 0
• Modulation formats are hybrids defined in the standard
 The 1xEV-DO Rev. A forward has two available modes offering
hi h speeds
higher d th
than available
il bl iin R
Rev. 00.

Basics of EV-DO Operation

EV-DO Terminal Identifiers
 In CDMA, mobiles are identified by the familiar IMSI and ESN.

These are permanent quantities stored in the mobile.
 EV-DO terminals have hardware addresses which can be queried
by the system, but connections are coordinated by the use of
Access Terminal Identifiers (ATIs)
 There are four types of ATIs:
• ’00’ BATI Broadcast Access Terminal Identifier
• ’01’ MATI Multicast Access Terminal Identifier
• ’02’ UATI Unicast
U i t Access
A Terminal
T i l Identifier
Id tifi
– Requested by the mobile at session setup and assigned by
the system. Updated when crossing various boundaries
• ’03’
03 RATI Random Access Terminal Identifier
– Used by the mobile during initial access
 From the view of the SLP protocol, ATIs simply define connection
endpoints.

Channels and Layer-3 Messages
in 1xEV-DO Call Processing

Dissecting a Layer-3 Message
EXAMPLE:
EXAMPLE
 1xEV-DO messages on both TRAFFIC CHANNEL
forward and reverse traffic channels ASSIGNMENT
are normally sent via dim-and-burst MESSAGE
Length
 Messages
M iinclude
l d many fifields
ld off Field (in bits)
binary data
MESSAGE ID 8
 The first byte of each message MESSAGE SEQUENCE 8
identifies message type: this allows CHANNEL INCLUDED 1
th recipient
the i i t to
t parse the
th contents
t t CHANNEL 0 or 24
 To ensure no messages are FRAME OFFSET 4
missed, all 1xEV-DO messages DRC LENGTH 2
bear serial numbers and important DRC CHANNEL GAIN 6
messages contain a bit requesting ACK CHANNEL GAIN 6
acknowledgment NUM PILOTS 4
 Messages not promptly NUMPILOTS occurrences of this block:
acknowledged are retransmitted
several times
times. If not acknowledged
acknowledged,
PILOT PN
SOFTER HANDOFF
9
1
t
the sender may release the call MAC INDEX 6
 Field data processing tools capture DRC COVER 3
and display the messages for study RAB LENGTH 2
RAB OFFSET 3

Message Vocabulary: Acquisition & Idle States
Pilot Channel Pilot Channel
Access Access Access
No Messages Network Point No Messages
Terminal
(AN) (AP) (AN)
C t l Channel
Control Ch l A
Access Ch
Channell
ACAck Sync Connection Request
Access Parameters SectorParameters Data Ready ACK
Broadcast Page Hardware ID Response
Reverse Rate Limit
Q i k Config
Quick C fi K
Keep Alive
Ali R Requestt
Connection Deny
Xoff Response Keep Alive Response
Data Ready
Xon Response Location Complete
Hardware ID Request
Traffic Channel Location Notification
Keep Alive Request Assignment
Route Update
Keep Alive Response UATI Assignment
Session Close
Location Request
UATI Request
Location Assignment
UATI Complete
Redirect
Xoff Request
Session Close
Xon Request

Message Vocabulary: Connected State
Forward Traffic Channel Access Reverse Traffic Channel
Point Access
ANKey Complete Session Close (AP) Terminal ATKey Complete Session Close
Attribute Override Traffic Channel (AN) Attribute Override Traffic Channel
Assignment Response Complete
Configuration Complete
UATI Assignment Configuration Complete UATI Complete
Configuration Request
Unicast Configuration Request Xoff Request
Configuration Response Reverse Rate Limit
Configuration Response Xon Request
Configuration Start
Xoff Response
C
Connection
ti Close
Cl
Connection Close
Xon Response
Data Ready ACK
Data Ready
Fixed Mode Enable
Hardware ID Request
Fixed Mode X Off
Keep Alive Request
Hardware ID Response
Keep Alive Response
Keep Alive Request
Key Request
Keep Alive Response
Location Assignment
Key Response
Location Request
Location Complete
Nak
Location Notification
Neighbor List
Nak
Redirect
Redirect
Reset
Reset
Reset ACK
Reset ACK
Reset Report
Route Update
RTC ACK

Rev. A
Layer-33
Messages
Part 1

Rev. A
Layer-33
Messages
Part 2

Message Sent on Channels
ACAck
Name
Access Parameters
ID Inst. CC Syn SS AC FTC
0x00
0x01
1 CC
1 CC
RTC SLP
Best Effort
Best Effort
Addressing
Unicast
Broadcast
Pri.
10
30
All the Messages
ANKey Complete
ATKey Complete
Attribute Override
0x02
0x03
0x05
1
1
1
FTC
FTC
RTC
Reliable
Reliable
Best Effort
Unicast
Unicast
Unicast
40
40
40
of 1xEV-DO
Attribute Override Response 0x06 1 RTC Best Effort Unicast 40
Broadcast Reverse Rate Limit 0x01 1 CC Best Effort Broadcast 40
Configuration Complete
Configuration Request
0x00
0x50 24
1 FTC
FTC
RTC
RTC
Reliable
Reliable
Unicast
Unicast
40
40  In 1xEV-DO, most call
Configuration Response 0x51 24 FTC RTC Reliable Unicast 40
Configuration Start
ConnectionClose
0x01
0x00
1
1
FTC
FTC RTC
Best Effort
Best Effort
Unicast
Unicast
40
40
processing events are
ConnectionDeny
ConnectionRequest
0x02
0x01
1 CC
1 AC
Best Effort
Best Effort
Unicast
Unicast
40
40
driven by messages
DataReady 0x0b 1 CC FTC Best Effort Unicast 40
DataReadyACK
Fixed Mode Enable
0x0c
0x00
1
1
AC RTC
RTC
Best Effort
Best Effort
Unicast
Unicast
40
40
 The MAC channels in
Fixed Mode X off
Hardware ID Request
0x01
0x03
1
2 CC FTC
RTC Best Effort
Best Effort
Unicast
Unicast
40
40
both directions are used
Hardware ID Response
K
Keep Alive
Ali R Requestt
0x04
0 02
0x02
1
1 CC
AC
AC FTC
RTC
RTC
Rel, Best Eff
B t Effort
Best Eff t
Unicast
U i
Unicastt
40
40 to carry messages or
Keep Alive Response
Key Request
0x03
0x00
1 CC
1
AC FTC
FTC
RTC Best Effort
Reliable
Unicast
Unicast
40
40 specific Walsh Masks to
Key Response 0x01 1 RTC Reliable Unicast 40
Location Assignment
Location Complete
0x05
0x06
1 CC
1 AC
FTC
RTC
Best Effort
Rel, Best Eff
Unicast
Unicast
40
40
convey commands and
Location Request
Location Notification
0x03
0x04
1 CC
1 AC
FTC
RTC
Best Effort
Rel, Best Eff
Unicast
Unicast
40
40
selection options
 Messages have priority
Nak 0x00 1 FTC RTC Best Effort Unicast 50
Neighbor List 0x00 1 FTC Reliable Unicast 40
Page 0x00 1 SS Best Effort Unicast 20
Quick Config
Redirect
0x00
0x00
1
1 CC
SS
FTC RTC
Best Effort
Best Effort
Broadcast
Bcst, Unicst
10
40
and delivery protocols
Reset 0x00 2 FTC RTC Best Effort Unicast 40
Reset ACK
Reset Report
0x01
0x03
2
1
FTC
FTC
RTC Best Effort
Reliable
Unicast
Unicast
40
40
 Each message has a
Route Update
RTCAck
0x00
0x00
1
1
AC
FTC
RTC Rel, Best Eff
Reliable
Unicast
Unicast
20
10
channel
h l or channels
h l on
SectorParameters
Session Close
0x01
0x01
1 CC SYN SS
1 CC AC FTC RTC
Best Effort
Best Effort
Broadcast
Unicast
30
40 which it may be sent
Sync '00' 1 CC SYN SS Best Effort Broadcast 30
Traffic Channel Assignment
Traffic Channel Complete
0x01
0x02
1 CC
1
FTC
RTC
Rel, Best Eff
Reliable
Unicast
Unicast
20
40  The structure of all the
g
UATI Assignment
UATI Complete
0x01
0x02
1 CC
1 AC
FTC
RTC
Best Effort
Rel, Best Eff
Unicast
Unicast
10
10 1xEV DO messages is
1xEV-DO
UATI Request 0x00 1 AC Best Effort Unicast 10
Unicast Reverse Rate Limit
Xoff Request
0x02
0x09
1
1 AC
FTC
RTC
Reliable
Best Effort
Unicast
Unicast
40
40
defined in IS-856
Xoff Response 0x0a 1 CC FTC Best Effort Unicast 40
Xon Request 0x07 1 AC RTC Best Effort Unicast 40
10-2008
Xon Response 0x08 1 CC (c)2008 Scott Baxter and Associates
FTC Best Effort Unicast 40 186
1xEV-DO Protocol Layers
and Packet Encapsulation
Application Layer Application Layer Packet
Stream Layer Header Payload
Session Layer Packet Packet
Connection Layer Header Payload Header Payload Pad
Encryption Layer Header Payload Trailer
Authentication Layer Header Payload Trailer
Security Layer Header Payload Trailer Header Payload Trailer
MAC MAC MAC

MAC Layer Header Payload Trailer
Physical Layer Payload

Physical Layer

EV DO Rev.
EV-DO Rev A
Protocols and
Subtypes

System Acquisition
and Synchronization

Sync Message
1/32 chip counter 1/32 Chip Counter 4
1.25 msec counter 1.25 msec Counter 0xAD 2A BD D6 98 00 01/06/2006 01:46:28
Frequency Band Band 1
CDMA Channel Nbr ChanNum 25
Pilot PN Offset PilotPN 216
Half-slot Reference Counter HSTR 0
IS-890 Signaling Is_hdris890 0 NOT IS-890
Seq Nbr Valid SeqValid 0 SeqNo is not valid
AckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not valid
Packet Fragmented Frgmented 0 Packet NOT fragmented
Signaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliable
Seq Nbr of Message SeqNo 255
Seq Nbr of Ack AckSeqNo 255
Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel Capsule
In Configuration Bit InConfiguration 0
Type Type 11 CONNECTION: Initialization State Protocol
Message ID MessageID 0 Sync
Maximum Revision MaximumRevision 1
Minimum Revision MinimumRevision 1
Pilot Pn Pilot Pn 216
SystemTime SystemTime 0x07 39 50 86 F0
 The Sync message gives the mobile system time and the Pilot PN,
along with basic signaling link details.
 After reading this message, the mobile can receive the control
channel messages

Access Parameters Message
1/32 chip
hi countert 1/32 Chi
Chip C
Counter
t 16384
1.25 msec counter 1.25 msec Counter 0x03 2C BD D6 98 00 01/06/2006 01:46:28
S Nb
Seq Nbr Valid
V lid S V lid
SeqValid 0 S N is
SeqNo i nott valid
lid
Type Type 2 MAC: Access Channel MAC Protocol
Message ID MessageID 1 Access Parameters
Access Cycle Duration AccessCycleDuration 64
Access Signature AccessSignature 0
Open Loop Adjust OpenLoopAdjust 79
Probe Initial Adjust ProdeInitialAdjust 0
Probe Num Step ProdeNumStep 5
Power Step PowerStep 8
Preamble Length PreambleLength 2
Capsule Length Max CapsuleLengthMax 2
APersistence APersistence 0
Reserved Reserved 0
 The Access Parameters message tells the mobile everything it

needs to know to transmit probes correctly on the access channel

Quick Config Message
IS-890
S S
Signaling Is_hdris890 0 NOT
O IS-890
S
S
Synchronous
h Control
C t l ChChannell S
SyncCCFlag
CCFl 1 S
Synchronous
h Control
C t l Channel
Ch l Capsule
C l
Type Type 15 CONNECTION: Overhead Messages Protocol
Message ID MessageID 0 Quick Config
Color Code ColorCode 30
SectorID 24 LSBits SectorID24 53506
Sector Signature SectorSignature 0
A
Access Si
Signature
t A
AccessSignature
Si t 0
Redirecting Terminals away from
this Network Redirect 0 Invalid
Max Nbr of RPC Channels
Supported by Sector RPCCount 0
 The Quick Config message tells the mobile the sector identify
(color code, sector ID, Sector Signature, and Access Signature)
 The redirection flag can be used to send mobiles to a different
carrier frequency or network
network, much like the GSRM in CDMA2000

Sector
IS-890 Signaling
Seqq Nbr Valid
AckSeqNo valid Ack
Is_hdris890
SeqValid
q
AckSeqValid
0
0
0
NOT IS-890
SeqNo
q is not valid
AckSeqNo is not valid
Parameters
Packet Fragmented
Signaling Link Protocol
Seq Nbr of Message
Frgmented
Reliable
SeqNo
0
0
255
Packet NOT fragmented
Signaling Link Protocol delivery mechanism NOT reliable Message
Synchronous Control Channel
In Configuration Bit
SyncCCFlag
InConfiguration
1
0
Synchronous Control Channel Capsule
 Gives full
Type
ype Type
ype 15
5 CO
CONNECTION:
C O O Overhead
e ead Messages
essages Protocol
otoco
Message ID MessageID 1 Sector Parameters details of the
Country Code Country Code 1
0x00 84 0A C0 00 00 00
00 00 0A 04 0C A8 00
sector
Sector Address Identifier
Subnet Mask
SectorID
SubnetMask
D1 02
104
configuration:
Sector Signature SectorSignature 0
Latitude
Longitude
Latitude
Longitude
0
0
00D00 00.00N
00D00'00 00N
000D00'00.00E
 ID,
ID subnet
Route Update Radius
Leap Seconds
RouteUpdateRadius
LeapSeconds
0
13
mask,
Local Time Offset
Reverse Link Silence Duration
LocalTimeOffset
ReverseLinkSilenceDuration
1568
0
26 Hours 08 Minutes
0 Frames Lat/Lon,leap
Reverse Link Silence Period ReverseLinkSilencePeriod 0
Channels Available ChannelCount 1 sec and local
System Type SystemType 0 System compliant to IS-856
Band Class
Channel Nbr
BandClass
ChannelNbr
1
25
1900MHz Band ti
time offset,
ff t RL
Neighboring Sectors
Neighbor Pilot PN
NeighborCount
NeighborPilotPN
14
435
silence,
Neighbor Pilot PN
Neighbor Pilot PN
NeighborPilotPN
NeighborPilotPN
48
384
Channels
Neighbor Pilot PN
Neighbor Pilot PN
NeighborPilotPN
NeighborPilotPN
285
99 available,
Neighbor Pilot PN NeighborPilotPN 321
Neighbor Pilot PN
Neighbor Pilot PN
NeighborPilotPN
NeighborPilotPN
477
291
system type,
Neighbor Pilot PN
Neighbor Pilot PN
NeighborPilotPN
NeighborPilotPN
267
309
band,
Neighbor Pilot PN
Neighbor Pilot PN
NeighborPilotPN
NeighborPilotPN
144
159
channel#,
N i hb Pil
Neighbor Pilott PN
Neighbor Pilot PN
N i hb Pil tPN
NeighborPilotPN
NeighborPilotPN
180
132
neighbor list
Neighbor Channel Included NeighborChannelIncluded
Neighbor Search Window Size Neighbor
0 Not Included
and search
Included
Search Window Size (14)
SearchWindowSizeIncluded
SearchWindowSize
1 Included
8 60 Chips windows/offset
Neighbor Search Window Neighbor
Offset Included
10-2008 SearchWindowOffsetIncluded
(c)2008 Scott Baxter and Associates
0 Not Included
193
Access Procedures

Access Channel Transmission
 The access channel is an uncoordinated, public channel where

mobiles compete for the sector’s attention despite risks of
uncertain signal-to-noise ratio and even collision with
transmissions of other users
 This situation is much like the access channel in IS-95 and
CDMA2000 although transmissions are shorter
CDMA2000,
 A transmission by a mobile is called a “probe”, first sent at
• A power level calculated by the mobile from its receive power
• A time delayed by a randomly computed number of slots
 If a mobile does not hear an acknowledgment within a prescribed
time, it knows the system did not hear its probe.
 A second p probe is sent at an incrementally
y higher
g p
power,, and only
y
after waiting a randomly computed number of slots
 If unsuccessful, probing continues for as many probes and as
many sequences of additional probes as parameters allow

Access Channel MAC Protocol
 Probes allowed to start at intervals of AccessCycleDuration

 PreambleLength frames of pilot only on I channel, followed by
 CapsuleLengthMax frames of data on Q channel
 Probes shall avoid falling
g on ReverseLinkSilence Duration pperiod,,
which occurs starting on ReverseLinkSilenceInterval times.
• Typical values RLSD, RLSI currently 0 on most systems
 ATI used is

MAC Layer Protocol Numeric Constants
Constant Meaning Value
NACMPType Type field for this protocol Table 2.5.4-1
NACMPDefault Subtype field for this protocol 0x0000
NACMPAPersist Number of different persistence values 4
The recommended maximum number of slots
between transmission of two consecutive
NACMPAccessParameters AccessParameters messages 3 * TACMPCycleLen
TACMPAPSupervision AccessParameters supervision timer 12 * TACMPCycleLen
Time to receive an acknowledgment at the
access terminal for a probe before sending
TACMPATProbeTimeout another probe 128 slots
Maximum time to send an acknowledgment g
TACMPANProbeTimeout for a probe at the access network 96 slots
Time for access terminal to wait after a
successful transmission efore returning a
TACMPTransaction TxEnded indication 1 second
Length of Control Channel Cycle used by the
TACMPCycleLen Access Channel MAC protocol 256 slots
A constant that determines the time for the
access terminal to wait until after
transmitting an access probe in the access
attempt before returning a
TACMPMaxDelayPrevProbe TransmissionFailed indication. 300 slots

Structure of an Access Probe

Access Channel and Reverse Traffic Channel
Long Code Masks
ACCESS CHANNEL LONG CODE MASK
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
10
11
BIT
9
8
7
6
5
4
3
2
1
0
Access Cycle
MIACMAC 1 1 Number P
Permuted
t d (Color
(C l Code
C d | Sector
S t ID)
REVERSE TRAFFIC CHANNEL LONG CODE MASK

41
40
0
39
9
38
8
37
7
36
6
35
5
34
4
33
3
32
2
31
30
0
29
9
28
8
27
7
26
6
25
5
24
4
23
3
22
2
21
20
0
19
9
18
8
17
7
16
6
15
5
14
4
13
3
12
2
10
0
11
BIT
9
8
7
6
5
4
3
2
1
0
MIRTCMAC 1 1 1 1 1 1 1 1 1 1 Permuted (ATILCM)
 A sector’s access channel is public. Its long code mask includes

the sector ID and color code, as well as the Access Cycle Number.
• This ensures uniqueness so that the sector hears only mobiles
i
intending
di to transmit i to iit, and
d not mobiles
bil on other
h sectors
 During traffic channel operation, a mobile uses a long code mask
unique to it
• long code offset is determined by the mobile’s permuted ATI

Establishing a Session

Sessions and Connections
 An EV-DO Session is a state shared by an Access Terminal and

the network.
• Negotiated protocols and configurations are remembered by
both sides as the basis for their communication.
• An access terminal must already have a session underway in
order to communicate with the network
– The only exception is the setup communications made
possible on the access channel for the purpose of initially
g up
setting p a session
 A Connection is a particular state of the air link in which the access
terminal is assigned a forward traffic channel, reverse traffic
channel, and associated MAC channels.
 Within
Withi th
the network,
t k a PPP session
i alsol mustt b be created,
t d allowing
ll i
the AT to obtain an IP address from the PDSN or HA.
 During one ongoing EV-DO session, the terminal and network may
open
p and close their connection many y times.

EV-DO Protocol Stack Reference Architecture
OSI Reference Model

Application User Laptop
Presentation or PDA
Session Application Application
Transport TCP/UDP TCP/UDP
Network IP IP
Upper Layer Upper Layer
Data Link
Application Application
Stream Access Stream
Point
Session (AP) Session
Physical Connection Connection
Security Security
MAC MAC
Physical Physical

Steps in EV-DO Session Setup
 Session Setup: AT requests a UATI from the AN.

• Uniquely identifies the AT within a subnet
 Session Configuration: The AT and the AN negotiate
• Protocol Subtypes
• Application Subtypes
• relevant parameters for multiple AT personalities, if used
 Session Authentication: AAA-AN authenticates the AN using g the
A12 interface.
• The AT is permitted to use network resources only after
successful authentication
 Notice that until the session is established, both the AT and the AN
use the default protocols in the standard. During session
establishment, non-default protocols may be selected for the
further communication in the session
session.

Following a Connection

EV-DO Connection
Access CONNECTION ROUTE UPDATE Access
ACCESS
Point Terminal
(AP) CONNECTION REQUEST (AT)
PILOT
FIC
TRAFFIC MAC ACK RRI
TRAFF
CONTROL DRC
TRAFFIC CHANNEL ASSIGNMENT ACK
MAC
Rake Receiver
MAC RTC ACK DATA
PILOT #1 PN168+0 W23
#2 PN168+2 W23
TRAFFIC CHANNEL COMPLETE #3 PN168+9 W23
#4 PN168+5 W23
XON REQUEST
Pilot Searcher
NULL MESSAGE
NEIGHBOR LIST
XON RESPONSE
ROUTE UPDATE
TRANSITION TO DORMANT
NULL MESSAGE
TRAFFIC CHANNEL ASSIGNMENT
TRAFFIC CHANNEL COMPLETE
NEIGHBOR LIST

Connection: Route Update Message
IS 890 Signaling
IS-890 Is hdris890
Is_hdris890 0 NOT IS-890
IS 890
Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel Capsule
Type Type 14 CONNECTION: Route Update Protocol
Message ID MessageID 0 Route Update
Message Seq MessageSeq 136
Pilot ReferencePilotPn 216
Pilot Ec/Io ReferencePilotStrength 4 0.6 dB
Keep Reference Pilot ReferenceKeep 1
Nbr of Pilots NumPilots 0
 The Route Update message is really a request for the sectors the
mobile wants to have in its active set
• much like the pilot strength measurement message in
CDMA2000
 In this example the mobile asks for only
y one sector, PN216
• “Num Pilots 0” means there is just one pilot

Connection Request Message
Type Type 12 CONNECTION: Idle State Protocol
Message ID MessageID 1 Connection Request
Transaction ID TransactionID 32
Request Reason RequestReason 0 Access Terminal Initiated
Reserved Reserved 0
 The Connection Request Message is sent by an idle mobile to

request entry into active state, creating or joining a session
 This message is sent on the Access Channel
Channel. The mobile expects:
• To hear an acknowledgment on the control channel, or it will
send another probe using the access protocol
• To hear a channel assignment message

AC Ack Message
1.25 msec counter 1.25 msec Counter 0x9A 2C BD D6 98 00 01/06/2006 01:46:28
Message ID MessageID 0 AC Ack
 The Access Channel ACK message is sent on the forward control

channel to tell the mobile its recent probe has been heard by the
system
 After hearing this message, the mobile knows it does not to send
any further
f th repeated t d copies
i off its
it probe
b
• The mobile now waits for some form of channel assignment
message

Traffic Channel Assignment Message
1.25 msec counter 1.25 msec Counter 0xB1 2C BD D6 98 00 01/06/2006 01:46:28
IS-890
IS 890 Signaling Is hdris890
Is_hdris890 0 NOT IS
IS-890
890
Message ID MessageID 1 Traffic Channel Assignment
Channel Included ChannelIncluded 0 Not Included
Frame Offset FrameOffset 8
Slots used to Transmit 1 DRC
Value DRCLength 1 2 Slots
DRC Channel Gain DRCChannelGain 61 30.5 dB
Ack Channel Gain AckChannelGain 8 4.0 dB
Pilot Pn PilotPn 216
SofterHandoff SofterHandoff 0
MacIndex MacIndex 63
DRCCover DRCCover 1
RAB Length RABLength 2 32 Slots
RAB Offset RABOffset 0 0 Slots
 The traffic channel assignment message tells the mobile the

sectors
t iin th
the active
ti sett and
d th
the MAC index
i d for
f each,
h along
l with
ith
DRC length/cover, RAB length/offset, and frame offset
RTC Ack Message
1.25 msec counter 1.25 msec Counter 0x00 2D BD D6 98 00 01/06/2006 01:46:28
Seq Nbr Valid SeqValid 1 SeqNo is valid
Signaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliable
Type Type 4 MAC: Reverse Traffic Channel MAC Protocol
Message ID MessageID 0 RTC Ack
 The mobile sends the RTC Ack message to confirm it has received
the channel assignment and is working to apply it

Traffic Channel Complete Message
AckSeqNo valid Ack AckSeqValid 1 AckSeqNo is valid
Seqq Nbr of Ack AckSeqNo
q 0
Message ID MessageID 2 Traffic Channel Complete
MessageSeq MessageSeq 0
 The mobile sends the Traffic Channel Complete message to

confirm it has implemented the Traffic Channel assignment given
to it by the system.
 Now the system can proceed with any additional signaling for
configuration and the actual connection can proceed

X On Request
Type Type 22 APPLICATION: Stream 2 Application
Message ID MessageID 7 XonRequest
 The mobile now requests that data transmission begin, by

transmitting an X On request.

Null Message
1.25 msec counter 1.25 msec Counter 0x4C 2D BD D6 98 00 01/06/2006 01:46:28
Half-slot
Half slot Reference Counter HSTR 0
 Null Message

Neighbor List Message
Message ID MessageID 4 Neighbor List
Neighbor Count Count 14
Pilot PN PilotPN 435
Pilot PN PilotPN 48
Pilot PN PilotPN 99
Channel Included (14) ChannelIncluded 0 Not Included
Search Window Size Included SearchWindowSizeIncluded 1 Included
Search Window Size (14) SearchWindowSize 8 60 Chips
Search Window Offset Included SearchWindowOffsetIncluded 0 Not Included
 Neighbor PNs, channels, search window sizes and offsets

X On Response
Message ID MessageID 8 XonResponse
 The system confirms whether it has implemented the X On request

from the mobile

Route Update Message
IS 890 Signaling
IS-890 Is hdris890
IS 890
 The mobile again reports its desired active pilot set

• This
Thi can include
i l d additional
dditi l desired
d i d sectors,
t or askk to
t drop
d
unwanted sectors
• In this example, no change is being made

Broadcast Reverse Rate Limit
MAC: Reverse
Broadcast Reverse
1/6/2006 1:46 Control Channel Broadcast Rate Limit
1.25 msec counter 1.25 msec Counter 0xB8 2E BD D6 98 00 01/06/2006 01:46:29
Message ID MessageID 1 Broadcast Reverse Rate Limit
RPC Count RPCCount 1
Rate Limit RateLimit 5 153.6 kbps
Reserved Reserved 0
 The Broadcast Reverse Rate Limit message tells EV-DO rev. 0

mobiles the maximum permitted reverse link transmit rate
• Mobiles start at 9600 bps and dynamically creep upward in
speed until they reach this limit, or until the system asks for
every mobile to reduce by setting the Reverse Activity bit
 EV-DO rev. B mobiles use a different mechanism for speed control

Nak Message
1.25 msec counter 1.25 msec Counter 0xD9 56 BD D6 98 00 01/06/2006 01:46:42
Message ID MessageID 2 Nak
 Mobile sends Application NAK message

• This indicates the end of transmission

Nak Message
1.25 msec counter 1.25 msec Counter 0x20 47 BD D6 98 00 01/06/2006 01:46:37
Message ID MessageID 2 Nak
 System sends Application NAK message in response to the mobile

• Mobile goes to idle state

Page Message
1.25 msec counter 1.25 msec Counter 0x12 C0 BF D6 98 00 01/06/2006 01:49:59
Type Type 12 CONNECTION: Idle State Protocol
Message ID MessageID 0 Page
 Forward control channel Page pages mobile to return to active

state
t t

AC Ack Message
1.25 msec counter 1.25 msec Counter 0xA5 C0 BF D6 98 00 01/06/2006 01:49:59
Message ID MessageID 0 AC Ack
 Control Channel MAC protocol sends this Access Channel AC Ack

message to confirm the mobile’s probe has been heard

RTC Ack Message
1.25 msec counter 1.25 msec Counter 0x9B C1 BF D6 98 00 01/06/2006 01:50:00
Message ID MessageID 0 RTC Ack
 Mobile acknowledges system

1.25 msec counter 1.25 msec Counter 0xAD C1 BF D6 98 00 01/06/2006 01:50:00
IS 890 Si
IS-890 Signaling
li I hd i 890
IS 890
 Mobile
M bil acknowledges
k l d it iis using
i ththe ttraffic
ffi channel
h l

Null Message
1.25 msec counter 1.25 msec Counter 0xEB C1 BF D6 98 00 01/06/2006 01:50:00
Half-slot
 Forward Traffic Channel

Neighbor List Message
1.25 msec counter 1.25 msec Counter 0xEB C1 BF D6 98 00 01/06/2006 01:50:00
IS 890 Signaling
IS-890 Is hdris890
IS 890
Message ID MessageID 4 Neighbor List
Neighbor Count Count 9
Pilot PN PilotPN 99
Pilot PN PilotPN 45
Pilot PN PilotPN 63
Channel Included (9) ChannelIncluded 0 Not Included
Search Window Size Included SearchWindowSizeIncluded 1 Included
Search Window Size (9) SearchWindowSize 8 60 Chips
Search Window Offset Included SearchWindowOffsetIncluded 0 Not Included
 Forward traffic channel

Route Update Message
IS 890 Signaling
IS-890 Is hdris890
IS 890
Pn Offset PilotPnPhase 31690
Ec/Io PilotStrength 19 0.1 dB
Pilot Drop Timer Not Expired Keep 1
 The mobile requests its desired active set.

 This time there are two pilots, PN offset 12 and PN phase 31690

Null Message
 Forward traffic channel null message

Traffic Channel Assignment Message
Message ID MessageID 1 Traffic Channel Assignment
Frame Offset FrameOffset 7
Slots used to Transmit 1 DRC
Value DRCLength 2 4 Slots
DRC Channel Gain DRCChannelGain 58 29.0 dB
Ack Channel Gain AckChannelGain 8 4.0 dB
Pilot Pn PilotPn 12
DRCCover DRCCover 1
Pilot Pn PilotPn 495
DRCCover DRCCover 2
 Forward Traffic Channel. Note PNs, MAC indices, DRC and RA

IS 890 Signaling
IS-890 Is hdris890
IS 890
 Reverse
R ttraffic
ffi channel
h l

Connection Close Message
1.25 msec counter 1.25 msec Counter 0x5E C3 C0 D6 98 00 01/06/2006 01:51:22
Half-slot
Seq Nbrb oof Ack
c AckSeqNo
c Seq o 255
55
Type Type 13 CONNECTION: Connected State Protocol
Message ID MessageID 0 Connection Close
Reason for Close CloseReason 0 Normal Close
Suspend Enable SuspendEnable 0 Disabled
 Forward traffic channel closes the connection

• Note “Normal Close”, i.e., “this was my idea”

Connection Close Message
1.25 msec counter 1.25 msec Counter 0x73 C3 C0 D6 98 00 01/06/2006 01:51:22
IS 890 Signaling
IS-890 Is hdris890
IS 890
Type Type 13 CONNECTION: Connected State Protocol
Message ID MessageID 0 Connection Close
Reason for Close CloseReason 1 Close Reply
Suspend Enable SuspendEnable 0 Disabled
 Reverse traffic channel. Note “Close Reply” i. e., “it wasn’t my

idea but we will since you want to”

Access Terminal Architecture
And Handoffs Route Updates

Block Diagram of an Access Terminal
Digital
Di it l
Rake Receiver Symbols
Chips Traffic Correlator
ming
PN xxx Walsh xx
summ
bits
Traffic Correlator
t 
PN xxx Walsh xx
ontrol
Symbols
Receiver Viterbi Decoder,
Decoder
co
Traffic Correlator
ttime-aligned
d
RF Section Convl. Decoder,
IF, Detector PN xxx Walsh xx Demultiplexer
power
Traffic Correlator Packets
AGC
PN xxx Walsh xx
RF
Open L
Messages
UART
Duplexer Pilot Searcher
CPU
PN xxx Walsh 0
Loop
Conv or
C
RF Transmit Gain Adjust Messages Turbo
Coder
Transmitter
Transmitter Digital Section
RF Section
Long Code Gen.

1xEV-DO Forward Link: AT Rake Receivers
Access Terminal
ONE sector at a time!!
Rake Receiver
PN Walsh
PN Walsh
 user
RF PN Walsh data
AP
PN Walsh
AP
PN W=0
 Burst by burst, the Access Terminal asks for transmission from whichever
Active sector it hears best, at the max speed it can successfully use
 Using latest multipath data from its pilot searcher, the Access Terminal uses
the combined outputs
p of the four traffic correlators ((“rake fingers”)
g )
 Each rake finger can be set to match any multipath component of the signal
 The terminal may be a dual-mode device also capable of 1xRTT voice/data
• fingers could even be targeted on different AP, but in 1xEV-DO mode
only a single AP transmits to usus, never more than one at a time time, so this
capability isn’t needed or helpful in 1xEV-DO mode

1xEV-DO Reverse Link: Soft Handoff
All “Active Set” sectors Access Terminal
can listen to the AT
Rake Receiver
PN Walsh
PN Walsh
 user
RF PN Walsh data
AP
PN Walsh
DO-RNC chooses AP
‘cleanest’ packet PN W=0
 The AT uses the Route Update protocol to frequently update its

preferences of which sectors it wants in its active set
 Frame-by-frame, all the sectors in the Active Set listen for the AT’s
signal
i l
 Each sector collects what it heard from the AT, and sends it back to
the DO-RNC.
 The DO-RNC uses the cleanest (lowest number of errors) packet

1xEV-DO Route Update Mechanics
Access Terminal
Rake Receiver
DO-RNC PN Walsh
? PN Walsh

S l
Sel. ? RF PN Walsh user
ser
data
AP PN Walsh
AP Searcher Pilot Ec/Io

PN W=0
 1xEV-DO Route Update is ‘driven’ by the Access Terminal

• Access Terminal continuously checks available pilots
• Access Terminal tells system pilots it currently sees
• System puts those sectors in the active set, tells Access Terminal
 Access terminal requests data bursts from the sector it likes best
• tells which sector and what burst speed using the DRC channel
• so there is no “Soft Handoff” on the forward link, just fast choices
 All sectors in Active Set try to hear AT, forward packets to the DO-RNC
• so the reverse link does benefit from CDMA soft handoff

Route Update Pilot Management Rules
 The Access Terminal considers pilots in sets PILOT SETS
AT m
• Active: sectors who listen and can transmit Active 6
must supp
• Candidates: sectors AT requested, but not
yet approved by system to be active Candidate 6
• Neighbors: pilots told to AT by system, as Neighbor 20
nearby sectors to check
port
• Remaining: any pilots used by system but Remaining
not already in the other sets (div. by PILOT_INC)
 Access Terminal sends a Route Update HANDOFF
Message to the system whenever: PARAMETERS
• It transmits on the Access Channel PilotAdd PilotDrop
• In idle state, it notices the serving sector is PilotDrop Pilot
far from the sector where last updated Timer Compare
• In connected state, whenever it notices the Dynamic Thresholds?
Handoff Parameters suggest a change Softslope
AddIntercept
DropIntercept
NeighborMaxAge

Format of Traffic Channel Assignment Message
 The Traffic Channel

Assignment Message
assigns all or some of the
sectors the access terminal
requested in its most recent
Route Update request
 The message lists every
Active pilot; if it doesn’t list it,
it’ss not approved as active
it
 Notice the MAC index and
DRC Cover so the access
terminal knows how to
request forward link bursts
on the data rate control
channel
Neighbor Structure Maintained by the AT
Pilot PN Channel SrchWinSize SrchWinOffset

IS-871 For Session
Interoperability

IS-871 For Session Interoperability
 Lack of RF transition trigger definitions has been largely resolved

by the “Hybrid
Hybrid Mode”
Mode of dual-mode
dual mode terminals
 The situation is better regarding Session portability
• session interoperability are described in IS-871
• although no RF triggers are described,
described the necessary steps are
defined for transition of packet sessions between EV and 1x
networks
 The following slides show the transitions defined in the IS-871
standard, along with the steps involved

cdma2000 to HRPD Dormant Packet Data
Session Handoff - Existing HRPD Session

Session Handoff - Existing HRPD Session
a. The change of AN is indicated by the Location Update procedures as defined in [10].
b. The target AN sends an A9-Setup-A8 message, with Data Ready Indicator set to ‘0’, to
the target PCF and starts timer TA8-setup
TA8-setup. The handoff indicator of the A9 Indicators IE
shall be set to ‘0’.
c. If the PDSN address is not available to the target PCF by other means, the target PCF
selects a PDSN for this connection using the PDSN selection algorithm as specified in
[10]. The target PCF sends an A11-Registration Request message to the PDSN. The
A11-Registration
A11 Registration Request message includes the MEI within the CVSE and the PANID
and CANID within the NVSE. The target PCF starts timer Tregreq.
d. The A11-Registration Request message is validated and the PDSN accepts the
connection by returning an A11-Registration Reply message with an accept indication
and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes
the Data Available Indicator within the CVSE. The A10 connection binding information at
th PDSN iis updated
the d t d tto point
i t tto th
the target
t t PCF.
PCF The
Th target
t t PCF stops
t timer
ti Tregreq.
T
e. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending
an A11-Registration Update message. The PDSN starts timer Tregupd.
f. The source BSC/PCF responds with an A11-Registration Acknowledge message. The
PDSN stops p timer Tregupd.
g p
g. The source BSC/PCF sends an A11-Registration Request message with Lifetime set to
zero, to the PDSN. The source BSC/PCF starts timer Tregreq.
h. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The
source BSC/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.
i.i The target PCF responds to the target AN with an A9 A9-Release-A8
Release A8 Complete message.
message The
target AN stops timer TA8-setup. Note that this step can occur any time after step d.

Session Handoff - New HRPD Session

Session Handoff - New HRPD Session
a. The AT and the target AN initiate HRPD session establishment. During this procedure, the target AN does not receive a
UATI for an existing HRPD session. Since no HRPD session exists between the MS/AT and target AN/PCF, an HRPD
session is established where protocols and protocol configurations are negotiated, stored and used for communications
between the MS/AT and the target AN. Refer to [10], Section 5, Session Layer.
b. The AT indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default
packet application bound to the target AN is in the open state)
state).
c. After HRPD session configuration the MS/AT initiates PPP and LCP negotiations for access authentication. Refer to [19].
d. The target AN/PCF generates a random challenge and sends it to the MS/AT in a CHAP Challenge message in accordance
with [22].
e. When the target AN/PCF receives the CHAP response message from the MS/AT, it sends an Access-Request message on
the A12 interface to the target AN-AAA which acts as a RADIUS server in accordance with [25].
f The target AN-AAA
f. AN AAA looks up a password based on the User-name
User name attribute in the Access-Request
Access Request message and if the
access authentication passes (as specified in [22] and [25]), the target AN-AAA sends an Access-Accept message on the
A12 interface in accordance with [25] (RADIUS). The Access-Accept message contains a RADIUS attribute with Type set
to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to Section 2.3.2, AN-AAA Support.
g. The target AN/PCF returns an indication of CHAP access authentication success to the MS/AT. Refer to [22].
h. If the target AN supports the Location Update procedure, the target AN updates the ANID in the AT using the Location
Update procedure. The target AN may also retrieve the PANID from the AT if necessary. This step may occur any time
after step a
a.
i. The AT indicates that it is ready to exchange data on the service stream. (E.g., the flow control protocol for the default
packet application bound to the packet data network is in the open state).
j. The target AN/PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message
includes the MEI within the CVSE and the PANID and the CANID within the NVSE. If PANID is not sent in step h, the
target AN/PCF sets the PANID field to zero and the CANID field to its own ANID. The target AN/PCF starts timer Tregreq.
k. The A11-Registration
A11 Registration Request message is validated and the PDSN accepts the connection by returning an A11- A11
Registration Reply message with an accept indication and Lifetime set to the configured Trp value. If the PDSN has data
to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is
updated to point to the target AN/PCF. The target AN/PCF stops timer Tregreq.
l. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending an A11-Registration Update
message. The PDSN starts timer Tregupd.
m. The source BSC/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd.
n. The
Th source BSC/PCF sends d an A11
A11-Registration
R i t ti Request
R t message with
ith Lif
Lifetime
ti sett to
t zero, to
t the
th PDSN
PDSN. The
Th source
BSC/PCF starts timer Tregreq.
o. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The source BSC/PCF closes the A10
connection for the MS/AT and stops timer Tregreq.

HRPD to cdma2000 Dormant Packet Data
Session Handoff

HRPD to cdma2000 Dormant Packet Data
Session Handoff
a. Upon transitioning to the cdma2000 system, the MS/AT transmits an Origination Message
with DRS set to ‘0’ and with layer 2 acknowledgment required, over the access channel of
the air interface to the target BSC/PCF to request service. This message may contain the
SID, NID and PZID corresponding to the source PCF from which the MS/AT is coming, if
p y is supported
this capability pp byy the air interface. If available,, these values are used to
populate the PANID field of the A11-Registration Request message that the target
BSC/PCF sends to the PDSN.
b. The target BSC/PCF acknowledges receipt of the Origination Message with a Base
Station Acknowledgment Order to the MS/AT.
c. The
c e target
ta get BSC/PCF
SC/ C sends
se ds aan A11-Registration
eg st at o Request
equest message
essage to tthee PDSN.
S The e
A11-Registration Request message includes the MEI within the CVSE and the PANID
and the CANID within the NVSE. The target BSC/PCF starts timer Tregreq.
d. The A11-Registration Request message is validated and the PDSN accepts the
connection by returning an A11-Registration Reply message with an accept indication
and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes
th D
the Datat AAvailable
il bl IIndicator
di t within
ithi the
th CVSE.
CVSE Th The A10 connection ti bi
binding
di iinformation
f ti att
the PDSN is updated to point to the target BSC/PCF. The target BSC/ PCF stops timer
Tregreq. If the PDSN responds to the target BSC/PCF with the Data Available Indicator,
the target BSC/PCFestablishes a traffic channel ([1] 2.15.5.4-1). In this case the
remaining steps in this procedure are omitted.
e The PDSN initiates closure of the A10 connection with the source AN/PCF by sending an
e.
A11-Registration Update message. The PDSN starts timer Tregupd.
f. The source AN/PCF responds with an A11-Registration Acknowledge message. The
PDSN stops timer Tregupd.
g. The source AN/PCF sends an A11-Registration Request message with Lifetime set to
zero to the PDSN.
zero, PDSN The source AN/PCF starts timer Tregreq Tregreq.
h. The PDSN sends an A11-Registration Reply message to the source AN/PCF. The source
AN/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.
MS/AT Terminated Voice Call During Active
HRPD Data Packet (Intra-PDSN/Inter-PCF)

HRPD Data Packet (Intra-PDSN/Inter-PCF)
a. The BS sends a Page Message containing the MS/AT address over the paging channel. The MS/AT may ignore this Page
Message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed.
b. The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop.
c. The AN sends an A9-AL Disconnected message to PCF2 to stop data flow and starts timer Tald9.
d Upon receipt of the A9-AL
d. A9 AL Disconnected message
message, PCF2 sends an A9-AL
A9 AL Disconnected Ack to the ANAN. The AN stops
timer Tald9.
e. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c.
f. The BS establishes a traffic channel.
g. The BS sends an Alert with Info message to instruct the MS/AT to ring.
h. The MS/AT and the cdma2000 system set up the data session for handoff from HRPD as a concurrent call service if the
MS/AT supports the concurrent call service capability and selects to handoff the data session from the HRPD to the
cdma2000 system. Refer to [11], Section 2.17.2.1 steps (a) to step (g).
i. The BS sends an A9-Setup-A8 message to PCF1 to establish the A8 connection and starts timer TA8-setup. If the MS/AT
has indicated the presence of data ready to send, the BS shall set the Data Ready Indicator to ‘1’; otherwise, the BS
shall set the Data Ready Indicator to ‘0’.
j. PCF1 sends an A11-Registration Request message to the PDSN to establish the A10 connection to handoff from the
HRPD system to the cdma2000 system. PCF1 starts timer Tregreq.
k The
k. Th A11
A11-Registration
R i i Request
R message iis validated
lid d and d the
h PDSN accepts the
h connectioni by
b returning
i an A11-
A11
Registration Reply message with an accept indication. PCF1 stops timer Tregreq.
l. PCF1 sends an A9-Connect-A8 message after the completion of the A10 connection handoff. The BS stops timer TA8-
setup.
m. At this point, the data session is successfully handed off from the HRPD to the cdma2000 system.
n. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.
o. PDSN Initiates closure of the A10 connection with PCF2 by sending an A11-Registartion Update message. PDSN starts
timer Tregupd. This step may occur direct after step j.
p. PCF2 responds with an A11-Registartion Acknowledge message. The PDSN stops timer Tregupd.
q. PCF2 sends an A11-Registration Request message with Lifetime set to zero, to the PDSN. PCF2 starts timer Tregreq.
r. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 closes the A10 connection for the MS/AT and stops
timer Tregreq.
s. Upon not having received any transmissions from the MS/AT prior to timer Tairdrop expiration, the AN sends an A9-
Release-A8 message to PCF2 and starts timer Trel9. This step can occur any time after step b.
t. PCF2 responds to the AN with an A9-Release-A8 Complete message. The AN stops timer Trel9.

AT Leaving During an
Active 1xEV-DO Data Session

AT Leaving During an
Active 1xEV-DO Data Session
a. The BS sends a Page Message containing the MS/AT address over the paging channel.
The MS/AT may ignore this Page Message to continue the HRPD session. If the MS/AT
g
ignores the message,
g , the following
g steps
p are not pperformed.
b. The AN determines that it is not receiving any transmissions from the MS/AT and starts
timer Tairdrop.
c. The AN sends an A9-AL Disconnected message to PCF2 to stop data flow and starts
timer Tald9.
d Upon receipt of the A9
d. A9-ALAL Disconnected message
message, PCF2 sends an A9 A9-AL
AL Disconnected
Ack message to the AN. The AN stops timer Tald9.
e. The MS/AT sends a Page Response message to the BS. This step can occur any time
after step c.
f. The BS establishes a traffic channel upon receipt of the Assignment Request message.
h. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.
i. When the timer Tairdrop expires, the AN initiates the release of the A8 connection by
sending an A9A9-Release-A8
Release A8 message to PCF2 and starts timer Trel9
Trel9.
j. PCF2 sends an A11-Registration Request message with Lifetime set to zero, to the
PDSN. PCF2 starts timer Tregreq.
k. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 closes the A10
connection for the MS/AT and stops timer Tregreq.
l. PCF2 responds to the AN with an A9-Release-A8 Complete message. The AN stops
timer Trel9.

HRPD Packet Data Session (Intra-PCF)

HRPD Packet Data Session (Intra-PCF)
a. The BS sends a Page Message containing the MS/AT address over the paging channel. The MS/AT may ignore
this Page Message to continue the HRPD session. If the MS/AT ignores the message, the following steps are
not performed.
b The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop
b. Tairdrop.
c. The AN sends an A9-AL Disconnected message to the PCF to stop data flow and starts timer Tald9.
d. Upon receipt of the A9-AL Disconnected message, the PCF sends an A9-AL Disconnected Ack to the AN. The
AN stops timer Tald9.
g Response
e. The MS/AT sends a Page p message
g to the BS. This step
p can occur any
y time after step
p c.
f. The BS establishes a traffic channel.
h. The MS/AT and cdma2000 system set up the data session for handoff from HRPD as a concurrent call service if
the MS/AT supports the concurrent call service capability and selects to handoff the data session from the
HRPD to
t the
th cdma2000
d 2000 system.
t R
Refer
f tto [11]
[11], S
Section
ti 2 2.17.2.1
17 2 1 steps
t ((a)) tto step
t 3(3(g).
)
i. The BS sends an A9-Setup-A8 message to the PCF to establish the A8 connection and starts timer TA8-setup. If
the MS/AT has indicated the presence of data ready to send, the BS shall set the Data Ready Indicator to ‘1’;
otherwise, the BS shall set the Data Ready Indicator to ‘0’.
j. The PCF sends an A9-Connect-A8 message to the BS. The BS stops timer TA8-setup.
k. At this point, the data session is successfully handed off from the HRPD system to the cdma2000 system.
l. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.
m. Upon not having received any transmissions from the MS/AT prior to timer Tairdrop expiration, the AN sends an
A9-Release-A8 message to the PCF and starts timer Trel9.
n. Upon
U receipt
i t off th
the A9
A9-Release-A8
R l A8 message, the
th PCF sends
d an A9-Release-A8
A9 R l A8 Complete
C l t message to
t the
th AN
AN.
The AN stops timer Trel9.

cdma2000 to HRPD Active Packet Data Session Handoff
Status Management Supported by Feature Invocation

cdma2000 to HRPD Active Packet Data Session Handoff
Status Management
g Supported
pp byy Feature Invocation
a. The MS/AT sends an Origination Message, including the feature code as
the called number, to the BS when the MS/AT starts the HRPD
communication. This feature code indicates that the MSC should activate a
feature (e.g.,
(e g do not disturb)
disturb).
b. The BS and the MSC setup the call. From the feature code, the MSC knows
not to page the MS/AT for a voice call. Refer to [11], Section 2.2.2.1,
Mobile Origination.
c. The BS and the MSC clear the call. Refer to [[11],
], Section 2.3.5.3,, Call Clear
Initiated by MSC.
d. The MS/AT starts communication on the HRPD session. Refer to Section
3.3.2, AT Initiated Call Re-activation from Dormant State (Existing HRPD
Session).
e. The
Th MS/AT terminates
t i t communication
i ti on theth HRPD sessioni whenh th the
HRPD session goes dormant or inactive. Refer to Section 3.5.2, HRPD
Session Release - Initiated by the AT (No Connection Established).
f. The MS/AT sends an Origination Message, including the feature code as the
calling number, to the BS when the MS/AT ends the HRPD communication.
This feature code indicates that the MSC should deactivate the feature
activated in step a.
g. The BS and the MSC setup the call. From the feature code, the MSC know
it may page the MS/AT for a voice call. Refer to [11], Section 2.2.2.1,
Mobile Origination
Origination.
h. The BS and the MSC clear the call. Refer to [11], Section 2.3.5.3, Call Clear
Initiated by MSC.
Module 344
1xEV-DO
RF Performance Optimization

344 Contents
 1xEV-DO Key Performance Indicators
• Bad Packet Rate, Serving Data Rate, Reverse Link Statistics
• Receive Power
Power, Composite C/I
• Mobile Transmit Power at Given Rate
• Reverse Link Closed Loop Power Control
• Latency and Throughput
 Air Interface Review from Optimization Perspective
 Backhaul Considerations
 Optimizing
O ti i i th the Ai
Air IInterface
t f
• Coverage, Neighbor List, Search Windows and Offsets
 Drive-Test Tools Summary and Examples
 Setup
S issues
i
 Forward Link Throughput Optimization
• Detecting IP and RF issues
• The role of RF interference in determining requested burst rate

1xEV-DO
Key Performance Indicators

Popular Generic KPIs for Wireless Services

Bad Packet Rate
 Packet error rates in both directions should be comparable to
packet retransmission rates in 1xRTT
 5% is a typical target value; this chart shows excellent results

Data Speed During Connection
 The average data

rate received
depends on:
• “dilution” of
sector capacity
by multiple users
• Reduction of
speed due to
poor RF channel
p
conditions
 The distribution of
packet rates of one
user show
h th
the
effects of RF
impairments only

Reverse Link Traffic Statistics
 This summary shows reverse link transmit power, PER, and

average PER
 Both
B th F
Forward d and
dRReverse lilink
k retransmitted
t itt d b
bytes
t are shown,
h
along with the total data KB transmitter

Io -- Receive Power
 As in 1xRTT, receive power is not the primary quality indicator
 It should be well above -100 dbm (“coverage hole” conditions) and
not higher than -40
40 dbm (“intermod”
( intermod conditions)
 Receive power is the “I” in C/I. C/I is more important than I alone
 Receive power remains a vital clue to some types of interference
troubleshooting

I0, Total AT Receive Power
 AT Receive Power I0
overload>>
• usually expressed in dBm
AT Receiver -40
• measured derived from Rake
LNA IF R
handset IF AGC voltage
 x
 R
• broadband, “unintelligent” BW BW R
30
~30 LO 1.25
1 25
measurement: includes all S
<too weak
MHz. MHz.
RX Level
RF in the carrier bandwidth (from AGC) -90
regardless of source, not -105
just RF from serving BTS
<<
 AT power is important, but it’s exact value isn’t critical
• too much received signal (-35 dbm or higher) could drive the
AT’s sensitive first amplifier into overload, causing intermod and
code distortion on received CDMA signals
• too little received signal (-105 or weaker) would leave too much
noise
i iin ththe signal
i l after
ft d de-spreading,
di resulting
lti iin symbol
b l errors,
bit errors, packet errors, and other problems
Mobile Transmit Power at Given Rate
 When mobile transmit power is significantly higher than expected

for the location of the mobile and its vicinity, reverse link
interference may exist
 Inspect the receive level indications from the base station, looking
for high receive power warnings
• Both peak and average RF receive levels are useful, indicating
whether the problem is constant or intermittent
• If the p
problem appears
pp to be real RF interference,, special
p
weak-signal detection techniques may be necessary to track it
down, just as in IS-95 CDMA

Reverse Link Closed Loop Power Control
 As in 1xRTT, Reverse Link Closed Loop Power Control is an

indication of general interference on either link
 Interference on the uplink of the serving sector will make the sector
request higher power from each served mobile
 Interference on the forward link at the mobile will raise the mobile’s
mobile s
receive power, causing it to want to transmit at lower power and
thereby forcing the serving sector to request the mobile to transmit
at higher power.
 If higher-than-normal closed loop power control is observed,
inspect the other forward and reverse link RF parameters to
identify whether the interference is forward link or reverse link.

Latency
IP Data Environment PDSN/Foreign Agent
Backbone
Internet Network
VPNs T SECURE TUNNELS T
EVDO RF Environment
nt
Authentication
a Environmen
PDSN
Home Agent
Authorization AAA R-P Interface
Accounting •Coverage Holes
AP •Pilot Pollution
•Missing Neighbors
SEL EVM •Fwd Pwr Ovld
t1
IP Data
•Rev
R P Pwr OOvldld
•Search Windows
DO RNC or FMS Wireless
•Island Cells
Mobile Device
EVDO IOS PPP •Slow Handoff
 Latency can occur because of RF channel congestion or from

IP network causes
• RF overload can delay availability of supplemental channels
• IP network
t k congestion
ti can delay
d l availability
il bilit off packets
k t
 Ping and loopback tests with local PDSN and servers can
identify whether problem is in backbone network
 Does latency correlate with independent evidence of RF
congestion?

Throughput
Backbone
Internet Network
CDMA RF Environment
nt
Authentication
a Environmen
PDSN
Home Agent
SEL EVM •Fwd Pwr Ovld
t1
IP Data
•Rev
R P Pwr OOvldld
•Search Windows
DO RNC / FMS Wireless
•Island Cells
Mobile Device
 Throughput can be limited by RF and IP causes

• Traditional RF problems limit capacity of the channel
• Co
Congestion
gest o in tthe
e IP network
et o cacan limitt speed o
of data a
available
a ab e
 Does low throughput correlate with independent RF indicators?
 Does low throughput correlate with independent IP pings and tests?

Composite C/I
 Composite C/I is the primary indication of forward link quality

• C/I drives the rate of the mobile’s DRC requests for packets
 Poor C/I can be the result of
• “pilot pollution” caused by too many comparable signals being
present at the mobile’s location
• Interference from external RF sources on the forward link

Ec/Io and C/I
 There are two main ways of expressing
signal quality in 1xEV-DO
AP
 C/I is the ratio of serving sector power to
everything else
Relationship of • C/I determines the forward data rate
C/I and Ec/Io • mobiles measure C/I during the pilot
For EV-DO
EV DO Signals burst period, then from it decide what
mobile receive power
data rate to request on the DRC
Power from
 Ec/Io is the ratio of one sector’s pilot power to
C Serving Sector Ec the total received power
Interference Power
 Ec/Io and C/I are related, and one can be
I from other cells Io calculated from the other
0
0
 EVDO Ec/Io is close to 0 db near a sector,
and ranges down to -10 at a cell’s edge
Ec/Io, db
-10
 EVDO C/I can be above +10 db near a
-20
sector, and -20 or lower at the edge
E
-30
-30 -20 -10 0 +10 +20
C/I, db
Relationship of Ec/Io and C/I in 1xEV-DO Systems
-30 -25 -20 -15 -10 -5 0 5 10 15 20
0
Ec/Io,
C/I,
db
db
-0.04 20
-0.14 15
-0.17 14 -5
-0.21 13
-0.27 12
-0.33 11
-0.41
0 41 10 10
-10
-0.51 9
-0.64 8
c/Io, db
-0.79 7
-0.97 6 -15
1.19
-1.19 5
Ec
-1.46 4
-1.76 3
-2.12 2 -20
-2.54 1
-3.01 0
-3.54 -1
-4.12 -2
-25
-4.76 -3
-5.46 -4
-6.97 -6
-8.64
8 64 -8
8
-10.41 -10 -30
-12.27 -12 C/I, db

Statistical EVDO Indications
 RF Connection failures
• Mobile does not reach an assigned traffic channel
 RF Connection Losses
• Existing connection is lost due to failure of forward or reverse
link
 RF Blocking
• Due to MAC index, backhaul, or other congestion

Backhaul and
Related Considerations

Rate Limitations from Backhaul
 Wireless sites are commonly connected using T-1s or E-1s,

depending on local availability
• In the case of T-1s, the raw rate is 1.544 megabits/second.
– Accounting for overhead, this translates into a maximum
steady throughput of roughly 400 to 450 kb/s per sector on
a 3-sector, 1-carrier EV-DO site.
– If one sector is busy while the other two are only lightly
loaded,, throughput
g p of roughly
g y 1 mb/s can be obtained on
one sector
– However, early 1xEV-DO cards without support for multiple
ARQ instances can only achieve about 400 kb/s
th
throughput
h t even without
ith t backhaul
b kh l lilimitations
it ti
 Solutions under study to relieve backhaul congestion include fiber-
based ATM to the sites; multiple-T1s; sites linked by Cable
Modems and other methods
Modems,

Optimizing the RF Air Interface

Dealing With RF Coverage Anomalies
 It is difficult to build a system without encountering a few coverage

holes and without having some sectors that cover more than
planned
• The techniques for identifying and resolving these problems
are similar to IS-95 and 1xRTT, with a few modifications
 Detection methods: Area sweeps with EV EV-DO DO PN scanners and
EV-DO terminals
• If a sector is in the active set of mobiles in places beyond the
line jjoining
g its surrounding
g tier of sites,, reduce its coverage
g
– Site RF parameters, antenna downtilt, or antenna height
• If a sector fails to cover its intended area, look for obvious
hardware or environmental reasons
– Repair or correct any such impairments, and if
unsuccessful, look for other serving sectors
– Reradiators are feasible for EV-DO, but setup is tricky

Generating and Optimizing Neighbor Lists
 After coverage of each sector has been studied and adjusted if

necessary, neighbor relationships are now stable
 Initial neighbor lists can be generated from propagation prediction
modeling or even from drive-test results with AT or PN scanners
 The most reliable way to groom neighbor lists is to use system
tools to collect route update requests from each sector. These
results can be analyzed in matrix form to determine the frequency
of requests for each surrounding sector
• Sectors with more than 5% of requests are usually added
• Sectors with less than 1% of requests are usually unnecessary
• Watch out for sectors that are already neighbors of neighbors
andd would
ld b
be unnecessary
• Watch out for special specific cases where unusual
relationships exist because of terrain and busy roadways

Optimizing Search Windows
 The pilot searcher of a mobile must be able to see the pilots of any
sectors it may encounter – otherwise route update is impossible
 Timing errors affect pilot searching
searching. Sources include:
• Timing delay from reference sector to mobile
– This delay is unknown to the mobile, but it goes into the mobile’s
reference timing without the mobile’s knowledge
• Timing delay from needed neighbor signal to the mobile
– This delay is also unknown to the mobile, but it can shift the
apparent timing of the desired neighbor either ahead or behind
the timing
g the mobile expects
p
• The worst-case error in timing is the propagation delay of a straight
line between reference sector and desired sector
• Neighbor search window can be set to this level initially and possibly
reduced if accumulated data later allows
 Active search windows “float” on their individual pilots and do not need to
be large enough to handle propagation delay. They only need to
accommodate delay spread, which is better measured than calculated.

Search Window Offset
Search Window Offset Offset (PN chips) -1.5 -1.0 -0.5 0.0 +0.5 +1.0 +1.5
0 0
1 +0.5 x WindowSize
2 +1.0 x WindowSize
3 +1.5 x WindowSize
4 - 0.5 x WindowSize
5 -1.0 x WindowSize
6 -1.5 x WindowSize
7 reserved
 Search window offsets make it possible to individually compensate

for the great distance of certain sectors from the service area of
another
• The range of adjustment can effectively shift the center of the
search window by up to 1.5 times earlier or later than the
actual search window width

Andrew’s Invex3G Tool
 100 MB ethernet connection to

PC
 the eight card slots can hold
receivers or dual-phone cards
 there’s also room for two
internal PN scanners
 Multiple Invex units can be
cascaded for multi-phone load-
test applications
pp
 Cards are field-swappable -
Users can reconfigure the unit
in the field for different tasks
without
ih ffactory assistance
i

Overview of Field Tool IP Test Capabilities
Application
pp Description
p Purpose
p
Raw Upload Uploads data with no overhead (no headers, no Testing uplink throughput
handshaking beyond the normal TCP handshaking)
Raw Download Downloads data with no overhead (no headers, no Testing downlink throughput
handshaking beyond the normal TCP handshaking.)
Raw Loopback A loopback (data is sent to the remote server which Simultaneous exercise of the uplink and downlink
returns the same data) application with no overhead (no
headers, no handshaking beyond the normal TCP
handshaking.)
Ping (ICMP ECHO) Ping does not use the TCP protocol, but rather uses the Determining round-trip-time between the user and the
connectionless and “unreliable” ICMP protocol. Sends remote server, as well as general link integrity (by
small echo request packets to a remote server
server, which counting the number of missing echo reply packets)
packets).
responds with an echo reply.
HTTP GET A standard web page “browse” request. If Raw Download is unavailable, testing downlink
throughput; modeling typical customer use.
HTTP POST A web-based upload (similar to how web-based email If Raw Upload is unavailable, testing uplink throughput.
p
sites allow users to upload files as “attachments”).
)
FTP GET A standard FTP file download. Many file downloads on If Raw Download and HTTP GET are unavailable, testing
the Internet use FTP. downlink throughput; modeling typical customer use.
FTP PUT A FTP file upload. The file is generated by the Invex3G If Raw Upload and HTTP POST are unavailable, testing
platform and sent to the server. uplink throughput
Mail GET (POP3) Retrieves all the mail for a given mailbox (e
(e-mail
mail Modeling typical customer use.
address) from an e-mail server. Note: does not delete
the e-mail messages from the mailbox.
Wait Waits a specified amount of time. Testing idle timers, timeouts, etc.

Agilent Drive-Test Tools
 Agilent offers Drive-Test tools

• Serial interfaces for upp to four
CDMA phones or cards
• A very flexible digital receiver
with several modes
 PN Scanner
• Fast, GPS-locked, can scan
two carrier frequencies
 Spectrum Analyzer
• Can scan entire 800 or 1900
mHz. Bands
 Base-Station Over-Air Tester
(BOAT)
• Can display all walsh channel
activity on a specific sector
• Useful for identifying hardware
problems, monitoring
instantaneous traffic levels, etc.
 Post-Processing tool: OPAS32
1xEV-DO Setup Performance:
Sessions and Connections

Session Configuration Parameters
 In initial Session and Connection setup, the access channel and

control channel carry the messages
• If L3 messages and RF indications are available, problems
usually can be identified
 Check the access parameters
• The range of powers should step through a range from the idle-
mode noise floor up to about 20 db above it
– A smaller power range can result in missed probes
– Check AP/BTS reverse receive levels, peak and average
looking for indications of interference
• Ensure sector size and acquisition search windows are
adequate

Long Setup Times and RF Failures
 Long setup times, often seen as bad latency in VOIP and PTT
applications, can result when extensive probing occurs. This can
be the result of:
• RF reverse link interference
– External interference or rogue terminals
• Incorrect Access Parameters, having mobiles start probing at
low RF levels

Forward Link
Throughput Optimization

PDSN/Foreign Agent
Forward Link Scheduler
data R-P User

Interface
Buffer Data Rate
AP
PCF SEL EVM
t1
EVDO device
DO-RNC or FMS
 The main bottleneck is forward link available C/I and timeslots

 Each connected data User has a buffer in the PDSN/PCF complex
• When data is in the buffer, a “Data Ready” message is sent to the mobile
• The mobile then requests data from the desired sector on DRC/DSC
• The scheduler fairly divides slots among the active users
• “Proportional Fairness” applies
applies, always trying to give slots to each user
when that user’s link is better than average
• This substantially improves (40%+) both user and overall sector
throughput
• QOS (Quality of Service) rules also may be implemented, giving
preference to some users and some types of traffic

So S L O W ! ! Where’s My Data?!!
Backbone
Internet Network
EVDO RF Environment
Data Environment
PDSN Authentication
Home Agent
Accounting
•Coverage Holes
SEL EVM •Missing Neighbors
•Rev Pwr Ovld
t1 •Search Windows
Island Cells
•Island
IP D
DO-RNC
DO RNC / FMS Wireless
EVDO IOS PPP •Slow Handoff Mobile Device
 Some sessions have long latency and slow throughput

 Where is the problem? Anywhere between user and distant host:
• Is the mobile user’s data device mis-configured and/or congested?
• Is the AP congested, with few timeslots available?
• Poor RF environment,, causing g low rates and p
packet retransmission?
• Congestion in the local IP network (PCU, R-P, PDSN FA)?
• Congestion in the wireless operator’s backbone (‘OSSN’) network?
• Congestion in the PDSN HA?
• Congestion in the outside-world internet or Private IP network?
• Is the distant host congested, with long response times?
Finding Causes of Latency and Low Throughput
Test Test Test
Server Server Server
Backbone
Internet Network
EVDO RF Environment
Data Environment
PDSN Authentication
Home Agent
BTS •Pilot Pollution
v SEL CE •Fwd Pwr Ovld
t1 •Rev Pwr Ovld
•Search Windows
IP D
DO-RNC
DO RNC or FMS Wireless
•Island
I l dC Cells
ll
Mobile Device
 IP network performance can be measured using test servers

 Problems between mobile a local test server? The problem is local
• check RF conditions, stats: poor environment, SCH blocking?
• if the RF is clean, investigate BSC/PCU/R-P/PDSN-FA
 Local results OK
OK, problems accessing test server at PDSNPDSN-HA?
HA?
• problem is narrowed to backbone network, or PDSN-HA
 Results OK even through test server at PDSN-HA
• then
th th the problem
bl iis iin th
the public
bli llayers b
beyond.
d

Pinging Network Nodes to test Latency
 Simple “ping” commands from a command prompt line can detect
latency to and from particular servers
 Notice in the example, the first ping in the second attempt is
delayed more than others because the user was in dormant state
immediately prior, and a new connection had to be established

Using Tracert to Identify Delays
 The command “Tracert” at the command prompt will show the

identification and timing details of all non-firewalled
non firewalled nodes in the
network.

Forward Link Speed – No Dominant Server
 When there are many y equal

q servers, the C/I values of each server
are very poor and the forward link data speed from any of the
servers is very low
 This is the equivalent of “pilot pollution” in 1xRTT CDMA

Forward Link Speed – Very Dominant Server
 When one server stands head and shoulders above the other
sectors, its C/I is excellent and it can deliver very fast data
 However, if this server is overloaded with traffic, the mobile has no
alternative sector and the blocking will have a large impact

Forward Link Speed – Three Equal Servers
 When three sectors are approximately equally strong, their C/I

values
l are medium-to-poor.
di t A off these
Any th sectors
t could
ld d
deliver
li
data to the mobile at 307 Kb/s
 If one of these sectors becomes saturated and puts up its “DRC
Lock” bit against our mobile, the mobile could choose another
Lock
sector and avoid most blocking

Single User Traffic Statistics from Invex
 The average bit speed obtained by a mobile on downlink is affected by:

• RF conditions (this determines the instantaneous bit speed when a
slot is being sent to the mobile)
• Fraction of time during which the mobile “owns” the sector
 The above tabulation from the Andrew Invex tool shows the bit speed for
all slots to the mobile, allowing independent identification of RF problems
and traffic congestion effects due to others

Reverse Link
Throughput Optimization

Reverse Link Throughput Considerations
 Reverse Link throughput is influenced by

• Instantaneous RF conditions, dictating selected packet speed
and Hybrid-ARQ speedup, if any
• Congestion on the reverse link,
link as indicated by the sector
limiting the available slots from the mobile
• T-1 or other backhaul limitation, imposing ceilings on the
number of reverse p packets which can be uploaded
p from an AP
to the AN

Reverse Link Rate Control in Rev. A
 Discussion of Reverse Link rate control algorithm

• Dependence on Observed C/I of serving sector
• Bucket control mechanism
 Available packet scheduling parameters vary by manufacturer
 Extreme sensitivity to reverse link interference, like 1xRTT

QOS
Quality of Service

Quality of Service
 Quality of Service allows a network to provide differentiated

service to specific groups of users and/or for specific types of
traffic, so that users may meet their service needs while efficiently
using the resources of the network
 In EV-DO Rev. A, QOS is provided by the Enhanced Multi-Flow
Packet Application (EMPA)
(EMPA). Its main features:
• Spectral Efficiency
– Packet-based RLP-EMPA enables packet streams to carry
packets between AT and AN.
p
– Packet-based RLP reduces the overhead.
• Single VoIP frames can fit in single air-interface frames, by
using Robust Header Compression (RoHC).
• Inter-RNC Handoff
– Two parallel routes can be terminated at different RNCs
simultaneously, reducing interruption in VOIP and other
sensitive applications during inter
inter-RNC
RNC handoff.
handoff

QOS Control Techniques in 1xEV-DO
 Admission Control at the RAN

• The 1xEV-DO Rev. A RAN mayy perform
p admission control techniques
q
to maintain QoS
• Admission Control – A technique to “block” or deny an incoming QoS
flow request in order to satisfy QoS requirements with a very high
p
probability
y
 Forward Link QoS via Scheduler
• Forward Link QoS at the AN may be achieved via the scheduler.
• QoS and serving of users is based on:
– QoS flow requirements – Delay bound, throughput, and reliability.
– Priority of application flow
– Best Effort, Assured Forwarding, Expedited Forwarding
– AND/OR Priority Level 0 – 7
– Amount of data in Forward link queue
– Channel conditions of AT
– Number of active users in the sector

Priority Levels and Classes
 A priority level (0-7) is

assigned to each
application’s traffic
 The QOS algorithm
uses these levels in
prioritizing traffic
 An operator usually
sets these priorities
b
based d on itits own
business philosophy,
with help from its
network vendor

Forward Link Queue Management
 Proportional Fairness (effectively “Best Effort”)

• Exploit channel quality variations (multi
(multi-user
user diversity).
diversity)
• Average user throughput is proportional to DRC.
• As load increases, users suffer even degradation.
 Delay Fairness (QoS flows)
• Different priorities for different users/traffic.
• User’s traffic delayy varies inverselyy with channel conditions
• Uneven degradation occurs, based on user priority

Forward Congestion Avoidance: RED
 Random Early Detection (RED)

• Typically used when there is a single queue buffer
• Drops incoming packets based on current load statistics
• Advantage: Gracefully slows a congested link
 Works as a function of three parameters:
• Min Thresh
• Max Thresh
• Drop Probability.
 Intended for undifferentiated “Best Effort” type traffic, or on highly
congested
g links

Forward Congestion Avoidance: WRED
 Weighted Random Early Detection (WRED)

• Same philosophy as RED,
RED but with IP precedence
precedence.
• Selectively discards lower priority traffic during congestion.
• Attempts to predict and manage congestion.
 WRED-Considered parameters for each traffic class or weight:
• Min thresh
• Max thresh
• Drop probability
 Drops more packets from large users than small.
 Appropriate for Assured Forwarding kinds of data flows

Rev. A Reverse Link MAC Enhancements
 EV-DO Rev. A provides many reverse link performance and QOS

enhancements
• Hybrid ARQ on Reverse Link Physical and MAC layer
• Early termination and new higher and lower payload sizes
• Larger payload sizes give higher rates for delay
delay-tolerant
tolerant
applications
• Lower latencies through smaller payload sizes for delay-
sensitive applications
• Comprehensive AN control of AT resource allocation
• QoS sensitive resource allocation across multiple data flows
• Independent
I d d t trade-off
t d ff per flflow b
between
t capacity
it and d latency
l t
• Improved Reverse link stability at higher occupancy

Reverse Link QOS
 In 1xEV-DO Rev A, Reverse link QoS is maintained by the AT and

the RTCMAC Algorithm.
 QoS and flow transmissions are based on:
• QoS requirements of flow
• Payload size,
size delay bound
bound, etc
etc.
• RTCMAC flow priority functions
• Amount of data in Reverse link queues
• Channel conditions of AT and sector loading
 Available T2P resources

Intra-AT QOS
 An AT may have multiple MAC flows existing at the same time (for
example, live video, live audio, and text
• MAC parameters control allocation for each of the flows
• Performance of delay-sensitive flows is not degraded by
competition from delay-tolerant
delay tolerant data flows
flows.
• MAC flow behavior is uniform whether within the flows of one
AT or across many ATs.
• In general
general, AT resource allocation is the sum of its MAC flow
allocations.

QOS Implementation for 1xEV-DO ATs
 Rel. 0 ATs support

• Default protocols,
protocols Default Packet Application
 Rev. A ATs support
• default protocols
• Multi-Flow Packet Application
• Enhanced Multi-Flow Packet Application
 Different make and model ATs support
pp different OSI applications:
pp
• VoIP, VT, PTx, etc.
 QoS requirements are expressed in terms of
• Latency,
Latency Throughput,
Throughput Reliability,
Reliability and Jitter

FlowProfile IDs
 ATs support specific FlowProfile IDs

• Flow Profiles must be mutually defined on AT and RAN
• All the flows within a application should be bundled to maintain
application integrity
 Traffic Flow Templates Information Elements (TFTs IE) specify the
QOS filter requirements
• TFTIEs must be coordinated with PDSN and AAA.

Traffic Flow Templates
 Traffic Flow Template

• The PDSN needs to know the A-10 A 10 connection (main or
auxiliary) on which to put the IP packets.
 Traffic Flow Templates convey:
• A-10
A 10 to IP flow mapping information
• QOS Parameters at the IP Layer
• Actions to take on IP packets
 This group of information is called a Packet Filter

Background and Introduction To 1xEV-DO Technology Background and Introduction To 1xEV-DO Technology To 1xEV-DO Technology To 1xEV-DO Technology

Uploaded by

Copyright:

Available Formats

Background and Introduction To 1xEV-DO Technology Background and Introduction To 1xEV-DO Technology To 1xEV-DO Technology To 1xEV-DO Technology

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Background and Introduction To 1xEV-DO Technology Background and Introduction To 1xEV-DO Technology To 1xEV-DO Technology To 1xEV-DO Technology

Uploaded by

Copyright:

Available Formats

Module 340

Background and Introduction

10-2008 (c)2008 Scott Baxter and Associates 1

10-2008 (c)2008 Scott Baxter and Associates 2

 Total Worldwide Wireless customers surpassed total worldwide landline

10-2008 (c)2008 Scott Baxter and Associates 3

10-2008 (c)2008 Scott Baxter and Associates 4

10-2008 (c)2008 Scott Baxter and Associates 5

3100 – 800 DL WCDMA 0

1xRTT RC4 EDGE TD-SCDMA

10-2008 (c)2008 Scott Baxter and Associates 6

10-2008 (c)2008 Scott Baxter and Associates 7

 1xEV, “1x Evolution”, is a family of alternative QPSK

10-2008 (c)2008 Scott Baxter and Associates 8

10-2008 (c)2008 Scott Baxter and Associates 9

First •Packet IP Integrated

10-2008 (c)2008 Scott Baxter and Associates 10

10-2008 (c)2008 Scott Baxter and Associates 11

 To satisfy the ITU 3G vision of four radio environments:

10-2008 (c)2008 Scott Baxter and Associates 12

 RF channel conditions change much faster than 1xRTT can track

10-2008 (c)2008 Scott Baxter and Associates 13

Thoughput: 0.15 or 0.31 Mb/s max, 0.06 Mb/s typ.

10-2008 (c)2008 Scott Baxter and Associates 16

 Each forward traffic channel subpacket is only 1

10-2008 (c)2008 Scott Baxter and Associates 17

10-2008 (c)2008 Scott Baxter and Associates 18

messages – with some delay

10-2008 (c)2008 Scott Baxter and Associates 19

IS-95: VARIABLE POWER

10-2008 (c)2008 Scott Baxter and Associates 20

IS-95, IS-2000, 1xRTT EV-DO

10-2008 (c)2008 Scott Baxter and Associates 21

10-2008 (c)2008 Scott Baxter and Associates 22

 All members of the CDMA family - IS-95, IS-95B,

10-2008 (c)2008 Scott Baxter and Associates 23

400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips

 The main “cargo” in a slot is the DATA being sent to a user

10-2008 (c)2008 Scott Baxter and Associates 24

400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips

 Sometimes there may be no data waiting to be sent on a sector’s

400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips

 Two Half-Slots make a Slot

10-2008 (c)2008 Scott Baxter and Associates 26

That’s a lot of slots!

10-2008 (c)2008 Scott Baxter and Associates 27

400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips

 Slots make Frames and Frames make Control Channel Cycles!

10-2008 (c)2008 Scott Baxter and Associates 28

1 Frame = 16 slots – 32k chips – 26-2/3 ms

10-2008 (c)2008 Scott Baxter and Associates 29

1 Slot 1 Slot 1 Slot 1 Slot

 The mobile transmits sub

10-2008 (c)2008 Scott Baxter and Associates 30

W MAC Primary Pilot W016

 The channels are not continuous like ordinary 1xRTT CDMA

10-2008 (c)2008 Scott Baxter and Associates 31

W264 Rev Activity ATs If the reverse link loading is

Each connected AT has MAC channel: