1xEVDO: 1x Evolution Data Optimized - 3G CDMA Wireless Data

1xEVDO
1x Evolution Data Optimized - 3G CDMA Wireless Data
John Burgess
June 24, 2010
Introduction
1xEVDO: Whats in a name?
Wireless Evolution
Compare/Contrast to CDMA
1xEVDO Architecture (ALU-style)
1xEVDO Protocol Layers
2 | 1xEVDO Overview | June 2010
All Rights Reserved Alcatel-Lucent 2010
1xEVDO: What is in a Name?

1xEVDO = 1x Evolution Data Only IS-856-0, or Rel. 0 Air Interface
Also known internally as HDR, or High Data Rate
AKA HRPD, or High Rate Packet Data
1xEVDO = 1x Evolution Data Optimized IS-856-A, or Rev. A
There is also a Rev B, that allows the split of forward channel
transmissions across multiple DO carriers.
Ongoing work in standards for Rev C, DO Advanced
Other flavors:
Evolved HRPD (eHRPD) access to a different packet core network
eXtended HRPD (xHRPD) HRPD over satellite
Alphabet Soup
AAA = Authentication, Authorization and Accounting
AN = Access Network (base station) Also, RAN: Radio Access Network
AT = Access Terminal (mobile)
BTS = Base Transceiver Station
CDMA = Code Division Multiple Access
GRE = Generic Routing Encapsulation
IP = Internet Protocol
PCF = Packet Control Function
PDSN = Packet Data Serving Node
PPP = Point to Point Protocol
QoS = Quality of Service
RATI = Random Access Terminal Identifier
RLP = Radio Link Protocol
RNC = Radio Network Controller
RoHC = Robust Header Compression
SSIR = Session State Information Record Also ESSIR, Extended SSIR
TCP = Transmission Control Protocol
TDMA = Time Division Multiple Access
UATI = Unicast Access Terminal Identifier
UDP = User Datagram Protocol
Wireless Evolution (Digital)

1xEVDO
Rev A, B
From CL8306-2.0-IG.en.UL, 4/2004

Compare/Contrast with IS-2000 CDMA

Same frequency usage per channel
Share amplifiers and filter cards
Thus the 1x moniker
IS-2000 uses codes to orthogonalize users signals

Same bit rates used for all circuit voice channels
IS-856 uses TDMA techniques in the Forward channel

Optimized for Data transmissions
Can pick user with best configuration to get the best rates, since conditions change
Rev A allows multiple smaller channels for VoIP applications
Reverse channels are very similar

CDMA has a circuit-based data flow
1xEVDO has an IP-based data flow
Designed from the ground up to be data-centric
Data Rates
Data
Direction
Data Rates for Technology Type (kbps)

CDMA 2000
1xEVDO,
Rel. 0
1xEVDO,
Rev. A
1xEVDO,
Rev. B
Forward
153.6k*
2.4M
3.1M
4.9M-14.7M
Reverse
153.6k
153.6k
1.8M
1.8M-5.4M
*307.2 is possible, but not implemented on the ALU system

The maximum rate depends on the number of carriers simultaneously used;
ALU uses up to 3 carriers, eventually
1xEVDO Architecture/Interfaces
RNC
Incl. PCF
Ethernet
Backhaul
Network
BTS
(HCS)
Idle Handoffs/DO Session

Transfer (A13)
Radio Network to Packet Data
Network (R-P) (A10)
RNC
Incl. PCF
Authentication (A12)
AAA
PDSN
PCF-PDSN
Signaling (A11)
AT
Data
Signaling
IP Network
A10/A11 = GRE
Generic Routing
Encapsulation
1xEVDO Data Protocol

AN Access Network
RNC (HDR Controller)
AAA
Call
Control
BTS
(HDR Modem)
AT
Airlink
Frame
Selector
Router
RLP
PCF
100
Base T
T1/E1
A10
Interface
PPP
PPP
RLP GRE
TCP
UDP
TCP
UDP
IP
PHY
PDSN
IP
RLP
MAC HDLC
PHY
T1
IP
HDLC
T1
IP
802.3
IP
GRE
IP
IP
802.3 802.3
1xEVDO Air Interface Protocols

Fixed
End
System
Internet
TCP
UDP
IP
MAC
Ethernet
802.3
IP
TCP
UDP
IP
1xEVDO Default Protocol Layers (Data & Signaling)

(DPA)
Other Packet
Applications
(Rev A): MFPA,
EMFPA
+DOS
Application Layer
Default Signaling Application Protocols
Personalities
Default Packet Application Protocols (DPA) Rel. 0
Multi-Flow Packet Application Protocols (MFPA) Rev. A
Enhanced MFPA Protocols (EMFPA) Rev. A
Multi-Link MFPA Protocols (MLMFPA) Rev. B
Signaling Messages
Default Signaling Application Protocol processes signaling messages
Signaling Network Protocol (SNP)
Message transmission services for signaling messages
SNP Header indicates the protocol that sends/receives the message
Message Id is unique only within a protocol
Signaling Link Protocol (SLP)

Fragmentation (SLP-F) for signaling messages (never used by ALU)
Reliable and best effort delivery (SLP-D) for signaling messages
Standards specify Reliable or Best Effort delivery for each message
Reliable Transmission
Retransmit if no ACK
SLP-D provides duplicate detection and retransmission for reliable messages
Best Effort Transmission

No acknowledgement is needed
Default Packet Application (DPA) Personality

Radio Link Protocol (RLP)
Provides in-order delivery of RLP packets, retransmission and duplicate detection
Forms an RLP packet by adding a 22 bit sequence number
NAK-based retransmission (request retransmission once)
NAK abort timer is 500ms
Packet Location Update Protocol (LUP)

Provides location update procedures for mobility management
Flow Control Protocol

Provides flow control for sending or receiving RLP packets
Multi-Flow Packet Application (MFPA, EMFPA & MLMFPA) Personality

Same RLP & LUP as the Default Packet
Application
Multi-Flow Packet Application Control
Protocol
Provides flow control for sending or
receiving RLP packets
RLP header is different than that used in
DPA
Allows multiple flows:
Multiple IP flows
Multiple RLP flows
Single Stream
Enhanced MFPA (EMFPA)

Adds enhancements needed for VoIP
ROHC
shorter RLP header
PPP free (allow other higher layer
protocols)
Out of order delivery
Multi-Link Multi-Flow Packet

Application (MLMFPA Rev. B)
Like EMFPA, but allows split of data stream
across carriers
Multiple RTCMAC flows
Introduces Quality of Service (QoS)

Adds Data Over Signaling (DOS)
Stream Layer
Multiplexing of application streams for one AT
Stream 0 is for Signaling
Packet Application is negotiated for use over Stream 2
DPA
MFPA
EMFPA
MLMFPA
Session Layer
Session Management Protocol
Provides control for activation of other Session Layer protocols
Provides Keep Alive and Session Close functions
Address Management Protocol

Provides UATI assignment and maintenance procedures
Session Configuration Protocol

Provisions and negotiates the configuration parameters for the protocols used by AT
and AN
Session Layer
What is a Session?
CDMA did not have the concept of session; had dial number instead
Multiple types of sessions
PPP session
R-P session (RNC-PDSN)
DO session This is the session we are talking about
Can have a DO session without having an R-P or PPP session
Session is data concept; allows for flat, distributed architecture

Session transfer required when moving between domains
Impact of mobile environment was not fully thought through
A session is a shared state maintained between the AT and AN

Shared negotiated parameters/attributes with the AN
Each AT with a session has been assigned a Unicast AT Identifier address (UATI)
A session may last a long time through Keep Alive Functions
Session Layer
Session Lifecycle
Session Setup
Session Lifecycle at the AN
UATI
Assignment
Available
UATI Request(RATI Random AT Identifier in

MAC layer header)
AT is assigned an address, UATI
Session Negotiation/Configuration
Session Maintenance
Session
Close,
Session
Transfer
Session Transfers
AT moves between subnets
Assigned
UATI Request(UATI existing Unique AT

Identifier in MAC layer header)
Prior Session
AT sets up new session, then negotiates for old
session
Keep Alive
Keep
Alive
Idle
(Dormant)
Configuration
Negotiation
Session Close
Released UATI can be assigned to another
AT
Connection
Close
Active
Connection
Assignment
Session Layer
The many faces of UATI
UATI024
Unique identifier of a session within a subnet
Multiple entities within subnet assign UATIs
Each has its own subset to maintain uniqueness
UATI032
8-bit Color Code + UATI024
Used in MAC layer header of messages
Identifies which AT the message is coming from
Used to determine source of session transfer request
UATI104
Upper 104 bits of SectorID of assigning entity

Color Code is a locally unique 8-bit representation of the UATI104
Upper bits specified by standards; identify system
Lower 32 bits include A13 IP address
UATI128
UATI104 + UATI024
IPv6 equivalent
UATI128
System ID
A13 IP Address
UATI24
UATI104
UATI032
Color Code
UATI24
Session Layer
Configuration Negotiation
Keep Alive
Not much to negotiate in Rel 0
Maintains inactive session from expiring
Session State Information Record (SSIR)

Mostly settings of default protocols
Rev A (&B)
Much more to negotiate
Personalities
QoS
Extended SSIR (ESSIR)
Negotiating sessions is expensive

Air interface
Processor Occupancy
Expensive to renegotiate session
Allows recycling of AN resources assigned

to lost sessions
Keep Alive Timer
0 to 65535 minutes (45 Days)
Default: 54 hours
We recommend 6 hours
Keep Alive Messages exchange can be

disabled (set to 0)
Transferring sessions is cheaper
Session Layer
Session Transfer
Other Names: Dormant session transfer, Idle session transfer, inter-PCF idle
transfer, A13 session transfer, DO session transfer
Color Code method
AT notices a change of subnet; sends UATIRequest with the UATI032 of its current
session in the MAC Layer header
New AN looks up A13 IP address from Color Code & contacts old AN
The session information is transferred to the new AN
A new UATI is assigned at the new AN (UATIAssign)
The old UATI is released
Prior Session method

AT notices a change of subnet but did not see the transition; sets up new session
UATIRequest with RATI in MAC layer header
New UATI assigned

AT negotiates for Prior Session instead of negotiating new session
Sends UATI128 of old session (ALU implementation includes A13 IP address)
New AN gets session information from old AN

The old UATI is released
Session Layer Field Issues

Assigned, but not negotiated, session is a valid session state
Subnet borders not clean RF-wise
Subnet borders on rivers
Subnet borders pointing out into coverage holes
Knife-edge subnet borders with quickly changing RF
AT bounces between subnets!
Combine the above with Prior Session Method voila, Dangling sessions
Undocumented criteria for AT using Prior Session method
PSM triggers off of coverage hole; but not distance traveled
PSM creates a new session to assigned state

BUT, then moves back to other subnet before negotiating
Session uses default keep-alive of 54 hours
Compare to normal 6-hour keep alive time of 6 hours
Since session was not negotiated it is never transferred,

Only removed if AT asks for another new session in the same location
Problem initially manifested itself as a processor occupancy problem

Software bug related to having very few UATIs left to dispense

Fixed by setting Keep Alive of unnegotiated sessions to 1 minute

Processor Occupancy
Too many session transfers
Session transfer is expensive
Resulted from poor planning

Too many subnet borders
Subnets:
Rectangles different colors =
different APs
Triangles
Circles
Diamonds

Remove borders by grouping RNCs
Little session transfer between group
members
RNC 1,2,3
RNC 4,5,6
Therefore less processing

Group across worst RF subnet borders
Creates issue for flood Paging

Need distance-based paging
Might create load imbalance

Session balancing
Implementation uses unused bits of

SectorID to identify groups and group
members
Interacted with low-level algorithm in
QCOM mobile that made a bad
assumption regarding content of
UATI128
RNC 7,8,9
RNC Grouping Example
Connection Layer
Air Link Management Protocol
Maintains overall connection state (Initialization, Idle, or Connected)
Initialization State Protocol

AT is initialized to acquire the network
Idle State Protocol

AT has acquired the network, does not have an open connection
AT monitors the network overhead channel
Enhanced Idle State Protocol (Rev. A)

Connected State Protocol
AT has an open connection with the AN
Route Update Protocol

Performs pilots supervision
Keeps track of the ATs location
Overhead Message Protocol

Maintains the updated broadcast parameters
Packet Consolidation Protocol

Consolidates and prioritizes packets for transmission
Connection Layer
Channel Structure
System Acquisition
Idle State Overhead Monitoring
Access Procedures
Connection Setup
Air Interface Resources
Paging
Connection Close
Active Hand-off
Connection Layer- Channel Structure
DRCLoc
k
ARQ
Rev. A
Data
Source
Control
Rev. A
Connection Layer System Acquisition

Pilot Channel
How does the AT find its service?

First look at its own Preferred Roaming
List (PRL)
Sync Message
QuickConfig Message
SectorParameters Message
Frequencies to start looking
Look for 1xEVDO signals on the

indicated frequencies
Control channel
AccessParameters Message
Other Messages
Control Channel Cycle
Half Frame
Pilot
Channel
Connection Layer System Acquisition

Finds Pilot
Determines timing from Sync message
Determines system information
QuickConfig
SectorParameters
SectorID (Upper 104 = UATI104)
Match upper bits of SectorID with PRL entry
If no match
Go back to PRL algorithm
Find another frequency to try
Repeat above steps until PRL match (or until battery dies)
Obtain Session
Setup and/or Transfer
Negotiate Session, if needed

Negotiation uses a connection, but does not set up PPP or R-P sessions
Negotiation connections behave differently than traffic connections
Finally, the AT is ready to make a real data connection!

Connection Layer - Idle State Overhead Monitoring, Route Update

In the Idle State, the AT monitors the Control Channel
Continuous Mode Operation
Monitors the Control Channel continuously
Supports Access Procedures
Suspended Mode Operation

Transition between Continuous & Slotted mode
Slotted Mode Operation (Sleep Mode)

Monitors only the selected slots
Supports Paging
Performs Idle hand-off
May trigger distance-based RouteUpdate
May trigger Session transfer
Enhanced Idle State (Rev. A)

Allows for shorter slot cycles; ~5 seconds too long for VoIP applications
Connection Layer Access Procedures

Access Channel Structure similar to CDMA
Access
Slot N+1
Access
Slot N
Access
Slot N+2
Access transmission max length
Preamble
1-7 frames
Max Capsule Size

1-15 frames
System
Time
26.66ms Access
Channel Frame
Access Cycle
Duration
Access Cycle
Duration
Connection Layer Connection Setup

RNC
(HDRC)
Cell
AT
Max respond time 96 slots
RouteUpdate & ConnectionRequest(UATI)

TIDPATsetup
(1.5s)
TACMPTransation
(1s)
TRUPConnSetup (1s)
AcACK
Allocate Traffic Channel Req

Allocate Traffic Channel Resp
DRCCoverInd
TrafficChannelAssignment
Send DRC + Pilot and ramp up RTC
SendTCA
MobileAcquiredInd
SendRTCAck
RTCAck
TrafficChannelComplete
ACK
TCC
Data or Configuration Negotiation
After Configuration Negotiation, the connection has to be closed

before another connection can be used for data
Access &
Control
Channels
Traffic
Channels
Connection Layer - Resources Allocation

A connection uses the following air interface resources
Forward Link:
Forward traffic channel
MAC Index for each forward leg
5-63 for Rel. 0; Rev A. added 64-127
DRC Cover for each forward leg

Reverse Link Power Control Bit
Frame Offset
Reverse Link:
Reverse traffic channel
DRC channel
Indicates selected Serving Sector
Indicates requested forward link data rate
Many different rates configurable depending on current airlink RF properties
Frame Offset
Connection Layer - Paging

Page message can be sent only if:
The AT has a UATI (DO Session)- and Is in the dormant mode
Use the assigned UATI to Page

Where & when to Page?
Last seen Active Set
Distance-based Paging
Based on last RouteUpdate message from AT
Flood paging the entire RNC coverage area if necessary

Carrier to page determined from RATI
Determine ATs wake up slot to page
AT wakes up once in every 12 Control Channel Cycle (I.e. 5.12s)
After the AT hears the Page message, the AT uses the same Access Procedure
(same messages) for connection setup
Connection Layer Connection Close

When the connection:
Has been idle too long or Has its session closed -or The airlink has stopped working
The connection will be closed

Traffic channel resources are released
The AT can choose to use the Suspended Mode Operation
The AT will tell the AN how long it will stay in the suspended mode
During the Suspended Mode, the AN can reconnect with a TCA instead of a Page message if
more data shows up
This will save the connection setup time
No need to wait for the ATs Wake up slot
No need to send the Page, the AT must use Access Probes to respond
If the AT still had data to send, it will attempt to reconnect
Connection Layer Active Hand-off

Analog/TDMA had no concept of soft hand-off
CDMA introduced soft hand-off
What is softer/soft handoff?
Pilot Sets
1xEVDO changes
1XEVDO virtual soft handoff on the forward link
Normal CDMA-like soft hand-off on the reverse link

Active hand-off defines hand-off of
connections
As opposed to idle hand-off of sessions
What is Soft Handoff?

For Analog and TDMA, a hand-off was a 1:1
swap.
Mobile
Only one cell/sector at a time
For CDMA, hand-off can add, drop or swap

cell/sectors
Multiple cells/sectors (Active Set)
transmit/receive the ATs signal
simultaneously
Must use identical band class, frequency
assignment and frame offset
Provides diversity on the forward and
reverse traffic channels.
Critical for CDMA system performance
AT

connections

swap.
Mobile

cell/sectors
simultaneously
AT

connections

swap.
Mobile

cell/sectors
simultaneously
AT

For 1xEVDO, hand-off can add, drop or swap cell/sectors
Multiple cells/sectors in Active Set
AT requests changes to active set in RouteUpdate message
AN assigns new active set in TrafficChannelAssignment message
Virtual soft hand-off in forward link; only one leg used at a time
DRC from AT tells AN which leg to transmit on, and at what rate
Picks sector from which it can get the best rate
Reverse link is true soft hand-off like CDMA
AT

AT

AT

AT

AT Maintains 4 mutually exclusive Pilot Sets
Active Set set of pilots currently serving the AT
Candidate Set Set of pilots not in the Active Set, but are ready for
inclusion in the Active Set
Neighbor Set Set of pilots not in either Candidate nor Active set, but are
likely candidates
Remaining Set The set of all possible pilots on the current channel
assignment

Pilots are moved in or out of each pilot set based on pilot signal strength and the
following parameters:
PilotADD (T_ADD) pilot detection threshold. If a pilot is in the Neighbor or
Remaining set and is detected above T_ADD, it is moved to the Candidate set. If the
pilot is already in the Candidate Set, it will be added to the Active Set when the
following conditions are met:
If the Active Set is not full
Or if the Active Set is full, but
The candidate pilots strength exceeds the weakest in the Active Set by at least T_COMP
PilotCompare (T_COMP) Threshold used to be compared when the pilot in the

Active Set should be replaced by that from the Candidate Set
PilotDrop (T_DROP) Threshold used to determine when a pilot should be removed
from the Active Set
PilotDropTimer (T_TDROP) Timer used together with T_DROP to determine when a
pilot in the Active Set and Candidate Set should be removed into a Neighbor or
Remaining Set.
Pilot
Strength
T_ADD
T_DROP
Above T_ADD
Send Route Update
BS sends
TCA
Receive TCA
Move Pilot to
Active Set
Sends TCC
Below T_DROP
BS sends TCA
Starts
T_TDROP
Moves Pilot to
timer
Timer expires
Sends RU message The Neighbor Set
Send TCC
Security Layer
Ensures security of the connection between the AT and the AN.
The Security layer provides the following functions:
Key Exchange Protocol
Exchange security keys for authentication and encryption
Diffie-Hellman Key Exchange method
Authentication Protocol
Provides the procedures for authenticating traffic
Encryption Protocol:
Provides the procedures for encrypting traffic
Currently not used by the ALU system
Security Protocol
Generates a cryptosync for the Authentication and Encryption Protocols
MAC Layer
Medium Access Control (MAC)
Contains the rules for the proper operation of the physical channels
[Enhanced] Control Channel MAC Protocol
Control Channel transmission by the AN
Control Channel reception by the AT
[Enhanced] Access Channel MAC Protocol

Access Channel timing & power requirements for AT
[Enhanced] Forward Traffic Channel MAC Protocol

Variable and fixed transmission rates and ARQ interlacing.
DRC Channel
Ack Channel
Reverse Traffic Channel MAC Protocol
Similar to the traditional CDMA2000 1X MAC layer.

Enables the AN in acquiring the Reverse Traffic Channel
Reverse Traffic Channel data rate selection.
Subtype 1 (Rel. 0)
Subtype 2 Rev. A
Subtype 3 Rev. A (aka. RTCMAC3 High capacity or low latency)
[Enhanced] = Rev. A
MAC Layer Access Procedures

Access Probe
Sequence 1
Seq 2
Seq MAX_REQ_SEQ
(15 max)
Seq 3
System
Time
PD
RS
PD*
PI
Access
Probe 2
PI
IP
Access
Probe 3
Access
Probe
1
TA
System
Time
RS - BKOFF, delay for the next probe sequence
PD - Persistence Test Delay
RT - PROBE_BKOFF, delay for the next probe
IP - Initial power based on open loop power
estimation
PI - PWR_STEP, power increment
TA -Time to wait for BSACK
RT
*For request attempt only
Access Probe
1 + NUM_STEP
(16 max)
MAC Layer - [Enhanced] Forward Traffic Channel MAC Protocol

Control Channel Cycle
Half Frame
MAC
Channel
Pilot
Channel
Forward Traffic Channel

Variable rate - AN transmits at the rate dictated by the DRC sent by the AT
Fixed rate - Fixed Mode Request message
Testing, Fwd/Rev Link mismatch, or VoIP
MAC layer header identifies the intended AT with UATI032
Forward MAC Channel
Reverse Activity Bit (RAB) Channel (Tells AT if reverse rate to increase or decrease)
DRCLock Channel (Tells AT not to point DRC to sector if locked)
Reverse Power Control (RPC) Channel
ARQ Channel (Rev. A - ACK/NAK of reverse traffic sub-packet)
Allows for 10x improvement in Reverse Traffic rates

Forward traffic channel scheduling algorithm
Trades fairness to individual users with maximizing sector throughput.
Provides higher throughput to users in better RF conditions
Optimizes total cell throughput by exploiting both short- and long- term
variability among user's RF

Forward Link Power Control
Forward Link transmits at a fixed power supported by the sector
Power Control Bits used for the Reverse Link Inner Loop Power Control
MAC Layer - [Enhanced] Reverse Traffic Channel MAC Protocol

Reverse Link Power Control
The purposes for reverse link power control are:
Maintain desired Frame Error Rate (FER), e.g. 1%
Determine the lowest power required to support each user
Maximize capacity when each mobile and cell transmits minimum power
Address reverse link overload situations
Outer Loop
Inner Loop
Reverse Link Transmit Rate

AT sends Reverse Rate Indicator (RRI)
Rate Limit Control on the reverse link

BS controls the maximum rate the AT shall transmit in the sector
AT starts with 9.6kbps
After a Rate Limit message is received, the AT can adjust the transmit rate
MAC Layer - Reverse Traffic Power Control

Similar to IS-95
PC bits
Inner Loop
Transmitted on Forward MAC RPC channel

Orthogonalized by a mobile-unique 64-ary
Walsh cover
128-ary for Rev. A. (subtype 2 physical
layer)
All sectors in Active set transmit PC bits to

the AT
Up to 59 ATs (123 for Rev. A) power

controlled simultaneously
Outer Loop
0:AT to increase
1: AT to decrease
Adjusts the Eb/No setpoint every frame

(26.66ms)
Adjustment is based on the received reverse
link frame quality
The Outer Loop controls the Eb/No setpoint
required for the desired FER
Speed 600Hz
Inner loop is performed in the ASIC
It determines the lowest AT transmit
power
AN compares the received Eb/No with the
Eb/No setpoint
Commands the AT to adjust its transmit
power to achieve setpoint
Power changes in 1dB or 0.5 dB steps
MAC Layer - Reverse Traffic Power Control
Forward MAC
RPC channel
Eb/No Setpoint:
Decrease until frame
error, then step up
Outer Loop
26.67 mSec
Power Control
(PC) Bits
AN
Frame Errors
of Reverse
Channel
Inner Loop
1.67 mSec
Power of
Reverse
Channel
(Eb/No)
Reverse Traffic
channel
AT
Physical Layer
Subtype 1 Rel. 0
Subtype 2 Rev. A
Required for RTCMAC Subtype 2 or 3
Allows for 128 MAC IDs
Questions
Questions?
Acknowledgements
1xEVDO Class
Gabriela Abramovici, Frances Lin, Dietz Vedder, June 2001
SRD-1853, v10.0, January, 2010

IS-856-0, IS-856-A, 1xEVDO Standards
1xEV: 1x EVolution IS-856 TIA/EIA Standard Airlink Overview
QUALCOMM, Inc., November 7, 2001, Revision 7.2
1xEVDO Class, Lucent document CL8306-2.0-IG.en.UL

Issue 2, April 2004
1xEV-DO RAN Rev A Related Features

Chokri Trabelsi

1xEVDO: 1x Evolution Data Optimized - 3G CDMA Wireless Data

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1xEVDO: 1x Evolution Data Optimized - 3G CDMA Wireless Data

Uploaded by

Copyright:

Available Formats

1xEVDO

1x Evolution Data Optimized - 3G CDMA Wireless Data

2 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

1xEVDO: What is in a Name?

3 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

4 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Wireless Evolution (Digital)

From CL8306-2.0-IG.en.UL, 4/2004

All Rights Reserved Alcatel-Lucent 2010

Compare/Contrast with IS-2000 CDMA

IS-2000 uses codes to orthogonalize users signals

IS-856 uses TDMA techniques in the Forward channel

Reverse channels are very similar

6 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Data Rates for Technology Type (kbps)

*307.2 is possible, but not implemented on the ALU system

7 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Idle Handoffs/DO Session

8 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

1xEVDO Data Protocol

RNC (HDR Controller)

1xEVDO Air Interface Protocols

All Rights Reserved Alcatel-Lucent 2010

1xEVDO Default Protocol Layers (Data & Signaling)

10 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

11 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Signaling Link Protocol (SLP)

Best Effort Transmission

12 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Default Packet Application (DPA) Personality

Packet Location Update Protocol (LUP)

Flow Control Protocol

13 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Multi-Flow Packet Application (MFPA, EMFPA & MLMFPA) Personality

Enhanced MFPA (EMFPA)

Multi-Link Multi-Flow Packet

Multiple RTCMAC flows

Introduces Quality of Service (QoS)

14 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

15 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Address Management Protocol

Session Configuration Protocol

16 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Session is data concept; allows for flat, distributed architecture

A session is a shared state maintained between the AT and AN

17 | 1xEVDO Overview | June 2010

All Rights Reserved Alcatel-Lucent 2010

Session Lifecycle at the AN

UATI Request(RATI Random AT Identifier in

UATI Request(UATI existing Unique AT