1xev do technology
DESCRIPTION
1x EV DO Technology descriptionTRANSCRIPT
Course 340
Background and IntroductionTo 1xEV-DO Technology
Background and IntroductionTo 1xEV-DO Technology
This course can be downloaded free from our website:
www.howcdmaworks.com/340.pdf
1-2005 340 - 1Course Series 340v3.2 (c)2005 Scott Baxter
Contents
Survey of Wireless Data Technologies and 1xEV-DOPurpose of 1xEV-DO and Differences from 1xRTT
• ITU requirements and user application capabilities• Exploiting rapidly-changing channel conditions• Channel Structure, Power Control, Unique Features
1xEV-DO transmission details• Codes, Channels, MAC Indices• Hybrid ARQ process
1xEV-DO Access Terminal Architecture• Route Update Operation
1xEV-DO Network Elements and Architecture• Lucent, Motorola, Nortel
1xEV-DO Layer-3 Messaging1xEV-DO/1xRTT Interoperability SummaryReview of 1xEV-DO Protocols
1-2005 340 - 2Course Series 340v3.2 (c)2005 Scott Baxter
Global and US Wireless Snapshot 4Q 2003
Worldwide USATotal Wireless Users
GSM usersCDMA usersTDMA usersIDEN users
Analog users
1,320,000,000 100%870,000,000 65.9%224,000,000 17.0%124,000,000 9.4%68,000,000 5.2%34,000,000 2.6%
141,000,000 100%33,732,506 23.9%64,503,287 45.7%26,375,232 18.6%11,978,382 8.5%4,510,594 3.2%
Total Worldwide Wireless customers surpassed total worldwide landline customers at year-end 2002, with 1,00,080,000 of each.2/3 of worldwide wireless customers use the GSM technologyCDMA is second-most-prevalent with 17.0%In the US, CDMA is the most prevalent technology at 45.7%Both CDMA and GSM are growing in the US
• most IS-136 TDMA systems are converting to GSM + GPRS + EDGE
1-2005 340 - 3Course Series 340v3.2 (c)2005 Scott Baxter
Global and US Wireless Users by Technology
GSM24%
CDMA46%
TDMA19%
Analog3%
IDEN8%
GSM66%
CDMA17%
TDMA9%
Analog3%
IDEN5%
GSM is by far the dominant global technologyCDMA is dominant in its country of origin, the USAThe IS-136 TDMA community is rapidly implementing GSM
• primary motivation is to provide GPRS and/or EDGE fast data
1-2005 340 - 4Course Series 340v3.2 (c)2005 Scott Baxter
A Quick Survey of Wireless Data TechnologiesUS CDMA ETSI / GSM ANALOG
AMPS Cellular9.6 – 4.8 kb/s
w/modem
PAGINGGSM CSD9.6 – 4.8 kb/s
GSM HSCSD32 – 19.2 kb/s
IS-9514.4 – 9.6 kb/s
IS-95B64 -32 kb/s
Mobitex9.6 – 4.8 kb/s
obsolete
CDPD19.2 – 4.8 kb/sdiscontinued
1xRTT RC3153.6 – 80 kb/s
1xRTT RC4307.2 – 160 kb/s
1xEV-DO2400 – 600 DL153.6 – 76 UL
1xEV-DO A3100 – 800 DL1800 – 600 UL
1xEV-DV5000 - 1200 DL307 - 153 UL
GPRS40 – 30 kb/s DL
15 kb/s UL
EDGE200 - 90 kb/s DL
45 kb/s UL
Other Misc.
IS-136IDEN
19.2 – 19.2 kb/sIS-136 TDMA19.2 – 9.6 kb/sWCDMA 0
384 – 250 kb/s
WCDMA 12000 - 800 kb/s
WCDMA HSPDA12000 – 6000 kb/s
Flarion OFDM1500 – 900 kb/s
TD-SCDMAIn Development
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!
1-2005 340 - 5Course Series 340v3.2 (c)2005 Scott Baxter
The CDMA Migration Path to 3G
1xEV-DORev. A
IS-856
1250 kHz.59 active
users
Higher data rates on data-
only CDMA carrier
3.1 Mb/sDL
1.8 Mb/sUL
RL FLSpectrum
1xEV-DORev. 0IS-856
1250 kHz.59 active
users
High data rates on data-only
CDMA carrier
2.4 Mb/sDL
153 Kb/sUL
CDMAone CDMA2000 / IS-2000
Technology
Generation
SignalBandwidth,
#Users
Features:Incremental
Progress
1G
AMPS
DataCapabilities
30 kHz.1
First System,Capacity
&Handoffs
None,2.4K by modem
2G
IS-95A/J-Std008
1250 kHz.20-35
First CDMA,
Capacity,Quality
14.4K
2G
IS-95B
1250 kHz.25-40
•Improved Access•Smarter Handoffs
64K
2.5G? 3G
IS-2000:1xRTT
1250 kHz.50-80 voice
and data
•Enhanced Access
•Channel Structure
153K307K230K
3G
1xEV-DV1xTreme
1250 kHz.Many packet
users
High data rates on
Data-Voice shared CDMA carrier
5 Mb/s
3G
IS-2000:3xRTT
F: 3x 1250kR: 3687k
120-210 per 3 carriers
Faster data rates on shared 3-carrier bundle
1.0 Mb/s
RL FLRL FLRL FLRL FLRL FLRL FLRL FL
1-2005 340 - 6Course Series 340v3.2 (c)2005 Scott Baxter
Modulation Techniques of 1xEV Technologies
1xEV, “1x Evolution”, is a family of alternative fast-data schemes that can be implemented on a 1x CDMA carrier.1xEV DO means “1x Evolution, Data Only”, originally proposed by Qualcomm as “High Data Rates” (HDR).
• Up to 2.4576 Mbps forward, 153.6 kbps reverse
• A 1xEV DO carrier holds only packet data, and does not support circuit-switched voice
• Commercially available in 20031xEV DV means “1x Evolution, Data and Voice”.
• Max throughput of 5 Mbps forward, 307.2k reverse
• Backward compatible with IS-95/1xRTT voice calls on the same carrier as the data
• Not yet commercially available; work continues
All versions of 1xEV use advanced modulation techniques to achieve high throughputs.
QPSKCDMA IS-95,
IS-2000 1xRTT,and lower ratesof 1xEV-DO, DV
16QAM1xEV-DOat highest
rates
64QAM1xEV-DVat highest
rates
1-2005 340 - 7Course Series 340v3.2 (c)2005 Scott Baxter
GSM Technology Migration Path to 3G
Integrated voice/data(Future rates to 12 MBPS using adv.
modulation?)
Technology
Generation
SignalBandwidth,
#Users
Features:Incremental
Progress
1G
variousanalog
DataCapabilities
various
various
various
2G
GSM
200 kHz.7.5 avg.
Europe’sfirst Digitalwireless
none
2.5G or 3?
GPRS
200 kHz.Many
Pkt. users
•Packet IP access
•Multiple attached
users
9-160 Kb/s(conditionsdetermine)
3G
EDGE
200 kHz.fast data
many users
8PSK for 3x Faster data rates
than GPRS
384 Kb/smobile user
3GUMTSUTRA
WCDMA3.84 MHz.up to 200+voice users
and data
2Mb/sstatic user
1-2005 340 - 8Course Series 340v3.2 (c)2005 Scott Baxter
TDMA IS-136 Technology Migration Path to 3G
2G
CDPD
30 kHz.Many
Pkt Usrs
19.2kbps
US PacketDataSvc.
Technology
Generation
SignalBandwidth,
#Users
Features:Incremental
Progress
DataCapabilities
2GTDMAIS-54
IS-136
30 kHz.3 users
USA’sfirst
Digitalwireless
none
2.5G or 3?
GPRS
200 kHz.Many
Pkt. users
•Packet IP access
•Multiple attached
users
9-160 Kb/s(conditionsdetermine)
3G
EDGE
200 kHz.fast data
many users
8PSK for 3x Faster data rates
than GPRS
384 Kb/smobile user
3GUMTSUTRA
WCDMA3.84 MHz.up to 200+voice users
and data
Integrated voice/data(Future rates to 12 MBPS using adv.
modulation?)
1G
AMPS
30 kHz.1
First System,Capacity
&Handoffs
None,2.4K by modem
2Mb/sstatic user
2G
GSM
200 kHz.7.5 avg.
Europe’sfirst
Digitalwireless
none
the familiar GSM path!
1-2005 340 - 9Course Series 340v3.2 (c)2005 Scott Baxter
4G: Broadband Wireless Access Technologies
Not BWA; for comparison only
802.16
BPSK to256QAMOFDM
54 Mb/s
TDD, FDDvarious
2-11 GHz10-66 GHz
802.20Mobile BWA
1-2005 340 - 10Course Series 340v3.2 (c)2005 Scott Baxter
Technology
ModulationType
Max RawData Rate
AccessMethod
FrequencyBand
InfraredIRDA
various
4 Mb/s
Single User perOptical Carrier
Optical
802.11b
CCK
11 Mb/s
DSSS
2.4 GHz
802.11a
BPSK, QPSK,16QAM, or
64QAM
54 Mb/s
DSSS
5 GHz
HIPERLANType 1
FSK orGMSK
23.5 Mb/s
OFDM
5 GHz
HIPERLANType 2
BPSK, QPSK,16QAM, or
64QAM
54 Mb/s
various.
5 GHz
Bluetooth
GFSKFH
1 Mb/s
various
2.4 GHz
BLUETOOTH
802.11A, B, WIFI, WILAN
Infrared IRDA
High Hopes!
4G – Evolution or Revolution?H
igh-
Tier
$$$
Low
-Tie
r $
1G: AMPS
There’s a revolution going on!• New 2.5G services arriving now, new 3G arriving 2002 through 2005• A groundswell of commercial (and even free!) WILAN deployment
3G networks and 4G networks have their own unique advantagesUltimately 3G and 4G will be integrated by wireless operators!
Technology Environment Service Provider/Infrastructure Owner
PSTN IP/VPNs
2G: TDMA, GSM, IS95 CDMA, IDEN
2.5G: GPRS, EDGE3G: IS2000 1xRTT, 1xEV DO, 1xEV DVUMTS WCDMA4G: Wireless LAN802.11b “Wi-Fi”802.11a, gHIPERLAN Type 1HIPERLAN Type 2BluetoothInfrared freenetworks.org
Near-Universal Macro-Coverage
Hotspots
1-2005 340 - 11Course Series 340v3.2 (c)2005 Scott Baxter
SPEED: 1xEV-DO’s PurposeDifferences from CDMA2000 1xRTT
SPEED: 1xEV-DO’s PurposeDifferences from CDMA2000 1xRTT
1-2005 340 - 12Course Series 340v3.2 (c)2005 Scott Baxter
Why 1xEV-DO?
To satisfy the ITU 3G vision of four radio environments:• 9600 bps megacells – met by satellite-based systems• 144 kbps macrocells – met by CDMA2000 1xRTT RC3• 384 kbps microcells – met by CDMA2000 1xRTT RC4 (307k)• 2 mbps picocells – met by 1xEV-DO and 1xEV-DV
To provide new applications for CDMA2000 users• high speed data access and web applications in the mobile
environment• speeds up to 2.4 mbps
1-2005 340 - 13Course Series 340v3.2 (c)2005 Scott Baxter
Why Can’t 1xRTT do high speeds?
RF channel conditions change much faster than 1xRTT can track• this causes 1xRTT to mis-estimate the feasible data speed
which can be used for a burst of data– sometimes conditions are worse than expected at the time
of a burst, and the burst is received with severe errors– other times the conditions are better than expected at the
time of a burst, and the burst transmitted more slowly than actually could have been received
Bursts in 1xRTT are so long that substantial latency is introduced into error correction and packet repetition schemesFor all these reasons, something more nimble is needed
1-2005 340 - 14Course Series 340v3.2 (c)2005 Scott Baxter
Mobile RF Channel Conditions Change RapidlyPa
th L
oss,
rela
tive
dB
+6
+4
+2
+0
-2
0 0.1 0.2 0.3 0.4 0.5Time, Seconds
Path Loss, db
“Slow Fading” due to obstructions and user
motion
“Fast Fading” due to user motion through
multipath fading standing-wave pattern
Radio Transmission Technologies must be “nimble” enough to quickly adapt for best results during changing channel conditions
• in choosing what data rate to transmit• in power control of the forward and reverse links
1-2005 340 - 15Course Series 340v3.2 (c)2005 Scott Baxter
1xRTT Data Burst Control Lags RF ConditionsDATA BURST
ACTUALLY OCCURSNOW
DA
TA R
ATE
DEC
ISIO
N
Fixed Rate!BTS
MO
BIL
E
Tseconds
F-SCH
F-FCH
R-FCH
R-SCH
0 0.50.1 0.2 0.3 0.4
SCH-Assignment Msg.
F-SCH Burst
Setup Time
Path
Los
s, re
lativ
e dB
Eb/N
t, dB
Path Loss, db
GOOD CONDITIONS
BAD CONDITIONS
+6
+4
+2
+0
-2
0 0.1 0.2 0.3 0.4 0.5Time, Seconds
1-2005 340 - 16Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO vs. 1xRTT at the Same Time-Scale
AP
Traffic
DRCSetup time can be less than 10 ms., depending on traffic loading. AT
1xEV-DO Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.
T0 0.50.1 0.2 0.3 0.4
Time, Seconds
BTS
MO
BIL
E
F-SCH
F-FCH
R-FCH
R-SCHSCH-Request Msg.
SCH-Assignment Msg.
F-SCH Burst
Setup Time Fixed Rate!1xRTT
Thoughput: 0.15 or 0.31 Mb/s max, 0.06 Mb/s typ.
1-2005 340 - 17Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Handles Data at the level of Packets and Subpackets
AP
Traffic
DRCSetup time can be less than 10 ms., depending on traffic loading. AT
1xEV-DO Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.
Each forward traffic channel subpacket is only 1.67 ms long• The flow of subpackets is stopped immediately when successful
decoding is achieved. • The reaction to channel conditions is effectively instantaneous,
with no wasted excess energy!Short preambles and embedded MAC bits identify the destination mobile
• No time is wasted sending layer-3 messages to control packet flowEach mobile DRC request is based on latest channel condition
• ACK/NAK commands can stop unneeded subpacket repetitions in less than 5 ms.!
1-2005 340 - 18Course Series 340v3.2 (c)2005 Scott Baxter
The Key Features and Structure of 1xEV-DO
The Key Features and Structure of 1xEV-DO
1-2005 340 - 19Course Series 340v3.2 (c)2005 Scott Baxter
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
1-2005 340 - 20Course Series 340v3.2 (c)2005 Scott Baxter
Power Management of 1xEV-DO vs. 1xRTT
PILOT
PAGINGSYNC
Maximum Sector Transmit Power
User 123
45 5 5678
time
pow
er
IS-95: VARIABLE POWER TO MAINTAIN USER FERPOWER MANAGEMENT
IS-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
time
pow
er
1xEV-DO: MAX POWER ALWAYS,DATA RATE OPTIMIZED
1-2005 340 - 21Course Series 340v3.2 (c)2005 Scott Baxter
Some EV-DO Terminology
IS-95, IS-2000, 1xRTT EV-DO
Phone, Mobile,
Handset, or Subscriber Terminal
ATAccess
Terminal
APAccess Point
Base Station,BTS,
Cell Site
1-2005 340 - 22Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Technical DetailsData Flow and Channels
1xEV-DO Technical DetailsData Flow and Channels
1-2005 340 - 23Course Series 340v3.2 (c)2005 Scott Baxter
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 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 Cycle of PN Short Code
One 1xEV-DO Frame
One Slot
1-2005 340 - 24Course Series 340v3.2 (c)2005 Scott Baxter
What’s In a Slot?½ Slot – 1024 chips ½ Slot – 1024 chips
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
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
1-2005 340 - 25Course Series 340v3.2 (c)2005 Scott Baxter
What if there’s No Data to Send?½ Slot – 1024 chips ½ Slot – 1024 chips
empty empty empty empty
MA
CPI
LOT
MA
C
MA
CPI
LOT
MA
C
400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips
SLOT
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
1-2005 340 - 26Course Series 340v3.2 (c)2005 Scott Baxter
Slots and Frames½ Slot – 1024 chips ½ Slot – 1024 chips
1-2005 340 - 27Course Series 340v3.2 (c)2005 Scott Baxter
Slot
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
400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips
Two Half-Slots make a Slot16 Slots make a frame
Frames and Control Channel Cycles
A Control Channel Cycle is 16 frames (that’s 426-2/3 ms, about 1/2 second)The first half of the first frame has all of its slots reserved for possible use carrying 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
FRAME1 Frame = 16 slots – 32k chips – 26-2/3 ms
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
1-2005 340 - 28Course Series 340v3.2 (c)2005 Scott Baxter
Forward Link Frame and Slot Structure:“Big Picture” Summary
½ Slot – 1024 chips ½ Slot – 1024 chips
SLOT
FRAME1 Frame = 16 slots – 32k chips – 26-2/3 ms
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
400 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips
Slots make Frames and Frames make Control Channel Cycles!
1-2005 340 - 29Course Series 340v3.2 (c)2005 Scott Baxter
The 1xEV-DO ChannelsIN 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
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
1-2005 340 - 30Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 31Course Series 340v3.2 (c)2005 Scott Baxter
Functions of the 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
AP
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)
Functions of the 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
1-2005 340 - 32Course Series 340v3.2 (c)2005 Scott Baxter
Information Flow Over 1xEV-DO
AP
Data Ready
DRC: 5
Data from PDSN for the Mobile
MP3, web page, or other content
1-2005 340 - 33Course Series 340v3.2 (c)2005 Scott Baxter
The system notifies a mobile when data for it is waiting to be sentThe mobile chooses which sector it hears best at that instant, and requests the sector to send it a packetthere are 16 possible transmission formats the mobile may request, called “DRC Indices”. Each DRC Index value is really a combined specification including specific values for:
• what data speed will be transmitted• how big a “chunk” of waiting data will be sent (that amount of data will be
cut of the front of the waiting data stream and will be the “Packet”transmitted)
• what kind of encoding will be done to protect the data (3x Turbo, 5x Turbo, etc.) and the symbol repetition, if any
• after the symbols are formed, how many SUBpackets they will be divided into
Then, the sector starts transmitting the SUBpackets in SLOTS on the forward linkThe first slot will begin with a header that the mobile will recognize so it can begin the receiving process
Transmission of a Packet over EV-DO
AP
Data ReadyData from PDSN for the Mobile
MP3, web page, or other content
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.
1-2005 340 - 34Course Series 340v3.2 (c)2005 Scott Baxter
Transmission of a Packet over EV-DO
AP
Data ReadyData from PDSN for the Mobile
MP3, web page, or other contentDRC: 5
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, and its C/I. The C/I dictates the maximum feasible speed for data reception by the mobile. The AT transmits on its DRC asking that sector to send it a packet – in this example at speed “DRC Index 5”.
1-2005 340 - 35Course Series 340v3.2 (c)2005 Scott Baxter
Transmission of a Packet over EV-DO
AP
Data ReadyData from PDSN for the Mobile
MP3, web page, or other contentDRC: 5
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.
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
1-2005 340 - 36Course Series 340v3.2 (c)2005 Scott Baxter
Transmission of a Packet over EV-DO
AP
1-2005 340 - 37Course Series 340v3.2 (c)2005 Scott Baxter
Data from PDSN for the Mobile
MP3, web page, or other content2048 bits
Interleaver
+ D+
+D D
++ +
+
+ D+
+D D
++ +
+
Turbo Coder
PACKET
Symbols
Data Ready
DRC: 5
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.
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
Transmission of a Packet over EV-DO
AP
1-2005 340 - 38Course Series 340v3.2 (c)2005 Scott Baxter
Data from PDSN for the Mobile
MP3, web page, or other content2048 bits
Interleaver
+ D+
+D D
++ +
+
+ D+
+D D
++ +
+
Turbo Coder
Block Interleaver
PACKET
Symbols
Data Ready
DRC: 5
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.
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
Transmission of a Packet over EV-DO
AP
1-2005 340 - 39Course Series 340v3.2 (c)2005 Scott Baxter
Data from PDSN for the Mobile
MP3, web page, or other content2048 bits
Interleaver
+ D+
+D D
++ +
+
+ D+
+D D
++ +
+
Turbo Coder
Block Interleaver
PACKET
Symbols
Interleaved Symbols
Data Ready
DRC: 5
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.
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
Transmission of a Packet over EV-DO
AP
1-2005 340 - 40Course Series 340v3.2 (c)2005 Scott Baxter
Data from PDSN for the Mobile
MP3, web page, or other content2048 bits
Interleaver
+ D+
+D D
++ +
+
+ D+
+D D
++ +
+
Turbo Coder
Block Interleaver
PACKET
Symbols
Interleaved Symbols
Data Ready
DRC: 5
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
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
Subp
acke
t 4
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
1 2 3 4
Interleaver
+ D+
+D D
++ +
+
+ D+
+D D
++ +
+
Turbo Coder
Block Interleaver
PACKET
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
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
SLOTS
1-2005 340 - 41Course Series 340v3.2 (c)2005 Scott Baxter
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 power
• the mobile uses Ec/Io to choose which sectors to request for its active set
Ec/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
1-2005 340 - 42Course Series 340v3.2 (c)2005 Scott Baxter
Relationship of Ec/Io and C/I in 1xEV-DO Systems
-30
-25
-20
-15
-10
-5
0-30 -25 -20 -15 -10 -5 0 5 10 15 20
C/I, db
Ec/Io
, db
Ec/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
1-2005 340 - 43Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Active Set and Forward Bursting Animation
AccessPoint(AP)
AccessNode(User
Terminal)
AccessPoint(AP)
AccessPoint(AP)
AccessPoint(AP)
AccessPoint(AP)
AccessPoint(AP)
DO-RNC
ACTIVE ACTIVE
ACTIVEACTIVE
NEIGHBOR
NEIGHBOR
DRC
THIS ISFOR YOU!
Good Signal!PACKET PLEASE!
@ x speed
1-2005 340 - 44Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Forward Link Details1xEV-DO Forward Link Details
1-2005 340 - 45Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Protective Coding
Discard6-bit
EncoderTail Field
TurboEncoderwith an
Internally-generated
tail
Data Packet
Encodingand
Scrambling
Inter-leaving
bits symbols
Forward Traffic Channel Packetsor Control Channel Packets
CodeSymbols
Data Total Bits Bits/Pkt SymbolsRate Slots Code per - Tail per
(kbps) Used Rate Packet Field Packet38.4 16 1/5 1,024 1,018 5,12076.8 8 1/5 1,024 1,018 5,120153.6 4 1/5 1,024 1,018 5,120307.2 2 1/5 1,024 1,018 5,120614.4 1 1/3 1,024 1,018 3,072307.2 4 1/3 2,048 2,042 6,144614.4 2 1/3 2,048 2,042 6,144
1,228.8 8 1/3 2,048 2,042 6,144921.6 2 1/3 3,072 3,066 9,216
1,843.2 2 1/3 3,072 3,066 9,2161,228.8 8 1/3 4,096 4,090 12,2882,457.6 8 1/3 4,096 4,090 12,288
Turbo coding is the default encoding method for 1xEV-DO on both forward and reverse linkThe code rate is determined by:
• input bit rate• effective turbo coder rate,
including number of coder outputs and symbol puncturing
The data rate and number of slots used per packet determine the other forward link variables as shown in the table at right
1-2005 340 - 46Course Series 340v3.2 (c)2005 Scott Baxter
Data Scrambling in 1xEV-DO
TurboEncoding &Puncturing
DataScrambling
BlockInterleavingData Bits
Symbolsready toTransmit
IS-95 and 1xRTT use data scrambling on the forward link• the scrambling sequence is a decimated version of the long PN
code from the previous frame• the purpose is to randomize the waveforms of multiple users so
that the composite transmitted waveform has a low peak-to-average ratio and effectively uses power amplifier capability
• a secondary purpose is to provide enhanced privacy1xEV-DO uses data scrambling on both links to randomize the data and avoid unbalanced waveforms
• the scrambling sequence is generic, not unique per user– security is already provided in a standard-defined layer
• the generic scrambling register coefficients are specified in the standard
1-2005 340 - 47Course Series 340v3.2 (c)2005 Scott Baxter
One Slot on the Forward Traffic Channel
DATA MAC
PILO
T
MAC DATA DATA MAC
PILO
T
MAC DATA
336 chips 64 96 64 400 chips 400 chips 64 96 64 400 chips½ Slot – 1024 chips ½ Slot – 1024 chips
PRBL
64
Example Subpacket: 1536 Data Modulation Symbols (1 slot, 614.4 Kb/s)
1/3 or 1/5encoder
scrambler
ChannelInterleaver
QPSK/8PSK16QAM
Modulator
SequenceRepetition,
SignalPuncturing
SymbolDEMUX1 to 16
16-aryWalshCovers
WalshChannel
Gain
WalshChip LevelSummer
Data(modulation
symbols)SequenceRepetition 0
I
Q
I
Q
32-symbol bi-OrthogonalMAC cover
SignalPoint
Mapping
SequenceRepetition(factor=4)
I
Q
WalshChip LevelSummer Q
RAchannel
gain
SignalPoint
Mapping
BitRepetition(xRAB len)
MAC channelRA bits
DRC LockChannel
Gain
RPCChannel
Gain
SignalPoint
Mapping
SignalPoint
Mapping
BitRepetition(xDRCLlen)
Walsh Cover W264
MAC Index Walsh CoverMAC RPC bits A
MAC channelDRC Lock symbols
0
I
Q
Walsh Cover 0
SignalPoint
MappingPilot Channel (all 0s)
TDM
Time D
ivision Multiplexer
To Quadrature Spreading and M
odulationI W
alsh Channels
Q W
alsh Channels
I
Preamble
1-2005 340 - 48Course Series 340v3.2 (c)2005 Scott Baxter
AP The MAC IndexMAC Channel Use Preamble Use
Not 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
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
32 16 I
MA
CIn
dex
Wal
sh C
ode
Phas
e
1 32 Q
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
34 17 I 3 33 Q36 18 I 5 34 QEach 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
38 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
1-2005 340 - 49Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 50Course Series 340v3.2 (c)2005 Scott Baxter
Forward MAC Contents
RA: Reverse Activity• The AP must manage its reverse traffic loading to keep the noise
level manageable• Reverse noise is directly proportional to the speed at which
mobiles transmit on the reverse link• When noise is too high, the AP can throttle back all the ATs
DRC Lock• This forward channel contains a stream of bits indicating whether
the network currently will allow the mobile to transmit requests on the reverse DRC channel; timing and signal quality conditional parameters are also involved
• The DRC Lock bits and DRC Lock state is independent per sector. A mobile should not transmit DRC requests to a sector sending DRC Lock indication, but may transmit DRC requests to other sectors in its active set
RPC: Reverse Power Control bits instruct the mobile to increase or decrease its transmit power by a programmable increment, in muchthe same way as in IS-2000. The rate is 600 bps.
AP
Reverse MAC Channel Contents
The Reverse MAC channel contains two streams of informationDRC Data Rate Control channel is used by the AT to request the data rate and desired sector
• Data rate is requested using 8-ary bi-orthogonal coding• Desired sector is requested using 8-ary Walsh cover• Each DRC channel slot contains 1024 chips to facilitate reliable
detection• DRC messages start at the center of a slot to minimize the
delay between C/I estimation and the start of AP transmissionRRI Reverse Rate Indicator channel identifies up to 8 different desired reverse data transmission rates
• 8-ary orthogonal code is used to indicate rates• The RRI symbol is transmitted 32 times in each frame• RRI symbols are inverted in the last half of the frame to make
synchronization easier
1-2005 340 - 51Course Series 340v3.2 (c)2005 Scott Baxter
How the DRC Channel Operates
The AT estimates the forward channel C/I and identifies the feasible data rate and the requested sector to be usedThe AT sends this information to the AP on the DRC channelOnly the requested sector will transmit packets to this ATThe requested sector sends a data packet including preamble to the AT at the rate requested by the DRC in the immediately preceding slotAfter the packet transmission is initiated, it must be continued until the payload has been fully transmitted
1-2005 340 - 52Course Series 340v3.2 (c)2005 Scott Baxter
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!
1-2005 340 - 53Course Series 340v3.2 (c)2005 Scott Baxter
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
1-2005 340 - 54Course Series 340v3.2 (c)2005 Scott Baxter
Construction of a Forward Link Packet
Sub-packet
0
Sub-packet
1
Sub-packet
2
Sub-packet
3
Sub-packet
0Data
Packet Encoding Inter-leaving
bits symbols
Physical Layer Packets encoded, interleaved, broken into subpackets• each subpacket is a unique coded representation of the packet
Each subpacket is sent independently during one slot• Subpackets are sent in sequential order with a three-slot gap between
successive subpacketsPacket
Subpacket00
otherpkts
01
02
03
10
otherpkts
otherpkts.
otherpkts.
otherpkts.
otherpkts.
otherpkts.
otherpkts
otherpkts
otherpkts
otherpkts
otherpkts
One Slot
Forward
ChannelTraffic
The receiver combines successive subpackets until it finally decodes the complete packet contents
• then sends an “ACK” to cancel any remaining unneeded subpackets• this Hybrid ARQ (HARQ) process gives “incremental redundancy”
1-2005 340 - 55Course Series 340v3.2 (c)2005 Scott Baxter
Multislot Packet Timing, Normal Termination
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
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
1-2005 340 - 56Course Series 340v3.2 (c)2005 Scott Baxter
Multislot Packet Timing, Early Termination
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
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
1-2005 340 - 57Course Series 340v3.2 (c)2005 Scott Baxter
Multiple ARQ Instances
Packet 0Subpackets
0 1 2 3Data
PacketsEncoding
andScrambling
Inter-leaving
bits symbols Packet 1Subpackets
0 1 2 3
Packet 2Subpackets
0 1 2 3
Packet 3Subpackets
0 1 2 3
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
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
1-2005 340 - 58Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Power Control
RX RF
TX RF Digital
AP
SNR target
Stronger thantarget SNR?
ReverseRF
600 bits per second
Access Terminal
OpenLoop
ClosedLoop
Digital
1xEV-DO reverse link power control is similar to IS-95/IS-20001xEV-DO power control holds the mobile pilot to a constant S/N ratio at the Access Point
• The DRC, RRI, and ACK channels are also controlled• The ideal ratio of reverse pilot to other channels also depends
on the reverse data ratePower control bits are sent on the forward MAC channel
• one bit per slot (that’s 600 per second), sent as four symbols --one in each of the MAC periods of that slot
1-2005 340 - 59Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Rate ControlReverse Rate Control
1-2005 340 - 60Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Rate Control
This process uses variables: MaxRate, CurrentRate, CombinedBusyBit, and CurrentRateLimit.CurrentRateLimit is set initially to 9.6kbps. After the AT receives a BroadcastReverseRateLimit message or a UnicastReverseRateLimitmessage it updates the CurrentRateLimit value as follows:
• If the RateLimit value in the message is less than or equal to the CurrentRateLimit value, the AT immediately sets CurrentRateLimit to the RateLimit value in the message.
• If the RateLimit value in the message is greater than CurrentRateLimit value, the AT waits one frame (16 slots) before setting CurrentRateLimit to the RateLimit value in the message.
If the last received reverse activity bit is set to ‘1’ from any sector in the AT’s active set, the AT sets CombinedBusyBit to ‘1’. Otherwise, the AT sets CombinedBusyBit to ‘0’. CurrentRate is set to the rate at which the AT was transmitting data immediately before the new transmission time. If the AT was not transmitting data immediately before the new transmission time, the AT sets CurrentRate to 0. The AT sets the variable MaxRate based on its current transmission rate, the value of the CombinedBusyBit, and a random number. The access terminal shall generate a uniformly distributed random number x, 0 < x < 1, using the procedure specified in 15.5. The AT evaluates the expression shown in the table, usoing the values of CurrentRate, CombinedBusyBit, and Condition.
• If the Condition is true, the AT sets MaxRate to the MaxRateTrue value for the corresponding row in the Table.
• Otherwise, the AT sets MaxRate to the MaxRateFalse value for the corresponding row in the Table
1-2005 340 - 61Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Rate Control Table
1-2005 340 - 62Course Series 340v3.2 (c)2005 Scott Baxter
Rate Constraints
The access terminal shall select a transmission rate that satisfies the following constraints:
• The access terminal shall transmit at a rate that is no greater than the value of MaxRate.
• The access terminal shall transmit at a rate that is no greater than the value of CurrentRateLimit.
• The access terminal shall transmit at a data rate no higher thanthe highest data rate that can be accommodated by the available transmit power.
• The access terminal shall not select a data rate for which the minimum payload length, as specified in Table 11.8.6-1, is greater than the size of data it has to send.
1-2005 340 - 63Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Rev. A1xEV-DO Rev. A
1-2005 340 - 64Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Rev. A Design Objectives
To enable multimedia services• high-speed upload of multimedia files and attachments • interactive gaming• IP-based services such as Voice over Internet Protocol (VoIP).
To allow real-time conversational services• push to talk, • video telephony • instant multimedia -- an extension of push to talk that combines
immediate voice with simultaneous delivery of video and pictures. multimedia multicasting using QUALCOMM's “Platinum Multicast”
• enables high-quality video/audio to many users simultaneously.Peak forward link data rates of 3.1 Mbps Peak reverse link data rates of 1.8 Mbps Optimized packet data service
• one of lowest costs per bit compared to other wireless technologies.
1-2005 340 - 65Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Rev. A Differences
Everything we’ve seen thus far applies to 1xEV-DO Revision 0.1xEV-DO Rev. A is now officially standardized and ready for commercial deployment
1-2005 340 - 66Course Series 340v3.2 (c)2005 Scott Baxter
Forward Link Enhancements in 1xEV-DO Rev. A
Forward Link Enhancements• Peak rates increased from 2.4 Mbps to 3.1 Mbps• Multi-user packet support• Small payload sizes (128, 256, 512 bits) improve frame fill efficiency• The DRC channel functions are broken out into two channels
– DRC retains rate control indication– new Data Source Control (DSC) Channel shows desired serving cell
• Minimizes interruptions due to server switching on FL
1-2005 340 - 67Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Link Enhancements in 1xEV-DO Rev. A
Reverse Link Enhancements• Higher data rates and finer quantization
• Data rates from 4.8 kbps to 1.8 Mbps with 48 payload sizes• 4 slots/sub-packets regardless of payload size (6.66 ms)• Modulation:
– Low rates: 1 walsh channel, BPSK modulation– Medium rates: 1 walsh channel, QPSK modulation– High Rates: 2 walsh channels, QPSK modulation– Highest Rate: 2 walsh channels, 8PSK modulation
• Hybrid ARQ using fast re-transmission (re-tx) and early termination• Flexible rate allocation: each AT has autonomous and scheduled mode• Efficient VOIP support• 3-channel synchronous stop-and-wait protocol• The mobile can use higher power and finish earlier when transmitting
packets of applications requiring minimum latency
1-2005 340 - 68Course Series 340v3.2 (c)2005 Scott Baxter
Available Link Rates in 1xEV-DO Rev. AFORWARD LINK REVERSE LINK
1-2005 340 - 69Course Series 340v3.2 (c)2005 Scott Baxter
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+8.3+11.3
Modu-lationQPSKQPSKQPSKQPSKQPSKQPSKQPSKQPSKQPSKQPSK
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 slots 16 slots1/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
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.
Basic Access TerminalArchitecture and Operation
Basic Access TerminalArchitecture and Operation
1-2005 340 - 70Course Series 340v3.2 (c)2005 Scott Baxter
How Does an Access Terminal Work?
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
1-2005 340 - 71Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Forward Link: AT Rake Receivers
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!!
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
1-2005 340 - 72Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Reverse Link: Soft Handoff
AP
AP
Access TerminalRake Receiver
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
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
1-2005 340 - 73Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Route Update Mechanics
??
AP
DO-RNC
AP
Sel.
Access TerminalRake Receiver
RFPN WalshPN WalshPN Walsh
SearcherPN W=0
Σ userdata
Pilot Ec/Io
PN Walsh
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
1-2005 340 - 74Course Series 340v3.2 (c)2005 Scott Baxter
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
1-2005 340 - 75Course Series 340v3.2 (c)2005 Scott Baxter
Format of Traffic Channel Assignment Message
Pilot PN Channel SrchWinSize SrchWinOffsetNeighbor Structure Maintained by the AT
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
1-2005 340 - 76Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Network Architecture1xEV-DO Network Architecture
1-2005 340 - 77Course Series 340v3.2 (c)2005 Scott Baxter
CDMA Network for Circuit-Switched Voice Calls
t1t1 v CESEL
t1PSTN
BTS
(C)BSC/Access ManagerSwitch
The first commercial IS-95 CDMA systems provided only circuit-switched voice calls
1-2005 340 - 78Course Series 340v3.2 (c)2005 Scott Baxter
CDMA 1xRTT Voice and Data Network
t1t1 v CESEL
t1
PDSNForeign Agent
PDSNHome Agent
BackboneNetworkInternet
VPNs
PSTN
AuthenticationAuthorization
AccountingAAA
BTS
(C)BSC/Access ManagerSwitch
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
1-2005 340 - 79Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO Overlaid On Existing 1xRTT Network
t1t1 v CESEL
t1
PDSNForeign Agent
PDSNHome Agent
BackboneNetworkInternet
VPNs
PSTN
AuthenticationAuthorization
AccountingAAA
BTS
(C)BSC/Access ManagerSwitch CE
DORadio
NetworkController
DO-OMC
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 solutions1-2005 340 - 80Course Series 340v3.2 (c)2005 Scott Baxter
Lucent 1xEV-DO ArchitectureLucent 1xEV-DO Architecture
1-2005 340 - 81Course Series 340v3.2 (c)2005 Scott Baxter
Lucent 1xEV-DO Radio Access Network (RAN)
T-1/E-1Ethernet
RF
Internet
AAAServer
AP
OMP FXElement Management
System
Router
FlexentMobilityServer
DownlinkInput
Router
DownlinkInput
Router
UplinkInput
Router
UplinkInput
Router
FlexentMobilityServer
PacketData
ServingNode
(PDSN)
User ATs(Access Terminals)
RFAP
AP
AP
A Lucent 1xEV-DO Radio Access Network (RAN) includes• 1xEV-DO base stations and the• 1xEV-DO Flexent® Mobility Server (FMS).
The 1xEV-DO equipment may be collocated with IS-95 and/or 1xRTT equipment, creating 1xEV-DO/IS-95 and 1xEVDO/3G-1X combination base stations.
1-2005 340 - 82Course Series 340v3.2 (c)2005 Scott Baxter
Details of Lucent RAN Elements
T-1/E-1Ethernet
RF
Internet
AAAServer
AP
OMP FXElement Management
System
Router
FlexentMobilityServer
DownlinkInput
Router
DownlinkInput
Router
UplinkInput
Router
UplinkInput
Router
FlexentMobilityServer
PacketData
ServingNode
(PDSN)
User ATs(Access Terminals)
RFAP
AP
AP
The PDSN maintains the link layer to the AT• it terminates the PPP link protocol with mobile• it serves as the Foreign Agent for Mobile IP functionality
The AAA server does authentication, authorization, and accounting• it authenticates terminal equipment users when they establish
connections• it stores and forwards billing information of customers’ data usage
1-2005 340 - 83Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO in Lucent Flexent Mod Cell Cabinets
Lucent Mod Cell cabinets can support up to three IS-95 or 1xRTT carriers on three sectors1xEV-DO CDMA Digital Modules (CDM) can be mixed with conventional CDMs in the same cabinetthe same RF hardware (filters, amplifiers, other RF components) can be used for IS-95, 1xRTT, and 1xEV-DO
1-2005 340 - 84Course Series 340v3.2 (c)2005 Scott Baxter
Lucent CDMA Digital Module (CDM) Configurations
At upper left is a CDM for conventional IS-95 / 1xRTT service. It includes
• CRC CDMA Radio controller• up to 6 CCU CDMA Channel Units• PCU power converter module• CBR CDMA Baseband Radio
At lower left is a CDM for 1xEV-DO• it must be occupy the leftmost slot• all CCU packs are removed and
replaced by a single 1xEV-DO modem (EVM) occupying 2 slots
• the CRC must be 44WW13D or later
1-2005 340 - 85Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO in Lucent Mod Cell 4.0 CabinetsThe Mod Cell 4 cabinet comes in many variationsInstead of per-carrier dedicated CDMs, resources are pooledURCs (Universal Radio Controllers) are used to steer data for each carrier to EVMs for EVDO or CMUs for IS-95/1xRTT.
• in a mixed-mode system, a URC is required for EVDO and a URC for IS-95/1xRTT
The modulated signal from a 4.0 EVM or CMU is upconverted to the RF carrier frequency by the UCR
• each UCR (Universal CDMA Radio) can handle up to three carriers
UniversalRadio
Controller(URC) Evolution
Modem(4.0 EVM) Universal
CDMARadio(UCR)CDMA
ModemUnit
(CMU)Universal
RadioController
(URC)ECP
FMS
Antenna
Carr1
Carr2, 3
Digital Shelf Flow
1-2005 340 - 86Course Series 340v3.2 (c)2005 Scott Baxter
Lucent 1xEV-DO Flexent Mobility Server (FMS)
The Flexent Mobility Server is the heart of the Radio Access NetworkIt provides four processors running the 1xEV-DO Application Processor (DO-AP), which provides the Packet Controller Function (PCF)The PCF provides air link and radio resource management to implement 1xEV-DO user sessions, including the dormant state and other DO-specific features
1-2005 340 - 87Course Series 340v3.2 (c)2005 Scott Baxter
Motorola 1xEV-DO ArchitectureMotorola 1xEV-DO Architecture
1-2005 340 - 88Course Series 340v3.2 (c)2005 Scott Baxter
Motorola 1xEV-DO System Architecture
MSC
MM/SDU
OMC-IP
OMC-R 1x-AN
1x-BTS
OMC-DO
BSC-DO
AN-DO
MCC-DO
AAAAN-AAA
PDSNs
HAsPacket CoreNetwork
VPU
1xEV-DOIS-95/1xShared 1x/DO
ConnectionsElementsExisting IS-95New 1xEV-DOShared IS-95/DO
New 1xEV-DO carrier appears as a standard carrier addition to existing network elements
• new MCC-DO cards and OMC-R database revisions needed• AAA and PDSN need software upgrades
1-2005 340 - 89Course Series 340v3.2 (c)2005 Scott Baxter
New Motorola 1xEV-DO Network Elements
MSC
MM/SDU
OMC-IP
OMC-R 1x-AN
1x-BTS
OMC-DO
BSC-DO
AN-DO
MCC-DO
AAAAN-AAA
PDSNs
HAsPacket CoreNetwork
1xEV-DOIS-95/1xShared 1x/DO
VPU
ConnectionsElementsExisting IS-95New 1xEV-DOShared IS-95/DO
MCC-DO (Multi-Channel Controller - Data Only)AN-DO (Access Node - Data only)
• CR (Consolidation Router) Similar in function to the 1x-AN MGX • LSW (Layer 3 Switch) Similar in function to the 1x-AN CATs
BSC-DO (Base Station Controller-Data Only)• Mobility functions like 1x MM - Packet Control & Selection – like SDU
OMC-DO (Operations & Maintenance Center - Data Only)LMT (Local Maintenance Terminal)
1-2005 340 - 90Course Series 340v3.2 (c)2005 Scott Baxter
Motorola 1xEV-DO Block Diagramand Network Upgrade Summary
CR
BSC-DO
PDSN
OMC-DO
LSW
BTS
RF
Fron
t End
1x Modems
DO BBX
1x BBX
MCC-DO
AN-AAA
BTSR
F Fr
ont E
nd
1x Modems
DO BBX
1x BBX
MCC-DO
T1 or E1
AN-DO
IS-2000 1xEV-DOTool LMF LMT
MCC-1XGLI (Traffic)
AN (MGX8800) CRAN (Catalyst 6509) LSW
BSC CBSC BSC-DOOMC-R
UNOIP Network
Telephone Network MSC/HLR Not RequiredData Network Not Required AAA
BTS frame & CCP shelf
BTS
PDSN (Note 1)
GLI (Control)
MCC-DO
OMC-DO
AN
O&M
LPABBX-1X
1-2005 340 - 91Course Series 340v3.2 (c)2005 Scott Baxter
Motorola MCC-DO Functions
1xEV-DO Modem• 1 carrier, 3 sectors per
MCC-DO card• Supports 59 channels per
sectorSpan Interface
• Up to 3 Active Span lines per MCC-DO
• Most operators will generally deploy with 2 spans per BTS
BTS provides control:• SCAP messaging• Redundant BBX Selection• Enhanced BBX interface
CR
BSC-DO
PDSN
OMC-DO
LSW
BTSR
F Fr
ont E
nd
1x Modems
DO BBX
1x BBX
MCC-DO
AN-AAA
BTS
RF
Fron
t End
1x Modems
DO BBX
1x BBX
MCC-DO
T1 or E1
AN-DO
MCC- DO
1-2005 340 - 92Course Series 340v3.2 (c)2005 Scott Baxter
Motorola 1xEV-DO AN-DO Elements
Consolidation Router (CR)• Performs span aggregation
for DO access points –Similar to 1x MGX
• 1 – 2 CR frames per BSC-DOLayer 3 Switch (LSW)
• Performs IP transport across DO Core Network – Similar to 1x CAT
• Two CAT4006 Cages per frame
• 1 LSW frame will serve all 1xEV-DO frames in a typical MTSO
CR
BSC-DO
PDSN
OMC-DO
LSW
BTS
RF
Fron
t End1x Modems
DO BBX
1x BBX
MCC-DO
AN-AAA
BTS
RF
Fron
t End1x Modems
DO BBX
1x BBX
MCC-DOT1 or E1
AN-DO
CR LSW
1-2005 340 - 93Course Series 340v3.2 (c)2005 Scott Baxter
Motorola BSC-DO FunctionsBSC Functionality:
• RF-scheduling, channel, connection, mobility management, security
Access Network Control• Radio Resource Management• Connection Control• Access control / Collision control• Handoff control
Packet Control and Session Control• Transmission of packet data
between MCC-DO and PDSN• Packet Data Control• PDSN selection• Provides Authentication
information to AAA• Management of Data Session• Support up to 80 MCC-DO cards
per a BSC-DO1 OMC-DO per each BSC-DO
CR
BSC-DO
PDSN
OMC-DO
LSW
BTSR
F Fr
ont E
nd
1x Modems
DO BBX
1x BBX
MCC-DO
AN-AAA
BTS
RF
Fron
t End
1x Modems
DO BBX
1x BBX
MCC-DOT1 or E1
AN-DO
1-2005 340 - 94Course Series 340v3.2 (c)2005 Scott Baxter
Motorola 1xEV-DO Network Elements: OMC-DO
OMC-DO provides GUI based O&M functions
• Status Management• Fault Management• Configuration Management• Software Management• System Parameter
Management• Performance Monitoring• CDL collection• Diagnostic & System Test• Logging• Health Check
CR
BSC-DO
PDSN
OMC-DO
LSW
BTS
RF
Fron
t End
1x Modems
DO BBX
1x BBX
MCC-DO
AN-AAA
BTS
RF
Fron
t End
1x Modems
DO BBX
1x BBX
MCC-DOT1 or E1
AN-DO
DO network element manager• Manages BSC-DO and MCC-
DO• Ethernet interface to BSC-
DO• Supports network
management applications (fault, alarm, performance, configuration)
1-2005 340 - 95Course Series 340v3.2 (c)2005 Scott Baxter
Nortel 1xEV-DO ArchitectureNortel 1xEV-DO Architecture
1-2005 340 - 96Course Series 340v3.2 (c)2005 Scott Baxter
A Typical Nortel CDMA2000 SystemProviding 1xRTT Voice, Data, and 1xEV-DO
1-2005 340 - 97Course Series 340v3.2 (c)2005 Scott Baxter
A Typical Nortel CDMA2000 SystemProviding Only 1xRTT Voice, Data
1-2005 340 - 98Course Series 340v3.2 (c)2005 Scott Baxter
A Typical Nortel CDMA2000 SystemProviding 1xEV-DO Only
1-2005 340 - 99Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 100Course Series 340v3.2 (c)2005 Scott Baxter
Nortel Multiple Backhaul and Configuration Possibilities
Nortel Univity® Indoor Metrocell
Univity® CDMA Metro Cell Indoor
Univity® Metro Cell can support:
• up to six CDMA 1.25 MHz carrier frequencies
• up to three sectors. High Power Amplifiers and Low Noise Amplifiers are housed in an external unit
• the Multi-Carrier Flexible Radio Module (MFRM)
• MFRM may be mast mounted to improve AP RF link budget
Base Transceiver System (AP)
1-2005 340 - 101Course Series 340v3.2 (c)2005 Scott Baxter
Nortel Metrocell LD(for rural sites)
Key Feature – small size, fits in any cornerConfigurations
• 1-3 Carrier OMNI• Expandable to 3 sectors• Single carrier high power
Power source• + 24VDC available
Standard Metro Cell modules
•Radio Module
•AC Rectifier
•Fan tray
•CORE•CM
•GPSTM
•XCEM/•DOM
•36”(0.91m)
•24”(0.61m)
•MiniBIP
Metro Cell LD – Rack MountedSupporting 3 sectors
1-2005 340 - 102Course Series 340v3.2 (c)2005 Scott Baxter
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
1-2005 340 - 103Course Series 340v3.2 (c)2005 Scott Baxter
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
1-2005 340 - 104Course Series 340v3.2 (c)2005 Scott Baxter
Nortel DO-RNC Functionality
DO-RNC functions similar to CDMA-2000 BSC and packet control unit:• handoff processing (reverse only), sector selection (forward only)• selection of reverse link traffic frames• data session connected/dormant transition management• termination of the A10/A11 RP interface to the PDSN• application, stream, session and connection layer management• radio link protocol (RLP)• connection control of access terminals• resource management, mobility management• packet control function (PCF)• data flow control
DO-RNC switch-like functions• service negotiation• paging and access channel message termination• forwards MAC-layer packets to the best-serving DOM• data-environment-specific performance logging
1-2005 340 - 105Course Series 340v3.2 (c)2005 Scott Baxter
Nortel T1/E1 Aggregator Functions
The T1/E1 aggregation router is based on the Shasta BSN5000
• this requires a T1 or E1 MUX co-located with the Shasta to terminate the T1/E1s and convert them into channelized DS-3 or channelized STM-1 (single mode), for connection to the Shasta BSN
The T1/E1 aggregation router is co-located with the RNCs
• aggregates all T1/E1s from the backhaul network to the RNC
• each DOM can have up to four T1/E1 links
• the DO-RNC does not accept T1/E1 signals
• T1/E1 aggregation router converts T1/E1 signals into ethernet links
TN-1X
T
STM-1
1-2005 340 - 106Course Series 340v3.2 (c)2005 Scott Baxter
The Nortel DO-EMS(Data-Only Element Management System)
The DO-EMS consists of • Hardware (the server) and Software (the client)
The DO-EMS Provides Operation, Administration, Maintenance, and Provisioning (OAM&P) for the 1xEV-DO radio access network (RAN)The existing BSS Manager (BSSM) continues management of the 1xEV-DO DOM module in a MetroCell APThe DO-EMS is a stand-alone platform providing OAM&P functionality within the CDMA2000 1xEV-DO network only. Its functions include:
• collecting, reporting, and managing DO-RNC and DOM alarms
• collecting and storing OMs from DO-RNC and DOM
• administering 1xEV-DO carrier/sector neighbor lists, including limited diagnostic capabilities (reciprocal neighbor analysis, etc)
The DO-EMS, DO-RNC and DOM provide overload controls for management of OAM&P messaging traffic during system events
1-2005 340 - 107Course Series 340v3.2 (c)2005 Scott Baxter
The Nortel DO-EMS Server and ClientThe DO-EMS server is a Sun Netra20
• normally located in the central office with the BSC/DO-RNC
Software modules on the server perform:• auto-discovery• configuration management• security management• fault management• performance management
DO-EMS Client / Management Terminal• since the Netra20 is a “headless” server, a
terminal is required for monitor, keyboard and mouse functionality
• The terminal connects to the DO-EMS to perform all required OAM&P functions for the 1xEV-DO network
• The management terminal is a Sun Blade150
• alternatively, customers may use a PC running an “X-Windows” application
1-2005 340 - 108Course Series 340v3.2 (c)2005 Scott Baxter
The Nortel DO-EMS Client
The DO-EMS client is web-based
• runs in standard web browsers
• offers network administrators a familiar, easy-to-use interface
• provides robust configuration, fault and performance management tools
1-2005 340 - 109Course Series 340v3.2 (c)2005 Scott Baxter
Nortel’s Univity® CDMA PDSN
PDSN• The Univity® CDMA PDSN provides CDMA radio network packet data
access to the Public Data Network (PDN) and is integrated on theShasta BSN 5000 chassis. With the addition of the AT IP access model, a Foreign Agent (FA) and Home Agent (HA) are required. The FA is always integrated onto the Shasta BSN with the Univity® PDSN resulting in the PDSN/FA.
Component BreakdownThe Shasta BSN is comprised of several components including the
Subscriber Service Gateway (SSG), the IP Services Operating System (iSOS) and the Service Creation System (SCS) as defined below:
• SSG - is the hardware platform (Shasta 5000 chassis)• iSOS - offers high-touch services scalability and extensibility• SCS - is a graphical management and provisioning tool allowing the
service provider to quickly and efficiently provision thousands of subscriber profiles through its GUI. It provides scalable centralized management for PDSNs covering a large range of geographical locations.
1-2005 340 - 110Course Series 340v3.2 (c)2005 Scott Baxter
Nortel Shasta BSN Hardware DescriptionHardware DescriptionThe Shasta BSN chassis consists of a card cage with 14 slots for cards, a fan tray for cooling; power entry and distribution and the backplane. The chassis mounts in a standard 19” rack and requires a -48VDC power source. The fan tray and all cards are all hot-swappable.All Shasta BSN components are new in the CDMA network and are required specifically for the CDMA 3G architecture. The requiredcomponents are as follows:
• Line Card (LC)• Subscriber Service Module (SSM II)• Subscriber Service Card (SSC)• Control and Management Card (CMC)• Switch Fabric Card (SFC)• Shasta Chassis (BSN)• Service Creation System (SCS)
– Server and Client• Shasta BSN Software• Cabinet
1-2005 340 - 111Course Series 340v3.2 (c)2005 Scott Baxter
Nortel’s Passport 8600 Routing Switch
1-2005 340 - 112Course Series 340v3.2 (c)2005 Scott Baxter
Passport 8600 Routing Switch• delivers high-density Layer 2 and Layer 3 wire-
speed switching and routing over copper and fiber media.
• switching architecture capable of delivering 128 Gbps of capacity, scaling to 256 Gbps in the future.
Supported interfaces include 10/100/1000BaseT autosensing and ATM
• Supports up to 384 10/100 TX Ports• Supports up to 192 100 FX Ports• Supports up to 64 1000 SX Ports• STM1/OC3 (up to 32 Ports)
Redundant power supplies and hot-swappable modules are also part of the product platform.
• Both 6 and 10 Slot Chassis are available. The price in Appendix A, B is applicable to 6 slot Chassis.
Core switching and processing• Routing switch fabric/CPU module—High-
performance Layer 2 and Layer 3 traffic switching. One per chassis; two if redundancy is desired
Nortel Passport 8600 Connectivity
Ethernet/Gigabit Ethernet• 48-port auto-sensing 10Base-T/100Base-TX Ethernet Routing Switch module (RJ-45)• Passport Routing Switch Module 8632TX
– 32-port mixed-media module for 10Base-T/100Base-TX switching and routing– two slots for Gigabit Interface Converters (GBICs), high port density
• 24-port 100Base-FX Fast Ethernet Routing Switch module (MT-RJ) long runs – 2km multimode
• 16-port 1000Base-SX Gigabit Ethernet Routing Switch module (MT-RJ)– Up to 128 Gigabit Ethernet ports per 10-slot chassis
• 8-port 1000Base-T Gigabit Ethernet Routing Switch module (RJ-45) – over cat. 5 copper to 100m
• 8-port 1000Base-SX Gigabit Ethernet Routing Switch module (SC) -for multimode fiber• 8-port Gigabit Ethernet Routing Switch module
– plug-in GBICs with SC connectors can mix and match interface types on a single module using multi-mode or single-mode fiber. GBICs available in short distance (SX), long distance (LX) and extended distance (XD and ZX)
• One- and two-port auto sensing 10-Gigabit Ethernet Routing Switch modules, full-featured LAN/WAN connectivity with full functionality and intelligence of the Passport 8600
ATM/SONET/SDH• 2-slot MDA Baseboard—Supports up to eight OC-3/STM1 for ATM interface
applications such as permanent virtual circuit VLAN bridging and routing, maintaining QoS prioritization.
1-2005 340 - 113Course Series 340v3.2 (c)2005 Scott Baxter
Nortel CDMA Univity®Base Station Controller EBSC
The Univity® CDMA Base Station Controller CBRS is a scalable and cost reduced IP enabled Base Station ControllerEliminates the need for separate BIU and CIS cabinets in the BSC for 1xEV-DO non-MTX systemsKey Features:• Scalable from very low to very high
capacity through module additions• Multiple frames deployed for
configuration flexibility
PP15K Fiber Tray
PP15K Breaker InterfacePanel
Cable Trough
0 1 2 3 4 5 6 7
8 9 1
0
1
1
1
2
1
3
1
4
1
5
Cable Trough
Cable Trough
Cable Trough
Cable Consolidation and Multiplexing Chassis
24pBCNW Functional Processor (NTPB11AA)
11pMSW Functional Processor (NTPB10AA)
CP3 - Control Processor (NTHR06CA)
Optional - 2nd Enhanced BSC Frame Connectivity
GPSTM - Global Positioning Satellite Timing Module (NTPB15AA)
Cable Consolidation and Multiplexing Chassis (NTPB13AA)
GPSTMGPSTM
1-2005 340 - 114Course Series 340v3.2 (c)2005 Scott Baxter
Nortel CDMA Univity®Base Station Controller EBSC
The Univity® CDMA BSC CBRS is built on the Passport 15K and includes two new Functional Processors (FPs), the 11pMSW FP and the 24pBCNW FP , along with a Cable Consolidation and Multiplexing Chassis
• The 11pMSW FP contains 3 OC-3/STM-1 ports. One (1) OC-3/STM-1 port is channelized and contains T1/E1/T3/E3 channels to carry AP or ISSHO traffic. The unchannelized ports can be configured as OC-3c to support interfaces to the DISCO or BSS Manager. In these instances they can be configured as OC-3c in North America or STM-1 for international installations. The 11pMSW FP provides 8 T1s for connectivity to the LPP.
• The 24pBCNW FP contains 24 LVDS ports for connectivity to the SBS shelves.
The Cable Consolidation and Multiplexing Chassis manages connectivity between the new 24pBCNW FP to current SBS shelves
• GPSTM to the 24WpBCNW FP• T1s/E1s on the 11pMSW FP to the LPP• The Univity® CDMA BSC CBRS can be added to current BSCs
allowing for expanding port and Erlang capacity
1-2005 340 - 115Course Series 340v3.2 (c)2005 Scott Baxter
Pre-EBSC Hardware Requiredfor Nortel 1xEV-DO Non-MTX Systems
Not Required!
no voice users,
no vocoders
UNIVITY® EBSC COMBINES
BIU, CIS, BSM IN A SINGLE CABINET
1-2005 340 - 116Course Series 340v3.2 (c)2005 Scott Baxter
Nortel’s BSS Manager (BSSM)within the Univity® EBSC
The BSS Manager consists of quad Ultra Enterprise 450 Servers• UltraSPARC IV processor cards • High Speed Serial Interface card interconnects to the BSC• 31 Gigabytes of mirrored disk space• Ethernet and LAN access.
The BSS Manager is a highly reliable platform, provisioned with an Active and a Standby unit.
• Constant heartbeat and monitoring are performed between the Active and Standby systems.
• System initiated (automatic) SWACT (Switch of activity) occurs from Active to Standby when the active unit experiences critical hardware/software fault.
• User or operator SWACT is also supported. • Redundant Ethernet links are provisioned between the two BSS
Manager servers• redundant links are also provisioned from BSS Manager to CIS (a
communication component within the Univity® BSC)
1-2005 340 - 117Course Series 340v3.2 (c)2005 Scott Baxter
Nortel BSSM:CDMA Base Station Subsystem Manager
The CDMA BSS Manager provides the Operations, Administration, and Maintenance (OA&M) interface for the Univity® BSC and Univity® AP. Within the context of TMN’s (Telecommunication Management Network) functional layer approach, the BSS Manager is the Element Manager and is the operator’s primary interface into Nortel Networks' CDMA RF network. The BSS Manager platform comprises the operating environment, hardware, and application interfaces, supporting four areas of the FCAPS model (Fault, Configuration, Accounting, Performance, and Security).Fault management primarily deals with the alarms of the CDMA network. Alarms are generated by the subsystem when there is a failure of the hardware/service or when there is a degradation of the hardware/service due to certain external environmental factors. The BSS Manager’s primary responsibility is to log, report, and manage the alarm events from its managed subsystems. ⎯ Configuration management controls the way in which the system provides service. It allows specification of configuration information, collects data from and provides data to the various network elements and the connections between those elements. Configuration management is primarily responsible for supporting network planning, installing, interconnecting, and establishing NE equipment, connections, and services.Performance management ensures that performance data is sent at regular intervals to the BSS Manager. Within the BSS Manager, two types of data are logged:Performance data, also referred to as Operational Measurements (OM) – statistical information about subsystem componentsDiagnostic Data - debugging information on messages among subsystems for troubleshootingSecurity management deals with security breaches (improper use) of network resources. Security management consists of software applications used to configure, control, create or delete the resources providing the services. Security Management also includes administration of security procedures and functions.
1-2005 340 - 118Course Series 340v3.2 (c)2005 Scott Baxter
EV-DO-Specific Nortel Documentation
1xEV-DO Release 2.0 Document Document
Relevance Number Revision Title 1 411-2133-012 1.11 CDMA2000 1xEV-DO System Overview Guide
1 411-2133-109 1.09 CDMA2000 1xEV-DO NBSS Delta MOs, Logs, OMs and
Alarms Reference Manual
1 411-2133-126 1.1 CDMA2000 1xEV-DO Element Management Subsystem
(EMS) Recovery and Upgrade Guide
1 411-2133-529 1.14 CDMA2000 1xEV-DO Element Management Subsystem
(DO-EMS) Administrator's Guide 1 411-2133-532 1.08 1xEV-DO DO-RNC Administration Guide
1 411-2133-822 1.02 CDMA2000 1xEV-DO Configuration Parameters Reference
Guide 1 411-2133-917 1.1 1xEV-DO Data Only Module (DOM) User Guide
1 411-2133-924 1.1 CDMA2000 1xEV-DO OMs and Performance Measurement
Reference Guide
1 411-2133-925 1.13 CDMA2000 1xEV-DO Command Line Interface (CLI)
Reference Guide 1 411-2133-926 1.08 CDMA2000 1xEV-DO Logging Message Reference Guide
1 411-2133-927 1.12 CDMA2000 1xEV-DO Element Management Subsystem
(DO-EMS) User Guide 1 411-2133-929 1.08 1xEV-DO Script Tool User Guide 1 411-2133-932 1.1 1xEV-DO Deployment Guide
1.00 411-2133-111 04.06
CDMA Metro Cell Deployment Guidelines Reference Manual
1.00 411-2133-802 05.06
Shasta PDSN/FA and HA Customer Information Guide
1.00 411-2133-101 12.06
BSC Theory of Operations Handbook
1-2005 340 - 119Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO / 1xRTT Interoperability
1xEV-DO / 1xRTT Interoperability
1-2005 340 - 120Course Series 340v3.2 (c)2005 Scott Baxter
1xEV-DO/1xRTT Interoperability
The CDMA2000 1xEV-DO 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 will be provided• the 1xEV control channel will be able to carry 1xRTT pages too• this and other changes may make the “hybrid” mode
unnecessary and obsolete
1-2005 340 - 121Course Series 340v3.2 (c)2005 Scott Baxter
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, this is not possible
1-2005 340 - 122Course Series 340v3.2 (c)2005 Scott Baxter
Hybrid Mode Transition Scenarios
1: 1: 1:2 Deployment 1 Deployment 1 Deployment
EV-DO, F21xRTT, F1
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
1-2005 340 - 123Course Series 340v3.2 (c)2005 Scott Baxter
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
1-2005 340 - 124Course Series 340v3.2 (c)2005 Scott Baxter
Hybrid Dual-Mode Idle Operation1xRTT / 1xEV-DO Paging Interoperability
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
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
1-2005 340 - 125Course Series 340v3.2 (c)2005 Scott Baxter
Initial System Acquisition by Hybrid Mobile1x
RTT
A
ctiv
e1x
RTT
Id
le1x
EV-D
OId
le1x
EV-D
O
Act
ive
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 not search for
1xEV service again
1-2005 340 - 126Course Series 340v3.2 (c)2005 Scott Baxter
Initial System Acquisition by Hybrid Mobile1x
RTT
A
ctiv
e1x
RTT
Id
le1x
EV-D
OId
le1x
EV-D
O
Act
ive
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:
1-2005 340 - 127Course Series 340v3.2 (c)2005 Scott Baxter
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.
Traffic Mode,Data Transfer
AT data ready
AN data ready
1-2005 340 - 128Course Series 340v3.2 (c)2005 Scott Baxter
Transition In-Traffic: Lost EV-DO and 1xRTT1x
RTT
A
ctiv
e1x
RTT
Id
le1x
EV-D
OId
le1x
EV-D
O
Act
ive
Fade
IdleMode
Fade
Fade
CloseConnection
LostSignal!!
Use 1x PRL,Search for
1xRTTNo
SignalFound!!
Traffic Mode,Data Transfer
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
1-2005 340 - 129Course Series 340v3.2 (c)2005 Scott Baxter
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
Traffic Mode,Data Transfer
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?
1-2005 340 - 130Course Series 340v3.2 (c)2005 Scott Baxter
IS-871 For Session Interoperability
Lack of RF transition trigger definitions has been largely resolved by the “Hybrid Mode” of dual-mode terminalsThe situation is better regarding Session portability
• session interoperability are described in IS-871• although no RF triggers are described, the necessary steps are
defined for transition of packet sessions between EV and 1x networks
The following slides show the transitions defined in the IS-871 standard, along with the steps involved
1-2005 340 - 131Course Series 340v3.2 (c)2005 Scott Baxter
cdma2000 to HRPD Dormant Packet Data Session Handoff - Existing HRPD Session
1-2005 340 - 132Course Series 340v3.2 (c)2005 Scott Baxter
cdma2000 to HRPD Dormant Packet Data Session Handoff - Existing HRPD Session
a. The change of AN is indicated by the Location Update procedures as defined in [10]. b. The target AN sends an A9-Setup-A8 message, with Data Ready Indicator set to ‘0’, to
the target PCF and starts timer TA8-setup. The handoff indicator of the A9 Indicators IE shall be set to ‘0’.
c. If the PDSN address is not available to the target PCF by other means, the target PCF selects a PDSN for this connection using the PDSN selection algorithm as specified in [10]. The target PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message includes the MEI within the CVSE and the PANID and CANID within the NVSE. The target PCF starts timer Tregreq.
d. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target PCF. The target PCF stops timer Tregreq.
e. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd.
f. The source BSC/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd.
g. The source BSC/PCF sends an A11-Registration Request message with Lifetime set to zero, to the PDSN. The source BSC/PCF starts timer Tregreq.
h. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The source BSC/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.
i. The target PCF responds to the target AN with an A9-Release-A8 Complete message. The target AN stops timer TA8-setup. Note that this step can occur any time after step d.
1-2005 340 - 133Course Series 340v3.2 (c)2005 Scott Baxter
cdma2000 to HRPD Dormant Packet Data Session Handoff - New HRPD Session
1-2005 340 - 134Course Series 340v3.2 (c)2005 Scott Baxter
cdma2000 to HRPD Dormant Packet Data Session Handoff - New HRPD Session
a. The AT and the target AN initiate HRPD session establishment. During this procedure, the target AN does not receive a UATI for an existing HRPD session. Since no HRPD session exists between the MS/AT and target AN/PCF, an HRPD session is established where protocols and protocol configurations are negotiated, stored and used for communications between the MS/AT and the target AN. Refer to [10], Section 5, Session Layer.
b. The AT indicates that it is ready to exchange data on the access stream (e.g., the flow control protocol for the default packet application bound to the target AN is in the open state).
c. After HRPD session configuration the MS/AT initiates PPP and LCP negotiations for access authentication. Refer to [19]. d. The target AN/PCF generates a random challenge and sends it to the MS/AT in a CHAP Challenge message in accordance
with [22].e. When the target AN/PCF receives the CHAP response message from the MS/AT, it sends an Access-Request message on
the A12 interface to the target AN-AAA which acts as a RADIUS server in accordance with [25]. f. The target AN-AAA looks up a password based on the User-name attribute in the Access-Request message and if the
access authentication passes (as specified in [22] and [25]), the target AN-AAA sends an Access-Accept message on the A12 interface in accordance with [25] (RADIUS). The Access-Accept message contains a RADIUS attribute with Type set to 20 (Callback-Id), which is set to the MN ID of the AT. Refer to Section 2.3.2, AN-AAA Support.
g. The target AN/PCF returns an indication of CHAP access authentication success to the MS/AT. Refer to [22]. h. If the target AN supports the Location Update procedure, the target AN updates the ANID in the AT using the Location
Update procedure. The target AN may also retrieve the PANID from the AT if necessary. This step may occur any time after step a.
i. The AT indicates that it is ready to exchange data on the service stream. (E.g., the flow control protocol for the default packet application bound to the packet data network is in the open state).
j. The target AN/PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message includes the MEI within the CVSE and the PANID and the CANID within the NVSE. If PANID is not sent in step h, the target AN/PCF sets the PANID field to zero and the CANID field to its own ANID. The target AN/PCF starts timer Tregreq.
k. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and Lifetime set to the configured Trp value. If the PDSN has data to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target AN/PCF. The target AN/PCF stops timer Tregreq.
l. The PDSN initiates closure of the A10 connection with the source BSC/PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd.
m. The source BSC/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd. n. The source BSC/PCF sends an A11-Registration Request message with Lifetime set to zero, to the PDSN. The source
BSC/PCF starts timer Tregreq. o. The PDSN sends an A11-Registration Reply message to the source BSC/PCF. The source BSC/PCF closes the A10
connection for the MS/AT and stops timer Tregreq.
1-2005 340 - 135Course Series 340v3.2 (c)2005 Scott Baxter
HRPD to cdma2000 Dormant Packet Data Session Handoff
1-2005 340 - 136Course Series 340v3.2 (c)2005 Scott Baxter
HRPD to cdma2000 Dormant Packet Data Session Handoff
a. Upon transitioning to the cdma2000 system, the MS/AT transmits an Origination Message with DRS set to ‘0’ and with layer 2 acknowledgment required, over the access channel of the air interface to the target BSC/PCF to request service. This message may contain the SID, NID and PZID corresponding to the source PCF from which the MS/AT is coming, if this capability is supported by the air interface. If available, these values are used to populate the PANID field of the A11-Registration Request message that the target BSC/PCF sends to the PDSN.
b. The target BSC/PCF acknowledges receipt of the Origination Message with a Base Station Acknowledgment Order to the MS/AT.
c. The target BSC/PCF sends an A11-Registration Request message to the PDSN. The A11-Registration Request message includes the MEI within the CVSE and the PANID and the CANID within the NVSE. The target BSC/PCF starts timer Tregreq.
d. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication and the Lifetime set to the configured Trp value. If the PDSN has data to send, it includes the Data Available Indicator within the CVSE. The A10 connection binding information at the PDSN is updated to point to the target BSC/PCF. The target BSC/ PCF stops timer Tregreq. If the PDSN responds to the target BSC/PCF with the Data Available Indicator, the target BSC/PCFestablishes a traffic channel ([1] 2.15.5.4-1). In this case the remaining steps in this procedure are omitted.
e. The PDSN initiates closure of the A10 connection with the source AN/PCF by sending an A11-Registration Update message. The PDSN starts timer Tregupd.
f. The source AN/PCF responds with an A11-Registration Acknowledge message. The PDSN stops timer Tregupd.
g. The source AN/PCF sends an A11-Registration Request message with Lifetime set to zero, to the PDSN. The source AN/PCF starts timer Tregreq.
h. The PDSN sends an A11-Registration Reply message to the source AN/PCF. The source AN/PCF closes the A10 connection for the MS/AT and stops timer Tregreq.
1-2005 340 - 137Course Series 340v3.2 (c)2005 Scott Baxter
MS/AT Terminated Voice Call During Active HRPD Data Packet (Intra-PDSN/Inter-PCF)
1-2005 340 - 138Course Series 340v3.2 (c)2005 Scott Baxter
MS/AT Terminated Voice Call During Active HRPD Data Packet (Intra-PDSN/Inter-PCF)
a. The BS sends a Page Message containing the MS/AT address over the paging channel. The MS/AT may ignore this Page Message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed.
b. The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop. c. The AN sends an A9-AL Disconnected message to PCF2 to stop data flow and starts timer Tald9. d. Upon receipt of the A9-AL Disconnected message, PCF2 sends an A9-AL Disconnected Ack to the AN. The AN stops
timer Tald9. e. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c. f. The BS establishes a traffic channel. g. The BS sends an Alert with Info message to instruct the MS/AT to ring. h. The MS/AT and the cdma2000 system set up the data session for handoff from HRPD as a concurrent call service if the
MS/AT supports the concurrent call service capability and selects to handoff the data session from the HRPD to the cdma2000 system. Refer to [11], Section 2.17.2.1 steps (a) to step (g).
i. The BS sends an A9-Setup-A8 message to PCF1 to establish the A8 connection and starts timer TA8-setup. If the MS/AT has indicated the presence of data ready to send, the BS shall set the Data Ready Indicator to ‘1’; otherwise, the BS shall set the Data Ready Indicator to ‘0’.
j. PCF1 sends an A11-Registration Request message to the PDSN to establish the A10 connection to handoff from the HRPD system to the cdma2000 system. PCF1 starts timer Tregreq.
k. The A11-Registration Request message is validated and the PDSN accepts the connection by returning an A11-Registration Reply message with an accept indication. PCF1 stops timer Tregreq.
l. PCF1 sends an A9-Connect-A8 message after the completion of the A10 connection handoff. The BS stops timer TA8-setup.
m. At this point, the data session is successfully handed off from the HRPD to the cdma2000 system. n. The MS/AT sends a Connect Order message when the call is answered at the MS/AT. o. PDSN Initiates closure of the A10 connection with PCF2 by sending an A11-Registartion Update message. PDSN starts
timer Tregupd. This step may occur direct after step j. p. PCF2 responds with an A11-Registartion Acknowledge message. The PDSN stops timer Tregupd. q. PCF2 sends an A11-Registration Request message with Lifetime set to zero, to the PDSN. PCF2 starts timer Tregreq. r. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 closes the A10 connection for the MS/AT and stops
timer Tregreq. s. Upon not having received any transmissions from the MS/AT prior to timer Tairdrop expiration, the AN sends an A9-
Release-A8 message to PCF2 and starts timer Trel9. This step can occur any time after step b. t. PCF2 responds to the AN with an A9-Release-A8 Complete message. The AN stops timer Trel9.
1-2005 340 - 139Course Series 340v3.2 (c)2005 Scott Baxter
AT Leaving During an Active 1xEV-DO Data Session
1-2005 340 - 140Course Series 340v3.2 (c)2005 Scott Baxter
AT Leaving During an Active 1xEV-DO Data Session
a. The BS sends a Page Message containing the MS/AT address over the paging channel. The MS/AT may ignore this Page Message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed.
b. The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop.
c. The AN sends an A9-AL Disconnected message to PCF2 to stop data flow and starts timer Tald9.
d. Upon receipt of the A9-AL Disconnected message, PCF2 sends an A9-AL Disconnected Ack message to the AN. The AN stops timer Tald9.
e. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c.
f. The BS establishes a traffic channel upon receipt of the Assignment Request message. g. The BS sends an Alert with Info message to instruct the MS/AT to ring. h. The MS/AT sends a Connect Order message when the call is answered at the MS/AT.mentsi. When the timer Tairdrop expires, the AN initiates the release of the A8 connection by
sending an A9-Release-A8 message to PCF2 and starts timer Trel9.j. PCF2 sends an A11-Registration Request message with Lifetime set to zero, to the
PDSN. PCF2 starts timer Tregreq. k. The PDSN sends an A11-Registration Reply message to PCF2. PCF2 closes the A10
connection for the MS/AT and stops timer Tregreq. l. PCF2 responds to the AN with an A9-Release-A8 Complete message. The AN stops
timer Trel9.
1-2005 340 - 141Course Series 340v3.2 (c)2005 Scott Baxter
MS/AT Terminated Voice Call During Active HRPD Packet Data Session (Intra-PCF)
1-2005 340 - 142Course Series 340v3.2 (c)2005 Scott Baxter
MS/AT Terminated Voice Call During Active HRPD Packet Data Session (Intra-PCF)
a. The BS sends a Page Message containing the MS/AT address over the paging channel. The MS/AT may ignore this Page Message to continue the HRPD session. If the MS/AT ignores the message, the following steps are not performed.
b. The AN determines that it is not receiving any transmissions from the MS/AT and starts timer Tairdrop. c. The AN sends an A9-AL Disconnected message to the PCF to stop data flow and starts timer Tald9. d. Upon receipt of the A9-AL Disconnected message, the PCF sends an A9-AL Disconnected Ack to the AN. The
AN stops timer Tald9.e. The MS/AT sends a Page Response message to the BS. This step can occur any time after step c. f. The BS establishes a traffic channel. g. The BS sends an Alert with Info message to instruct the MS/AT to ring.h. The MS/AT and cdma2000 system set up the data session for handoff from HRPD as a concurrent call service if
the MS/AT supports the concurrent call service capability and selects to handoff the data session from the HRPD to the cdma2000 system. Refer to [11], Section 2.17.2.1 steps (a) to step 3(g).
i. The BS sends an A9-Setup-A8 message to the PCF to establish the A8 connection and starts timer TA8-setup. If the MS/AT has indicated the presence of data ready to send, the BS shall set the Data Ready Indicator to ‘1’; otherwise, the BS shall set the Data Ready Indicator to ‘0’.
j. The PCF sends an A9-Connect-A8 message to the BS. The BS stops timer TA8-setup. k. At this point, the data session is successfully handed off from the HRPD system to the cdma2000 system. l. The MS/AT sends a Connect Order message when the call is answered at the MS/AT. m. Upon not having received any transmissions from the MS/AT prior to timer Tairdrop expiration, the AN sends an
A9-Release-A8 message to the PCF and starts timer Trel9. n. Upon receipt of the A9-Release-A8 message, the PCF sends an A9-Release-A8 Complete message to the AN.
The AN stops timer Trel9.
1-2005 340 - 143Course Series 340v3.2 (c)2005 Scott Baxter
cdma2000 to HRPD Active Packet Data Session HandoffStatus Management Supported by Feature Invocation
1-2005 340 - 144Course Series 340v3.2 (c)2005 Scott Baxter
cdma2000 to HRPD Active Packet Data Session HandoffStatus Management Supported by Feature Invocationa. The MS/AT sends an Origination Message, including the feature code as
the called number, to the BS when the MS/AT starts the HRPD communication. This feature code indicates that the MSC should activate a feature (e.g., do not disturb).
b. The BS and the MSC setup the call. From the feature code, the MSC knows not to page the MS/AT for a voice call. Refer to [11], Section 2.2.2.1, Mobile Origination.
c. The BS and the MSC clear the call. Refer to [11], Section 2.3.5.3, Call Clear Initiated by MSC.
d. The MS/AT starts communication on the HRPD session. Refer to Section 3.3.2, AT Initiated Call Re-activation from Dormant State (Existing HRPD Session).
e. The MS/AT terminates communication on the HRPD session when the HRPD session goes dormant or inactive. Refer to Section 3.5.2, HRPD Session Release - Initiated by the AT (No Connection Established).
f. The MS/AT sends an Origination Message, including the feature code as the calling number, to the BS when the MS/AT ends the HRPD communication. This feature code indicates that the MSC should deactivate the feature activated in step a.
g. The BS and the MSC setup the call. From the feature code, the MSC know it may page the MS/AT for a voice call. Refer to [11], Section 2.2.2.1, Mobile Origination.
h. The BS and the MSC clear the call. Refer to [11], Section 2.3.5.3, Call Clear Initiated by MSC.
1-2005 340 - 145Course Series 340v3.2 (c)2005 Scott Baxter
An Introduction to theIS-856 Standard for 1xEV-DO
An Introduction to theIS-856 Standard for 1xEV-DO
1-2005 340 - 146Course Series 340v3.2 (c)2005 Scott Baxter
Conceptual Framework of the IS-856 StandardArchitecture Reference Model
AccessTerminal Access Network
Sector
AirInterfaceIS-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
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
1-2005 340 - 147Course Series 340v3.2 (c)2005 Scott Baxter
IS-856 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
1-2005 340 - 148Course Series 340v3.2 (c)2005 Scott Baxter
Channels and Layer-3 Messagesin 1xEV-DO Call Processing
Channels and Layer-3 Messagesin 1xEV-DO Call Processing
1-2005 340 - 149Course Series 340v3.2 (c)2005 Scott Baxter
Dissecting a Layer-3 Message
1-2005 340 - 150Course Series 340v3.2 (c)2005 Scott Baxter
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
1xEV-DO messages on both forward and reverse traffic channels are normally sent via dim-and-burstMessages 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 callField data processing tools capture and display the messages for study
Message Vocabulary: Acquisition & Idle StatesPilot Channel
No Messages
Control Channel
Pilot ChannelNo Messages
1-2005 340 - 151Course Series 340v3.2 (c)2005 Scott Baxter
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
SectorParameters
Session Close
Sync
Traffic ChannelAssignment
UATI Assignment
AccessPoint(AP)
AccessTerminal
(AN)
AccessNetwork
(AN)
Route Update
Connection Request
Data Ready ACK
Hardware ID Response
Keep Alive Request
Keep Alive Response
Session Close
Xoff Response
Xon Response
UATI Complete
UATI Request
Xoff Request
Xon Request
Message Vocabulary: Connected State
Forward 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 Report
Reverse Traffic Channel
1-2005 340 - 152Course Series 340v3.2 (c)2005 Scott Baxter
Route 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
AccessPoint(AP)
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 CloseAccessTerminal(AN)
ATKey Complete
Attribute OverrideResponse
Configuration Complete
Configuration Request
All the Messages of 1xEV-DO
1-2005 340 - 153Course Series 340v3.2 (c)2005 Scott Baxter
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
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
1-2005 340 - 154Course Series 340v3.2 (c)2005 Scott Baxter
Stream Layer
Session Layer
Connection Layer
Encryption Layer
Authentication Layer
Security Layer
PayloadHeader Trailer
PayloadHeader Trailer
Packet
Payload
MAC Header
MAC Payload
MACTrailer
PayloadHeader Trailer
MAC Layer
Physical Layer
Appendix: Protocols of theIS-856 1xEV-DO Standard
Appendix: Protocols of theIS-856 1xEV-DO Standard
1-2005 340 - 155Course Series 340v3.2 (c)2005 Scott Baxter
ALL the1xEV-DOProtocols
Page 1 of 2
1-2005 340 - 156Course Series 340v3.2 (c)2005 Scott Baxter
ALL the 1xEV-DO Protocols Page 2 of 2
1-2005 340 - 157Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
IS-856 Protocol Survey
The following section shows basic information on each layer in the IS-856 protocol stackMost protocols are briefly described along with fundamental details of their states and operationWe’ve tried to take the “shalls” and “shoulds” of legal standard-talk out of the way so you can dig in and understand what’s reallyhappening, and whyFor deeper information, of course you can always go to the appropriate chapter of the current version of the IS-856 standard, and/or to your network manufacturer’s documentation
• never drive or operate heavy machinery while reading the CDMA standards
1-2005 340 - 158Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Physical Layer Protocol
The transmission unit of the physical layer is a physical layer packet. • A physical layer packet can be 256, 512, 1024, 2048, 3072, or 4096 bits long. • The format of the physical layer packet is different on the different channels.• A physical layer packet can carry one or more MAC layer packets.
Physical Layer Packet Formats • A Control Channel physical layer packet is 1024 bits long.• Control Channel physical layer packets carry one MAC layer packet each. • Control Channel physical layer packets use the format below:
– MAC Layer Packet from the Control Channel MAC protocol. – FCS - Frame check sequence (explained in 9.1.4). – TAIL - Encoder tail bits. This field is set to all ‘0’s.
1-2005 340 - 159Course Series 340v3.2 (c)2005 Scott Baxter
Access Channel Physical Layer Packet Format
Each Access Channel physical layer packet is 256 bits long. Each Access Channel physical layer packet carries one Access Channel MAC layer packet. Access Channel physical layer packets use the following format:
• MAC Layer Packet from the Access Channel MAC protocol. • FCS - Frame check sequence (see 9.1.4). • TAIL - Encoder tail bits. This field shall be set to all ‘0’s.
1-2005 340 - 160Course Series 340v3.2 (c)2005 Scott Baxter
Forward Traffic Channel Physical Layer Packet Format
Forward Traffic Channel physical layer packets can be 1024, 2048, 3072, or 4096 bits long. A Forward Traffic Channel physical layer packet can carry 1, 2, 3, or 4 Forward Traffic Channel MAC layer packets, determined by the date rate. The format for Forward Traffic Channel physical layer packets is above.
1-2005 340 - 161Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Traffic Channel Physical Layer Packet Format
Reverse Traffic Channel physical layer packet can be 256, 512, 1024, 2048, or 4096 bits long. Each Reverse Traffic Channel physical layer packet carries one Reverse Traffic Channel MAC layer packet. Reverse Traffic Channel physical layer packets use this format:
1-2005 340 - 162Course Series 340v3.2 (c)2005 Scott Baxter
Modulation and Reverse Channel StructureThe reverse link has only Access Channel and the Reverse Traffic Channel. The Access Channel consists of just a Pilot and a Data Channel. The Reverse Traffic Channel has five sub-channels: a Pilot Channel,
• a Reverse Rate Indicator (RRI) Channel– tells the AP the data speed being transmitted by the AT– the encoded bits are really carried piggyback in the AT pilot
• a Data Rate Control (DRC) Channel– tells which sector the AT wants to hear from, and how fast
• an Acknowledgement (ACK) Channel (reception status of last packet) • and a Data Channel.
On the Access Channel, there are no RRI symbols to send – just pure pilot.The Pilot (and the RRI multiplexed on top of it) is Walsh Code 0 16 chips longWalsh Code 8 16 chips long carries the DRC channel
• But DRC bits are pre-mixed with a Walsh Code #0-#7 8 chips longcorresponding to which active sector the AT wants to hear from
• the ACK Channel is Walsh Code 4 8 chips long• the Data Channel is Walsh Code 2 4 chips long
Each terminal has a unique long code offset as its Reverse Traffic Channel.Each sector has a unique long code offset for its’ ATs Access Channel.
1-2005 340 - 163Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Traffic ChannelCoding and Modulation Parameters
Data Rate 4.8 9.6 19.2 38.4 76.8 153.6 KbpsReverse Rate Index 1 2 3 4 5 6Encoder Packet Size 256 512 1024 2048 4096 8192 bits
Packet Duration 53.33… ms53.33… 53.33… 53.33… 53.33… 53.33…Overall Code Rate 0.25 Bits/sym0.25 0.25 0.25 0.25 0.5
Code Symbols/Packet 1024 Code
Symbols2048 4096 8192 16384 16384
Code Symbol Rate 19.2 Ksps38.4 76.8 153.6 307.2 307.2Interleaved Packet
Repeats 16 8 4 2 1 1
Mod. Symbol Rate 307.2 Ksps307.2 307.2307.2 307.2 307.2Data Modulation BPSK BPSK BPSK BPSK BPSK BPSK
PN Chips perEncoder Bit 256 PN Chips128 64 32 16 8
1-2005 340 - 164Course Series 340v3.2 (c)2005 Scott Baxter
Frames and Slots of the Reverse Channels
Access Channel and Reverse Traffic Channel frames are 26.66… ms long• same length as the short PN code, and its rollover begins the frame!• A frame has 16 slots, each slot 2048 chips long, that’s 1-2/3 ms• When transmitting, the access terminal’s Reverse Traffic Channel
includes its Pilot Channel and its RRI Channel, on W016 long
• When the DRC Channel is transmitted, it lasts full slot durations on Walsh channel 8 16 chips long
• The access terminal transmits an ACK Channel bit after every Forward Traffic Channel slot when the sector is sending preamble or data to this access terminal. Otherwise, there’s nothing to report and the ACK Channel isn’t transmitted.
• The ACK Channel is the first half slot of Walsh code 8 4 chips long. On the Reverse Traffic Channel, the encoded RRI symbols get transmitted on top of the pilot for the first 256 chips of every slot.
1-2005 340 - 165Course Series 340v3.2 (c)2005 Scott Baxter
ACK Channel Operation
Next page figures show examples of the ACK Channel operation during a 153.6-kbps Forward Traffic Channel. The 153.6-kbps Forward Traffic Channel physical layer packets use four slots, with a three-slot interval between them, on the top channel. The slots of other user’s physical layer packets are interlaced in the three intervening slots. Top Figure 9.2.1.3.1-5 shows a normal physical layer packet termination. Notice - the access terminal transmits NAK responses on the ACK Channel after the first three slots of the physical layer packet are received, since it hasn’t got the whole Forward Channel physical layer packet yet. But after the last slot, an ACK or NAK is also transmitted and this one really is live, meaning what it says.
• by the way, an “ACK” is a 0 bit, and a “NAK” is a 1Bottom Figure 9.2.1.3.1-6 shows what happens where the Forward Traffic Channel physical layer packet transmission finishes early. This time, the access terminal transmits an ACK on the ACK Channel after the third slot, since it has correctly received the physical layer packet. When the access network receives an early ACK response like that, it does not transmit the empty remaining slots of the physical layer packet. Instead, it can start sending the next packet. When the access terminal has received all slots of a physical layer packet or has transmitted a positive ACK response, the physical layer officially returns to “ForwardTrafficCompleted” indication.
1-2005 340 - 166Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 167Course Series 340v3.2 (c)2005 Scott Baxter
TrackingACKsand
NAKs
Band Class
Frequency Range
0 800 MHz.1 1900 MHz.2 TACS3 JTACS4 Korean PCS5 450 MHz.6 2 GHz.7 700 MHz.8 1800 MHz. 9 900 MHz.
What areBand Classes?
Curious?
Access Channel Structure
This diagram shows how the Pilot channel and Data Channel are combined with the appropriate walsh codes and sent on for complex spreading
1-2005 340 - 168Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Traffic Channel Structure
1-2005 340 - 169Course Series 340v3.2 (c)2005 Scott Baxter
Access Channel and Reverse Traffic Channel
Anytime a terminal transmits the Access Channel, it sends its data at 9.6 kbps. The access terminal can transmit information on the Reverse Traffic Channel 9.6, 19.2, 38.4, 76.8, or 153.6 kbps, depending on what the sector tells it to do, using the Reverse Traffic Channel MAC Protocol. The whole reason for having the Access Channel is so the access terminal can initiate communication with the access network, or respond to a message directed to it by the network.
• The Access Channel has a Pilot Channel and a Data Channel as shown below.• An access “probe” starts with a preamble of just Pilot, followed by one or more
Access Channel physical layer packets which include both the Pilot and the Data Channel with the terminal’s message in it.
• During the preamble, the power of the Pilot Channel is set deliberately higher than during the data portion of the probe. The goal is to keep the transmit power the same both during the preamble and the data portion of the probe.
• Using the Access Channel MAC protocol the sector keeps ATs informed about how long a preamble it wants to hear.
1-2005 340 - 170Course Series 340v3.2 (c)2005 Scott Baxter
ACK Channel Nuts and Bolts
The ACK Channel is how the access terminal tells the access network whether it received every physical layer packet sent to it on the Forward Traffic ChannelThe access terminal responds with an ACK Channel bit after every Forward Traffic Channel slot containing either preamble or data meant for it to hear.
• It’s not good enough just to hear some bits in the slot – an ACK is only sent after a complete physical layer packet has been received OK.
• A terminal “ACKs” as soon as it gets the complete packet. When a packet is short, so it ends before the normal number of slots, the AP usually hears the ACK in time to abort sending wasteful empty slots, and it begins the next packet if there is one.
• However, if the AP doesn’t get the cue in time to abort and instead sends the rest of the useless empty packets, the AT is permitted only one additional “ACK” bit, and then isn’t supposed to send any more ACKs about that packet..
The ACK Channel is BPSK modulated. An ACK is a “0” bit, and a NAK is a 1• The way the terminal knows if it has received a good packet is if the Frame
Check Sequence (FCS) bits match up correctly with the other stuff in the frame.
• The ACK or NAK bit is actually transmitted on the Reverse Channel in the third slot after the slot the terminal is reporting about on the Forward Channel.
• The ACK is always transmitted in the first half of the slot. It lasts for 1024 PN chips. It always uses Walsh Code 4 8 chips long. and it’s always transmitted on the I phase channel.
1-2005 340 - 171Course Series 340v3.2 (c)2005 Scott Baxter
Reverse Data Channel Nuts and Bolts
The Data Channel is transmitted at 9.6, 19.2, 38.4, 76.8, or 153.6 kb/s. Data transmissions begin only at a slot designated by the FrameOffsetsent to the terminal by the Reverse Traffic Channel MAC Protocol. All data transmitted on the Reverse Traffic Channel is encoded against errors, block interleaved to make it rugged against pulsed noise, sequence repeated, and orthogonally spread by Walsh code 2 4 chips long.
1-2005 340 - 172Course Series 340v3.2 (c)2005 Scott Baxter
Forward Channel Structure
The Forward Channel is put together in the complex circuitry on the next page. It includes the following channels, all time-multiplexed together:
• Pilot Channel• Forward Medium Access Control (MAC) Channel, • Forward Traffic Channel or the Control Channel.
– The Traffic Channel carries user physical layer packets. The Control Channel carries control messages, and can carry user traffic. Notice each channel is combined with a unique Walsh code. Forward link slots are 2048 chips long (1.66… ms). Groups of 16 slots line up with the PN rollovers of zero-offset short PN code, and also line up with system time on even-second ticks. Inside each slot, the Pilot, MAC, and Traffic or Control Channels are time-division multiplexed and transmitted at the same power level.
The power level doesn’t vary!
1-2005 340 - 173Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 174Course Series 340v3.2 (c)2005 Scott Baxter
How All theForward
Channelsare Assembledand Combined
The TDM?That’s not an analog combiner like in IS-95. It’s a time division multiplexer!
Forward Channel Walsh Composition
The Forward Pilot Channel is all ‘0’ symbols covered with Walsh Code 0 (all ‘0’) and transmitted on the I channel, not steadily – but in bursts..
• Each slot is divided into two half-slots, and there’s a pilot burst in the middle of each of them. Pilot bursts are 96 chips long.
The MAC Channel includes three subchannels: • the Reverse Power Control (RPC) Channel (controlling terminal transmit
power)• the DRCLock Channel, • and the Reverse Activity (RA) Channel (a bitstream concerned with reverse
activity)– Each MAC Channel symbol is BPSK modulated on one of 64 64-ary
Walsh codes. – All the MAC symbol Walsh covers are transmitted four times per slot in
bursts of 64 chips each, just before and just after each pilot burst. – The Walsh channel gains may vary the relative power.
1-2005 340 - 175Course Series 340v3.2 (c)2005 Scott Baxter
Forward Channel Walsh Composition
The Forward Traffic Channel and Control Channel transmit data to access terminals• Forward Traffic Channel data rates can be from 38.4 kbps to 2.4576 Mbps.• Data on these channels are encoded into blocks called physical layer packets. • The encoded packets are scrambled, interleaved, then fed into a modulator
– modulation is QPSK, 8-PSK, or 16-QAM, as determined by data speed – The modulated symbols are repeated and punctured, if necessary
• The resulting sequences of modulation symbols are demultiplexed to form 16 pairs (in-phase and quadrature) of parallel streams.
• Each of the parallel streams is covered with a unique 16-chip Walsh code running at 1.2288 Mcps; the Walsh code repeats 76.8 ksps.
• All 16 streams’ Walsh symbols are then summed together to form a single in-phase stream and a single quadrature stream at a chip rate of 1.2288 Mcps.
• The resulting chips are time-division multiplexed with the preamble, Pilot Channel, and MAC Channel chips
Preamble
Pilot Channel
MAC Channel
Time D
ivision Multiplexer
Forward Traffic Channel or Control Channel
1-2005 340 - 176Course Series 340v3.2 (c)2005 Scott Baxter
Forward Channel Multiplexing
1-2005 340 - 177Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 178Course Series 340v3.2 (c)2005 Scott Baxter
The Three Adaptive Modulations of 1xEV-DO
QPSK
8-PSK
16-QAM
Forward Traffic ChannelCoding and Modulation Parameters
Data Rate(kbps)
38.4, 76.8,102.4, 153.6
Short,204.8, 307.2Short, 614.4
153.6Long,307.2Long
921.6 1,228.8 1,843.2 2,457.6
Concatenated Code rate 1/4 1/4 3/8 1/2 1/2 1/2Information Bits per
Encoder Packet 1019 4091 3067 2043 3067 4091
Effective no. of Tail Bits 0.25 0.25 0.25 0.25 0.25 0.5Code Interleaver length
(binary symbols) 2046 8190 6142 3070 4606 6142
PN Generator for CodeInterleaver P11[x] P13[x] P13[x] P12[x] P13[x] P13[x]
Encoder Output BlockLength (code symbols) 4096 16384 8192 4096 6144 8192
1-2005 340 - 179Course Series 340v3.2 (c)2005 Scott Baxter
Generic Configuration Protocol
The Generic Configuration Protocol provides a means to negotiate protocol parameters. The protocol uses a ConfigurationRequest message and a ConfigurationResponsemessage to negotiate a mutually acceptable configuration.
• The initiator uses the ConfigurationRequest message to provide the responder with a list of acceptable values for each attribute.
• The responder chooses an acceptable value from the initiator’s list, then sends a ConfigurationResponse message to tell the initiator its choice
• The initiator lists the acceptable attribute values in descending order of preference. It may require one or more ConfigurationRequest messages to include them all.
– If the ordered attribute value lists fit within one ConfigurationRequestmessage, only one is sent
– If the ordered attribute value lists are too long for one ConfigurationRequestmessage, more than one ConfigurationRequest message may be sent.
• All the proposed values for an attribute must be contained together in one ConfigurationRequest message; the list of values for that attribute cannot be split across multiple messages.
• After sending a ConfigurationRequest message, the sender shall set the value of all parameters that were listed in the message to NULL.
• After receiving a ConfigurationRequest message, the responder must choose an acceptable value from the list for each attribute, and respond within Tturnaround(default value = 2 seconds), unless specified otherwise.
1-2005 340 - 180Course Series 340v3.2 (c)2005 Scott Baxter
The MAC Layer
The MAC Layer contains the following protocols:Control Channel MAC Protocol:
• builds Control Channel MAC Layer packets from Security Layer packets• adds access terminal addresses to transmitted packets for specific ATs • lists the rules/procedures for
– access channel transmission and Control Channel packet scheduling– access terminal acquisition of the Control Channel– access terminal Control Channel MAC Layer packet reception.
Access Channel MAC Protocol: • specifies timing and power of ATs transmitting on the Access Channel.
Forward Traffic Channel MAC Protocol• contains the rules governing Forward Traffic Channel operation
– supports both variable rate and fixed rate operation of the FTC• gives rules for AT transmission on the DRC (Data Rate Control Channel)• gives the rules the access network uses to interpret the DRC
Reverse Traffic Channel MAC Protocol: • contains the rules governing Reverse Traffic Channel operation • Specifies how the AT helps the network find its the Reverse Traffic Channel. • Specifies how the AT and AN choose the Reverse Traffic Channel data rate
1-2005 340 - 181Course Series 340v3.2 (c)2005 Scott Baxter
MAC Layer Packet Encapsulationon the Control Channel
1-2005 340 - 182Course Series 340v3.2 (c)2005 Scott Baxter
MAC Layer Packet Encapsulation on the Access Channel
1-2005 340 - 183Course Series 340v3.2 (c)2005 Scott Baxter
MAC Layer Packet Encapsulation on theForward and Reverse Traffic Channels
1-2005 340 - 184Course Series 340v3.2 (c)2005 Scott Baxter
MAC Protocol for the Control ChannelDefaultSignalingApplication
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
The Default Control Channel MAC Protocol gives the procedures and messages required to run the Control ChannelThe network maintains one instance of this protocol for all access terminals. This protocol can be in one of two states:
• Inactive State: in this state the network waits for an Activate command. This state happens when the access terminal has not acquired an access network, or is not monitoring the Control Channel.
• Active State: in this state the access network transmits and theaccess terminal receives the Control Channel.
1-2005 340 - 185Course Series 340v3.2 (c)2005 Scott Baxter
MAC Protocol for the Access Channel
The Default Access Channel MAC Protocol gives the procedures andmessages required to operate the Access Channel. This specification assumes that the access network has one instance of this protocol for each access terminal. This protocol has two states:
• Inactive State: The Access Terminal doesn’t communicate on the Access Channel. The network watches for an Activate command from the terminal, which it sends if it newly acquires the network or ends any connection it may already have open.
• Active State: The access terminal has already Activated and may now transmit on the Access Channel whenever desired.
DefaultSignalingApplication
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
1-2005 340 - 186Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Access Channel Probing
ATs may start sending probes only at the Access Channel Cycle Start In an access probe, the AT first sends pilot (I-channel) only, as a preamble
• After the preamble, the AT also sends the Q-channel to carry its message– preamble duration is set to (PreambleLength × 16 slots)– message capsule can be up to CapsuleLengthMax × 16 slots long
• The AT must send another probe unless one of the following occurs– Access terminal receives an ACAck message. – a Deactivate command is received, forcing the AT to abort – Maximum number of probes per sequence have been sent
(ProbeNumStep) • Before transmitting the first probe, the access terminal performs a
persistence test to avoid congestion on the Access Channel. – a persistence test is also performed between probe sequences.
1-2005 340 - 187Course Series 340v3.2 (c)2005 Scott Baxter
MAC Protocol for the Forward Traffic Channel
The Default Forward Traffic Channel MAC Protocol provides the procedures and messages operate the Forward Traffic Channel. It specifies
• Forward Traffic Channel addressing and• Forward Traffic Channel rate control.
The network tracks one instance of this protocol for each access terminal. There are three states:
• Inactive State: the access terminal has no Forward Traffic Channel. To get one, the AT must send an Activate command.
• Variable Rate State: the Forward Traffic Channel is transmitted at variable rate, requested by the access terminal’s DRC
• Fixed Rate State: the Forward Traffic Channel is transmitted to the access terminal from one particular sector, at one particular rate.
DefaultSignalingApplication
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
1-2005 340 - 188Course Series 340v3.2 (c)2005 Scott Baxter
MAC Protocol for theReverse Traffic Channel
The Default Reverse Traffic Channel MAC Protocol specifies transmission rules and rate control for the Reverse Traffic Channel . The network tracks one instance of this protocol for every access terminal. It has three states:
• Inactive State: The access terminal does not have a Reverse Traffic Channel. To get one, the AT must send an Activate command.
• Setup State: In this state, the access terminal negotiates for a session, already obeying power control commands from the access network, but not yet allowed to send data on the Reverse Traffic Channel.
• Open State: In this state, the access terminal may transmit data and negotiate different transmission rates on the Reverse Traffic Channel.
DefaultSignalingApplication
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
1-2005 340 - 189Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Security Protocol
The Security Layer provides:Key Exchange:
• AT and AN exchange security keys for authentication and encryption
Authentication: • AT and AN authenticate traffic
Encryption: • AT and AN encrypt traffic
The Security Layer uses • Key Exchange Protocol• Authentication Protocol• Encryption Protocol • Security Protocol to provide these
functionsSecurity Protocol provides public variables needed by the authentication and encryption protocols (e.g., cryptosynctime-stamp, etc.).
Security Layer Encapsulation
1-2005 340 - 190Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 191Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Key Exchange Protocol
DefaultSignalingApplication
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
Authentication Protocol
The Default Authentication Protocol does not provide any services except transferring packets between the Encryption Protocol and the Security Protocol. It does not define any commands or return any indications.The protocol data unit for this protocol is an Authentication Protocol packet. Operation for the InConfiguration Protocol Instance
• Set fall-back values of the attributes to their default values• If the InUse instance of this protocol has the same protocol subtype as
this InConfiguration protocol instance, then set the fall-back values of the attributes defined by the InConfiguration protocol instance to match
Operation for the InUse Protocol Instance• set the value of the attributes for this protocol instance to defaults • When Encryption Protocol packets are received, forward them to the
Security Protocol. • When Security Protocol packets are received, set the Encryption
Protocol packet to the Authentication Protocol packet and forward the Encryption Protocol packet to the Encryption Protocol.
1-2005 340 - 192Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Encryption Protocol
The Default Encryption Protocol does not alter the Security Layer packet payload (i.e., no encryption/decryption)
• it does not add an Encryption Protocol Header or Trailer;
The Cipher-text for this protocol is equal to the Connection Layer packet. If needed, end-to-end encryption can be provided at the application layer (which is outside the scope of this specification).
1-2005 340 - 193Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
The Connection Layer
The connection between an Access Terminal and the Access Network can be in either of two states -- closed or open:
• Closed Connection: the access terminal has no dedicated air-link resources. Any communications are over the Access Channel and the Control Channel.
• Open Connection: the access terminal can be assigned the Forward Traffic Channel, and is assigned a Reverse Power Control Channel and a Reverse Traffic Channel. Communications between the access terminal and the access network are conducted over these assigned channels, as well as over the control channel.
1-2005 340 - 194Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Packet Consolidation Protocol
Packet Consolidation Protocol: This protocol consolidates and prioritizes packets for transmission as a function of their assigned priority and the target transmission channel.
1-2005 340 - 195Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Route Update Protocol
Route Update Protocol: • keeps track of an access
terminal’s location and maintains the radio link between the access terminal and the access network.
• The main thrust of this protocol is tracking pilots and requesting/managing the terminal’s active set.
A route update in 1xEV-DO is similar in several ways to a handoff in IS-95 or IS-2000.
1-2005 340 - 196Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Default Route Update Protocol
The Default Route Update Protocol keeps track of the access terminal’s approximate location to maintain the radio link as the access terminal moves between the coverage areas of different sectors. This protocol can be in one of three states:Inactive State: The protocol waits for an Activate command. Idle State: As in the Air-Link Management Protocol Idle State, the AT autonomously manages the Active Set. Route update messages from the access terminal to the access network are triggered by terminal-computed distance between the current serving sector and the serving sector at the time of the last update. Connected State: As in the Air-Link Management Protocol Connected State, the access network dictates the access terminal’s Active Set. Route update messages from the access terminal to the access network are based on changing radio link conditions.
1-2005 340 - 197Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Route Update Reporting Rules
Route Update Report Rules The AT sends RouteUpdate messages to the AN to update its location
• No RouteUpdate message is sent while connection timer is active.• anytime it transmits on the Access Channel. • anytime the formula below gives a value r greater than the value told
to the AT by the last sector on which it performed a location update – (xL,yL) are the longitude and latitude of the last sector where the
AT performed a route update. (xC,yC) are the longitude and latitude of the sector currently covering the access terminal.
– The AT must compute r with an error of no more than ±5% of its true value when |yL/14400| < 60 and with an error of no more than ±7% of its true value when |yL/14400| is between 60 and 70. (This specification is given to ensure any abbreviated computation algorithms used by ATs are sufficiently accurate.)
The RouteUpdate message includes the pilot PN phase, pilot strength, and drop timer status for every pilot in the Active Set and Candidate Set.
1-2005 340 - 198Course Series 340v3.2 (c)2005 Scott Baxter
Overhead Messages ProtocolDefaultSignalingApplication
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
The QuickConfig message and the SectorParameters message are collectively termed the overhead messages. Broadcast by the access network, they carry essential parameters to the ATs over the Control Channel and affect multiple other protocols. The Overhead Messages Protocol:
• manages transmission, reception and supervision of these messages and supervises the pilots
There are two possible Overhead Messages Protocol states: • Inactive State: the access terminal has not acquired an access
network or is not required to receive overhead messages. the network waits for an Activate command.
• Active State: the AN transmits overhead messages to the AT
1-2005 340 - 199Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 200Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Air Link Management Protocol
Air Link Management Protocol: This protocol maintains the overall connection between the access terminal and the access network. There are three states:
• Initialization State: Access Terminal hasn’t yet acquired network• Idle State: AT acquired network but connection is closed • Connected State: AT has open connection with access network
Depending on its current state, this protocol activates Initialization State Protocol, Idle State Protocol, or Connected State Protocol
DefaultSignalingApplication
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
Initialization State Protocol
The Default Initialization State Protocol manages the process of an access terminal acquiring a serving network. At the access terminal, this protocol operates in one of the following four states:
• Inactive State: protocol waits for an Activate command.
• Network Determination State: the access terminal chooses an access network on which to operate.
• Pilot Acquisition State: access terminal acquires a Forward Pilot Channel.
• Synchronization State: access terminal synchronizes to the ControlChannel cycle, receives the Sync message, and synchronizes to system time.
1-2005 340 - 201Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Idle State Protocol
Idle State Protocol: manages an access terminal that has acquired the network, but does not have an open connection.
• keeping track of the access terminal’s approximate location in support of efficient Paging (using the Route Update Protocol)
• procedures leading to the opening of a connection
• support of access terminal power conservation.
1-2005 340 - 202Course Series 340v3.2 (c)2005 Scott Baxter
Connected State Protocol
Connected State Protocol: manages an open connection with an access terminal that has an open connection
• managing the radio link between the access terminal and the access network
• performing handoffs via the Route Update Protocol
• connection closing proceduresThe Default Connected State Protocol can be in one of three states:
• Inactive State: protocol waits for an Activate command.
• Open State: AT can use the Reverse Traffic Channel and the AN can use the Forward Traffic Channel and Control Channel for traffic to each other.
• Close State: access network waits for safe release of connection resources
DefaultSignalingApplication
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
1-2005 340 - 203Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Session Management Protocol
Default Session Management protocol controls activation of Address Management Protocol and then Session Configuration Protocol before a session is established. It periodically ensures that the session is still valid and manages closing the session. There are four states:
• Inactive State: applies only to the AT; there are no communications between the AT and the AN.
• AMP Setup State: The AT and AN make exchanges under Address Management Protocol and the AN assigns a UATI to the AT.
• Open State: a session is open. • Close State: applies only to AN, waiting for close procedure to
complete.Protocols activated by the Default Session Management Protocol. return indications which trigger most of the state transitions of this protocol.
1-2005 340 - 204Course Series 340v3.2 (c)2005 Scott Baxter
Address Management ProtocolDefaultSignalingApplication
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
The Default Address Management Protocol provides the following functions: • Initial UATI assignment• Maintaining the access terminal unicast address as the access terminal
moves between subnets. Default Address Management Protocol has three states:
• Inactive State: no communications between the AT and AN• Setup State: The AT and AN exchange UATIRequest / UATIAssignment /
UATIComplete to assign theAT a UATI. • Open State: The AT has been assigned a UATI. The AT and AN may
also perform a UATIRequest / UATIAssignment / UATIComplete or a UATIAssignment / UATIComplete exchange so that the access terminal obtains a new UATI.
1-2005 340 - 205Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Session Configuration Protocol
Default Session Configuration Protocol manages protocol negotiation and configuration during a session. It supports two phases of negotiation:
• Exchanges initiated by the AT to negotiate protocols used in the session and some of their parameters (authentication key lengths, etc).
• Exchanges initiated by the access network typically to override default values used by the negotiated protocols.
Session Configuration Protocol uses Generic Configuration Protocol when negotiating. Even if the AT uses a Session Configuration Protocol other than the Default Session Configuration Protocol, it still uses the Default Session Configuration Protocol to negotiate that other protocol.Additional protocols may be negotiated without further modifications to the Default Session Configuration Protocol. Default Session Configuration Protocol has four states:
• Inactive State: the protocol waits for an Activate command. ・• AT Initiated State: negotiation is performed at the initiative of the AT• AN Initiated State: negotiation is performed at the initiative of the AN• Open State: The AT may initiate session configuration procedure at any
time and the AN may request the AT to do so at any time.
1-2005 340 - 206Course Series 340v3.2 (c)2005 Scott Baxter
Session Configuration ProtocolDefaultSignalingApplication
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
1-2005 340 - 207Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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 Default Session Configuration Protocol:
Extensive Negotiation Procedure
1-2005 340 - 208Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Stream Protocol
The Stream Layer provides: Multiplexing application streams for one access terminal.
• Stream 0 is always assigned to the Signaling Application.
• The other streams can be assigned to applications with different QoS (Quality of Service) requirements, or other applications.
Configuration messages that map applications to streams, using Stream Layer Protocol. Data Encapsulation for the InUse Protocol Instance
1-2005 340 - 209Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Default Signaling Application:Signaling Link Protocol
The Default Signaling Application includes Signaling Network Protocol (SNP) and Signaling Link Protocol (SLP). Protocols in each layer use SNP to exchange messages. SNP is also used by application specific control messages. SNP provides a single octet header that defines the Type of the protocol and the protocol instance (i.e., InConfiguration or InUse) with which the message is associated.
• The SNP uses the header to route the message to the appropriate protocol instance.
• SLP provides message fragmentation, reliable and best-effort message delivery and duplicate detection for messages that are delivered reliably.
The Signaling Link Protocol (SLP) has two layers: The delivery layer and the fragmentation layer.
• The SLP delivery layer (SLP-D) provides best effort and reliable delivery for SNP packets; duplicate detection/retransmission formessages using reliable delivery. It does not ensure in-order delivery.
• The SLP fragmentation layer (SLP-F) provides fragmentation for SLP-D packets.
1-2005 340 - 210Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Default Signaling Application:Signaling Network Protocol
Signaling Network Protocol (SNP) routes messages to protocols specified by the <InConfigurationProtocol, Type> pair of fields provided in the SNP header.
• The InConfigurationProtocol field in the SNP header determines whether the encapsulated message corresponds to the InUse protocol instance or the InConfiguration protocol instance.
• The actual protocol indicated by the Type is negotiated during session set-up. For example, Type 0x01 is associated with the Control Channel MAC Protocol. The specific Control Channel MAC Protocol used (and, therefore, the Control Channel MAC protocol generating and processing the messages delivered by SNP) is negotiated when the session is setup.
The remainder of the message following the Type field (SNP header) is processed by the protocol specified by the Type. SNP is a protocol associated with the Default Signaling Application.
1-2005 340 - 211Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
General Signaling Requirements
The following requirements are common to all protocols that carry messages using SNP and that provide for message extensibility. Both access terminal and access network must comply with the following rules when generating and processing any signaling message carried by SNP.Messages are always an integer number of octets in length; and, if necessary, include a Reserved field at the end of the message to make them so. The receiver ignores the value of the Reserved fields. The first field of the message is always transmitted first. Within each field, the most significant bit of the field is always transmitted first. Message identifiers must be unambiguous for each protocol Type and for each Subtype for all protocols compatible with the Air Interface, defined by MinimumRevision and above. For future revisions, the transmitter adds new fields only at the end of a message (excluding any trailing Reserved field). The transmitter must not add fields if their addition makes the parsing of previous fields ambiguous for receivers whose protocol revision is equal to or greater than MinimumRevision. The receiver discards and ignores all unrecognized messages. The receiver shall discards and ignores all unrecognized fields.
1-2005 340 - 212Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Default Packet Application:Radio Link Protocol
The Default Packet Application provides an octet stream that canbe used to carry packets between the access terminal and the access network. It provides:
• The Radio Link Protocol (RLP), which provides retransmission, and duplicate detection, thus, reducing the radio link error rate as seen by the higher layer protocols.
• Packet Location Update Protocol, which defines location update procedures and messages in support of mobility management for the Packet Application.
• Flow Control Protocol, which provides flow control for the Default Packet Application.
1-2005 340 - 213Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Radio Link Protocol Operation
Radio Link Protocol (RLP) provides an octet stream service with an acceptably low erasure rate for efficient operation of higher layer protocols (e.g., TCP). When used as part of the Default Packet Application, the protocol carries an octet stream from the upper layer. RLP uses Nak-based retransmissions. Protocol Data Unit: The transmission unit of this protocol is an RLP packet. RLP is unaware of higher layer framing; it operates on afeatureless octet stream. RLP receives octets for transmission from the higher layer and forms an RLP packet by concatenating the RLP packet header with a number of received contiguous octets. RLP follows policies beyond this document’s scope in determining the number of octets to send in an RLP packet. It is subject to the requirement that an RLP packet shall not exceed the maximum payload length that can be carried by a Stream Layer packet given the target channel and current transmission rate on that channel. RLP makes use of the Reset, ResetAck, and Nak messages to perform control related operations. When RLP sends these messages it uses the Signaling Application.
1-2005 340 - 214Course Series 340v3.2 (c)2005 Scott Baxter
DefaultSignalingApplication
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
Default Packet Application:Location Update Protocol
The Location Update Protocol defines location update procedures and messages for mobility management for the Default Packet Application.
• The transmission unit of this protocol is a message. It is a control protocol, so it does not carry payload for other layers or protocols.
When the protocol in the access network receives an AddressManagement.SubnetChanged indication, the access network:
– May query the information with a LocationRequest message– May update the location with a LocationAssignment message
• When the access terminal receives a LocationRequest message, it sends a LocationNotification message. If it has a stored value for the LocationValue parameter, it sets the LocationType, LocationLength, and LocationValue fields in this message to its stored values of these fields. If it does not have a stored value for the LocationValueparameter, the access terminal omits the LocationLength and LocationValue fields in this message.
If the access terminal receives a LocationAssignment message, sends a LocationComplete message and stores the value of the LocationType, LocationLength, and LocationValue fields of the message in the corresponding variables.
1-2005 340 - 215Course Series 340v3.2 (c)2005 Scott Baxter
Default Packet Application:Flow Control Protocol
Flow Control Protocol provides procedures and messages used by the access terminal and the access network to perform flow control for the Default Packet Application. It has the following states:
• Close State: in this state the Default Packet Application does not send or receive any RLP packets.
• Open State: in this state the Default Packet Application can send or receive RLP packets.
The flow control protocol is a protocol under the default packetapplication.
DefaultSignalingApplication
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
1-2005 340 - 216Course Series 340v3.2 (c)2005 Scott Baxter
1-2005 340 - 217Course Series 340v3.2 (c)2005 Scott Baxter
ALL IS-856 1xEV-DO
Messages –Page 1 of 4
1-2005 340 - 218Course Series 340v3.2 (c)2005 Scott Baxter
ALL IS-856 1xEV-DO
Messages –Page 2 of 4
1-2005 340 - 219Course Series 340v3.2 (c)2005 Scott Baxter
ALL IS-856 1xEV-DO
Messages –Page 3 of 4
ALL IS-856 1xEV-DO Messages – Page 4 of 4
1-2005 340 - 220Course Series 340v3.2 (c)2005 Scott Baxter