1xEVDOrevA

10-2007 EV-DO rev A - 11xEV-DO Rev. A (c)2007 Scott Baxter and Nortel

1xEV-DO Rev. A Networks1xEV-DO Rev. A Networks


Outline

The Place of EVDO in the 3G Family1xEV-DO Physical LayerForward Link Data Transmission during Established ConnectionHybrid ARQ: Repeat-Request ProtocolEV-DO Operation FundamentalsChannels and Layer-3 MessagesAccess ProceduresAn EV-DO ConnectionAccess Terminals and Route Updates1xEV-DO Network Architecture, Simple and Mobile IPBackhaul ConsiderationsKey Performance IndicatorsOptimizing the Air Interface1xEV-DO / 1xRTT Interoperability Standards Documents


Introduction:How EVDO Fits In the 3G Family

Introduction:How EVDO Fits In the 3G Family


A Quick Survey of Wireless Data Technologies

This summary is a work-in-progress, tracking latest experiences and reports from all the high-tier (provider-network-oriented) 2G and 3G wireless data technologiesHave actual experiences to share, latest announced details, or corrections to the above? Email to [email protected]. Thanks for your comments!

AMPS Cellular9.6 – 4.8 kb/s

w/modem

IS-136 TDMA19.2 – 9.6 kb/s

GSM CSD9.6 – 4.8 kb/s

GSM HSCSD32 – 19.2 kb/s

IDEN19.2 – 19.2 kb/s

IS-9514.4 – 9.6 kb/s

IS-95B64 -32 kb/s

CDPD19.2 – 4.8 kb/sdiscontinued

GPRS40 – 30 kb/s DL

15 kb/s UL

EDGE200 - 90 kb/s DL

45 kb/s UL

1xRTT RC3153.6 – 80 kb/s

1xRTT RC4307.2 – 160 kb/s

1xEV-DO 02400 – 600 DL153.6 – 76 UL

1xEV-DO A3100 – 800 DL1800 – 600 UL

WCDMA 0384 – 250 kb/s

WCDMA 12000 - 800 kb/s

WCDMA HSDPA12000 – 6000 kb/s

Flarion OFDM1500 – 900 kb/s

TD-SCDMAIn Development

Mobitex9.6 – 4.8 kb/s

obsolete

WI-MAX

US CDMA ETSI/GSM

CELLULAR

PAGING

MISC/NEW1xEV-DV

5000 - 1200 DL307 - 153 UL


Channel Structure of 1xEV-DO vs. 1xRTTCHANNEL STRUCTURE

IS-95 and 1xRTT• many simultaneous users, each

with steady forward and reverse traffic channels

• transmissions arranged, requested, confirmed by layer-3 messages – with some delay……

1xEV-DO -- Very Different:• Forward Link goes to one user at a

time – like TDMA!• users are rapidly time-multiplexed,

each receives fair share of available sector time

• instant preference given to user with ideal receiving conditions, to maximize average throughput

• transmissions arranged and requested via steady MAC-layer walsh streams – very immediate!

BTS

IS-95 AND 1xRTTMany users’ simultaneous forward

and reverse traffic channelsW0W32W1W17W25W41

W3

W53

PILOTSYNC

PAGINGF-FCH1F-FCH2F-FCH3

F-SCH

F-FCH4

AP

1xEV-DO AP (Access Point)

ATs (Access Terminals)

1xEV-DO Forward Link


Power Management of 1xEV-DO vs. 1xRTT

POWER MANAGEMENTIS-95 and 1xRTT:

• sectors adjust each user’s channel power to maintain a preset target FER

1xEV-DO IS-856:• sectors always operate at

maximum power• sector output is time-

multiplexed, with only one user served at any instant

• The transmission data rate is set to the maximum speed the user can receive at that moment

PILOT

PAGINGSYNC

Maximum Sector Transmit Power

User 123

45 5 5678

time

pow

er

IS-95: VARIABLE POWER TO MAINTAIN USER FER

time

pow

er

1xEV-DO: MAX POWER ALWAYS,DATA RATE OPTIMIZED


1xEV-DO Physical Layer:Channels in Time and Codes

1xEV-DO Physical Layer:Channels in Time and Codes


1xEV-DO Transmission TimingForward Link

All members of the CDMA family - IS-95, IS-95B, 1xRTT, 1xEV-DO and 1xEV-DV transmit “Frames”

• 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– each 1xEV-DO frame is divided into

1/16ths, called “slots”The Slot is the basic timing unit of 1xEV-DO forward link transmission

• Each slot is directed toward somebody and holds a subpacket of information for them

• Some slots are used to carry 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 like in TDMA or GSM; instead, each slot or small string of slots is dynamically addressed to whoever needs it at the moment

One 1xEV-DO Frame

One Slot

One Cycle of PN Short Code


What’s In a Forward Link Slot?

The main “cargo” in a slot is the DATA being sent to a userBut all users need to get continuous timing and administrative information, even when all the slots are going to somebody elseTwice 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

SLOT DATA

MA

CPI

LOT

MA

C

DATA DATA

MA

CPI

LOT

MA

C

DATA

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

½ Slot – 1024 chips ½ Slot – 1024 chips


empty empty empty empty

What if there’s No Data to Send?

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 MAC and PILOT must be transmitted!!• New and existing mobiles on this sector and surrounding

sectors need to monitor the relative strength of all the sectorsand decide which one to use 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, even in an empty slot

SLOT

MA

CPI

LOT

MA

C

MA

CPI

LOT

MA

C




Slot

Forward Link Slots and Frames

SLOT

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

DATA

MA

CPI

LOT

MA

C

DATA DATA

MA

CPI

LOT

MA

C

DATA



Two Half-Slots make a Slot16 Slots make a frame


Forward Link 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 Control Channel packetsThe last half of the first frame, and all of the remaining 15 frames, have their slots available for ordinary use transmitting subpackets to users


16 Frames – 524k chips – 426-2/3 ms

CONTROLCHANNEL USER(S) DATA CHANNEL

16-FRAMECONTROL CHANNEL

CYCLE

Slot

That’s a lot of slots!16 x 16 = 256


Forward Link Frame and Slot Structure:“Big Picture” Summary

Slots make Frames and Frames make Control Channel Cycles!

SLOT


16 Frames – 524k chips – 426-2/3 ms

CONTROLCHANNEL USER(S) DATA CHANNEL

16-FRAMECONTROL CHANNEL

CYCLE

DATA

MA

CPI

LOT

MA

C

DATA DATA

MA

CPI

LOT

MA

C

DATA




Reverse Link Frame and Slot Structure:“Big Picture” Summary

Reverse Link frames are the same length as forward link framesThe mobile does not include separate MAC and Pilot 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

SLOT


DATA


1 Subframeholds

1 SubpacketSubframe Subframe Subframe


Rev. A Reverse Channel Sub-Frame Structure

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

RRI

ACK DSC ACK DSC ACK DSC ACK DSC

DATA CHANNEL

DRC CHANNEL

AUXILIARY PILOT CHANNELPILOT CHANNEL

1 Sub-Frame

1 Slot 1 Slot 1 Slot 1 Slot


The 1xEV-DO Rev. 0 Channels

These channels are NOT CONTINUOUS like IS-95 or 1xRTT!• They are made up of SLOTS carrying data subpackets to individual

users or control channel subpackets for everyone to monitor• Regardless of who “owns” a SLOT, the slot also carries two small

generic bursts containing PILOT and MAC information everyone canmonitor

IN THE WORLD OF CODES

Sect

or h

as a

Sho

rt P

N O

ffset

just

like

IS-9

5A

ccessLong PN

offsetPublic or Private

Long PN offset

ACCESS

FORWARD CHANNELS

AccessPoint(AP)

REVERSE CHANNELS

TRAFFIC

Pilot

Data

Pilot

DataACK

Pilot

ControlTraffic

MAC

MAC FORWARD

Rev ActivityDRCLockRPC

DRC

RRI

W 64

W264

W064

Wx16

Wx16

W48

W24

W816

W016

W24

W016

MA

C

W0 W4W1 W5W2 W6W3 W7

AccessTerminal

(UserTerminal)

Walshcode

Walshcode

Access Channelfor session setup

from Idle Mode

Traffic Channelas used duringa data session


Functions of Rev. 0 Forward Channels

Sect

or h

as a

Sho

rt P

N O

ffset

FORWARD CHANNELSPilot

ControlTraffic

MACRev ActivityDRCLockRPCW 64

W264

W064

Wx16

Wx16

MA

C

AccessPoint(AP)

•Access terminals watch the Pilot to select the strongest sector and choose burst speeds

•The Reverse Activity Channel tells ATs If the reverse link loading is too high, requiring rate reduction

•Each AT with open connection has a MAC channel including DRCLock and RPC (Reverse Power Control) muxed using the same MAC index 5-63.

•The Control channel carries overhead messages for idle ATs but can also carry user traffic

•Traffic channels carry user data to one user at a time

IN THE WORLD OF TIME

DATA

MA

CPI

LOT

MA

C

DATA DATA

MA

CPI

LOT

MA

C

DATA

400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips½ Slot – 1024 chips ½ Slot – 1024 chips

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

AP


Functions of Rev. 0 Reverse Channels

Access

Long PN offset

Public or PrivateLong PN

offset

ACCESS

REVERSE CHANNELS

Pilot

Data

Pilot

DataACK

MAC DRC

RRI

W48

W24

W816

W016

W24

W016

W0 W4W1 W5W2 W6W3 W7

AccessTerminal

(UserTerminal)

•The Pilot is used as a preamble during access probes

•Data channel during access carries mobile requests

•Pilot during traffic channel allows synchronous detection and also carries the RRI channel

•RRI reverse rate indicator tells the AP the AT’s desired rate for reverse link data channel

•DRC Data Rate Control channel asks a specific sector to transmit to the AT at a specific rate

•ACK channel allows AT to signal successful reception of a packet

•DATA channel during traffic carries the AT’s traffic bits

TRAFFIC


EV-DO Rev. A Channels

The channels are not continuous like ordinary 1xRTT CDMANotice the differences between the MAC channels and the Rev. 0 MAC channels – these are the heart of the Rev. 0/A differences

IN THE WORLD OF CODES

Sect

or h

as a

Sho

rt P

N O

ffset

just

like

IS-9

5A

ccessLong PN

offsetPublic or Private

Long PN offset

ACCESS

FORWARD CHANNELS

AccessPoint(AP)

REVERSE CHANNELS

TRAFFIC

Pilot

Data

Primary Pilot

DataACK

Pilot

Control

Traffic

MAC

MAC

FORWARD

Rev ActivityDRCLockRPC

RRI

W 64

W264

W064

Wx16

Wx16

W1232

W12

W416

W016

W24

W016

MA

C

AccessTerminal

(UserTerminal)

Walshcode

Walshcode


from Idle Mode


ARQ Auxiliary Pilot

DRCDSC

W2832

W816

W1232


Sect

or h

as a

Sho

rt P

N O

ffset

just

like

IS-9

5

FORWARDCHANNELS

AccessPoint(AP)

Pilot

Control

Traffic

MAC

Rev ActivityDRCLockRPCW 64

W264

W064

Wx16

Wx16

MA

C

Walshcode

ARQ

Functions of Rev. A Forward Channels

•Access terminals watch the Pilot to select the strongest sector and choose burst speeds

•The Reverse Activity Channel tells ATs If the reverse link loading is too high, requiring rate reduction

Each connected AT has MAC channel:• DRCLock indication if sector busy• RPC (Reverse Power Control) • ARQ to halt reverse link subpackets as soon as complete packet is recovered

•The Control channel carries overhead messages for idle ATs but can also carry user traffic

•Traffic channels carry user data to one user at a time

DATA

MA

CPI

LOT

MA

C

DATA DATA

MA

CPI

LOT

MA

C

DATA

400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips½ Slot – 1024 chips ½ Slot – 1024 chips

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

AP


• Auxiliary Pilot on traffic channel allows synchronous detection during high data rates

Access

Long PN offset

Public or PrivateLong PN

offsetACCESS

REVERSE CHANNELS

TRAFFIC

Pilot

Data

Primary Pilot

DataACK

MAC RRI

W24

W016

AccessTerminal

(UserTerminal)

Walshcode


from Idle Mode


Auxiliary Pilot

DRCDSC

Functions of Rev. A Reverse Channels•The Pilot is used as a preamble during access probes

•Data channel during access carries mobile requests

• Primary Pilot on traffic channel allows synchronous detection and also carries the RRI channel

•RRI reverse rate indicator tells AP what rate is being sent by AT

•DRC Data Rate Control channel tells desired downlink speed

•ACK channel allows AT to signal successful reception of a packet

•DATA channel during traffic carries the AT’s traffic bits

•DSC Data Source Control channel tells which sector will send burst

W1232

W12

W416

W016

W2832

W816

W1232


The Rev. 0 MAC Index

Each active user on a sector is assigned a unique 7-bit MAC index (64 MACs possible)Each data packet begins with a preamble, using the MAC index of the intended recipientFive values of MAC indices are reserved for “multi-user” packets

• packets intended for reception by a group– for example, control channels

• mobiles may have individual MAC indices AND be simultaneously in various groups

• this “trick” keeps payload size low even for transmissions to groups

MAC Channel Use Preamble UseNot Used Not UsedNot Used 76.8 kbps CCHNot Used 38.4 kbps CCH

RA Channel Not UsedAvailable for RPC

and DRCLockChannel

Transmissions

Available forForward

Traffic ChannelTransmissions

MACIndex0 and 1

234

5-63

MA

CIn

dex

Wal

sh C

ode

Phas

e

32 16 I

MA

CIn

dex

Wal

sh C

ode

Phas

e

1 32 Q34 17 I 3 33 Q36 18 I 5 34 Q38 19 I 7 35 Q40 20 I 9 36 Q42 21 I 11 37 Q44 22 I 13 38 Q46 23 I 15 39 Q48 24 I 17 40 Q50 25 I 19 41 Q52 26 I 21 42 Q54 27 I 23 43 Q56 28 I 25 44 Q58 29 I 27 45 Q60 30 I 29 46 Q62 31 I 31 47 Q

MA

CIn

dex

Wal

sh C

ode

Phas

e

0 0 I2 1 I4 2 I6 3 I8 4 I

10 5 I12 6 I14 7 I16 8 I18 9 I20 10 I22 11 I24 12 I26 13 I28 14 I30 15 I

MA

CIn

dex

Wal

sh C

ode

Phas

e

33 48 Q35 49 Q37 50 Q39 51 Q41 52 Q43 53 Q45 54 Q47 55 Q49 56 Q51 57 Q53 58 Q55 59 Q57 60 Q59 61 Q61 62 Q63 63 Q

AP


Rev. A MAC Index Values and Their Uses

114 MAC indices are available for regular single-user packets3 MAC indices are earmarked for control channel packets5 MAC indices are reserved for mult-user packets1 MAC index is reserved for broadcast packets, or single-users4 MAC indices are not used due to conflicts with multiplexing patterns


Rev. A MAC Index and I/Q Channel Contents


Forward Link Data TransmissionDuring an Established ConnectionForward Link Data Transmission

During an Established Connection


Transmission of a Packet over EV-DO

AP

Data Ready

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” message to let the AT know it has data waiting.

Data from PDSN for the Mobile

MP3, web page, or other content


Transmission of a Packet over EV-DO

AP

Data Ready

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” message to let the AT know it has data waiting.

The AT quickly determines which of its active sectors is the strongest. On the AT’s DRC channel it asks that sector to send it a packet at speed “DRC Index 5”.

The mobile’s choice, DRC Index 5, determines everything:The raw bit speed is 307.2 kb/s.The packet will have 2048 bits.There will be 4 subpackets (in slots 4 apart).The first subpacket will begin with a 128 chip preamble.

DRC: 5

DRCIndex Slots Preamble

ChipsPayload

BitsRawkb/s

0x0 n/a n/a 0 null rate0x1 16 1024 1024 38.40x2 8 512 1024 76.80x3 4 256 1024 153.60x4 2 128 1024 307.20x5 4 128 2048 307.20x6 1 64 1024 614.40x7 2 64 2048 614.40x8 2 64 3072 921.60x9 1 64 2048 1,228.80xa 2 64 4096 1,228.80xb 1 64 3072 1,843.20xc 1 64 4096 2,457.60xd 2 64 5120 1,536.00xe 1 64 5120 3,072.0

C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3

in Rev. Ain Rev. A

Modu-lationQPSKQPSKQPSKQPSKQPSKQPSKQPSKQPSKQPSKQPSK

16QAM8PSK

16QAM16QAM16QAM

Data from PDSN for the Mobile

MP3, web page, or other content


Transmission of a Packet over EV-DOData from PDSN for the Mobile

MP3, web page, or other content AP

Data Ready

DRC: 5

2048 bits

Interleaver

+ D+

+D D

++ +

+

+ D+

+D D

++ +

+

Turbo Coder

PACKET

Symbols

Using the specifications for the mobile’s requested DRC index, the correct-size packet of bits is fed into the turbo coder and the right number of symbols are created.


ChipsPayload

BitsRawkb/s


C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3

in Rev. Ain Rev. A


16QAM8PSK

16QAM16QAM16QAM




Data Ready

DRC: 5

2048 bits

Interleaver

+ D+

+D D

++ +

+

+ D+

+D D

++ +

+

Turbo Coder

Block Interleaver

PACKET

Symbols


To guard against bursty errors in transmission, the symbols are completely “stirred up” in a block interleaver.


ChipsPayload

BitsRawkb/s


C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3

in Rev. Ain Rev. A


16QAM8PSK

16QAM16QAM16QAM




Data Ready

DRC: 5

2048 bits

Interleaver

+ D+

+D D

++ +

+

+ D+

+D D

++ +

+

Turbo Coder

Block Interleaver

PACKET

Symbols

Interleaved Symbols


To guard against bursty errors in transmission, the symbols are completely “stirred up” in a block interleaver.

The re-ordered stream of symbols is now ready to transmit.


ChipsPayload

BitsRawkb/s


C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3

in Rev. Ain Rev. A


16QAM8PSK

16QAM16QAM16QAM




Data Ready

DRC: 5

2048 bits

Interleaver

+ D+

+D D

++ +

+

+ D+

+D D

++ +

+

Turbo Coder

Block Interleaver

PACKET

Symbols

Interleaved Symbols

Using the specifications for the mobile’s requested DRC index, the correct-size packet of bits is fed into the turbo coder and the right number of symbols are created.To guard against bursty errors in transmission, the symbols are completely “stirred up” in a block interleaver.The re-ordered stream of symbols is now ready to transmit. The symbols are divided into the correct number of subpackets, which will occupy the same number of transmission slots, spaced four apart.It’s up to the AP to decide when it will start transmitting the stream, taking into account any other pending subpackets for other users, and “proportional fairness”. Su

bpac

ket

1

Subp

acke

t 2

Subp

acke

t 3

Subp

acke

t 4


ChipsPayload

BitsRawkb/s


C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3

in Rev. Ain Rev. A


16QAM8PSK

16QAM16QAM16QAM




Data Ready

DRC: 5

2048 bits

1 2 3 4

Interleaver

+ D+

+D D

++ +

+

+ D+

+D D

++ +

+

Turbo Coder

Block Interleaver

PACKET

SLOTS

Symbols

Interleaved Symbols

When the AP is ready, the first subpacket is actually transmitted in a slot.

The first subpacket begins with a preamble carrying the user’s MAC index, so the user knows this is the start of its sequence of subpackets, and how many subpackets are in the sequence..

The user keeps collecting subpackets until either:

1) it has been able to reverse-turbo decode the packet contents early, or

2) the whole schedule of subpackets has been transmitted.

Subpackets


ChipsPayload

BitsRawkb/s


C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3

in Rev. Ain Rev. A


16QAM8PSK

16QAM16QAM16QAM


Hybrid ARQ:Hybrid Repeat-Request Protocol

Hybrid ARQ:Hybrid Repeat-Request Protocol


The Hybrid ARQ Process

In 1xRTT, retransmission protocols typically work at the link layer

• Radio Link Protocol (RLP)– communicates using

signaling packets– lost data packets aren’t

recognized and are discarded at the decoder

This method is slow and wasteful!

SYSTEM

MAClayer

Physicallayer

RLP RadioLink Protocol

Application layer

LAC layer

MAClayer

Physicallayer

RLP RadioLink Protocol

CDMA2000 1xRTT

F-FCHR-FCH

Application layer

LAC layer

Application layer

Stream layer

Session layer

Connection layer

Security layer

MAC layer

Physicallayer

HARQprotocol

AP Access Point AT Access TerminalCDMA2000 1xEV-DO

Physicallayer

HARQprotocol

R-ACK

Application layer

Stream layer

Session layer

Connection layer

Security layer

MAC layer

F-TFC repeats

In 1xEV-DO, RLP functions are replicated at the physical layer

• HARQ Hybrid Repeat Request Protocol– fast physical layer ACK bits– Chase Combining of multiple

repeats– unneeded repeats pre-empted

by positive ACKThis 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’s 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


Forward Link Multislot ARQ, Normal Termination

AT selects sector, sends request for dataAP starts sending next packet, one subpacket at a timeAfter each subpacket, AT either NAKs or AKs on ACK channelIn this example,

• AP transmits all 4 scheduled subpackets of packet #0 before the AT is finally able to decode correctly and send AK

• then the AP can begin packet #1, first subpacket

One Slot

UserPacket

Subpacket

A00

diff.user

A01

A02

A03

A10

R-DRC

F-Traffic

R-ACK

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

NAK NAK NAK AK!

AP

AT1/2 Slotoffset

deco

dedecid

e

prepa

reNAK

deco

de

decide

prepa

reNAK

deco

de

decide

prepa

reNAK

deco

de

decide

prepa

reNAK


Forward Link Multislot ARQ, Early Termination

AT selects sector, sends request for dataAP starts sending next packet, one subpacket at a timeAfter each subpacket, AT either NAKs or AKs on ACK channelIn this example,

• AT is able to successfully decode packet #0 after receiving only the first two subpackets

• AT sends ACK. AP now continues with first subpacket of packet #1

NAK NAK AK!

UserPacket

Subpacket

A00

diff.user

A01

A10

A11

A20

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

AK!

AP

AT

One Slot

UserPacket

Subpacket

A00

diff.user

A01

R-DRC

F-Traffic

R-ACK

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

diff.user

NAK NAK AK!

1/2 Slotoffset

deco

dedecid

e

prepa

reNAK

deco

de

decide

prepa

reNAK

deco

de

decide

prepa

reNAK

deco

de

decide

prepa

reNAK


Packet 0Subpackets

Multiple ARQ Instances

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 instancesPackets 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

0 1 2 3Data

PacketsEncoding

andScrambling

Inter-leaving

bits symbols

PacketSubpacket

00

1.0

01

02

03

2.0

3.0

1.1

2.1

3.1

1.2

2.2

3.2

1.3

2.3

3.3

One Slot

Forward

ChannelTraffic

A


Packet 0Subpackets






0 1 2 3Data

PacketsEncoding

andScrambling

Inter-leaving

bits symbols

PacketSubpacket

00

1.0

01

02

03

2.0

3.0

1.1

2.1

3.1

1.2

2.2

3.2

1.3

2.3

3.3

One Slot

Forward

ChannelTraffic

Packet 1Subpackets

0 1 2 3

A


Packet 0Subpackets






0 1 2 3Data

PacketsEncoding

andScrambling

Inter-leaving

bits symbols

PacketSubpacket

00

1.0

01

02

03

2.0

3.0

1.1

2.1

3.1

1.2

2.2

3.2

1.3

2.3

3.3

One Slot

Forward

ChannelTraffic

Packet 1Subpackets

0 1 2 3

Packet 2Subpackets

0 1 2 3

A


Packet 0Subpackets






0 1 2 3Data

PacketsEncoding

andScrambling

Inter-leaving

bits symbols

PacketSubpacket

00

1.0

01

02

03

2.0

3.0

1.1

2.1

3.1

1.2

2.2

3.2

1.3

2.3

3.3

One Slot

Forward

ChannelTraffic

Packet 1Subpackets

0 1 2 3

Packet 2Subpackets

0 1 2 3

Packet 3Subpackets

0 1 2 3


Link Rates and Packet/Subpacket Formats

The 1xEV-DO Rev. A reverse link has seven available modes offering higher speeds than available in Rev. 0

• Modulation formats are hybrids defined in the standardThe 1xEV-DO Rev. A forward has two available modes offering higher speeds than available in Rev. 0.

FORWARD LINK REVERSE LINKDRCIndex Slots Preamble

ChipsPayload

BitsRawkb/s


C/Idbn/a

-11.5-9.2-6.5-3.5-3.5-0.6-0.5+2.2+3.9+4.0+8.0+10.3+8.3+11.3


16QAM8PSK

16QAM16QAM16QAM

PayloadBits128256512768102415362048307240966144819212288

Modu-lation

B4B4B4B4B4Q4Q4Q2Q2

Q4Q2Q4Q2E4E2

Effective Rate kbps after:4 slots

184312289216144613072301531157638

19.28 slots

92161446130723015311576.857.638.419.29.6

12 slots

614409307

204.8153.6102.476.851.238.425.612.86.4

16 slots

460.8307.2230.4153.6115.276.857.638.428.819.29.64.8

Code Rate (repetition) after4 slots 8 slots 12 slots16 slots

1/5 1/5 1/5 1/51/5 1/5 1/5 1/51/4 1/5 1/5 1/53/8 1/5 1/5 1/51/2 1/4 1/5 1/53/8 1/5 1/5 1/51/2 1/4 1/5 1/53/8 1/5 1/5 1/51/2 1/4 1/5 1/51/2 1/4 1/5 1/52/3 1/3 2/9 1/52/3 1/3 1/3 1/3


Fundamentals of EV-DO Operation

Fundamentals of EV-DO Operation


Sessions and Connections

A 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 setting up 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.During one ongoing session, the terminal and network may open and close their connection many times.


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 Access Terminal Identifier

– Requested by the mobile at session setup and assigned by the system. Updated when crossing various boundaries

• ’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 Messagesin 1xEV-DO Connection ProcessingChannels and Layer-3 Messages

in 1xEV-DO Connection Processing


Most EV-DO basic packet flow and bursts are managed by layer-2 burstsLayer-3 messages are used to set up and control sessions, connections, location updating, and other higher-level tasksMessages include many fields of binary dataThe first byte of each message identifies message type: this allows the recipient to parse the contentsTo ensure no messages are missed, all 1xEV-DO messages bear serial numbers and important messages contain a bit requesting acknowledgmentMessages not promptly acknowledged are retransmitted several times. If not acknowledged, the sender may release the call

Dissecting a Layer-3 Message

MESSAGE ID

NUMPILOTS occurrences of this block:

FieldLength (in bits)

EXAMPLE: TRAFFIC CHANNEL

ASSIGNMENT MESSAGE

t

MESSAGE SEQUENCECHANNEL INCLUDED

CHANNELFRAME OFFSET

DRC LENGTHDRC CHANNEL GAINACK CHANNEL GAIN

NUM PILOTS

PILOT PNSOFTER HANDOFF

MAC INDEXDRC COVERRAB LENGTHRAB OFFSET

8810 or 2442664

916323


Message Vocabulary: Acquisition & Idle StatesPilot Channel

No Messages

Control Channel Access ChannelACAck

Access Parameters

BroadcastReverse Rate Limit

Connection Deny

Data Ready

Hardware ID Request

Keep Alive Request

Keep Alive Response

Location Assignment

Location Complete

Location Request

Location Notification

Page

Quick Config

Redirect

Route Update

SectorParameters

Session Close

Sync

Traffic ChannelAssignment

UATI Assignment

UATI Complete

UATI Request

Xoff Request

Xoff Response

Xon Request

Xon Response

Connection Request

Data Ready ACK

Hardware ID Response

Keep Alive Request

Keep Alive Response

Session Close

AccessPoint(AP)

AccessTerminal

(AN)

AccessNetwork

(AN)

Pilot ChannelNo Messages


Message Vocabulary: Connected State

Reverse Traffic ChannelForward Traffic Channel

ANKey Complete

Attribute Override

Configuration Complete

Configuration Request

Configuration Start

Connection Close

Data Ready

Hardware ID Request

Keep Alive Request

Keep Alive Response

Key Request

Location Assignment

Location Request

Nak

Neighbor List

Reset ACK

Reset ReportRoute UpdateRTC ACK

Session Close

Traffic ChannelAssignment

Traffic ChannelComplete

UATI Assignment UATI Complete

UnicastReverse Rate Limit

Xoff Request

Xoff ResponseXon Request

Xon Response

Configuration Response

Redirect

Reset

Data Ready ACK

Fixed Mode Enable

Fixed Mode X Off

Key Response

Location Complete

Location Notification

Nak

Hardware ID Response

Configuration Response

Connection Close

Keep Alive Request

Keep Alive Response

Reset ACK

Redirect

Reset

Session Close

AccessPoint(AP)

AccessTerminal(AN)

ATKey Complete

Attribute OverrideResponse

Configuration Complete

Configuration Request


All the Messages of 1xEV-DO Rev. 0

In 1xEV-DO, most call processing events are driven by messagesThe MAC channels in both directions are used to carry messages or specific Walsh Masks to convey commands and selection optionsMessages have priority and delivery protocolsEach message has a channel or channels on which it may be sentThe structure of all the 1xEV-DO messages is defined in IS-856

Name ID Inst. CC Syn SS AC FTC RTC SLP Addressing Pri.ACAck 0x00 1 CC Best Effort Unicast 10Access Parameters 0x01 1 CC Best Effort Broadcast 30ANKey Complete 0x02 1 FTC Reliable Unicast 40ATKey Complete 0x03 1 RTC Reliable Unicast 40Attribute Override 0x05 1 FTC Best Effort Unicast 40Attribute Override Response 0x06 1 RTC Best Effort Unicast 40Broadcast Reverse Rate Limit 0x01 1 CC Best Effort Broadcast 40Configuration Complete 0x00 1 FTC RTC Reliable Unicast 40Configuration Request 0x50 24 FTC RTC Reliable Unicast 40Configuration Response 0x51 24 FTC RTC Reliable Unicast 40Configuration Start 0x01 1 FTC Best Effort Unicast 40ConnectionClose 0x00 1 FTC RTC Best Effort Unicast 40ConnectionDeny 0x02 1 CC Best Effort Unicast 40ConnectionRequest 0x01 1 AC Best Effort Unicast 40DataReady 0x0b 1 CC FTC Best Effort Unicast 40DataReadyACK 0x0c 1 AC RTC Best Effort Unicast 40Fixed Mode Enable 0x00 1 RTC Best Effort Unicast 40Fixed Mode X off 0x01 1 RTC Best Effort Unicast 40Hardware ID Request 0x03 2 CC FTC Best Effort Unicast 40Hardware ID Response 0x04 1 AC RTC Rel, Best Eff Unicast 40Keep Alive Request 0x02 1 CC AC FTC RTC Best Effort Unicast 40Keep Alive Response 0x03 1 CC AC FTC RTC Best Effort Unicast 40Key Request 0x00 1 FTC Reliable Unicast 40Key Response 0x01 1 RTC Reliable Unicast 40Location Assignment 0x05 1 CC FTC Best Effort Unicast 40Location Complete 0x06 1 AC RTC Rel, Best Eff Unicast 40Location Request 0x03 1 CC FTC Best Effort Unicast 40Location Notification 0x04 1 AC RTC Rel, Best Eff Unicast 40Nak 0x00 1 FTC RTC Best Effort Unicast 50Neighbor List 0x00 1 FTC Reliable Unicast 40Page 0x00 1 SS Best Effort Unicast 20Quick Config 0x00 1 SS Best Effort Broadcast 10Redirect 0x00 1 CC FTC RTC Best Effort Bcst, Unicst 40Reset 0x00 2 FTC RTC Best Effort Unicast 40Reset ACK 0x01 2 FTC RTC Best Effort Unicast 40Reset Report 0x03 1 FTC Reliable Unicast 40Route Update 0x00 1 AC RTC Rel, Best Eff Unicast 20RTCAck 0x00 1 FTC Reliable Unicast 10SectorParameters 0x01 1 CC SYN SS Best Effort Broadcast 30Session Close 0x01 1 CC AC FTC RTC Best Effort Unicast 40Sync '00' 1 CC SYN SS Best Effort Broadcast 30Traffic Channel Assignment 0x01 1 CC FTC Rel, Best Eff Unicast 20Traffic Channel Complete 0x02 1 RTC Reliable Unicast 40UATI Assignment 0x01 1 CC FTC Best Effort Unicast 10UATI Complete 0x02 1 AC RTC Rel, Best Eff Unicast 10UATI Request 0x00 1 AC Best Effort Unicast 10Unicast Reverse Rate Limit 0x02 1 FTC Reliable Unicast 40Xoff Request 0x09 1 AC RTC Best Effort Unicast 40Xoff Response 0x0a 1 CC FTC Best Effort Unicast 40Xon Request 0x07 1 AC RTC Best Effort Unicast 40Xon Response 0x08 1 CC FTC Best Effort Unicast 40

Message Sent on Channels


Rev. ALayer-3

MessagesPart 1


Rev. ALayer-3

MessagesPart 2


EV-DO Rev. A Protocols and

Subtypes


Access ProceduresAccess 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 usersThis situation is much like the access channel in IS-95 and CDMA2000, although transmissions are shorter 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 probe is sent at an incrementally higher power, and only after waiting a randomly computed number of slotsIf 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 AccessCycleDurationPreambleLength frames of pilot only on I channel, followed byCapsuleLengthMax frames of data on Q channelProbes shall avoid falling on ReverseLinkSilence Duration period, which occurs starting on ReverseLinkSilenceInterval times.

• Typical values RLSD, RLSI currently 0 on most systemsATI used is


Access Channel and Reverse Traffic ChannelLong Code Masks

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 intending to transmit to it, and not mobiles on other sectors

During traffic channel operation, a mobile uses a long code maskunique to it

• long code offset is determined by the mobile’s permuted ATI

BIT 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 11 10 9 8 7 6 5 4 3 2 1 0

MIACMAC 1 1 Access CycleNumber Permuted (Color Code | Sector ID)

ACCESS CHANNEL LONG CODE MASK

BIT 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 11 10 9 8 7 6 5 4 3 2 1 0

MIRTCMAC 1 1 Permuted (ATILCM)

REVERSE TRAFFIC CHANNEL LONG CODE MASK

1 1 1 1 1 1 1 1


Structure of an Access Probe


An EV-DO ConnectionAn EV-DO Connection


EV-DO Connection

CONTROL

MAC

PILOT

TRAFFIC

AccessPoint(AP)

ACCESS

TRA

FFIC

PILOTRRIDRCACK

DATA

AccessTerminal

(AT)

Rake Receiver#1 PN168+0 W23

#2 PN168+2 W23

#3 PN168+9 W23

#4 PN168+5 W23

Pilot Searcher

CONNECTION REQUESTCONNECTION ROUTE UPDATE

MAC ACKTRAFFIC CHANNEL ASSIGNMENT

MAC RTC ACKTRAFFIC CHANNEL COMPLETE

XON REQUEST

NEIGHBOR LISTXON RESPONSE

ROUTE UPDATE

TRANSITION TO DORMANT

NULL MESSAGE

NULL MESSAGETRAFFIC CHANNEL ASSIGNMENT

TRAFFIC CHANNEL COMPLETENEIGHBOR LIST


System Acquisitionand SynchronizationSystem Acquisitionand Synchronization


Sync Message1/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:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 11 CONNECTION: Initialization State ProtocolMessage ID MessageID 0 SyncMaximum 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 Message1/32 chip counter 1/32 Chip Counter 16384 1.25 msec counter 1.25 msec Counter 0x03 2C BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 2 MAC: Access Channel MAC ProtocolMessage ID MessageID 1 Access ParametersAccess 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 APersistence APersistence 0 APersistence APersistence 0 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 Message1/32 chip counter 1/32 Chip Counter 3 1.25 msec counter 1.25 msec Counter 0xAD 2A BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 15 CONNECTION: Overhead Messages ProtocolMessage ID MessageID 0 Quick ConfigColor Code ColorCode 30 SectorID 24 LSBits SectorID24 53506 Sector Signature SectorSignature 0 Access Signature AccessSignature 0 Redirecting Terminals away from this Network Redirect 0 InvalidMax 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, much like the GSRM in CDMA2000


Gives full details of the sector configuration:ID, subnet mask, Lat/Lon,leapsec and local time offset, RL silence, Channels available, system type, band, channel#, neighbor list and search windows/offset

SectorParameters

Message

1/32 chip counter 1/32 Chip Counter 49156 1.25 msec counter 1.25 msec Counter 0xAD 2A BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 15 CONNECTION: Overhead Messages ProtocolMessage ID MessageID 1 Sector ParametersCountry Code Country Code 1

Sector Address Identifier SectorID

0x00 84 0A C0 00 00 00 00 00 0A 04 0C A8 00 D1 02

Subnet Mask SubnetMask 104 Sector Signature SectorSignature 0 Latitude Latitude 0 00D00'00.00NLongitude Longitude 0 000D00'00.00ERoute Update Radius RouteUpdateRadius 0 Leap Seconds LeapSeconds 13 Local Time Offset LocalTimeOffset 1568 26 Hours 08 MinutesReverse Link Silence Duration ReverseLinkSilenceDuration 0 0 FramesReverse Link Silence Period ReverseLinkSilencePeriod 0 Channels Available ChannelCount 1 System Type SystemType 0 System compliant to IS-856Band Class BandClass 1 1900MHz BandChannel Nbr ChannelNbr 25 Neighboring Sectors NeighborCount 14 Neighbor Pilot PN NeighborPilotPN 435 Neighbor Pilot PN NeighborPilotPN 48 Neighbor Pilot PN NeighborPilotPN 384 Neighbor Pilot PN NeighborPilotPN 285 Neighbor Pilot PN NeighborPilotPN 99 Neighbor Pilot PN NeighborPilotPN 321 Neighbor Pilot PN NeighborPilotPN 477 Neighbor Pilot PN NeighborPilotPN 291 Neighbor Pilot PN NeighborPilotPN 267 Neighbor Pilot PN NeighborPilotPN 309 Neighbor Pilot PN NeighborPilotPN 144 Neighbor Pilot PN NeighborPilotPN 159 Neighbor Pilot PN NeighborPilotPN 180 Neighbor Pilot PN NeighborPilotPN 132 Neighbor Channel Included NeighborChannelIncluded 0 Not IncludedNeighbor Search Window Size Included

Neighbor SearchWindowSizeIncluded 1 Included

Search Window Size (14) SearchWindowSize 8 60 ChipsNeighbor Search Window Offset Included

Neighbor SearchWindowOffsetIncluded 0 Not Included


Observing a ConnectionObserving a Connection


EV-DO Connection

CONTROL

MAC

PILOT

TRAFFIC

AccessPoint(AP)

ACCESS

TRA

FFIC

PILOTRRIDRCACK

DATA

AccessTerminal

(AT)

Rake Receiver#1 PN168+0 W23

#2 PN168+2 W23

#3 PN168+9 W23

#4 PN168+5 W23

Pilot Searcher

CONNECTION REQUESTCONNECTION ROUTE UPDATE

MAC ACKTRAFFIC CHANNEL ASSIGNMENT

MAC RTC ACKTRAFFIC CHANNEL COMPLETE

XON REQUEST

NEIGHBOR LISTXON RESPONSE

ROUTE UPDATE

TRANSITION TO DORMANT

NULL MESSAGE

NULL MESSAGETRAFFIC CHANNEL ASSIGNMENT

TRAFFIC CHANNEL COMPLETENEIGHBOR LIST


Connection: Route Update Message1/32 chip counter 1/32 Chip Counter 49157 1.25 msec counter 1.25 msec Counter 0x04 2C BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 0 Route UpdateMessage Seq MessageSeq 136 Pilot ReferencePilotPn 216 Pilot Ec/Io ReferencePilotStrength 4 0.6 dBKeep Reference Pilot ReferenceKeep 1 Nbr of Pilots NumPilots 0

The Route Update message is really a request for the sectors themobile wants to have in its active set

• much like the pilot strength measurement message in CDMA2000

In this example the mobile asks for only one sector, PN216• “Num Pilots 0” means there is just one pilot


Connection Request Message1/32 chip counter 1/32 Chip Counter 49152 1.25 msec counter 1.25 msec Counter 0x05 2C BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 12 CONNECTION: Idle State ProtocolMessage ID MessageID 1 Connection RequestTransaction ID TransactionID 32 Request Reason RequestReason 0 Access Terminal InitiatedReserved Reserved 0

The Connection Request Message is sent by an idle mobile to request entry into active state, creating or joining a sessionThis message is sent on the Access 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 Message1/32 chip counter 1/32 Chip Counter 49155 1.25 msec counter 1.25 msec Counter 0x9A 2C BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 2 MAC: Access Channel MAC ProtocolMessage 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 systemAfter hearing this message, the mobile knows it does not to sendany further repeated copies of its probe

• The mobile now waits for some form of channel assigmentmessage


Traffic Channel Assignment Message1/32 chip counter 1/32 Chip Counter 49153 1.25 msec counter 1.25 msec Counter 0xB1 2C BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 1 Traffic Channel AssignmentMessage Seq MessageSeq 0 Channel Included ChannelIncluded 0 Not IncludedFrame Offset FrameOffset 8 Slots used to Transmit 1 DRC Value DRCLength 1 2 SlotsDRC Channel Gain DRCChannelGain 61 30.5 dBAck Channel Gain AckChannelGain 8 4.0 dBNbr of Pilots NumPilots 1 Pilot Pn PilotPn 216 SofterHandoff SofterHandoff 0 MacIndex MacIndex 63 DRCCover DRCCover 1 RAB Length RABLength 2 32 SlotsRAB Offset RABOffset 0 0 Slots

The traffic channel assignment message tells the mobile the sectors in the active set and the MAC index for each, along withDRC length/cover, RAB length/offset, and frame offset


RTC Ack Message1/32 chip counter 1/32 Chip Counter 2 1.25 msec counter 1.25 msec Counter 0x00 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 0 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 4 MAC: Reverse Traffic Channel MAC ProtocolMessage 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 Message1/32 chip counter 1/32 Chip Counter 0 1.25 msec counter 1.25 msec Counter 0x19 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 0 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 2 Traffic Channel CompleteMessageSeq 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 Request1/32 chip counter 1/32 Chip Counter 1 1.25 msec counter 1.25 msec Counter 0x19 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 22 APPLICATION: Stream 2 ApplicationMessage ID MessageID 7 XonRequest

The mobile now requests that data transmission begin, by transmitting an X On request.


Null Message1/32 chip counter 1/32 Chip Counter 16387 1.25 msec counter 1.25 msec Counter 0x4C 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel Capsule

Null Message


Neighbor List Message1/32 chip counter 1/32 Chip Counter 32772 1.25 msec counter 1.25 msec Counter 0x4C 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 1 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 4 Neighbor ListNeighbor Count Count 14 Pilot PN PilotPN 435 Pilot PN PilotPN 48 Pilot PN PilotPN 384 Pilot PN PilotPN 285 Pilot PN PilotPN 99 Pilot PN PilotPN 321 Pilot PN PilotPN 477 Pilot PN PilotPN 291 Pilot PN PilotPN 267 Pilot PN PilotPN 309 Pilot PN PilotPN 144 Pilot PN PilotPN 159 Pilot PN PilotPN 180 Pilot PN PilotPN 132 Channel Included (14) ChannelIncluded 0 Not IncludedSearch Window Size Included SearchWindowSizeIncluded 1 IncludedSearch 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 Response1/32 chip counter 1/32 Chip Counter 16389 1.25 msec counter 1.25 msec Counter 0x4C 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 22 APPLICATION: Stream 2 ApplicationMessage ID MessageID 8 XonResponse

The system confirms whether it has implemented the X On request from the mobile


Route Update Message1/32 chip counter 1/32 Chip Counter 0 1.25 msec counter 1.25 msec Counter 0x59 2D BD D6 98 00 01/06/2006 01:46:28Frequency 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-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 1 Seq Nbr of Ack AckSeqNo 1 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 0 Route UpdateMessage Seq MessageSeq 137 Pilot ReferencePilotPn 216 Pilot Ec/Io ReferencePilotStrength 4 0.6 dBKeep Reference Pilot ReferenceKeep 1 Nbr of Pilots NumPilots 0

The mobile again reports its desired active pilot set• This can include additional desired sectors, or ask to drop

unwanted sectors• In this example, no change is being made


Broadcast Reverse Rate Limit

1/6/2006 1:46 Control Channel Broadcast

MAC: Reverse Broadcast Reverse Rate Limit

1/32 chip counter 1/32 Chip Counter 49152 1.25 msec counter 1.25 msec Counter 0xB8 2E BD D6 98 00 01/06/2006 01:46:29Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 4 MAC: Reverse Traffic Channel MAC ProtocolMessage ID MessageID 1 Broadcast Reverse Rate LimitRPC Count RPCCount 1 Rate Limit RateLimit 5 153.6 kbpsReserved 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 Message1/32 chip counter 1/32 Chip Counter 0 1.25 msec counter 1.25 msec Counter 0xD9 56 BD D6 98 00 01/06/2006 01:46:42Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 22 APPLICATION: Stream 2 ApplicationMessage ID MessageID 2 Nak

Mobile sends Application NAK message• This indicates the end of transmission


Nak Message1/32 chip counter 1/32 Chip Counter 32771 1.25 msec counter 1.25 msec Counter 0x20 47 BD D6 98 00 01/06/2006 01:46:37Frequency 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-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 22 APPLICATION: Stream 2 ApplicationMessage ID MessageID 2 Nak

System sends Application NAK message in response to the mobile• Mobile goes to idle state


Page Message1/32 chip counter 1/32 Chip Counter 49156 1.25 msec counter 1.25 msec Counter 0x12 C0 BF D6 98 00 01/06/2006 01:49:59Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 1 Synchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 12 CONNECTION: Idle State ProtocolMessage ID MessageID 0 Page

Forward control channel Page pages mobile to return to active state


AC Ack Message1/32 chip counter 1/32 Chip Counter 1 1.25 msec counter 1.25 msec Counter 0xA5 C0 BF D6 98 00 01/06/2006 01:49:59Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 2 MAC: Access Channel MAC ProtocolMessage ID MessageID 0 AC Ack

Control Channel MAC protocol sends this Access Channel AC Ackmessage to confirm the mobile’s probe has been heard


RTC Ack Message1/32 chip counter 1/32 Chip Counter 16384 1.25 msec counter 1.25 msec Counter 0x9B C1 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 0 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 4 MAC: Reverse Traffic Channel MAC ProtocolMessage ID MessageID 0 RTC Ack

Mobile acknowledges system


Traffic Channel Complete1/32 chip counter 1/32 Chip Counter 32771 1.25 msec counter 1.25 msec Counter 0xAD C1 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 0 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 2 Traffic Channel CompleteMessageSeq MessageSeq 0

Mobile acknowledges it is using the traffic channel


Null Message1/32 chip counter 1/32 Chip Counter 32770 1.25 msec counter 1.25 msec Counter 0xEB C1 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel Capsule

Forward Traffic Channel


Neighbor List Message1/32 chip counter 1/32 Chip Counter 49155 1.25 msec counter 1.25 msec Counter 0xEB C1 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 1 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 4 Neighbor ListNeighbor Count Count 9 Pilot PN PilotPN 267 Pilot PN PilotPN 495 Pilot PN PilotPN 180 Pilot PN PilotPN 99 Pilot PN PilotPN 312 Pilot PN PilotPN 45 Pilot PN PilotPN 159 Pilot PN PilotPN 132 Pilot PN PilotPN 63 Channel Included (9) ChannelIncluded 0 Not IncludedSearch Window Size Included SearchWindowSizeIncluded 1 IncludedSearch Window Size (9) SearchWindowSize 8 60 Chips

Search Window Offset Included SearchWindowOffsetIncluded 0 Not Included

Forward traffic channel


Route Update Message1/32 chip counter 1/32 Chip Counter 16387 1.25 msec counter 1.25 msec Counter 0x02 C2 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 1 Seq Nbr of Ack AckSeqNo 1 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 0 Route UpdateMessage Seq MessageSeq 141 Pilot ReferencePilotPn 12 Pilot Ec/Io ReferencePilotStrength 18 0.1 dBKeep Reference Pilot ReferenceKeep 1 Nbr of Pilots NumPilots 1 Pn Offset PilotPnPhase 31690 Channel Included ChannelIncluded 0 Not IncludedEc/Io PilotStrength 19 0.1 dBPilot 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 Message1/32 chip counter 1/32 Chip Counter 32769 1.25 msec counter 1.25 msec Counter 0x42 C2 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 1 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel Capsule

Forward traffic channel null message


Traffic Channel Assignment Message1/32 chip counter 1/32 Chip Counter 49157 1.25 msec counter 1.25 msec Counter 0x52 C2 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 2 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 1 Traffic Channel AssignmentMessage Seq MessageSeq 1 Channel Included ChannelIncluded 0 Not IncludedFrame Offset FrameOffset 7 Slots used to Transmit 1 DRC Value DRCLength 2 4 SlotsDRC Channel Gain DRCChannelGain 58 29.0 dBAck Channel Gain AckChannelGain 8 4.0 dBNbr of Pilots NumPilots 2 Pilot Pn PilotPn 12 SofterHandoff SofterHandoff 0 MacIndex MacIndex 63 DRCCover DRCCover 1 RAB Length RABLength 2 32 SlotsRAB Offset RABOffset 0 0 SlotsPilot Pn PilotPn 495 SofterHandoff SofterHandoff 0 MacIndex MacIndex 62 DRCCover DRCCover 2 RAB Length RABLength 2 32 SlotsRAB Offset RABOffset 0 0 Slots

Forward Traffic Channel. Note PNs, MAC indices, DRC and RA


Traffic Channel Complete1/32 chip counter 1/32 Chip Counter 49155 1.25 msec counter 1.25 msec Counter 0x57 C2 BF D6 98 00 01/06/2006 01:50:00Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 1 SeqNo is validAckSeqNo valid Ack AckSeqValid 1 AckSeqNo is validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 1 Signaling Link Protocol delivery mechanism was reliableSeq Nbr of Message SeqNo 2 Seq Nbr of Ack AckSeqNo 2 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 14 CONNECTION: Route Update ProtocolMessage ID MessageID 2 Traffic Channel CompleteMessageSeq MessageSeq 1

Reverse traffic channel


Connection Close Message1/32 chip counter 1/32 Chip Counter 32773 1.25 msec counter 1.25 msec Counter 0x5E C3 C0 D6 98 00 01/06/2006 01:51:22Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 255 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 13 CONNECTION: Connected State ProtocolMessage ID MessageID 0 Connection CloseReason for Close CloseReason 0 Normal CloseSuspend Enable SuspendEnable 0 Disabled

Forward traffic channel closes the connection• Note “Normal Close”, i.e., “this was my idea”


Connection Close Message1/32 chip counter 1/32 Chip Counter 16389 1.25 msec counter 1.25 msec Counter 0x73 C3 C0 D6 98 00 01/06/2006 01:51:22Frequency Band Band 1 CDMA Channel Nbr ChanNum 25 Pilot PN Offset PilotPN 12 Half-slot Reference Counter HSTR 0 IS-890 Signaling Is_hdris890 0 NOT IS-890Seq Nbr Valid SeqValid 0 SeqNo is not validAckSeqNo valid Ack AckSeqValid 0 AckSeqNo is not validPacket Fragmented Frgmented 0 Packet NOT fragmentedSignaling Link Protocol Reliable 0 Signaling Link Protocol delivery mechanism NOT reliableSeq Nbr of Message SeqNo 255 Seq Nbr of Ack AckSeqNo 0 Synchronous Control Channel SyncCCFlag 0 Asynchronous Control Channel CapsuleIn Configuration Bit InConfiguration 0 Type Type 13 CONNECTION: Connected State ProtocolMessage ID MessageID 0 Connection CloseReason for Close CloseReason 1 Close ReplySuspend 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 ArchitectureAnd Handoffs Route Updates

Access Terminal ArchitectureAnd Handoffs Route Updates


Block Diagram of an Access Terminal

ReceiverRF SectionIF, Detector

TransmitterRF Section

Digital Rake Receiver

Traffic CorrelatorPN xxx Walsh xx ΣTraffic CorrelatorPN xxx Walsh xxTraffic CorrelatorPN xxx Walsh xx

Pilot SearcherPN xxx Walsh 0

Viterbi Decoder,Convl. Decoder,Demultiplexer

CPUDuplexer

TransmitterDigital Section

Long Code Gen.

Open Loop Transmit Gain Adjust

Messages

Messages

Packets

Symbols

SymbolsChips

RF

RF

AGC

time-

alig

ned

su

mm

ing

pow

er

Traffic CorrelatorPN xxx Walsh xx

∆tcont

rol

bits

Conv orTurboCoder

UART


1xEV-DO Forward Link: AT Rake Receivers

Burst by burst, the Access Terminal asks for transmission from whichever Active sector it hears best, at the max speed it can successfully useUsing latest multipath data from its pilot searcher, the Access Terminal uses the combined outputs of the four traffic correlators (“rake fingers”)Each rake finger can be set to match any multipath component of the signalThe 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 us, never more than one at a time, so this capability isn’t needed or helpful in 1xEV-DO mode

Access TerminalRake Receiver

RF

PN Walsh

PN Walsh

PN Walsh

SearcherPN W=0

Σ userdata

Pilot Ec/Io

AP

AP

PN Walsh

ONE sector at a time!!


1xEV-DO Reverse Link: Soft Handoff

The AT uses the Route Update protocol to frequently update its preferences of which sectors it wants in its active setFrame-by-frame, all the sectors in the Active Set listen for the AT’s signalEach 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

AP

AP


RF

PN Walsh

PN Walsh

PN Walsh

SearcherPN W=0

Σ userdata

Pilot Ec/Io

PN Walsh

All “Active Set” sectorscan listen to the AT

DO-RNC chooses‘cleanest’ packet


??

1xEV-DO Route Update Mechanics

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

AP

DO-RNC

AP

Sel.


RFPN WalshPN WalshPN Walsh

SearcherPN W=0

Σ userdata

Pilot Ec/Io

PN Walsh


Route Update Pilot Management Rules

The Access Terminal considers pilots in sets• Active: sectors who listen and can transmit• Candidates: sectors AT requested, but not

yet approved by system to be active• Neighbors: pilots told to AT by system, as

nearby sectors to check• Remaining: any pilots used by system but

not already in the other sets (div. by PILOT_INC)

Access Terminal sends a Route Update Message to the system whenever:

• It transmits on the Access Channel• In idle state, it notices the serving sector is

far from the sector where last updated • In connected state, whenever it notices the

Handoff Parameters suggest a change

66

Remaining

ActiveCandidateNeighbor 20

PILOT SETS

AT m

ust support

PilotCompare

PilotAdd PilotDropPilotDropTimer

HANDOFF PARAMETERS

Dynamic Thresholds?SoftslopeAddInterceptDropInterceptNeighborMaxAge


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 requestThe message lists every Active pilot; if it doesn’t list it, it’s not approved as activeNotice the MAC index and DRC Cover so the access terminal knows how to request forward link bursts on the data rate control channel

Pilot PN Channel SrchWinSize SrchWinOffsetNeighbor Structure Maintained by the AT


1xEV-DO Network ArchitectureSimple IP and Mobile IP

1xEV-DO Network ArchitectureSimple IP and Mobile IP


CDMA Network for Circuit-Switched Voice Calls

The first commercial IS-95 CDMA systems provided only circuit-switched voice calls

t1t1 v CESEL

t1PSTN

BTS

(C)BSC/Access ManagerSwitch


CDMA 1xRTT Voice and Data Network

CDMA2000 1xRTT networks added two new capabilities:• 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-Radio Interface) to the heart of the BSC

The overall connection speed was still limited by the 1xRTT air interface

t1t1 v CESEL

t1

PDSNForeign Agent

PDSNHome Agent

BackboneNetworkInternet

VPNs

PSTN

AuthenticationAuthorization

AccountingAAA

BTS

(C)BSC/Access ManagerSwitch


1xEV-DO Overlaid On Existing 1xRTT Network

1xEV-DO requires faster resource management than 1x BSCs can give• 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 additionExisting PDSNs and backbone network are used with minor upgradingThe following sections show Lucent, Motorola, and Nortel’s specific solutions

t1t1 v CESEL

t1

PDSNForeign Agent

PDSNHome Agent


VPNs

PSTN


AccountingAAA

BTS

(C)BSC/Access ManagerSwitch CE

DORadio

NetworkController

DO-OMC


Simple IP Network Architecture

In a Simple IP network, the mobile is able to connect to the external packet networks directly through the PDSN attached to the local BSCThe IP address for the internet connection is assigned by the local PDSN from the pool of addresses available to itIf the mobile moves into a different network, the data session ends

• The mobile can establish an entirely new connection through the new network, if desired

t1t1 v CESEL

t1

R-P Interface

PDSN

PSTN

TAuthenticationAuthorizationAccountingAAA

CIRCUIT-SWITCHED VOICE TRAFFIC

BTS(C)BSC/Access Manager

Switch

WirelessMobile Device

POINT-TO-POINT PACKETS

FAST IP PACKET TRAFFIC

Simple IP•IP Based transport to data networks•Dynamic/static connection from local PDSN•No mobility beyond serving PDSN

InternetVPNs

rfFast!


Mobile IP in a Multi-Market Network

PSTN PSTN PSTN

RegionalDataCenter

Internet Private IPNetworks

Operator's Private Network

PDSNFA

SwitchBSC

PDSNFA

Switch

AccessMgr.

PDSN/FA

SwitchCBSC

PCF

RP Interface

RPRP

Voice Voice Voice

IP Data IP Data IP Data

HomeAgent Home

Agent

Nortel System Lucent System Motorola System

AAAServer


Mobile IP

Subscriber’s IP routing service is provided by a public IP networkMobile station is assigned a static IP address belonging to its Home AgentMobile can maintain the static IP address even for handoff between radio networks connected to separate PDSNs!Mobile IP capabilities will be especially important for mobiles on system boundaries

• Without Mobile IP roaming capability, data service for border-area mobiles will be erratic

MOBILE IPIMPLICATIONS

•Handoffs possible between PDSNs•Mobile can roam in the public IP network•Mobile termination is possible while Mobile is in dormant or active mode


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 packets just as if they were physically present at their home agent location.

158766

158767

158768

158769

158770

158771

158772

158773

158774

158775

158776

158778

158779

158780

158781

158782

158783

158784

158785

158786

158787

158788

158789

158790

158791

158792

158793

158794

158795

158796

158797

FedE

x

FedE

x

Secure TunnelingForward and Reverse

Encapsulation

HomeAgent

ForeignAgent

MobileUser

This box is the mobile user's

Postal address

Just likeHome!


Nortel 1xEV-DO ArchitectureNortel 1xEV-DO Architecture


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


A Typical Nortel CDMA2000 SystemProviding Only 1xRTT Voice, Data


A Typical Nortel CDMA2000 SystemProviding 1xEV-DO Only


Nortel Multiple Backhaul and Configuration Possibilities


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 performs all encoding/decoding of IP packets for transport on data-only network to the Data-Only Radio Network Controller (DO-RNC)

• One DOM supports up to a three-sector, one-carrier MetroCell AP

• Additional DOMs support additional carriers


Nortel’s DO-RNCThe 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 multiple 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 standard A10-A11 interfaces

• connects to MetroCell AP via dedicated IP backhaul network

DO-RNC is the peer of the access terminal for most over-the-air signaling protocols, including session and connection layers

Nortel DO-RNCData-Only

Radio Network Controller


Backhaul and Related Considerations

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 of roughly 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 throughput even without backhaul limitations

Solutions under study to relieve backhaul congestion include fiber-based ATM to the sites; multiple-T1s; sites linked by Cable Modems, and other methods


1xEV-DO Key Performance Indicators

1xEV-DO Key Performance Indicators


Latency

Latency can occur because of RF channel congestion or from IP network causes

• RF overload can delay availability of supplemental channels• IP network congestion can delay availability of packets

Ping and loopback tests with local PDSN and servers can identify whether problem is in backbone networkDoes latency correlate with independent evidence of RF congestion?

IP D

ata

Envir

onm

entEVDO RF Environment

EVDO IOS PPP

IP Data Environment

EVMSEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs T TSECURE TUNNELS


Accounting AAA

AP

DO RNC or FMS WirelessMobile Device

•Coverage Holes•Pilot Pollution•Missing Neighbors•Fwd Pwr Ovld•Rev Pwr Ovld•Search Windows•Island Cells•Slow Handoff


Throughput

Throughput can be limited by RF and IP causes• Traditional RF problems limit capacity of the channel• Congestion in the IP network can limit speed of data available

Does low throughput correlate with independent RF indicators?Does low throughput correlate with independent IP pings and tests?

IP D

ata

Envir

onm

entCDMA RF Environment

EVDO IOS PPP

IP Data Environment

EVMSEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




Accounting AAA

AP

DO RNC / FMS WirelessMobile Device



I0, Total AT Receive Power

AT Receive Power• usually expressed in dBm• measured derived from

handset IF AGC voltage• broadband, “unintelligent”

measurement: includes all RF in the carrier bandwidth regardless of source, notjust RF from serving BTS

-40

-90

-105

<<to

o w

eak

ove

rload

>>

I0

≈ x

LO

≈

RX Level(from AGC)

IFLNA

BW~30

MHz.

BW1.25MHz.

AT Receiver

R

R

R

S

Rake

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 in the signal after de-spreading, resulting in symbol errors, bit errors, packet errors, and other problems


Ec/Io and C/I

There are two main ways of expressing signal quality in 1xEV-DOC/I is the ratio of serving sector power to everything else

• C/I determines the forward data rate• mobiles measure C/I during the pilot

burst period, then from it decide what data rate to request on the DRC

Ec/Io is the ratio of one sector’s pilot power to the total received powerEc/Io and C/I are related, and one can be calculated from the otherEVDO Ec/Io is close to 0 db near a sector, and ranges down to -10 at a cell’s edgeEVDO C/I can be above +10 db near a sector, and -20 or lower at the edge

AP

Relationship ofC/I and Ec/IoFor EV-DO Signals

Io

Power fromServing Sector

I Interference Powerfrom other cells

EcC

0

mobile receive power

C/I, db-30 -20 -10 0 +10 +20

Ec/Io

, db

-30

-20

-10

0


-30

-25

-20

-15

-10

-5

0-30 -25 -20 -15 -10 -5 0 5 10 15 20

C/I, db

Ec/Io

, db

Relationship of Ec/Io and C/I in 1xEV-DO SystemsEc

/Io,

db C/I,

db

-0.04 20-0.14 15-0.17 14-0.21 13-0.27 12-0.33 11-0.41 10-0.51 9-0.64 8-0.79 7-0.97 6-1.19 5-1.46 4-1.76 3-2.12 2-2.54 1-3.01 0-3.54 -1-4.12 -2-4.76 -3-5.46 -4-6.97 -6-8.64 -8

-10.41 -10-12.27 -12


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

linkRF Blocking

• Due to MAC index, backhaul, or other congestion


Optimizing the RF Air InterfaceOptimizing 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-DO PN scanners and EV-DO terminals

• If a sector is in the active set of mobiles in places beyond theline joining its surrounding tier of sites, reduce its coverage

– 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 stableInitial neighbor lists can be generated from propagation prediction modeling or even from drive-test results with AT or PN scannersThe 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

and would 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 impossibleTiming errors affect pilot 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 the mobile expects

• 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 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

Search Window Offset01234567

Offset (PN chips)0

+0.5 x WindowSize

reserved

+1.0 x WindowSize+1.5 x WindowSize- 0.5 x WindowSize-1.0 x WindowSize-1.5 x WindowSize

-1.5 -1.0 -0.5 0.0 +0.5 +1.0 +1.5


Andrew’s Invex3G Tool

100 MB ethernet connection to PCthe eight card slots can hold receivers or dual-phone cardsthere’s also room for two internal PN scannersMultiple Invex units can be cascaded for multi-phone load-test applicationsCards are field-swappable -Users can reconfigure the unit in the field for different tasks without factory assistance


Overview of Field Tool IP Test Capabilities

Application Description Purpose

Raw Upload Uploads data with no overhead (no headers, no handshaking beyond the normal TCP handshaking)

Testing uplink throughput

Raw Download Downloads data with no overhead (no headers, no handshaking beyond the normal TCP handshaking.)

Testing downlink throughput

Raw Loopback A loopback (data is sent to the remote server which returns the same data) application with no overhead (no headers, no handshaking beyond the normal TCP handshaking.)

Simultaneous exercise of the uplink and downlink

Ping (ICMP ECHO) Ping does not use the TCP protocol, but rather uses the connectionless and “unreliable” ICMP protocol. Sends small echo request packets to a remote server, which responds with an echo reply.

Determining round-trip-time between the user and the remote server, as well as general link integrity (by counting the number of missing echo reply packets).

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 sites allow users to upload files as “attachments”).

If Raw Upload is unavailable, testing uplink throughput.

FTP GET A standard FTP file download. Many file downloads on the Internet use FTP.

If Raw Download and HTTP GET are unavailable, testing downlink throughput; modeling typical customer use.

FTP PUT A FTP file upload. The file is generated by the Invex3G platform and sent to the server.

If Raw Upload and HTTP POST are unavailable, testing uplink throughput

Mail GET (POP3) Retrieves all the mail for a given mailbox (e-mail address) from an e-mail server. Note: does not delete the e-mail messages from the mailbox.

Modeling typical customer use.

Wait Waits a specified amount of time. Testing idle timers, timeouts, etc.


Agilent Drive-Test Tools

Agilent offers Drive-Test tools• Serial interfaces for up to four

CDMA phones or cards• A very flexible digital receiver

with several modesPN Scanner

• Fast, GPS-locked, can scan two carrier frequencies

Spectrum Analyzer• Can scan entire 800 or 1900

mHz. BandsBase-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

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

Forward Link Throughput Optimization


Forward Link Scheduler

The main bottleneck is forward link available C/I and timeslotsEach 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, 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

EVMSELt1

R-PInterface

PDSN/Foreign Agent

AP

DO-RNC or FMSEVDO device

data

Buffer

UserData Rate

PCF


So S L O W ! ! Where’s My Data?!!

Some sessions have long latency and slow throughputWhere 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 low rates and 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?

IP D

ata

Envir

onm


EVDO IOS PPP

IP Data Environment

EVMSEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




AccountingAAA

AP

DO-RNC / FMS WirelessMobile Device



Finding Causes of Latency and Low Throughput

IP network performance can be measured using test serversProblems 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, problems accessing test server at PDSN-HA?• problem is narrowed to backbone network, or PDSN-HA

Results OK even through test server at PDSN-HA• then the problem is in the public layers beyond.

IP D

ata

Envir

onm


EVDO IOS PPP

IP Data Environment

v CESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




AccountingAAA

BTS

DO-RNC or FMS WirelessMobile Device


TestServer

TestServer

TestServer


Forward Link Speed – No Dominant Server

When there are many equal servers, the C/I values of each serverare very poor and the forward link data speed from any of the servers is very lowThis 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 dataHowever, 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 are medium-to-poor. Any of these sectors could deliver data to the mobile at 307 Kb/sIf one of these sectors becomes saturated and puts up its “DRC Lock” bit against our mobile, the mobile could choose another 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 LinkThroughput Optimization

Reverse LinkThroughput 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, 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 packets which can be uploaded from an AP to the AN


Reverse Link Rate Control in Rev. A

Discussion of Reverse Link rate control algorithm• Bucket control mechanism

Available packet scheduling parameters vary by manufacturerExtreme sensitivity to reverse link interference, like 1xRTT


1xEV-DO / 1xRTT Interoperability

1xEV-DO / 1xRTT Interoperability


1xEV-DO/1xRTT Interoperability

The CDMA2000 1xEV-DO Rev. 0 Standard IS-856 makes no provision for any kind of handoff to or from any other technologyDriven by Operator interest, a “Hybrid” mode has been developed to provide some types of handoff functions to the best extent possibleHybrid Mode

• is a mobile only function – neither the EV nor 1xRTT network knows anything about it

• is a proprietary feature with vendor-specific implementation• has no standard-defined RF “triggers”; no “hooks”

In the 1xEV rev. A standard, some new features are provided• Using the CDMA2000 Circuit Services Negotiation Protocol,

the 1xEV control channel can carry 1xRTT pages too• this and other changes will eventually 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” 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, it can be closed and then re-originated on the other system

• In some cases this can be accomplished automatically without the end-user’s awareness – in other cases, the user must manually reconnect


Hybrid Mode Transition Scenarios

DO systems will be Implemented in Several Configurations• 1:1 overlays in busy core areas• 1:1 or 1:N overlays in less dense areas

Many EV>1x and 1x>EV transition events may occur as a user transitions from area to areaInitial system acquisition is also involved as a user activates their AT in different locationsThese transitions are dependent on the Hybrid mode implementation in the ATThe following pages show some possible transitions assuming Mobile IP and AT Hybrid Mode are implemented

EV-DO, F21xRTT, F1

1:2 Deployment 1:1 Deployment1:1 Deployment


1xRTT / 1xEV-DO Hybrid Idle Mode

1xRTT/1xEV-DO Hybrid Mode• depends on being able to hear pages on both

systems – 1xRTT and 1xEV-DO• is possible because of slotted mode paging• 1xRTT and 1xEV-DO paging slots do not occur

simultaneously• mobile can monitor both

During 1xEV-DO traffic operation, the hybrid-aware mobile can still keep monitoring 1xRTT paging channelDuring 1xRTT traffic operation, the hybrid-aware mobile is unable to break away; 1xRTT traffic operation is continuous

• no opportunity to see 1xEV-DO signalThis hybrid Idle mode capability is the foundation for all 1xRTT/1xEV mode transfers

• the network does not trigger any transfers

1xR

TT

Act

ive

1xR

TT

Idle

1xEV

-DO

Idle

1xEV

-DO

A

ctiv

e

IdleMode

IdleMode

HybridMode


Hybrid Dual-Mode Idle Operation1xRTT / 1xEV-DO Paging Interoperability

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 timeHow is it possible for the mobile to monitor both at the same time?

• The paging timeslots of the two technologies are staggeredThree of the 16 timeslots in 1xRTT conflict with the control channel slots of 1xEV-DO

• However, conflicts can be avoided by page repetition, a standardfeature in systems of both technologies

16-frame Control Channel Cycle16 slots of 26-2/3 ms = 426-2/3 ms

1xRTT Minimum Slot Cycle Index: 16 slots of 80 ms each = 48 26-2./3 ms frames1xRTT Minimum Slot Cycle Index: 16 slots of 80 ms each = 48 26-2./3 ms frames

16-frame Control Channel Cycle16 slots of 26-2/3 ms = 426-2/3 ms

LONGEST POSSIBLEPACKET

DRC 16 Subpackets


1xR

TT

Act

ive

1xR

TT

Idle

1xEV

-DO

Idle

1xEV

-DO

A

ctiv

eInitial System Acquisition by Hybrid Mobile

IdleMode

Acquire1xRTTSystem

driven byPRL

Registerwith

1xRTTNetwork

Acquire1xEV-DOSystem

driven byPRL

Classical 1xRTTIdle Mode

no, can’t see EV

VoicePage!

1xRTTVoiceCall

IdleMode

Release

when 1xEV-DO is NOT Available

After entering this state, the mobile will search for EV-DO

at intervals (typ. 3 min)


1xR

TT

Act

ive

1xR

TT

Idle

1xEV

-DO

Idle

1xEV

-DO

A

ctiv

eInitial System Acquisition by Hybrid Mobile

IdleMode

Acquire1xRTTSystem

driven byPRL

Registerwith

1xRTTNetwork

Acquire1xEV-DOSystem

driven byPRL

Set Up orRe-establish

1xEVDOData

Session

yes, found EV

IdleMode

IdleMode

HybridMode

1xEVTraffic

AT DataReady!

AN DataPage!

DataConnectionClosed

VoicePage!

1xEVTraffic

1xRTTVoiceCall

IdleMode

HybridMode

IdleMode

IdleMode

HybridMode

Release

when 1xEV-DO is Available

interruptedduring1xRTT

voice call

Triggers:


In-Traffic: EV-DO Fade with 1xRTT Available1x

RTT

A

ctiv

e1x

RTT

Id

le1x

EV-D

OId

le1x

EV-D

O

Act

ive

Traffic Mode,Data Transfer

IdleMode

Fade

Fade

CloseConnection

ReestablishCall

PPPResync

MIPRegistr.

ResumeData Transfer

TransferFinished

Dormant/Idle

Dormant/Idle

DOSystem

Acquired SameDO

Subnet?

Get NewUATI

no

PPPResync

MIPRegistr.


AT data ready

AN data ready


1xR

TT

Act

ive

1xR

TT

Idle

1xEV

-DO

Idle

1xEV

-DO

A

ctiv

eTransition In-Traffic: Lost EV-DO and 1xRTT

Fade

IdleMode

Fade

Fade

CloseConnection

LostSignal!!

Use 1x PRL,Search for

1xRTTNo

SignalFound!!


DO PRL,Search for

DO

FoundNew DOSignal!!

IdleMode

Same DOSubnet?

Get NewUATI

No

IdleModeYes

Use 1x PRL,Search for

1xRTT

No Signal Found!!

IdleMode

HybridMode

No 1x Signal,Continue EV

Operation

Set Up orRe-establish

1xEVDOData

Session

1xEVTraffic

AT DataReady!

AN DataPage!

Triggers:

IdleMode


Dormant Session, EV-DO Lost > 1xRTT > 1xEV-DO1x

RTT

A

ctiv

e1x

RTT

Id

le1x

EV-D

OId

le1x

EV-D

O

Act

ive

IdleMode

Fade

Fade


DO PRL,Search for

DO

FoundNew DOSignal!!

Same DOSubnet?

Get NewUATI

No

IdleModeYes

IdleMode

HybridMode

IdleMode

Data Finished,Call Dormant

CoverageEdge

NoSignal

Found!!

PPPResync

MIPRegistr.

IdleMode

DO PRL,DO

Available?

PPPResync

MIPRegistr.

DO PRL,DO

Available?No

SignalFound!!

NoSignal

Found!!

DO PRL,DO

Available?


EVDO StandardAnd Standards Documents

EVDO StandardAnd 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. 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 Rev. A Standard: More application-driven 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

IS-856 defines the behavior of three main entities:

• Access Terminal• Air Interface• Access Network

The behavior of the system is defined in layers

• the layers provide a simple, logical foundation for performing functions and applications

• Specific applications, functions and protocols exist in each layer

• Each layer is defined in specific chapters of the standard

Architecture Reference Model

AccessTerminal Access Network

Sector

AirInterface

Protocol Architecture

Physical

Mac

Security

Connection

Session

Stream

Application •Default Signaling Application •Default Packet Application

•Stream 0: Default Signaling•Stream 1, 2, 3: not used by default

•Address Mgt.•State Mtce.

•Protocol Negotiation•Protocol Configuration

•Air Link Connection Establishment•Air Link Connection Maintenance

•Authentication•Encryption

•Defines procedures to transmit and receive over the physical layer

•Modulation.•Encoding.

•Channel Structure•Frequency, Power

IS-856ChapterLayer Protocol & Function

234

5

6

7

8

9


Stack Layers and their Default ProtocolsDefaultSignalingApplication

DefaultPacketApplication

Physicallayer

Maclayer

Securitylayer

Connectionlayer

Sessionlayer

Streamlayer

Applicationlayer

ReverseTraffic ChannelMAC Protocol

Access ChannelMAC Protocol

ForwardTraffic ChannelMAC Protocol

Control ChannelMAC Protocol

Physical Layer Protocol

EncryptionProtocol

AuthenticationProtocol

Key ExchangeProtocol

SecurityProtocol

OverheadMessagesProtocol

Route UpdateProtocol

PacketConsolidation

Protocol

ConnectedState

ProtocolIdle StateProtocol

InitializationState

Protocol

Air LinkManagement

Protocol

SessionConfiguration

Protocol

AddressManagement

Protocol

SessionManagement

Protocol

Stream Protocol

Location UpdateProtocol

Radio LinkProtocol

Signaling LinkProtocol

Flow ControlProtocol

SignalingNetworkProtocol


1xEV-DO Protocol Layers and Packet Encapsulation

Applicaton Layer Packet

Header

Packet

Header

Payload

Physical Layer Payload

Payload Header Pad

Payload

Header Trailer

Application Layer

Stream Layer

Session Layer

Connection Layer

Encryption Layer

Authentication Layer

Security Layer

PayloadHeader Trailer


MAC Layer

Packet

Payload

MAC Header

MAC Payload

MACTrailer


Physical Layer


EV-DO Rev. A Improvements

Support of enhanced reverse link• One channel per mobile station• Mobile station is required to transmit at 1.84 Mbps peak rate• Shorter frames• Higher capacity

Forward link enhancements• – Higher peak data rate of 3.1 Mbps• – Smaller packet sizes (128, 256, and 512 bits)• – Multi-user packets

Improved slotted mode• Shorter slot cycle for reduced activation time• 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 channelEnhanced multi-flow packet data applicationReverse link MAC enhancements for QoSData Source Control (DSC) for seamless cell selectionEnhanced Generic Attribute Update protocol


Non-Default ProtocolsMulti-Flow Packet Application CDMA2000 Circuit Services

Notification Application

Physicallayer

Maclayer

Securitylayer

Connectionlayer

Sessionlayer

Streamlayer

Applicationlayer

Subtype 1 Physical Layer Protocol

SHA-1 AuthenticationProtocol

Enhanced Idle State Protocol

Generic MultimodeCapability Discovery Protocol

Generic Virtual Stream Protocol

CDMA2000 Circuit ServicesNegotiation ProtocolLocation Update

Protocol

Data over Signal-Ing Protocol

Flow ControlProtocol

Radio LinkProtocol

DH Key ExchangeProtocol

Generic SecurityProtocol

Subtype 2 Physical Layer Protocol

Subtype-1 ReverseTrafic ChannelMAC Protocol

EnhancedAccess Channel

MAC Protocol

Enhanced ForwardTraffic ChannelMAC Protocol

Subtype 3 ReverseTraffic ChannelMAC Protocol

Subtype-2 ReverseTraffic ChannelMAC Protocol

EnhancedControl Channel

MAC Protocol

1xEVDOrevA

Documents

Transcript of 1xEVDOrevA