1xEV DO Technology

Course 340
Background and Introduction Background and Introduction To 1xEV-DO Technology To 1xEV-DO Technology
This course can be downloaded free from our website:
www.howcdmaworks.com/340.pdf
1-2005 Course Series 340v3.2 (c)2005 Scott Baxter 340 - 1
Contents
Survey of Wireless Data Technologies and 1xEV-DO Purpose 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 Messaging 1xEV-DO/1xRTT Interoperability Summary Review of 1xEV-DO Protocols
Global and US Wireless Snapshot 4Q 2003
Total Wireless Users GSM users CDMA users TDMA users IDEN users Analog users
Worldwide 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%
USA 141,000,000 33,732,506 64,503,287 26,375,232 11,978,382 4,510,594
100% 23.9% 45.7% 18.6% 8.5% 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 technology CDMA 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
Global and US Wireless Users by Technology
TDMA 9%
Analog 3%
IDEN 5%
Analog 3% TDMA 19%
IDEN 8%
GSM 24%
CDMA 17%
GSM 66%
CDMA 46%
GSM is by far the dominant global technology CDMA is dominant in its country of origin, the USA The IS-136 TDMA community is rapidly implementing GSM primary motivation is to provide GPRS and/or EDGE fast data
A Quick Survey of Wireless Data Technologies

US CDMA
IS-95
14.4 9.6 kb/s
ETSI / GSM
GSM CSD
9.6 4.8 kb/s
ANALOG
AMPS Cellular
9.6 4.8 kb/s w/modem
PAGING
Mobitex
9.6 4.8 kb/s obsolete
IS-95B
64 -32 kb/s
GSM HSCSD
32 19.2 kb/s
CDPD
19.2 4.8 kb/s discontinued
1xRTT RC3
153.6 80 kb/s
GPRS
40 30 kb/s DL 15 kb/s UL
Other Misc. IS-136

IDEN IS-136 TDMA
19.2 9.6 kb/s 19.2 19.2 kb/s
1xRTT RC4
307.2 160 kb/s
EDGE
200 - 90 kb/s DL 45 kb/s UL
1xEV-DO
2400 600 DL 153.6 76 UL
WCDMA 0
384 250 kb/s
1xEV-DO A
3100 800 DL 1800 600 UL
WCDMA 1
2000 - 800 kb/s
TD-SCDMA
In Development
1xEV-DV
5000 - 1200 DL 307 - 153 UL
WCDMA HSPDA
12000 6000 kb/s
Flarion OFDM
1500 900 kb/s
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 technologies Have actual experiences to share, latest announced details, or corrections to the above? Email to Scott@ScottBaxter.com. Thanks for your comments!
The CDMA Migration Path to 3G

CDMAone Generation Technology Spectrum Signal Bandwidth, #Users 1G AMPS
RL FL
CDMA2000 / IS-2000 2.5G? 3G 3G 3G IS-2000: IS-2000: 1xEV-DO 1xEV-DO 1xEV-DV Rev. 0 Rev. A 1xRTT 3xRTT 1xTreme IS-856 IS-856
RL FL RL FL RL FL RL FL RL FL
2G
2G
IS-95A/ IS-95B J-Std008

RL FL RL FL
1250 kHz. F: 3x 1250k 30 kHz. 1250 kHz. 1250 kHz. R: 3687k 50-80 voice 120-210 per 1 20-35 25-40 3 carriers and data 14.4K 64K 153K 307K 230K
Enhanced Access Channel Structure
1250 kHz. 59 active users
1250 kHz. 1250 kHz. 59 active Many packet users users 3.1 Mb/s DL 1.8 Mb/s UL Higher data rates on dataonly CDMA carrier 5 Mb/s
None, Data Capabilities 2.4K by modem Features: Incremental Progress

First System, Capacity & Handoffs
2.4 Mb/s DL 1.0 Mb/s 153 Kb/s

UL
First CDMA, Capacity, Quality
Improve d Access Smarter Handoffs
Faster data rates on shared 3-carrier bundle
High data rates on data-only CDMA carrier
High data rates on Data-Voice shared CDMA carrier
1-2005
Course Series 340v3.2 (c)2005 Scott Baxter
340 - 6
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 2003 1xEV 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.
QPSK
CDMA IS-95, IS-2000 1xRTT, and lower rates of 1xEV-DO, DV
16QAM
1xEV-DO at highest rates
64QAM
1xEV-DV at highest rates
1-2005
340 - 7
GSM Technology Migration Path to 3G

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

Generation Technology Signal Bandwidth, #Users Data Capabilities 1G AMPS 2G CDPD 2G TDMA IS-54 IS-136 2G GSM 2.5G or 3? 3G 3G UMTS GPRS EDGE UTRA WCDMA 3.84 MHz. 200 kHz. 200 kHz. up to 200+ Many fast data voice users Pkt. users many users and data 9-160 Kb/s 384 Kb/s (conditions mobile user determine) 2Mb/s static user
30 kHz. 1 None, 2.4K by modem
30 kHz. 30 kHz. Many 3 users Pkt Usrs 19.2 kbps none
200 kHz. 7.5 avg.
none
First System, Features: Incremental Capacity & Progress Handoffs
US Packet Data Svc.
USAs first Digital wireless
Europes first Digital wireless
Integrated Packet IP 8PSK for voice/data access 3x Faster (Future rates Multiple data rates to 12 MBPS attached than GPRS using adv. users modulation?)
1-2005
340 - 9
4G: Broadband Wireless Access Technologies

High Hopes!
Technology Frequency Band Access Method Modulation Type Max Raw Data Rate
Infrared IRDA Optical

Single User per Optical Carrier
Bluetooth 802.11b 2.4 GHz 2.4 GHz various GFSK FH 1 Mb/s

DSSS
802.11a 5 GHz DSSS

BPSK, QPSK, 16QAM, or 64QAM
HIPERLAN HIPERLAN Type 1 Type 2 5 GHz OFDM 5 GHz various.
802.16 2-11 GHz 10-66 GHz TDD, FDD various
802.20
Mobile BWA
various 4 Mb/s
CCK
FSK or BPSK, QPSK, BPSK to 16QAM, or 256QAM GMSK 64QAM OFDM 23.5 Mb/s 54 Mb/s 54 Mb/s
11 Mb/s
54 Mb/s
Not BWA; for comparison only
BLUETOOTH
802.11A, B, WIFI, WILAN
Infrared IRDA
1-2005
340 - 10
4G Evolution or Revolution?
Technology Environment
Service Provider/ Infrastructure Owner
High-Tier $$$
1G: AMPS 2G: TDMA, GSM,

IS95 CDMA, IDEN
Near-Universal Macro-Coverage
2.5G: GPRS, EDGE 3G: IS2000 1xRTT,

1xEV DO, 1xEV DV UMTS WCDMA
PSTN
IP/VPNs
Low-Tier $
4G: Wireless LAN

802.11b Wi-Fi 802.11a, g HIPERLAN Type 1 HIPERLAN Type 2 Bluetooth Infrared
Hotspots
freenetworks.org
Theres 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 advantages Ultimately 3G and 4G will be integrated by wireless operators!
SPEED: 1xEV-DOs Purpose SPEED: 1xEV-DOs Purpose

Differences from CDMA2000 1xRTT Differences from CDMA2000 1xRTT
1-2005
340 - 12
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 - 13
Why Cant 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 schemes For all these reasons, something more nimble is needed
1-2005
340 - 14
Mobile RF Channel Conditions Change Rapidly

Path Loss, relative dB +6 +4 +2 +0 -2 0 0.1
Path Loss, db 0.2 0.3 Time, Seconds
0.4
0.5
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
1xRTT Data Burst Control Lags RF Conditions

Eb/Nt, dB Path Loss, relative dB
+4 +2 +0 -2 0 0.1
DATA RATE DECISION
+6
GOOD CONDITIONS
DATA BURST ACTUALLY OCCURS NOW
BAD CONDITIONS
Path Loss, db 0.2 0.3 Time, Seconds 0.4 0.5
BTS F-SCH
Setup Time
F-FCH
Fixed Rate!
F-SCH Burst
SCH-Assignment Msg.
R-FCH MOBILE R-SCH T seconds 0 1-2005 0.1 0.2 0.3 0.4 340 - 16 0.5
1xEV-DO vs. 1xRTT at the Same Time-Scale

AP
1xEV-DO
Traffic DRC
Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.
AT
Setup time can be less than 10 ms., depending on traffic loading.
T 0 0.1 0.2 Time, Seconds 0.3 0.4 0.5
1xRTT
BTS F-SCH
Setup Time
F-FCH
Fixed Rate!
F-SCH Burst
SCH-Assignment Msg.
R-FCH MOBILE
SCH-Request Msg.
R-SCH
Thoughput: 0.15 or 0.31 Mb/s max, 0.06 Mb/s typ.

1xEV-DO Handles Data at the level of Packets and Subpackets

AP
1xEV-DO
Traffic DRC
Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.
AT
Setup time can be less than 10 ms., depending on traffic loading.
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 flow Each mobile DRC request is based on latest channel condition ACK/NAK commands can stop unneeded subpacket repetitions in less than 5 ms.!
The Key Features The Key Features and Structure of 1xEV-DO and Structure of 1xEV-DO
1-2005
340 - 19
Channel Structure of 1xEV-DO vs. 1xRTT

CHANNEL 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!
1-2005
IS-95 AND 1xRTT

Many users simultaneous forward and reverse traffic channels
PILOT SYNC PAGING F-FCH1 F-FCH2 F-FCH3 F-SCH W0 W32 W1 W17 W25 W41 W3
BTS
F-FCH4 W53
ATs
1xEV-DO
AP
(Access Terminals)
(Access Point)
1xEV-DO Forward Link
AP
340 - 20
Power Management of 1xEV-DO vs. 1xRTT

IS-95: VARIABLE POWER
POWER MANAGEMENT IS-95 and 1xRTT: sectors adjust each users channel power to maintain a preset target FER 1xEV-DO IS-856: sectors always operate at maximum power sector output is timemultiplexed, 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
1-2005
TO MAINTAIN USER FER

Maximum Sector Transmit Power 8 7 6
power
5 4 2
5 3 User 1 PAGING SYNC PILOT
time
1xEV-DO: MAX POWER ALWAYS,

DATA RATE OPTIMIZED
power
time
340 - 21
Some EV-DO Terminology

IS-95, IS-2000, 1xRTT
Phone, Mobile, Handset, or Subscriber Terminal
EV-DO
AT
Access Terminal
Base Station, BTS, Cell Site
AP
Access Point
1-2005
340 - 22
1xEV-DO Technical Details 1xEV-DO Technical Details

Data Flow and Channels Data Flow and Channels
1-2005
340 - 23
1xEV-DO Transmission Timing

Forward Link
All members of the CDMA family - IS-95, IS-95B, 1xRTT, 1xEV-DO and 1xEV-DV transmit Frames One Cycle of PN Short Code IS-95, IS-95B, 1xRTT frames are usually 20 ms. long 1xEV-DO frames are 26-2/3 ms. long same length as the short PN code One 1xEV-DO Frame 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 dont own long continuing series of slots One Slot like in TDMA or GSM; instead, each slot or small string of slots is dynamically addressed to whoever needs it at the moment
Whats In a Slot?
Slot 1024 chips Slot 1024 chips
PILOT
PILOT
MAC
MAC
MAC
SLOT
DATA
400 chips
DATA
400 chips
DATA
400 chips
MAC
DATA
400 chips
64
96
64
64
96
64
The main cargo in a slot is the DATA being sent to a user But all users need to get continuous timing and administrative information, even when all the slots are going to somebody else Twice in every slot there is regularly-scheduled burst of timing and administrative information for everyone to use MAC (Media Access Control) information such as power control bits a burst of pure Pilot allows new mobiles to acquire the cell and decide to use it keeps existing user mobiles exactly on sector time mobiles use it to decide which sector should send them their next forward link packet
What if theres No Data to Send?

PILOT
PILOT
MAC
MAC
MAC
SLOT
empty
400 chips
empty
400 chips
empty
400 chips
MAC
empty
400 chips
64
96
64
64
96
64
Sometimes there may be no data waiting to be sent on a sectors forward link When theres 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 sectors and 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
Slots and Frames

PILOT
PILOT
MAC
MAC
MAC
SLOT
DATA
400 chips
DATA
400 chips
DATA
400 chips
MAC
DATA
400 chips
64
96
64
64
96
64
Slot
FRAME
1 Frame = 16 slots 32k chips 26-2/3 ms
Two Half-Slots make a Slot 16 Slots make a frame
1-2005
340 - 27
Frames and Control Channel Cycles

A Control Channel Cycle is 16 frames (thats 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 packets The last half of the first frame, and all of the remaining 15 frames, have their slots available for ordinary use transmitting subpackets to users
Slot
FRAME
CONTROL CHANNEL
USER(S) DATA CHANNEL
16-FRAME
CONTROL CHANNEL CYCLE
16 Frames 524k chips 426-2/3 ms
Thats a lot of slots! 16 x 16 = 256
1-2005
340 - 28
Forward Link Frame and Slot Structure: Big Picture Summary

PILOT
PILOT
MAC
MAC
MAC
SLOT
DATA
400 chips
DATA
400 chips
DATA
400 chips
MAC
DATA
400 chips
64
96
64
64
96
64
FRAME
CONTROL CHANNEL
USER(S) DATA CHANNEL
16-FRAME
CONTROL CHANNEL CYCLE
16 Frames 524k chips 426-2/3 ms
Slots make Frames and Frames make Control Channel Cycles!

The 1xEV-DO Channels

IN THE WORLD OF CODES
FORWARD CHANNELS
Sector has a Short PN Offset
W064 Pilot W264 Rev Activity
just like IS-95
REVERSE CHANNELS
Long PN offset
ACCESS
MAC
Pilot W016 Data

W24
Access Channel for session setup from Idle Mode
Access
64
DRCLock RPC
MAC
Wx16 Control Wx16 Traffic
Pilot W016 RRI

Long PN offset
Public or Private
Access Point (AP)
MAC DRC
FORWARD
Walsh code
W0 W4 W1 W5 W816 W2 W6 W3 W7
Access Terminal (User Terminal)

Traffic Channel as used during a 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 can monitor
A TR IC FF
ACK Data
W48 W24
Walsh code
AP
Functions of the Forward Channels

FORWARD CHANNELS
Sector has a Short PN Offset
W064 Pilot W264 Rev Activity W
64
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
DRCLock RPC
Wx16 Control Wx16 Traffic
Access Point (AP)
MAC
MAC
Traffic channels carry user data to one user at a time
IN THE WORLD OF TIME

Forward Link Slot Structure (16 slots in a 26-2/3 ms. frame)
PILOT PILOT MAC MAC MAC DATA
400 chips
DATA
400 chips
DATA
400 chips
MAC
DATA
400 chips
64 96 64 Slot 1024 chips
64 96 64 Slot 1024 chips
1-2005
340 - 31
Functions of the Reverse Channels

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 ATs 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 ATs traffic bits
REVERSE CHANNELS
Long PN offset
Access
ACCESS
Pilot W016 Data

W24
TRAFFIC
MAC DRC
Pilot W016 RRI

Long PN offset W0 W4 W1 W5 W816 W2 W6 W3 W7
Public or Private
Access Terminal (User Terminal)
ACK Data
W48 W24
1-2005
340 - 32
Information Flow Over 1xEV-DO

Data from PDSN for the Mobile Data Ready DRC: 5 MP3, web page, or other content
AP
The system notifies a mobile when data for it is waiting to be sent The mobile chooses which sector it hears best at that instant, and requests the sector to send it a packet there are 16 possible transmission formats the mobile may request, called DRC 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 link The first slot will begin with a header that the mobile will recognize so it can begin the receiving process
Transmission of a Packet over EV-DO

Data from PDSN for the Mobile Data Ready 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.
AP
1-2005
340 - 34

Data from PDSN for the Mobile Data Ready DRC: 5 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. 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.
AP
1-2005
340 - 35

Data from PDSN for the Mobile Data Ready DRC: 5 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. The AT quickly determines which of its active sectors is the strongest. On the ATs DRC channel it asks that sector to send it a packet at speed DRC Index 5. The mobiles 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.
AP
DRC Modu- Preamble Payload Raw C/I Index Slots lation Chips Bits kb/s db 0x0 n/a QPSK n/a 0 null rate n/a 0x1 16 QPSK 1024 1024 38.4 -11.5 0x2 8 QPSK 512 1024 76.8 -9.2 0x3 4 QPSK 256 1024 153.6 -6.5 0x4 2 QPSK 128 1024 307.2 -3.5 0x5 4 QPSK 128 2048 307.2 -3.5 0x6 1 QPSK 64 1024 614.4 -0.6 0x7 2 QPSK 64 2048 614.4 -0.5 0x8 2 QPSK 64 3072 921.6 +2.2 0x9 1 QPSK 64 2048 1,228.8 +3.9 0xa 2 16QAM 64 4096 1,228.8 +4.0 0xb 1 8PSK 64 3072 1,843.2 +8.0 0xc 1 16QAM 64 4096 2,457.6 +10.3 0xd 2 16QAM 64 5120 1,536.0 in Rev. A 0xe 1 16QAM 64 5120 3,072.0 in Rev. A
1-2005
340 - 36

Data from PDSN for the Mobile PACKET Data Ready DRC: 5 MP3, web page, or other content 2048 bits
AP
Turbo Coder Using the specifications for the mobiles requested DRC + + + + + + D D D index, the correct-size packet + + + of bits is fed into the turbo + + + + D D D coder and the right number of + symbols are created. Symbols
Interleaver
1-2005
340 - 37

AP
Interleaver
To guard against bursty errors in transmission, the symbols are completely stirred up in a block interleaver.
Block Interleaver
1-2005
340 - 38

AP
Interleaver
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.
Block Interleaver
Interleaved Symbols
1-2005
340 - 39

AP
Turbo Coder Using the specifications for the mobiles requested DRC + + + + + + D D D index, the correct-size packet + + + of bits is fed into the turbo + + + + D D D coder and the right number of + symbols are created. Symbols To guard against bursty errors in transmission, the symbols are completely stirred up in Block Interleaver 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 Interleaved Symbols will occupy the same number of transmission slots, spaced four apart. Its 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.
Interleaver
Subpacket 2
Subpacket 3
1-2005
Subpacket 1
Subpacket 4
340 - 40

AP
Turbo Coder When the AP is ready, the first + + subpacket is actually + + + + D D D transmitted in a slot. + + + The first subpacket begins with + + + + D D D a preamble carrying the + users MAC index, so the Symbols user knows this is the start of its sequence of subpackets, and how Block Interleaver many subpackets are in the sequence.. The user keeps collecting subpackets until either: 1) it has been able to reverse-turbo decode the Interleaved Symbols packet contents early, or 2) the whole schedule of subpackets has been transmitted.
Interleaver
Subpackets
1
SLOTS
4
340 - 41
1-2005
Ec/Io and C/I

There are two main ways of expressing signal quality in 1xEV-DO C/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 sectors 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 other EVDO Ec/Io is close to 0 db near a sector, and ranges down to -10 at a cells edge EVDO C/I can be above +10 db near a sector, and -20 or lower at the edge
340 - 42
AP
Relationship of C/I and Ec/Io For EV-DO Signals

mobile receive power
C I
0 0
Power from Serving Sector
Ec Io
Interference Power from other cells
Ec/Io, db
-10 -20 -30 -30
-20
-10
+10
+20
C/I, db 1-2005 Course Series 340v3.2 (c)2005 Scott Baxter
Relationship of Ec/Io and C/I in 1xEV-DO Systems

-30
Ec/Io, db C/I, db
-25
-20
-15
-10
-5
10
15
20 0
-0.04 -0.14 -0.17 -0.21 -0.27 -0.33 -0.41 -0.51 -0.64 -0.79 -0.97 -1.19 -1.46 -1.76 -2.12 -2.54 -3.01 -3.54 -4.12 -4.76 -5.46 -6.97 -8.64 -10.41 -12.27
20 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 -1 -2 -3 -4 -6 -8 -10 -12
-5
-10
Ec/Io, db
-15
-20
-25
-30
C/I, db
1-2005
340 - 43
1xEV-DO Active Set and Forward Bursting Animation

NEIGHBOR Access Point (AP) ACTIVE Access Point (AP) ACTIVE
THIS IS FOR YOU!
Access Point (AP)
Good Signal!
PACKET PLEASE!
@ x speed DRC
NEIGHBOR Access Point (AP)
ACTIVE Access Point (AP)
ACTIVE Access Point (AP)
DO-RNC
Access Node (User Terminal)
1-2005
340 - 44
1xEV-DO Forward Link Details 1xEV-DO Forward Link Details
1-2005
340 - 45
1xEV-DO Protective Coding

Forward Traffic Channel Packets or Control Channel Packets
bits symbols Encoding and Scrambling Interleaving
Discard 6-bit Encoder Tail Field Turbo Encoder with an Internallygenerated tail
Data Packet
Code Symbols
Turbo coding is the default encoding method for 1xEV-DO on both forward and reverse link The 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
Data Total Rate Slots Code (kbps) Used Rate 38.4 16 1/5 76.8 8 1/5 153.6 4 1/5 307.2 2 1/5 614.4 1 1/3 307.2 4 1/3 614.4 2 1/3 1,228.8 8 1/3 921.6 2 1/3 1,843.2 2 1/3 1,228.8 8 1/3 2,457.6 8 1/3
Bits per Packet 1,024 1,024 1,024 1,024 1,024 2,048 2,048 2,048 3,072 3,072 4,096 4,096
Bits/Pkt - Tail Field 1,018 1,018 1,018 1,018 1,018 2,042 2,042 2,042 3,066 3,066 4,090 4,090
Symbols per Packet 5,120 5,120 5,120 5,120 3,072 6,144 6,144 6,144 9,216 9,216 12,288 12,288
340 - 46
Data Scrambling in 1xEV-DO

Data Bits Turbo Encoding & Puncturing Data Scrambling Block Interleaving Symbols ready to Transmit
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-toaverage ratio and effectively uses power amplifier capability a secondary purpose is to provide enhanced privacy 1xEV-DO uses data scrambling on both links to randomize the data and avoid unbalanced waveforms the scrambling sequence is generic, not unique per user security is already provided in a standard-defined layer the generic scrambling register coefficients are specified in the standard
One Slot on the Forward Traffic Channel

Example Subpacket: 1536 Data Modulation Symbols (1 slot, 614.4 Kb/s)
PRBL
PILOT PILOT
MAC
MAC
MAC
DATA
336 chips
DATA
DATA
400 chips
MAC
DATA
64
64 96 64 400 chips Slot 1024 chips

Channel Interleaver QPSK/8PSK 16QAM Modulator Sequence Repetition, Signal Puncturing
64 96 64 400 chips Slot 1024 chips

16-ary Walsh Covers Walsh Channel Gain I Walsh Chip Level Q Summer
Data
(modulation symbols)
1/3 or 1/5 encoder scrambler
Symbol DEMUX 1 to 16 Signal Point Mapping
To Quadrature Spreading and Modulation
I Walsh Channels
TDM Time Division Multiplexer
I Sequence Repetition 0 Q
Preamble
32-symbol bi-Orthogonal MAC cover Signal Point Mapping Signal Point Mapping RPC Channel Gain DRC Lock Channel Gain Signal Point Mapping RA channel gain MAC Index Walsh Cover
MAC RPC bits A MAC channel DRC Lock symbols

Bit Repetition (xDRCLlen)
Q Walsh Channels
MAC channel RA bits
I I Walsh Sequence Chip Level Repetition Summer Q (factor=4) Q Walsh Cover 0 Signal Point Mapping 0 I Q
Bit Repetition (xRAB len)
Walsh Cover W264
Pilot Channel (all 0s)

1-2005 Course Series 340v3.2 (c)2005 Scott Baxter
340 - 48
AP
The MAC Index

MACIndex MAC Channel Use 0 and 1 Not Used 2 Not Used 3 Not Used 4 RA Channel Available for RPC and DRCLock 5-63 Channel Transmissions Preamble Use Not Used 76.8 kbps CCH 38.4 kbps CCH Not Used Available for Forward Traffic Channel Transmissions
MACIndex Walsh Code Phase
MACIndex Walsh Code Phase
MACIndex Walsh Code Phase 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q
Each active user on a sector is assigned a unique 7-bit MAC index (64 MACs possible) Each data packet begins with a preamble, using the MAC index of the intended recipient Five 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
1-2005
0 2 4 6 8 10 12 14 16 18 20 22 24 26 28
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
I I I I I I I I I I I I I I I
32 34 36 38 40 42 44 46 48 50 52 54 56 58 60
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
I I I I I I I I I I I I I I I
33 35 37 39 41 43 45 47 49 51 53 55 57 59 61
30 15 I
62 31 I
31 47 Q
63 63 Q
340 - 49
MACIndex Walsh Code Phase 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q
AP
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 much the same way as in IS-2000. The rate is 600 bps.
Reverse MAC Channel Contents

The Reverse MAC channel contains two streams of information DRC Data Rate Control channel is used by the AT to request the data rate and desired sector Data rate is requested using 8-ary bi-orthogonal coding Desired sector is requested 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 transmission RRI 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 - 51
How the DRC Channel Operates

The AT estimates the forward channel C/I and identifies the feasible data rate and the requested sector to be used The AT sends this information to the AP on the DRC channel Only the requested sector will transmit packets to this AT The requested sector sends a data packet including preamble to the AT at the rate requested by the DRC in the immediately preceding slot After the packet transmission is initiated, it must be continued until the payload has been fully transmitted
1-2005
340 - 52
The Hybrid ARQ Process

CDMA2000 1xEV-DO
AP Access Point AT Access Terminal
Application layer Stream layer Session layer Connection layer Security layer MAC layer Physical layer HARQ protocol
CDMA2000 1xRTT
SYSTEM
Application layer LAC layer MAC layer Physical layer RLP Radio Link Protocol MAC layer Physical layer Application layer LAC layer RLP Radio Link Protocol
Application layer Stream layer Session layer Connection layer Security layer MAC layer Physical layer HARQ protocol
F-FCH R-FCH
F-TFC repeats R-ACK
In 1xRTT, retransmission protocols typically work at the link layer Radio Link Protocol (RLP) communicates using signaling packets lost data packets arent recognized and are discarded at the decoder This method is slow and wasteful!
1-2005
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 ACK This method is fast and efficient!
340 - 53
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 its 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 - 54
Construction of a Forward Link Packet

bits symbols Encoding Interleaving
Subpacket Subpacket Subpacket Subpacket Subpacket
Data Packet
Physical Layer Packets encoded, interleaved, broken into subpackets each subpacket is a unique coded representation of the packet Each subpacket is sent independently during one slot Subpackets are sent in sequential order with a three-slot gap between successive subpackets
Forward Channel
Packet Subpacket 0 other other other 0 other other other 0 other other other 0 other other other 1 0 pkts pkts pkts. 1 pkts. pkts. pkts. 2 pkts. pkts pkts 3 pkts pkts pkts 0
Traffic
One Slot
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
Multislot Packet Timing, Normal Termination

AP
User A Packet 0 Subpacket 0 diff. diff. diff. user user user A 0 1 diff. diff. diff. user user user A 0 2 diff. diff. diff. user user user A 0 3 diff. diff. diff. user user user A 1 0
F-Traffic
AT
R-DRC
1/2 Slot offset
pr e NA par K e pr e NA par K e
de co de co de co de co
R-ACK
One Slot
de
ci d
de
ci d
pr e NA par K e
de
ci d
de
ci d
NAK
NAK
NAK
AT selects sector, sends request for data AP starts sending next packet, one subpacket at a time After each subpacket, AT either NAKs or AKs on ACK channel In this example, AP transmits all 4 scheduled subpackets of packet #0 before the AT is finally able to decode correctly and send AK then the AP can begin packet #1, first subpacket
pr e NA par K e
de
de
de
de
AK!
Multislot Packet Timing, Early Termination

AP
User A Packet 0 Subpacket 0 diff. diff. diff. user user user A 0 1 diff. diff. diff. user user user A 1 0 diff. diff. diff. user user user A 1 1 diff. diff. diff. user user user A 2 0
F-Traffic
AT
R-DRC
1/2 Slot offset
pr e NA par K e pr e NA par K e
de co de co de co de co
R-ACK
One Slot
de
ci d
de
ci d
pr e NA par K e
de
ci d
de
ci d
NAK
AK!
NAK
AT selects sector, sends request for data AP starts sending next packet, one subpacket at a time After each subpacket, AT either NAKs or AKs on ACK channel In 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
pr e NA par K e
de
de
de
de
AK!
Multiple ARQ Instances

bits
symbols
Data Packets
Encoding Interand Scrambling leaving
Packet 0
Subpackets
Packet 1
Subpackets
Packet 2
Subpackets
Packet 3
Subpackets
Forward Channel
Packet Subpacket
0 0
1. 0
2. 0
3. 0
0 1
1. 1
2. 1
3. 1
0 2
1. 2
2. 2
3. 2
0 3
1. 3
2. 3
3. 3
Traffic
One Slot
Definition: Number of ARQ Instances the maximum number of packets that may be in transit simultaneously sometimes also called the number of ARQ channels This figure and the preceding page appear to show 4 ARQ instances Packets in the different ARQ instances may be for the same user (the most common situation) may be for different users (determined by QOS and scheduling) Destination mobile knows its packets by their preamble
Reverse Power Control

600 bits per second
AP
Stronger than target SNR? SNR target
Reverse RF
RX RF Digital Open Loop Closed Loop
TX RF Digital
Access Terminal 1xEV-DO reverse link power control is similar to IS-95/IS-2000 1xEV-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 rate Power control bits are sent on the forward MAC channel one bit per slot (thats 600 per second), sent as four symbols -one in each of the MAC periods of that slot
Reverse Rate Control Reverse Rate Control
1-2005
340 - 60
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 UnicastReverseRateLimit message 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 ATs 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 - 61
Reverse Rate Control Table
1-2005
340 - 62
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 than the 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 - 63
1xEV-DO Rev. A 1xEV-DO Rev. A
1-2005
340 - 64
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 - 65
1xEV-DO Rev. A Differences

Everything weve 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 - 66
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 - 67
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 - 68
Available Link Rates in 1xEV-DO Rev. A

FORWARD LINK
DRC Modu- Preamble Payload Raw Index Slots lation Chips Bits kb/s 0x0 n/a QPSK n/a 0 null rate 0x1 16 QPSK 1024 1024 38.4 0x2 8 QPSK 512 1024 76.8 0x3 4 QPSK 256 1024 153.6 0x4 2 QPSK 128 1024 307.2 0x5 4 QPSK 128 2048 307.2 0x6 1 QPSK 64 1024 614.4 0x7 2 QPSK 64 2048 614.4 0x8 2 QPSK 64 3072 921.6 0x9 1 QPSK 64 2048 1,228.8 0xa 2 16QAM 64 4096 1,228.8 0xb 1 8PSK 64 3072 1,843.2 0xc 1 16QAM 64 4096 2,457.6 0xd 2 16QAM 64 5120 1,536.0 0xe 1 16QAM 64 5120 3,072.0 C/I db n/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 Payload Bits 128 256 512 768 1024 1536 2048 3072 4096 6144 8192 12288 Modulation B4 B4 B4 B4 B4 Q4 Q4 Q2 Q2 Q4Q2 Q4Q2 E4E2
REVERSE LINK
Effective Rate kbps after: 4 slots 8 slots 12 slots 16 slots 19.2 9.6 6.4 4.8 38 19.2 12.8 9.6 76 38.4 25.6 19.2 115 57.6 38.4 28.8 153 76.8 51.2 38.4 230 115 76.8 57.6 307 153 102.4 76.8 461 230 153.6 115.2 614 307 204.8 153.6 921 461 307 230.4 1228 614 409 307.2 1843 921 614 460.8 Code Rate (repetition) after 4 slots 8 slots 12 slots 16 slots 1/5 1/5 1/5 1/5 1/5 1/5 1/5 1/5 1/4 1/5 1/5 1/5 3/8 1/5 1/5 1/5 1/2 1/4 1/5 1/5 3/8 1/5 1/5 1/5 1/2 1/4 1/5 1/5 3/8 1/5 1/5 1/5 1/2 1/4 1/5 1/5 1/2 1/4 1/5 1/5 2/3 1/3 2/9 1/5 2/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 standard The 1xEV-DO Rev. A forward has two available modes offering higher speeds than available in Rev. 0.
Basic Access Terminal Basic Access Terminal Architecture and Operation Architecture and Operation
1-2005
340 - 70
How Does an Access Terminal Work?

summing time-aligned
Chips
control
Traffic Correlator PN xxx Walsh xx Receiver RF Section IF, Detector AGC RF Duplexer RF Open Loop Traffic Correlator PN xxx Walsh xx Traffic Correlator PN xxx Walsh xx Pilot Searcher PN xxx Walsh 0
bits
Digital Rake Receiver Symbols Traffic Correlator PN xxx Walsh xx
Symbols
power
Viterbi Decoder, Convl. Decoder, Demultiplexer
Packets
UART Conv or Turbo Coder
Messages
CPU
Transmit Gain Adjust Messages Transmitter Digital Section Long Code Gen.
Transmitter RF Section
1-2005
340 - 71
1xEV-DO Forward Link: AT Rake Receivers

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

All Active Set sectors can listen to the AT
Access Terminal
Rake Receiver PN Walsh PN RF PN PN Walsh Walsh Walsh Pilot Ec/Io
user data
AP
DO-RNC chooses cleanest packet
AP
Searcher PN W=0
The AT uses the Route Update protocol to frequently update its preferences of which sectors it wants in its active set Frame-by-frame, all the sectors in the Active Set listen for the ATs signal Each sector collects what it heard from the AT, and sends it back to the DO-RNC. The DO-RNC uses the cleanest (lowest number of errors) packet
1xEV-DO Route Update Mechanics

Access Terminal
DO-RNC
Sel.
AP AP
Rake Receiver PN Walsh
? ?
PN RF PN PN
Walsh Walsh Walsh
user data
Searcher PN W=0
Pilot Ec/Io
1xEV-DO Route Update is driven by the Access Terminal Access Terminal continuously checks available pilots Access Terminal tells system pilots it currently sees System puts those sectors in the active set, tells Access Terminal Access terminal requests data bursts from the sector it likes best tells which sector and what burst speed using the DRC channel so there is no Soft Handoff on the forward link, just fast choices All sectors in Active Set try to hear AT, forward packets to the DO-RNC so the reverse link does benefit from CDMA soft handoff
Route Update Pilot Management Rules

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

The Traffic Channel Assignment Message assigns all or some of the sectors the access terminal requested in its most recent Route Update request The message lists every Active pilot; if it doesnt list it, its not approved as active Notice the MAC index and DRC Cover so the access terminal knows how to request forward link bursts on the data rate control channel
Neighbor Structure Maintained by the AT
Pilot PN Channel SrchWinSize SrchWinOffset
1-2005
340 - 76
1xEV-DO Network Architecture 1xEV-DO Network Architecture
1-2005
340 - 77
CDMA Network for Circuit-Switched Voice Calls
(C)BSC/Access Manager Switch
PSTN
t1
t1
SEL
t1
CE
BTS
The first commercial IS-95 CDMA systems provided only circuitswitched voice calls
1-2005
340 - 78
CDMA 1xRTT Voice and Data Network

PDSN Foreign Agent Backbone Network
Authentication Authorization Accounting
Internet VPNs
PDSN Home Agent
AAA
Switch
(C)BSC/Access Manager
PSTN
t1
t1
SEL
t1
CE
BTS
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
1xEV-DO Overlaid On Existing 1xRTT Network

PDSN Foreign Agent Backbone Network
Authentication Authorization Accounting
Internet VPNs
PDSN Home Agent
DO Radio Network Controller

(C)BSC/Access Manager
DO-OMC
AAA
Switch
CE
PSTN
t1
t1
SEL
t1
CE
BTS
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 addition Existing PDSNs and backbone network are used with minor upgrading The following sections show Lucent, Motorola, and Nortels specific solutions
Lucent 1xEV-DO Architecture Lucent 1xEV-DO Architecture
1-2005
340 - 81
Lucent 1xEV-DO Radio Access Network (RAN)

OMP FX Element Management System AP
T-1/E-1 Ethernet RF
AAA Server Downlink Input Router
Router
AP
Uplink Input Router
Flexent Mobility Server
AP
RF User ATs (Access Terminals)

AP
Uplink Input Router
Downlink Input Router
Packet Data Serving Node (PDSN)
Internet
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.
Details of Lucent RAN Elements

OMP FX Element Management System AP
T-1/E-1 Ethernet RF
AAA Server Downlink Input Router
Router
AP
Uplink Input Router
AP
RF User ATs (Access Terminals)

AP
Uplink Input Router
Downlink Input Router
Packet Data Serving Node (PDSN)
Internet
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 - 83
1xEV-DO in Lucent Flexent Mod Cell Cabinets

Lucent Mod Cell cabinets can support up to three IS-95 or 1xRTT carriers on three sectors 1xEV-DO CDMA Digital Modules (CDM) can be mixed with conventional CDMs in the same cabinet the same RF hardware (filters, amplifiers, other RF components) can be used for IS-95, 1xRTT, and 1xEV-DO
1-2005
340 - 84
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 - 85
1xEV-DO in Lucent Mod Cell 4.0 Cabinets

The Mod Cell 4 cabinet comes in many variations Instead of per-carrier dedicated CDMs, resources are pooled URCs (Universal Radio Controllers) are used to steer data 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
340 - 86
FMS
Universal Radio Controller (URC)
Digital Shelf Evolution Carr1 Flow Modem

(4.0 EVM) Carr 2, 3 CDMA Modem Unit (CMU) Universal Antenna CDMA Radio (UCR)
ECP
Universal Radio Controller (URC)
1-2005
Lucent 1xEV-DO Flexent Mobility Server (FMS)

The Flexent Mobility Server is the heart of the Radio Access Network It provides four processors running the 1xEV-DO Application Processor (DO-AP), which provides the Packet Controller Function (PCF) The PCF provides air link and radio resource management to implement 1xEV-DO user sessions, including the dormant state and other DOspecific features
1-2005
340 - 87
Motorola 1xEV-DO Architecture Motorola 1xEV-DO Architecture
1-2005
340 - 88
Motorola 1xEV-DO System Architecture

MSC MM/SDU
VPU
OMC-IP
OMC-DO BSC-DO AN-DO
AAA AN-AAA PDSNs
OMC-R
Elements Existing IS-95 New 1xEV-DO Shared IS-95/DO
1x-AN 1x-BTS MCC-DO
Packet Core Network
HAs
Connections IS-95/1x 1xEV-DO Shared 1x/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 - 89
New Motorola 1xEV-DO Network Elements

MSC MM/SDU
VPU
OMC-IP
OMC-DO BSC-DO AN-DO
AAA AN-AAA PDSNs
OMC-R
Elements Existing IS-95 New 1xEV-DO Shared IS-95/DO
1x-AN 1x-BTS MCC-DO
Packet Core Network
HAs
Connections IS-95/1x 1xEV-DO Shared 1x/DO
MCC-DO (Multi-Channel Controller - Data Only) AN-DO (Access Node - Data only) CR (Consolidation Router) Similar in function to the 1x-AN MGX LSW (Layer 3 Switch) Similar in function to the 1x-AN CATs BSC-DO (Base Station Controller-Data Only) Mobility functions like 1x MM - Packet Control & Selection like SDU OMC-DO (Operations & Maintenance Center - Data Only) LMT (Local Maintenance Terminal)
Motorola 1xEV-DO Block Diagram and Network Upgrade Summary

BTS
1x BBX RF Front End 1x Modems DO BBX
BSC-DO
MCC-DO AN-DO
IS-2000 1xEV-DO Tool LMF LMT BTS frame & CCP shelf LPA BBX-1X BTS MCC-1X MCC-DO GLI (Traffic) GLI (Control) AN (MGX8800) CR AN AN (Catalyst 6509) LSW BSC CBSC BSC-DO OMC-R O&M OMC-DO UNO PDSN (Note 1) IP Network Telephone Network MSC/HLR Not Required Data Network Not Required AAA
BTS
CR
LSW
PDSN
T1 or E1
MCCDO
OMC-DO
AN-AAA
1-2005
340 - 91
BTS
Motorola MCC-DO Functions

BSC-DO
MCC-DO
AN-DO
BTS
CR
LSW
PDSN
T1 or E1
MCC-DO
OMC-DO
AN-AAA
1xEV-DO Modem 1 carrier, 3 sectors per MCC-DO card Supports 59 channels per sector Span 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
MCC- DO
Motorola 1xEV-DO AN-DO Elements

BTS
MCC-DO
BSCDO
AN-DO
BTS
CR
LSW
PDSN
T1 or E1
MCC-DO
OMC-DO
AN-AAA
CR
LSW
Consolidation Router (CR) Performs span aggregation for DO access points Similar to 1x MGX 1 2 CR frames per BSC-DO Layer 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
1-2005
340 - 93
BTS
Motorola BSC-DO Functions

BSC-DO
MCC-DO
AN-DO
BTS
CR
LSW
PDSN
T1 or E1
MCC-DO
OMC-DO
AN-AAA
BSC 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-DO 1 OMC-DO per each BSC-DO
1-2005
340 - 94
Motorola 1xEV-DO Network Elements: OMC-DO

BTS
BSC-DO
MCC-DO
AN-DO
CR LSW
PDSN
BTS
T1 or E1
MCC-DO
OMC-DO
AN-AAA
DO network element manager Manages BSC-DO and MCCDO Ethernet interface to BSCDO Supports network management applications (fault, alarm, performance, configuration) 1-2005
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
340 - 95
Nortel 1xEV-DO Architecture Nortel 1xEV-DO Architecture
1-2005
340 - 96
A Typical Nortel CDMA2000 System

Providing 1xRTT Voice, Data, and 1xEV-DO
1-2005
340 - 97

Providing Only 1xRTT Voice, Data
1-2005
340 - 98

Providing 1xEV-DO Only
1-2005
340 - 99
Nortel Multiple Backhaul and Configuration Possibilities
1-2005
340 - 100
Nortel Univity Indoor Metrocell

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
Univity CDMA Metro Cell Indoor Base Transceiver System (AP)
Nortel Metrocell LD (for rural sites)
XCEM/ DOM GPSTM CM CORE Fan tray
MiniBIP Radio Module 36 (0.91m) AC Rectifier
Key Feature small size, fits in any corner Configurations 1-3 Carrier OMNI Expandable to 3 sectors Single carrier high power Power source + 24VDC available Standard Metro Cell modules
24 (0.61m)
Metro Cell LD Rack Mounted Supporting 3 sectors
1-2005
340 - 102
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 - 103
Nortels DO-RNC The Data-Only Radio Network Controller

DO-RNC is the heart of a 1xEV-DO network, located at the central office (CO) with the BSC and/or BSS Manager (BSSM) DO-RNC is a stand-alone node supporting 1xEV-DO. It manages: DOMs at 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). Nortel DO-RNC connections from airlink to PDSN over Data-Only standard A10-A11 interfaces Radio Network Controller 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-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
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
1-2005 Course Series 340v3.2 (c)2005 Scott Baxter
TN-1X
STM-1
340 - 106
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 AP The 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
The Nortel DO-EMS Server and Client

The DO-EMS server is a Sun Netra20 normally located in the central office with the BSC/DO-RNC Software modules on the server perform: auto-discovery configuration management security management fault management performance management DO-EMS Client / Management Terminal since the Netra20 is a headless server, a terminal is required for monitor, keyboard and mouse functionality The 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
The Nortel DO-EMS Client

The DO-EMS client is webbased 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 - 109
Nortels 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 the Shasta BSN 5000 chassis. With the addition of the AT IP access model, a Foreign Agent (FA) and Home Agent (HA) are required. The FA is always integrated onto the Shasta BSN with the Univity PDSN resulting in the PDSN/FA. Component Breakdown The 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 - 110
Nortel Shasta BSN Hardware Description

Hardware Description The Shasta BSN chassis consists of a card cage with 14 slots for cards, a fan tray for cooling; power entry and distribution and the backplane. The chassis mounts in a standard 19 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 required components are as follows: Line Card (LC) Subscriber Service Module (SSM II) Subscriber Service Card (SSC) Control and Management Card (CMC) Switch Fabric Card (SFC) Shasta Chassis (BSN) Service Creation System (SCS) Server and Client Shasta BSN Software Cabinet
1-2005
340 - 111
Nortels Passport 8600 Routing Switch

Passport 8600 Routing Switch delivers high-density Layer 2 and Layer 3 wirespeed 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 moduleHighperformance 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, fullfeatured LAN/WAN connectivity with full functionality and intelligence of the Passport 8600 ATM/SONET/SDH 2-slot MDA BaseboardSupports 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 - 113
Nortel CDMA Univity Base Station Controller EBSC

PP15K Breaker Interface Panel PP15K Fiber Tray
GPSTM
Cable Trough
GPSTM
Cable Consolidation and Multiplexing Chassis
Cable Trough
The Univity CDMA Base Station Controller CBRS is a scalable and cost reduced IP enabled Base Station Controller Eliminates the need for separate BIU and CIS cabinets in the BSC for 1xEV-DO nonMTX systems Key Features: Scalable from very low to very high capacity through module additions Multiple frames deployed for configuration flexibility
7
24pBCNW Functional Processor (NTPB11AA) 11pMSW Functional Processor (NTPB10AA)
Cable Trough
CP3 - Control Processor (NTHR06CA) Optional - 2nd Enhanced BSC Frame Connectivity
8 9 1 0 1 1 1 2 1 3 1 4 1 5
Cable Trough
Cable Consolidation and Multiplexing Chassis (NTPB13AA) GPSTM - Global Positioning Satellite Timing Module (NTPB15AA)
1-2005
340 - 114
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 STM1 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 - 115
Pre-EBSC Hardware Required for Nortel 1xEV-DO Non-MTX Systems
BI
U, UNI CI VIT S, BS Y E M BS IN C A CO SI NG MB LE INE CA S BI NE T
No no t R vo eq no i c ui vo e u red co se ! de rs, rs
1-2005
340 - 116
Nortels 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)
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 TMNs (Telecommunication Management Network) functional layer approach, the BSS Manager is the Element Manager and is the operators 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 Managers 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 components Diagnostic Data - debugging information on messages among subsystems for troubleshooting Security management deals with security breaches (improper use) of network resources. Security management consists of software applications used to configure, control, create or delete the resources providing the services. Security Management also includes administration of security procedures and functions.
1-2005
340 - 118
EV-DO-Specific Nortel Documentation

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

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

1.00 411-2133-101 12.06
1-2005
340 - 119
1xEV-DO // 1xRTT 1xEV-DO 1xRTT Interoperability Interoperability
1-2005
340 - 120
1xEV-DO/1xRTT Interoperability
The CDMA2000 1xEV-DO Standard IS-856 makes no provision for any kind of handoff to or from any other technology Driven by Operator interest, a Hybrid mode has been developed to provide some types of handoff functions to the best extent possible Hybrid Mode is a mobile only function neither the EV nor 1xRTT network knows anything 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
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-users awareness in other cases, this is not possible
1-2005
340 - 122
Hybrid Mode Transition Scenarios

1:2 Deployment 1:1 Deployment EV-DO, F2 1xRTT, F1 1:1 Deployment
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 area Initial system acquisition is also involved as a user activates their AT in different locations These transitions are dependent on the Hybrid mode implementation in the AT The following pages show some possible transitions assuming Mobile IP and AT Hybrid Mode are implemented
1-2005
340 - 123
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 channel During 1xRTT traffic operation, the hybrid-aware mobile is unable to break away; 1xRTT traffic operation is continuous no opportunity to see 1xEV-DO signal This hybrid Idle mode capability is the foundation for all 1xRTT/1xEV mode transfers the network does not trigger any transfers
1xEV-DO Idle
1xEV-DO Active
Idle Mode
Hybrid Mode 1xRTT Idle

Idle Mode
1xRTT Active
1-2005
340 - 124
Hybrid Dual-Mode Idle Operation 1xRTT / 1xEV-DO Paging Interoperability

16-frame Control Channel Cycle 16 slots of 26-2/3 ms = 426-2/3 ms
LONGEST POSSIBLE PACKET DRC 16 Subpackets
1xRTT Minimum Slot Cycle Index: 16 slots of 80 ms each = 48 26-2./3 ms frames
A dual-mode 1xRTT/1xEV-DO mobile using slotted-mode paging can effectively watch the paging channels of both 1xRTT and 1xEV-DO at the same time How is it possible for the mobile to monitor both at the same time? The paging timeslots of the two technologies are staggered Three of the 16 timeslots in 1xRTT conflict with the control channel slots of 1xEV-DO However, conflicts can be avoided by page repetition, a standard feature in systems of both technologies
Initial System Acquisition by Hybrid Mobile when 1xEV-DO is NOT Available

1xEV-DO Active 1xEV-DO Idle
Acquire 1xEV-DO System driven by PRL
no, cant see EV
Acquire 1xRTT System driven by PRL
Register with 1xRTT Network
1xRTT Idle
Idle Mode Classical 1xRTT Idle Mode
After entering this state, the mobile will not search for 1xEV service again Voice Page! Idle Mode Release
1xRTT Active
1xRTT Voice Call
1-2005
340 - 126
Initial System Acquisition by Hybrid Mobile when 1xEV-DO is Available

1xEV-DO Active
Set Up or Re-establish 1xEVDO Data Session 1xEV Traffic interrupted during 1xRTT voice call 1xEV Traffic Data Connection Closed
Triggers:
1xEV-DO Idle
Acquire 1xEV-DO System driven by PRL
yes, found EV Idle Mode
AT Data Ready! AN Data Page!
Idle Mode
Hybrid Mode
Acquire 1xRTT System driven by PRL Register with 1xRTT Network
Hybrid Mode
Voice Page! Idle Mode
Hybrid Mode
Idle Mode
1xRTT Idle
Idle Mode
Idle Mode
Release
1xRTT Active
1xRTT Voice Call
1-2005
340 - 127
In-Traffic: EV-DO Fade with 1xRTT Available
Fade
1xEV-DO Active
AT data ready
Traffic Mode, Data Transfer
Close Connection
PPP Resync MIP Registr.

AN data ready
Fade
1xEV-DO Idle
Get New UATI Dormant /Idle DO System Acquired

no
Same DO Subnet?
1xRTT Idle
Idle Mode
Dormant /Idle
1xRTT Active
Reestablish Call
Resume Data Transfer
Transfer Finished
1-2005
340 - 128
Transition In-Traffic: Lost EV-DO and 1xRTT
Fade
1xEV-DO Active
Close Connection
Set Up or Re-establish 1xEVDO Data Session Get New UATI

No
1xEV Traffic
Fade
1xEV-DO Idle
DO PRL, Idle Search for Mode DO
Found New DO Signal!!
Triggers: AT Data Ready! AN Data Page!
Same DO Subnet? Yes
Idle Mode
Idle Mode
Hybrid Mode
Fade
Idle Mode Use 1x PRL, Search for 1xRTT Use 1x PRL, Search for 1xRTT
No Signal Found!!
1xRTT Idle
Idle Mode
Lost Signal!!
No Signal Found!!
No 1x Signal, Continue EV Operation
1xRTT Active
1-2005
340 - 129
Dormant Session, EV-DO Lost > 1xRTT > 1xEV-DO
1xEV-DO Active
Coverage Edge
Fade

Data Finished, Call Dormant Fade Found New DO Signal!!
1xEV-DO Idle
Get New UATI

No
Idle Mode
DO PRL, Search for DO
No Signal Found!!
DO PRL, DO Available?
No Signal Found!!
No Signal Found!!
Same DO Subnet? Yes
Idle Mode
Hybrid Mode
Idle Mode
1xRTT Idle
Idle Mode
Idle Mode
1xRTT Active
1-2005
340 - 130
IS-871 For Session Interoperability

Lack of RF transition trigger definitions has been largely resolved by the Hybrid Mode of dual-mode terminals The 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 - 131
cdma2000 to HRPD Dormant Packet Data Session Handoff - Existing HRPD Session
1-2005
340 - 132
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.
cdma2000 to HRPD Dormant Packet Data Session Handoff - New HRPD Session
1-2005
340 - 134
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 A11Registration 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 - 135
HRPD to cdma2000 Dormant Packet Data Session Handoff
1-2005
340 - 136
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.
MS/AT Terminated Voice Call During Active HRPD Data Packet (Intra-PDSN/Inter-PCF)
1-2005
340 - 138
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 A11Registration 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 TA8setup. 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 A9Release-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 - 139
AT Leaving During an Active 1xEV-DO Data Session
1-2005
340 - 140
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. ments i. 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.
MS/AT Terminated Voice Call During Active HRPD Packet Data Session (Intra-PCF)
1-2005
340 - 142
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 - 143
cdma2000 to HRPD Active Packet Data Session Handoff Status Management Supported by Feature Invocation
1-2005
340 - 144
cdma2000 to HRPD Active Packet Data Session Handoff Status Management Supported by Feature Invocation
a. The MS/AT sends an Origination Message, including the feature code as the called number, to the BS when the MS/AT starts the HRPD communication. This feature code indicates that the MSC should activate a feature (e.g., 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.
An Introduction to the An Introduction to the IS-856 Standard for 1xEV-DO IS-856 Standard for 1xEV-DO
1-2005
340 - 146
Conceptual Framework of the IS-856 Standard

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

Default Signaling Application
Signaling Network Protocol Signaling Link Protocol
Default Packet Application

Radio Link Protocol
Flow Control Protocol Location Update Protocol
Application
layer
Stream Protocol Session Management Protocol Air Link Management Protocol Packet Consolidation Protocol Security Protocol Control Channel MAC Protocol Address Management Protocol Initialization State Protocol Route Update Protocol Key Exchange Protocol Forward Traffic Channel MAC Protocol Authentication Protocol Access Channel MAC Protocol Idle State Protocol Session Configuration Protocol Connected State Protocol Overhead Messages Protocol Encryption Protocol Reverse Traffic Channel MAC Protocol
Stream
layer
Session
layer
Connection
layer
Security
layer
Mac
layer
Physical Layer Protocol
Physical
layer
1-2005
340 - 148
Channels and Layer-3 Messages Channels and Layer-3 Messages in 1xEV-DO Call Processing in 1xEV-DO Call Processing
1-2005
340 - 149
Dissecting a Layer-3 Message

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

Pilot Channel
No Messages Access Network (AN) Access Point (AP) Access Terminal (AN)
Pilot Channel
No Messages
Control Channel
ACAck Access Parameters Broadcast Reverse Rate Limit Connection Deny Data Ready Hardware ID Request Keep Alive Request Keep Alive Response Location Request Location Assignment Redirect Session Close Sync SectorParameters Page Quick Config Xoff Response Xon Response Traffic Channel Assignment UATI Assignment
Access Channel
Connection Request Data Ready ACK Hardware ID Response Keep Alive Request Keep Alive Response Location Complete Location Notification Route Update Session Close UATI Request UATI Complete Xoff Request Xon Request
1-2005
340 - 151
Message Vocabulary: Connected State

Forward Traffic Channel
ANKey Complete Attribute Override Configuration Complete Configuration Request Configuration Response Configuration Start Connection Close Data Ready Hardware ID Request Keep Alive Request Keep Alive Response Key Request Location Assignment Location Request Nak Neighbor List Redirect Reset Reset ACK Reset Report RTC ACK Session Close Traffic Channel Assignment UATI Assignment Unicast Reverse Rate Limit Xoff Response Xon Response
Access Point (AP)
Reverse Traffic Channel

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

In 1xEV-DO, most call processing events are driven by messages The MAC channels in both directions are used to carry messages or specific Walsh Masks to convey commands and selection options Messages have priority and delivery protocols Each message has a channel or channels on which it may be sent The structure of all the 1xEV-DO messages is defined in IS-856
340 - 153
1xEV-DO Protocol Layers and Packet Encapsulation

Application Layer Stream Layer Session Layer Connection Layer Encryption Layer Authentication Layer Security Layer
Header Applicaton Layer Packet
Header
Payload
Packet
Packet
Payload
Header
Payload
Pad
Header
Payload
Trailer
Header
Payload
Trailer
Header
Payload
Trailer
Header
Payload
Trailer
MAC Layer
MAC Header
MAC Payload
MAC Trailer
Physical Layer
Physical Layer Payload
1-2005
340 - 154
Appendix: Protocols of the Appendix: Protocols of the IS-856 1xEV-DO Standard IS-856 1xEV-DO Standard
1-2005
340 - 155
ALL the 1xEV-DO Protocols

Page 1 of 2
1-2005
340 - 156
ALL the 1xEV-DO Protocols
Page 2 of 2
1-2005
340 - 157
Default Packet Application Radio Link Protocol
Application layer
Stream layer Session layer
Connection layer
IS-856 Protocol Survey
Security layer Mac layer Physical layer
The following section shows basic information on each layer in the IS-856 protocol stack Most protocols are briefly described along with fundamental details of their states and operation Weve tried to take the shalls and shoulds of legal standard-talk out of the way so you can dig in and understand whats really happening, and why For 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 manufacturers documentation
never drive or operate heavy machinery while reading the CDMA standards
1-2005
340 - 158
Application layer
Connection layer
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 0s.
1-2005
340 - 159
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 0s.
1-2005
340 - 160
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.
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 - 162
Modulation and Reverse Channel Structure

The 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 long Walsh Code 8 16 chips long carries the DRC channel But DRC bits are pre-mixed with a Walsh Code #0-#7 8 chips long corresponding 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.
Reverse Traffic Channel Coding and Modulation Parameters
Data Rate 4.8 9.6 19.2 38.4 76.8 153.6 Kbps Reverse Rate Index 1 2 3 4 5 6 Encoder Packet Size 256 512 1024 2048 4096 8192 bits Packet Duration 53.33 53.33 53.33 53.33 53.33 53.33 ms Overall Code Rate 0.25 0.25 0.25 0.25 0.25 0.5 Bits/sym Code Symbols/ Code 1024 2048 4096 8192 16384 16384 Symbols Packet Code Symbol Rate 19.2 38.4 76.8 153.6 307.2 307.2 Ksps Interleaved Packet 16 8 4 2 1 1 Repeats Mod. Symbol Rate 307.2 307.2 307.2 307.2 307.2 307.2 Ksps Data Modulation BPSK BPSK BPSK BPSK BPSK BPSK PN Chips per PN Chips 256 128 64 32 16 8 Encoder Bit
1-2005
340 - 164
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, thats 1-2/3 ms When transmitting, the access terminals 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, theres nothing to report and the ACK Channel isnt 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 - 165
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 users 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 hasnt 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 1 Bottom 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.
Tracking ACKs and NAKs

Curious?
What are
Band Classes?
Band Frequency Class Range 0 800 MHz. 1 1900 MHz. 2 TACS 3 JTACS 4 Korean PCS 5 450 MHz. 6 2 GHz. 7 700 MHz. 8 1800 MHz. 9 900 MHz.
1-2005
340 - 167
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 - 168
Reverse Traffic Channel Structure
1-2005
340 - 169
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 terminals 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 - 170
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 Channel The access terminal responds with an ACK Channel bit after every Forward Traffic Channel slot containing either preamble or data meant for it to hear. Its 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 doesnt 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 isnt 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 its always transmitted on the I phase channel.
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 FrameOffset sent 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 - 172
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 timedivision multiplexed and transmitted at the same power level. The power level doesnt vary!
1-2005
340 - 173
How All the
Forward Channels are Assembled and Combined
The TDM?
Thats not an analog combiner like in IS-95. Its 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 theres 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.
Forward Channel Walsh Composition

Forward Traffic Channel or Control Channel Time Division Multiplexer
Preamble Pilot Channel MAC Channel
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 inphase 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
Forward Channel Multiplexing
1-2005
340 - 177
The Three Adaptive Modulations of 1xEV-DO
QPSK 8-PSK 16-QAM

Forward Traffic Channel Coding and Modulation Parameters
Data Rate (kbps) Concatenated Code rate Information Bits per Encoder Packet Effective no. of Tail Bits Code Interleaver length (binary symbols) PN Generator for Code Interleaver Encoder Output Block Length (code symbols)
1-2005
38.4, 76.8, 153.6 102.4, 153.6 Long, Short, 204.8, 307.2 307.2 Short, 614.4 Long 1/4 1019 0.25 2046 P11[x] 4096 1/4 4091 0.25 8190 P13[x] 16384
921.6
1,228.8 1,843.2 2,457.6
3/8 3067 0.25 6142 P13[x] 8192
1/2 2043 0.25 3070 P12[x] 4096
1/2 3067 0.25 4606 P13[x] 6144
1/2 4091 0.5 6142 P13[x] 8192
340 - 179
Generic Configuration Protocol

The Generic Configuration Protocol provides a means to negotiate protocol parameters. The protocol uses a ConfigurationRequest message and a ConfigurationResponse message 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 initiators 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 ConfigurationRequest message, only one is sent If the ordered attribute value lists are too long for one ConfigurationRequest message, 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 - 180
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
MAC Layer Packet Encapsulation on the Control Channel
1-2005
340 - 182
MAC Layer Packet Encapsulation on the Access Channel
1-2005
340 - 183
MAC Layer Packet Encapsulation on the Forward and Reverse Traffic Channels
1-2005
340 - 184
Application layer
MAC Protocol for the Control Channel
Connection layer
The Default Control Channel MAC Protocol gives the procedures and messages required to run the Control Channel The 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 the access terminal receives the Control Channel.
Application layer
MAC Protocol for the Access Channel
Connection layer
The Default Access Channel MAC Protocol gives the procedures and messages 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 doesnt 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.
Application layer
Access Channel Probing
Connection layer
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.
Application layer
Connection layer
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 terminals DRC Fixed Rate State: the Forward Traffic Channel is transmitted to the access terminal from one particular sector, at one particular rate.
Application layer
Connection layer
MAC Protocol for the Reverse 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.
Application layer
Security Protocol
Connection layer
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 functions Security Protocol provides public variables needed by the authentication and encryption protocols (e.g., cryptosync time-stamp, etc.).
1-2005
Security Layer Encapsulation
340 - 190
Application layer
Connection layer
Key Exchange Protocol
1-2005
340 - 191
Application layer
Connection layer
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.
Application layer
Connection layer
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 - 193
Application layer
The Connection Layer
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.
Application layer
Connection layer
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 - 195
Application layer
Connection layer
Route Update Protocol
Route Update Protocol: keeps track of an access terminals 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 terminals 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 - 196
Application layer
Default Route Update Protocol
Connection layer
The Default Route Update Protocol keeps track of the access terminals 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 terminals Active Set. Route update messages from the access terminal to the access network are based on changing radio link conditions.
Application layer
Route Update Reporting Rules
Connection layer
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.
Application layer
Overhead Messages Protocol
Connection layer
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
Application layer
Connection layer
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 hasnt 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
1-2005
340 - 200
Application layer
Connection layer
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.
Application layer
Idle State Protocol
Connection layer
Idle State Protocol: manages an access terminal that has acquired the network, but does not have an open connection. keeping track of the access terminals 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 - 202
Application layer
Connected State Protocol
Connection layer
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 procedures The 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
Application layer
Session Management Protocol
Connection layer
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.
Application layer
Address Management Protocol
Connection layer
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.
Application layer
Session Configuration Protocol
Connection layer
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.
Application layer
Session Configuration Protocol
Connection layer
1-2005
340 - 207
Application layer
Default Session Configuration Protocol:
Connection layer
Extensive Negotiation Procedure
1-2005
340 - 208
Application layer
Stream Protocol
Connection layer
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
Application layer
Connection layer
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 for messages using reliable delivery. It does not ensure in-order delivery. The SLP fragmentation layer (SLP-F) provides fragmentation for SLPD packets.
Application layer
Connection layer
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 - 211
Application layer
General Signaling Requirements
Connection layer
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.
Application layer
Connection layer
Default Packet Application: Radio Link Protocol
The Default Packet Application provides an octet stream that can be 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 - 213
Application layer
Connection layer
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 Nakbased retransmissions. Protocol Data Unit: The transmission unit of this protocol is an RLP packet. RLP is unaware of higher layer framing; it operates on a featureless 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 documents 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 - 214
Application layer
Connection layer
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 LocationValue parameter, 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.
Application layer
Connection layer
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 packet application.
1-2005
340 - 216
ALL IS-856 1xEV-DO Messages Page 1 of 4
1-2005
340 - 217
1-2005
340 - 218
1-2005
340 - 219
1-2005
340 - 220

1xEV DO Technology

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1xEV DO Technology

Uploaded by

Copyright:

Available Formats

Course 340

Global and US Wireless Snapshot 4Q 2003

USA 141,000,000 33,732,506 64,503,287 26,375,232 11,978,382 4,510,594

100% 23.9% 45.7% 18.6% 8.5% 3.2%

Global and US Wireless Users by Technology

Analog 3% TDMA 19%

A Quick Survey of Wireless Data Technologies

Other Misc. IS-136

The CDMA Migration Path to 3G

IS-95A/ IS-95B J-Std008

1250 kHz. 59 active users

None, Data Capabilities 2.4K by modem Features: Incremental Progress

2.4 Mb/s DL 1.0 Mb/s 153 Kb/s

First CDMA, Capacity, Quality

Improve d Access Smarter Handoffs

Faster data rates on shared 3-carrier bundle

High data rates on data-only CDMA carrier

High data rates on Data-Voice shared CDMA carrier

Course Series 340v3.2 (c)2005 Scott Baxter

Modulation Techniques of 1xEV Technologies

Course Series 340v3.2 (c)2005 Scott Baxter

GSM Technology Migration Path to 3G

200 kHz. 7.5 avg.

Features: Incremental Progress

Europes first Digital wireless

Course Series 340v3.2 (c)2005 Scott Baxter

TDMA IS-136 Technology Migration Path to 3G

the familiar GSM path!

30 kHz. 1 None, 2.4K by modem

30 kHz. 30 kHz. Many 3 users Pkt Usrs 19.2 kbps none

200 kHz. 7.5 avg.

First System, Features: Incremental Capacity & Progress Handoffs

US Packet Data Svc.

USAs first Digital wireless

Europes first Digital wireless

Course Series 340v3.2 (c)2005 Scott Baxter

4G: Broadband Wireless Access Technologies

Infrared IRDA Optical

Bluetooth 802.11b 2.4 GHz 2.4 GHz various GFSK FH 1 Mb/s

802.11a 5 GHz DSSS

HIPERLAN HIPERLAN Type 1 Type 2 5 GHz OFDM 5 GHz various.

802.16 2-11 GHz 10-66 GHz TDD, FDD various

Not BWA; for comparison only

Course Series 340v3.2 (c)2005 Scott Baxter

1G: AMPS 2G: TDMA, GSM,

2.5G: GPRS, EDGE 3G: IS2000 1xRTT,

4G: Wireless LAN

SPEED: 1xEV-DOs Purpose SPEED: 1xEV-DOs Purpose

Course Series 340v3.2 (c)2005 Scott Baxter

Course Series 340v3.2 (c)2005 Scott Baxter

Why Cant 1xRTT do high speeds?

Course Series 340v3.2 (c)2005 Scott Baxter

Mobile RF Channel Conditions Change Rapidly

Path Loss, db 0.2 0.3 Time, Seconds

Slow Fading due to obstructions and user motion

1xRTT Data Burst Control Lags RF Conditions

DATA RATE DECISION

DATA BURST ACTUALLY OCCURS NOW

Course Series 340v3.2 (c)2005 Scott Baxter

1xEV-DO vs. 1xRTT at the Same Time-Scale

Thoughput: 2.4 Mb/s max, 0.6 Mb/s typ.

Setup time can be less than 10 ms., depending on traffic loading.

T 0 0.1 0.2 Time, Seconds 0.3 0.4 0.5

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