RF 200

Course RF200
Wireless
Wireless CDMA
CDMA RF
RF
Performance
Performance Optimization
Optimization
August, 2007
RF200 v5.9 (c) 2007 Scott Baxter
RF200 - 1
Contents
Chapter
1. Introduction
2. Foundation Topics
Layer-3 Messaging
Call Processing
Performance Indicators and Problem Signatures
PN Planning and Search Windows
2. Analyzing System Performance
System Data and Analysis Techniques
3. Mobile Field Tools and Data Analysis
Autonomous Mobile Data Collection
Conventional Field Data Collection Tools
4. Multiple Carrier Systems: Operating Principles and Analysis
5. Applied Optimization
6. 1xRTT Optimization Issues
Appendix I. Cell Loading Example
Appendix II. CDMA/3g1x Books, Publications, Web Resources
August, 2007
RF200 - 2
Course RF200
Introduction
Introduction to
to Performance
Performance
Optimization
Optimization
August, 2007
RF200 - 3
Welcome to Course RF200

Q Course RF100 is an introduction to RF and CDMA principles. After
completing it, you should be familiar with:
General RF system design principles
CDMA technology - principles, channels, network basics
key fundamentals of Messaging and Call Processing
Q Course RF200 covers how to recognize and deal with system
performance problems
key performance indicators and what they mean
what tools are available for discovering and analyzing
problems
mechanisms and situations that cause trouble
how to solve many of the problems youll see
August, 2007
RF200 - 4
Good Performance is so Simple!!
BTS
BTS
FORWARD
LINK
August, 2007
BTS C
BTS B
BTS A
Ec/Io
BTS
Q One, Two, or Three good signals in handoff

Composite Ec/Io > -10 db
Q Enough capacity
No resource problems Ive got what I
need
-10
available
power
Traffic
Channels
In use
Paging
Sync
Pilot
RF200 - 5
Good Performance is so Simple!!
BTS
BTS
BTS C
BTS B
BTS A
Ec/Io
BTS
Q One, Two, or Three good signals in handoff

Composite Ec/Io > -10 db
Q Enough capacity
No resource problems Ive got what I
need
In principle, a COW next door can

solve almost any CDMA problem!
-10
Reality Check:
FORWARD
LINK
August, 2007
available
power
Traffic
Channels
In use
Paging
Sync
Pilot
1. But who has enough regular cells OR cows or money to

fix every problem location?!!
2. Problems occur in the areas between cells dominant
coverage. Adding a cow only pushes the problems
out to its own boundary with other cells.
Conclusion: We need to design better, and to use our
existing cells more effectively. We need to provide
one, two, or three dominant signals everywhere.
RF200 - 6
Bad Performance Has Many Causes

+41
+8
360
A
360+33c
BTS
B
BTS
BTS Sector Transmitter
No
Available
Power!
Traffic
Channels
In Use
Paging
Sync
Pilot
BTS Rx Pwr
Overload
CEs
Vocoders
Selectors
BTS A
PN 100
BTS B
PN 99
ACTIVE SEARCH WINDOW
1 mile
11 miles
August, 2007
Q Weak Signal / Coverage Hole

Q Pilot Pollution
Excessive Soft Handoff
Q Handoff Failures, Rogue mobiles
Missing Neighbors
Search Windows Too Small
BTS Resource Overload / No Resources
No Forward Power, Channel
Elements
No available Walsh Codes
No space in Packet Pipes
Q Pilot Surprise ambush; Slow Handoffs
Q PN Plan errors
Q Slow Data Problems: RF or IP congestion
Q Improper cell or reradiator configuration
Q Hardware and software failures
Q But on analysis, all of these problems bad
effects happen because the simple few-signal
ideal CDMA environment isnt possible.
RF200 - 7
What is Performance Optimization?

Q The words performance optimization mean different things to
different people, viewed from the perspective of their own jobs
Q System Performance Optimization includes many different smaller
processes at many points during a systems life
recognizing and resolving system-design-related issues (cant
build a crucial site, too much overlap/soft handoff, coverage
holes, etc.)
cluster testing and cell integration to ensure that new base
station hardware works and that call processing is normal
fine-tuning system parameters to wring out the best possible
call performance
identifying causes of specific problems and customer
complaints, and fixing them
carefully watching system traffic growth and the problems it
causes - implementing short-term fixes to ease hot spots, and
recognizing problems before they become critical
August, 2007
RF200 - 8
Performance Optimization Phases/Activities

Phase
Drivers/Objectives
Activities
Main Tools
Success Indicators
RF Design and
Cell Planning
Cover desired area;

have capacity for
anticipated traffic
Plan cells to effectively cover

as needed and divide traffic
load appropriately
Prop. Models,
Test Transmitters,
planning tools
Model results
New Cluster
Testing and
Cell Integration
Ensure cells properly

constructed and
configured to give
normal performance
Drive-test: coverage, all

handoff boundaries, all call
events and scenarios
Drive-test tools;
cell diagnostics and
hardware test
All handoffs occur;

all test cases
verified
Solve Specific
Performance
Problems
Identify problems
from complaints or
statistics; fix them!
Detect, Investigate, Resolve

performance problems
Drive-test tools,
system stats,
customer reports
Identified
problems are
resolved
Well-System
Performance
Management
Ensure present plant

is giving best possible
performance
Watch stats: Drops, Blocks,

Access Failures; identify/fix hot
spots
System statistics
Acceptable levels
and good trends
for all indicators
Capacity
Optimization
Manage congested
areas for most
effective performance
Watch capacity indicators;

identify problem areas, tune
parameters & configuration
Smart optimization
of parameters;
system statistics
Stats-Derived
indicators; carried
traffic levels
Traffic analysis and

trending tools;
prop. models for
cell spliiting; carrier
additions
Sectors are
expanded soon
after first signs of
congestion;
capital budget
remains within
comfortable
bounds
Growth
Management:
Optimizing both
Performance
and Capital
Effectiveness
Q hello
August, 2007
Overall traffic
increases and
congestion;
competition for capital
during tight times
Predict sector and area

exhaustion: plan and validate
effective growth plan, avoid
integration impact
RF200 - 9
Course RF200
CDMA2000
CDMA2000 Layer
Layer 33 Messages
Messages
August, 2007
RF200 - 10
Messages in CDMA
Q In CDMA, most call processing events are driven by messages
Q Some CDMA channels exist for the sole purpose of carrying
messages; they never carry users voice traffic
Sync Channel (a forward channel)
Paging Channel (a forward channel)
Access Channel (a reverse channel)
Forward or Reverse Dedicated Control Channels
On these channels, there are only messages, not voice or data
Q Some CDMA channels exist just to carry user traffic
Forward Fundamental and Supplemental Channels
Reverse Fundamental and Supplemental Channels
On these channels, most of the time is filled with traffic and
messages are sent only when there is something to do
Q All CDMA messages have very similar structure, regardless of the
channel on which they are sent
August, 2007
RF200 - 11
The Basic Format of CDMA Messages

Q CDMA messages on both forward
and reverse traffic channels are
normally sent via dim-and-burst
Q Messages include many fields of
binary data
Q The first byte of each message
identifies message type: this allows
the recipient to parse the contents
Q To ensure no messages are
missed, all CDMA messages bear
serial numbers and important
messages contain a bit requesting
acknowledgment
Q Messages not promptly
acknowledged are retransmitted
several times. If not acknowledged,
the sender may release the call
Q Field data processing tools capture
and display the messages for study
EXAMPLE:
A POWER MEASUREMENT
REPORT MESSAGE
MSG_TYPE (00000110)
ACK_SEQ
MSG_SEQ
ACK_REQ
ENCRYPTION
ERRORS_DETECTED
POWER_MEAS_FRAMES
10
LAST_HDM_SEQ
NUM_PILOTS
NUM_PILOTS occurrences of this field:

PILOT_STRENGTH
RESERVED (0s)
August, 2007
Length
(in bits)
Field
6
0-7
RF200 - 12
Message Vocabulary: Acquisition & Idle States

Pilot Channel
Sync Channel
No Messages
Sync Channel Msg
Paging Channel
Access Parameters Msg
General Page Msg
System Parameters Msg
Order Msg
BTS
Access Channel
Registration Msg
Order Msg
Mobile Station Acknowldgment
Long Code Transition Request
SSD Update Confirmation
many others..
CDMA Channel List Msg
Base Station Acknowledgment

Lock until Power-Cycled
Maintenance required
many others..
Extended System
Parameters Msg
Channel Assignment
Msg
Origination Msg
Extended Neighbor
List Msg
Feature Notification Msg
Page Response Msg
Global Service
Redirection Msg
Authentication
Challenge Msg
Authentication Challenge
Response Msg
Service Redirection Msg
Status Request Msg
Status Response Msg
SSD Update Msg
TMSI Assignment Msg
TMSI Assignment
Completion Message
Null Msg
Data Burst Msg
Data Burst Msg
August, 2007
RF200 - 13
Message Vocabulary: Conversation State

Forward Traffic Channel
Order Msg
Base Station Acknowledgment
Base Station Challenge
Confirmation
Message Encryption Mode
Alert With
Information Msg
Reverse Traffic Channel
Service Request Msg
Service Request Msg
Origination
Continuation Msg
Authentication
Challenge Msg
Service Response Msg
Service Response Msg
Authentication Challenge
Response Msg
TMSI Assignment Msg
Service Connect Msg
Service Connect
Completion Message
TMSI Assignment
Completion Message
Send Burst DTMF Msg
Service Option
Control Msg
Service Option Control

Message
Send Burst DTMF Msg
Set Parameters Msg
Status Request Msg
Status Response Msg
Parameters Response
Message
Power Control
Parameters Msg.
Flash With
Information Msg
Flash With
Information Msg
Power Measurement
Report Msg
Retrieve Parameters Msg
Data Burst Msg
Data Burst Message
Order Message
Analog Handoff
Direction Msg
Extended Handoff
Direction Msg
Pilot Strength
Measurement Msg
SSD Update Msg
Neighbor List
Update Msg
Handoff Completion Msg
Mobile Station
Registered Msg
In-Traffic System
Parameters Msg
August, 2007
Mobile Sta. Acknowledgment

Long Code Transition
Request
SSD Update Confirmation
Connect
RF200 - 14
Course RF200
CDMA
CDMA Call
Call Processing
Processing Basics
Basics
August, 2007
RF200 - 15
Troubleshooting Call Processing

Q CDMA call processing is complex!
Calls are a relationship between mobile and system
the events driven by messaging
the channels supported by RF transmission
Multiple codes and channels available for use
Multiple possible problems - physical, configuration, software
Multiple concurrent processes in the mobile and the system
Q Troubleshooting focuses on the desired call events
What is the desired sequence of events?
Compare the actual sequence of events.
Whats missing or wrong? Why did it happen?
Q Messaging is a major blow-by-blow troubleshooting tool
Q RF indications reveal the transmission risks and the channel
configurations
Bottom Line: To troubleshoot effectively, youve got to know call
processing steps and details AND the RF basis of the transmission
August, 2007
RF200 - 16
Course RF200
Let's
Let's Acquire
Acquire The
The System!
System!
August, 2007
RF200 - 17
System Acquisition Messaging

SYNC CHANNEL
SYNC CHANNEL MESSAGE
PAGING CHANNEL
SYSTEM PARAMETERS
MESSAGE
ACCESS PARAMETERS
MESSAGE
NEIGHBOR LIST
MESSAGE
EXTENDED SYSTEM
PARAMETERS MSG
CDMA CHANNEL LIST
MESSAGE
ACCESS CHANNEL
GLOBAL SERVICE
REDIRECTION MSG
REGISTRATION
MESSAGE
PROBE INFORMATION
August, 2007
RF200 - 18
Traffic Correlator
PN xxx Walsh xx
AGC
Duplexer
RF
Open Loop
RF
Transmitter
RF Section
August, 2007
Traffic Correlator
PN xxx Walsh xx
bits
Symbols
time-aligned
Receiver
RF Section
IF, Detector
control
Traffic Correlator
PN xxx Walsh xx
power
Chips
Digital
Rake Receiver
Symbols
Traffic Correlator
PN xxx Walsh xx
summing
Whats In a Handset? How does it work?
Viterbi Decoder,
Convl. Decoder,
Demultiplexer
Packets
Audio
Messages
Pilot Searcher
PN xxx Walsh 0
CPU
Vocoder
Transmit Gain Adjust

Transmitter
Digital Section
Audio
Messages
Long Code Gen.

RF200 - 19
The Task of Finding the Right System

Reverse Link Frequencies
(Mobile Transmit)
Forward Link Frequencies

(Base Station Transmit)
800 MHz. Cellular Spectrum

835
824 MHz.
845
849
870
825
Paging, ESMR, etc.
890
880
869
846.5
894
891.5
1900 MHz. PCS Spectrum

A
1850MHz.
E F
unlic. unlic.
data voice
1910MHz.
E F
1930MHz.
Mobile scans forward link frequencies:

(Cellular or PCS, depending on model)
History List (MRU)
Preferred Roaming List (PRL)
until a CDMA signal is found.
Use PRL to find best signal in area.
NO CDMA? Try AMPS. No AMPS? Standby
August, 2007
C
1990 MHz.
FREQUENCY LISTS:
HISTORY
LIST/MRU
Last-used:
Freq
Freq
Freq
Freq
Freq
etc.
PREFERRED
ROAMING
LIST/PRL
System1
System2
System3
System4
System5
etc.
RF200 - 20
The System Determination Algorithm

Q At turnon, Idle mobiles use proprietary System Determination Algorithms
(SDA) to find the initial CDMA carrier intended for them to use
Q The mobile finally acquires a CDMA signal and reads the Sync channel
Find the SID & NID in the PRL (Preferred Roaming List)
Check: is there a more-preferred system in the PRL? What Freq(s)?
Go look for the better system
Start
Preferred
Only Bit
MRU
PRL
Acq Idx
Yes
Go to last
Strongest
frequency
PN, read
from MRU
Sync
No Signal
Is SID
permitted?
Denied SID
Legend
August, 2007
No
Read
Paging
Channel
Last Resort:
GEO escape
Or Analog
Steps from
the CDMA
standards
Is better
SID
available?
Steps from
proprietary
SDAs
Proprietary
SDA
databases
Best System Found!
Begin Normal Paging Channel Operation
Typical Mobile
System Determination Algorithm
RF200 - 21
Ec/Io
1xRTT Acquisition On the Current Frequency:

Find Strongest Pilot, Read Sync Channel
All PN Offsets
1. Pilot Searcher Scans the Entire Range of PNs
-20
Chips 0
PN 0
32K
SYNC CHANNEL MESSAGE 512
2. Put Rake finger(s) on strongest

available PN, decode Walsh 32,
and read Sync Channel Message
Active Pilot
Handset
Rake Receiver
F1 PN168 W32
RF
LO
F2 PN168 W32
n Rake Fingers
o
p
F3 PN168 W32
Srch PN??? W0
August, 2007
Reference PN
001594, Time 16:33:58.838, Record

71913, QcpCdmaLogMsgSyncChan
MSG_LENGTH: 28 octets
MSG_TYPE: Sync Channel Message
P_REV: IS-2000 Revision 0
Is this the
MIN_P_REV: J-STD-008
right system
SID: 5216 NID: 0
to use?
PILOT_PN: 168
Check the
LC_STATE: 0x02 90 9D 0B 49 AC
PRL!
SYS_TIME: 01/25/2006 09:01:15
LP_SEC: 14
LTM_OFF: -600 minutes
DAYLT: No
PRAT: 9600 bps
CDMA_FREQ: 425
EXT_CDMA_FREQ: 425
SR1_BCCH_SUPPORTED: No
SR3_INCL: No DS_INCL: No
RESERVED: 0
RF200 - 22
Climbing the GEO Group

SYSTEM TABLE
August, 2007
ACQUISITION TABLE
NEG/
NID PREF
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
65535 Pref
GEO
NEW
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
NEW
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
SAME
a GEO GROUP
Q When traveling the first signal

found is usually not the best
one to use
Q When the SID and NID are
looked up in the PRL, they
are far down the list of
available choices
Q The starts at the top of the
GEO group and works down
to the first (most preferred)
system it can find
the Acquisition Table is
the list of frequencies
used by the various
systems, so the mobile
knows where to search
SID
4144
4812
205
208
208
342
342
478
1038
1050
1058
1375
1385
143
143
4103
4157
312
444
444
1008
1012
1014
1688
113
113
179
179
465
2119
2094
1005
1013
a GEO GROUP
Roaming List Type:

IS-683A
Preferred Only:
FALSE
Default Roaming Indicator:
0
Preferred List ID:
10018
INDEX
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
Climb!
ROAMING LIST
ACQ ROAM
PRI INDEX IND
SAME 13
1
MORE 21
1
SAME
4
0
MORE 37
0
SAME
4
0
MORE 37
0
SAME
4
0
SAME
4
0
SAME
4
0
SAME
4
0
SAME
4
0
SAME
4
0
MORE
4
0
MORE 37
0
MORE
4
0
SAME
3
1
MORE
2
1
SAME
4
0
MORE 37
0
SAME
4
0
SAME
4
0
SAME
4
0
SAME
4
0
MORE
4
0
MORE 37
0
SAME
4
0
MORE 37
0
SAME
4
0
SAME
4
0
MORE
4
0
MORE
4
0
SAME
4
0
SAME
4
0
INDEX ACQ TYPE

0
6
1
6
2
6
3
6
4
1
5
6
6
6
7
6
8
6
9
6
10
6
11
6
12
6
13
6
14
6
15
6
16
6
17
6
18
6
19
6
20
6
21
6
22
6
23
6
24
6
25
6
26
6
27
1
28
1
29
5
30
5
31
5
32
5
33
5
34
5
35
4
36
4
37
4
38
6
39
6
40
6
41
6
42
6
43
6
44
6
45
6
46
6
CH1
500
575
50
25
Both
450
675
250
550
75
200
425
500
500
650
25
425
200
825
350
750
325
1150
350
25
50
500
A
B
A
B
C
D
E
F
A
B
Both
350
25
675
850
650
450
325
150
1025
CH2
425
625
100
200
CH3
825
500
75
350
CH4
575
425
475
375
CH5 CH6 CH7 CH8 CH9

850 325 625
500
500
50
375
50
250
500
575
625
500
50
550
50
850
325
725
725
1175
875
1175
200
1075
350
600
175
425
175
175
575
475
350
675
375
225
175
925
375
775
350
575
575
650
475
625
250
50
25
25
50
25
350
725
375
325
675
375
75
250
750
250
325
825
25
850
375 1175
200 75 175 250
100 250 75
825
825
100
600
750
850 1175 775
825
725
850 175 250

50 475 175 250
650
775 575 725 425
425 50 575
175
775
675
25
1175 725 600 100
750
375
775 425 575 625
475
350 375 1025 1050 1075
475 625 675
1050 1075
PRL: Preferred Roaming List

Programmed into each phone by the system
operator; can be updated over the air.
RF200 - 23
Ec/Io
Found it! Now were on the Right System

All PN Offsets
1. Pilot Searcher Scans the Entire Range of PNs
-20
Chips 0
PN 0
32K
512
2. Put Rake finger(s) on strongest

available PN, decode Walsh 32,
and read Sync Channel Message
Active Pilot
Handset
Rake Fingers
Rake Receiver
F1 PN168 W32
RF
LO
F2 PN168 W32
n
o
p
F3 PN168 W32
Srch PN??? W0
August, 2007
Ref.
PN
98/05/24 23:14:09.817 [SCH]

MSG_LENGTH = 208 bits
MSG_TYPE = Sync Channel Message
P_REV = 3
If PRL shows:
MIN_P_REV = 2
SID = 179
This is the Best
NID = 0
Available System!
PILOT_PN = 168
Offset Index
LC_STATE = 0x0348D60E013
SYS_TIME = 98/05/24 23:14:10.160
LP_SEC = 12
LTM_OFF = -300 minutes
DAYLT = 0
PRAT = 9600 bps
RESERVED = 1
Go to the
Paging
Channel!
RF200 - 24
Course RF200
After
After finding
finding the
the right
right system:
system:
Normal
Normal Paging
Paging Channel
Channel Operation
Operation
August, 2007
RF200 - 25
The Configuration Messages

Q After reading the Sync Channel, the mobile is now capable of reading the
Paging Channel, which it now monitors constantly
Q Before it is allowed to transmit or operate on this system, the mobile must
collect a complete set of configuration messages
Q In IS-95, the configuration messages are sent on the Paging Channel,
repeated every 1.28 seconds
Q In CDMA2000 systems, the configuration messages may be sent on the
separate F-BCH channel
This would be indicated as SR1_BCCH_SUPPORTED = 1
Q There are six possible types of configuration messages; some are
optional; and they may happen in any order
Q The configuration messages contain sequence numbers so the mobile
can recognize if any of the messages have been freshly updated as it
continues to monitor the paging channel
Access parameters message sequence number
Configuration message sequence number
If a mobile notices a changed sequence number, or if 600 seconds
passes since the last time these messages were read, the mobile
reads all of them again
August, 2007
RF200 - 26
Ec/Io
Reading the Configuration Messages

All PN Offsets
-20
Chips 0
PN 0
Read the
Configuration Messages
Access Parameters Msg
Keep Rake finger(s) on strongest

available PN, monitor Walsh 1,
the Paging Channel
System Parameters Msg

CDMA Channel List Msg
Active Pilot
Handset
Rake Receiver
F1 PN168 W01
RF
x
LO
F2 PN168 W01
32K
512
Extended System
Parameters Msg (*opt.)
(Extended*) Neighbor
List Msg
n Rake Fingers
o
p
Global Service
Redirection Msg (*opt.)
F3 PN168 W01
Srch PN??? W0
Reference PN
August, 2007
Now were ready to operate!!
RF200 - 27
1xRTT Access Parameters Message

ACCESS PARAMETERS MESSAGE
01/18/2006 16:19:51
PD: P_REV_IN_USE < 6
MSG_TYPE: Access Parameters Message
PILOT_PN: 4
ACC_MSG_SEQ: 4
ACC_CHAN: 1 Access Channel(s)
NOM_PWR: 0 dB INIT_PWR: 0 dB
PWR_STEP: 4 dB
NUM_STEP: 5 Probe(s)
MAX_CAP_SZ: 10 ACH Frames
PAM_SZ: 4 ACH Frame(s)
PSIST(0-9): 0
PSIST(10): 0
PSIST(11): 0
PSIST(12): 0
PSIST(13): 0
PSIST(14): 0
PSIST(15): 0
MSG_PSIST: 1.00
REG_PSIST: 1.00
PROBE_PN_RAN: 127 PN chip(s)
ACC_TMO: 320 ms
PROBE_BKOFF: 1 Slot(s)
BKOFF: 1 Slot(s)
MAX_REQ_SEQ: 2
MAX_RSP_SEQ: 2
AUTH_MODE: 0
NOM_PWR_EXT: -8 to 7 dB inclusive
PSIST_EMG_INCL: No
RESERVED: 0
August, 2007
Basic Access Procedure

Any Access Msg
Success!
BTS
MS
Probing
an Access Probe
a Probe Sequence
an Access Attempt
Q The Access Parameters message

controls all the steps mobiles must
perform when they transmit on the
Access Channel
Q Mobiles perform a trial-and-error
process called Probing to get their
messages through
RF200 - 28
Phone Operation on the Access Channel

Successful Basic Access Attempt
Q A sectors Paging Channel announces 1
(typ) to 32 (max) Access Channels: PN
Long Code offsets for mobiles to use if
accessing the system.
For mobiles sending Registration,
Origination, Page Responses
Base Station always listening!
Q On the access channel, phones are not
yet under BTS closed-loop power control!
Q Phones access the BTS by probing at
power levels determined by receive power
and an open loop formula
If probe not acknowledged by BTS
within ACC_TMO (~400 mS.), phone
will wait a random time (~200 mS)
then probe again, stronger by PI db.
There can be 15 max. (typ. 5) probes
in a sequence and 15 max. (typ. 2)
sequences in an access attempt
most attempts succeed on first probe!
Q The Access Parameters message on the
paging channel announces values of all
related parameters
August, 2007
Origination Msg
ACCESS
Success!
BTS
MS
Probing
an Access Probe
a Probe Sequence
an Access Attempt
PAGING Base Sta. Acknlgmt. Order
FW TFC TFC frames of 000s
PAGING
Channel Assnmt. Msg.

TFC preamble of 000s RV TFC
FW FC
Base Sta. Acknlgmt. Order

Mobile Sta. Ackngmt. Order RV TFC
FW TFC
Service Connect Msg.

Svc. Connect Complete Msg RV TFC
FW TFC Base Sta. Acknlgmt. Order
Call is Established!
RF200 - 29
1xRTT System Parameters Message

SYSTEM PARAMETERS MESSAGE
000029, Time 15:28:37.607, Record 6330,
QcpCdmaLogMsgPagingChan
MSG_TYPE: System Parameters Message
PILOT_PN: 36
CONFIG_MSG_SEQ: 1
SID: 4379 NID: 15 REG_ZONE: 6
TOTAL_ZONES: 3 ZONE_TIMER: 1 min
MULT_SIDS: No MULT_NIDS: No BASE_ID: 2155
BASE_CLASS: Public PCS System
# Paging Channels, Slotted
PAGE_CHAN: 1 MAX_SLOT_CYCLE_INDEX: 1
HOME_REG: Yes FOR_SID_REG: Yes FOR_NID_REG: Yes
POWER_UP_REG: Yes POWER_DOWN_REG: Yes
Who Registers?
PARAMETER_REG: No
Why & When?
REG_PRD: 30.89 min
BASE_LAT: 37D18'35.00N
BASE_LONG: 079D15'19.00W
REG_DIST: 0 SRCH_WIN_A: 60 chips
Search Window
SRCH_WIN_N: 60 chips SRCH_WIN_R: 80 chips
Widths
NGHBR_MAX_AGE: 0
PWR_REP_THRESH: 2 Bad Frame(s)
PWR_REP_FRAMES: 113 frame(s)
PWR_THRESH_ENABLE: Yes
Handoff Thresholds
PWR_PERIOD_ENABLE: No
PWR_REP_DELAY: 4 frames
RESCAN: No T_ADD: -14.0 dB T_DROP: -16.0 dB
T_COMP: 4.0 T_TDROP: 4 sec
EXT_SYS_PARAMETER: Yes EXT_NGHBR_LIST: Yes
GEN_NGHBR_LIST: No GLOBAL_REDIRECT: Yes
PRI_NGHBR_LIST: No USER_ZONE_ID: No
What other optional
EXT_GLOBAL_REDIRECT: No
configuration messages
EXT_CHAN_LIST: Yes
RESERVED: 0
exist?
August, 2007
Mode period
RF200 - 30
Configuration Messages:
Extended System Parameters Message
01/18/2006 16:19:51
MSG_TYPE: Extended System Parameters Message
PILOT_PN: 4 CONFIG_MSG_SEQ: 25
DELETE_FOR_TMSI: No USE_TMSI: No
PREF_MSID_TYPE: IMSI and ESN
MCC: 1134 IMSI_11_12: 813
TMSI_ZONE_LEN: 1 octet TMSI_ZONE: 0
BCAST_INDEX: Disable Periodic Broadcast Paging
IMSI_T_SUPPORTED: No
P_REV: IS-2000 Revision 0 MIN_P_REV: J-STD-008
SOFT_SLOPE: 0 ADD_INTERCEPT: 0 dB
DROP_INTERCEPT: 0 dB
PACKET_ZONE_ID: 33 MAX_NUM_ALT_SO: 0
RESELECT_INCLUDED: No PILOT_REPORT: No
NGHBR_SET_ENTRY_INFO: No
NGHBR_SET_ACCESS_INFO: No
BROADCAST_GPS_ASST: No
QPCH_SUPPORTED: Yes
NUM_QPCH: 1 QPCH_RATE: 9600 bps
QPCH_POWER_LEVEL_PAGE: 3 dB below Pilot Channel Transmit Power
QPCH_CCI_SUPPORTED: Yes
QPCH_POWER_LEVEL_CONFIG: 3 dB below Pilot Channel Transmit Power
SDB_SUPPORTED: No
RLGAIN_TRAFFIC_PILOT: 0.000000 dB
REV_PWR_CNTL_DELAY_INCL: No
AUTO_MSG_SUPPORTED: No
August, 2007
Q The Extended System

Parameters Message tells
the mobile additional key
parameters:
Preferred Mobile
Station Identification
type (IMSI, ESN, both)
Dynamic Handoff
Thresholds, if used
Packet Zone
parameters, if used
Access handoff
parameters, if used
QPCH details, if used
RF200 - 31
Variations of the Neighbor List Message
04/03/2002 22:17:52
MSG_TYPE: Neighbor List Message
PILOT_PN: 44
CONFIG_MSG_SEQ: 47
PILOT_INC: 4
NGHBR_CONFIG: 0 NGHBR_PN: 216
RESERVED: 0
August, 2007
04/16/2003 19:08:07
MSG_TYPE: Extended Neighbor List Message
PILOT_PN: 213
CONFIG_MSG_SEQ: 10
PILOT_INC: 3
NGHBR_CONFIG: 0 NGHBR_PN: 45 SEARCH_PRIORITY: Very High FREQ_INCL: No
NGHBR_CONFIG: 0 NGHBR_PN: 381 SEARCH_PRIORITY: Very High FREQ_INCL: No
NGHBR_CONFIG: 0 NGHBR_PN: 300 SEARCH_PRIORITY: High FREQ_INCL: No
RESERVED: 0
RF200 - 32
More Variations of the Neighbor List Message
04/03/2002 22:43:16
MSG_LENGTH: 33 octets PD: P_REV_IN_USE < 6
MSG_TYPE: General Neighbor List Message
PILOT_PN: 380 CONFIG_MSG_SEQ: 8 PILOT_INC: 4
NGHBR_SRCH_MODE: Search Priorities
NGHBR_CONFIG_PN_INCL: Yes
FREQ_FIELDS_INCL: No USE_TIMING: No
NUM_NGHBR: 12
NGHBR_CONFIG: 0 NGHBR_PN: 212 SEARCH_PRIORITY: Very High
NGHBR_CONFIG: 0 NGHBR_PN: 40 SEARCH_PRIORITY: Very High
NGHBR_CONFIG: 0 NGHBR_PN: 504 SEARCH_PRIORITY: High
NGHBR_CONFIG: 0 NGHBR_PN: 260 SEARCH_PRIORITY: Medium
NGHBR_CONFIG: 0 NGHBR_PN: 184 SEARCH_PRIORITY: Medium
NUM_ANALOG_NGHBR: 0 SRCH_OFFSET_INCL: No
ADD_PILOT_REC_INCL: No, No, No, No, No, No, No, No, No, No, No, No
SRCH_OFFSET_NGHBR: 0 BCCH_IND_INCL: No
RESQ_ENABLED: No RESQ_DELAY_TIME: 0
RESQ_ALLOWED_TIME: 0 RESQ_ATTEMPT_TIME: 0
RESQ_CODE_CHAN: 0 RESQ_QOF: 0
RESQ_MIN_PERIOD_INCL: No RESQ_MIN_PERIOD: 0
RESQ_NUM_TOT_TRANS_INCL: 0 RESQ_NUM_TOT_TRANS_20MS: 0
RESQ_NUM_TOT_TRANS_5MS: 0 RESQ_NUM_PREAMBLE_RC1_RC2: 0
RESQ_NUM_PREAMBLE: 0 RESQ_POWER_DELTA: 0
NGHBR_RESQ_CONFIGURED: No, No, No, No, No, No, No, No, No, No, No, No
August, 2007
RF200 - 33
CDMA Channel List Message
04/03/2002 22:17:52
MSG_TYPE: CDMA Channel List Message
PILOT_PN: 44
CONFIG_MSG_SEQ: 47
CDMA_FREQ: 384
CDMA_FREQ: 425
RESERVED: 0
04/03/2002 22:17:52
MSG_TYPE: Extended CDMA Channel List Message
PILOT_PN: 44
CONFIG_MSG_SEQ: 47
NUM_FREQ: 1
CDMA_FREQ: 384
RC_QPCH_SEL_INCL: No
TD_SEL_INCL: No
RESERVED: 0
Q The CDMA Channel List message lists all carrier frequencies equipped on
the current sector for use by IS-95 mobiles
Q The Extended Channel List message lists all carrier frequencies equipped
on the current sector for use by 1xRTT mobiles
Q After receiving the appropriate message, a IS-95 or 1xRTT mobile
immediately uses the hashing formula to determine its appropriate
frequency from the list. The mobile immediately starts listening to the
paging channel on that carrier.
Q This set of messages provides a simple way to evenly distribute idle
mobiles among the available carriers for traffic balancing reasons
August, 2007
RF200 - 34
How Hashing Works

Q If a mobile sees a CDMA Channel List Message, it notices the list
of channels included in the message
There may be one, two, three, or more channels listed
Q Whenever a phone encounters multiple announced resources, it
uses its number (IMSI, International Mobile Subscriber Identity)
and a randomized process called hashing to determine which
resource it should use. This is how mobiles select:
Carrier Frequencies in idle mode
Preferred Paging Channel
Preferred Access Channel
Paging Time Slot in Slotted Mode
Q Optimization personnel may wish to carry a phone for each carrier
frequency, or use the multiple NAM capability of some handsets to
operate on different numbers so as to prefer different frequencies
August, 2007
RF200 - 35
Hashing Examples
Q Try your own phone in the spreadsheet Hashing.xls (in utilities folder)
Hashing Examples
Time between active slots, seconds:

1.28
2.56 5.12 10.24
20.48
Number of Slots in Mobile's Cycle:
16
32
64
128
256
v2. 1-28-2000
How Many
Key in red-shaded Frequencies?
values
2
40.96
81.92
163.84
512
1024
2048
How Many Paging

Channels?
Slot Cycle Index:
10 Digit IMSI
Use Freq. #
Use PCH #
0
Slot#
6153000124
6153000125
6153000126
6153000127
6153000128
6153000129
6153000130
6153000131
6153000132
6153000133
15
31
63
127
127
383
895
895
11
27
27
27
27
27
539
1563
69
69
69
69
69
67
195
451
451
1475
24
24
24
152
152
152
1176
25
25
25
25
25
25
25
11
27
27
27
27
27
539
1563
33
97
225
225
737
737
40
40
40
40
552
552
19
51
115
243
243
755
755
August, 2007
1
2
Slot# Slot#
3
Slot#
4
Slot#
5
Slot#
6
Slot#
7
Slot#
RF200 - 36
Global Service Redirection Message
01/05/2005 19:20:09
MSG_TYPE: Global Service Redirection Message
PILOT_PN: 6 CONFIG_MSG_SEQ: 35
REDIRECT_ACCOLC (ACCOLC_0): Yes
REDIRECT_ACCOLC (ACCOLC_10): No
RETURN_IF_FAIL: No DELETE_TMSI: No
EXCL_P_REV_MS: No
RECORD_TYPE: Redirection to An Analog System
RECORD_LEN: 3 octets
EXPECTED_SID: 0 IGNORE_CDMA: No
SYS_ORDERING: Attempt To Obtain Service On Either System
A Or System B. If Unsuccessful, Attempt Alternate System
MAX_REDIRECT_DELAY: 0 sec
August, 2007
Q The Global Service Redirection

Message (GSRM) sends mobiles
to a different channel or system
There are many configuration
options for the destination,
even including a return-if-fail
option if desired
The message only applies to
mobiles whose overload
classes (ACCOLC) are flagged
yes in the message
customer mobiles
ACCOLC are set equal to
the last digit of the mobile
number
RF200 - 37
Summary: How Idle Mobiles Choose CDMA Carriers

Q At turnon, Idle mobiles use proprietary System Determination Algorithms
(SDA) to find the initial CDMA carrier intended for them to use
Q On the paging channel of the idle mobiles newly-found home signal, the
mobile might be sent to a different frequency if it hears
CDMA Channel List Message
Global Service Redirection Message (GSRM)
Start
System Determination Algorithm

Preferred
Only Bit
MRU
PRL
Acq Idx
Yes
Go to last
Strongest
frequency
PN, read
from MRU
Sync
No Signal
Is SID
permitted?
Denied SID
Idle Mode Carrier Selection
CDMA Ch
List Message
HASH using
IMSI
Global Svc
Redir Msg
my ACCOLC?
redirect
F3
F2
F1
Config
Messages:
remain
to another CDMA frequency or system
Legend
August, 2007
No
Read
Paging
Channel
Last Resort:
GEO escape
Or Analog
Steps from
the CDMA
standards
Is better
SID
available?
Steps from
proprietary
SDAs
Proprietary
SDA
databases
to Analog
RF200 - 38
Idle Mode Handoff

(Reselection by the Mobile)
Q An idle mobile always uses the best available signal
In idle mode, it isnt possible to do soft handoff and listen to
multiple sectors or base stations at the same time -- the paging
channel information stream is different on each sector
Since a mobile cant combine sectors, the mobile can only try
to stay on top of the strongest one
Q The mobiles pilot searcher is constantly checking neighbor pilots
Q A Mobile might change pilots for either of two reasons:
It notices another pilot at least 3 db stronger than the current
active pilot, and it stays this good continuously for at least five
seconds: mobile switches at end of the next superframe
If the mobile loses the current paging channel, and another
pilot exists better than the old active sector, it is immediately
promoted to active
Q On the new paging channel, if the mobile notices a different SID,
NID, or other reason for registration, it re-registers
August, 2007
RF200 - 39
Ec/Io
Idle Mode on the Paging Channel:

Meet the Neighbors, track the Strongest Pilot
All PN Offsets
-20
SRCH_WIN_A
Chips 0
PN 0
Mobile Rake RX
F1 PN168 W01
Active Pilot
Rake Fingers
SRCH_WIN_N
Reference PN
n
o
p
32K
512
F2 PN168 W01
F3 PN168 W01
Srch PN??? W0
The phones pilot searcher constantly checks

the pilots listed in the Neighbor List Message
Neighbor Set
If the searcher ever notices a neighbor pilot 3 db stronger than

the current reference pilot, after 5 seconds the mobile makes it the new reference
pilot and the phone switches over to its paging channel on the next superframe.
This is called an idle mode handoff.
August, 2007
RF200 - 40
Improved Reliability for the Access Process

Q In original IS-95 CDMA, a when receiving or making a call a mobile chose
the strongest sector available. During all the following steps of call setup,
it was stuck on this sector -- even if another sector suddenly became
stronger and started interfering.
Q Beginning in IS-95B, and continuing in IS-2000, there are new tricks the
mobile and system can use in cooperation to allow the mobile to roll with
the punches and shift among sectors during the critical few moments
during call setup
Q ACCESS ENTRY HANDOFF
mobile can switch sectors after receiving a page but before sending its
first probe in response
Q ACCESS HANDOFF
mobile can switch sectors after successful access while waiting for
traffic channel assignment
Q Channel Assignment into Soft Handoff (Lucent CAMSHO)
the system can set up the mobiles initial traffic channel assignment
on multiple sectors, allowing the call to begin already in soft handoff
August, 2007
RF200 - 41
The Access Handoff List

Q ACCESS_HO_LIST is the key to all the techniques of handoff in
access mode
Q An idle mobile builds and constantly updates its own internal
ACCESS_HO_LIST, consisting only of:
neighbor pilots shown as access handoff enabled in the
neighbor list, only if stronger than T_Add
the current active pilot
Q The mobile sends its ACCESS_HO_LIST to the system
in any page response message
in any origination message
it can be included in other access channel messages if the
system requests it (system declares Pilot Reporting = 1)
August, 2007
RF200 - 42
Access Handoff, Access Entry Handoff

Q In this Origination Message,
a mobile is asking for Access
Handoff with two sectors:
its current Active sector
PN189
Q Access Attempted: NO
means it has not sent a
probe yet to PN189
Q If the current active fades
before the mobile hears a
response or during the
remainder of its probing, the
mobile will listen to the
paging channel on PN189
instead
Q If Channel Assignment into
Soft Handoff is enabled, an
Extended Channel
Assignment Message will
assign traffic channels on
both the current active PN
and PN189
August, 2007
QcpCdmaLogMsgAccessChan 04/16/2003 19:06:56

MSG_LENGTH: 42 octets D: P_REV_IN_USE >= 6
MSG_ID: Origination Message LAC_LENGTH: 13 octets
ACK_SEQ: 7 MSG_SEQ: 5 ACK_REQ: 1
VALID_ACK: 0 ACK_TYPE: 0
MSID_TYPE: IMSI and ESN MSID_LEN: 9 octets
ESN: D:06916245430 H:45F7E2B6
IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S included
RESERVED: 0 IMSI_S: 6015737284
AUTH_MODE: 0 LAC_PADDING: 0
ACTIVE_PILOT_STRENGTH: -9.00 dB
FIRST_IS_ACTIVE: Yes FIRST_IS_PTA: No NUM_ADD_PILOTS: 1
PILOT_PN_PHASE: PN:189 + 0 chips
PILOT_STRENGTH: -12.50 dB ACCESS_HO_EN: Yes
ACCESS_ATTEMPTED: No MOB_TERM: Yes
SLOT_CYCLE_INDEX: 5.12 MOB_P_REV: IS-2000 Revision 0
SCM: Band Class 1, Dual Mode, Slotted, Continuous, Class III
REQUEST_MODE: CDMA Only SPECIAL_SERVICE: Yes
SERVICE_OPTION: Standard: EVRC (8 kbps) PM: No
DIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: No
NUM_FIELDS: 10 CHARi: 6 6 2 3 2 8 9 0 3 9 NAR_AN_CAP: No
PACA_REORIG: User Directed Origination RETURN_CAUSE: Normal Access
MORE_RECORDS: No PACA_SUPPORTED: No
NUM_ALT_SO: 0 DRS: No UZID_INCL: No
CH_IND: Fundamental Channel SR_ID: 1
OTD_SUPPORTED: No QPCH_SUPPORTED: Yes
ENHANCED_RC: Yes FOR_RC_PREF: 3 REV_RC_PREF: 3
FCH_SUPPORTED: Yes FCH_FRAME_SIZE: Supports only 20 ms Frame Sizes
FOR_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: Yes RC6: No
REV_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: No RC6: No
DCCH_SUPPORTED: No GEO_LOC_INCL: No REV_FCH_GATING_REQ: Yes
RESERVED: 0
RF200 - 43
Course RF200
Lets
Lets Register!
Register!
August, 2007
RF200 - 44
Registration
Q Registration is the process by which an idle mobile lets the system
know its awake and available for incoming calls
this allows the system to inform the mobiles home switch of
the mobiles current location, so that incoming calls can be
delivered
registration also allows the system to intelligently page the
mobile only in the area where the mobile is currently located,
thereby eliminating useless congestion on the paging channels
in other areas of the system
Q There are many different conditions that could trigger an obligation
for the mobile to register
there are flags in the System Parameters Message which tell
the mobile when it must register on the current system
August, 2007
RF200 - 45
Mobile Registration Messaging

SYNC CHANNEL
PAGING CHANNEL
SYSTEM PARAMETERS
MESSAGE
ACCESS PARAMETERS
MESSAGE
NEIGHBOR LIST
MESSAGE
EXTENDED SYSTEM
PARAMETERS MSG
CDMA CHANNEL LIST
MESSAGE
ACCESS CHANNEL
GLOBAL SERVICE
REDIRECTION MSG
REGISTRATION
MESSAGE
PROBE INFORMATION
August, 2007
RF200 - 46
Mobile Registration
Q The Registration Message

is sent in the form of one
or more probes on the
Access Channel
Q Most test equipment used
for monitoring the layer-3
messages also displays
Access Probe Information,
confirming each individual
probe when it is
transmitted
The access probe
information is not sent
over the air, it is just a
report that the mobile
did in fact send a
probe
August, 2007
QcpCdmaLogMsgAccessChan
09/22/2004 14:03:08
MSG_ID: Registration Message
MSID_TYPE: IMSI and ESN
MSID_LEN: 9 octets
ESN: D:25411321874 H:FEACC212
AUTH_MODE: 0
REG_TYPE: Zone-Based
SLOT_CYCLE_INDEX: 2.56
MOB_P_REV: J-STD-008
EXT_SCM: Band Class 1 RESERVED: 0
SLOTTED_MODE: Yes RESERVED: 0
MOB_TERM: Yes RESERVED: 0
Access Probe Info 09/22/2004 14:03:08

Access Probe Sequence Number: 1 Access Probe Number: 1
Access Channel Number: 0 PN Randomization delay: 10
Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 1
Rx Power: -81.248 Tx Power (Est): 8.248 Tx Gain Adjust: 0
RF200 - 47
Feature
Feature Notification:
Notification:
You
You Have
Have Voicemail!
Voicemail!
August, 2007
RF200 - 48
Voicemail Notification Messaging

PAGING CHANNEL
ACCESS CHANNEL
FEATURE NOTIFICATION
MESSAGE (MSG WTG)
MOBILE STATION
ACK. ORDER
PROBE INFORMATION
August, 2007
RF200 - 49
Feature Notification
04/03/2002 22:44:05
MSG_TYPE: Feature Notification Message
ACK_SEQ: 2 MSG_SEQ: 7 ACK_REQ: Yes
VALID_ACK: Yes
ADDR_TYPE: IMSI
ADDR_LEN: 5 octets
RESERVED: 0
IMSI_S: 9145899573
RELEASE: No
RECORD_TYPE: Message Waiting
RECORD_LEN: 1 octet
MSG_COUNT: 1 RESERVED: 0
The mobile confirms it has received the

notification by sending a Mobile Station
Acknowledgment Order on the access
channel.
Test equipment connected to the mobile
may show the Access Probe Info,
confirming that a probe was actually sent.
August, 2007
The Feature Notification Message on

the Paging Channel tells a specific
mobile it has voice messages waiting.
There are other record types to notify
the mobile of other features.
QcpCdmaLogMsgRevTrafChan 04/03/2002 22:44:05

MSG_LENGTH: 7 octets MSG_TYPE: Order Message
ACK_SEQ: 7 MSG_SEQ: 4 ACK_REQ: No
ENCRYPTION: Encryption Disabled
ESN: D:11600081479 H:74013E47
ORDER: Mobile Station Acknowledgement Order
ADD_RECORD_LEN: 0 octet RESERVED: 0
Access Probe Info Time Stamp: 04/03/2002 22:44:05

Sequence Backoff: 0 Probe Backoff: 0
Persistence Tests Performed: 0
Rx Power: -70.9147 Tx Power (Est): -3.08533 Tx Gain Adjust: 2
RF200 - 50
Example 4
Lets
Lets Receive
Receive an
an Incoming
Incoming
Call!
Call!
August, 2007
RF200 - 51
Receiving an Incoming Call

Q All idle mobiles monitor the paging channel to receive incoming
calls.
Q When an incoming call appears, the paging channel notifies the
mobile in a General Page Message.
Q A mobile which has been paged sends a Page Response
Message on the access channel.
Q The system sets up a traffic channel for the call, then notifies the
mobile to use it with a Channel Assignment Message.
Q The mobile and the base station notice each others traffic channel
signals and confirm their presence by exchanging
acknowledgment messages.
Q The base station and the mobile negotiate what type of call this will
be -- I.e., 13k voice, etc.
Q The mobile is told to ring and given a calling line ID to display.
Q When the human user presses the send button, the audio path is
completed and the call proceeds.
August, 2007
RF200 - 52
Mobile Termination Messaging

PAGING CHANNEL
ACCESS CHANNEL
GENERAL PAGE
MESSAGE
PAGE RESPONSE MESSAGE

PROBE INFORMATION
BASE STATION
ACK. ORDER
CHANNEL ASSIGNMENT
MESSAGE
FORWARD TRAFFIC CHANNEL
REVERSE TRAFFIC CHANNEL
LAYER 2 HANDSHAKE
LAYER 2 HANDSHAKE
BASE STATION
ACK. ORDER
SERVICE CONNECT
MESSAGE
ALERT WITH INFORMATION
MESSAGE
BASE STATION
ACK. ORDER
August, 2007
MOBILE STATION
ACK. ORDER
SERVICE CONNECT
COMPLETE MESSAGE
MOBILE STATION
ACK ORDER
CONNECT
MESSAGE
RF200 - 53
Call Termination Messaging (1)

09/22/2004 13:33:56
MSG_TYPE: General Page Message

CONFIG_MSG_SEQ: 2
ACC_MSG_SEQ: 1
CLASS_0_DONE: Yes
CLASS_1_DONE: Yes
TMSI_DONE: No
ORDERED_TMSIS: No
BROADCAST_DONE: Yes
RESERVED: 0
ADD_LENGTH: 0 octets
PAGE_CLASS: Page With Class 0 IMSI
PAGE_SUBCLASS: 0
MSG_SEQ: 1
IMSI_S: 8436840009
SPECIAL_SERVICE: Yes
SERVICE_OPTION: QUALCOMM: Voice 13K

MSG_ID: Page Response Message
ACK_SEQ: 1 MSG_SEQ: 1 ACK_REQ: 1 VALID_ACK: 1 ACK_TYPE: 2
ESN: D:25411321874 H:FEACC212
IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0
IMSI_S: 8436840009
AUTH_MODE: 0 MOB_TERM: Yes
SLOT_CYCLE_INDEX: 2.56
MOB_P_REV: J-STD-008
REQUEST_MODE: Either Wide Analog or CDMA Only
PM: No NAR_AN_CAP: No RESERVED: 0
Access Probe Info Time Stamp: 9/22/2004 13:33:56.000

August, 2007
RF200 - 54

QcpCdmaLogMsgPagingChan 09/22/2004 13:33:57
MSG_TYPE: Order Message
VALID_ACK: Yes ADDR_TYPE: ESN ADDR_LEN: 4 octets
ESN: D:25411321874 H:FEACC212
ORDER: Base Station Acknowledgement Order
ADD_RECORD_LEN: 0 octets
QcpCdmaLogMsgPagingChan 09/22/2004 13:33:57

MSG_TYPE: Channel Assignment Message
VALID_ACK: Yes ADDR_TYPE: ESN ADDR_LEN: 4 octets
ESN: D:25411321874 H:FEACC212
ASSIGN_MODE: Extended Traffic Channel Assignment
ADD_RECORD_LEN: 5 octets FREQ_INCL: Yes RESERVED: 0
BYPASS_ALERT_ANSWER: No
DEFAULT_CONFIG: Multiplex Option 1
and Radio Config 1 For Both FTC and RTC
GRANTED_MODE: MS use Service Configuration of
default Multiplex Option and Transmission Rates
CODE_CHAN: 36 FRAME_OFFSET: 12.50 ms
ENCRYPT_MODE: Encryption Disabled
BAND_CLASS: 1.850 to 1.990 GHz Band
CDMA_FREQ: 1175 C_SIG_ENCRYPT_MODE_INCL: No
RESERVED: 0
August, 2007
Q The Base Station

Acknowledgment Order tells
the mobile to stop sending
probes
Q The Channel Assignment
Message tells the mobile the
walsh code and other details
of its traffic channel
RF200 - 55

The mobile sees at least two
good blank frames in a row on
the forward channel, and
concludes this is the right traffic
channel. It sends a preamble
of two blank frames of its own
on the reverse traffic channel.
The base station is already

sending blank frames on
the forward channel,using
the assigned Walsh code.
QcpCdmaLogMsgForTrafChan
09/22/2004 13:33:57
USE_TIME: No ACTION_TIME: 0 ms
ADD_RECORD_LEN: 0 octets RESERVED: 0
The base station acknowledges

receiving the mobiles preamble.
The mobile station acknowledges receiving the

Base Stations message. This is usually done
in a Mobile Station Acknowledgment Order,
but if the mobile has some other message it
needs to send, the acknowledgment can be
taken care of in the ACK_SEQ field in it.
August, 2007
QcpCdmaLogMsgRevTrafChan
09/22/2004 13:33:57
MSG_TYPE: Pilot Strength Measurement Message
REF_PN: 8 PILOT_STRENGTH: -9.00 dB KEEP: Yes
PILOT_STRENGTH: -8.00 dB KEEP: Yes
RESERVED: 0
RF200 - 56

09/22/2004 13:33:57
MSG_TYPE: Service Connect Message
SERV_CON_SEQ: 0 RESERVED: 0
RECORD_TYPE: Service Configuration
FOR_MUX_OPTION: 2 REV_MUX_OPTION: 2
RS2_14400_FOR: Supports 276 bits per F-FCH frame
RESERVED: 0
RS2_14400_REV: Supports 276 bits per R-FCH frame
RESERVED: 0 NUM_CON_REC: 1
RECORD_LEN: 5 octets CON_REF: 1
FOR_TRAFFIC: SO Uses Primary Traffic On FTC
REV_TRAFFIC: SO Uses Primary Traffic On RTC
Q The mobile can accept by

sending a Service Connect
Complete Message, or propose
something different with a
Service Response Message
August, 2007
Q The Service Connect Message

is the systems proposal to the
mobile specifying the technical
details of the call:
Radio Configuration
Multiplex options
Service Option, Vocoder
type
Traffic type to be carried
09/22/2004 13:33:57
MSG_TYPE: Service Connect Completion Message
RESERVED: 0 SERV_CON_SEQ: 0 RESERVED: 0
RF200 - 57

09/22/2004 13:33:57
MSG_TYPE: Alert With Information Message
RECORD_TYPE: Signal
SIGNAL_TYPE: IS-54B Alerting
ALERT_PITCH: Medium Pitch SIGNAL: Long
RESERVED: 0 RESERVED: 0
Q The Alert With Information

Message tells the mobile to
start ringing, and optionally to
display a calling-party number
on its screen
Q The mobile acknowledges the

Alert With Information Message,
indicating it is now ringing
August, 2007
09/22/2004 13:33:58
RF200 - 58

Q When the mobile user presses
SEND or opens their
mouthpiece, the phone sends a
Connect Order and the switch
connects the trunks for audio
09/22/2004 13:33:58
RESERVED: 0
09/22/2004 13:33:58
ORDER: Connect Order
RESERVED: 0
Now the switch completes the audio circuit and

the two callers can talk!
August, 2007
RF200 - 59
Course RF200
Lets
Lets Make
Make An
An Outgoing
Outgoing Call!
Call!
August, 2007
RF200 - 60
Placing an Outgoing Call

Q The mobile user dials the desired digits, and presses SEND.
Q Mobile transmits an Origination Message on the access channel.
Q The system acknowledges receiving the origination by sending a base
station acknowledgement on the paging channel.
Q The system arranges the resources for the call and starts transmitting on
the traffic channel.
Q The system notifies the mobile in a Channel Assignment Message on the
paging channel.
Q The mobile arrives on the traffic channel.
Q The mobile and the base station notice each others traffic channel signals
and confirm their presence by exchanging acknowledgment messages.
Q The base station and the mobile negotiate what type of call this will be -I.e., 13k voice, etc.
Q The audio circuit is completed and the mobile caller hears ringing.
Q Supplemental channels can be requested for data bursts as needed
August, 2007
RF200 - 61
Call Origination Messaging

PAGING CHANNEL
ACCESS CHANNEL
ORIGINATION MESSAGE
BASE STATION
ACK. ORDER
PROBE INFORMATION
CHANNEL ASSIGNMENT
MESSAGE
LAYER 2 HANDSHAKE
LAYER 2 HANDSHAKE
BASE STATION
ACK. ORDER
SERVICE CONNECT
MESSAGE
August, 2007
MOBILE STATION
ACK. ORDER
SERVICE CONNECT
COMPLETE MESSAGE
RF200 - 62
Call Origination Messaging (1)

Q An Origination
message contains all
details needed for
setup of a call
mobile identity
and technical
capabilities
destination
number and type
of call requested
Access Handoff
information, if
involved
Q Most message
capture test
equipment also
displays the mobiles
internally-generated
Access Probe Info,
showing technical
details of each probe
August, 2007

MSG_LENGTH: 43 octets PD: P_REV_IN_USE >= 6
MSID_TYPE: IMSI and ESN MSID_LEN: 9 octets ESN: D:11600081479 H:74013E47
AUTH_MODE: 1 AUTHU: 195061 RANDC: 122 COUNT: 0
LAC_PADDING: 0 ACTIVE_PILOT_STRENGTH: -4.00 dB
MOB_TERM: Yes SLOT_CYCLE_INDEX: 2.56 MOB_P_REV: IS-2000 Revision 0
SERVICE_OPTION: Standard: EVRC (8 kbps) PM: Yes DIGIT_MODE: 4-bit DTMF Codes
MORE_FIELDS: No NUM_FIELDS: 10 CHARi: 4 3 4 3 8 6 5 2 9 7
NAR_AN_CAP: No PACA_REORIG: User Directed Origination
RETURN_CAUSE: Normal Access MORE_RECORDS: No
ENCRYPTION_SUPPORTED: Basic Encryption Supported PACA_SUPPORTED: No
NUM_ALT_SO: 0 DRS: No UZID_INCL: No CH_IND: Fundamental Channel SR_ID: 1
OTD_SUPPORTED: No QPCH_SUPPORTED: Yes
ENHANCED_RC: Yes FOR_RC_PREF: 3 REV_RC_PREF: 3
FCH_SUPPORTED: Yes FCH_FRAME_SIZE: only 20 ms Frame Sizes
DCCH_SUPPORTED: No GEO_LOC_INCL: Yes
GEO_LOC_TYPE: Reserved REV_FCH_GATING_REQ: No
Access Probe Info 4/3/2002 22:43:16.000

RF200 - 63

04/03/2002 22:43:16
MSG_LENGTH: 13 octets PD: P_REV_IN_USE < 6 MSG_TYPE: Order Message
ACK_SEQ: 5 MSG_SEQ: 0 ACK_REQ: No VALID_ACK: Yes ADDR_TYPE: ESN
ADDR_LEN: 4 octets ESN: D:11600081479 H:74013E47
04/03/2002 22:43:16
MSG_TYPE: Extended Channel Assignment Message
ACK_SEQ: 5 MSG_SEQ: 1 ACK_REQ: No VALID_ACK: Yes
ADDR_TYPE: ESN ADDR_LEN: 4 octets ESN: D:11600081479 H:74013E47
RESERVED_1: 0 ADD_RECORD_LEN: 15 octets
ASSIGN_MODE: Enhanced Traffic Channel Assignment
RESERVED_2: 0 FREQ_INCL: Yes
BAND_CLASS: 800 MHz Cellular Band CDMA_FREQ: 384
GRANTED_MODE: MS use Service Configuration of default Multiplex Option and
Transmission Rates
DEFAULT_CONFIG: Reserved
FOR_RC: RC 3 REV_RC: RC 3 FRAME_OFFSET: 12.50 ms
FPC_SUBCHAN_GAIN: 0.0 dB RLGAIN_ADJ: 0 dB NUM_PILOTS: 0 Pilots
CH_IND: Fundamental Channel CH_RECORD_LEN: 7 octets
FPC_FCH_INIT_SETPT: 7.000 dB
FPC_FCH_FER: 0.5% - 10% (in units of 0.5%)
FPC_FCH_MIN_SETPT: 3.000 dB FPC_FCH_MAX_SETPT: 8.000 dB
PILOT_PN: 380 ADD_PILOT_REC_INCL: No PWR_COMB_IND: No
CODE_CHAN_FCH: 33 QOF_MASK_ID_FCH: 0 3X_FCH_INFO_INCL: No
REV_FCH_GATING_MODE: No 3XFL_1XRL_INCL: No RESERVED: 0
August, 2007
Q After receiving the

probe, the base station
transmits a Base Station
Acknowledgment order
on the Paging Channel
this tells the mobile
not to transmit more
probes
Q After the system sets up
the traffic channel for
the call, the Extended
Channel Assignment
Message gives the
mobile the channel
details
Operating mode
Band, Frequency
Walsh Code
Radio
Configurations
RF200 - 64

04/03/2002 22:43:17
ACK_SEQ: 7
MSG_SEQ: 0
ACK_REQ: Yes
USE_TIME: No
ACTION_TIME: 0 ms
The mobile station acknowledges the base

stations acknowledgment. This is usually by
a Mobile Station Acknowledgment order, but
in this case, it is tucked into a PSMM the
mobile needs to send.
August, 2007

channel. It sends a preamble
of two blank frames of its own
on the reverse traffic channel.
04/03/2002 22:43:17
ACK_SEQ: 0
MSG_SEQ: 0
ACK_REQ: Yes
REF_PN: 380
RESERVED: 0
RF200 - 65

QcpCdmaLogMsgForTrafChan 04/03/2002 22:43:17 MSG_LENGTH: 31 octets
MSG_TYPE: Service Connect Message
ENCRYPTION: Encryption Disabled USE_TIME: No ACTION_TIME: 0 ms
SERV_CON_SEQ: 0 RESERVED: 0 USE_OLD_SERV_CONFIG: 0 SYNC_ID_INCL: No
RECORD_TYPE: Service Configuration RECORD_LEN: 15 octets
FOR_MUX_OPTION: 1 REV_MUX_OPTION: 1
RESERVED: 0
RESERVED: 0 NUM_CON_REC: 1 RECORD_LEN: 6 octets CON_REF: 1
Q The Service Connect Message

is the systems proposal for the
technical details of the call
including service option,
multiplexing, and type of traffic
SERVICE_OPTION: Standard: EVRC (8 kbps)

FOR_TRAFFIC: SO Uses Primary Traffic On FTC REV_TRAFFIC: SO Uses Primary Traffic On RTC
UI_ENCRYPT_MODE: User Information Encryption Disabled SR_ID: 1
RLP_INFO_INCL: No QOS_PARMS_INCL: No RESERVED: -- FCH_CC_INCL: Yes
FCH_FRAME_SIZE: Supports only 20 ms Frame Sizes
FOR_FCH_RC: RC 3 REV_FCH_RC: RC 3
DCCH_CC_INCL: No FOR_SCH_CC_INCL: No REV_SCH_CC_INCL: No RESERVED: 0
RECORD_TYPE: Non-Negotiable Service Configuration
RECORD_LEN: 5 octets FPC_INCL: Yes FPC_PRI_CHAN: No FPC_MODE: 0
FPC_OLPC_FCH_INCL: Yes FPC_FCH_FER: 0.5% - 10% (in units of 0.5%)
FPC_OLPC_DCCH_INCL: No GATING_RATE_INCL: No FOR_SCH_INCL: No REV_SCH_INCL: No
LPM_IND: Use the default Logic-to-Physical Mapping NUM_REC: 0 USE_FLEX_NUM_BITS: No
USE_VAR_RATE: No LTU_INFO_INC: No USE_OLD_PARTITION_TABLE: No RESERVED: --
August, 2007
RF200 - 66
Q The Service Connect

Complete Message is the
mobiles confirmation that it
accepts the mode of
operation the system has
proposed
000036, Time 22:43:17.131, Record 264, QcpCdmaLogMsgRevTrafChan

1/32 Chip Counter: 49248
1.25 msec Counter: 04/03/2002 22:43:17
ACK_SEQ: 0
MSG_SEQ: 1
ACK_REQ: Yes
RESERVED: 0
SERV_CON_SEQ: 0
RESERVED: 0
The audio connection is now complete and the

user of this phone is listening to hear ringing
while waiting for the other party to answer.
August, 2007
RF200 - 67
Access Failures
Q In an access failure, the mobile never hears an acknowledgment of its
probes by the base station
Q From the mobile side, it is not possible to know absolutely whether the
problem is the reverse link (base station not hearing mobile) or the
forward link (the mobile not hearing the base stations acknowledgments)
general RF indications may help for example, if Ec/Io is poor, then
the forward link is stressed and may be the problem
if mobile transmit power is near maximum during the probes, then the
problem may be on the reverse link (high reverse power at the base
station receiver due to heavy traffic, a rogue mobile, or a foreign
interferer)
Q After the access failure, if the mobile reselects a different PN than it was
using during the probes, the newly discovered strong sector may have
been the interference source preventing reception earlier
check to see if Access Entry Handoff and Access Handoff can be
enabled to avoid this type of problem
August, 2007
RF200 - 68
Access Failure Messaging

ACCESS CHANNEL
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
ORIGINATION MESSAGE
PROBE INFORMATION
SYNC CHANNEL
August, 2007
RF200 - 69
Access Failure Messaging (1)

01:40:12.273 QcpCdmaLogMsgPagingChan
MSG_TYPE: Access Parameters Message
PILOT_PN: 4 ACC_MSG_SEQ: 0
ACC_CHAN: 1 Access Channel(s)
NOM_PWR: 0 dB
INIT_PWR: 0 dB
PWR_STEP: 3 dB
NUM_STEP: 4 Probe(s)
MAX_CAP_SZ: 5 ACH Frames
PAM_SZ: 4 ACH Frame(s)
PSIST(0-9): 0
PSIST(10): 0
PSIST(11): 0
PSIST(12): 0
PSIST(13): 0
PSIST(14): 0
PSIST(15): 0
MSG_PSIST: 1.00
REG_PSIST: 1.00
PROBE_PN_RAN: 0 PN chip(s)
ACC_TMO: 400 ms
PROBE_BKOFF: 1 Slot(s)
BKOFF: 2 Slot(s)
MAX_REQ_SEQ: 2
MAX_RSP_SEQ: 2
AUTH_MODE: 0
NOM_PWR_EXT: -8 to 7 dB inclusive
PSIST_EMG_INCL: No
RESERVED: 0
August, 2007
Q This is a sequence of
messages leading up to an
access failure
Q The mobile will follow the
access parameters given in
the message at left
up to 4 access probes per
probe sequence
up to 2 probe sequences
per access attempt
RF200 - 70

Q The mobile sends this origination
message, attempting to get
acknowledgment from the
system
Q Each time this message is sent,
we will see a Probe Information
report from the mobiles
processor confirming the time
that probe was sent, the power
level, and other details
August, 2007
01:40:12.455 QcpCdmaLogMsgAccessChan
MSG_ID: Origination Message
MSID_TYPE: IMSI and ESN
MSID_LEN: 9 octets
ESN: D:00113967208 H:01D51F68
AUTH_MODE: 0 MOB_TERM: Yes
SLOT_CYCLE_INDEX: 5.12 MOB_P_REV: J-STD-008
SERVICE_OPTION: QUALCOMM: Voice 13K PM: No
DIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: No
NUM_FIELDS: 10 CHARi: 5 0 2 2 0 7 0 2 9 9
NAR_AN_CAP: No RESERVED: 0
RF200 - 71

Q Here are the probe
reports for the first
probe sequence.
Q No acknowledgment
was received from the
system
Q Probing continues into
the second probe
sequence on the next
page
01:40:12.564 Access Probe Info

Rx Power: -63.248 Tx Power (Est): -12.752


Time Stamp: 8/8/2000 01:40:16.000 Access Probe Sequence Number: 1
Access Probe Number: 4 Access Channel Number: 0
PN Randomization delay: 0 Sequence Backoff: 0
Probe Backoff: 1 Persistence Tests Performed: 0
August, 2007
RF200 - 72

Q The mobile continues with
the second probe
sequence (4 probes),
completing all the probes
allowed by the Access
Parameters Message
it never hears an
acknowledgment from
the sector
Q The mobile access
attempt failed, so it
restarts the system
acquisition process

01:40:19.500 QcpCdmaLogMsgSyncChan
P_REV: J-STD-008 MIN_P_REV: J-STD-008
SID: 4139 NID: 41 PILOT_PN: 116
LC_STATE: 0x02 B9 77 D6 59 D0
SYS_TIME: 08/14/2000 00:31:49
LP_SEC: 13 LTM_OFF: -660 minutes
DAYLT: No PRAT: 4800 bps CDMA_FREQ: 50
August, 2007
RF200 - 73
Setup Failures
Q A setup failure is a failure to arrive successfully on a traffic
channel despite the base station hearing and acknowledging the
mobiles probes.
Q The problem can occur in any of the steps after the base station
acknowledgment:
the base station might not have resources for the call, causing
it to send a Reorder message (Call Failed, Network Busy)
the base station may have set up the resources for the call, but
the mobile cannot hear the channel assignment message due
to forward link problems
the mobile or the base station may fail to hear the other during
initialization of the traffic channel (this is called a Traffic
Channel Confirmation Failure TCCF in Lucent systems)
August, 2007
RF200 - 74
Setup Failure Messaging

PAGING CHANNEL
ACCESS CHANNEL
ORIGINATION MESSAGE
BASE STATION
ACK. ORDER
CHANNEL ASSIGNMENT
MESSAGE
PROBE INFORMATION
ANY OF THE STRIPED STEPS

MAY NOT OCCUR,
STOPPING THE SETUP PROCESS
LAYER 2 HANDSHAKE
LAYER 2 HANDSHAKE
BASE STATION
ACK. ORDER
August, 2007
MOBILE STATION
ACK. ORDER
RF200 - 75
Setup Failure Messaging (1)

MSG_ID: Origination Message
ESN: D:00113967208 H:01D51F68
IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0
IMSI_S: 9723333534 AUTH_MODE: 0 MOB_TERM: Yes
SLOT_CYCLE_INDEX: 5.12 MOB_P_REV: J-STD-008
EXT_SCM: Band Class 1 RESERVED: 0 SLOTTED_MODE: Yes
RESERVED: 0 REQUEST_MODE: CDMA Only SPECIAL_SERVICE: Yes
SERVICE_OPTION: QUALCOMM: Voice 13K PM: No
DIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: No NUM_FIELDS: 10
CHARi: 5 0 2 2 0 7 0 2 9 9 NAR_AN_CAP: No RESERVED: 0
VALID_ACK: Yes ADDR_TYPE: IMSI
ADDR_LEN: 7 octets IMSI_CLASS: 0
IMSI_CLASS_0_TYPE: IMSI_S, IMSI_11_12, and MCC
included RESERVED: 0
MCC: 310 IMSI_11_12: 00 IMSI_S: 9723333534
August, 2007
Q The mobiles first probe is

acknowledged, and the mobile now waits
for a traffic channel assignment.
Q If the mobile does not hear a channel
assignment message within 12 seconds,
it will abort.
RF200 - 76
Setup Failure Messaging

Q If the mobile never hears the channel assignment message, the
setup fails and the mobile reacquires the system.
MSG_TYPE: Channel Assignment Message
ADDR_TYPE: IMSI ADDR_LEN: 7 octets IMSI_CLASS: 0
IMSI_CLASS_0_TYPE: IMSI_S, IMSI_11_12, and MCC included
RESERVED: 0 MCC: 310 IMSI_11_12: 00 IMSI_S: 9723333534
ADD_RECORD_LEN: 5 octets FREQ_INCL: Yes RESERVED: 0
DEFAULT_CONFIG: Multiplex Option 1 and Radio Config 1 For
Both FTC and RTC
GRANTED_MODE: MS use Service Configuration of default
Multiplex Option and Transmission Rates
CODE_CHAN: 9 FRAME_OFFSET: 5.00 ms
BAND_CLASS: 1.850 to 1.990 GHz Band
CDMA_FREQ: 50 C_SIG_ENCRYPT_MODE_INCL: No
RESERVED: 0
X
or
X
August, 2007
Q If the mobile hears the channel

assignment message but if the
link fails to initialize in either
direction on the traffic channel,
the setup attempt will fail and
the mobile will attempt to
reacquire the system.
Q Steps in traffic channel
initialization:
Q Forward link layer 2 handshake
Q Reverse link layer 2 handshake
Q L3 base station ack. order
Q L3 mobile ack. order
Q Failure of any one is a TCCF
RF200 - 77
Dropped Calls
Q Normal calls end with an exchange of release messages by the
mobile and system
Whichever side wants to end the call sends an order message,
Release Normal. The other side sends an order message,
Release No Reason.
The mobile then immediately tries to reacquire the system, and
the Sync Channel Message is seen quickly during this process
Q When a call fails (drops), no Release Normal message is sent
by either side. Usually the first evidence of the drop will be the
Sync Channel Message during system re-acquisition after the
drop.
Q Layer-2 timers and counters supervise every call on both ends,
and abort the call when their limits are exceeded. A few are:
Forward Link Fade Timer (typically 5 seconds)
Reverse Link Fade Timer (typically 5 seconds)
various unacknowledged message counters
August, 2007
RF200 - 78
A Beautiful End to a Normal Call

MOBILE RELEASE ORDER
BASE STATION ACKNOWLEDGMENT

008090, Time 17:39:26.020, Record 167747,
ACK_SEQ: 1
MSG_SEQ: 5
ACK_REQ: No
USE_TIME: No
ACTION_TIME: 0 ms
ORDER: Release Order (No Reason Given)
RESERVED: 0
008091, Time 17:39:26.108, Record 167760,

ACK_SEQ: 4
MSG_SEQ: 1
ACK_REQ: No
ORDER: Release Order (Normal Release)
RESERVED: 0

008092, Time 17:39:26.514, Record 167820,
QcpCdmaLogMsgSyncChan
P_REV: IS-95B
MIN_P_REV: IS-95A
SID: 179
NID: 0
PILOT_PN: 468
LC_STATE: 0x02 87 7C F3 7F BA
SYS_TIME: 06/29/2002 06:15:19
LP_SEC: 13
LTM_OFF: -660 minutes
August, 2007
The mobile left the traffic channel,

scanned to find the best pilot, and read
the Sync Channel Message.
RF200 - 79
Dropped Call Messaging

ANY COMBINATION OF NORMAL MESSAGES

MAY OCCUR ON THE FORWARD AND
REVERSE TRAFFIC CHANNELS, BUT NO
RELEASE NORMAL IS SENT.
SYNC CHANNEL
August, 2007
RF200 - 80
Dropped Call Messaging

Q In a normal call end, there
will be a Release
Normal message from
one side and a Release
No Reason message from
the other.
Q In this example, there are
no release messages.
The mobile requests
adding PN196 to its
other 2 weak signals
The mobile reports
40% FER
Then the mobile drops,
and reacquires the
system on PN196.
13:37:13.600 QcpCdmaLogMsgRevTrafChan
ENCRYPTION: Encryption Disabled REF_PN: 284
RESERVED: 0
MSG_TYPE: Power Measurement Report Message
ERRORS_DETECTED: 2 PWR_MEAS_FRAMES: 5
LAST_HDM_SEQ: 3 NUM_PILOTS: 2
PILOT_STRENGTH: -18.50 dB
PILOT_STRENGTH: -18.00 dB
13:37:23.188 QcpCdmaLogMsgSyncChan
P_REV: Unknown (3) MIN_P_REV: IS-95A
SID: 22 NID: 0 PILOT_PN: 196
LC_STATE: 0x02 9E 9B E4 EE C4
SYS_TIME: 03/27/1998 06:01:32
LP_SEC: 8 LTM_OFF: -660 minutes
DAYLT: No PRAT: 9600 bps CDMA_FREQ: 777
August, 2007
RF200 - 81
Normal End of Call

W23
BTS
TRAFFIC
Voice
RELnorm
W1
PAGING KGKSAKKNKGGKSKPG
NSASPPCKGKSA
ACK SYS ChASN CHN XSYS NBR
W32
SYNC SSSSSSSSSSSSSSSSSSSSSSSSSSS
SYN SYN SYN SYN SYN SYN SYN SYN SYN
W0
SCAN Ref Time
PILOT
TIME
ACCESS CHANNEL
TRAFFIC CHANNEL
MOBILE REACQUIRES SYSTEM NORMALLY

Voice
RELnoRsn
Q When a call ends normally, it is because the caller on one side of the
conversation decided to hang up
Q The side ending the call sends a Release Normal order
Q The other side sends a Release No reason order
It may send an acknowledgment first, if it cannot give the release
order immediately
Q After the system receives a release order from the mobile, it releases the
resources it used for the call
Q After the mobile receives a release order from the base station, it stops
listening to the traffic channel and freshly reacquires the system
August, 2007
RF200 - 82
Abnormal End of Call Forward Link Failure

W23
BTS
TRAFFIC
Voice
5s timer
All bad frames
W1
NSASPPCKGKSA
ACK SYS ChASN CHN XSYS
W32
SYNC SSSSSSSSSSSSSSSSSSSSSSSSSSS
SYN SYN SYN SYN SYN SYN SYN SYN
W0
SCAN Ref Time
PILOT
TIME
ACCESS CHANNEL
TRAFFIC CHANNEL
MOBILE REACQUIRES SYSTEM, if available

Voice
Mute! No pc
5s timer
Q The mobile is always counting and tracking the bad frames it

receives on the forward link
Q Forward Link Fade Timer: If the mobile does not receive any good
frames during a 5-second period, it aborts the call
Q If a mobile receives 10 consecutive bad frames, it mutes its
transmitter until at least 2 consecutive good frames are heard
If the mobile stays muted 5 seconds, the BTS will release too
Q After a call ends for any reason, the mobile tries to reacquire the
system, making an independent cold start
August, 2007
RF200 - 83
Abnormal End of Call Reverse Link Failure

W23
BTS
TRAFFIC
RELnoRsn
Voice
W1
NSASPPCKGKSAAKSKPG
NSAS
ACK SYS ChASN CHN XSYS
W32
SYNC SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
SYN SYN SYN SYN SYN SYN SYN SYN
W0
SCAN Ref Time
PILOT
TIME
ACCESS CHANNEL
TRAFFIC CHANNEL
MOBILE REACQUIRES SYSTEM, if available

Voice
All bad frames

5s timer
Q The BTS is always counting and tracking the bad frames it

receives on the reverse link from the mobile
Q Reverse Link Fade Timer: If the BTS does not receive any good
frames during a 5-second period, it releases the call
Q After a call ends for any reason, the mobile tries to reacquire the
system, making an independent cold start
August, 2007
RF200 - 84
Example 8
Lets
Lets Do
Do A
A Soft
Soft Handoff!
Handoff!
August, 2007
RF200 - 85
Basic Rules of Soft Handoff
August, 2007
PILOT SETS
Active
6
Candidate 5
Neighbor 20
Remaining
Min. Members
Reqd. By Std.
Q The Handset considers pilots in sets

Active: pilots of sectors actually in use
Candidates: pilots mobile requested, but
not yet set up & transmitting by system
Neighbors: pilots told to mobile by system,
as nearby sectors to check
Remaining: any pilots used by system but
not already in the other sets (div. by PILOT_INC)
Q Handset sends Pilot Strength Measurement
Message to the system whenever:
It notices a pilot in neighbor or remaining set
exceeds T_ADD
An active set pilot drops below T_DROP for
T_TDROP time
A candidate pilot exceeds an active by
T_COMP
Q The System may set up all requested handoffs,
or it may apply special manufacturer-specific
screening criteria and only authorize some
HANDOFF
PARAMETERS
T_ADD
T_DROP
T_TDROP
T_COMP
Exercise: How does a pilot

in one set migrate into
another set, for all cases?
Identify the trigger, and the
messages involved.
RF200 - 86
Ec/Io
The Call is Already Established. What Next?

All PN Offsets
-20
Chips
10752
PN 0
14080
32002
168 220
Active Pilot
Mobile Rake RX
F1 PN168 W61
Rake Fingers
F2 PN168 W61
F3 PN168 W61
Srch PN??? W0
Reference PN
T_ADD
n
o
p
500 512
The call is already in progress.

PN 168 is the only active signal,
and also is our timing reference.
Continue checking the neighbors.
Neighbor Set
If we ever notice a neighbor with Ec/Io above T_ADD,

ask to use it! Send a Pilot Strength Measurement Message!
August, 2007
32K
RF200 - 87
Basic Soft/Softer Handoff

Q The fundamental and most common type of handoff in CDMA is
Soft Handoff directed by the mobile itself
The mobile constantly checks the strength of the pilots it sees
Whenever the mobile discovers a new pilot strong enough to
be useful, or notices a pilot its already using has faded to the
point of uselessness, it tells the system in a Pilot Strength
Measurement Message (PSMM)
Q The system normally makes the changes requested by a mobile
some systems have algorithms for intelligent screening of the
mobiles requests, and may not give everything requested
August, 2007
RF200 - 88
Soft Handoff Messaging

BASE STATION
ACK. ORDER
EXTENDED HANDOFF
DIRECTION MSG.
BASE STATION
ACK. ORDER
NEIGHBOR LIST
UPDATE MESSAGE.
August, 2007

PILOT STRENGTH
MEASUREMENT MSG.
MOBILE STATION
ACK. ORDER
HANDOFF COMPLETION
MESSAGE
MOBILE STATION
ACK. ORDER
RF200 - 89
Soft Handoff Messaging (1)

Q Soft Handoff begins with a
request the Pilot Strength
Measurement Message from
the mobile
04/03/2002 22:43:17
MSG_TYPE: General Handoff Direction Message
ENCRYPTION: Encryption Disabled USE_TIME: No
HDM_SEQ: 1 SEARCH_INCLUDED: Yes
SRCH_WIN_A: 40 chips
SRCH_WIN_N: 100 chips
SRCH_WIN_R: 4 chips
T_ADD: -14.0 dB T_DROP: -16.0 dB
SOFT_SLOPE: 0
ADD_INTERCEPT: 0 dB DROP_INTERCEPT: 0 dB
EXTRA_PARMS: No
SUP_CHAN_PARAMS_INCLUDED: No
USE_PWR_CNTL_STEP: No
NUM_PILOTS: 2 Pilots
PILOT_PN: 380 PWR_COMB_IND: No
FOR_FUND_CODE_CHAN: 33
PILOT_PN: 212 PWR_COMB_IND: Yes
FOR_FUND_CODE_CHAN: 56
FPC_SUBCHAN_GAIN: 0.0 dB
USE_PC_TIME: No REV_FCH_GATING_MODE: No
August, 2007
04/03/2002 22:43:17
RESERVED: 0
Q As soon as the system has set

up the requested changes, it
sends a Handoff Direction
Message (Enhanced HDM,
General HDM, etc.)
this gives the mobile the PN
offsets and walsh codes of all
sectors now active
RF200 - 90

Q The mobile acknowledges
receiving the Handoff Direction
Message
Q After double-checking that the
requested sectors are still
usable, the mobile accepts
them by sending a Handoff
Completion Message
August, 2007
04/03/2002 22:43:17
CON_REF_INCL: No RESERVED: 0
04/03/2002 22:43:17
MSG_TYPE: Handoff Completion Message
LAST_HDM_SEQ: 1 PILOT_PN: 380 PILOT_PN: 212
RESERVED: 0
RF200 - 91

04/03/2002 22:43:18
MSG_TYPE: Extended Neighbor List Update Message
PILOT_INC: 4
NGHBR_SRCH_MODE: Search Priorities
USE_TIMING: No NUM_NGHBR: 20
NGHBR_PN: 40 SEARCH_PRIORITY: Very High
NGHBR_PN: 32 SEARCH_PRIORITY: High
NGHBR_PN: 336 SEARCH_PRIORITY: Medium
SRCH_OFFSET_INCL: No
ADD_PILOT_REC_INCL: None RESERVED: 0
August, 2007
Q The system takes the pilots

accepted by the mobile in the
Handoff Completion Message
and builds a new combined list
of all their neighbors
Q The new blended neighbor list
is sent to the mobile in an
Extended Neighbor List Update
Message, which the mobile
acknowledges
Q The handoff is now in effect!
04/03/2002 22:43:18
CON_REF_INCL: No RESERVED: 0
RF200 - 92
Ec/Io
Handoff Now In Effect, but still check Pilots!

All PN Offsets
-20
Chips
10752
PN 0
14080
168 220
F1 PN168 W61
F3 PN220 W20
Rake Fingers
T_DROP
Srch PN??? W0
Reference PN
Neighbor Set
T_ADD
Continue checking each ACTIVE pilot. If any are less than T_DROP and remain
so for T_TDROP time, send Pilot Strength Measurement Message, DROP IT!!
Continue looking at each NEIGHBOR pilot. If any ever rises above T_ADD, send
Pilot Strength Measurement Message, ADD IT!
August, 2007
32K
500 512
Active Set
Mobile Rake RX
F2 PN500 W50
32002
RF200 - 93
Ec/Io
The Complete Picture of Handoff & Pilot Sets

All PN Offsets
-20
Chips 0
PN 0
Rake Fingers
SRCH_WIN_A
T_DROP
T_ADD
SRCH_WIN_A
Active Set
Pilots of sectors
now used for
communication
T_DROP
Reference PN
Candidate Set
SRCH_WIN_N
Pilots requested
by mobile but not
set up by system
32K
512
Mobile Rake RX
F1 PN168 W61
F2 PN500 W50
F3 PN220 W20
Srch PN??? W0
Neighbor Set
Pilots suggested
by system for
more checking
Remaining Set
All other pilots divisible by PILOT_INC but not

presently in Active, Candidate, or Neighbor sets
T_ADD
SRCH_WIN_R
August, 2007
RF200 - 94
Improved
Improved Soft
Soft Handoff
Handoff Control
Control
in
in 1xRTT
1xRTT
August, 2007
RF200 - 95
The IS-95 Situation

Q IS-95 handoff is driven by fixed thresholds
of pilot strength (Ec/Io)
Q If the mobile notices a new pilot stronger
than T_Add, it asks for it immediately
Q If an active pilot drops below T_Drop and
stays below for T_Tdrop seconds, the
mobile asks for permission to stop using it
Q The mobile has no discretion the T_Add
and T_Drop values apply no matter what
-5
-10
T_ADD
-15
T_DROP
Ec/Io THRESHOLDS, db
-20
August, 2007
RF200 - 96
Disadvantages of Standard Handoff Triggers
August, 2007
Pilot Strength
(Ec/Io, db)
-3
Active
All Six
sectors in
soft handoff!
Active
Active
Active
Active
Active
T_Add
-20
-3
Pilot Strength
(Ec/Io, db)
Q Mobile requests soft handoff with all

pilots above T_Add
This occasionally leads to some
rigid, less-than-optimum decisions!
Q Problem Situation 1
One dominant, strong signal and a
lot of weak ones:
Mobile asks for them all, but
only one is really needed!
Q Problem Situation 2
Heavy pilot pollution, many signals
lurk barely below the threshold
Mobile starts call on the best
one, but never asks for
handoffs with any others
mobile needs handoff to
survive! Four -16 signals are as
good as a single -10 signal!!
Only One
Sector in soft
handoff!
Active
T_Add
-20
RF200 - 97
1xRTT Allows Dynamic Handoff Thresholds

Q A handoff process more intelligent than fixed thresholds
Handoff events driven by smarter, situation-influenced triggers
Q Candidate Set Removal: if that sector isnt worth adding anymore
Q Neighbor-to-Active transition: only if its a worthwhile improvement
Q Removal from Active Set: if that sector isnt needed anymore
August, 2007
RF200 - 98
Standard Equation of a Line

y
b
x
Q The equation of a straight line

is pretty simple. It includes
y, the vertical-axis value
m, the slope of the line
the ratio of rise/run
x, the horizontal-axis value
b, the y intercept
the value of y where
the line crosses the y
axis
August, 2007
intercept
slope
y = mx + b
RF200 - 99
The Dynamic Handoff Threshold Line

+10
+5
COMBINED Ec/Io, db
-15
-10
-5
0
-5
Combined
Ec/Io
of Existing
Active Pilots
-10
-20
Add
Intercept
Drop
Intercept
T_Add
-15
T_Drop
-20
August, 2007
RF200 - 100
Weak-Signal, Pilot-Pollution Conditions

+10
+5
COMBINED Ec/Io, db
-15
-10
-5
0
-5
T_Add and T_Drop can be

greatly reduced to allow soft
handoff under pilot pollution
conditions
Combined
Ec/Io
of Existing
Active Pilots
-10
Drop
Intercept
-15
T_Add
-20
August, 2007
-20
Add
Intercept
T_Drop
RF200 - 101
Strong-Signal Conditions
+10
+5
COMBINED Ec/Io, db
-15
-10
-5
0
-5
Low T_Add and T_Drop will

not cause excessive soft
handoff when good signals
are available
Combined
Ec/Io
of Existing
Active Pilots
-10
Drop
Intercept
-15
T_Add
-20
August, 2007
-20
Add
Intercept
T_Drop
RF200 - 102
Section G
Deeper
Deeper Handoff
Handoff Details:
Details:
Search
Search Windows
Windows &
& Timing
Timing
August, 2007
RF200 - 103
The Pilot Searchers Measurement Process

CURRENT PILOT SET CONTENTS
3 A A A
1 C
12 N N N N N N N N N N N N
112 R R R R R R R R R R R R
R
The searcher checks pilots in nested

loops, much like meshed gears.
Actives and candidates
N
N
occupy the fastestspinning wheel.
N
A
Neighbors are
next, advancing
N
A A
one pilot for each
N
Act+Cand. revolution.
Remaining is slowest,
N
N
advancing one pilot each
time the Neighbors revolve.
R
R
NR
R
R
R
N
R
PILOT SEARCHER VIEWED IN SEQUENCE: Typical Elapsed Time = 4 seconds

A
August, 2007
Only 3 of 112 remaining set pilots

have been checked thus far!
RF200 - 104
Meet
Meet the
the CDMA
CDMA
Performance
Performance Indicators
Indicators
August, 2007
RF200 - 105
CDMA Performance Indicators

Q A Flight Data Recorder logs aircraft operational settings. Its CDMA
equivalent is a file of RF performance indicators captured by drive-test
equipment.
Q Key CDMA parameters and measurements show the condition of the RF
environment. They are the primary gauges used to guide CDMA
optimization and troubleshooting
some indicate uplink conditions, some downlink, and some, both.
these parameters are collected primarily at the subscriber end of the
link, and thus are easy to capture using readily available commercial
equipment without requiring assistance at the BSC
Q Understanding these parameters and their important implications requires
basic knowledge in several subject areas:
General: RF units, transmitter and receiver basics
CDMA and spread-spectrum signal characteristics
channel definitions
power control systems
basic CDMA call processing flow
signal behavior characteristics in noise and interference
August, 2007
RF200 - 106
Indicator #1: FER

Q FER Frame Erasure Rate
on forward channel
(realized at Handset)
on reverse channel
(realized at base station)
FER is an excellent call
quality summary statistic
Forw
R ev
ar d
er se
0 2 5
100
FER
%
Q FER is the end-result of the whole transmission link

if FER is good, then any other problems arent having much
effect
if FER is bad, thats not the problem - it is just the end-result of
the problem
we must investigate other indicators to get a clue what is
going on
August, 2007
RF200 - 107
I0
Handset Receiver
LNA
BW
~30
MHz.
x
LO
IF
Rake
R
-40
R
BW
1.25
S
MHz.
RX Level
(from AGC)
-90
-105
<<too weak
Q Mobile Receive Power

usually expressed in dBm
measured derived from
handset IF AGC voltage
broadband, unintelligent
measurement: includes all
RF in the carrier bandwidth
regardless of source, not
just RF from serving BTS
overload>>
Indicator #2: I0, Total Mobile Receive Power
Q Receive power is important, but its exact value isnt critical

too much received signal (-35 dbm or higher) could drive the
phones sensitive first amplifier into overload, causing intermod
and code distortion on received CDMA signals
too little received signal (-105 or weaker) would leave too much
noise in the signal after de-spreading, resulting in symbol errors,
bit errors, bad FER, and other problems
August, 2007
RF200 - 108
Indicator #3, EC/I0 - What does it mean?

Q Why cant we just use the handsets
received power level to guide
handoffs?
Because it is a simple total RF
power measurement, the total of
all sectors reaching the mobile
Handset Receiver
BW
~30
MHz.
LNA
x
LO
IF
Rake
R
R
BW
1.25
S
MHz.
RX Level
(from AGC)
Q We need a way to measure the signal strength of each sector

individually, and we must be able to measure it quickly and simply
Q The solution is to use each sectors pilot (Walsh 0) as a test signal
to guide handoffs
At the mobile, if the pilot of a certain sector is very strong and
clean, that means we also should be able to hear a traffic
channel on that sector, so handoff would be a good idea
if the pilot of a certain sector is weak, then we probably wont
be able to get much benefit from using a traffic channel on that
sector
August, 2007
RF200 - 109
How EC/I0 Varies with Traffic Loading
August, 2007
Ec/Io = (2/4)
= 50%
= -3 db.
Paging
Sync
Pilot
1.5w
0.5w
2w
EC
I0
Heavily Loaded
Ec/Io = (2/10)
= 20%
= -7 db.
Traffic Channels
Q Each sector transmits a certain

amount of power, the sum of:
pilot, sync, and paging
any traffic channels in use
at that moment
Q Ec/Io is the ratio of pilot power
to total power
On a sector with nobody
talking, Ec/Io is typically
about 50%, which is -3 db
On a sector with maximum
traffic, Ec/Io is typically
about 20%, which is -7 db.
Light Traffic Loading
Paging
Sync
Pilot
6w
I0
1.5w
0.5w
2w
EC
RF200 - 110
How EC/I0 varies with RF Environment

Traffic
Channels
Q In a clean situation, one

sector is dominant and the
mobile enjoys an Ec/Io just
as good as it was when
transmitted
Q In pilot pollution, too many
sectors overlap and the
mobile hears a soup made
up of all their signals
Io is the power sum of all
the signals reaching the
mobile
Ec is the energy of a
single sectors pilot
The large Io overrides the
weak Ec; Ec/Io is low!
One Sector Dominant

Io = -90 dbm
Ec = -96 dbm
Ec/Io = -6 db
Paging
Sync
Pilot
I0
1.5w
0.5w
2w
EC
Many Sectors, Nobody Dominant
Io = 10 signals
each -90 dbm
= -80 dbm
Ec of any one
sector = -96
Ec/Io = -16 db
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
Traffic
Sync & Paging
Pilot
August, 2007
4w
BTS10
BTS9
BTS8
BTS7
BTS6
BTS5
I0
BTS4
BTS3
BTS2
BTS1
EC
RF200 - 111
Indicator #4: Handset Transmitter Power

Q TXPO Handset Transmit Power
Actual RF power output of the
handset transmitter, including
combined effects of open
loop power control from
receiver AGC and closed
loop power control by BTS
cant exceed handsets
maximum (typ. +23 dBm)
Subscriber Handset
BTS
Receiver>>
LNA
DUP
TXPO
PA
LO
x
Rake
R
IF
LO
Viterbi
Decoder
Open Loop
Closed Loop Pwr Ctrl
IF
Long PN
x
IF Mod
x
x
Q
Orth
Mod
Vocoder
FEC
<<Transmitter
Typical TXPO:
TXPO = -(RXdbm) -C + TXGA
C = +73 for 800 MHz. systems
= +76 for 1900 MHz. systems
+23 dBm in a coverage hole

0 dBm near middle of cell
-50 dBm up close to BTS
Q What is the right power TX level? Whatever the BTS asks for!
As long as closed loop control is working, the phones opinion
isnt the last word. Just do what the BTS wants!!
However, if the BTS ever asks the phone to do the impossible,
something is wrong (lower than -60 dbm, higher than +23 dbm)
August, 2007
RF200 - 112
Indicator #5: Transmit Gain Adjust

Q What is Closed Loop Transmit Gain Adjust (TXGA)?
The power correction the base station is asking the mobile to
make right now, in real-time
At the beginning of a call, before the power control bits begin, it
is zero. Then the power control bits begin, 800 per second.
During a call, TXGA is the running total of all the power control
bits which have been received thus far.
Each power control bit asks for a 1 db correction, up or down
Each power control bit is based on the base stations latest new
decision: mobile is too strong, or mobile is too weak -- there is
no cumulative error, since each decision is fresh
0 dB
TXPO = -(RXdbm) -C + TXGA

C = +73 for 800 MHz. systems
= +76 for 1900 MHz. systems
Typical Transmit Gain Adjust
-10 dB
-20 dB
August, 2007
Time, Seconds
RF200 - 113
Closed Loop Power Control Dynamics

Q The figures at right show the
power control reactions to a
sudden change in path loss
Q The sudden change in path loss
causes a sudden change in
handset received signal
Q Both open loop and closed loop
control race to get the phone
back to the right new power and
succeed in about 10 milliseconds
Q Open loop continues to approach
the correct value better and better
on its own
Q 40 milliseconds later, no net
closed loop correction is needed.
August, 2007
RF200 - 114
Problem
Problem Signatures
Signatures
August, 2007
RF200 - 115
Signatures of Common Conditions

Q The key CDMA RF Performance
Indicators provide powerful clues
in cause-and-effect analysis for
understanding problem conditions
Q There are many common
conditions which are easy to
recognize from their characteristic
signatures -- unique
relationships among the key
indicators which are observed
when these conditions exist
Q We will use the simplified format
shown at right to display the key
indicators for each of several
interesting cases.
August, 2007
SIGNATURE:
GOOD CALL
FFER
I0
100%
EC/IO
TxGa
+23
+25
-30
TxPo
+10
-40
+10
-6
-10
0
-10
50%
-20
-30
-10
-15
FFER
BTS
-40
-90
10%
5%
2%
0%
-20
-100
I0
-25
-20
-110
EC/IO
-50
TxGa
TxPo
Messaging
RF200 - 116
Signature of a Successful Call
Q If the mobile station originates

successfully, remains in service
area, and makes normal release,
data will show:
SIGNATURE:
GOOD CALL
FFER
I0
100%
EC/IO
Transmit power < +20 dBm

Good Messaging
+10
August, 2007
+10
-6
-10
0
-10
50%
-20
-30
-10
-15
BTS
-40
-90
10%
5%
2%
0%
FFER
Parsed message files will

contain a full set of normal
messages.
+23
-40
Receive power > -100 dBm

Normal Transmit Gain Adjust
(actual value depends on site
configurations, loading &
NOM_PWR setting)
TxPo
+25
-30
Low forward FER

Good Ec/Io (> -12 dB)
TxGa
-20
-100
I0
-25
-20
-110
EC/IO
-50
TxGa
TxPo
Messaging
RF200 - 117
Signature of a Dropped Call in Poor Coverage

SIGNATURE:
Q If a mobile station is taken out
of the service area or into a
coverage hole, and only data
from the mobile station is
available, the log files will show
the following characteristics:
DROPPED CALL, BAD COVERAGE

FFER
I0
100%
EC/IO
TxGa
+23
+25
-30
TxPo
+10
-40
+10
-6
-10
High forward FER

Low receive power (<-100
dBm)
Low Ec/Io (< -10 dB)
Higher-than-normal Transmit
Gain Adjust (actual value depends
on site configurations, loading,
NOM_PWR setting)
Higher-than-normal transmit
power (> +20 dBm)
Poor messaging on both links
August, 2007
-10
50%
-20
-30
-10
-15
FFER
BTS
-40
-90
10%
5%
2%
0%
-20
-100
I0
-25
-20
-110
EC/IO
-50
TxGa
TxPo
Messaging
RF200 - 118
Signature of Forward Link Interference

Q Characteristics of data for a phone
experiencing forward link
interference from a source other
than the current BTS:
High forward FER

Good receive power (> -100 dBm)
Low Ec/Io (< -10 dB)
Higher-than-normal Transmit Gain
Adjust
Normal transmit power (< +20
dBm)
Poor forward link messaging
unreliable at best and may be
the actual cause of the drop.
SIGNATURE:
FORWARD LINK INTERFERENCE
FFER
EC/IO
TxGa
+23
+25
-30
TxPo
+10
-40
+10
-6
-10
0
-10
50%
-20
-30
-10
-15
FFER
-40
-90
10%
5%
2%
0%
BTS
August, 2007
I0
100%
-20
-100
I0
-25
-20
-110
EC/IO
-50
TxGa
TxPo
Messaging
RF200 - 119
A CDMA Drop Example: Forward Link Case

Q A mobile using Site A comes
down the highway and
suddenly begins to see the
signal of Site B
Q If the mobile begins soft
handoff with site B, everything
continues to go well
Q If the mobile cannot begin
handoff with B for any reason,
the call is doomed
site Bs signal will override
site As signal, making it
unreadable
as soon as the FER goes
too high, a fade timer will
start the the mobile will
eventually die
August, 2007
FORWARD LINK DIES

ns
o
i
t
uc
r
t
s
B
Ob
BTS
A
BTS
l
ve
a
Tr
B grows stronger and stronger.

Mobiles open-loop instinct is to transmit
weaker; closed-loop correction from A
goes higher and higher, maintaining the
mobile at the right power.
Finally B obscures A, which disappears
in an explosion of FER. The mobile
mutes since it cant hear power control
bits, and a fade timer or message timer
kills the call in a few seconds.
RF200 - 120
Signature of Reverse Link Interference

Q Characteristics of data for a phone
whose BTS has a raised noise
floor due to reverse link
interference
Good forward FER

Good receive power (> -100 dBm)
Good Ec/Io (> -10 dB)
Higher-than-normal Transmit Gain
Adjust
Higher-than-normal transmit power
(< +20 dBm)
Poor reverse link messaging
in the message files, youll
see repeats of messages on
the forward link and reverse
link
August, 2007
SIGNATURE:
REVERSE LINK INTERFERENCE
FFER
I0
100%
EC/IO
TxGa
+23
+25
-30
TxPo
+10
-40
+10
-6
-10
0
-10
50%
-20
-30
-10
-15
FFER
BTS
-40
-90
10%
5%
2%
0%
-20
-100
I0
-25
-20
-110
EC/IO
-50
TxGa
TxPo
Messaging
RF200 - 121
A CDMA Drop Example: Reverse Link Case

Q When a cell is penetrated by a
mobile not under its own
power control, bad things
happen!
The foreign mobile is being
power controlled by a
more distant cell, so it is
transmitting louder than
appropriate
the local mobiles must
power up in a deadly race
to keep up with the
interferor
local mobiles can still hear
the cell fine; the forward
link is just great, to the
very end
August, 2007
REVERSE LINK DIES

B
BTS
ns
o
i
t
uc
r
t
s
Ob
l
ve
a
Tr
It was a beautiful day in the neighborhood

for all the mobiles on site B until the grim
reaper arrived, transmitting at high power
to maintain its link with distant Cell A.
Cell B tried to power up each of its
individual mobiles so they would be
received as strong as the new interferor,
but mobiles more distant than the
interferor just couldnt keep up, and died.
Eventually the interferor died from
forward link interference, too.
If only the interferor had a soft handoff, all
of this violence could have been avoided.
RF200 - 122
Solving the #1 Death Scenario: Failed Handoff

What Went Wrong??!
Steps in the Handoff Process
see
Mobiles searcher notices

the needed new pilot
ask
Mobile sends PSMM

requesting handoff
System sets up the handoff:

channel elements
do
forward power
BTS space in packet pipes
Simulcasting begins!
Now the system can hear
the mobile better!
tell
System tells mobile how to

hear the new sectors:
BTS Handoff Direction Message
Now the mobile can hear
the system better, too!
ok!
tell
Mobile confirms completion:

System makes new neighbor list,
sends to mobile: Neighbor List
BTS Update Message
August, 2007
s
FORWARD LINK
on DIES A
i
t
BTS
ruc
B b st
l
BTS O
ve
a
Tr
s
REVERSE LINK DIES
on
i
t
uc
B bstr
BTS O
el
v
a
Tr
Q Why didnt the mobile ask for handoff?

New sector not on neighbor list
Neighbor Search Window too Small?
BTS in island mode, wrong PN?
Q Why didnt the BTS set up the handoff?
Old BTS didnt hear mobile rev link
interf?
No resources available on new BTS?
T-1 unstable, messages lost
Q Why didnt the mobile do the handoff?
Couldnt hear BTS, Fwd link interf?
RF200 - 123
Pilot Pollution
Q When a large number of
CDMA signals are received
at about the same strength,
they cause severe
interference to each other
this is called Pilot
Pollution
Q The cure for pilot pollution
is to eliminate unneeded
signals which really werent
intended to serve this
location anyway, and to
boost the one or a few
signals which were
intended to serve this
location
Q See the first page of the
workbook ECIOPLAY.XLS
August, 2007
Ec/Io value
at each
BTS TX
Io
-3
-80.0
Signal
Strength Ec/Io
-90
-13.0 1
-90
-13.0 2
-90
-13.0 3
-90
-13.0 4
-90
-13.0 5
-90
-13.0 6
-90
-13.0 7
-90
-13.0 8
-90
-13.0 9
-90
-13.0 10
-80.0 Sum Power
Ec/Io of Multiple CDMA Signals
Ec/Io value
at each
Io
BTS TX
-3
-73.9
Signal
Strength Ec/Io
-90
-19.1 1
-90
-19.1 2
-90
-19.1 3
-90
-19.1 4
-75
-4.1 5
-90
-19.1 6
-90
-19.1 7
-90
-19.1 8
-90
-19.1 9
-90
-19.1 10
-73.9 Sum Power
10
10
Ec/Io of Multiple CDMA Signals
RF200 - 124
Pilot Pollution/Handoff/Composite Ec/Io Demo

Q See the second page of the workbook ECIOPLAY.XLS
Ec/Io, Handoff, and Rake Finger Pilot Status
%Pilot
Power
10%
%
Overhead
Power
Nominal
Max
Power
W
20%
12
Sum
RF
Comp Max #
Power osite Lockable
Io
Ec/Io Rake Fingers
-86.2
-3.0
Max #
Pilots in
Soft
Handoff
Traffic
Trans Path
Signal
Loading mitted Loss,
Streng
%
Ec/Io dB
th
Ec/Io
0%
-3.0
120 -86.2
-3.0 Rake Locked Handoff
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
0%
-3.0
200 -166.2 -83.0
Relative Energies of Multiple CDMA Signals

Pilot Energy
T_ADD
6
Sync, Paging, Traf fic
-12
0.9
0.8
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
Interferor
1
2
3
4
5
6
7
8
9
10
11
12
13
14
0.7
0.6
0.5
0.4
0.3
0.2
0.1
0
1
Only grey-shaded fields can be changed. Other fields calculate automatically.

To unlock all cells, select TOOLS>PROTECTION>UNPROTECT SHEET.
August, 2007
10
11
12
13
14
I nd i vi d ual Sig nal s
RF200 - 125
System Performance Optimization
Basic
Basic PN
PN Planning
Planning and
and
Search
Search Window
Window Considerations
Considerations
August, 2007
RF200 - 126
Introduction to PN Planning and

Search Windows
Q In PN planning and setting Search Windows, several pitfalls must
be avoided. These slides explain most of the basic facts,
background, principles, and practical considerations involved.
August, 2007
RF200 - 127
Short PN Basics:
PN Offsets Distinguish Sectors
Phone
A
B
x
C
BPF
LNA
x
LO
BPF
IF
Rake Receiver
PN A Walsh X
PN B
Walsh Y
PN C
Walsh Z
Decoding
Vocoder
Pilot Searcher
D
Q Each sector uses the short PN code, but at a different timing delay called
its PN offset
PN delays are settable in 64-chip steps called "PN offsets"
For example, PN offset 100 means 6,400 chips of delay
PN short code is 32,768 chips long - room for 512 different PN offsets
Q In the rake finger of a mobile in soft handoff, the short PN code is
generated in step with just one sector the mobile is trying to hear
The rake finger hears the matching sector's signal, ignores all others
The rake finger next decodes the walsh code of the desired channel
from that sector, ignoring all other users on that sector
August, 2007
RF200 - 128
A Practical "Rule of Thumb" to Remember

Received:
Transmitted:
6,464 chips delay
6,400 chips offset
PN 101
PN 100
9.70 miles = 64 chips = 1 PN
ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890abcdefghijkmnopqrstuvwxyz!@#$%^&*()_+
The PN chips SEEN by the mobile are what the base station
transmitted 64 chips in the past! What the base station is really
doing now, its true PN offset, is 64 chips later than what the mobile
sees. So the base station's signal at the mobile seems to be one
PN lower than it was actually transmitted.
BTS
Mobile
Q The signal of a base station roughly 10 miles distant will SEEM to

be one PN higher than it was transmitted
August, 2007
RF200 - 129
Propagation Delay changes apparent PN Offset

Q Base stations transmit signals on assigned,
fixed short PN delays called PN Offsets
Q Transmitted signals encounter additional
delay traveling to the mobile
~6.7 chips/mile = ~4.1 chips/kilometer
Q These additional delays can become
significant and cause errors at the mobile!
Failure to recognize certain signals
Misidentification of signals, recognizing
on BTS as another
Improper combination of signals listening to the wrong BTS and trying to
decode and combine its signal in a
handoff
August, 2007
PN360
10 KM
41 chips
2 KM
8 chips
PN200
RF200 - 130
Mobile Timing: the Reference PN

How many chips????
Ec/Io
UNKNOWN EXTRA
PROPAGATION DELAY
All PN Offsets
Active Pilot
Pilot Searcher Scans All PNs
-20
Chips 0
PN 0
32K
n Rake Fingers
o
512
p SYNC CHANNEL MESSAGE
Mobile System Acquisition Process

98/05/24 23:14:09.817 [SCH]
Q Scan entire range of PNs
MSG_LENGTH = 208 bits
MSG_TYPE = Sync Channel Msg
Q Lock to strongest Pilot found
P_REV = 3, MIN_P_REV = 2
Reference
PN
SID = 179 NID = 0
Put rake fingers on multipaths
PILOT_PN = 168 Offset Index
LC_STATE = 0x0348D60E013
Earliest arriving multipath is "reference PN"
SYS_TIME = 98/05/24 3:14:10.160
LP_SEC = 12
Q Read sync channel message
LTM_OFF = -300 minutes
DAYLT = 0, PRAT = 9600 bps
Learn what PN this is!
Q But there's no way to know how many chips of propagation delay have
happened before this signal was received
The mobile is "blind" to whatever this error may be; so the mobile's
internal PN reference is late by an unknown amount
Every pilot the mobile looks for will appear to be early or late too!
August, 2007
RF200 - 131
What are "Search Windows"?

Q New pilots usually seem earlier or later
than their official PNs from the neighor list
Some have come from nearer, some
from farther, than the reference PN
Q A mobile must look for pilot energy through
a range of chips earlier and later than the
exact expected PN offset of the signal it is
trying to measure
Q These "tolerance" ranges are called
"Search Windows"
SRCH_WIN_A applies to active and
candidate pilots
SRCH_WIN_N applies to neighbors
SRCH_WIN_R applies to remaining
Q Search windows are chosen by RF
engineers and transmitted to the mobile in
messages from the BTS
August, 2007
PN360
10 KM
41 chips
+41
PN200
2 KM
8 chips
360
+8
360+33c
SRCH_WIN_N
RF200 - 132
What are the Available Search Window Values?

Q Search windows can't be set to the exact number
of chips desired; each window can be set to a
value from the list at right
Q Remember the widths are total and apply with the
mobile's reference at the center.
For example, SRCH_WIN_N = 10 means
when the mobile is checking for neighbor
pilots, it will search a range 100 chips wide,
centered on what it thinks is the reference PN.
The mobile will search from 50 chips
earlier to 50 chips later than the exact PN
it expects to find
Q Search windows should be wide enough to include
needed signals, but not unnecessarily wide
Grossly over-wide search windows will slow
down the mobiles' overall pilot searching
speed
August, 2007
SRCH_WIN_val Width, Chips

0
4 (2)
6 (3)
8 (4)
10 (5)
14 (7)
20 (10)
28 (14)
40 (20)
60 (30)
80 (40)
10
100 (50)
11
130 (65)
12
160 (80)
13
226 (113)
14
330 (165)
15
452 (226)
RF200 - 133
Search Window Settings: Neighbor Set

Neighbor Search Window
Example
Q The neighbor search window must be set

wide enough to include the energy of any
needed neighbor pilot
Q The mobile at right is using PN200 as its
reference (and only active) pilot
Q To the mobile, the pilot of neighbor sector
PN360 seems 33 chips late
Q SRCH_WIN_N must be set to at least 2 x
33 = 66 chips wide so the PN360 pilot can
be noticed by the mobile
Q The closest search window setting above
66 chips is SRCH_WIN_N = 9, which is 80
chips wide
PN360
Neighbor
Sector
10 KM
41 chips
+41
PN200
2 KM
8 chips
Active
Sector
August, 2007
360
+8
360+33c
SRCH_WIN_N
RF200 - 134
Worst-Case Wide Neighbor Window Situation

BTS A
BTS B
1/2
mile
12 miles
Q In some terrain, it is possible for a mobile to be very close to one BTS

and far from another BTS, yet need them both in soft handoff
Q This occurs when local terrain or buildings obstruct the signal of the near
BTS, making it much weaker than normal
The far BTS may have much more favorable conditions, such as an
over-water path
The signals of the two BTSs may seem equally strong!
Q Almost the entire distance between the BTSs appears as timing skew
If near BTS is reference PN, distant BTS is late this number of chips
If far BTS is reference PN, near BTS is late by this number of chips
August, 2007
RF200 - 135
Safe Initial Neighbor Search Window Value

Determining Safe
Q Examine a cell map for an area of your system
Initial SRCH_WIN_N
Q Identify the farthest-apart pair of cells likely to
be used in soft handoff
F
D
Their distance separation determines
maximum timing skew a mobile could ever
E
possibly encounter in this part of the
B
system
11.5 KM
Q Calculate the timing skew in chips
C
A
6.7 chips times miles or 4.1 chips times
kilometers
Required Window
Safe required window size = two times the
= 4.1 x 11.5 x 2 = 94.3 chips
skew
SRCH_WIN_N = 10
Q Refer to table to convert required window size If locations
exist near site A
in chips to required value of SRCH_WIN_N
where mobiles are in handoff with
site F, mobiles could encounter
Q After thorough drive-test data is available, it
neighbor pilot timing skews as
may be possible to reduce SRCH_WIN_N if
large as the A-F distance. If
locked to A, F looks late by this
observed delay spread is significantly
amount. If locked to F, A looks
narrower than the window
early by this amount. Window
must be twice the skew value.
August, 2007
RF200 - 136
Search Window Settings: Remaining Set

Q Remaining set search window size is
determined by maximum possible timing
skew in the same way as for neighbor set
window
Q Recommended SRCH_WIN_R is one or two
steps greater than SRCH_WIN_N
Q Remaining set pilots can be requested by the
mobile in a PSMM but the system cannot
assign traffic channels since it uses the
Neighbor Pilot Database as its crossreference for identification of their base
stations
Q There is still value in allowing mobiles to find
and request remaining pilots, since the
requests help system RF engineers identify
missing pilots that should be added to the
neighbor lists of various sectors
August, 2007
F
E
11.5 KM
A
RF200 - 137
Search Window Initial Settings: Active Set
August, 2007
Active Search Window

40 chips wide (typical)
-20
+20
Ec/Io
Q Neighbor and Remaining search window

centers are indexed against the mobiles
Reference PN
Q Each active search window is different a
floating window centered over the earliest
observed multipath energy during the previous
mobile searcher scan of that individual pilot
Q Active search windows need not accommodate
distance-based timing skews they float
centered on their respective pilots!
Q The only timing variations they must
accommodate are multipath delay spreads
Q Multipath delay spreads are determined by
terrain and clutter-driven scattering and
reflection of the signal
Q Measurements are better than predictions to
set SRCH_WIN_A
Earliest Detected
Multipath
The earliest arriving multipath
seen by the mobile during this
searcher sweep will be used
as the center of this active
window on the next searcher
sweep! This makes each
active search window "track"
individually with its pilot.
RF200 - 138
SRCH_WIN_A Settings from Measurements
Q
Q
Q
Q
Typical active set delay spread from actual drive-tests

Notice the narrow distribution of energy!
28-chip width, SRCH_WIN_A = 6, is enough for this case
Drive-test your own system to determine your own value of spread
It is determined by the signal-scattering characteristics of your terrain
August, 2007
RF200 - 139
SRCH_WIN_A Special Consideration
SRCH_WIN_N, Chips
Q Active set delay spread is very narrow

can the active search window be set
narrow too?
Q Mobile reference timing occasionally
jumps due to false early-window
detection of the reference pilot
20
28
40
60
80
100
130
160
226
SRCH_WIN_A, Chips
10 14 20 28 40 60
No No No No No No
No No No No No No
No No No No Yes No
No No No Yes Yes Yes
No No No Yes Yes Yes
No Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes Yes
Q There is a dynamic relationship between mobile reference timing

stability and the active and neighbor search window sizes
Q The chart above shows which combinations of SRCH_WIN_A
and SRCH_WIN_N are safe and stable for all mobiles
August, 2007
RF200 - 140
The Potential for PN Problems and Conflicts

Q After seeing the skewing effects of propagation, it is easy to
anticipate problems of PN confusion and misidentification!
There are many different kinds of possible PN problems:
Q Two same-PN base stations with areas of coverage overlap
Mobiles can't distinguish them, experience horrible FER
Q Combining unintended signals into the handoff mix being heard
The new signals cause interference instead of helping
Q Mistaken identity of signals when requesting handoff
The wrong base station is added, the mobile can't hear it
Q Running out of available PNs due to bad parameter choices
Fortunately, these problems can be avoided by careful planning!
August, 2007
RF200 - 141
Co-Active PN Demodulation Errors

BTS A
PN 142
BTS B
PN 142
x miles
x miles
Q Mobile is midway between two BTSs with the same PN, in a call on BTS A
Q PN energy of BTS A and B is indistinguishable in active search window
Q Rake fingers may be assigned to both A and B energy
If the walsh code used on A also happens to be in use by someone on
BTS B, demodulation of B will cause severe FER
The mobile audio will frequently clip and mute, and the call may drop
All the while, the phone will see very good Ec/Io since both A and B
are recognized as good energy!
Q Solution: Two different BTS covering the same area should never have
the same PN offset. Change the PN offset for one of the sectors involved.
August, 2007
RF200 - 142
Adjacent-Active-PN Demodulation Errors

BTS A
PN 100
BTS B
PN 99
1 mile
11 miles
Q Mobile is in a call on BTS A from 1 mile away; A is the reference PN

Q The signal from BTS B on PN 99 travels 11 miles to the mobile and is
approximately as strong as BTS A due to terrain effects
Q Due to propagation delay, the signal of B is skewed and falls inside the
active search window of the mobile for A
A and B energy are indistinguishable to the mobile
Rake fingers may be assigned to both A and B multipaths
If the walsh code used by the mobile on A also is in use by someone
else on B, the mobile may demodulate their symbols and combine
them with its own symbols from BTS A
This would cause severe FER and possibly a dropped call
Q Solution: The PNs of the two BTSs are too close together. Use a different
PN offset for BTS B.
August, 2007
RF200 - 143
PILOT_INC Helps Avoid PN Problems

Q Imagine a network with base stations spaced
approximately 10 miles apart - this is 1 PN offset!
Q Recall if we use adjacent PNs for adjacent base
stations, there will be locations where their PNs are
close together or even indistinguishable
Q It would be smart to assign PNs farther apart!
Q If properly set, PILOT_INC can prevent this problem
Only PNs divisible by PILOT_INC are allowed to
be assigned to sectors
Q PILOT_INC can be chosen from 1 to 16
If too small, interfering PNs can be assigned
If too large, the pool of available PNs is small
Q PILOT_INC is set based on the density of cells
3 or 4 in typical cities with suburban density
2 in dense urban environments
6 or 8 in very rural areas
August, 2007
RF200 - 144
Adjacent-Neighbor PN Recognition Errors

BTS A
PN 100
20 miles
BTS
BTS G
PN 198
BTS
NEIGHBOR SEARCH WINDOW
mo
un
tai
ns
BTS F
PN 200
BTS
Q Mobile is in a call on BTS A, PN 100

Q Mobile checks neighbor PN 200 to see if handoff needed with BTS F
Q Energy from distant BTS G on PN 198 is skewed so that it falls in the
neighbor search window for PN 200; mobile asks for handoff with F
Q The system sets up a traffic channel on BTS F - but mobile hears G!
Q If the walsh code assigned on F happens also to be in use on G, the mobile
may put a rake finger on it and include it in the mix
Severe FER and a possible dropped call will result!
Q Solution: Careful RF design to avoid such "pockets" of distant coverage
If signal of G can't be reduced by RF methods, assign it to a different PN
August, 2007
RF200 - 145
Sector PN Assignments:
Consecutive Assignment
Q Use only PNs divisible by PILOT_INC.
PILOT_INC is chosen large enough to
prevent aliasing of pilots in adjacent cells
Q Assign PNs in sequence to the sectors of all
the base stations
Q Common Usage: This is the typical default
method used in Nortel and Motorola CDMA
networks
Q Advantage
Simple assignment
When adjacent PNs are observed in the
field, they are known to be from sister
sectors of the same BTS or from nearby
BTSs
August, 2007
12
96
88
24
92
20
84
108
100
76
80
36
104
112
116
28
32
72
120
16
64
68
48
40
44
60
52
56
RF200 - 146
Sector PN Assignments:
Segment Assignment
Q Assign only PNs divisible by PILOT_INC
PILOT_INC is chosen to avoid aliasing
Q Different ranges of PN values are reserved
First 1/3 of PN offsets for alpha sectors
Second 1/3 of PN offsets for beta sectors
Third 1/3 of PN offsets for gamma sectors
Q Although 512/3 = 170.666, the value 168 is
usually used for the inter-sector PN increment
Q Common Usage: default in Lucent networks
Q Advantage: In the field, interference is
suddenly noticed from PN 468. Quickly, what
is the source of it?
Definitely some cells gamma sector!
August, 2007
340
368
32
172
344
200
176
364
372
36
28
196
348
204
40
208
12
180
360
376
24
192
352
16
184
356
20
188
RF200 - 147
PN Reuse Explorations
August, 2007
RF200 - 148
PN Reuse Symmetrical N=37 Pattern
August, 2007
RF200 - 149
PN Symmetrical N=37 Reuse Pattern Exploded View
August, 2007
RF200 - 150
Course RF200 Section II.
Introduction
Introduction to
to CDMA
CDMA
Performance
Performance Data
Data
August, 2007
RF200 - 151
What Data is Available for Performance Study?

HANDSET
CDMA NETWORK EQUIPMENT

Switch
SLM
Access Mgr./BSC-BSM
CM
GPSR
LPP
ENET
BSM
TFU1
DMS-BUS
LPP
DTCs
CDSU
CDSU
DISCO 1
DISCO 2
SBS
IOC
Switch OMs,
pegs, logs
Vocoders
Selectors
Selector
Logs
Various
External
Analysis
Tools
BTS
NOIS Messages
CDSU
CDSU
DISCO
NMIS
Messages
CDSU
CDSU
CDSU
CDSU
CDSU
Ch. Card
GPSR
TFU1
IS-95/J Std 8
Messages
ACC
Txcvr A RFFE A
Txcvr B RFFE B
Txcvr C RFFE C
QC-Specific Messages
IS-95/J Std 8 Messages
Unix-based,
PC-based
Data Analysis
Post-Processing
Tools
Handset
Messages
PC-based
Mobile Data
Capture Tools
PC-based
Mobile Data
Post-Processing
Tools
Q CDMA data for analysis flows from three sources:

Switch, CDMA peripherals and base stations, and the Handset
Q Various software and hardware tools are available for collection and
analysis of each of these streams of data
Q Data contains messages and various indicators of RF performance
August, 2007
RF200 - 152
Resources on System and Switch Data

Q CDMA networks are complex, including large conventional telephone
switches, high-capacity CDMA system peripherals such as BSCs, CBSCs,
and Access Managers, and many base stations (BTSs) which are usually
multi-carrier
A network is literally a CITY of processors and software
Q The specific performance statistics and event counters ('peg counts') are
best described in official documentation from the network manufacturers
However, current documentation always seems to lag behind cuttingedge hardware and software releases
Q Each manufacturer publishes help on its own hardware & software:
Lucent: Wireless Networks Systems Documentation CDs
Application notes; many good training courses
Nortel: Helmsman CD, documents, training courses
Motorola: Planning Guides, documents, training courses
Q This course focuses on the generic key indications to observe, and the
analytical skills and perspective necessary for optimization
The manufacturers' documentation will describe the actual counters
and measurements available from your network
August, 2007
RF200 - 153
System
System Data
Data and
and
Statistical
Statistical Analysis
Analysis
August, 2007
RF200 - 154
Statistical CDMA Performance Indicators

Each network platform (Lucent,
Nortel, Motorola) has its own
unique set of available statistics.
These indications are collected from
the Switch, CDMA peripherals, and
the base stations. They can be
analyzed, tracked and trended for
system performance
benchmarking.
These indications should be examined
from many perspectives: overall for
an entire system, by individual
sector and cell, and both in
absolute numbers and by
percentages of total traffic.
August, 2007
Q Dropped Call Statistics

Q Failed Access Attempts
Q Blocking Statistics
BTS sector level
BSC resource level
Switch resource level
PSTN trunking level
Q Counts of specific call
processing error events
RF200 - 155
Comparing All Systems Sorted By Daily Traffic Level

Example System D Day
All 1,338,386 1,240,937
Example System E Day
All
355,247
347,325
Example System B Day
All
227,257
222,425
Example System C Day
All
220,707
205,766
Example System A Day
All
209,621
205,461
Example System F Day
All
206,482
198,945
Example System H Day ALL
163,921
160,473
Example System G Day
All
148,765
143,633
97.9%
96.1%
443
0.04% 12,429
2.1%
1.1% 20,015
2.8%
92.7% 44,593
97.8%
n/a
97.9%
388
93.2%
6,312
98.0%
n/a
96.4%
n/a
97.9%
63
96.6%
n/a
3.33% 35,329
n/a
7,922
0.17%
4,444
2.86%
6,090
n/a
n/a
n/a
7,537
0.04% 1,776
n/a
5,132
2.64% 30,576
2.23%
n/a
1.96%
n/a
2.76%
5,088
n/a
3,297
3.65%
4,556
1.1% 2,859
3.45%
3,074
1.7% 11,229
2.1%
2.28%
n/a
n/a
2.31%
1.60%
2.29%
1.7%
2.14%
% Screen Cal
Screen Calls
%-Drop
Calls-Drop
%RF Acc-Fail
RF Acc-Fails
%Tot-Block
1,123,308
Total-Block
1,147,447
%-Succ.
Call-Succ.
Cells
Week ALL
Call-Att.
Example H
Average of Others
Period
MTA-Name
Typical Network Performance
1.0%
0.6%
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
1,327 0.6%
n/a
n/a
1,604 1.0%
n/a
n/a
Q Here is a comparison of typical network performance in the industry

against a new rural wireless system with light loading
Q How does your system compare against the industry norms? Against the
lightly loaded rural system?
August, 2007
RF200 - 156
Another Network Performance Example
August, 2007
RF200 - 157
Lucent
Lucent System
System Data
Data
Examples
Examples
August, 2007
RF200 - 158
Lucent System Data Examples
S ys/ ECP / Ce ll/ N a m

e / La be l
% CD MA
R e Acquir
CCE
CD MA_CE
Prim_CS
% P rim_CS
S e c_CS
% CD MA
% CD MA
CD MA
% CD MA
T otCD MA
CD MAT otl
CD MAT otl
CD MA
CD MAOnly
CD MA_Org
CD MA
CD MA
CD MA
CD MA
CD MA
TOTALS
96.83
e d_Ca lls
2.84
e rla ngs
6,580.44
U sa ge
2,368,959
CE _U se
1,451,816
CE _U se
61.28
CE _U se
917,143
SoftH O U se
38.72
SU Fa il
2.79
Lost_Ca ll
1,722
Lost Ca lls
1.17
Fa ilure s
7,856
Origins
5,069
T e rmins
2,787
Ma int Busy
0
P rfSz
80
T rm_Ovf
713
Org_S z
109,076
Org_Asn
105,970
Pg_R sp_S z
46,720
T rm_Asn
44,951
R e q_Alg
4,426
August, 2007
E st Ca lls
179 2 67
S MIT H SP R IN G
S
93.55
179 2 28
179 2 30
179 2 121
179 2 10 IN GLEW OO N OLEN SV IL CLAR KSV IL 179 2 1 179 2 45
BOBCAT
D
LE
LE/ BR ILE Y T E XT R ON FAR MER S
93.58
94.18
94.36
94.44
94.67
94.73
3.22
2.61
3.89
2.38
5.26
2.65
2.06
62.60
128.68
71.45
63.54
36.16
76.37
115.21
22,535
46,323
25,722
22,873
13,016
27,494
41,476
9,300
19,788
13,689
11,113
8,448
15,965
23,219
41.27
42.72
53.22
48.59
64.90
58.07
55.98
13,235
26,535
12,033
11,760
4,568
11,529
18,257
58.73
57.28
46.78
51.41
35.10
41.93
44.02
6.14
5.68
5.44
3.62
3.68
4.64
5.04
15
42
20
10
64
15
35
1.67
2.18
1.18
0.89
5.98
0.98
1.44
95
208
143
77
108
102
206
65
143
89
47
73
67
141
30
65
54
30
35
35
65
680
1,500
1,236
771
828
1,229
1,862
659
1,454
1,197
752
786
1,192
1,824
313
611
640
445
369
430
755
301
590
603
412
329
414
736
32
55
73
29
63
44
54
RF200 - 159
Lucent Overload Data Examples from

Autopace
S ys/ E CP / Ce ll/ N
a me / Ante nna
ID / Ant_N a me
CD MA_Acs
CD MA_Avg
CD MA_Fwd
CD MA_Fwd
CD MA
CD MA_P g
CD MA_P k
CD MA_P k
CD MA_R e v
CD MA_R e v
CD MA
CD MA_T f
CD MA_Jmr
TOTALS
5,921
S q_D G
1,123,466
P COLdur
581
P COLcnt
339
Intcpt_Msg
0
Ch_Ocpn
489,506
Acs_ChOc
91,989
P g_ChOc
555,984
P COLdur
305
P COLcnt
6
R e orde r_Msg
2
CdCh_U sg
245,143
D e t_D ur
0
August, 2007
Chn_Oc
179 2 1
179 2 1
179 2 1
T E XT R ON 1 T E XT R ON T E XT R ON
2 Ante nna :2 3 Ante nna :3
Ante nna :1
179 2 2
179 2 2
179 2 2
BE LMON T BE LMON T
BE LMON T
1 Ante nna :1 2 Ante nna :2 3 Ante nna :3
30
28
10
27
13.00
13.00
6,187
6,157
6,088
6,168
5,016.00
4,818.00
12
0.00
0.00
0.00
0.00
0.00
0.00
2,771
2,763
2,754
2,795
2,756.00
2,766.00
985
563
281
563
422.00
281.00
3,264
3,140
3,197
3,125
3,120.00
3,155.00
0.00
0.00
0.00
0.00
0.00
0.00
1,360
1,188
980
953
821.00
862.00
0.00
0.00
RF200 - 160
Nortel
Nortel System
System Data
Data
Examples
Examples
August, 2007
RF200 - 161
Nortel BTSC MO Attributes

Each attribute is a periodic counter maintained during the 15-minute automatic logging period.
Attribute Name
Data
Type
Seq. Access,
Number Range
BlockedOriginationsNoTCE
word16
0x0002A
42
P
full
Number of originations blocked because

no idle channel elements were available
BlockedOriginationsNoFwdCap word16
0x0002B
43
P
full
Number of originations blocked due to

lack of BTS forward link excess capacity
BlockedOriginationsNoRevCap word16
0x0002C
44
P
full
Number of originations blocked due to

lack of reverse link capacity
Description
BlockedHandoffsNoTCE
word16
0x0002D
45
P
full
Number of handoffs blocked because no

idle channel elements were available
BlockedHandoffsNoFwdCap
word16
0x0002E
46
P
full
Number of handoffs blocked due to lack

of BTS forward link excess capacity
BlockedHandoffsNoRevCap
word16
0x0002F
47
P
full
Number of handoffs blocked due to lack

of reverse link capaicty
SuccessfulOriginations
word16
0x00030
48
P
full
Number of successful originations
SuccessfulHandoffs
word16
0x00031
49
P
full
Number of successful handoffs
August, 2007
RF200 - 162
Nortel FA MO Attributes
Each attribute is a periodic counter maintained during the 15-minute automatic logging period.
FA MO
Sequence
Number
16
17
18
19
1A
1B
1C
1D
1E
1F
20
21
22
23
24
25
26
27
28
29
2A
2B
2C
August, 2007
OM name
TCEUtilMaximum
NumOfTCsConfigured
soft1softer1Alpha
soft1softer1Beta
soft1softer1Gamma
soft1softer2AlphaBeta
soft1softer2BetaGamma
soft1softer2GammaAlpha
soft1softer3
soft2softer1Alpha
soft2softer1Beta
soft2softer1Gamma
soft2softer3
soft3softer1Alpha
soft3softer1Beta
soft3softer1Gamma
soft3softer3
FA MO
Sequence
Number
2D
2E
2F
30
31
32
33
34
35
36
37
38
39
3A
3B
3C
3D
OM name
soft4softer1Alpha
soft4softer1Beta
soft4softer1Gamma
soft4softer3
soft5softer1Alpha
soft5softer1Beta
soft5softer1Gamma
soft6softer1Alpha
soft6softer1Beta
soft6softer1Gamma
TimeNotInUse
RF200 - 163
Nortel BTSC MO Events

Each event counter is maintained during the 15-minute automatic logging period.
Event Report Name
Type
Event Report
Seq.
Number
0x000?
BTSCPerformanceData PerformanceData
0?
Description
Includes as parameters all attributes with P
access documented in the attribute table for
this MO.
FA MO Events
Each event counter is maintained during the 15-minute automatic logging period.
Event Report Name
FAPerformanceData
August, 2007
Type
Event Report
Seq.
Number
0x000?
PerformanceData
0?
Description
Includes as parameters all attributes with P
access documented in the attribute table for
this MO.
RF200 - 164
Nortel BTSC MO Report Example

XYZ 19971120 BTSC MO Report
+----+----------------------------+------+------+------+------+------+------+------+------+
|BTS |
Start Date/Time |OBlock|OBlock|OBlock|HBlock|HBlock|HBlock| Succ | Succ |
|
|
End Date/Time
|No TCE|No Fwd|No Rev|No TCE|No Fwd|No Rev| Origs|Handof|
+----+----------------------------+------+------+------+------+------+------+------+------+
|
1|1997/11/20 01:30:00-02:00:00|
0|
0|
0|
0|
0|
0|
3|
5|
|
1|1997/11/20 12:00:00-12:30:00|
0|
0|
0|
0|
0|
0|
46|
314|
|
1|1997/11/20 12:30:00-13:00:00|
0|
0|
0|
0|
0|
0|
76|
470|
|
1|1997/11/20 13:00:00-13:30:00|
0|
0|
0|
0|
0|
0|
45|
414|
|
1|1997/11/20 13:30:00-14:00:00|
0|
0|
0|
0|
0|
0|
55|
375|
|
1|1997/11/20 14:00:00-14:30:00|
0|
0|
0|
0|
0|
0|
50|
525|
|
1|1997/11/20 14:30:00-15:00:00|
0|
0|
0|
0|
0|
0|
72|
433|
|
1|1997/11/20 15:00:00-15:30:00|
0|
0|
0|
0|
0|
0|
66|
412|
|
1|1997/11/20 15:30:00-16:00:00|
0|
0|
0|
0|
0|
0|
53|
323|
|
1|1997/11/20 16:00:00-16:30:00|
0|
0|
0|
0|
0|
0|
63|
342|
|
1|1997/11/20 16:30:00-17:00:00|
0|
0|
0|
0|
0|
0|
51|
331|
|
1|1997/11/20 17:00:00-17:30:00|
0|
0|
0|
0|
0|
0|
39|
323|
|
1|1997/11/20 17:30:00-18:00:00|
0|
0|
0|
0|
0|
0|
51|
310|
|
1|1997/11/20 18:00:00-18:30:00|
0|
0|
0|
0|
0|
0|
45|
237|
|
1|1997/11/20 18:30:00-19:00:00|
0|
0|
0|
0|
0|
0|
31|
299|
|
1|1997/11/20 19:00:00-19:30:00|
0|
0|
0|
0|
0|
0|
37|
282|
|
1|1997/11/20 19:30:00-20:00:00|
0|
0|
0|
0|
0|
0|
19|
143|
|
1|1997/11/20 20:00:00-20:30:00|
0|
0|
0|
0|
0|
0|
18|
96|
|
1|1997/11/20 20:30:00-21:00:00|
0|
0|
0|
0|
0|
0|
33|
192|
|
1|1997/11/20 21:00:00-21:30:00|
0|
0|
0|
0|
0|
0|
25|
226|
|
1|1997/11/20 21:30:00-22:00:00|
0|
0|
0|
0|
0|
0|
15|
235|
|
1|1997/11/20 22:00:00-22:30:00|
0|
0|
0|
0|
0|
0|
15|
216|
|
1|1997/11/20 22:30:00-23:00:00|
0|
0|
0|
0|
0|
0|
9|
162|
|
1|1997/11/20 23:00:00-23:30:00|
0|
0|
0|
0|
0|
0|
3|
40|
|
|Totals for BTS 1
|
0|
0|
0|
0|
0|
0| 1235| 8895|
August, 2007
RF200 - 165
Nortel Selector Log File Example

=====================================================
Status
: OLFLR_OK
Record Type
: NEIGHBOR_LIST_TUNING_DATA_ARRAY
File Offset
: 414 (octal)
Time Stamp
: 97/10/29-00:29:25.380
Record Length
: 72
Header Length
: 51
Source Node Id
: 297543 (0x00048a47)
OID:AgentId
: 297536 (0x00048a40)
OID:MOClass
: 81 (0x0051)
OID:MOVersion
: 1 (0x0001)
OID:MOInstance
: 1 (0x0001)
Call Id
: SID 0x4026 EntryPoint 0x134a Count 0x0 Time 0x2cfe821
IMSI
: NumDigits 15 Digits 134006043294814 (123-63-251-3692bf)
ESN
: 0x9f0d02ac
PFFlags
: 0x1f
Secondary Agent Id : 0x8a40
FramingBytes
: 0xfaae
Sequence Number
: 57
AttributeType
: 0x0256
AttributeInstance
: 0x0030
Log Attr -> Type : LogSBSNeighborListTuningDataArray
Seq Num : 0030
LogData object contents:

Data Type
: NEIGHBOR_LIST_TUNING_DATA_ARRAY
Resource Type : OCC_SBS_RESOURCE
TimeStamp
: 97/10/29-00:29:25.380
Count : 2
Ext'dBaseId
PowerCombineBit
PilotStrength
PNOffset
+++++=========================++++=========================+++++
0x018002a3
1
8
0x0104
0x018002a1
1
19
0x01a4
=====================================================
August, 2007
RF200 - 166
Nortel FAMO Report Example

XYZ 19971120 FA MO Report
+----+----------------------------+---------+---------+-----+-------+-------+-------+-----+---+
|BTS |
Start Date/Time |
MOU
|
MOU
| CE/ | MOU | MOU | MOU |%Soft|Max|
|
|
End Date/Time
|
CE
| Traffic | User| Alpha | Beta | Gamma | HO |TCE|
+----+----------------------------+---------+---------+-----+-------+-------+-------+-----+---+
|
1|1997/11/20 07:00:00-07:30:00|
41.99|
33.35| 1.26| 11.77|
4.62| 16.96|20.58| 15|
|
1|1997/11/20 07:00:00-07:30:00|
73.06|
46.22| 1.58| 17.72| 14.10| 14.39|36.75| 15|
|
1|1997/11/20 08:00:00-08:30:00|
109.87|
66.05| 1.66| 24.78| 20.21| 21.06|39.88| 15|
|
1|1997/11/20 10:00:00-10:30:00|
153.79|
89.81| 1.71| 41.85| 32.19| 15.77|41.60| 15|
|
1|1997/11/20 10:30:00-11:00:00|
181.09|
102.19| 1.77| 43.60| 28.22| 30.38|43.57| 15|
|
1|1997/11/20 11:00:00-11:30:00|
152.59|
84.73| 1.80| 37.61| 18.51| 28.61|44.47| 15|
|
1|1997/11/20 11:30:00-12:00:00|
143.70|
89.16| 1.61| 39.66| 24.78| 24.72|37.95| 15|
|
1|1997/11/20 12:00:00-12:30:00|
156.58|
89.52| 1.75| 25.51| 21.91| 42.10|42.83| 15|
|
1|1997/11/20 12:30:00-13:00:00|
165.54|
89.97| 1.84| 44.41| 22.89| 22.67|45.65| 15|
|
1|1997/11/20 13:00:00-13:30:00|
170.36|
99.19| 1.72| 52.81| 24.58| 21.79|41.78| 15|
|
1|1997/11/20 13:30:00-14:00:00|
145.34|
93.71| 1.55| 41.88| 24.05| 27.77|35.53| 15|
|
1|1997/11/20 14:00:00-14:30:00|
189.61|
121.49| 1.56| 52.43| 30.99| 38.06|35.93| 15|
|
1|1997/11/20 14:30:00-15:00:00|
153.65|
108.08| 1.42| 47.58| 37.52| 22.99|29.65| 15|
|
1|1997/11/20 15:00:00-15:30:00|
165.08|
106.66| 1.55| 49.00| 29.69| 27.97|35.39| 15|
|
1|1997/11/20 15:30:00-16:00:00|
159.27|
94.72| 1.68| 42.04| 28.43| 24.25|40.53| 15|
|
1|1997/11/20 16:00:00-16:30:00|
172.52|
114.62| 1.51| 56.57| 28.50| 29.55|33.56| 15|
|
1|1997/11/20 16:30:00-17:00:00|
156.83|
105.46| 1.49| 53.29| 30.38| 21.80|32.76| 15|
|
1|1997/11/20 17:00:00-17:30:00|
129.13|
82.52| 1.56| 31.50| 24.28| 26.73|36.10| 15|
|
1|1997/11/20 17:30:00-18:00:00|
134.80|
81.76| 1.65| 35.80| 30.20| 15.77|39.35| 15|
|
1|1997/11/20 18:00:00-18:30:00|
96.91|
60.49| 1.60| 27.80| 15.38| 17.31|37.58| 15|
|
1|1997/11/20 18:30:00-19:00:00|
124.25|
73.62| 1.69| 22.37| 30.93| 20.33|40.75| 15|
|
1|1997/11/20 19:00:00-19:30:00|
75.50|
41.14| 1.83| 18.03| 14.88|
8.24|45.50| 15|
|
1|1997/11/20 19:30:00-20:00:00|
40.58|
23.56| 1.72| 12.50|
5.72|
5.33|41.95| 15|
|
1|1997/11/20 20:00:00-20:30:00|
51.14|
29.81| 1.72| 13.26| 10.37|
6.19|41.71| 15|
|
1|1997/11/20 20:30:00-21:00:00|
102.45|
55.26| 1.85| 16.36| 18.49| 20.41|46.07| 15|
|
1|1997/11/20 21:00:00-21:30:00|
108.48|
74.86| 1.45| 28.32| 17.26| 29.27|30.99| 15|
|
1|1997/11/20 21:30:00-22:00:00|
109.92|
68.50| 1.60| 26.53| 19.22| 22.75|37.68| 15|
|
1|1997/11/20 22:00:00-22:30:00|
86.58|
59.36| 1.46| 26.09| 15.11| 18.15|31.45| 15|
|
1|1997/11/20 22:30:00-23:00:00|
94.96|
63.48| 1.50| 27.73| 20.85| 14.90|33.15| 15|
|
1|1997/11/20 23:00:00-23:30:00|
28.07|
20.76| 1.35|
9.06|
8.14|
3.55|26.04| 15|
|
|Totals for BTS 1
| 3690.90| 2280.64| 1.62| 980.80| 655.61| 644.22|38.21| 15|
August, 2007
RF200 - 167
Motorola
Motorola System
System Data
Data
Examples
Examples
August, 2007
RF200 - 168
Motorola System Data Examples

Usage OOS
Orig
Orig
Orig
Term
Term
Term
RF
RF
Usage/
Cell MCC CE min
min
Atts
Comps Fail% Atts
Comps Fail% Loss
Loss% Att
---- --- --- ------ ------ ------ ------ ------ ------ ------ ------ ------ ------ -----88
1
2 383.1 146.2
170
160
5.9
20
19
5.0
2
1.1 121.0
88
1
3 426.3 146.2
154
150
2.6
10
10
0.0
3
1.9 156.0
88
1
4 456.9 146.2
160
156
2.5
22
22
0.0
7
3.9 150.6
88
1
5 448.2 146.2
163
162
0.6
18
18
0.0
4
2.2 148.6
88
1
6 439.5 146.2
162
159
1.9
20
20
0.0
2
1.1 144.9
88
1
7 439.9 146.2
160
157
1.9
14
14
0.0
5
2.9 151.7
88
1
8 351.6 146.2
186
182
2.2
23
23
0.0
5
2.4 100.9
88
1
9 397.4 146.2
164
161
1.8
20
20
0.0
3
1.7 129.6
88
1 10 422.5 146.2
177
174
1.7
15
15
0.0
2
1.1 132.0
88
1 11 402.2 146.2
183
179
2.2
22
22
0.0
1
0.5 117.7
88
1 12 398.2 146.2
179
176
1.7
13
13
0.0
5
2.6 124.4
88
1 13 447.5 146.2
163
161
1.2
26
26
0.0
11
5.9 142.1
88
1 14 263.5 146.2
290
83
71.4
31
19
38.7
5
4.9
49.3
88
1 15 307.8 146.2
264
68
74.2
36
9
75.0
3
3.9
61.5
88
2
2 403.1 105.9
165
162
1.8
14
14
0.0
1
0.6 135.1
88
2
3 477.0 105.9
163
158
3.1
18
18
0.0
3
1.7 158.1
88
2
4 419.4 105.8
166
161
3.0
24
24
0.0
2
1.1 132.4
88
2
5 445.8 105.8
174
171
1.7
14
14
0.0
7
3.8 142.3
88
2
6 525.1 105.8
157
155
1.3
17
17
0.0
3
1.7 181.1
88
2
7 422.0 105.8
165
161
2.4
18
17
5.6
1
0.6 138.4
88
2
8 430.3 105.8
188
183
2.7
14
14
0.0
7
3.6 127.8
88
2
9 419.9 105.8
167
166
0.6
12
11
8.3
6
3.4 140.7
88
2 10 391.0 105.3
165
164
0.6
22
22
0.0
4
2.2 125.5
88
2 11 443.5 105.3
174
168
3.4
11
11
0.0
5
2.8 143.8
88
2 12 412.5 105.3
177
171
3.4
21
21
0.0
4
2.1 125.0
88
2 13 394.2 105.3
196
192
2.0
16
16
0.0
6
2.9 111.6
88
2 14 432.0 105.3
141
139
1.4
18
18
0.0
5
3.2 163.0
88
2 15 388.5 105.3
178
176
1.1
17
17
0.0
2
1.0 119.5
August, 2007
RF200 - 169
Analyzing
Analyzing System
System Data
Data
August, 2007
RF200 - 170
Percent
Total Blocked Call Percentage Example

Total Block Call Percentage
8.0%
7.5%
7.0%
6.5%
6.0%
Blkd
5.5%
5.0%
4.5%
4.0%
3.5%
3.0%
2.5%
2.0%
1.5%
1.0%
Date
Q This is an example of a cumulative system-wide total blocked call

percentage chart maintained in one market
August, 2007
RF200 - 171
Percent
Dropped Call Percentage Tracking Example
Total Drop Call Percentage

5.0%
4.5%
%Drops
4.0%
3.5%
3.0%
2.5%
2.0%
1.5%
1.0%
0.5%
0.0%
Date
Q Dropped call percentage tracking by one market

August, 2007
RF200 - 172
Total System Daily MOU Example
MOU
Daily Total System MOU
300000
Daily Total System MOU
250000
200000
150000
100000
50000
Date
Q Total system daily MOU plotted by one market

August, 2007
RF200 - 173
Top Ten Performance Tracking Example

Call Attempts
3000
2500
2000
1500
1000
500
108.1
43.3
108.2
1.3
Sector
102.2
137
130
65
101
83
49
30
24
46
31
7.5
5.1
5.1
4.5
4.3
3.0
2.9
2.8
2.6
1.9
136
130
65
101
83
49
30
24
45
31
7.4
5.1
5.1
4.5
4.3
3.0
2.9
2.8
2.6
1.9
110
145
90
93
66
66
58
112
83
81
6.0
5.7
7.0
4.1
3.4
4.1
5.7
13.1
4.8
5.0
8.0
7.0
6.0
5.0
4.0
3.0
2.0
1.0
0.0
Sector
26.3
84.5
87.2
85.7
89.9
90.7
91.6
90.2
81.6
91.3
91.7
% Blocked Calls
64.1
1549
2234
1098
2017
1743
1486
926
698
1589
1495
%Acc Drop %Drop

Fail Calls Calls
63.2
1833
2561
1282
2244
1922
1623
1027
855
1740
1630
Acc
Fail
1.2
Call %Call Block %Blck

Call Att Succ Succ Calls Calls
2.1
93Z
13X
57Z
2X
1Y
57Y
93X
35Z
30Y
1Z
Call Attempts
63.3
64.3
6.1
63.3
2.1
1.2
63.2
64.1
26.3
108.2
1.3
5.7
4.1
3.4
6.0
4.8
5.0
4.1
4.3
3.6
3.6
6.1
MSC
Site
145
93
66
110
83
81
66
70
54
53
September 5, 1997
% Blocked Calls
Eng
Site
5.1
4.5
4.3
7.4
2.6
1.9
3.0
1.1
1.8
0.3
63.2
130
101
83
136
45
31
49
18
27
4
1.3
5.1
4.5
4.3
7.5
2.6
1.9
3.0
1.1
1.8
0.3
108.2
130
101
83
137
46
31
49
18
27
4
64.3
87.2
89.9
90.7
84.5
91.3
91.7
91.6
92.6
93.1
94.8
1.2
2234
2017
1743
1549
1589
1495
1486
1495
1387
1410
2.1
2561
2244
1922
1833
1740
1630
1623
1615
1490
1488
%Acc Drop %Drop

Fail Calls Calls
6.1
13X
2X
1Y
93Z
30Y
1Z
57Y
4Y
30X
42Z
Acc
Fail
64.3
6.1
2.1
1.2
64.3
108.2
1.3
63.2
102.2
108.1
43.3
Call %Call Block %Blck

Call Att Succ Succ Calls Calls
Calls
MSC
Site
Eng
Site
Q Many markets use scripts or spreadsheet macros to produce

ranked lists of sites with heavy traffic, performance problems, etc.
August, 2007
RF200 - 174
Bracketing: Fault Notification and Alarming

Historic Performance Data and Automatic Alarming
Q Some operators develop their

own software for monitoring
and tracking performance data
Q Each new 30-minute period is
compared against a six-week
average for that day and time
Q If the new value is outside
user-selectable tolerances
(typically +/- 30%), an alarm is
sent to operations personnel
By SMS or pager
Q The tolerance values can be
adjusted to produce
reasonable numbers of alarms
Typically 20-40 alarms per
day
August, 2007
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
SM TWT F S SM TWT F S SM TWT F S SM TWT F S SM TWT F S SM TWT F S SM TWT F S
TOO LOW
+30%
NORMAL
TOO HIGH
+30%
+30%
-30%
-30%
6-week average
-30%
If an important performance statistic varies

outside a user-specified range, an alarm message
is sent automatically to the performance specialist
responsible for that base station.
RF200 - 175
CDMA
CDMA System
System Parameters
Parameters
August, 2007
RF200 - 176
Lucent BTS Parameters Example
SysID
ECPID
CellID
Antenna
CDMAPilotPN
CDMAPilotDrpThrsh
CDMAPilotDetThrsh
CDMACompThrsh
CDMADropTimer
CDMASrchWinActCand
CDMASrchWinNbr
CDMASrchWinRemain
CDMAPilotGain
CDMAPageGain
CDMASyncGain
CDMABCRAtt
SectorSize_ceqface
BBAMaxPower
CDMAMinTrfChnlGain_R2
CDMAMaxTrfChnlGain_R2
CDMATrafGain_R2
CDMAFwdFrmErrRate_R2
CDMARevFrmErrRate_R2
CDMANomEbNoSetPt_R2
CDMAMinEbNoSetPt_R2
CDMAMaxEbNoSetPt_R2
Srchwincell
August, 2007
179
2
1
1
4
-15
-13
2.5
179
2
1
1
4
-15
-13
2.5
179
2
1
1
4
-15
-13
2.5
179
2
1
1
4
-15
-13
2.5
179
2
1
1
4
-15
-13
2.5
179
2
1
2
172
-15
-13
2.5
179
2
1
2
172
-15
-13
2.5
179
2
1
2
172
-15
-13
2.5
179
2
1
2
172
-15
-13
2.5
179
2
1
2
172
-15
-13
2.5
179
2
1
3
340
-15
-13
2.5
179
2
1
3
340
-15
-13
2.5
179
2
1
3
340
-15
-13
2.5
179
2
1
3
340
-15
-13
2.5
179 179 179 179

2
2
2
2
1
2
2
2
3
1
1
1
340
8
8
8
-15 -15 -15 -15
-13 -13 -13 -13
2.5
2
2
2
3
7
9
0
108
64
34
6
3
3
3
7
7
7
9
9
9
0
0
0
108 108 108
64 64 64
34 34 34
6
6
6
3
7
9
0
108
64
34
6
3
7
9
0
108
64
34
6
3
7
7
0
108
64
34
6
3
3
3
7
7
7
7
7
7
0
0
0
108 108 108
64 64 64
34 34 34
6
6
6
3
7
7
0
108
64
34
6
3
7
7
0
108
64
34
6
3
7
7
0
108
64
34
8
3
3
3
7
7
7
7
7
7
0
0
0
108 108 108
64 64 64
34 34 34
8
8
8
3
7
7
0
108
64
34
8
3
3
3
3
7
7
7
7
7
7
7
7
0
0
0
0
108 108 108 108
64 64 64 64
34 34 34 34
8
8
8
8
33.5 33.5
179
2
1
1
4
-15
-13
2.5
21
21 33.5 33.5 33.5 33.5
179
2
1
2
172
-15
-13
2.5
21
21 33.5 33.5 33.5 33.5
179
2
1
3
340
-15
-13
2.5
21
21 33.5 33.5
25
25
25
1
1
6.8
1
1
1
1
1
1
6.8 6.8 6.8
1
1
6.8
1
1
6.8
1
1
6.8
1
1
1
1
1
1
6.8 6.8 6.8
1
1
6.8
1
1
6.8
1
1
6.8
1
1
1
1
1
1
6.8 6.8 6.8
1
1
6.8
1
1
1
1
1
1
1
1
6.8 6.8 6.8 6.8
3.8
8.8
32
3.8 3.8 3.8

8.8 8.8 8.8
32 32 32
3.8
8.8
32
3.8
8.8
32
3.8
8.8
32
3.8 3.8 3.8

8.8 8.8 8.8
32 32 32
3.8
8.8
32
3.8
8.8
32
3.8
8.8
32
3.8 3.8 3.8

8.8 8.8 8.8
32 32 32
3.8
8.8
32
3.8 3.8 3.8 3.8

8.8 8.8 8.8 8.8
32 32 32 32
RF200 - 177
Nortel System Parameters Example

Proto type datafill for 1900 CDMA System Parameters
Parameter Name
1. CDMA Channel Parameters
System Determination and Acquisition
CDMA_ AVAIL
CDMA_FREQ (CDMA_CHAN)
BAND_CLASS
System Acquisition (Sync channel Information)
P_REV
MIN_P_REV
SID
NID
PILOT_PN
LC_STATE
SYS_TIME
PRAT
LP_SEC
LTM_OFF
DAYLT
Range
Recommended Value
0-1
0 - 2047
0 - 31
0-255
0-255
0 - 32,767
0 - 65,535
0 - 511
TFU_1 or TFU_2
0-3
0-255
0-63
0-1
Remarks
1
See Remarks As determined by the local MTA
1 1900 MHz
1
1
See Remarks
See Remarks
See Remarks
See Remarks
See Remarks
1
13
16
0 or 1
As determined by the local MTA

Determined by the system. TBA
As detetermined by the System time
TBA
TBA
Depending on whether Daylight saving is On/Off
Q Nortel parameters are built in files on the BSM, then downloaded

to BTS and SBS locations
August, 2007
RF200 - 178

2. Access Parameters
Request Response Parameters
PSIST(0-9)
PSIST(10-15)
MAX_CAP_SZ
PAM_SZ
REG_PSIST
MSG_PSIST
PROBE_PN_RAN
ACC_CHAN
ACC_TMO
PROBE_BKOFF
BKOFF
MAX_REQ_SEQ
MAX_RSP_SEQ
AUTH
RAND
0 - 63
0-7
0-7
0 - 15
0-7
0-7
0 - 15
0 - 31
0 - 15 (x80 ms)
0 - 15
0 - 15
0 - 15
0 - 15
0-3
0-(232-1)
0
0
3
4
0
0
0
0
3
0
1
2
2
0
0
ACCOLC(0 -9) are all permitted to transmit

ACCOLC(10 -15) are all permitted to transmit
3 Frames message
4 Frames preamble
1 Access channel
(2+1), 240 ms
(0 + 1) slot delay
(0 + 1) slot delay
No standard Authentication
Not applicable without Authentication
Q Parameters here determine contents of Access Parameters

Message on the Paging Channel
August, 2007
RF200 - 179

Registaration Parameters
SID
NID
REG_ZONE
TOTAL_ZONES
ZONE_TIMER
MULTI_SIDS
MULTI_NIDS
BASE_ID
BASE_CLASS
PAGE_CHAN
MAX_SLOT_CYCLE_INDEX
HOME_REG
FOR_SID_REG
FOR_NID_NEG
POWER_UP_REG
POWER_DOWN_REG
PARAMETER_REG
REG_PRD
BASE_LAT
BASE_LONG
REG_DIST
RESCAN
0 - 32,767
0 - 65,535
0 - 4095 As determined by the network Zone Registration not currently supported
0-7
0 Zone Registration not currently supported
0-7
0 Zone Registration not currently supported
0-1
0 If roaming is permitted, this should be set to 1
0-1
0 If roaming or more than one NID in the MTA, set to 1
0 - 65,535
0 - 15
0 Public macro cellular system
0-7
1 One paging channel
0-7
5
0-1
1
0-1
1
0-1
1
0-1
1
0-1
1
0-1
1
0 - 127
0 Periodic registration every 2621 sec (43 min)
-1296000, +1296000
-2592000, +2592000
0 No distance based registration
0-2047
0
Q Parameters here determine the contents of the registration fields of

the System Parameters Message on the paging channel
August, 2007
RF200 - 180

3. Power Control Parameters
Open Loop
NOM_PWR
INIT_PWR
PWR_STEP
NUM_STEP
0 -15
0 - 31
0-7
0 - 15
8
16
3
6
Forward Power Control

PWR_REP_THRESH
PWR_REP_FRAMES
PWR_THRESH_ENABLE
POWER_PERIOD_ENABLE
POWER_REP_DELAY
0 - 31
0 - 15
0-1
0 -1
0 - 31
2
7
1
0
1
0-1
0 - 15(4 - 452 PN Chps)
0 - 15(4 - 452 PN Chps)
0 - 15(4 - 452 PN Chps)
0 - 15
0 - 15
0-7
1
8
10
10
2
4
0

60 PN chips
100 PN chips
100 PN chips
0 - 63(-0.5x dB)
0 - 63(-0.5x dB)
0 - 15 (=< 0.1 - 319 sec)
0 - 15 (x0.5 dB)
28
32
3
5
-14 dB
-16 dB
4 sec
2.5 dB
4. Handoff Parameters
Pilot Search Parameters
PILOT_PN
SEARCH_WIN_A
SEARCH_WIN_N
SEARCH_WIN_R
NGHBR_MAX_AGE
PILOT_INC
NGHBR_CONFIG
Pilot Strength Parameters
T_ADD
T_DROP
T_TDROP
T_COMP
8' = 0 dB
16' = 0 dB
3 dB
(6 +1) access probes per sequence
Only applicable to RateSet1 (8 kbps) data

4 frames, only applicable to RateSet1 (8 kbps) data
Q These parameters are communicated to the mobile in the

overhead messages on the Paging Channel.
August, 2007
RF200 - 181

NMIS Parameter
Range
Recommended Value
Remarks
Acquisition
AccessChannelAcquisitionSearchWidth
AccessChannelDemodulationSearchWidth
TrafficChannelAcquisitionSearchWidth
TrafficChannelDemodulationSearchWidth
PowerControl
RateSet1Data, RateSet2Data
PrRXerror (FER %)
Full
Half
Quarter
Eighth
Unknown
RRXincrease
Full
Half
Quarter
Eighth
Unknown
RateSet1Data
PRXlower (Ew/Nt)
PRXupper (Ew/Nt)
PRXstart (Ew/Nt)
RateSet2Data
PRXlower (Ew/Nt)
PRXupper (Ew/Nt)
PRXstart (Ew/Nt)
RateSet1Data
PrTXerror
RTXincrease
PTXlower
PTXupper
PTXstart
RateSet2Data
PrTXerror
RTXincrease
PTXlower
PTXupper
PTXstart
PowerControlGainOffset
August, 2007
25 - 4095
25 - 4095
25 - 4095
25 - 4095
1/16 - 256/16
1/16 - 256/16
1/16 - 256/16
1/16 - 256/16
1/16 - 256/16
1/256 - 4095/256
1/256 - 4095/256
1/256 - 4095/256
1/256 - 4095/256
1/256 - 4095/256
TBA
TBA
TBA
TBA
16/16
80/16
80/16
80/16
16/16
Used by
Used by
Used by
Used by
the BTS
the BTS
the BTS
the BTS
for the revese link

for the revese link
for the revese link
for the revese link
1%
5%
5%
5%
1%
42/256
7/256
7/256
7/256
14/256
1/256 - 4095/256
1/256 - 4095/256
1/256 - 4095/256
2048/256 (8 - 10log2) = 5 dB Eb/Nt

3328/256 (11 - 10log2) = 8 dB Eb/Nt
2688/256 (10.5 - 10log2) = 7.5 dB Eb/Nt
1/256 - 4095/256
1/256 - 4095/256
1/256 - 4095/256
2509/256 (10 - 10log3) = 5.2 dB Eb/Nt

3789/256 (13 - 10log3) = 8.2 dB Eb/Nt
3149/256 (12.5 - 10log3) = 7.7 dB Eb/Nt
1/16 - 256/16
1/256 - 4095/256
-4095/256 - 0/256
-4095/256 - 0/256
-4095/256 - 0/256
16
20/256
-2304/256
-768/256
-1536/256
1/16 - 256/16
1/256 - 4095/256
-4095/256 - 0/256
-4095/256 - 0/256
-4095/256 - 0/256
16
133/256
-3072/256
-256/256
-1536/256
-127 to 128
1%
-9 dB
-3 dB
-6 dB
1%
-12 dB
-1 dB
-6 dB
RF200 - 182

Wilting, Blossoming and Breathing Parameters
WiltBlossStepSize
WiltBlossStepTime
WiltBlossEnabled
BreathingStepSize
BreathingStepTime
BreathingDelta
BreathingEnabled
RecPowerEstimationFilterRate
RecPowerDecayExponential
TXAttenNormal
TXPowerMax
TXAttenAntenna
TPEFilterDecayExponential
ReverseLinkCapacityEstimationRate
HandoffBlockingThreshold
CallBlockingThreshold
RXFEGain
RcvrA
RCVRB
RXFENoiseFigure
RCVRA
RCVRB
RXCableAtten
RcvrA
RCVRB
RXCableNoiseFigure
RCVRA
RCVRB
RXCardNoiseFigureMin
RXCardNoiseFigureMax
0/16 - 255/16 dB (0-255)

1 - 20 (units of 100 ms)
0-1
1/16 - 255/16 dB/ms
1 - 20 (units of 100 ms)
0/16 - 255/16 dB (0-255)
0-1
2 - 40 (units of 5 ms)
0 - 16
0-70 (0/16 - 1120/16 dB)
384/16 - 736/16 dBm
0-6 (0/16 - 96/16 dB)
0 - 16
20*5 to 255*5 ms
0-100 %
0-100 %
0/16 - 480/16 dB
0/16 - 480/16 dB
0/16 - 160/16 dB
0/16 - 160/16 dB
0/16 - 480/16 dB
0/16 - 480/16 dB
0/16 - 160/16 dB
0/16 - 160/16 dB
0/16 - 1120/16
0/16 - 1120/16
4/16 dB (4)
1
1
4/16 dB/ms
1
192/16 (4 dB [64] or more)
0
4
6
See Remarks
672/16
0
5
100 (20*5)
5?
10?
Rate should be 1 dB/sec

100 msec
Rate should be 1 dB/sec
100 msec
12 dB rise over the noise floor
Disabled
Steps of 5 ms. 4 =20 ms
As given by the installtion & calibration
42 dBm(16 W)
As determined by Pilot Channel calibration process. As measure
Not supported
Not supported
Not supported
See Remarks As given by the installtion & calibration

According to above cable loss of antenna path for the specific ap
Close to RxCableAtten According to noise figure intro'd due to cable loss of antenna pat
5 dB for 800, 4 dB for 1900 As given by the Rx card calibration
960/16 60 dB
Q Wilting and blossoming are techniques for gracefully taking a sector from
service or returning it to service without dropping traffic.
August, 2007
RF200 - 183

Pilot Data Base
PilotChannel
CDMACenterFrequency ??
ExtendedBaseId
Available
QuickRepeat
BlankAndBurst
ForwardGain
PilotGain
MinPilotToTotalPwrRatio
NeighborList
CellType
word32
0 -1
0 -1
0 -1
0 - 255
0 - 255
-255/16 to 0/16 dB
word32Array, up to 20 nieghb
CELL_STANDARD, CELL_P
CELL_BORDER
See Remarks
See Remarks
1
0
0
TBA
216
-7
See Remarks
CELL_STANDARD
As determined by the Preferred Channel Set

BandClass, CDMAFreq,BASE_ID,Sector
disabled
Not used
216 for 800 MHz
20% of HPA power
As determined by the RF design
If no HHO in the cell
SyncChannel
SyncGain
0 - 255
68 10 dB down from pilot for 800 MHz
PagingGain
0 - 255
130 4.4 dB down from pilot for 800 MHz
PagingChannel
Q These parameters set the power levels of the overhead channels.
August, 2007
RF200 - 184
Motorola System Parameters

Q Motorola customers should obtain the proprietary Motorola
document, CDMA RF Application Note: Parameters and
Optimization, draft version 8.1 or later, available from your
Motorola representative.
Q This document gives descriptions of most system parameters and
many operational peg counts and valuable guidance for setting
parameters.
August, 2007
RF200 - 185

Forward Pwr Ctrl
August, 2007
Sector 1
Sector 2
Sector 3
C1
C1
C1
PilotPn
66
237
408
PilotGain
127
127
127
127
SchGain
40
40
40
40
PchGain
110
110
110
110
SifPilotPwr
31
31
31
31 dBm
MinPcbGain
20
20
20
20
PcbGainFact
0.75
0.75
0.75
0.75
FwdPwrThresh
2 Frm
PwrThreshEna
PwrPeriodEna
PwrRepThresh
3 Frm
PwrRepFrames
7 Frm
PwrRepDelay
12
12
12
12 Frm
Default
RF200 - 186

Reverse Pwr Ctrl
Sector 1
Sector 2
Sector 3
C1
C1
C1
NomPwr
3 dB
InitPwr
-3
-3
-3
-3 dB
PwrStep
5 dB
NumStep
RPCMaxEbNo
12.5
12.5
12.5
12.5 dB
RPCNomEbNo
9 dB
RPCMinEbNo
6 dB
RPCThrshNom
1930
1930
1930
Cell Size
Sector 1
Sector 2
Sector 3
Default
C1
C1
C1
TchacqWinSz
125
125
125
125 chp
TchmpthWinSz
25
25
25
25 chp
TchPamWinSz
25
25
25
25 chp
CellRadius
10 km
August, 2007
Default
RF200 - 187

Handoff Sector 1
August, 2007
Sector 2
Sector 3
Default
C1
C1
C1
SrchWinA
6 chp
SrchWinN
8 chp
SrchWinR
9 chp
TAdd
-14
-14
-14
-14 dB
TDrop
-16
-16
-16
-16 dB
TComp
4 dB
TTDrop
RF200 - 188

TCH Gain
Sector 1
Sector 2
Sector 3
C1
C1
C1
MaxGain1Way
127
127
127
127
NomGain1Way
80
80
80
80
MinGain1Way
20
20
20
20
MaxGain2Way
127
127
127
127
NomGain2Way
80
80
80
75
MinGain2Way
20
20
20
20
MaxGain3Way
127
127
127
127
NomGain3Way
80
80
80
75
MinGain3Way
20
20
20
20
StepUp
10
10
10
StepDown
DeltaTime
7 Frm
StepDownDel
21
21
21
21 Frm
OrigDelay
100
100
100
100 Frm
TchWCCnt
42
42
42
42 TCH
August, 2007
Default
RF200 - 189

N-Way
HoConstr
MaxActSetSz
MaxCEPerCall
TcompEnaThr
MaxBTSLegs1
MaxBTSLegs2
MaxBTSLegs3
AggActLimit1
AggActLimit2
AggActLimit3
EnableSofter
EnableBTS
EnableSoft
AggrStr1
AggrStr2
AggrStr3
NumCandidate
XCTComp
SofterShuff
BTSShuffleC
SoftShuffle
August, 2007
Sector 1
C1
1
6
3
-14.5
3
2
2
35
43
51
Enable
Enable
Enable
0
-7
-9
10
3
3
3
3
Sector 2
C1
1
6
3
-14.5
3
2
2
35
43
51
Enable
Enable
Enable
0
-7
-9
10
3
3
3
3
Sector 3
C1
1
6
3
-14.5
3
2
2
35
43
51
Enable
Enable
Enable
0
-7
-9
10
3
3
3
3
Default
1
6
3
-14.5
3
3
2
35
43
51
0
0
0
-6 dB
-8 dB
-10 dB
10
4 dB
3 dB
0 dB
3 dB
RF200 - 190
Course RF200 Section III
Introduction
Introduction to
to
Optimization
Optimization Tools
Tools
August, 2007
RF200 - 191
Introduction To CDMA Field Tools: Topics

Q Two Important Concepts
The Department Store Analogy - Tops-Down vs. Bottoms-Up
The Aeronautical Analogy - Accident Investigation Resources
Q Survey of CDMA Field Tools
Mobile Tools
Handsets - Maintenance Displays
August, 2007
RF200 - 192
Department Store Analogy: Tops-Down, Bottoms-Up

ce
n
a
ur
s
In
Co
sts
Profits
TaLosses
xe
s
Management
Dis
trib
utio
n
Capital
Complex!!!
Lea
s
vice
r
e
S
ion
t
c
e
Sel
es
ing
s
Stocking Su
i
pp
ert
v
lations
e
R
lie
r
o
d
b
a
L
A
rs
Test Shopper
Simpler
Con
ven
ienc
Price
e
System
are Administration
w
t
f
o
S
TransProvisioning
mission
nce
Phone
e
r
e
f
r
Inte
alls
C
d
ppe
o
r
D
Switch CBSC
Simpler
Complex!!!
Data C
apture
PSTN TrunkingData
Analys
is
BTS
Neighbor Lists Configuration
Acces
s
Cov
erag
e
Failur
es
Field Tools
Some things are easier to measure from the customer side!

August, 2007
RF200 - 193
Aeronautical Analogy: Tools for Problem Investigation

Control & Parameters
11500
114.50
118.25
130.75
Messaging
11500
Aeronautical
Case
Flight Data Recorder
Cockpit Voice Recorder
CDMA Case
BTS
Temporal Analyzer Data
Layer 3 Message Files
To study the cause of an aeronautical accident, we try to recover the Flight Data
Recorder and the Cockpit Voice Recorder.
To study the cause of a CDMA call processing accident, we review data from the
Temporal Analyzer and the Layer 3 Message Files -- for the same reasons.
August, 2007
RF200 - 194
Sources of CDMA Data and Tools for Processing

HANDSET
CDMA NETWORK EQUIPMENT

Switch
SLM
CM
Switch Data
LPP
ENETlogs
LPP
pegs,
DMS-BUS
DTCs
CBSC
GPSR
TFU1
CDSU
CDSU
SBS
IOC
Vocoders
Selectors
Various
External
Analysis
Tools
BTS
IS-95/J-STD-8
Messages
GPSR
BSM
CDSU
CDSU
CDSU
CDSU
CDSU
CDSU
DISCO 1
DISCO
2
System
CDSU
Ch. Card
DISCO
TFU1
ACC
Txcvr A
Internal Messages
Txcvr B
RFFE A
RFFE B
Txcvr C RFFE C
IS-95/J-STD-008 Messages
Unix-based,
PC-based
Data Analysis
Post-Processing
Tools
Handset
Messages
PC-based
Mobile Data
Capture Tools
PC-based
Mobile Data
Post-Processing
Tools
Q CDMA optimization data flows from three places:

Switch
CDMA peripherals (CBSC & BTS)
Handset
Q Each stream of data has a family of software and hardware tools for
collection and analysis
August, 2007
RF200 - 195
Autonomous
Autonomous Data
Data Collection
Collection
By
By Stowaway
Stowaway Mobiles
Mobiles
August, 2007
RF200 - 196
Stowaway Mobiles
Q Some operators are using stowaway mobiles in courier vehicles
or public transport (under agreement, of course)
Q A typical installation includes:
a commercial data collection device by a manufacturer such as
ZKcelltest
two attached phones, one for collection and one as a modem
a PN scanner
a GPS receiver
Q The data collection begins anytime the vehicle is driven
Q Collected data is uploaded to a server on the system
Q The central server also provides post-processing functions via a
web interface, allowing remote users to examine data for their
areas
August, 2007
RF200 - 197
Autonomous
Autonomous Data
Data Collection
Collection
By
By Subscriber
Subscriber Handsets
Handsets
August, 2007
RF200 - 198
Using Autonomous Collection

Collection Server
software download
collected data upload
data management, analysis
BTS
PDSN/Foreign Agent
BTS
Backbone
Internet
Network
T SECURE TUNNELS T
VPNs
PDSN Authentication
Authorization
R-P Interface
Home Agent Accounting AAA
PSTN
t1
Switch
t1 v
BTS
SEL
t1
(C)BSC/Access Manager BTS
Q A Server downloads software to a large population of subscriber mobiles

Q Mobiles collect on custom profiles
all or groups of mobiles can be enabled/disabled
new triggers can be rapidly developed and downloaded when desired
Q Mobiles upload compacted packets to server driven by custom triggers
may be immediately if needed, or at low-traffic pre-programmed times
collected data can include location/GPS/call event/L3
messaging/timestamps/etc.
Q Server manages data, provides filtering and reporting
Q Performance optimizers use terminals and post-processing software
August, 2007
RF200 - 199
Advantages of Autonomous Collection

Q Mobile-reported data can be
location-binned
post-processing provides
visual identification of problem
areas
Q Collection can be rapidly enabled
per cell or area for immediate
investigation of problem reports
Q Requires less employee drive time
for collection
Q Customer mobiles cover area
more densely than drivetesters
Q Customer mobiles include inbuilding populations
Q Individual mobile identification can
be included with customer
permission for direct customer
service interaction
August, 2007
RF200 - 200
Current Issues in Autonomous Collection

Collection Server
software download
collected data upload
data management, analysis
BTS
PDSN/Foreign Agent
BTS
Backbone
Internet
Network
T SECURE TUNNELS T
VPNs
PDSN Authentication
Authorization
R-P Interface
Home Agent Accounting AAA
PSTN
t1
Switch
t1 v
BTS
SEL
t1
(C)BSC/Access Manager BTS
Q Requires extensive software capability to develop/manage

current progress is from specialty application consulting houses
Q Requires cooperation of handset vendor to effectively integrate software
onto handset platform
caution required to avoid negative call processing side-effects
Q Privacy issues involved if any user-specific data tracking
Q Additional network capacity required for large-scale reporting
August, 2007
RF200 - 201
Conventional
Conventional Field
Field Tools
Tools
August, 2007
RF200 - 202
CDMA Field Test Tools

Field Collection Tools using Handset Data
Qualcomm
Motorola
Andrew
MDM, CAIT
Agilent
Comarco
PN Scanners
Agilent
Berkeley
Varitronics
Andrew
Qualcomm
DTI
TouchWave
TouchWave
Ericsson
TEMS
Q There are many commercial CDMA field test tools

Q Characteristics of many test tools:
capture data from data ports on commercial handsets
log data onto PCs using proprietary software
can display call parameters, messaging, graphs, and maps
store data in formats readable for post-processing analysis
small and portable, easy to use in vehicles or even on foot
Q A few considerations when selecting test tools:
does it allow integration of network and mobile data?
Cost, features, convenience, availability, and support
new tools are introduced every few months - investigate!
August, 2007
RF200 - 203
Qualcomms MDM: Mobile Diagnostic Monitor

Q The Qualcomm Mobile Diagnostic
Monitor was the industrys first field
diagnostic tool
used industry-wide in the early
deployment of CDMA
pictures at right from Sprints first
1996-7 CDMA trials in Kansas City
Q Qualcomms Mobile Diagnostic Monitor
CDMA handset (customer provided)
Proprietary connecting cable
PC software for collection and field preanalysis
Temporal analyzer display mode
Messaging
August, 2007
RF200 - 204
Andrews Invex3G Tool

Q 100 MB ethernet connection to
PC
Q the eight card slots can hold
receivers or dual-phone cards
Q theres also room for two
internal PN scanners
Q Multiple Invex units can be
cascaded for multi-phone loadtest applications
Q Cards are field-swappable Users can reconfigure the unit
in the field for different tasks
without factory assistance
August, 2007
RF200 - 205
Touchwave Tools
Q The BlueRose platform can
manage multiple phones and
collect data
Internal processor
manages test operations
independently for standalone operation
Internal PCMCIA flash
card provides storage
An external PC can display
collected data during or
after data collection
August, 2007
RF200 - 206
Agilent Drive-Test Tools

Q Agilent offers Drive-Test tools
Serial interfaces for up to four
CDMA phones
A very flexible digital receiver
with several modes
Q PN Scanner
Fast, GPS-locked, can scan
two carrier frequencies
Q Spectrum Analyzer
Can scan entire 800 or 1900
mHz. Bands
Q Base-Station Over-Air Tester
(BOAT)
Can display all walsh channel
activity on a specific sector
Useful for identifying hardware
problems, monitoring
instantaneous traffic levels, etc.
Q Post-Processing tool: OPAS32
August, 2007
RF200 - 207
IS-95 Busy Sector

Snapshot of Walsh Usage
August, 2007
RF200 - 208
1xRTT Busy Sector

Walsh Code Usage
August, 2007
RF200 - 209
Comarco Mobile Tools

Q X-Series Units for more dataintensive collection activities
Multiple handsets can be
collected
Data is displayed and
collected on PC
Q LT-Series provides integrated
display and logging
Q "Workbench" Post-Processing
tool analyzes drive-test files
August, 2007
RF200 - 210
PN Scanners
Q Why PN scanners? Because phones cant
scan remaining set fast enough, miss
transient interfering signals
Q Berkeley Varitronics
high-resolution, GPS-locked
full-PN scan speed 26-2/3 ms.
2048 parallel processors for very fast
detection of transient interferors
Q Agilent (formerly Hewlett-Packard)
high resolution, GPS-locked
full-PN scan speed 1.2 sec.
Integrated with spectrum analyzer and
phone call-processing tool
Q Andrew
lower-cost, low-end solution
full-PN scan speed 6.3 sec.
integrated with phone & call-processing
data collection tool
high-end version also available using
Berkeley Scanner
August, 2007
RF200 - 211
Post-Processing Tools
Windcatcher
Analyzer
Interpreter
Post-Processing tools display drive-test files for detailed

analysis - Faster, more effective than studying data
playback with collection tools alone
Q Actix Analyzer
Imports/analyzes data from almost every brand of
drive-test collection tool
Q Andrew (formerly Grayson) Interpreter
Imports/analyzes data from Andrew Invex3G
Q Nortel RF Optimizer
Can merge/analyze drive-test and Nortel CDMA
system data
Q Xceed Technologies Windcatcher
Imports/analyzes data from almost every brand of
drive-test device
Q Xceed Technologies Vortex
Provides automated analysis of data from manual,
autonomous, and stand-alone sources
Q Verizon/Airtouch internal tool DataPro
August, 2007
Vortex
RF200 - 212
Drive-Testing
Some
Some General
General Guidelines
Guidelines
August, 2007
RF200 - 213
Safety Considerations
Q Dont worry for the companys loss due to your accidental death
Qualified and eager replacements have resumes on file
Were constantly buying more drive-test vehicles
We were going to replace that old drive-test equipment soon
Were not really sure we needed your last drive test, anyway
Your death will serve as a warning to others, so its not in vain
Q Its OK to be careful and continue living for your own sake if you wish!
Q Always start and stop drive test file collection in a safe place off the road
and out of traffic patterns
Set up a graph window, message window, etc., whose motion can
provide a quick-glance visual reassurance that collection is running OK
Q While on the road, do not attempt to start or stop files, open or close
windows, or review results - just glance occasionally for signs of activity
Q If the PC freezes, the power cord pops out, or any other problem occurs
while collecting, dont try to deal with it or correct it while driving
Just pull over to the next really safe place to assess and correct
August, 2007
RF200 - 214
Physical Considerations
Q Be sure the connections (power, phone, PC and GPS cables) are
secure so they wont dislodge during collection and distract you
Q Be sure the equipment is physically restrained so it wont go flying
around and hit you in case of a panic stop or sudden swerve
Q Some GPS antennas are not weatherproof. Try to avoid getting
them drenched in heavy rain
Q The GPS antennas should be mounted where they have a view of
the sky as unobstructed as possible
Q External PCS or Cellular antennas should not be mounted closer
than about 1 foot to each other or to GPS antennas to ensure
there is no significant electromagnetic interference or pattern
distortion
August, 2007
RF200 - 215
Operational Concerns
Q The ideal length for drive-test files is 30 minutes to an hour
Youd hate to lose bigger files in case the PC locks up!
Larger files are a hassle to move around, load, and analyze
When interesting call processing events occur, its nice if they are in
small files that can be easily processed and stored
Q Always make sure you have at least 2 or 3 GB of free hard drive space
before you start a new drive-test collection
Dont open other programs while collecting data - they can tie up all
your free space in swap files and cause a crash
Check your hard drive for errors and defragment it every week or so if
youre collecting and transferring big files
Q Dont retrace large parts of your travel path during a drive-test run
Its harder to distinguish what happened on each run when analyzing
drives that cruise the same road multiple times
Q Always stop the test call before you stop recording -- otherwise, postprocessing software may misinterpret calling events
August, 2007
RF200 - 216
Getting Location Data into Drive-Test Files

Q In order to be able to build maps from drive-test data, location
information must be imbedded in the data files while they are
collected in the field. Several methods for obtaining location data
have been popular:
Q GPS Global Positioning System
This is the least expensive and most popular source of location
information for drive-testing since 1992
Q Stored Vector Maps and position-recognition software
Commercial products take raw vehicle distance and direction
data and match it to a stored road database to deduce location
Bosch TravelPilot and other tools used this method
More expensive and troublesome than GPS, not popular today
Q LORAN
MF Loran transmissions are only reliable in some coastal areas
and are being phased out
August, 2007
RF200 - 217
GPS Basics
Q GPS (Global Positioning System) was funded and implemented by the US
military and serves both civilian and military users
approved military users use a high precision signal (C/A)
civilian users use a lower-precision component of the signal
GPS signals are spread-spectrum at 1.545 and 1.2 GHz.
Q Other Global Navigation Systems:
Europe: Galileo (not yet launched)
Russia: GLONASS (in poor repair)
Q GPS uses 21 active satellites and 3 parked spares, all in mid-level orbits
at about 10,000 KM
Hour-by-hour, 5 to 7 satellites are usually in view anywhere
Reception of four satellites is enough to fix determine location
Three satellites are enough if users elevation already known
GPS reception is often blocked in cities, under bridges, dense forests,
or wherever obstacles interrupt the signal path
Q Dead Reckoning is a method of supplementing GPS with independent
location information when GPS cant be received
Q Differential GPS is a technique adding independent corrections to
received GPS data for better accuracy. GPS civilian accuracy was
improved in May, 2000. DGPS hasnt been widely used since then
August, 2007
RF200 - 218
Dead-Reckoning Systems
Q Dead-reckoning systems normally use a combination of magnetic
compass and wheel rotation sensors to augment GPS
Q The manufacturers instructions should be followed for installation.
Major factors requiring attention are:
If used, Wheel sensors must be securely mounted to prevent
accidental breakaway while driving (major injury hazard)
Magnetic compasses should be located as far as possible from
magnetic field sources in or on the vehicle
example: mag-mount antennas
(experimentation is often required)
Calibration by actual test is required to achieve workable
accuracy for dead-reckoning systems
August, 2007
RF200 - 219
Drive-Tests: Phones
Maintenance
Maintenance Features
Features of
of
CDMA
CDMA Handsets
Handsets
August, 2007
RF200 - 220
Handsets as Tools: Simple but always Available!

Q Most CDMA handsets provide some form of maintenance display (Debug
Mode) as well as instrumentation access
all CDMA drive-test tools use handsets as their front-ends
Using the handset as a manual tool without Commercial Test Tools:
Q Enter the maintenance mode by special sequence of keystrokes
Q Displayed Parameters
PN Offset, Handset Mode, Received RF Level , Transmit Gain Adjust
Q Maintenance Display Applications
best serving cell/sector
simple call debugging (symptoms of weak RF, forward link
interference, etc.)
Q Handset Limitations during manual observation
no memory: real-time observations only; no access to messages or
call details; serving PN offset not updated during voice calls
August, 2007
RF200 - 221
Interpreting Samsung Maintenance Display:

Acquisition, Idle, and Access States
Display toggles between:
System Identifier (SID)
Network Identifier (NID)
Transmit
Gain Adjust,
db
Reference
PN Offset
System Protocol
Revision Level
Radio Configuration
(Idle mode = 0, 0)
August, 2007
Slot Cycle Index
0 - Pilot Channel Acquisition Substate

1 - Sync Channel Acquisition Substate
2 - MS Idle State
3 - System Access State
4 - Traffic Channel State
5,6,7 - various call service options
Processing State
Debug Screen
S04274 SI2 2
T-56 D070-04
P0060 CH0350
PR6 RC0 0Z11
V206T144L:02
Receive
Power,
dbm
Ec/Io, db
(primary PN only)
Carrier Freq.
(Channel #)
Packet Zone ID
RF200 - 222
Interpreting Samsung Maintenance Display:

Traffic Channel State
Transmit (RL)
Vocoder Rate
1 = 1/8
2 = 1/4
4 = 1/2
8 = Full
Transmit
Gain Adjust,
db
PN Offset
System Protocol
Revision Level
Service Option
Live Cumulative
FER
August, 2007
FCH
Receive (FL)
Vocoder Rate Walsh Code
0 - Pilot Channel Acquisition Substate

1 - Sync Channel Acquisition Substate
2 - MS Idle State
3 - System Access State
4 - Traffic Channel State
5,6,7 - various call service options
Processing State
Debug Screen
TE8 RE8 40 6
T-10 D070-04
P0060 CH0350
PR6 RC33 Z11
SO00003 G207
F001.54%L:02
Receive
Power,
dbm
Ec/Io, db
(primary PN only)
Carrier Freq.
(Channel #)
Packet Zone ID
Radio Configuration
(RC3, RC3 common)
RF200 - 223
Denso Maintenance Display

Charging Battery Voltage
Average Battery Voltage
System ID
Network ID
RF Channel Frequency
Digital PN Offset
Number of Bad Frames
Number of Good Frames
Base Station coordinates
Current status of Rake Fingers
Active Pilot Set
Candidate Pilot Set
August, 2007
D
CBV: 3957
ABV: 3954 ABT: 031
ARF: 0000 CCL: 01
SID: 04157
NID: 00001
CH: 0100 RSSI: 093
DPN: 084 TX:-46
BFRM:0000000968
TFRM:0000135712
FER:% 000.71
LT: 036:06:36
LG: -086:45:36
EC: -16 -63 -63
PN: 084 084 084
FNGLK: Y Y N
WLSH: 01 01 01
ACT: 084 484 096
-01 -01 200
CND: 220 332 200
200 332 NGH: 076
080 340 068 196
O56 320 220 316
344 488 196 200
392 124 128 084
224 008 084
Average Battery Temperature
Received Signal Strength

Estimated Transmitter
Power Output
Frame Erasure Rate, Percent
Neighbor Pilot Set
RF200 - 224
Sanyo SPC-4500 Maintenance Display

Q
Q
Q
Q
Q
Q
Q
Q
Q
August, 2007
Choose the following:

DISPLAY
OK
0
OK
Enter Code: 0 0 0 0 0 0
Debug Menu
SCREEN
OK
RF200 - 225
Sanyo SPC-4900 Maintenance Display

Call Proc. State
Q
Q
Q
Q
Q
##
040793
select MENU/OK button
scroll to save Phone #
select
August, 2007
PN offset
Receive
Power
Io
Channel
Frequency
RF200 - 226
The Motorola Q
Q Getting Into Maintenance Mode:
Enter # # 3 3 2 8 4 #
Press the green Talk button
A Field Test Mode screen will appear
Choose one:
A Call Status Screen <<< USE
(this is the main maintenance display)
B Field Test Menu
(this controls special test modes and
GPS/HDR settings)
C GPS data
(shows various GPS parameters)
D Debug Information
I/O register and error log display
Q Getting Out of Maintenance Mode:
Press EXIT at bottom of Field Test Mode screen
August, 2007
RF200 - 227
Maintenance Display on the Motorola Q:

The CDMA Parameters
Strongest Active Pilot

PN
Ec/Io (-)
Number of
Actives
Number of
Candidates
Strongest Neighbor Pilot

PN
Ec/Io (-)
Transmit Power, dbm
Receive Power, dbm
Current Service Option
CDMA 111
186
84
NA
EVDO 100
111
OPN
Carrier
Channel #
60 1 20 P 50
120 0 IDL CE
H N/A 0.00 0
4139 43 6 2 0
120 0x785B64D2 5
79 -77 -128 128 7
ACC 0 70.11.225.186
SID
August, 2007
Number of
Neighbors
Band:
P=PCS, C=800
NID
Call Processing
State
Reason Last
Call Ended
# dropped calls
# total calls
Avg. FER
RF200 - 228

CDMA Call Proc. States, Call End Reasons
8V 8K voice original
IL 8K loopback
8EV 8K EVRC
8S 8K SMS
13L 13K loopback
13S 13K SMS
8MO 8K Markov Old
DAT Data
8M 8K Markov New
13M 13K Markov New
13V 13K Voice
August, 2007
Call Processing States

CP CP Exit
RST CP Restart
RTC Restricted
PLT Pilot Acquisition
SYN Sync Acquisition
TIM Timing Change
BKS Background Sch
IDL Idle
OVD Overhead
PAG Paging
ORG Call Origination
SMS Short Message Svc
ORD Order Response
REG Registration
TCI Tfc Ch Initialization
WFO Waiting for Order
WFA Waiting for Answer
CON Conversation state
REL Release
NON No State
Last Call End Indicator

NI No Indication yet
MR Mobile Release
BR Base Sta. Release
TC Traffic Channel Lost
L2 Layer 2 Ack Fail
NC No Channel Assn Msg
N5 N5M failure
BS BS Ack failure
WO L3 WFO State Timeout
MP Max Probe Failure
PC Paging Channel loss
RR Reorder or Release on PCH
?? Unknown Condition
RF200 - 229

The EVDO Parameters
UATI
Carrier
Channel #
PN
HDR Session State
CDMA 111
186
84
NA
EVDO 100
111
OPN
60 1 20 P 50
120 0 IDL CE
H N/A 0.00 0
4139 43 6 2 0
120 0x785B64D2 5
79 -77 -128 128 7
ACC 0 70.11.225.186
Receive
Power, dbm
August, 2007
IP Address
RF200 - 230
Entering Maintenance Mode: Motorola StarTac

Contact your service provider to obtain your phones Master
Subscriber entity Lock (MSL). Then enter the following:
Q FCN 000000 000000 0 RCL You'll be prompted for your
MSL, enter it and press STO.
New prompts will appear, Press STO in response to
each prompt until no more appear. Dont delay continue quickly and enter:
Q FCN 0 0 * * T E S T M O D E STO
The display will briefly show US then just '.
Q Press 55#.
Step 1 will appear with its current setting displayed.
Press * to accept and move on to the next step. Repeat
for steps 2-8.
Q Step 9 (Option byte 2) is the only step requiring manual
changes. Enter 1 0 0 0 0 0 0 0 (The leftmost bit now set to
'1' is what enables test mode.)
Q Now press STO to accept the entry and exit back to the '
prompt.
Q Power off and back on.
Q You should now be in test mode!
August, 2007
RF200 - 231
August, 2007
RF200 - 232
Last Call Indicator

NI No Indication yet
MR Mobile Release
BR Base Sta. Release
TC Traffic Channel Lost
L2 Layer 2 Ack Fail
NC No Channel Assn Msg
N5 N5M failure
BS BS Ack failure
WO L3 WFO State Timeout
MP Max Probe Failure
PC Paging Channel loss
RR Reorder or Release on PCH
?? Unknown Condition
Battery
Local Time Condition
RX Power
Strongest Active
#
#
Channel
PN
Ec/Io Actives Neighbors Number
Strongest Neighbor
# Cand- Call Proc Last Call
Exit Reason
PN
Ec/Io idates
State
Rx Power Tx Power Last Call FER% # Drops
dbm
dbm (Io)
Current
# Calls
Service Option
SID
NID
Call Processing States ORG Call Origination
CP CP Exit
RST CP Restart
RTC Restricted
8V 8K voice original 13S 13K SMS
PLT Pilot Acquisition
IL 8K loopback
8MO 8K Markov Old SYN Sync Acquisition
TIM Timing Change
8EV 8K EVRC
DAT Data
Background Sch
8S 8K SMS
8M 8K Markov New BKS
IDL
13L 13K loopback
13M 13K Markov New OVD Idle
Overhead
13V
13K
Voice
PAG
Paging
August, 2007
RF200 v5.9 (c) 2007 Scott
Baxter
SMS
ORD
REG
TCI
WFO
WFA
CON
REL
NON
Short Message Svc

Order Response
Registration
Tfc Ch Initialization
Waiting for Order
Waiting for Answer
Conversation state
Release
RF200
- 233
No State
Motorola V120C Series

Q
Q
Q
Q
MENU 073887*
Enter 000000 for security code.
Scroll down to Test Mode.
Enter subscriber entity lock code
if required by your phone
Same maintenance display as

shown for Startac
August, 2007
RF200 - 234
Motorola V60C
Q MENU 073887*
Q Enter 000000 for security
code.
Q Scroll down to Test Mode.
Q Enter subscriber entity lock
code if required by your phone
Same maintenance display as
shown for Startac
August, 2007
RF200 - 235
Nokia 6185 Maintenance Display

Q Enter *3001#12345# MENU
Q Scroll down to Field test
Q Press Select
Q Scroll up to Enabled
Q Press OK
Q Power the phone off and on
Q You should now be in Field test mode
August, 2007
RF200 - 236
Novatel Merlin C201 1xRTT Data Card

Q Enter # # D E B U G to enter maintenance mode.
Q To exit, just click OK box in the Debug window.
August, 2007
RF200 - 237
Audiovox Thera Maintenance Mode Screens

How to enter
Debug Mode:
[ctrl] [D] [enter]
Advanced Usr Pwd:
##DEBUG [enter]
Protocol Statistics
August, 2007
RF200 - 238
Sierra 580 1xEV-DO Rev 0 Aircard

Q To enter the maintenance display,
hover your cursor over the
Connection Manager main
indicator window or the Start
button and type ##debug.
Q The Network, Network 2, and HDR tabs provide the most useful
information on the air interface. The other tabs provide details of the
packet operations and error counters.
August, 2007
RF200 - 239
Novatel S720 EV-DO Rev. A Aircard:

Entering Debug Mode
Q To enter the maintenance display, hover your PCs cursor over the
Connection Manager main indicator window or the Go button and
type ##debug.
August, 2007
RF200 - 240
Novatel S720 EV-DO Rev. A Aircard

Debug Display
August, 2007
RF200 - 241
RF200 Section IV
Multi-Carrier
Multi-Carrier Operation
Operation
and
and Its
Its Complications
Complications
August, 2007
RF200 - 242
A CDMA network with 5 carriers
August, 2007
RF200 - 243
Its A
Multi-Carrier/Multi-System/Multi-Manufacturer
World!
Q Systems are forced to use multiple carriers to achieve needed traffic

capacity
Its important that the traffic load be divided between carriers
Q Physically adjacent friendly systems often desire to allow seamless mobile
operation across their borders, although they use different carrier
frequencies
Q Even within one large network, seamless mobile operation is desired
across serving switch boundaries
Q These situations are not completely solved in the original IS-95 CDMA
vision, so additional standards documents and additional proprietary
processes provide the needed functionality
IS-95: hashing or GSRMs can distribute idle mobiles among carriers
IS-41 - provides intersystem handoffs and call delivery
Proprietary algorithms can distribute in-call traffic among carriers
RF tricks and network proprietary algorithms can support inter-carrier
handoff
Q Multi-Carrier Operation is a complex sport
August, 2007
RF200 - 244
Transitions at System Boundaries

IDLE
IDLE
IN-CALL
IN-CALL
Q Boundary types
between different operators
same frequency, different frequency, even different band
between different BSCs or Switches of Same Operator
same frequency, different frequency, even different band
between different carriers where number of carriers changes
same frequency, different frequency, even different band!
Q A reliable transition method must be planned for users in all
circumstances
all directions of approach
all modes of operation (idle, active voice call, dormant data session,
active data session)
August, 2007
RF200 - 245
Foundation for Transition Troubleshooting

Q Multi-carrier and intersystem boundary transitions are complex
relationships between mobile, air interface, and system
to solve problems, its necessary to understand the basic actions of
mobile and the system
this information comes from the standard, summarized in the next
few slides
Q The mobiles actions are generic, defined by the standards, and
simpler/more specific than the steps taken by the system
A thorough knowledge of the mobile side is the easiest-to-get
resource for general troubleshooting of problems
Q For in-call transition troubleshooting, the systems generic and proprietary
algorithms must also be understood
artificial proprietary trigger mechanisms and internal system order
communications and IS-41 implementation
this information comes from manufacturer documentation
trunking and networking between adjoining systems
this information comes from operators own network design
August, 2007
RF200 - 246
The
The Mobile
Mobile View:
View:
When
When Do
Do II Change
Change Frequencies?
Frequencies?
August, 2007
RF200 - 247
Multi-Carrier Operation:
Mobiles Change Frequencies. When/Why/How?
Finding the System
Idle Mode
Call Start
In-Call Operation
Q There are many situations where a mobile should change

frequency
Finding a new system when turning on in a new location
Crossing a boundary and entering a new system when in idle
mode
Beginning a call on a sector that has more than one carrier
Crossing a boundary and entering a new system when in a call
Q Fortunately, there are defined triggers for all of these situations
August, 2007
RF200 - 248
Finding the System
MRU
1025
650
25
125
250
175
384
100
375
675
625
825
PRL
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
Start at top
Of MRU and
Check until Look up found
A signal is Signal in PRL
found
And try to climb
To more preferred
Signal if available
August, 2007
RF200 - 249
Idle Mode
Channel List Message
50, 125, 175
Hash and go!
August, 2007
RF200 - 250
Idle Mode
Global Service
Redirection Message
ACCOLC:1111100000100000
GO TO CH. 225
If your ACCOLC is ON,
Go where they tell you!
August, 2007
RF200 - 251
Idle Mode
Neighbor List Message

F1 PN240
F1 PN168
F1 PN336
F1 PN500
F1 PN372
F1 PN232
F2 PN240
F2 PN272
F3 PN240
F2 PN474
Check neighbors on
Other frequencies during
Unused paging slots.
If stronger than current
Active, do idle mode
Handoff to new frequencuy
August, 2007
RF200 - 252
Idle Mode
50, 125, 175
Hash and go!
Global Service
Redirection Message
ACCOLC:1111100000100000
GO TO CH. 225
F1 PN240
F1 PN168
F1 PN336
F1 PN500
F1 PN372
F1 PN232
F2 PN240
F2 PN272
F3 PN240
F2 PN474
Check neighbors on
August, 2007
RF200 - 253
Call Start
Getting Started:
Mobile sends
Page Response or
Origination Message
System evaluates
Present loading on
Each carrier and
Prepares a traffic
Channel on the
Carrier it prefers.
System sends channel
Assignment message
To the mobile
Mobile goes to the
Frequency it is told
Nortel: MCTA
Lucent: Pooling
Motorola: Pooling
August, 2007
RF200 - 254
In-Call Operation
NORMAL SOFT HANDOFFS
Mobile monitors pilots
And sends PSMM to
Request handoffs
When it desires
No Frequency Changes
August, 2007
RF200 - 255
In-Call Operation
HARD HANDOFFS
Mobile cannot see signals
On other frequencies.
System must use special
traps to trigger
And decide handoffs:
Pilot Beacons
PILOT
DATABASE
August, 2007
RF200 - 256
In-Call Operation
HARD HANDOFFS
traps to trigger
Round-Trip Delay, or
Ec/Io and Quality Triggers
Border Cells
RTD rings
August, 2007
RF200 - 257
In-Call Operation
And sends PSMM to
Request handoffs
When it desires
HARD HANDOFFS
traps to trigger
Pilot Beacons
PILOT
DATABASE
Border Cells
RTD rings
August, 2007
RF200 - 258
Finding the System
MRU
1025
650
25
125
250
175
384
100
375
675
625
825
PRL
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
Idle Mode
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
XXX
Start at top
Of MRU and
Check until Look up found
A signal is Signal in PRL
found
And try to climb
To more preferred
Signal if available
50, 125, 175

Hash and go!
Global Service
Redirection Message
ACCOLC:1111100000100000
GO TO CH. 225
F1 PN240
F1 PN168
F1 PN336
F1 PN500
F1 PN372
F1 PN232
F2 PN240
F2 PN272
F3 PN240
F2 PN474
Check neighbors on
August, 2007
Call Start
Getting Started:
Mobile sends
Page Response or
Origination Message
System evaluates
Present loading on
Each carrier and
Prepares a traffic
Channel on the
Carrier it prefers.
System sends channel
Assignment message
To the mobile
Mobile goes to the
Frequency it is told
Nortel: MCTA
Lucent: Pooling
Motorola: Pooling
In-Call Operation
And sends PSMM to
Request handoffs
When it desires
HARD HANDOFFS
traps to trigger
Pilot Beacons
PILOT
DATABASE
Border Cells
RTD rings
RF200 - 259
Hard Handoffs
Q Soft Handoff is the preferred mode in CDMA. Its diversity provides
excellent reliability and resistance to fading.
Q Soft Handoff is possible only if all these conditions are true:
the mobile is a one-frequency-at-a-time device, so all sectors in
handoff must be on the same carrier frequency
on the network side, all the base stations involved must have
packet paths in backhaul to the BSC/access manager currently
being used by the mobile. If more than one BSC/access
manager is involved, special packet links are required between
them
all new base stations being added in handoff must accept the
call using its current frame offset (rarely a concern)
Q If any of these conditions cannot be met, then the handoff must be
hard i.e., the mobile must give up its current links and quickly
jump to the new link or links
Q Notice that if the new target sector is on a different frequency than
the mobiles current call, the mobile will not even see its pilot and
will not know to request a handoff!
August, 2007
RF200 - 260
Triggering Hard Handoffs in Traffic

Q Hard Handoffs during a mobiles call or data session can be
triggered by a variety of methods:
Pilot Beacon The mobile notices a rising pilot and sends a
Pilot Strength Measurement Message asking for handoff. The
system responds with an Extended Handoff Direction Message
with the Hard Handoff field enabled, and sending the mobile to
a different system or frequency.
Border-Cell Special Triggers Unknown to the mobile, it is now
using only one or more special sectors defined as border
sectors in the systems databases. Special tracking is going
on, either round-trip-delay measurement or Ec/Io reporting.
When the system decides the mobile has reached the trigger
conditions, it suddenly and without warning sends an Extended
Handoff Direction Message with the Hard Handoff field
enabled, sending the mobile to a different system or frequency
it is not unusual for the EHDM to list multiple target sectors
August, 2007
RF200 - 261
Hard Handoff Messaging

(Beacon Trigger)
BASE STATION
ACK. ORDER
EXTENDED HANDOFF
DIRECTION MSG.
NEW FORWARD TRAFFIC CH.

BASE STATION
ACK. ORDER
NEIGHBOR LIST
UPDATE MESSAGE.
IN-TRAFFIC SYS. PARAM.
MESSAGE (OPTIONAL)
August, 2007

PILOT STRENGTH MEAS.
MSG. (BEACON SEEN)
MOBILE STATION
ACK. ORDER
NEW REVERSE TRAFFIC CH.

HANDOFF COMPLETION
MESSAGE
MOBILE STATION
ACK. ORDER
RF200 - 262
Hard Handoff Messaging

(RTD Trigger)
EXTENDED HANDOFF
DIRECTION MSG.
NEW FORWARD TRAFFIC CH.

BASE STATION
ACK. ORDER
NEIGHBOR LIST
UPDATE MESSAGE.
IN-TRAFFIC SYS. PARAM.
MESSAGE (OPTIONAL)
August, 2007
MOBILE STATION
ACK. ORDER
NEW REVERSE TRAFFIC CH.

HANDOFF COMPLETION
MESSAGE
MOBILE STATION
ACK. ORDER
RF200 - 263
Hard Handoff in Traffic Messaging (1)

11/09/2002 00:07:55
MSG_TYPE: Extended Handoff Direction Message
USE_TIME: Yes
ACTION_TIME: 240 ms
HDM_SEQ: 3
SEARCH_INCLUDED: Yes

T_ADD: -9.0 dB
T_DROP: -11.0 dB
T_COMP: 2.5
T_TDROP: 2 sec
HARD_INCLUDED: Yes
FRAME_OFFSET: 5.00 ms
PRIVATE_LCM: No RESET_L2: Yes
RESET_FPC: Yes SERV_NEG_TYPE: Yes
NOM_PWR_EXT: No
NOM_PWR: 0 dB
NUM_PREAMBLE: 7
BAND_CLASS: 800 MHz Cellular Band
CDMA_FREQ: 384
ADD_LENGTH: 0
PILOT_PN: 360
PWR_COMB_IND: No
CODE_CHAN: 48
RESERVED: 0
August, 2007
Q Increasing RTD or perhaps a

PSMM with a Beacon listed has
alerted the system to the need for
the hard handoff
Q The EHDM at left is sent to the
mobile
Q Notice the Hard Included terms
like those normally seen when
setting up a traffic channel initially
Q Notice also the larger Srch_Win_A
and unusually high T_Add and
T_Drop
11/09/2002 00:07:55
RESERVED: 0
RF200 - 264
Hard Handoff in Traffic Messaging (2)

Q The mobile acknowledges upon arrival
on the new traffic channel by sending a
QcpCdmaLogMsgForTrafChan 11/09/2002 00:07:56
MSG_TYPE: Neighbor List Update Message
PILOT_INC: 6
NGHBR_PN: 348 NGHBR_PN: 354 NGHBR_PN: 390
NGHBR_PN: 408 RESERVED: 0
QcpCdmaLogMsgForTrafChan 11/09/2002 00:07:56

MSG_TYPE: In-Traffic System Parameters Message
SID: 1382 NID: 5
SRCH_WIN_R: 320 chips
T_ADD: -14.0 dB T_DROP: -16.0 dB
NGHBR_MAX_AGE: 0 P_REV: IS-2000 Revision 0
SOFT_SLOPE: 0 ADD_INTERCEPT: 0 dB DROP_INTERCEPT: 0 dB
PACKET_ZONE_ID: Base Station Does Not Support A Packet Data
Service Zone
EXTENSION: No RESERVED: 0
August, 2007
QcpCdmaLogMsgRevTrafChan 11/09/2002 00:07:56

MSG_TYPE: Handoff Completion Message
LAST_HDM_SEQ: 3 PILOT_PN: 360 RESERVED: 0
Q After arrival on the new

frequency and traffic channel,
the mobile is given a new
Neighbor List Update
Message
Q The mobile is also given new
system parameters including
more normal search windows
and handoff parameters
appropriate to the new
environment of the mobile
RF200 - 265
f1
August, 2007
W0 Pilot
w1 Paging
wa
Data
w32 Sync
wx Traffic
wy Traffic
wz Traffic
f1
f3
W0 Pilot
wa Traffic
wb Traffic
wc Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
IS-95
IS-95
IS-95
IS-95
f2
W0 Pilot
wa Traffic
wb Traffic
wc Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
f2
1xRTT
IS-95
IS-95
f1
W0 Pilot
w1 Paging
wa Traffic
wb Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
IS-95
W0 Pilot
wa Traffic
wb Traffic
wc Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
f3
f4
W0 Pilot
wa Traffic
wb Traffic
wc Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
IS-95
IS-95
W0 Pilot
wa Traffic
wb Traffic
wc Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
Basic Multi-Carrier
Operation
W0 Pilot
w1 Paging
wa Traffic
wb Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
W0 Pilot
w1 Paging
wa Traffic
wb Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
f2
f4
W0 Pilot
w1 Paging
wa Traffic
wb Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
f3
IS-95
W0 Pilot
w1 Paging
wa Traffic
wb Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
f4
W0 Pilot
w1 Paging
wa Traffic
wb Traffic
w32 Sync
wx Traffic
wy Traffic
wz Traffic
Many Network/Carrier Configurations are Possible!

Non-originating carriers
can carry more traffic!
Some Carriers may

support 1xRTT
IS-95
RF200 - 266
CDMA/Analog
CDMA/Analog Overlay
Overlay Considerations
Considerations
August, 2007
RF200 - 267
CDMA/AMPS Overlays: Idle CDMA Acquisition

CDMA Overlay
GSRM
GSRM
AMPS Existing System
Q System acquisition is primarily controlled by the mobile

dual-mode mobiles look for CDMA first, then AMPS if needed
Q Distant mobiles may notice weak CDMA signals beyond the edge
of CDMA coverage, and originate calls likely to drop
most systems transmit Global Service Redirection Messages
on all out-looking sectors to immediately force any distant
mobiles to reacquire AMPS system
hence no CDMA originations on outermost CDMA sectors!
However, still possible to soft-handoff into outer sectors
Q Most operators request handset manufacturers to add feature of
periodic rechecking by idle handsets seeking to acquire CDMA
August, 2007
RF200 - 268
CDMA/AMPS Overlays: Analog Handdown

CDMA Overlay
AMPS Existing System
Q CDMA mobiles approaching the edge of CDMA coverage must

hand down to AMPS
however, CDMA mobiles cannot see AMPS signals during
CDMA calls, and therefore will not request handoff
Q Methods for triggering CDMA-to-AMPS Handdown: the same ones
we considered for CDMA-CDMA intersystem handoff
beacon cells
bridge cells with RTD trigger
arbitrary Ec/Io thresholds on boundary sectors
Q Once a CDMA phone hands down to analog, it cannot be handed
back up during the same call (due to long CDMA acquisition time)
August, 2007
RF200 - 269
RF200
1xRTT
1xRTT Data
Data Introduction:
Introduction:
Radio
Radio Configurations,
Configurations,
Variable
Variable Length
Length Walsh
Walsh Codes
Codes
August, 2007
RF200 - 270
The Original IS-95 CDMA Code Channels

FORWARD CHANNELS
REVERSE CHANNELS
W0: PILOT
W32: SYNC
BTS
W1: PAGING
ACCESS
TRAFFIC
Wn: TRAFFIC
Q Existing IS-95A/JStd-008 CDMA uses the channels above for call setup and
traffic channels all call processing transactions use these channels
traffic channels are 9600 bps (rate set 1) or 14400 bps (rate set 2)
Q IS-2000 CDMA is backward-compatible with IS-95, but offers additional
radio configurations and additional kinds of possible channels
These additional modes are called Radio Configurations
IS-95 Rate Set 1 and 2 are IS-2000 Radio Configurations 1 & 2
August, 2007
RF200 - 271
1xRTT Code Channels, Rev. 0

REVERSE CHANNELS
FORWARD CHANNELS
F-Pilot
Same coding as IS-95B,

Backward compatible
Includes Power
Control Subchannel
F-Sync

Backward compatible
1 to 7
PAGING

Backward compatible
Access Channel
(IS-95B compatible)
Enhanced
Access Channel
0 to 8
F-BCH
0 to 3
F-QPCH
Quick Paging Channel
F-CPCCH
Common
Power Control Channel
How many 1
Possible:
1
0 to 4
BTS
0 to 7
0 to 7
Users:
0 to many
1
Broadcast Channel
F-CACH
Common
Assignment Channel
F-CCCH
Common
Control Channels
F-TRAFFIC
F-FCH
Forward
Traffic Channels
Fundamental Channel
Dedicated
Control Channel
0 or 1
F-DCCH
0 to 7
F-SCH IS-95B only Channels IS-95B only
0 to 2
F-SCH
Supplemental
Supplemental
Channels RC3,4,5
Common
Control Channel
R-Pilot 1
R-ACH or
R-EACH
R-CCCH 0 or 1
R-TRAFFIC
Reverse Fundamental
Channel (IS95B comp.)
Dedicated
Control Channel
Reverse
Supplemental Channel
R-FCH 1
R-DCCH 0 or 1
R-SCH 0 to 2
Q No more wasteful duplication

on I and Q means the 1xRTT
signal can hold about twice
as much information. The
extra capacity can allow
more voice users, or new
faster data transmission.
See Course 332 for more details.
August, 2007
RF200 - 272
Spreading Rates & Radio Configurations

Spreading
Rate
SR1
1xRTT
1 carrier
1.2288
MCPS
SR3
3xRTT
Fwd:
3 carriers
1.2288
MCPS
Rev:
3.6864
MCPS
Radio
Configuration
Forward Link
Data
Rates
Data
Rates
Radio
Configuration
Reverse Link
Required. IS-95B Compatible

No CDMA2000 coding features
RC1
9600
9600
RC1
Required. IS-95B Compatible

Compatible with IS-95B RS2

RC2
14400
14400
RC2
Compatible with IS-95B RS2

Quarter-rate convolutional or
Turbo Coding, base rate 9600
RC3
9600
RC3
Quarter rate convolutional or

Turbo coding; Half rate
convolutional or Turbo coding;
base rate 9600
RC4
Quarter rate convolutional or

RC5
Required. or 1/3 convolutional

or Turbo coding, base rate 9600
RC6
or convolutional or Turbo
encoding, base rate 14400
Half-rate convolutional or
RC4
Quarter-rate convolutional or
RC5
1/6 rate convolutional

RC6
Required. 1/3 rate convolutional

RC7
or 1/3 rate convolutional or

Turbo coding, base rate 14400
RC8
or 1/3 rate convolutional or

Turbo encoder, base rate 14400
August, 2007
RC9
153600
9600
9600
153600
307200
307200
14400
14400
230400
230400
9600
307200
9600
614400
14400
460800
14400
1036800
9600
307200
614400
14400
460800
1036800
RF200 - 273
SR1, RC1 9,600 bps F-FCH (IS-95-Compatible)

Orthogonal
Spreading
I
Short Code
Power
Control
Puncturing
Data Bits
+CRC &
Tail bits
8.6 kbps
BTS
1/2 rate
Conv Encoder
9.6 kbps
Symbol
Repetition
User Long
Code Mask
Pwr Ctrl
Bits
800 bps
Gain
Gain
PC 19.2 ksps
Punc
Long Code
Generator
800 bps
Power Ctrl
Decimator
19.2 ksps
August, 2007
Long Code
Decimator
Walsh 64
Generator
FIR
LPF
FIR
LPF
1228.8 kcps
1228.8 kcps
/W
1228.8 kcps
Same symbols go on both I and Q!
1228.8 kbps
Interleaver
Q
Short Code
RF200 - 274
SR1, RC2 14,400 bps F-FCH (IS-95-Compatible)

Orthogonal
Spreading
2 of 6
Data Bits
13.35 kbps
+CRC &
Tail bits
1/2 rate
Conv Encoder
14.4 kbps
Symbol
Repetition
Symbol
Puncturing
28.8 ksps
Pwr Ctrl
Bits
800 bps
Gain
Gain
PC 19.2 ksps
Punc
19.2 ksps
Long Code
Generator
August, 2007
Long Code
Decimator
FIR
LPF
FIR
LPF
1228.8 kcps
1228.8 kcps
800 bps
Power Ctrl
Walsh 64
Decimator
Generator
/W
1228.8 kcps
Same symbols go on both I and Q!
1228.8 kbps
Interleaver
User Long
Code Mask
BTS
I
Short Code
Power
Control
Puncturing
Q
Short Code
RF200 - 275
SR1, RC3 F-FCH (9,600 bps)

Complex
Scrambling
Power
Control
Puncturing
Full Rate
Data Bits
8.6 kbps
+CRC &
Tail bits
1/4 rate
Conv Encoder
9.6 kbps
Pwr Ctrl
Bits
800 bps
Gain
Gain
Interleaver
38.4 ksps
User Long
Code Mask
PC
Punc
38.4 ksps
BTS
Long Code
Generator
Long Code
Decimator
1228.8 kbps
/W/2
1228.8 kcps
Orthogonal
Spreading
19.2 ksps
I
Serial to
Parallel
800 bps
Power Ctrl
Decimator
August, 2007
+
-
FIR
LPF
1228.8 kcps
1228.8 kcps
Walsh 64
Generator
1228.8 kcps
19.2 ksps
Power control information

may be carried as shown
or on the F-DCCH
Doubled power efficiency,

but still only 64 walsh codes
I
Short Code
The
stream of
symbols
is divided
into two
parts:
one on
logical I
and
one on
logical Q
1228.8 kcps
Q
Short Code
+
+
FIR
LPF
1228.8 kcps
Complex scrambling
ensures that the
physical I and Q phase
planes contain equal
amplitudes at all times.
This minimizes the
peak-to-average power
levels in the signal.
RF200 - 276
SR1, RC4 F-FCH (9,600 bps)

Complex
Scrambling
Power
Control
Puncturing
Full Rate
Data Bits
8.6 kbps
+CRC &
Tail bits
1/2 rate
Conv Encoder
9.6 kbps
Pwr Ctrl
Bits
800 bps
Gain
Gain
Interleaver
19.2 ksps
User Long
Code Mask
BTS
PC
Punc
Long Code
Generator
19.2 ksps
Long Code
Decimator
1228.8 kbps
/W/2
1228.8 kcps
Orthogonal
Spreading
9.6 ksps
FIR
LPF
1228.8 kcps
1228.8 kcps
1228.8 kcps
9.6 ksps
Power control information

may be carried as shown
or on the F-DCCH
August, 2007
Serial to Walsh 128

Parallel Generator
800 bps
Power Ctrl
Decimator
Double the walsh codes,

but no better power efficiency.
I
Short Code
The
stream of
symbols
is divided
into two
parts:
one on
logical I
and
one on
logical Q
1228.8 kcps
Q
Short Code
+
+
FIR
LPF
1228.8 kcps
Complex scrambling
ensures that the
This minimizes the
RF200 - 277
SR1, RC3 F-SCH (153,600 bps)

Complex
Scrambling
1228.8 kcps
Orthogonal
Spreading
614.4 ksps
Payload
Data Bits
152.4 kbps
+CRC &
Tail bits
1/4 rate
Conv Encoder
153.6 kbps
Interleaver
614.4 ksps
Gain
User Long
Code Mask
614.4 ksps
BTS
Long Code
Generator
Long Code
Decimator
1228.8 kbps
/W/2
307.2 ksps
+
-
FIR
LPF
1228.8 kcps
1228.8 kcps
Serial to
Parallel
Walsh 4
Generator
1228.8 kcps
307.2 ksps
1228.8 kcps
Q
Short Code
The
stream of
symbols
is divided
into two
parts:
one on
logical I
and
one on
logical Q
August, 2007
I
Short Code
+
+
FIR
LPF
1228.8 kcps
Complex scrambling
ensures that the
This minimizes the
RF200 - 278
SR1, RC4 F-SCH (307,200 bps)

Complex
Scrambling
1228.8 kcps
Orthogonal
Spreading
614.4 ksps
Payload
Data Bits
304.8 kbps
+CRC &
Tail bits
1/2 rate
Conv Encoder
307.2 kbps
Interleaver
614.4 ksps
Gain
User Long
Code Mask
614.4 ksps
BTS
Long Code
Generator
Long Code
Decimator
1228.8 kbps
/W/2
307.2 ksps
+
-
FIR
LPF
1228.8 kcps
1228.8 kcps
Serial to
Parallel
Walsh 4
Generator
1228.8 kcps
307.2 ksps
1228.8 kcps
Q
Short Code
The
stream of
symbols
is divided
into two
parts:
one on
logical I
and
one on
logical Q
August, 2007
I
Short Code
+
+
FIR
LPF
1228.8 kcps
Complex scrambling
ensures that the
This minimizes the
RF200 - 279
The Famous Walsh Codes from IS-95 Days

WALSH CODES
Q 64 Magic Sequences, each 64 chips long

Q Each Walsh Code is precisely Orthogonal with
respect to all other Walsh Codes and their
opposites too!
its simple to generate the codes, or
theyre small enough to use from ROM
Unique Properties:
Mutual Orthogonality
EXAMPLE:
Correlation of Walsh Code #23 with Walsh Code #59
#23
#59
Sum
0110100101101001100101101001011001101001011010011001011010010110
0110011010011001100110010110011010011001011001100110011010011001
0000111111110000000011111111000011110000000011111111000000001111
Correlation Results: 32 1s, 32 0s: Orthogonal!!
August, 2007
#
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
---------------------------------- 64-Chip Sequence -----------------------------------------0000000000000000000000000000000000000000000000000000000000000000

0101010101010101010101010101010101010101010101010101010101010101
0011001100110011001100110011001100110011001100110011001100110011
0110011001100110011001100110011001100110011001100110011001100110
0000111100001111000011110000111100001111000011110000111100001111
0101101001011010010110100101101001011010010110100101101001011010
0011110000111100001111000011110000111100001111000011110000111100
0110100101101001011010010110100101101001011010010110100101101001
0000000011111111000000001111111100000000111111110000000011111111
0101010110101010010101011010101001010101101010100101010110101010
0011001111001100001100111100110000110011110011000011001111001100
0110011010011001011001101001100101100110100110010110011010011001
0000111111110000000011111111000000001111111100000000111111110000
0101101010100101010110101010010101011010101001010101101010100101
0011110011000011001111001100001100111100110000110011110011000011
0110100110010110011010011001011001101001100101100110100110010110
0000000000000000111111111111111100000000000000001111111111111111
0101010101010101101010101010101001010101010101011010101010101010
0011001100110011110011001100110000110011001100111100110011001100
0110011001100110100110011001100101100110011001101001100110011001
0000111100001111111100001111000000001111000011111111000011110000
0101101001011010101001011010010101011010010110101010010110100101
0011110000111100110000111100001100111100001111001100001111000011
0110100101101001100101101001011001101001011010011001011010010110
0000000011111111111111110000000000000000111111111111111100000000
0101010110101010101010100101010101010101101010101010101001010101
0011001111001100110011000011001100110011110011001100110000110011
0110011010011001100110010110011001100110100110011001100101100110
0000111111110000111100000000111100001111111100001111000000001111
0101101010100101101001010101101001011010101001011010010101011010
0011110011000011110000110011110000111100110000111100001100111100
0110100110010110100101100110100101101001100101101001011001101001
0000000000000000000000000000000011111111111111111111111111111111
0101010101010101010101010101010110101010101010101010101010101010
0011001100110011001100110011001111001100110011001100110011001100
0110011001100110011001100110011010011001100110011001100110011001
0000111100001111000011110000111111110000111100001111000011110000
0101101001011010010110100101101010100101101001011010010110100101
0011110000111100001111000011110011000011110000111100001111000011
0110100101101001011010010110100110010110100101101001011010010110
0000000011111111000000001111111111111111000000001111111100000000
0101010110101010010101011010101010101010010101011010101001010101
0011001111001100001100111100110011001100001100111100110000110011
0110011010011001011001101001100110011001011001101001100101100110
0000111111110000000011111111000011110000000011111111000000001111
0101101010100101010110101010010110100101010110101010010101011010
0011110011000011001111001100001111000011001111001100001100111100
0110100110010110011010011001011010010110011010011001011001101001
0000000000000000111111111111111111111111111111110000000000000000
0101010101010101101010101010101010101010101010100101010101010101
0011001100110011110011001100110011001100110011000011001100110011
0110011001100110100110011001100110011001100110010110011001100110
0000111100001111111100001111000011110000111100000000111100001111
0101101001011010101001011010010110100101101001010101101001011010
0011110000111100110000111100001111000011110000110011110000111100
0110100101101001100101101001011010010110100101100110100101101001
0000000011111111111111110000000011111111000000000000000011111111
0101010110101010101010100101010110101010010101010101010110101010
0011001111001100110011000011001111001100001100110011001111001100
0110011010011001100110010110011010011001011001100110011010011001
0000111111110000111100000000111111110000000011110000111111110000
0101101010100101101001010101101010100101010110100101101010100101
0011110011000011110000110011110011000011001111000011110011000011
0110100110010110100101100110100110010110011010010110100110010110
RF200 - 280
IS-95 Busy Sector

Snapshot of Walsh Usage
August, 2007
RF200 - 281
Walsh Codes in 1xRTT

2G VOICE AND DATA
One Symbol of Information
19,200 symbols/second
DATA
SYMBOLS
WALSH
CODE
1,228,800 walsh chips/second

64 chips of Walsh Code
Data Rates are different, but

Chip Rates must stay the same!
3G 153.6 kb/s DATA

One Symbol of Fast Data
307,200 symbols/second
DATA
SYMBOLS
WALSH
CODE
4 Chips of Walsh Code
August, 2007
1,228,800 walsh chips/second
RF200 - 282
Families of the Walsh Codes

WALSH
# 1-Chip
0 0
WALSH
# 2-Chips
0 00
1 01
WALSH
#
0
1
2
3
4-Chips
0000
0101
0011
0110
2x2 4x4
WALSH
#
0
1
2
3
4
5
6
7
8-Chips
00000000
01010101
00110011
01100110
00001111
01011010
00111100
01101001
8x8
WALSH
#
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
---- 16-Chips ------0000000000000000

0101010101010101
0011001100110011
0110011001100110
0000111100001111
0101101001011010
0011110000111100
0110100101101001
0000000011111111
0101010110101010
0011001111001100
0110011010011001
0000111111110000
0101101010100101
0011110011000011
0110100110010110
16x16
Walsh Code Names

W1232 = Walsh Code #12, 32 chips long.
Walsh Level Mapping

The Walsh Codes shown here are in logical
state values 0 and 1.
Walsh Codes also can exist as physical
bipolar signals. Logical zero is the signal
value +1 and Logical 1 is the signal value -1.
Mapping: Logical 0,1 > +1, -1 Physical
WALSH CODES
#
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
----------- 32-Chip Sequence ------------00000000000000000000000000000000

01010101010101010101010101010101
00110011001100110011001100110011
01100110011001100110011001100110
00001111000011110000111100001111
01011010010110100101101001011010
00111100001111000011110000111100
01101001011010010110100101101001
00000000111111110000000011111111
01010101101010100101010110101010
00110011110011000011001111001100
01100110100110010110011010011001
00001111111100000000111111110000
01011010101001010101101010100101
00111100110000110011110011000011
01101001100101100110100110010110
00000000000000001111111111111111
01010101010101011010101010101010
00110011001100111100110011001100
01100110011001101001100110011001
00001111000011111111000011110000
01011010010110101010010110100101
00111100001111001100001111000011
01101001011010011001011010010110
00000000111111111111111100000000
01010101101010101010101001010101
00110011110011001100110000110011
01100110100110011001100101100110
00001111111100001111000000001111
01011010101001011010010101011010
00111100110000111100001100111100
01101001100101101001011001101001
32x32
Q All Walsh codes can be built to any size from a

single zero by replicating and inverting
Q All Walsh matrixes are square -- same number
of codes and number of chips per code
August, 2007
WALSH CODES
#
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
---------------------------------- 64-Chip Sequence -----------------------------------------0000000000000000000000000000000000000000000000000000000000000000

0101010101010101010101010101010101010101010101010101010101010101
0011001100110011001100110011001100110011001100110011001100110011
0110011001100110011001100110011001100110011001100110011001100110
0000111100001111000011110000111100001111000011110000111100001111
0101101001011010010110100101101001011010010110100101101001011010
0011110000111100001111000011110000111100001111000011110000111100
0110100101101001011010010110100101101001011010010110100101101001
0000000011111111000000001111111100000000111111110000000011111111
0101010110101010010101011010101001010101101010100101010110101010
0011001111001100001100111100110000110011110011000011001111001100
0110011010011001011001101001100101100110100110010110011010011001
0000111111110000000011111111000000001111111100000000111111110000
0101101010100101010110101010010101011010101001010101101010100101
0011110011000011001111001100001100111100110000110011110011000011
0110100110010110011010011001011001101001100101100110100110010110
0000000000000000111111111111111100000000000000001111111111111111
0101010101010101101010101010101001010101010101011010101010101010
0011001100110011110011001100110000110011001100111100110011001100
0110011001100110100110011001100101100110011001101001100110011001
0000111100001111111100001111000000001111000011111111000011110000
0101101001011010101001011010010101011010010110101010010110100101
0011110000111100110000111100001100111100001111001100001111000011
0110100101101001100101101001011001101001011010011001011010010110
0000000011111111111111110000000000000000111111111111111100000000
0101010110101010101010100101010101010101101010101010101001010101
0011001111001100110011000011001100110011110011001100110000110011
0110011010011001100110010110011001100110100110011001100101100110
0000111111110000111100000000111100001111111100001111000000001111
0101101010100101101001010101101001011010101001011010010101011010
0011110011000011110000110011110000111100110000111100001100111100
0110100110010110100101100110100101101001100101101001011001101001
0000000000000000000000000000000011111111111111111111111111111111
0101010101010101010101010101010110101010101010101010101010101010
0011001100110011001100110011001111001100110011001100110011001100
0110011001100110011001100110011010011001100110011001100110011001
0000111100001111000011110000111111110000111100001111000011110000
0101101001011010010110100101101010100101101001011010010110100101
0011110000111100001111000011110011000011110000111100001111000011
0110100101101001011010010110100110010110100101101001011010010110
0000000011111111000000001111111111111111000000001111111100000000
0101010110101010010101011010101010101010010101011010101001010101
0011001111001100001100111100110011001100001100111100110000110011
0110011010011001011001101001100110011001011001101001100101100110
0000111111110000000011111111000011110000000011111111000000001111
0101101010100101010110101010010110100101010110101010010101011010
0011110011000011001111001100001111000011001111001100001100111100
0110100110010110011010011001011010010110011010011001011001101001
0000000000000000111111111111111111111111111111110000000000000000
0101010101010101101010101010101010101010101010100101010101010101
0011001100110011110011001100110011001100110011000011001100110011
0110011001100110100110011001100110011001100110010110011001100110
0000111100001111111100001111000011110000111100000000111100001111
0101101001011010101001011010010110100101101001010101101001011010
0011110000111100110000111100001111000011110000110011110000111100
0110100101101001100101101001011010010110100101100110100101101001
0000000011111111111111110000000011111111000000000000000011111111
0101010110101010101010100101010110101010010101010101010110101010
0011001111001100110011000011001111001100001100110011001111001100
0110011010011001100110010110011010011001011001100110011010011001
0000111111110000111100000000111111110000000011110000111111110000
0101101010100101101001010101101010100101010110100101101010100101
0011110011000011110000110011110011000011001111000011110011000011
0110100110010110100101100110100110010110011010010110100110010110
64x64
RF200 - 283
Walsh Code Trees and Interdependencies

W316 0110 0110 0110 0110
8
W3
0110 0110
16 0110
W11
W332 0110 0110 0110 0110 0110 0110 0110 0110

W1932 0110 0110 0110 0110 1001 1001 1001 1001
W1132 0110 0110 1001 1001 0110 0110 1001 1001
0110 1001 1001
W2732 0110 0110 1001 1001 1001 1001 0110 0110
W34 0110
W716 0110 1001 0110 1001
8
W7
0110 1001
16 0110
W15
W732 0110 1001 0110 1001 0110 1001 0110 1001

W2332 0110 1001 0110 1001 1001 0110 1001 0110
W1532 0110 1001 1001 0110 0110 1001 1001 0110
1001 1001 0110
W3132 0110 1001 1001 0110 1001 0110 0110 1001
W364
W3564
W1964
W5164
W1164
W4364
W2764
W5964
W764
W3964
W2364
W5564
W1564
W4764
W3164
W6364
Q Entire Walsh matrices can be built by replicating and inverting -- Individual

Walsh codes can also be expanded in the same way.
Q CDMA adds each symbol of information to one complete Walsh code
Q Faster symbol rates therefore require shorter Walsh codes
Q If a short Walsh code is chosen to carry a fast data channel, that walsh
code and all its replicative descendants are compromised and cannot be
reused to carry other signals
Q Therefore, the supply of available Walsh codes on a sector diminishes
greatly while a fast data channel is being transmitted!
Q CDMA2000 Base stations can dip into a supply of quasi-orthogonal codes
if needed to permit additional channels during times of heavy loading
August, 2007
RF200 - 284
Walsh Code Families and Exclusions

Q Consider a forward link supplemental
channel being transmitted with a data
W34
rate of 307,200 symbols/second
Each symbol will occupy 4 chips at
the 1x rate of 1,228,800 c/s.
A 4-chip walsh code will be used for
this channel
Q If Walsh Code #3 (4 chips) is chosen for
this channel:
Use of W34 will preclude other usage
of the following 64-chip walsh codes:
3, 35, 19, 51, 11, 43, 27, 59, 7, 39,
23, 55, 15, 47, 31, 63 -- all forbidden!
16 codes are tied up since the data is
being sent at 16 times the rate of
conventional 64-chip walsh codes
Q The BTS controller managing this sector
must track the precluded walsh codes
and ensure they arent assigned
WALSH CODES
0110
Which Walsh Codes get tied up by another?

Wxxyyties up every YYth Walsh Code starting with #XX.
August, 2007
#
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
---------------------------------- 64-Chip Sequence -----------------------------------------0000000000000000000000000000000000000000000000000000000000000000

0101010101010101010101010101010101010101010101010101010101010101
0011001100110011001100110011001100110011001100110011001100110011
0110011001100110011001100110011001100110011001100110011001100110
0000111100001111000011110000111100001111000011110000111100001111
0101101001011010010110100101101001011010010110100101101001011010
0011110000111100001111000011110000111100001111000011110000111100
0110100101101001011010010110100101101001011010010110100101101001
0000000011111111000000001111111100000000111111110000000011111111
0101010110101010010101011010101001010101101010100101010110101010
0011001111001100001100111100110000110011110011000011001111001100
0110011010011001011001101001100101100110100110010110011010011001
0000111111110000000011111111000000001111111100000000111111110000
0101101010100101010110101010010101011010101001010101101010100101
0011110011000011001111001100001100111100110000110011110011000011
0110100110010110011010011001011001101001100101100110100110010110
0000000000000000111111111111111100000000000000001111111111111111
0101010101010101101010101010101001010101010101011010101010101010
0011001100110011110011001100110000110011001100111100110011001100
0110011001100110100110011001100101100110011001101001100110011001
0000111100001111111100001111000000001111000011111111000011110000
0101101001011010101001011010010101011010010110101010010110100101
0011110000111100110000111100001100111100001111001100001111000011
0110100101101001100101101001011001101001011010011001011010010110
0000000011111111111111110000000000000000111111111111111100000000
0101010110101010101010100101010101010101101010101010101001010101
0011001111001100110011000011001100110011110011001100110000110011
0110011010011001100110010110011001100110100110011001100101100110
0000111111110000111100000000111100001111111100001111000000001111
0101101010100101101001010101101001011010101001011010010101011010
0011110011000011110000110011110000111100110000111100001100111100
0110100110010110100101100110100101101001100101101001011001101001
0000000000000000000000000000000011111111111111111111111111111111
0101010101010101010101010101010110101010101010101010101010101010
0011001100110011001100110011001111001100110011001100110011001100
0110011001100110011001100110011010011001100110011001100110011001
0000111100001111000011110000111111110000111100001111000011110000
0101101001011010010110100101101010100101101001011010010110100101
0011110000111100001111000011110011000011110000111100001111000011
0110100101101001011010010110100110010110100101101001011010010110
0000000011111111000000001111111111111111000000001111111100000000
0101010110101010010101011010101010101010010101011010101001010101
0011001111001100001100111100110011001100001100111100110000110011
0110011010011001011001101001100110011001011001101001100101100110
0000111111110000000011111111000011110000000011111111000000001111
0101101010100101010110101010010110100101010110101010010101011010
0011110011000011001111001100001111000011001111001100001100111100
0110100110010110011010011001011010010110011010011001011001101001
0000000000000000111111111111111111111111111111110000000000000000
0101010101010101101010101010101010101010101010100101010101010101
0011001100110011110011001100110011001100110011000011001100110011
0110011001100110100110011001100110011001100110010110011001100110
0000111100001111111100001111000011110000111100000000111100001111
0101101001011010101001011010010110100101101001010101101001011010
0011110000111100110000111100001111000011110000110011110000111100
0110100101101001100101101001011010010110100101100110100101101001
0000000011111111111111110000000011111111000000000000000011111111
0101010110101010101010100101010110101010010101010101010110101010
0011001111001100110011000011001111001100001100110011001111001100
0110011010011001100110010110011010011001011001100110011010011001
0000111111110000111100000000111111110000000011110000111111110000
0101101010100101101001010101101010100101010110100101101010100101
0011110011000011110000110011110011000011001111000011110011000011
0110100110010110100101100110100110010110011010010110100110010110
RF200 - 285
Forward Link Walsh Codes in 1xRTT
This way of arranging Walsh codes is called bit reversal order. It shows each
Walsh codes parents and children. Remember, we cannot use any Walsh code if
another Walsh code directly above it or below it is in use.
4 chips
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
16 chips
76.8
ksps
76,800
sps
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
31 Code#
38.4k
38,400
sps
15
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
32 chips
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
Sync
Pilot
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging 7
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging 3
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging 5
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
PCH 6
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
PCH 2
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
PCH 4
19.2k
19.2k
19.2k
19.2k
19,200
sps
64 chips
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 286
August, 2007
76.8
ksps
76.8
ksps
8 chips
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH
307.2 ksps
F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
IS-95 Today Typical Usage:
Pilot, Paging Sync, up to 61 Voice Users
But if the users are highly mobile, forward power may exhaust at typically 30-40 users.
In fixed-wireless or stadium type applications, all walsh codes may be usable.
4 chips
76.8
ksps
76.8
ksps
76.8
ksps
76,800
sps
16 chips
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
31 Code#
38.4k
38,400
sps
15
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
32 chips
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Sync
Pilot
19,200
sps
64 chips
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 287
August, 2007
76.8
ksps
76.8
ksps
8 chips
Code#
Code#
76.8
ksps
76.8
ksps
???????
Traffic Channels
Voice or Data
9.6k/14.4k
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH
307.2 ksps
F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
Mixed IS-95 / 1xRTT RC3 Voice Typical Usage:

FCHs of 1xRTT RC3 users consume less power, so more total users are possible than in
IS-95. The BTS will probably have enough forward power to carry calls on all 61 walsh codes!
4 chips
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
16 chips
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
31 Code#
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Sync
Pilot
64 chips
RC1,2,3 Voice
38,400
sps
15
32 chips
19,200
sps
??
F-FCHs mixed
76,800
sps
76.8
ksps
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 288
August, 2007
76.8
ksps
76.8
ksps
8 chips
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH
307.2 ksps
F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
A Not-too-Desirable 1xRTT RC3 State:
1 F-SCH, 27 Voice IS-95/1xRTT RC3 Users, 16 Active Data Users

The data users can rapidly share the one F-SCH for 153 kb/s peak, ~9Kb/s avg. user rates.
But so many active data users F-FCHs consume a lot of capacity, reduce number of voice users!
Code#
4 chips
0
8 chips
Code#
F-SCH
153.6 ksps
F-SCH
153.6 ksps
F-SCH
153.6 ksps
10
16 chips
14
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
F-SCH
153.6 ksps
F-SCH
153.6 ksps
F-SCH
153.6 ksps
153,600
sps
15
Code#
76.8
ksps
76.8
ksps
13
11
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
25
21
13
29
19
11
27
23
15
31 Code#
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
F-FCHs 9.6k
F-FCHs 9.6k
RC3 Voice
RC3 Voice
RC3 Data
38,400
sps
Code#
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Sync
Pilot
64 chips
F-FCHs 9.6k
76,800
sps
38.4k
38.4k
17
Code#
38.4k
38.4k
38.4k
30
38.4k
14
38.4k
22
38.4k
38.4k
26
38.4k
10
38.4k
18
38.4k
76.8
ksps
38.4k
28
76.8
ksps
38.4k
12
76.8
ksps
38.4k
20
76.8
ksps
38.4k
76.8
ksps
38.4k
24
38.4k
32 chips
38.4k
16
76.8
ksps
307200
sps
F-SCH
307.2 ksps
12
Code#
F-SCH 153K RC3
Wasteful, since many of these users are

not actively sending or receiving data
76.8
ksps
Code# 0
19,200
sps
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
Code#
F-SCH
307.2 ksps
Code#
Code#
Code#
QPCH
QPCH
QPCH
TX Div PIlot
128 chips
9,600
4,800
2,400
sps
August, 2007
RF200 - 289
A Better 1xRTT RC3 BTS Dynamic State:
1 F-SCH, 39 IS-95/1xRTT RC3 Voice Users, 4 Active+12 Dormant Data Users

But it takes seconds to move various data users from Dormant to Active!
Data users will get 153 kb/s peak, ~9 kb/s average, but latency will be high.
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
16 chips
76.8
ksps
8 chips
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
F-FCHs
Data
RC3 Voice
38.4k
38.4k
38.4k
RC3 Voice
38.4k
38.4k
38.4k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
RC3 Voice
64 chips
Sync
Pilot
F-FCHs 9.6k
31 Code#
38.4k
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
F-FCHs 9.6k
38,400
sps
15
32 chips
19,200
sps
F-FCHs 9.6k
76,800
sps
76.8
ksps
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 290
August, 2007
F-SCH
307.2 ksps
4 chips
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH 153K RC3

F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
Slightly Improved 1xRTT RC3 BTS Dynamic State:

1 F-SCH, 37 IS-95/1xRTT RC3 Voice Users, 4 Active+12 Control-Hold Data Users
Instead of sending 16 data users to Dormant State, let them time-share 2 F-DCCH for
Control Hold state. Data users will get 153 kb/s peak, ~9 kb/s average, good latency.
Not yet available or implemented.
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
16 chips
76.8
ksps
8 chips
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
F-FCHs
Data
F-DCCHs
RC3 Voice
38.4k
38.4k
38.4k
RC3 Voice
38.4k
38.4k
38.4k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
RC3 Voice
64 chips
Sync
Pilot
F-FCHs 9.6k
31 Code#
38.4k
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
F-FCHs 9.6k
38,400
sps
15
32 chips
19,200
sps
F-FCHs 9.6k
76,800
sps
76.8
ksps
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 291
August, 2007
F-SCH
307.2 ksps
4 chips
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH 153K RC3

F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
Heavy Data 1xRTT RC3 BTS Dynamic State:
2 F-SCH, 21 IS-95/1xRTT RC3 Voice Users, 4 Active+12 Control-Hold Data Users

16 data users time-share 2 F-DCCH for Control Hold state. Data users get 38.4, 76.4,
or 153.6 kb/s peak, ~19 kb/s average, good latency. But only 21 voice users!
4 chips
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
F-FCHs
Data
F-DCCHs
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
64 chips
Sync
Pilot
RC3 Voice
31 Code#
38.4k
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
RC3 Voice
38,400
sps
15
32 chips
F-FCHs 9.6k
76,800
sps
16 chips
19,200
sps
F-FCHs 9.6k
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 292
August, 2007
76.8
ksps
76.8
ksps
8 chips
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
76.8
ksps
11
6
11
76.8
ksps
19
26
3
14
3
10
13
6
29
18
5
10
13
2
9
2
1
12
21
28
153,600
sps
4
5
12
F-SCH
153.6 ksps
8
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
0
F-SCH
307.2 ksps
F-SCH
307.2 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH 153K RC3

F-SCH 153K RC3
Code#
3
1
2
0
Code#
1xRTT Busy Sector

Walsh Code Usage
August, 2007
RF200 - 293
1xRTT RC3 BTS with Different User Data Rates:
3 F-SCH, 37 IS-95/1xRTT RC3 Voice Users, 4 Active+12 Control-Hold RC3 Data Users
16 data users time-share 2 F-DCCH for Control Hold state.
Data users get 38.4, 76.4, or 153.6 kb/s peak, ~9 kb/s average, good latency.
4 chips
14
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
7
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
22
14
30
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
F-FCHs
Data
F-DCCHs
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
RC3 Voice
RC3 Voice
64 chips
Sync
Pilot
RC3 Voice
38.4k
27
26
38.4k
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
F-FCHs 9.6k
38.4k
11
38.4k
19
10
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
9,600
4,800
2,400
sps
128 chips
RF200 - 294
August, 2007
3
18
32 chips
F-FCHs 9.6k
31 Code#
29
2
19,200
sps
F-FCHs 9.6k
38,400
sps
15
13
23
21
28
F-SCH
38K
F-SCH
38K
10
16 chips
8 chips
Code#
Code#
12
Code#
Code#
5
12
76.8
ksps
8
0
25
20
76.8
ksps
F-SCH
153.6 ksps
9
4
76.8
ksps
F-SCH
153.6 ksps
17
24
76.8
ksps
F-SCH
153.6 ksps
1
8
76,800
sps
76.8
ksps
76.8
ksps
11
76.8
ksps
Code#
16
Code# 0
Code#
13
15
9
2
153,600
sps
F-SCH
153.6 ksps
F-SCH
F-SCH
153.6 ksps
76K
RC3
F-SCH
153.6 ksps
Code#
7
3
5
1
4
0
Code#
307200
sps
F-SCH
307.2 ksps
F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
1xRTT RC4 Voice Only:
Wow! 118 users! But RC4 users F-FCHs consume as much power as old IS-95 calls.
BTS may run out of forward power before the all walsh codes are used.
4 chips
76.8
ksps
76.8
ksps
76.8
ksps
8 chips
16 chips
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
31 Code#
38.4k
38,400
sps
15
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
32 chips
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
Sync
Pilot
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19,200
sps
64 chips
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
???????
9,600
4,800
2,400
sps
F-FCHs 9.6k
RC4 Voice
76,800
sps
76.8
ksps
QPCH
QPCH
QPCH
TX Div PIlot
128 chips
RF200 - 295
August, 2007
76.8
ksps
76.8
ksps
F-FCHs 9.6k
RC4 Voice
F-FCHs 9.6k
RC4 Voice
F-FCHs 9.6k
RC4 Voice
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH
307.2 ksps
F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
1xRTT RC4 Voice and Data:
1 F-SCH, 80 1xRTT RC4 Voice Users, 4 Active+12 Control-Hold RC4 Data Users
16 data users time-share 2 F-DCCH for Control Hold state. Data users will get 38.4,
76.4, 153.6 or 307.2 kb/s peak, ~19 kb/s average, good latency. But fwd power may exhaust!
F-SCH
307.2 ksps
4 chips
76.8
ksps
76.8
ksps
76.8
ksps
8 chips
16 chips
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
31 Code#
38.4k
38,400
sps
15
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
32 chips
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
Sync
Pilot
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19,200
sps
64 chips
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
9,600
4,800
2,400
sps
F-FCHs
F-DCCHs
????
76,800
sps
76.8
ksps
QPCH
QPCH
QPCH
TX Div PIlot
128 chips
RF200 - 296
August, 2007
76.8
ksps
76.8
ksps
F-FCHs 9.6k
RC4 Voice
F-FCHs 9.6k
RC4 Voice
F-FCHs 9.6k
RC4 Voice
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
Code#
Code#
76.8
ksps
76.8
ksps
23
30
Code#
76.8
ksps
7
14
15
76.8
ksps
27
22
7
14
11
6
11
6
19
26
3
10
3
10
13
2
29
18
5
12
13
2
9
4
21
28
153,600
sps
8
5
12
F-SCH
153.6 ksps
0
25
20
F-SCH
153.6 ksps
F-SCH
153.6 ksps
9
4
F-SCH
153.6 ksps
F-SCH
153.6 ksps
Code#
F-SCH
153.6 ksps
17
24
7
6
1
8
3
2
Code#
16
Code# 0
5
1
4
0
Code#
307200
sps
F-SCH 307K RC4

F-SCH
307.2 ksps
Code#
3
1
2
0
Code#
Mature 1xRTT Mixed-Mode Voice and Data:

1 RC3/RC4 Shared F-SCH, 20 RC3 Voice Users, 38 RC4 Voice Users,
3 Active+12 Control-Hold RC3 and RC4 Data Users
16 data users time-share 2 F-DCCH for Control Hold state. Data users will get
38.4, 76.4, 153.6 or 307.2 kb/s peak, ~9 or 19 kb/s average, good latency. Fwd power tight!
Code#
4 chips
0
16 chips
F-SCH
153.6 ksps
F-SCH
153.6 ksps
F-SCH
153.6 ksps
12
10
14
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
76.8
ksps
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
38.4k
21
13
29
19
11
27
23
15
31 Code#
63
31
47
15
55
23
39
7
59
27
43
11
51
19
35
3
61
29
45
13
53
21
37
5
57
25
41
9
49
17
33
1
62
30
46
14
54
22
38
6
58
26
42
10
50
18
34
2
60
28
44
12
52
20
36
4
56
24
40
8
48
16
32
0
F-FCHs 9.6k
RC3 Voice
RC3 Voice
38,400
sps
Code#
F-FCHs 9.6k
????
19,200
sps
RC3 Voice
127
63
95
31
111
47
79
15
119
55
87
23
103
39
71
7
123
59
91
27
107
43
75
11
115
51
83
19
99
35
67
3
125
61
93
29
109
45
77
13
117
53
85
21
101
37
69
5
121
57
89
25
105
41
73
9
113
49
81
18
97
33
65
1
126
62
94
30
110
46
78
14
118
54
86
22
102
38
70
6
122
58
90
26
106
42
74
10
114
50
82
18
98
34
66
2
124
60
92
28
108
44
76
12
116
52
84
20
100
36
68
4
120
56
88
24
104
40
72
8
112
48
80
16
96
32
64
0
QPCH
QPCH
QPCH
TX Div PIlot
128 chips
F-FCHs
F-DCCHs
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Paging
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
19.2k
Sync
Pilot
64 chips
F-FCHs 9.6k
76,800
sps
38.4k
38.4k
25
Code#
38.4k
38.4k
ns
io
38.4k
17
38.4k
38.4k
76.8
ksps
38.4k
30
76.8
ksps
t
na
14
76.8
ksps
38.4k
22
76.8
ksps
38.4k
76.8
ksps
15
38.4k
26
76.8
ksps
153,600
sps
38.4k
10
Code#
11
38.4k
18
38.4k
13
38.4k
28
38.4k
12
307200
sps
F-SCH
153.6 ksps
38.4k
20
F-SCH
153.6 ksps
38.4k
38.4k
24
38.4k
32 chips
38.4k
16
5
F-SCH
153.6 ksps
38.4k
Code# 0
bi
m
Co
Or
Code#
F-SCH 153K RC3

F-SCH
or
ksps RC4
F-SCH307.2
307K
8 chips
Code#
Code#
F-SCH
307.2 ksps
Code#
Code#
F-FCHs 9.6k
RC4 Voice
August, 2007
F-FCHs 9.6k
RC4 Voice
Code#
F-FCHs 9.6k
RC4 Voice
9,600
4,800
2,400
sps
RF200 - 297
1xRTT
1xRTT Data
Data Operation
Operation
August, 2007
RF200 - 298
1xRTT Data Call States

Q IS-95 CDMA channels and structure were conceived to provide
circuit-switched voice service. Typical hold time of a voice call is
roughly two minutes.
Q 1xRTT packet data traffic comes in many types, ranging from very
bursty scattered packets to heavy almost-continuous data flows
when large files are involved
Q If steady code channels were assigned to data users for their
entire sessions, the capacity of the system would be largely
wasted during the periods when a user transmits no data
Q The Media Access Control layer of the 1xRTT protocol stack
manages the use of the air interface, defining several states for
user sessions and managing the transitions between states based
on user activity and quality of service (QOS) concerns.
August, 2007
RF200 - 299
Current and Future 1xRTT Call States

Active
T_active or
Release
Initialization
Traffic channel
Exists
Service Option
Connected
Control Channel
Exists
Control Channel
exists
Control Hold
(DCCH)
Packet Service Packet Service

Request
Deactivated
Suspended
T_suspend
T_hold
PPP Terminated
Release Sent!
Service Option
Connected
Control Channel Exists
Have New Data
to send!
Null
Reconnect
August, 2007
Dormant
PPP Terminated
Release Sent!
RF200 - 300
MAC States Implemented in 1xRTT Phase 0

IP
Session
Internet
VPNs
Selector/
Channel
PPP
Svc Cfg (RLP)
Element
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
(C)BSC/
Access Manager
PDSN/
Foreign BTS
Agent
R-P Interface
SEL
t1
CE
Dormant
timer
exceeded
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
(C)BSC/
Access Manager
August, 2007
F-TRAFFIC
F-FCH
ACTIVE
F-SCH
exit timer:
a few seconds
SCH driven
by traffic
Mobile has
data for
System
PDSN/
Foreign BTS
Agent
R-P Interface
SEL
PAGING
R-TRAFFIC
R-FCH
R-SCH
SCH driven
by traffic
System has
data for
Mobile
Origination
Release
Normal
Internet
VPNs
State
General
Page
DORMANT
Page
Response
R-ACH
exit timer: minutes, hours

between data bursts
t1
intermittent
RF200 - 301
Future MAC States in 1xRTT Phase 1

IP
Session
Internet
VPNs
Selector/
Channel
PPP
Svc Cfg (RLP)
Element
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
(C)BSC/
Access Manager
Internet
VPNs
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
(C)BSC/
Access Manager
Internet
VPNs
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
(C)BSC/
Access Manager
Internet
VPNs
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
(C)BSC/
Access Manager
August, 2007
PDSN/
Foreign BTS
Agent
R-P Interface
SEL
t1
CE
PDSN/
Foreign BTS
Agent
R-P Interface
SEL
t1
State
F-TRAFFIC
F-FCH
ACTIVE
F-SCH
exit timer:
a few seconds
SCH driven
by traffic
F-TRAFFIC
F-DCCH
t1
PAGING
R-P Interface
SEL
SUSPENDED
(Optional State)
exit timer: a few seconds
between data bursts
CE
PDSN/
Foreign BTS
Agent
R-TRAFFIC
R-DCCH
intermittent
exit timer: a few seconds

very fast return to active state
R-P Interface
SEL
R-SCH
SCH driven
by traffic
(Optional State)
CE
PDSN/
Foreign BTS
Agent
CONTROL
HOLD
R-TRAFFIC
R-FCH
PAGING
R-EACH
R-CCCH
intermittent
DORMANT
R-EACH
exit timer: minutes, hours

between data bursts
R-CCCH
t1
intermittent
RF200 - 302
Mobile-Originated Packet Data Call Flow

PAGING CHANNEL
ACCESS CHANNEL
ORIGINATION MESSAGE
BASE STATION
ACK. ORDER
PROBE INFORMATION
EXTENDED CHANNEL
ASSIGNMENT MSG
LAYER 2 HANDSHAKE
LAYER 2 HANDSHAKE
BASE STATION
ACK. ORDER
STATUS REQUEST
MESSAGE
SERVICE CONNECT
MESSAGE
August, 2007
MOBILE STATION
ACK. ORDER
STATUS RESPONSE
MESSAGE
SERVICE CONNECT
COMPLETE MESSAGE
RF200 - 303
Packet Session Origination Messaging (1)

Q The mobile sends an
origination message
on the Access
Channel
Q The Access Probe
Information record
shows the time when
the message was
sent and the power
level
MSG_LENGTH: 43 octets PD: P_REV_IN_USE >= 6
ESN: D:25405233216 H:FE4FDA40 IMSI_CLASS: 0
IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0
IMSI_S: 5402304897 AUTH_MODE: 1 AUTHU: 147354 RANDC: 120
COUNT: 0 LAC_PADDING: 0 ACTIVE_PILOT_STRENGTH: -4.50 dB
PILOT_STRENGTH: -14.50 dB ACCESS_HO_EN: No
ACCESS_ATTEMPTED: No MOB_TERM: Yes
SLOT_CYCLE_INDEX: 2.56 MOB_P_REV: IS-2000 Revision 0
SERVICE_OPTION: Standard: 144kbps PacketData, Internet or ISO Protocol
PM: Yes DIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: No NUM_FIELDS: 4
CHARi: # 7 7 7 NAR_AN_CAP: No
PACA_REORIG: User Directed Origination RETURN_CAUSE: Normal Access
MORE_RECORDS: No ENCRYPTION_SUPPORTED: Basic Encryption Supported
PACA_SUPPORTED: No NUM_ALT_SO: 0 DRS: Yes UZID_INCL: No
CH_IND: Fundamental Channel SR_ID: 1 OTD_SUPPORTED: No
QPCH_SUPPORTED: Yes ENHANCED_RC: Yes
FOR_RC_PREF: 3 REV_RC_PREF: 3 FCH_SUPPORTED: Yes
DCCH_SUPPORTED: No GEO_LOC_INCL: No REV_FCH_GATING_REQ: Yes RESERVED: 0
Access Probe Sequence Number: 1 Access Probe Number: 1 Access Channel Number: 0
PN Randomization delay: 0 Sequence Backoff: 0 Probe Backoff: 0
Persistence Tests Performed: 1 Rx Power: -77.9 Tx Power (Est): 4.9 Tx Gain Adjust: 0
August, 2007
RF200 - 304

MSG_LENGTH: 13 octets PD: P_REV_IN_USE < 6 MSG_TYPE: Order Message
ADDR_TYPE: ESN ADDR_LEN: 4 octets ESN: D:25405233216 H:FE4FDA40
MSG_TYPE: Extended Channel Assignment Message
ADDR_TYPE: ESN ADDR_LEN: 4 octets ESN: D:25405233216 H:FE4FDA40
RESERVED_1: 0 ADD_RECORD_LEN: 15 octets
RESERVED_2: 0 FREQ_INCL: Yes BAND_CLASS: 800 MHz Cellular Band
CDMA_FREQ: 384 BYPASS_ALERT_ANSWER: Yes
GRANTED_MODE: MS use Service Configuration of default Multiplex Option and
Transmission Rates
DEFAULT_CONFIG: Reserved FOR_RC: RC 3 REV_RC: RC 3
FRAME_OFFSET: 7.50 ms ENCRYPT_MODE: Encryption Disabled
FPC_SUBCHAN_GAIN: 0.0 dB RLGAIN_ADJ: 0 dB NUM_PILOTS: 0 Pilots
CH_IND: Fundamental Channel CH_RECORD_LEN: 7 octets
FPC_FCH_INIT_SETPT: 7.000 dB FPC_FCH_FER: 0.5% - 10% (in units of 0.5%)
PILOT_PN: 44 ADD_PILOT_REC_INCL: No PWR_COMB_IND: No
CODE_CHAN_FCH: 33 QOF_MASK_ID_FCH: 0 3X_FCH_INFO_INCL: No
REV_FCH_GATING_MODE: No 3XFL_1XRL_INCL: No RESERVED: 0
August, 2007
Q After receiving the

probe, the base station
transmits a Base Station
Acknowledgment order
on the Paging Channel
this tells the mobile
not to transmit more
probes
Q After the system sets up
the traffic channel for
the call, the Extended
Channel Assignment
Message gives the
mobile the channel
details
Operating mode
Band, Frequency
Walsh Code
Radio
Configurations
RF200 - 305

22:18:00.491 QcpCdmaLogMsgForTrafChan


channel. It starts sending good
blank frames of its own on the
reverse traffic channel.
RESERVED: 0
The mobile station acknowledges the base stations acknowledgment, as part of a

Pilot Strength Measurement Message it needs to send anyway for a handoff it
wants. The fundamental channels are working, so its time to negotiate the service
option to be used.
August, 2007
RF200 - 306

MSG_TYPE: Status Request Message
QUAL_INFO_TYPE: None
QUAL_INFO_LEN: 0 octets NUM_FIELDS: 2
RECORD_TYPE: Channel Configuration
Capability Information
RECORD_TYPE: Reserved
Q The system asks for the

mobiles Channel
Configuration Capability
Information
August, 2007
MSG_LENGTH: 44 octets MSG_TYPE: Status Response Message
ACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: No ENCRYPTION: Encryption Disabled
QUAL_INFO_TYPE: None QUAL_INFO_LEN: 0 octets
RECORD_TYPE: Extended Multiplex Option Information
RECORD_LEN: 24 octets NUM_MO_FOR_FCH: 2 MO_FOR_FCH: 1
RS1_9600_FOR: RS1_4800_FOR: RS1_2400_FOR: RS1_1200_FOR:
MO_FOR_FCH: 2
RESERVED: 0 NUM_MO_REV_FCH: 2 MO_REV_FCH: 1
RS1_9600_REV: RS1_4800_REV: RS1_2400_REV: RS1_1200_REV:
RESERVED: 0 MO_REV_FCH: 2
RESERVED: 0 NUM_MO_FOR_DCCH: 0 NUM_MO_REV_DCCH: 0
NUM_MO_FOR_SCH: 2 FOR_SCH_ID: 0 MO_FOR_SCH: 2337
FOR_SCH_ID: 0 MO_FOR_SCH: 2081 NUM_MO_REV_SCH: 2
REV_SCH_ID: 0 MO_REV_SCH: 2321 REV_SCH_ID: 0 MO_REV_SCH: 2065
RESERVED: 0
RECORD_TYPE: Channel Configuration Capability Information
RECORD_LEN: 9 octets OTD_SUPPORTED: No FCH_SUPPORTED: Yes
DCCH_SUPPORTED: No FOR_SCH_SUPPORTED: Yes FOR_SCH_LEN: 2
RC1: No RC2: No RC3: Yes RC4: Yes RC5: No RC6: No
FOR_SCH_NUM: 1 FOR_TURBO_SUPPORTED: No
FOR_CONV_SUPPORTED: Yes
FOR_MAX_CONV_BLOCK_SIZE: Rate Set 1: 3048, Rate Set 2: 4584
FOR_FRAME_40_SUPPORTED: No FOR_FRAME_80_SUPPORTED: No
FOR_MAX_RATE: 9.6 kbps or 14.4 kbps REV_SCH_SUPPORTED: Yes
REV_SCH_LEN: 1 RC1: No RC2: No RC3: Yes REV_SCH_NUM: 1
REV_TURBO_SUPPORTED: No REV_CONV_SUPPORTED: Yes
REV_MAX_CONV_BLOCK_SIZE: Rate Set 1: 3048, Rate Set 2: 4584
REV_FRAME_40_SUPPORTED: No REV_FRAME_80_SUPPORTED: No
REV_MAX_RATE: 9.6 kbps or 14.4 kbps STS_SUPPORTED: No
3X_CCH_SUPPORTED: No RESERVED: 0 RESERVED: 0
RF200 - 307

MSG_LENGTH: 46 octets MSG_TYPE: Service Connect Message
USE_TIME: No ACTION_TIME: 0 ms SERV_CON_SEQ: 0
RESERVED: 0 RECORD_TYPE: Service Configuration
RECORD_LEN: 30 octets FOR_MUX_OPTION: 1 REV_MUX_OPTION: 1
RESERVED: 0
RESERVED: 0
NUM_CON_REC: 1 RECORD_LEN: 12 octets CON_REF: 1
SERVICE_OPTION:
Standard: 144kbps PacketData, Internet or ISO Protocol
FOR_TRAFFIC: SO Uses Primary Traffic On FTC
REV_TRAFFIC: SO Uses Primary Traffic On RTC
RESERVED: -- -- 6 65 193 178 153 76 0 134 53 2 72 72
RESERVED: 96 40 18 34 67 0 19 5 132 67 7 10 0
Q The system proposes the

service connection
parameters and the mobile
accepts
ENCRYPTION: Encryption Disabled RESERVED: 0
SERV_CON_SEQ: 0 RESERVED: 0
August, 2007
RF200 - 308
Session Transition to Dormant State

NORMAL OPERATION CONTINUES,

BUT NO DATA HAS BEEN SENT
IN EITHER DIRECTION
DURING THE DORMANT TIMER PERIOD
RELEASE -- NORMAL
RELEASE NO REASON
SYNC CHANNEL
PAGING CHANNEL
THE MOBILE READS THE CONFIGURATION

MESSAGES. THE SYSTEM IS UNCHANGED,
SO NO NEW REGISTRATION IS NEEDED.
August, 2007
RF200 - 309
Session Return from Dormant State

Due to Data at System
PAGING CHANNEL
ACCESS CHANNEL
GENERAL PAGE MESSAGE

PAGE RESPONSE MESSAGE
BASE STATION
ACK. ORDER
PROBE INFORMATION
CHANNEL ASSIGNMENT
MESSAGE
FORWARD FUNDAMENTAL
TRAFFIC CHANNEL
REVERSE FUNDAMENTAL
TRAFFIC CHANNEL
LAYER 2 HANDSHAKE
LAYER 2 HANDSHAKE
BASE STATION
ACK. ORDER
STATUS REQUEST
MESSAGE
SERVICE CONNECT
MESSAGE
MOBILE STATION
ACK. ORDER
STATUS RESPONSE
MESSAGE
SERVICE CONNECT
COMPLETE MESSAGE
THE DATA CALL IS BACK IN ACTIVE STATE.

NORMAL MESSAGING AND DATA TRANSFER
CONTINUE.
August, 2007
RF200 - 310
Session Return from Dormant State

Due to Data at Mobile
PAGING CHANNEL
ACCESS CHANNEL
ORIGINATION MESSAGE
BASE STATION
ACK. ORDER
PROBE INFORMATION
CHANNEL ASSIGNMENT
MESSAGE
FORWARD FUNDAMENTAL
CHANNEL
REVERSE FUNDAMENTAL
CHANNEL
LAYER 2 HANDSHAKE
LAYER 2 HANDSHAKE
BASE STATION
ACK. ORDER
STATUS REQUEST
MESSAGE
SERVICE CONNECT
MESSAGE
MOBILE STATION
ACK. ORDER
STATUS RESPONSE
MESSAGE
SERVICE CONNECT
COMPLETE MESSAGE
THE DATA CALL IS BACK IN ACTIVE STATE.

NORMAL MESSAGING AND DATA TRANSFER
CONTINUE.
August, 2007
RF200 - 311
PDSN/Foreign Agent
Forward Link SCH Scheduling

FCH or
data
FCH +
R-P
Interface
Buffer
SCH?
My F-SCH
Data Rate
BTS
CE
PCF SEL
t1
(C)BSC/Access Manager
BTSC
Wireless
Mobile Device
Q The main bottleneck is the forward link itself: restricted by available

transmitter power and walsh codes
Q Each connected data User has a buffer in the PDSN/PCF complex
When waiting data in the buffer exceeds a threshold, the PDSN/PCF asks
the BTS for an F-SCH. Its data rate is limited by:
Available BTS forward TX power; available walsh codes; competition
from other users who also need F-SCHs; and mobile capability
When the buffer is nearly empty, the SCH ends; FCH alone
Occupancy timers and other dynamic or hard-coded triggers may apply
QOS (Quality of Service) rules also may be implemented, giving
preference to some users and some types of traffic
August, 2007
RF200 - 312
Forward Link Supplemental Channel Burst

FORWARD FUNDAMENTAL
TRAFFIC CHANNEL
EXTENDED SUPPL. CHAN.
ASSIGNMENT MSG.
REVERSE FUNDAMENTAL
TRAFFIC CHANNEL
MOBILE STATION
ACK. ORDER
FORWARD
SUPPLEMENTAL
CHANNEL
DATA BURST
August, 2007
RF200 - 313
Forward Supplemental Channel Assignment

Mobile: Watch
Walsh Code 2
Starting in 320 ms
For 1000 ms.
PN 168
BTS
W2
F-SCH
W23
F-FCH
Mobile: Watch
Walsh Code 2
Starting in 320 ms
For 1000 ms.
Supplemental
Channel Burst
ESCAM
Supplemental
Channel Burst
ESCAM
W1
NSASPPCKGKSAKGKSAKKNKGGKSKPG
NSASPPCK
W32
SYNC SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
W0
PILOT
TIME
ACCESS CHANNEL
R-FCH
August, 2007
RF200 - 314
Forward Link Supplemental

Channel Burst Messaging
MSG_TYPE: Extended Supplemental Channel
Assignment Message

START_TIME_UNIT: 0 ms REV_SCH_DTX_DURATION: 200 ms
USE_T_ADD_ABORT: No USE_SCRM_SEQ_NUM: No
ADD_INFO_INCL: Yes
FPC_PRI_CHAN: Forward Fundamental Channel inner loop
estimation
REV_CFG_INCLUDED: No NUM_REV_SCH: 0
FOR_CFG_INCLUDED: Yes FOR_SCH_FER_REP: Yes
NUM_FOR_CFG_RECS: 0 FOR_SCH_ID: 0 SCCL_INDEX: 0
FOR_SCH_NUM_BITS_IDX: RC 1,3,4,6,7=744; RC 2,5,8,9=1128;
12 CRC bits
NUM_SUP_SHO: 0 PILOT_PN: 12
ADD_PILOT_REC_INCL: No CODE_CHAN_SCH: 2
QOF_MASK_ID_SCH: 0 (rot 256 bit)
NUM_FOR_SCH: 1 FOR_SCH_ID: 0
FOR_SCH_DURATION: 2560 ms
FOR_SCH_START_TIME_INCL: Yes
FOR_SCH_START_TIME: 28 SCCL_INDEX: 0
FPC_INCL: Yes FPC_MODE_SCH: 1
FPC_SCH_INIT_SETPT_OP: FPC_SCH_INIT_SETPT has Offset
value of initial F-SCH Eb/Nt setpoint
FPC_SEC_CHAN: 0 NUM_SUP: 1 SCH_ID: 0
FPC_SCH_FER: 0.5% - 10% (in units of 0.5%)
FPC_SCH_INIT_SETPT: 3.500 dB
FPC_SCH_MIN_SETPT: 2.000 dB
FPC_SCH_MAX_SETPT: 8.000 dB
FPC_THRESH_SCH_INCL: No RPC_INCL: No
3X_SCH_INFO_INCL: No CCSH_INCLUDED: No
FOR_SCH_CC_INCL: No REV_SCH_CC_INCL: No
RESERVED: 0
August, 2007
22:39:42.250, Record 224546, QcpCdmaLogMsgRevTrafChan

RF200 - 315
Reverse Link Supplemental Channel Burst

FORWARD FUNDAMENTAL
TRAFFIC CHANNEL

ASSIGNMENT MSG.
REVERSE FUNDAMENTAL
TRAFFIC CHANNEL
REQUEST MSG.
MOBILE STATION
ACK. ORDER
REVERSE
SUPPLEMENTAL
CHANNEL
DATA BURST
August, 2007
RF200 - 316
Reverse Supplemental Channel Assignment

Mobile: Send
Walsh Code 1
Starting in 320 ms
For 1000 ms.
W23
PN 168
BTS
Mobile: Send
Walsh Code 1
Starting in 320 ms
For 1000 ms.
ESCAM
F-FCH
ESCAM
W1
NSASPPCK
W32
SYNC SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
W0
PILOT
TIME
ACCESS CHANNEL
R-FCH
SCRM
SCRM
Supplemental
Channel Burst
R-SCH
System: I need to
Send you the
Following blocks:
August, 2007
Supplemental
Channel Burst
System: I need to
Send you the
Following blocks:
RF200 - 317
Reverse Link Supplemental

Channel Burst Messaging
MSG_TYPE: Extended Supplemental Channel
Assignment Message

START_TIME_UNIT: 0 ms
REV_SCH_DTX_DURATION: 200 ms
USE_T_ADD_ABORT: No USE_SCRM_SEQ_NUM: No
ADD_INFO_INCL: Yes
FPC_PRI_CHAN: Forward Fundamental Channel inner
loop estimation
REV_CFG_INCLUDED: Yes NUM_REV_CFG_RECS: 0
REV_SCH_ID: 0
REV_WALSH_ID: Forward Dedicated Control Channel
inner loop estimation
REV_SCH_NUM_BITS_IDX: RC 1,3,5=1512; RC 2,4,6=2280;
12 CRC bits
NUM_REV_SCH: 1 REV_SCH_ID: 0
REV_SCH_DURATION: Reserved
REV_SCH_START_TIME_INCL: Yes
REV_SCH_START_TIME: 30
REV_SCH_NUM_BITS_IDX: RC 1,3,5=1512; RC 2,4,6=2280;
12 CRC bits
FOR_CFG_INCLUDED: No NUM_FOR_SCH: 0
FPC_INCL: No RPC_INCL: Yes
RPC_NUM_SUP: 0 SCH_ID: 0
RLGAIN_SCH_PILOT: 1.000000 dB
3X_SCH_INFO_INCL: No
CCSH_INCLUDED: No
FOR_SCH_CC_INCL: error: 1 bit field, 0 bits available
REV_SCH_CC_INCL: error: no bits available
August, 2007
MSG_TYPE: Supplemental Channel Request Message
SIZE_OF_REQ_BLOB: 3 bytes
REQ_BLOB: 228
REQ_BLOB: 39
REQ_BLOB: 255
USE_SCRM_SEQ_NUM: No
REF_PN: 132 PILOT_STRENGTH: -3.00 dB NUM_ACT_PN: 2
ACT_PN_PHASE: PN:304 + 0 chips ACT_PILOT_STRENGTH: -14.50 dB
ACT_PN_PHASE: PN:372 + 22 chips ACT_PILOT_STRENGTH: -21.00 dB
NUM_NGHBR_PN: 0
REF_PILOT_REC_INCL: No PILOT_REC_INCL: No PILOT_REC_INCL: No
RF200 - 318
Protocol Stack and

Connection Setup Scenarios
Q After setup of the basic traffic channels for a mobile session, the
appropriate TCP-IP connections must be established
Q The following figures show the protocol stack from the perspective
of the 1xRTT system, as well as from a more general TCP-IP view.
Q Two types of connections are available:
Simple IP connections use a single PDSN to allow mobile
connection to the internet, but the connection is not portable
and cannot be maintained after handoff to a different system
Mobile IP connections use a Home Agent PDSN as the anchor
for the internet connection, and a Foreign Agent PDSN to
forward the packets to the mobile in its local system. If the
mobile hands off to a different system, the new systems
Foreign Agent PDSN can set up a new tunneling relationship
with the Home Agent PDSN to continue the session.
August, 2007
RF200 - 319
Simple IP and Mobile IP 1x Networks

Simple IP Network View
PDSN
IP/VPN
AAA
PSTN
t1
SW
BSC R-P
t1
Mobile IP Network View
v SEL
Backbone
IP/VPN
PDSN HA
BTS
t1
AAA
PSTN
CE
USER
t1
SW
PDSN
FA
BSC R-P
t1
v SEL
BTS
t1
CE
USER
Q In Simple IP, a single PDSN manages the users connection to the outside
IP/VPN world
Q In Mobile IP, two PDSNs are used.
One is the Home Agent PDSN, providing a non-changing point of
connection to the outside world IP/VPN.
The other is the Foreign Agent PDSN, connected to the BSC of the
mobiles current system.
The FA PDSN establishes a tunnel with the HA PDSN for forwarding
the mobiles packets
Q If the mobile hands into a different system, the new systems FA PDSN
will establish its own tunnel to the HA PDSN, allowing the mobiles
session to continue.
August, 2007
RF200 - 320
1xRTT Wireless Data Protocol Stack
Protocol Stack View

MOBILE
1x
L3
Sig
Other Pkt Voice Ckt

L3 Data Svc Data
Sig Svc
Svc
IS95
L2
Sig
1x
L2
Sig
Other Pkt
L2 Data
Sig
L2
Inst 3
L3 Sig
Inst 2
User Pkts
SRBP
SRLP
Null
L2
Ckt
Data
L2
Inst 1
Voc Bits
RBP
RLP
PLDCF MUX / QoS

Physical - RLAC
PLDCF
MUX/QOS PLDCF PLICF LAC
IS95
L3
Sig
APPL
SYSTEM
IS95
L3
Sig
1x
L3
Sig
Other Pkt Voice Ckt

L3 Data Svc Data
Sig Svc
Svc
IS95
L2
Sig
1x
L2
Sig
Other Pkt
L2 Data
Sig
L2
Inst 3
L3 Sig
SRBP
Inst 2
User Pkts
SRLP
Null
L2
Ckt
Data
L2
Inst 1
Voc Bits
RBP
RLP
PLDCF MUX / QoS

Physical - RLAC
Frames
August, 2007
RF200 - 321
Simple IP Protocol Stack

Application
HL
Protocols
HTTP
Applications
HL
Protocols
HTTP
CDMA
Upper Layers
TCP
UDP
TCP
UDP
IP
IP
PPP
MAC
MAC
CDMA
PL
CDMA
PL
Mobile
Station
R-P
R-P
PL
PL
AN
LAC
AN
LAC
Link
Layer
PL
Gateway Routers
PPP
IP
Link
Layer
PL
End Host
(Internet,
RAN
intranet)
Logical (software) connections established
PDSN
HA
User Data: application/bearer and control
August, 2007
RF200 - 322
Mobile IP Protocol Stack Application Data

Applications
UL
Protocols
(HTTP)
Applications
UL
Protocols
(HTTP)
CDMA U.L.
TCP
UDP
TCP
UDP
PPP
PPP
LAC
MAC
CDMA
PL
CDMA
PL
Mobile
Station
R-P
R-P
PL
PL
AN
MAC
RAN
AN
LAC
IP
Link
Layer
PL
Gateway Routers
IP
IP
Link Link
Layer Layer
PL
PDSN
PL
HA
Logical conn. Mobile--RAN
Gateway Routers
IP
Link
Layer
PL
End Host
(Internet,
intranet)
Logical connections MobilePDSN for PPP

Logical connections MobileEnd Host
Mobile IP User Application Data
August, 2007
RF200 - 323
Mobile IP Protocol Stack Control Signalling
Mobile
IP
UDP
Mobile IP
Mobile
IP
UDP
UDP
IP
IP
IP
PPP
PPP
LAC
LAC
MAC
MAC
CDMA
PL
CDMA
PL
Mobile
Station
R-P
R-P
PL
PL
RAN
Link
Layer
Link
Layer
PL
PL
PDSN
HA
Mobile IP control signalling
August, 2007
RF200 - 324
Simple IP Setup (PAP Authentication) (1)

Q The mobile sends an LCP Configure Request message to the PDSN. This
starts setup of the datalink layer connection between mobile and PDSN.
Q The PDSN sends an LCP Configure Request PAP authentication
seeking the mobiles datalink layer and authentication information.
Q The mobile sends an LCP Configure Acknowledgement PAP
authentication message to the PDSN, containing configuration information
the PDSN uses to set up the connection.
Q The PDSN sends an LCP Configure Acknowledgement PAP
authentication to the mobile, acknowledging it received the message.
Q The Mobile-PDSN datalink layer connection is now configured; now set
up the networklayer connection.
Q Mobile requests AAA authentication from the PDSN, sending a PAP
Authentication Request message.
Q The PDSN receives the message and sends an Access Request message
to the Foreign AAA server, including the mobile subscribers
MSID@domain (also called an NAI) and Password to the AAA.
Q The Foreign AAA server sends an Access Accept message to the PDSN,
providing a dynamic IP address assignment for the mobile.
August, 2007
RF200 - 325
Simple IP Setup (PAP Authentication) (2)

Q The PDSN receives the Access Accept message and sends a PAP
authentication Acknowledgement to the mobile.
Q The mobile sends an IPCP Configure Request to the PDSN with its IP
address set to 0.0.0.0 (the mobile will be assigned an IP address for the
packet data session by the PDSN/AAA)
Q The PDSN assigns an dynamic IP address to the mobile by sending an
IPCP Configure Nak message.
Q The mobile receives the IPCP Configure Nak message sends an IPCP
Configure request message to the PDSN, accepting the IP address.
Q The PDSN associates the MAC address of the PDSN with the mobiles
assigned IP address.
Q The PDSN sends an IPCP Configure Acknowledgement message to the
mobile. This message indicates that the networklayer connection is
complete.
Q A PPP session is now established between the mobile and the PDSN, and
the following activities can occur:
The PDSN can start sending accounting records to AAA and on to a
home or broker AAA.
The mobile and PDSN can start exchanging packets.
August, 2007
RF200 - 326
Simple IP Setup CHAP Authentication (1)

Q The mobile sends an LCP Configure Request message to the PDSN to initiate
setup of the datalink layer connection between the mobile and the PDSN.
Q The PDSN requests the mobiles datalink layer and authentication information by
sending an LCP Configure Request CHAP authentication.
Q Mobile replies by sending an LCP Configure Acknowledgement CHAP
authentication message to PDSN, containing configuration information PDSN uses
to set up the connection.
Q The PDSN sends an LCP Configure Ack CHAP authentication to the mobile to
acknowledge receiving the response. The mobile-PDSN datalink layer connection
is configured; set up the networklayer connection.
Q The PDSN sends a CHAP challenge to the mobile, containing a challenge value
used for authentication.
Q The mobile sends a CHAP response to the PDSN with:
Username=MSID@domain (MSID= mobile stations ID)
CHAP response value
CHAP ID
Q The PDSN sends an Access Request message to the Foreign AAA server. The
Access Request message contains:
NAI= MSID@domain
CHAP password = CHAP ID + CHAP response value
NAS IP address = PDSN IP address
CHAP challenge
August, 2007
RF200 - 327
Simple IP Setup CHAP Authentication (2)

Q The Foreign AAA server determines whether to accept or deny the Access Request
autonomously or use the services of a home or broker network AAA server.
Q The Foreign AAA server sends an Access Accept message to the PDSN, providing
a dynamic IP address assignment for the mobile.
Q The PDSN receives the Access Accept message and sends a CHAP Success
message to the mobile indicating that it was authenticated.
Q The mobile sends an IPCP Configure Request to the PDSN with its IP address set
to 0.0.0.0 (since its IP address for the session will be assigned the PDSN/AAA).
Q The PDSN sends an IPCP Configure Nak message to the mobile, containing the
dynamic IP address assignment for the mobile (from the Foreign AAA).
Q The mobile sends an IPCP Configure request message to the PDSN, indicating
that the mobiles IP address is now assigned/accepted.
Q The PDSN now associates the MAC address of the PDSN with the mobiles
assigned IP address.
Q The PDSN sends an IPCP Configure Acknowledgement message to the mobile.
The networklayer configuration is complete.
Q A PPP session is now established between the mobile and the PDSN, and
The PDSN can start sending accounting records to AAA and on to a home or
broker AAA.
The mobile and PDSN can start exchanging packets.
August, 2007
RF200 - 328
Mobile IP Setup (1)

Q The mobile sends an LCP Configure Request message to the PDSN, initiating
setup of the datalink layer connection between the mobile and the PDSN.
Q The PDSN sends an LCP Configure Acknowledgment No Authentication
message to the PDSN. No authentication means the PDSN wont authenticate the
mobile during PPP setup.
Q The mobile and PDSN perform the IPCP (network layer) phase of the PPP setup
process. The mobile can register using its own static IP address assigned by the
HA, or request a dynamic IP address from its HA for the duration of the call. If the
mobile is configured to use its own static IP address, the mobile specifies a non
zero source IP address in the IPAddress Configuration option during the IPCP
phase of the PPP negotiations. If the mobile is configured to use a dynamic IP
address, it does not use the IPAddress Configuration option during the IPCP
phase of the PPP negotiations.
Q The PPP session is established between the mobile and PDSN.
Q The mobile sends a Mobile IP based Agent Solicitation message to the PDSN,
requesting to use an HA for Mobile IP Internet access. This HA will be the mobiles
HA located in its home network which may be a home ISP, a private network, a
home access provider network, etc.
Q The PDSN sends a Mobile IP based Agent Advertisement message with a Foreign
Agent Challenge to authenticate the mobile.
Q The mobile sends a Mobile IP based Registration Request message with the
Foreign Agent Challenge Response to the PDSN.
If the mobile is configured for dynamic IP address assignment, the Registration
Request specifies the mobiles source IP address as 0.0.0.0, to initiate HA
assignment of a dynamic IP address to the mobile.
If the mobile is configured for using a static IP address, the mobile includes its
IP address in the Registration Request.
August, 2007
RF200 - 329
Mobile IP Setup (2)

Q The PDSN sends an Access Request to the Foreign AAA. The message contains
the Foreign Agent Challenge Response authentication information.
Q The Foreign AAA accepts or denies the Access Request using services of a home
or broker AAA server.
Q The Foreign AAA server sends an Access Accept message to the PDSN to indicate
that the mobile user can access the services.
Q The PDSN sends a Mobile IP based Registration Request to the mobiles HA. By
registering the mobile with its HA, the HA can track the location of the mobile by
PDSN IP address, and when the HA receives any packets addressed to the mobile,
it can redirect those to the PDSN.
Q The HA sends a Mobile IP based Registration Reply to the PDSN.
Q The PDSN sends a Mobile IP based Registration Reply to the mobile.
Q The PDSN sends a AAA Accounting Start message to the Foreign AAA.
Q Foreign AAA forwards accounting messages to the users home/broker network
AAA server.
Q The mobile IP user now accesses Internet/Intranet via connection between PDSN
and the HA.
The PDSNHA tunnel enables the sending and receiving of IP packets to and
from the correspondent Internet node.
The HA receives packets from the Internet/Intranet node corresponding with
the mobile, and redirects them to the current PDSN.
Q The HA receives packets from the PDSN and routes them to the Internet/Intranet
node corresponding with the mobile. Tunneling of data from the mobile to the HA
only occurs in the case of Reverse tunneling.
August, 2007
RF200 - 330
Proxy Mobile IP Setup

Q PPP portion of the call setup is same as in Simple IP scenarios.
Q PDSN sends AAA Access Request to Foreign AAA server, with:
NAI (mobile ID @domain)
User password (PAP), or CHAP password
IP address of the PDSN
CHAP Challenge
Q Foreign AAA server will accept or deny Access Request or use a
home network AAA server or a broker network AAA server.
Q Foreign AAA server sends Access Accept message to PDSN, with:
IP address for the mobile
IP address of an HA to use for sending and receiving packets.
Q PDSN sends a Mobile IP protocol Registration Request to the HA.
Q HA uses the information in the Registration Request to form the
binding record for the mobile station and allow internet access.
Q PDSN starts sending accounting records to the Foreign AAA.
Q Foreign AAA forwards accounting records to broker or home AAA.
Q The Proxy mobile IP user can now access the Internet/Intranet
through the connection set up between the PDSN and the HA.
August, 2007
RF200 - 331
Course RF200
CDMA2000
CDMA2000 1xRTT
1xRTT Data
Data
System
System Performance
Performance Optimization
Optimization
August, 2007
RF200 - 332
The Big Picture:

IP Data Environment
T
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
CDMA RF Environment
R-P Interface
BTS
PSTN
t1
t1
Switch
SEL
t1
CE
Traditional Telephony
CDMA IOS PPP
Coverage Holes
Pilot Pollution
Missing Neighbors
Fwd Pwr Ovld
Rev Pwr Ovld
Search Windows
Wireless
Island Cells
Mobile Device
Slow Handoff
Q 1xRTT services may include both traditional circuit-switched voice and

new fast IP data connections
A User's link is in multiple jeopardy, both radio and packet worlds
Q Radio environment portion
Problems: FER, drops, access failures, capacity woes
Causes: mainly in the RF world, because of mainly RF problems
Q Packet environment
Problems: Setup failures, dropped connections, low throughput
Causes: could be IP-related, or could be RF related
August, 2007
RF200 - 333
IP Data Environment
Internet
VPNs
PDSN/Foreign Agent
Optimization Issues
Q Network Design and Configuration
Coverage holes, excessive coverage overlap
Q Call Processing Problems due to Misconfiguration
Neighbor Lists
Search Windows
Power control parameters
Q Physical Problems/Hardware Problems
Mismatched multicarrier sector coverage
Q Capacity Issues
Forward and Reverse Power Control Overload
Physical resource congestion
Channel elements, packet pipes
IP network congestion
Q Managing A New Dimension: circuit-switched and IP traffic blend
QoS-related competitive issues
August, 2007
RF200 - 334
Optimizing in Two Worlds

Q Circuit-Switched Voice Traffic
Some operators are implementing 1xRTT mainly to gain capacity for
additional voice traffic
Their optimization techniques remain about the same as for 2G voice
networks today
Keep network adequately dimensioned
Control RF environment
Monitor and manage capacity utilization
Q IP Data Traffic
Operators adding IP traffic to upgraded voice networks
Conventional optimization techniques are still appropriate for general
RF environment and circuit-switched network performance
New IP and QoS issues require a new optimization focus for the
blended total network
IP performance depends on both IP and RF factors
IP and Voice performance involve competitive tradeoffs
August, 2007
RF200 - 335
Managing Forward Link Sector Loading vs. Time

Sector Total TX Power or Throughput
Sector Maximum TX Power, Maximum Throughput
Packet Data Traffic

Voice Traffic
Time, Seconds
Q Both voice and data traffic loads a sector, driving up transmit power
Voice calls are typically given higher priority than data
MAC-layer throttling holds lower-priority data sessions off until there is
enough free power available
August, 2007
RF200 - 336
#6 Indicator: Data Latency

IP Data Environment
T
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
CDMA RF Environment
R-P Interface
BTS
PSTN
t1
t1
Switch
SEL
t1
CE
CDMA IOS PPP
Coverage Holes
Pilot Pollution
Missing Neighbors
Fwd Pwr Ovld
Rev Pwr Ovld
Search Windows
Wireless
Island Cells
Mobile Device
Slow Handoff
Q Latency can occur because of RF channel congestion or from

IP network causes
RF overload can delay availability of supplemental channels
IP network congestion can delay availability of packets
Q Ping and loopback tests with local PDSN and servers can
identify whether problem is in backbone network
Q Does latency correlate with independent evidence of RF
congestion?
August, 2007
RF200 - 337
IP Data Environment
Internet
VPNs
PDSN/Foreign Agent
#7 Indicator: Data Throughput

IP Data Environment
T
PDSN
Home Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
CDMA RF Environment
R-P Interface
BTS
PSTN
t1
t1
Switch
SEL
t1
CE
CDMA IOS PPP
Coverage Holes
Pilot Pollution
Missing Neighbors
Fwd Pwr Ovld
Rev Pwr Ovld
Search Windows
Wireless
Island Cells
Mobile Device
Slow Handoff
Q Throughput can be limited by RF and IP causes

Traditional RF problems limit capacity of the channel
Congestion in the IP network can limit speed of data available
Q Does low throughput correlate with independent RF indicators?
Q Does low throughput correlate with independent IP pings and tests?
August, 2007
RF200 - 338
IP Data Environment
Internet
VPNs
PDSN/Foreign Agent
Course RF200
System-Side
System-Side 1xRTT
1xRTT Tools
Tools
August, 2007
RF200 - 339
Basic Philosophy of System Data

Q Each network manufacturer has its own data sets and counters
Access failures, TCCFs, blocks, drops, failed handoffs
These counters are normally available in 2G-only, 3G-only, and total
categories
Additional new statistics are available for IP traffic
Q The basic philosophy of system data analysis is to analyze and
discriminate within the available data
Identify and rank existing sectors based on
Traffic levels
raw failures/blocks/drops
percentage failures/blocks/drops
Benchmark and track incremental changes
Investigate all significant problems uncovered
Drive-testing or data testing may be required
Q In-Class activity: view manufacturer documentation and examples
August, 2007
RF200 - 340
Information on System-Side Statistics

Q Lucent
Technical Reference: Watchmark Prospect for Lucent, v17.0
Q Nortel
411-2131-814 DMS-MTX Operational Measurements Reference
Manual version v. 12.02 June, 2001
411-2131-900 DMS-MTX Operational Measurements Quick
Reference Guide
Q Motorola
Performance Analysis 2.16.0 v O , Motorola Inc., January 2002.
1x network Performance Matrix v. 0.1, Motorola Inc., April 2001.
CDMA 2000 1x Voice and Data Cellular Application Note , v. 1.1
Draft; Motorola Inc.
Impact on CDL and CFC in Version 2.16.0 v.1.4, Part No.
8700SCRP20GCDLCFC-D, Motorola Inc., August 2001
CFC Resolution Document v. 1.3, Motorola Inc Performance
Analysis 2.16.0 v O , Motorola Inc., January 2002
August, 2007
RF200 - 341
Mobile Tool: Andrew Invex Playback Example

76.8
kb/s
This mobile is in a 4-way soft handoff

(four green FCH walsh codes
assigned) in the middle of a downlink
SCH burst. Notice walsh code #2, 8
chips long, is assigned as an SCH
but only on one sector, and the
downlink data speed is 76.8kb/s.
August,RF200
2007v5.9 (c) 2007 Scott BaxterTechnical Introduction to Wireless -- 1997 Scott Baxter - V0.0
342

153.6
kb/s
This mobile is in a 2-way soft handoff

(two green FCH walsh codes
assigned) in the middle of a downlink
SCH burst. Notice walsh code #3, 4
chips long, is assigned as an SCH
but only on one sector, and the
downlink data speed is 153.6kb/s.
August, 2007
RF200 - 343

F-SCH rates 153.6 kbps; R-SCH 76.8kbps
CDMA Status
PN Scanner Data
Current Data Task Status
Layer-3 Messages
August,RF200
2007v5.9 (c) 2007 Scott BaxterTechnical Introduction to Wireless -- 1997 Scott Baxter - V0.0
344
Course RF200
Data
Data Flow
Flow Management:
Management:
MAC/LAC
MAC/LAC Layer
Layer Operation
Operation
August, 2007
RF200 - 345
PDSN/Foreign Agent
Forward Link SCH Scheduling

FCH or
data
FCH +
R-P
Interface
Buffer
SCH?
My F-SCH
Data Rate
BTS
CE
PCF SEL
t1
BTSC
Wireless
Mobile Device
Q The main bottleneck is the forward link itself: restricted by available

transmitter power and walsh codes
Q Each connected data User has a buffer in the PDSN/PCF complex
When waiting data in the buffer exceeds a threshold, the PDSN/PCF asks
the BTS for an F-SCH. Its data rate is limited by:
Available BTS forward TX power; available walsh codes; competition
from other users who also need F-SCHs; and mobile capability
When the buffer is nearly empty, the SCH ends; FCH alone
Occupancy timers and other dynamic or hard-coded triggers may apply
QOS (Quality of Service) rules also may be implemented, giving
preference to some users and some types of traffic
August, 2007
RF200 - 346
Forward Link Events in a Typical User Session

Data volume in PDSN
buffer triggers SCH
assignment. SCH rate is
driven by amount of
data in buffer and
available TX power
sector can allocate.
Data volume
in buffer low,
SCH released.
Data flow
continues on
FCH until
complete.
Data volume in PDSN

buffer triggers SCH
driven by amount of
data in buffer and
available TX power
Data volume in buffer

low, SCH released.
Flow continues on FCH.
153.6
Data Rate, kbps
Data volume in PDSN

buffer triggers SCH
driven by amount of
data in buffer and
available TX power
76.8
Active
timer
runs out!
FCH drops.
Session is
dormant.
38.4
19.2
9.6
Act
Susp
Init
CHld
Dorm
Null
Rcon
Data volume
in buffer low,
SCH released.
Data flow
continues on
FCH until
complete.
No data,
FCH idle,
1200 bps
Mobile
ends
session.
TA
1.2
0
STATE
Session begins.
No data, FCH
idle, 1200 bps
Data in PDSN
buffer. Data
flow begins
on FCH
August, 2007
FCH
idle
1200
bps
No data,
FCH idle,
1200 bps
Data in PDSN
buffer. Data
flow begins
on FCH
QOS algorithm
gives SCH to
another user
briefly. Data
meanwhile
flows on FCH.
No data,
FCH idle,
1200 bps
Data in PDSN
buffer. Data
flow begins
on FCH
Channel Legend:
FundamentalSupplemental
Idle
Data
Data
RF200 - 347
Course RF200
1x
1x Data
Data Tests
Tests and
and Optimization
Optimization
August, 2007
RF200 - 348
So S L O W ! !
IP Data Environment
T
PDSN
Home Agent
PDSN/Foreign Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
CDMA RF Environment
R-P Interface
BTS
PSTN
t1
Switch
t1
v SEL
t1
CDMA IOS PPP
CE
IP Data Environment
Internet
VPNs
Wheres My Data?!!
Coverage Holes
Pilot Pollution
Missing Neighbors
Fwd Pwr Ovld
Rev Pwr Ovld
Search Windows
Wireless
Island Cells
Mobile Device
Slow Handoff
Q Some sessions are tormented by long latency and slow throughput

Q Where is the problem? Anywhere between user and distant host:
Is the mobile users data device mis-configured and/or congested?
Is the BTS congested, with no power available to produce an SCH?
Poor RF environment, causing low rates and packet retransmission?
Congestion in the local IP network (PCU, R-P, PDSN FA)?
Congestion in the wireless operators backbone (OSSN) network?
Congestion in the PDSN HA?
Congestion in the outside-world internet or Private IP network?
Is the distant host congested, with long response times?
August, 2007
RF200 - 349
Finding Causes of Latency and Low Throughput

Test
Server
IP Data Environment
Internet
VPNs
PDSN
Home Agent
Test
Server
PDSN/Foreign Agent
Backbone
Network
SECURE TUNNELS
Authentication
Authorization
Accounting
AAA
CDMA RF Environment
R-P Interface
BTS
PSTN
t1
Switch
t1
v SEL
t1
CDMA IOS PPP
CE
IP Data Environment
Test
Server
Coverage Holes
Pilot Pollution
Missing Neighbors
Fwd Pwr Ovld
Rev Pwr Ovld
Search Windows
Wireless
Island Cells
Mobile Device
Slow Handoff
Q IP network performance can be measured using test servers

Q Problems between mobile a local test server? The problem is local
check RF conditions, stats: poor environment, SCH blocking?
if the RF is clean, investigate BSC/PCU/R-P/PDSN-FA
Q Local results OK, problems accessing test server at PDSN-HA?
problem is narrowed to backbone network, or PDSN-HA
Q Results OK even through test server at PDSN-HA
then the problem is in the public layers beyond.
August, 2007
RF200 - 350
Overview of Field Tool IP Test Activities
Application
Description
Purpose
Raw Upload
Uploads data with no overhead (no headers, no

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

handshaking beyond the normal TCP handshaking.)
Testing downlink throughput
Raw Loopback
A loopback (data is sent to the remote server which

returns the same data) application with no overhead (no
headers, no handshaking beyond the normal TCP
handshaking.)
Simultaneous exercise of the uplink and downlink
Ping (ICMP ECHO)
Ping does not use the TCP protocol, but rather uses the
connectionless and unreliable ICMP protocol. Sends
small echo request packets to a remote server, which
responds with an echo reply.
Determining round-trip-time between the user and the

remote server, as well as general link integrity (by
counting the number of missing echo reply packets).
A standard web page browse request.
If Raw Download is unavailable, testing downlink

throughput; modeling typical customer use.
A web-based upload (similar to how web-based email

sites allow users to upload files as attachments).
If Raw Upload is unavailable, testing uplink throughput.
FTP GET
A standard FTP file download. Many file downloads on

the Internet use FTP.
If Raw Download and HTTP GET are unavailable, testing

downlink throughput; modeling typical customer use.
FTP PUT
A FTP file upload. The file is generated by the Invex3G

platform and sent to the server.
If Raw Upload and HTTP POST are unavailable, testing

uplink throughput
Mail GET (POP3)
Retrieves all the mail for a given mailbox (e-mail

address) from an e-mail server. Note: does not delete
the e-mail messages from the mailbox.
Modeling typical customer use.
Waits a specified amount of time.
Testing idle timers, timeouts, etc.
HTTP GET
HTTP POST
Wait
August, 2007
RF200 - 351
Course RF200
Protocol-Layer-Specific
Protocol-Layer-Specific Data
Data
August, 2007
RF200 - 352
Watching Throughput in Real-Time
Q This display shows the relationship between instantaneous throughputs of

six protocols at various levels in the stack
a useful for identifying real-time problems by their signatures
Courtesy of Grayson Wireless from their Invex3G data collection tool
August, 2007
RF200 - 353
Protocol Stack Message Tracing

Q Some collection tools can
display and track messages
between layers of the
protocol stack
PAP, HDLC, IPCP, TCP,
IP
Q This allows detailed
troubleshooting of connection
and TCP/IP transfer problems
Capability of seeing
packet header contents is
useful for identifying and
debugging authentication
and connection problems
August, 2007
RF200 - 354
TCP Application Flow and Timing

Measurements
Start
Q Test equipment tools include software for

automatically attempting IP connections
Q Processes can be automatically
measured for performance
Throughput
Peak
average
Latency
Minimum
Average
Peak
Q Tests can be conducted end-to-end at
various levels of the protocol stack
Task Timing Begins Here
Send Connect
Request
Connect
Response
Received?
Transfer Data
(Application-Specific)
Timeout?
Application
throughput amount
and timing begins
and ends within
this block
Send Terminate
Request
Terminate
Response
Received?
Timeout?
Finish
Task Timing Ends Here
August, 2007
RF200 - 355
Course RF200 Section V.
Applied
Applied Optimization
Optimization
August, 2007
RF200 - 356
Starting Optimization on a New System

Q RF Coverage Control
try to contain each sectors coverage, avoiding gross spillover
into other sectors
tools: PN Plots, Handoff State Plots, Mobile TX plots
Q Neighbor List Tuning
try to groom each sectors neighbors to only those necessary
but be alert to special needs due to topography and traffic
tools: PSMM data from mobiles; propagation prediction
Q Search Window Settings
find best settings for SRCH_WIN_A, _N, _R
especially optimize SRCH_WIN_A per sector using collected
finger separation data; has major impact on pilot search speed
Q Access Failures, Dropped Call Analysis
finally, iterative corrections until within numerical goals
Getting these items into shape provides a solid baseline and foundation from
which future performance issues can be addressed.
August, 2007
RF200 - 357
Performance Monitoring/Growth Management

Q Benchmark Existing Performance
Dropped Call %, Access Failure %, traffic levels
Q Identify Problem Cells and Clusters
weigh cells and clusters against one another
Q Look for signs of Overload
TCE or Walsh minutes -- excessive ? Soft handoff excessive?
Required number of channel elements -- excessive?
Forward Power Overloads: Originations, Handoffs blocked
Q Traffic Trending and Projection
track busy-hour traffic on each sector; predict exhaustion
develop plan for expansion and capacity relief
split cells, multi-sector expansions, multiple carriers
These steps must be continuously applied to guide needed growth.

August, 2007
RF200 - 358
CDMA Problems, Causes, and Cures

PROBLEMS
Q Excessive Access Failures
Q Excessive Dropped Calls
Q Forward Link Interference
Q Slow Handoff
Q Handoff Pilot Search Window Issues
Q PN Planning Considerations
Q Excessive Soft Handoff
Q Grooming Neighbor Lists
Q Software Bugs, Protocol Violations
EXAMPLES
Q Normal Call
Q Dropped Call - Coverage
Q Dropped Call - Neighbor List
Q Dropped Call - Search Window
August, 2007
RF200 - 359
Solving CDMA Performance Problems

Q CDMA optimization is very different from optimization in analog
technologies such as AMPS
Q AMPS: a skilled engineer with a handset or simple equipment can
hear, diagnose, and correct many common problems
co-channel, adjacent channel, external interferences
dragged handoffs, frequency plan problems
Q CDMA impairments have one audible symptom: Dropped Call

voice quality remains excellent with perhaps just a hint of garbling as
the call approaches death in a hostile RF environment
Q Successful CDMA Optimization requires:

recognition and understanding of common reasons for call failure
capture of RF and digital parameters of the call prior to drop
analysis of call flow, checking messages on both forward and reverse
links to establish what happened, where, and why.
August, 2007
RF200 - 360
Troubleshooting
Troubleshooting Access
Access Failures
Failures
August, 2007
RF200 - 361
Investigating Access Failures

An access attempt failure can occur at
any point in the process:
Q Access probes exhausted (not received
by system)
Q Access probes exhausted (seen by
system but ACK not reaching mobile
station)
Q Ack received by mobile station but
Channel Assignment Message not seen
Q Channel Assignment Message seen at
mobile but mobile station does not
acquire Forward Traffic Channel
Q Mobile station acquires Forward Traffic
Channel but system does not acquire
Reverse Traffic Channel
Q System acquires Reverse Traffic
Channel but Service Connect Message
is not seen at mobile station.
August, 2007
Successful Access Attempt

Origination Msg
ACCESS
MS
Probing
BTS
PAGING Base Sta. Acknlgmt. Order
PAGING
Channel Assnmt. Msg.

FW FC
Base Sta. Acknlgmt. Order

FW TFC

Svc. Connect Complete Msg
RF200 - 362
RV TFC
Troubleshooting Access Failures & TCCFs

Q Troubleshooting access failures (Traffic Channel Confirmation Failures)
can be difficult
Q There are many steps in the access process
Finding which step failed is not easy
Q Rarely, circumstantial evidence points clearly to the problem
Q Usually, it is necessary to debug the process leading up to the access
failure
Consider each step in the access process
Get evidence to determine whether this step occurred successfully
Move on to the next step and keep checking steps until the
unsuccessful step is found
Determine why this step failed
Q The following slides describe the steps in the access process, where they
take place, and some of the factors which may cause them to fail
Q This narrative might be useful as a template for organizing your own
thinking as you investigate access failures you are tracking!
Go out and capture actual drive tests of failed origination attempts
If possible, also collect system logs (RF call trace, etc.) for the same
event
August, 2007
RF200 - 363
Troubleshooting Access Failures (1)

BTS
Steps in the Access Process
Paging Channel
Access Channel
Origination Msg.
Probe #1
Mobile waits to see if the BTS hears and

acknowledges its probe within the time ACC_TMO.
If not, the mobile must transmit the message again
in another probe, this time PI db. louder.
Origination Msg.
Probe #2
Mobile waits again to see if the BTS hears and
acknowledges its probe within the time ACC_TMO.
If not, the mobile must transmit the message again
in another probe, this time PI db. louder.
Origination Msg.
Probe #3
The mobile keeps probing until NUM_STEP probes
have been sent, then repeats the probe sequence
again until Max_Probe_Sequences have been
sent.
Troubleshooting Comments
If the mobile does not hear acknowledgment from
the BTS within ACC_TMO, this could mean either:
The BTS did not hear the mobile
Maybe the mobile collided with another
mobile transmitting at the same time
Maybe mobile was too weak to overcome
the existing reverse noise level at the BTS
In either case another probe should solve
the problem, provided PI is set reasonably
and additional probes are allowed (check the
Access Parameters Message to see if
Num_Step and the power parameters make
sense; be sure also the cell size or Access
Channel acquisition search width is set large
enough and the number of access preamble
frames is large enough for the cell size)
The BTS is acknowledging but the mobile cannot
hear the acknowledgment
If the mobile cant hear the BTS
acknowledging, Ec/Io is likely quite poor. If
so, check whether this is due to weak signal
(poor coverage) or pilot pollution (lots of
pilots all weak but no dominant server)
Collect system logs if necessary to determine
definitely whether the system heard the mobiles
origination or not
August, 2007
RF200 - 364

BTS
The Access Process
Paging Channel
Access Channel
One Dreaded Possibility:

Reorder
Mobile beeps and displays Call Failed - System
Busy
August, 2007
If this problem happens frequently, the BTS traffic
overload must be relieved. Here are some steps to
try:
Investigate BTS TX hardware to ensure everything
is working correctly and properly calibrated,
particularly gain settings in the TX chain
To free up more forward power for traffic channels,
try:
Reduce PTXstart (initial traffic channel
DGU) watching for less forward power
control overloads. If you go too far, you will
notice access failures increase.
Reduce PTXmax (maximum traffic channel
DGU) watching for less forward power
control overloads. If you go too far, dropped
calls will increase.
Reduce sector traffic by reorienting the sectors to
more closely balance the load carried by each
Or, add another carrier
Or split cells
RF200 - 365

BTS
The Access Process
Paging Channel
Access Channel
Base Station
Acknowledgment
After hearing the BTS acknowledgment, the mobile

will stop probing and wait for further instructions on
the paging channel.
If the mobile does not hear the Channel
Assignment Message within 12 seconds, the
mobile will beep and display Call Failed. Possible
causes:
The BTS did not transmit the Channel Assignment
Message
Check system logs to see if this was not
transmitted. If not transmitted, get
troubleshooting help from the system
manufacturer -- this should never occur
The BTS did transmit the Channel Assignment
Message, but the mobile did not hear it
Was this because the paging channel
faded? (Did the Ec/Io drop momentarily)? If
so, see If this is a recurring problem such as
a coverage hole or severe pilot pollution
Channel Assignment
Message
STOP! Leave the Paging Channel, and dont

transmit again on the access channel.
The mobile now goes to try to hear the Forward
Traffic Channel.
August, 2007
Finally! The mobile hears the Channel Assignment

Message!
Now it will immediately leave the paging channel
and start trying to hear the new Forward Traffic
Channel.
RF200 - 366

BTS
The Access Process
FWD Traffic Channel REV Traffic Channel

00000000000000000000
00000000000000000000
00000000000000000000
Mobile beeps and displays Call Failed
00000000000000000000
00000000000000000000
00000000000000000000
The mobile listens to the Walsh Code # given in the
Channel Assignment Message. It should hear N5M
good frames full of all zeroes within T2M seconds
(usually 2 frames in 10 frames).
If the mobile does not hear the required number of
good empty frames, it will beep and give an error
message, then reacquire the system.
If the mobile hears the required number of good
empty frames, it starts transmitting its own
Reverse Traffic Channel Preamble of empty allzero frames.
If the BTS does NOT hear the mobiles access
preamble within a prescribed delay, it will abort the
process and release all the resources, and the
mobile will reacquire the system. . This is what
Lucent terms a Traffic Channel Confirmation
Failure (TCCF).
Base Station
Acknowledgment
Mobile Station
Acknowledgment
August, 2007
If the BTS DOES hear the mobiles access

preamble, it will send an acknowledgment.
The mobile responds with an acknowledgment, or
maybe even a pilot strength measurement
message if it already needs a handoff.
RF200 - 367

BTS
The Access Process
FWD Traffic Channel REV Traffic Channel

Service Connect
Message
Service Connect
Complete Message
This is still just an ongoing access attempt
Base Station
Acknowledgment
Now this is officially a call in progress
Now that the BTS and mobile see each other on
the traffic channels, the next step is service
negotiation.
The BTS sends a Service Connect message listing
the type and rate set of the vocoder or other
primary traffic source.
The mobile either accepts the proposal with a
Service Connect Complete message, or
counterproposes a different mode.
The BTS acknowledges the Service Connect

Complete message.
The call is now officially in progress. If anything

happens to interrupt it after this point, that is
considered a dropped call.
If any of these steps is unsuccessful, the call
attempt will probably fail. Suspect RF conditions on
the link which was supposed to carry the
unsuccessful command. Look at system logs and
message logs from mobile drive testing to pin down
just what happened.
August, 2007
RF200 - 368
Access Failure/TCCF Troubleshooting

Access Attempt Failed
Were any probes acknowledged?

Yes,
BS Ack
No,
Nothing
Yes,
Reorder
Blocking
Paging Channel
faded, lost
Check System Logs.

Was mobile heard?
yes
no
Was Channel Assignment

Message heard?
yes
Did mobile see N5M good
frames on F-TCH?
yes
Check System Logs. Did
BTS see mobile preamble?
yes
Did mobile see BS Ack?
yes
Check System Logs.
Did BTS see mobile Ack?
OK
August, 2007
yes
Check System Logs.

Was CH ASN sent?
no
no
no
Check System Logs.
CH EL initialized OK?
yes
no
Forward Power
Channel Elements
Rev. Link Noise
Weak Signal/Coverage Hole?
Add coverage
Strong Fwd interf / pollution?
Identify, eliminate
Is T-1unstable/blocking?
Report/repair
Rev Link Overload?
Identify, fix source
Num_Step, Pwr_Step
appropriate?
Ensure reasonable
values
Sector Size, Acq Width

appropriate?
Ensure reasonable
values for cell size
System Problem.
Investigate why
no
Software problem
Resource blocking
Rev. Link Noise
no
no
Optmz Fpwr DGUs

Add chan cards
F-TFC Channel
faded, lost
Init TCH DGU large enough?

Strong Fwd interf / pollution?
Raise DGU
Improve coverage
Identify, eliminate
Report/repair
R-TFC Channel
faded, lost

Strong Rev Noise?
Improve coverage
Identify, eliminate
Report/repair
RF200 - 369
Reducing Access Failures

If the base station never sees the mobiles probes,
Access Attempt
the cause is probably coverage-related. If it happens
in strong signal areas, suspect BTS hardware. Also
Origination Msg
ACCESS
check datafill for proper NOM_PWR and PWR_INC.
Be sure the BTS datafill access channel acquisition BTS
MS
Probing
and demodulation search windows are adequate.
1. If the failures occur in areas where one BTS PAGING Base Sta. Acknlgmt. Order
is dominant, suspect BTS hardware problems.
2. Plot the access failures to see if they correlate
with areas of BTS overlap. If so, suspect
PAGING Channel Assnmt. Msg.
forward link problems. This is probable
because the mobile does not have the normal
FW FC Base Sta. Acknlgmt. Order
advantage it would get from soft handoff on a
traffic channel. During access, it must
successfully demodulate all five BTS messages
without the benefit of soft handoff. If the
FW TFC
handset is in an area of multiple BTS overlaps
Svc. Connect Complete Msg RV TFC
or weak signal, this can be risky. In such cases,
try to make the serving BTS more dominant.
Also check the access/probing parameters.
August, 2007
RF200 - 370
Troubleshooting
Troubleshooting Dropped
Dropped Calls
Calls
August, 2007
RF200 - 371
Dropped Call Troubleshooting - Mobile Side

Just arrived on sync channel!
Is this a drop?
Were there release

messages?
no
yes
OK, normal
end of call
This is a drop!
Was the Sync Channel PN

Active before the drop?
no
no
Add PN to Neighbor List!
Widen SRCH_WIN_N!
no
yes
Repair/Re-initialize Cell!
Did mobile request Sync CH

PN in PSMM before drop?
no
yes
Check
for:
yes
Improve coverage
Strong Fwd/Rev interference?
Identify, eliminate
Report/repair
Why didnt handoff happen?

PN not in neighbor list
Add PN to Nbr List!
Is PN in neighbor list?
yes
Add coverage
FER already too bad?
Push earlier
Is SRCH_WIN_N adequate?
yes
Border configuration problems
Debug, reconfigure
Fast-rising pilot, slow reaction
Incr Sector Overlap

Speed up searcher
Forward Power
Channel Elements
Rev. Link Noise
Optmz Fpwr DGUs

Add chan cards
Is cell in island Mode?

no
Blocking
Report/repair
More information needed.

Collect system logs and
merge with mobile data,
analyze
August, 2007
RF200 - 372
Investigating Dropped Calls

BAD COVERAGE
Q If the radio link fails after the mobile sends the

Service Connect Complete Message then it is
considered a dropped call. Using the signatures
described earlier, it is possible to recognize and
separate the dropped calls into the categories at
right.
Q Each category has its own causes and solutions
FFER
RXL
100%
-30
EC/IO
TxGa
TxPo
+23
+25
-6
+10
-10
-20
-10
-30
+10
-40
0
-10
50%
10%
5%
2%
0%
FFER
-90
-100
-110
RXL
-15
-40
-20
EC/IO
-50
-25
-20
TxGa
TxPo
Messaging
BTS
FWD. INTERFERENCE
FFER
RXL
100%
-30
EC/IO
TxGa
TxPo
+23
+25
-6
+10
-10
-20
-10
-30
-40
+10
0
-10
Q Dropped call analysis can consume a

considerable amount of time. Using good postprocessing analysis tools, the root cause of
some of the drops can be determined from
mobile data alone. However, there will be
cases where the cause cannot be reliably
confirmed unless system data is also used
50%
10%
5%
2%
0%
FFER
-15
-40
-20
-20
EC/IO
-50
-25
TxGa
TxPo
Messaging
REV. INTERFERENCE
FFER
RXL
100%
-30
EC/IO
TxGa
TxPo
+23
+25
-6
+10
-10
-20
-10
-30
+10
-40
0
-10
50%
10%
5%
2%
0%
BTS
RXL
BTS
FFER
August, 2007
-90
-100
-110
-90
-100
-110
RXL
-15
-40
-20
-20
EC/IO
-50
-25
TxGa
TxPo
Messaging
RF200 - 373
Handoff Problems: Window Dropped Calls

Q Calls often drop when strong
neighbors suddenly appear
outside the neighbor search
window and cannot be used to
establish soft handoff.
Q Neighbor Search Window
SRCH_WIN_N should be set
to a width at least twice the
propagation delay between
any site and its most distant
neighbor site
Q Remaining Search Window
SRCH_WIN_R should be set
to a width at least twice the
propagation delay between
any site and another site
which might deliver occasional
RF into the service area
August, 2007
SITUATION 1
A
BTS
12
80 mile
Ch s
ips
Locked to distant
mo site, cant see
un one nearby
tai
ns
B
BTS
SRCH_WIN_N = 130
BTS A is reference.
1 mi.
BTS B appears (7-80) chips
7 Chips
early due to its closer distance.
vel
This is outside the 65-chip window.Tra
Mobile cant see BTS Bs pilot, but its
strong signal blinds us and the call drops.
SITUATION 2
A
Locked to nearby
mo site, cant see
un distant one
tai
ns
B
12
80 mile
Ch s
ips
SRCH_WIN_N = 130
BTS
BTS B is reference.
1 mi.
BTS A appears (80-7) chips
7 Chips
late due to its farther distance.
l
This is outside the 65-chip window. Trave
Mobile cant see BTS As pilot.
BTS
RF200 - 374
Optional: Quick Primer on Pilot Search Windows

Q The phone chooses one strong sector and
locks to it, accepting its offset at face value
and interpreting all other offsets by
comparison to it
Q In messages, system gives to handset a
neighbor list of nearby sectors PNs
Q Propagation delay skews the apparent PN
offsets of all other sectors, making them
seem earlier or later than expected
Q To overcome skew, when the phone
searches for a particular pilot, it scans an
extra wide delta of chips centered on the
expected offset (called a search window)
Q Search window values can be datafilled
individually for each Pilot set:
Q There are pitfalls if the window sizes are
improperly set
too large: search time increases
too small: overlook pilots from far away
too large: might misinterpret identity of a
distant BTS signal
PROPAGATION DELAY
SKEWS APPARENT PN OFFSETS
33
4
Chips
Chips
A
BTS
B
BTS
If the phone is locked to BTS A, the
signal from BTS B will seem 29 chips
earlier than expected.
If the phone is locked to BTS B, the
signal from BTS A will seem 29 chips
later than expected.
One chip is 801 feet or 244.14 m

1 mile=6.6 chips; 1 km.= 4.1 chips
August, 2007
RF200 - 375
Pilot Search Order, Speed, and Implications

PILOT SEARCHING IN NESTED LOOPS:
WINDOW SIZE
IN CHIPS AND DATA UNITS
Active+Cand
Neighbor
Remaining
THE CAR ODOMETER ANALOGY

The searcher checks pilots in the
order they would appear if pasted
on the wheels of a car odometer.
Actives and candidates occupy the
fastest-spinning wheel.
Neighbors are next, advance one
pilot each time Act+cand revolves.
Remaining is slowest, advance one
pilot each time Neighbors revolve.
Datafill
Value
Window
Size (Chips)
14 (7)
20 (10)
28 (14)
40 (20)
60 (30)
80 (40)
10
100 (50)
Q Actives & candidates have the biggest influence.
11
130 (65)
Keep window size as small as possible
During soft handoff, this set dominates searcher
12
160 (80)
Minimize excessive Soft HO!
13
226 (113)
Q Neighbor set is second-most-important
14
320 (160)
Keep window size as small as possible
15
452 (226)
Keep neighbor list as small as possible
But dont miss any important neighbors!
Q Remaining Set: pay your dues, but get no reward
You must spend time checking them, but the system cant assign one to you
August, 2007
RF200 - 376
Treating Drops with Poor-Coverage Symptoms

Drops with weak-signal symptoms
Q Using a post-processing tool,
happened in predicted strong-signal
display a map of the locations of
area. Suspect bad BTS hardware.
dropped calls that exhibit
symptoms of poor coverage
It is particularly useful to be
able to overlay the drop
locations on a map of
predicted or measured signal
levels
Q Verify this type of drop is not
occurring in good-coverage areas
If so, suspect and investigate
hardware at the serving site
Q Coverage related drops occurring
in poor-coverage areas are to be
expected; additional RF (usually
from new BTSs) is the only
These drops are probably normal
solution except in rare cases
due to their locations in a
predicted weak-signal area.
August, 2007
RF200 - 377
Treating Drops with Forward-Link Problems

Q Plot the data containing the
forward-link interference drops on
maps from your propagation
prediction tool
Use the prediction tool to help
identify other strong signals
reaching the drop areas
If the signals are from other
CDMA carriers, add their Pilot
PNs to the neighbor list
Resolve any PN conflicts
Q Another technique is to examine
the dropped call message files
and identify the BTS from which
the sync channel message is
received immediately after each
drop (this will be the cleanest pilot
the handset sees at that time)
August, 2007
The call on sector A dropped here,

apparently due to interference
from sector B. Find out why soft
handoff with B did not occur.
B
Sync Channel Message
p_rev 1, bit_len: 170
min_p_rev 1
sid 4139 nid 41
pilot_pn 0x164 = 356 ( RMCZ )
lc_state 1ED595B9632
sys_time 189406BE8
lp_sec 13
ltm_off 0x10 (8.0 hours)
daylt 0 prat 1
cdma_freq 50
RF200 - 378
Optimizable Dropped Calls: Slow Handoff

Q When the mobile is suddenly
confronted with a strong new signal,
or when the signal it is using takes a
sudden deep fade, it will have poor
Ec/Io and high forward FER. The call
will drop unless it gets help quickly.
Several steps which must occur
without delay:
The mobile search correlator
must first notice the new pilot
and send a PSMM to the system. BTS
The system must set up the soft
handoff and notify the mobile.
The mobile must acquire the
new signal by locking a finger
August, 2007
BTS
RF200 - 379
Sources of Delay Causing Slow Handoff

Every step in the handoff process can suffer delay if were not careful
to control conditions:
Q Mobile search correlator notices new pilot
Window sizes too large, searching is slow
Multi-sector soft handoff already underway, many active pilots,
searching is slow
Interferor not a neighbor, must find in remaining set: slow, DIE!
System cannot currently set up true remaining-set handoffs
Q Mobile reports PSMM to system.
Reverse link noisy, PSMM must be re-requested & repeated
Q System sets up handoff, sends EHDM to mobile
Resource congestion: no TCEs, or other problems
Forward link is noisy, mobile doesnt hear EHDM, must repeat
Fortunately, these problems do not have to happen.

August, 2007
RF200 - 380
Auditing System Handoff Setup Time
100%
Typical Handoff
Setup Time
Cumulative Distribution Function
90%
80%
70%
60%
50%
40%
30%
20%
10%
0%
0
100
200
300
400
500
Q After the mobile searcher recognizes the

pilot it needs, the job is only begun
The mobile must send a PSMM to
system; it must be received
System must recognize reported PN
phase, set up resources in the
appropriate sector
An EHDM must be sent to the
mobile, received, acknowledged
Mobile must acknowledge again
when handoff implemented
Q Time required for this process can be
measured by watching messages
most post-processing tools can show
histogram or graph of this delay
if system is healthy, almost all
handoffs will happen in <200 msec.
and there will be no stragglers
Time (milliseconds)
August, 2007
RF200 - 381
Setting Pilot Search Window Sizes

Q When the handset first powers up, it does an exhaustive search for the
best pilot and no windows apply to this process.
Q When finally on the paging channel, the handset learns the window sizes
SRCH_WIN_A, N, R and uses them when looking for neighbors both in
idle mode and during calls.
Q During a call, when a strong neighbor is recognized, a PSMM is sent
requesting soft handoff. The former neighbor pilot is now a candidate set
pilot and its offset is precisely remembered and frequently rechecked and
tracked by the phone.
Q The window size for active and candidate pilots doesnt need to be very
large, since the searcher has already found them and is tracking them
very frequently. We need only enough width to accommodate all
multipath components of these pilots.
This greatly speeds up the overall pilot search management!
Q Most post-processing tools deliver statistics on the spread (in chips)
between fingers locked to the same pilot. These statistics literally show us
how wide the SRCH_WIN_A should be set.
Q Neighbor and Remaining search windows should be set based on intercell
distances as described in a preceding slide.
August, 2007
RF200 - 382
Maximum Timing Budget for CDMA Cells

Q The range of a CDMA cell is normally limited by the attenuation that
occurs along ordinary propagation paths. Occasionally, a site is
located atop a high mountain or other location from which it can see a
very large distance, so large that timing considerations must be
recognized. Search windows are the main concern.
Q The BTS uses acquisition and demodulation search windows much
like the pilot search windows used by the mobile. The maximum
setting is 4095/8 chips (512 chips -1/8 chip). A mobile 38.8 miles from
the site would be at the edge of this maximum window setting, and
could not originate or be acquired during handoff beyond this distance.
Q The mobile is not restricted on acquiring the system forward channels
but its pilot search windows are limited to 452 chips. Neighbor pilots
couldnt be recognized if coming from a cell more than 34.3 miles
closer or farther than the cell to which the mobile is locked.
Q The IS-95 and J-Std008 specify a maximum of 350 sec maximum
round trip delay, BTS-Handset. This is a distance of 32.6 miles.
Q General Observation: If your cell radius exceeds 30 miles, be careful.
August, 2007
RF200 - 383
A Word About Soft Handoff for

Former AMPS/TDMA Personnel
Q Former AMPS/TDMA optimizers may feel an instinctive obligation to
minimize handoff activity, with good reason. In AMPS/TDMA, handoffs
involved muting and real risk of a drop. Since the mobile could be served
by just one sector at a time, there was pressure to be sure it was the best
available sector, but also pressure not to do many handoffs. Ping-pong is
unpopular in AMPS/TDMA.
Q In CDMA, there is no muting or audible effect during soft/softer handoff,
and there is no pressure to use just the right sector -- if several are
roughly as good, use them all, up to 6 at a time.
The noise level on the reverse link actually decreases during soft
handoff - by roughly 4 db. - allowing the system to handle from 1.5 to
2 times as many subscribers as otherwise.
The forward link noise does rise, but not to troublesome levels
There is an additional cost for doing soft handoff: each involved BTS
must dedicate a TCE channel element to the handoff. However, even
if every user is constantly involved in soft handoff, this increases the
cost of a BTS a small percentage.
Q So, to former AMPS/TDMA folks, dont fear. Use the force, Luke! And
to our GSM friends, Resistance is futile...
August, 2007
RF200 - 384
How Much Soft Handoff is Normal?

Q How much soft handoff is normal?
Expectations in early CDMA development were for roughly 35%
The level of soft handoff which should be used depends on how much
diversity gain can be achieved, and terrain roughness
If the reverse link budget assumed 4 dB soft handoff gain, and
propagation decays 35 dB/decade, 42% of the sectors area is within
the last 4 dB. of coverage where soft handoff occurs.
In typical markets, terrain irregularities scatter RF beyond cleanly
designed cell edges; soft handoff is typically 50-60%
In rough terrain, proper soft handoff may rise to 70% or more
Q In a system not yet well-tuned, soft handoff may be clearly excessive
The main cause is usually excessive RF overlap between cells
RF coverage control is the most effective means of reducing and
managing soft handoff (BTS attenuation, antenna downtilting)
Thresholds T_ADD and T_DROP can be adjusted to reduce soft handoff,
but this penalizes mobiles that need soft handoff to escape interference
from the excessively overlapping sites
Controlling soft handoff percentage with T_ADD and T_DROP is like limiting
allowed hospital days for various illnesses. Works, but some patients may drop.
August, 2007
RF200 - 385
Dangerous Environments
Q The CDMA handset is designed with a digital rake receiver including
three correlators (fingers) which can demodulate signals from up to three
sectors simultaneously, combining and using the energy from all three to
improve reception. Implications:
If One dominant signal: this is a good situation; the three fingers will
be looking for resolvable multipath components; good diversity
If Two usable signals: good situation; soft handoff & diversity
If Three usable signals: good situation; soft handoff & diversity
If Four roughly equal signals: workable but not ideal. Three best
signals are demodulated; other remains an interferor. 3 vs 1
If Five roughly equal signals: probably workable but not good. Three
best are demodulated; remaining two are interferors. 3 vs 2
If Six roughly equal signals: very frightening. Three best signals are
demodulated; three remaining signals are interferors. 3 vs 3
Q The system can provide up to 6-way soft handoff, but anything above
three-way is an indication that there is too much RF coverage overlap.
More than three-way soft handoff should be the notable exception rather
than the rule.
August, 2007
RF200 - 386
Identifying Causes of Excessive Soft Handoff

Q RF Drive Test data (preferred) or Propagation Prediction runs
(second choice) can be used to identify the excessive coverage
overlaps which cause soft handoff.
Q Suggested Procedure:
Use a post processing tool to display all locations where a
sector has strongest rake finger status, or
Use a propagation prediction tool to show all locations where a
sector is best server
Draw a curve through all the adjacent surrounding sites
If more than 15% of the best-finger or best-server points lie
outside this line, this sectors coverage is excessive.
Reduce signal levels by at least 8 dB. through attenuation or
downtilt and re-examine either using prediction or re-driving
Be aware that as strong unwanted signals are reduced or
removed by this process, other signals formerly degraded may
become apparent and also require similar treatment. This is
therefore a somewhat iterative process.
August, 2007
RF200 - 387
Grooming Neighbor Lists

Q Earlier we described a general technique for creating initial neighbor lists.
During initial optimization, and especially after your system generates data
from commercial traffic, youll want to revisit and groom the neighbor lists.
Q Use your post-processing tool to show you all handoff transitions
requested by mobiles on a per-sector basis. If you dont have a fancy
software tool, you can still do it with fairly simple scripts parsing captured
pilot strength measurement messages.
Q For each sector, examine the statistics in conjunction with the Planet
equal power boundaries plot. Consider removing any pilots that are
currently in the neighbor list but have less than 1% of the handoff
transitions. However, make sure that is not a consequence of no test
drives being made across a particular sector boundary (for example, do
not remove adjacent sectors of a sectored site).
Q Consider adding pilots that are not currently in the neighbor list but have
greater than 5% of the handoff transitions. Remember, though, that the
goal is to keep neighbor lists to a minimum (see below) so avoid adding
sites that are obviously not immediate neighbors of the serving cell (i.e. try
to make use of the composite neighbor list as much as possible).
August, 2007
RF200 - 388
TX Gain Adjust as a Per-Site Debugging Tool

Q Collect Transmit Gain Adjust Statistics
Q For an unloaded system, the average should be -7 to -12 db. and
should be fairly constant throughout the coverage area
Q Look for big jumps in TX GA from sector to sector. Look for
hardware problems (antennas OK, RX noise figure OK?, etc.)
Q If you see values generally outside the range above uniformly
across the coverage area, look at the BS Eb/Nt. It should be 5-9
dB for mobile systems, or 3-4 dB. for fixed wireless access.
Q Other parameters can have similar uses; compare and study.
Typical Mobile Station Transmit Gain Adjust
0 dB
-10 dB
-20 dB
Time, Seconds
August, 2007
RF200 - 389
RF200 Appendix I
Case
Case Study:
Study:
Sudden
Sudden Heavy
Heavy Sector
Sector Loading
Loading
August, 2007
RF200 - 390
Runaway Class turns to Dark Side of the Force

Q A major PCS operator often holds
technical classes in an attractive
conference center on the south side of
Kansas City
Q In early November, 1998, a CDMA
performance optimization class realized it
had a large number of mobiles on hand
and decided to try to push a cell to the
limit: to see just how far we could go in
cell loading, and what would happen
Q Data collection equipment was on hand to
record the event from the mobile side
Q System operations personnel were
available to retrieve system-side statistics
for the period
Q Lets see what happened!
August, 2007
RF200 - 391
The BTS at the BTA Conference Center

Classroom
208
204
212
Q The classroom is about

500 feet northwest of
the three-sector BTS
Q The BTS gamma face
is the dominant sector
for the classroom, at
PN 212.
BTS
from RFCAD
Looking northwest
from IQAnalyzer
August, 2007
RF200 - 392
What to Expect:
Loading Effects on the Forward Link
August, 2007
Ec/Io = (2/4)
= 50%
= -3 db.
BTS
Transmit
Power
Paging
Sync
Pilot
Heavily Loaded
Ec/Io = (2/10)
= 20%
= -7 db.
1.5w
0.5w
2w
EC
I0
BTS
Transmit
Power
Traffic Channels
Q On the forward link, the

overhead channels (Pilot,
Sync, and Paging) remain
constant
Q Each new traffic channel
consumes additional transmit
power
Q Total transmit power increases
as traffic increases
Q Ec/Io decreases as traffic
increases (Ec stays the same,
but Io is driven up)
Paging
Sync
Pilot
6w
I0
1.5w
0.5w
2w
EC
RF200 - 393
What to Expect:
Loading Effects on the Reverse Link
BTS
Receive
Power
Mobile
Thermal
Noise
Heavily Loaded Sector

BTS
Receive
Power
Mobile
Other
Mobiles
Q On a lightly-loaded sector, the

noise floor is relatively low and an
individual mobile can be heard at
comfortably low power
Q When the forward power goes up,
each mobiles open-loop power
control will try to decrease mobile
power output
Q On a heavily loaded sector each
mobile is competition against the
others, so the BTS must raise
each mobiles power to remain
competitive
Q Closed Loop power control takes a
double hit correcting for both
increased noise and the mobiles
incorrect power control instincts
Lightly Loaded Sector
Thermal
Noise
I can hear it coming in the air tonight..

--Phil Collins
August, 2007
RF200 - 394
BTS Loading Effects on the Reverse Link
August, 2007
Paging
Sync
Pilot
1.5w
0.5w
2w
EC
I0
Heavily Loaded
Traffic Channels
Q On the reverse link, receive power

at the BTS increases when traffic
increases
BTS closed-loop power control
must counter this trend,
keeping each mobile
competitive with the rest
Q On the reverse link, the mobile
responds inversely to BTS power
output changes
When traffic drives BTS power
up, the mobile instinctively
tries to power down
BTS closed-loop power control
must also counter this trend
Q Mobile transmit power increases
substantially during heavy-traffic
periods!
Paging
Sync
Pilot
6w
I0
1.5w
0.5w
2w
EC
RF200 - 395
A Sudden Change!!
25+ Mobiles
Calls begin
August, 2007
Test Mobile Call Begins
All Phones
in Idle Mode
Test Mobile call has ended,

Other mobile calls continue
RF200 - 396
Test Mobile Receive Power
As expected, the additional

calls increase the total power
output of the sector. This
causes received power to
increase at the test mobile.
Average
-70.5 dbm
With max users
Average
-76.5 dbm
With one user
August, 2007
RF200 - 397
Test Mobile Combined Ec/Io
Average
-3.6 db
With one user
Average
-6.8 db
With max users
Since the additional calls
increase the total power
output of the sector, but the
pilot power remains fixed,
the Ec/Io at the test mobile
decreases in proportion.
August, 2007
RF200 - 398
Test Mobile Closed-Loop Power Control (TXGA)
Average
-16 db
With only this
User active
Since the additional calls
increase the noise level at
the BTS receiver, the BTS
must ask the test mobile to
increase its transmit power
output to keep up with the
crowd.
August, 2007
Average
-6 db
while max users
active
About 6 db of this increase is
necessary to counteract the
mobiles own open-loop instinct
to power down due to
increased BTS power.
The rest is needed to keep the
mobiles signal competitive at
the BTS.
RF200 - 399
Test Mobile Transmit Power
Average
-16 dbm
With this user only
Responding to the BTS

closed-loop power control
instructions, the test mobile
operates at a higher transmit
power while competing with
many other users.
August, 2007
Average
-10 dbm
While max users
active
Why does all this data bounce
around so much?
1. Random motion of users
2. Rayleigh fading
3. Users varying vocoder rates
4. Interference from elsewhere
RF200 - 400
System-Side Data: Channel Element Usage

BTS
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
Date
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
11/3/98
Totals for
Start
MOU
MOU
MOU
MOU
Time
End Time MOU CE Traffic
CE/User Alpha
Beta
Gamma %SHO
Max TCE
7:00:00
7:30:00
256.73
130.11
1.97
37.2
58.52
34.38
49.32
23
8:00:00
8:30:00
265.42
145.49
1.82
45.22
62.49
37.78
45.18
17
8:30:00
9:00:00
342.7
186.94
1.83
52.01
90.66
44.28
45.45
18
9:00:00
9:30:00
317.5
172.02
1.85
43.67
79.94
48.4
45.82
21
9:30:00 10:00:00
408.81
245.55
1.66
78.35
92.33
74.87
39.93
22
10:00:00 10:30:00
288.33
138.41
2.08
46.61
60.9
30.91
52
16
10:30:00 11:00:00
334.61
195.06
1.72
59.71
81.78
53.58
41.71
22
10:30:00 11:00:00
289.53
161.27
1.8
60.04
60.48
40.75
44.3
18
11:00:00 11:30:00
366.75
210.19
1.74
70.51
91.65
48.03
42.69
21
12:00:00 12:30:00
299.25
156.26
1.92
53.34
63.01
39.91
47.78
18
12:00:00 12:30:00
343.03
196.39
1.75
60.06
83.54
52.79
42.75
22
13:00:00 13:30:00
327.2
225.23
1.45
71.01
78.72
75.51
31.16
31
13:00:00 13:30:00
316.68
168.14
1.88
54.19
68.32
45.62
46.9
18
13:30:00 14:00:00
270.9
163.34
1.66
57.55
55.8
49.99
39.7
18
14:00:00 14:30:00
266.42
137.25
1.94
42.92
48.73
45.6
48.48
17
15:00:00 15:30:00
323.56
193.92
1.67
56.77
79.3
57.85
40.07
20
15:00:00 15:30:00
427.2
269.9
1.58
83.71
100.68
85.52
36.82
23
15:30:00 16:00:00
316.61
191.03
1.66
56.15
82.61
52.27
39.66
21
16:00:00 16:30:00
458.76
274.99
1.67
77.06
123.62
74.31
40.06
23
17:00:00 17:30:00
444.98
244.12
1.82
81.45
94.16
68.51
45.14
24
17:30:00 18:00:00
414.68
233.43
1.78
84.75
86.33
62.35
43.71
24
18:00:00 18:30:00
354.47
180.47
1.96
66.13
74.77
39.57
49.09
19
BTS 196
9783.79 5348.84
1.83 1760.71 2109.54 1478.61
45.33
31
The number of channel elements active on this BTS reaches its highest value
for the day during the 30-minute period of our experiment.
August, 2007
RF200 - 401
System-Side Data: BTS Blocks

Cell
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
196
Start
Blocks
Blocks
Blocks
SHO Blk SHO Blk SHO Blk Succ
Succ
Start Date Time
End Time No TCE No Fwd
No Rev
No TCE No Fwd
No Rev
Calls
SHO
11/3/98
8:00:00
8:30:00
0
0
0
0
0
0
66
988
11/3/98
8:30:00
9:00:00
0
0
0
0
0
0
112
934
11/3/98
9:00:00
9:30:00
0
0
0
0
0
0
126
907
11/3/98
9:30:00 10:00:00
0
0
0
0
0
0
160
1099
11/3/98 10:00:00 10:30:00
0
0
0
0
0
0
77
853
11/3/98 10:30:00 11:00:00
0
0
0
0
0
0
121
1009
11/3/98 10:30:00 11:00:00
0
0
0
0
0
0
102
924
11/3/98 11:00:00 11:30:00
0
0
0
0
0
0
132
905
11/3/98 12:00:00 12:30:00
0
0
0
0
0
0
102
885
11/3/98 12:00:00 12:30:00
0
0
0
0
0
0
105
852
11/3/98 13:00:00 13:30:00
0
20
0
0
0
0
172
1018
11/3/98 13:00:00 13:30:00
0
0
0
0
0
0
97
913
11/3/98 13:30:00 14:00:00
0
0
0
0
0
0
117
744
11/3/98 14:00:00 14:30:00
0
0
0
0
0
0
83
953
11/3/98 15:00:00 15:30:00
0
0
0
0
0
0
132
924
11/3/98 15:00:00 15:30:00
0
0
0
0
0
0
149
1103
11/3/98 15:30:00 16:00:00
0
0
0
0
0
0
119
828
11/3/98 16:00:00 16:30:00
0
0
0
0
0
0
129
1064
11/3/98 17:00:00 17:30:00
0
1
0
0
0
0
128
1044
11/3/98 17:30:00 18:00:00
0
0
0
0
0
0
129
914
11/3/98 18:00:00 18:30:00
0
0
0
0
0
0
96
979
Totals for BTS 196
0
21
0
0
0
0
3140
28102
The BTS experiences 20 cases of blockage due to no forward power available

during the 30-minute period of our experiment. The only other time during the
day when it experienced ANY such blocks was 17:00-17:30, when there was
only one despite traffic levels actually higher than during our experiment.
August, 2007
RF200 - 402
System-Side Data: BTS Blocks, Access Failures
Site
=====
196X
196Y
196Z
Call
Att.
=====
Call
Succ.
=====
55
111
95
%
Total
% Tot
BTS
%BTS
Acc.
%Acc.
Screen
%Scr.
Calls
%
Succ.
Block
Block
Block
Block
Fail
Fail
Calls
Calls
Drop
Drop
=====
=====
=====
=====
=====
=====
=====
=====
=====
=====
=====
54
98.18
1
1.82
0
0
0
0
0
0
0
0
110
99.1
0
0
0
0
1
0.9
0
0
4
3.64
93
97.89
1
1.05
1
1.05
1
1.05
0
0
0
0
The sector hit by our experiment shows the worst BTS blocks and Access
Failures.
August, 2007
RF200 - 403
RF200 Appendix II
CDMA
CDMA Information
Information Resources
Resources
Bibliography
Bibliography -- Web
Web Links
Links
August, 2007
RF200 - 404
Bibliography, 3G Air Interface Technologies

"Wireless Network Evolution 2G to 3G" by Vijay K. Garg. 764pp. 2002 Prentice-Hall, Inc.
ISBN 0-13-028077-1. $130. Excellent technical tutorial and reference. The most
complete and comprehensive technical detail seen in a single text on all these
technologies: IS-95 2G CDMA, CDMA2000 3G CDMA, UMTS/WCDMA, Bluetooth,
WLAN standards (802.11a, b, WILAN). Includes good foundation information on
CDMA air interface traffic capacity, CDMA system design and optimization, and
wireless IP operations. Excellent level of operational detail for IS-95 systems operating
today as well as thorough explanations of 2.5G and 3G enhancements.
3G Wireless Demystified by Lawrence Harte, Richard Levine, and Roman Kitka
488pp. Paperback, 2001 McGraw Hill, ISSBN 0-07-136301-7 $50. For both non-technical
and technical readers. An excellent starting point for understanding all the major
technologies and the whole 3G movement. Comfortable plain-language explanations
of all the 2G and 3G air interfaces, yet including very succinct, complete, and
rigorously correct technical details. You will still want to read books at a deeper
technical level in your chosen technology, and may sometimes turn to the applicable
standards for finer details. This book will give you how your technology relates in the
big picture, and probably all you care to know about technologies other than your own.
"3G Wireless Networks" by Clint Smith and Daniel Collins. 622pp. Paperback. 2002
McGraw-Hill, ISBN 0-07-136381-5. $60. An excellent overview of all 3G technologies
coupled with good detail of network architectures, channel structures, and general
operational details. Good treatment of both CDMA2000 and UMTS/WCDMA systems.
WCDMA: Towards IP Mobility and Mobile Internet by Tero Ojanpera and Ramjee
Prasad. 476pp. 2001 Artech House, ISSBN 1-58053-180-6. $100. A complete and
definitive work on UMTS (good CDMA2000, too!). CDMA principles, Mobile Internet,
RF Design, Air Interface, WCDMA FDD standard, WCDMA TDD, CDMA2000,
Performance, Hierarchical Cell Structures, Implementation, Network Planning, Basic
IP Principles, Network Architectures, Standardization, Future Directions.
August, 2007
RF200 - 405
More Bibliography,
3G Air Interface Technologies
The UMTS Network and Radio Access Technology by
Dr. Jonathan P. Castro, 354 pp. 2001 John Wiley,
ISBN 0 471 81375 3, $120. An excellent, wellorganized, and understandable exploration of UMTS.
Includes radio interface, channel explanations, link
budgets, network architecture, service types, ip
network considerations, a masterful tour de force
through the entire subject area. Very readable, too!
WCDMA for UMTS by Harri Holma and Antti Toskala,
322 pp. 2000 Wiley, ISBN 0 471 72051 8, $60. Very
good overall treatment of UMTS. Excellent
introduction to 3G and summary of standardization
activities, every level of UMTS/UTRA. Good overview
of CDMA-2000, too!
The GSM Network - GPRS Evolution: One Step
Towards UMTS 2nd Edition by Joachim Tisal,
227pp. paperback, 2001 Wiley, ISBN 0 471 49816 5,
$60. Readable but not overwhelming introduction to
GSM in all its aspects (140pp), DECT (11pp), GPRS
(6pp), UMTS (7pp), WAP (25pp), EDGE (10pp).
August, 2007
RF200 - 406
Bibliography, The IP Aspect of 3G

Mobile IP: Design, Principles and Practices by Charles E. Perkins, 275 pp., 200,
1998 Addison-Wesley, ISBN 0-201-63469-4. $60. Comprehensive view of Mobile
IP including home and foreign agents, advertisement, discovery, registration,
datagrams, tunneling, encapsulation, route optimization, handoffs, firewalls, IPv6,
DHCP. Tour-de-force of mobile IP techniques.
Mobile IP Technology for M-Business by Mark Norris, 291 pp., 2001 Artech House,
ISSBN 1-58053-301-9. $67. GPRS overview and background, Mobile IP,
Addressing, Routing, M-business, future prospects, IPv4, IPv6, Bluetooth & IrDA
summaries.
TCP/IP Explained by Phillip Miller, 1997 Digital Press, ISBN 1-55558-166-8, 518pp.
$50. In-depth understanding of the Internet protocol suite, network access and
link layers, addressing, subnetting, name/address resolution, routing, error
reporting/recovery, network management. IF youre not already strong in TCP/IP,
youll need this to fully master Mobile IP.
Cisco Networking Academy Program: First-Year Companion Guide edited by Vito
Amato, 1999 Cisco Press, ISBN 1-57870-126-0, 438pp. Textbook supporting a
year-long course on networking technologies for aspiring LAN/WAN (and 3G)
technicians and engineers. It covers every popular networking technology
(including all its elements and devices) in deep and practical detail. Excellent
real-world understanding of TCP/IP, as well as the nuts-and-bolts of everything
from physical components to protocols to actual devices such as routers,
switches, etc. You might even want to take the evening courses at a local
community college near you.
Cisco Networking Academy Program: Engineering Journal and Workbook, Volume I
edited by Vito Amato, 1999 Cisco Press, ISBN 1-57870-126-x, 291pp. The
workbook for the First Year Companion Guide above. If you want some external
structure in your self-study, this workbook will hold your hand as you climb every
step of the ladder, and will lead you step by step through the sister textbook,
ensuring you absorb everything you need to know.
August, 2007
RF200 - 407
Bibliography - General CDMA

IS-95 CDMA and CDMA2000: Cellular/PCS Systems
Implementation by Vijay K. Garg. 422 pp. 2000 Prentice Hall,
ISBN 0-13-087112-5, $90. IS-95 and CDMA2000 Access
technologies, DSSS, IS-95 air interface, channels, call processing,
power control, signaling, soft handoff, netw. planning, capacity,
data. CDMA2000 layers, channels, coding, comparison w/
WCDMA.
CDMA Systems Engineering Handbook by Jhong Sam Lee and
Leonard E. Miller, 1998 Artech House, ISBN 0-89006-990-5.
Excellent treatment of CDMA basics and deeper theory, cell and
system design principles, system performance optimization,
capacity issues. Recommended.
CDMA RF System Engineering by Samuel C. Yang, 1998 Artech
House, ISBN 0-89006-991-3. Good general treatment of CDMA
capacity considerations from mathematical viewpoint.
CDMA Internetworking: Deploying the Open A-Interface by Low and
Schneider. 616 pp. 2000 Prentice Hall, ISBN 0-13-088922-9, $75.
A tour-de-force exposition of the networking between the CDMA
BSC, BTS, and mobile, including messaging and protocols of IS634. Chapters on SS7, Call Processing, Mobility Management,
Supplementary Services, Authentication, Resource Management
(both radio and terrestrial), 3G A-Interface details. One-of-a-kind
work!
"CDMA: Principles of Spread Spectrum Communication" by Andrew J.
Viterbi. 245 p. Addison-Wesley 1995. ISBN 0-201-63374-4, $65.
Very deep CDMA Theory. Prestige collectors item.
August, 2007
RF200 - 408
Bibliography - General Wireless

Mobile and Personal Communication Services and
Systems by Raj Pandya, 334 pp. 2000 IEEE Press, $60.
IEEE order #PC5395, ISBN 0-7803-4708-0. Good
technical overview of AMPS, TACS< NMT, NTT, GSM,
IS-136, PDC, IS-95, CT2, DECT, PACS, PHS, mobile
data, wireless LANs, mobile IP, WATM, IMT2000
initiatives by region, global mobile satellite systems,
UPT, numbers and identities, performance benchmarks.
Wireless Telecom FAQs by Clint Smith, 2001 McGraw Hill,
ISBN 0-07-134102-1. Succint, lucid explanations of
telecom terms in both wireless and landline technologies.
Includes cellular architecture, AMPS, GSM, TDMA,
iDEN, CDMA. Very thorough coverage; an excellent
reference for new technical people or anyone wishing for
clear explanations of wireless terms.
"Mobile Communications Engineering" 2nd. Edition by
William C. Y. Lee. 689 pp. McGraw Hill 1998 $65. ISBN
0-07-037103-2 Lees latest/greatest reference work on
all of wireless; well done.
August, 2007
RF200 - 409
Web Links and Downloadable Resources

Scott Baxter: http://www.howcdmaworks.com
Latest versions of all courses are downloadable.
Category - Username - Password
Intro - (none required) - (none required)
RF/CDMA/Performance - shannon - hertz
3G - generation - third
Grayson - telecom - allen
Agilent - nitro - viper
Dr. Ernest Simos Space2000:
http://www.cdmaonline.com/ and
http://www.3Gonline.com/
CDG: http://www.cdg.org (check out the digivents
multimedia viewable sessions)
The IS-95 and IS-2000 CDMA trade marketing
webside, CDMA cheerleaders.
GSM: http://www.gsmworld.com
The GSM Association website. Worldwide GSM
marketing cheerleaders but also includes some
excellent GSM and GPRS technical overview
whitepapers and documents; latest user figures.
RCR News: http://www.rcrnews.com
Wireless Industry trade publication - regulatory,
technical, business, marketing news.
Subscribers can access text archives of past
articles; very handy in researching events.
August, 2007
RF200 - 410
More Web Links

3GPP: http://www.3gpp.org/
The operators harmonization group concerned mainly with
ETSI-related standards
3GPP2: http://www.3gpp2.org/
The operators harmonization group concerned mainly with IS95-derived CDMA standards
ITU: http://www.itu.int/imt/
ETSI: http://www.etsi.fr/
UMTS forum: http://www.umts-forum.org/
GSM MoU: http://www.gsmworld.com/
TIA: http://www.tiaonline.org/
T1: http://www.t1.org/
ARIB: http://www.arib.or.jp/arib/english/index.html
TTC: http://www.ttc.or.jp/
TTA: http://www.tta.or.kr/
ETRI: http://www.etri.re.kr/
RAST: http://www.rast.etsi.fi/
August, 2007
RF200 - 411

RF 200

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RF 200

Încărcat de

Drepturi de autor:

Formate disponibile

Course RF200

RF200 v5.9 (c) 2007 Scott Baxter

RF200 v5.9 (c) 2007 Scott Baxter

RF200 v5.9 (c) 2007 Scott Baxter

Welcome to Course RF200

RF200 v5.9 (c) 2007 Scott Baxter

Good Performance is so Simple!!

Q One, Two, or Three good signals in handoff

RF200 v5.9 (c) 2007 Scott Baxter

Good Performance is so Simple!!

Q One, Two, or Three good signals in handoff

In principle, a COW next door can

1. But who has enough regular cells OR cows or money to

RF200 v5.9 (c) 2007 Scott Baxter

Bad Performance Has Many Causes

BTS Sector Transmitter

Q Weak Signal / Coverage Hole

RF200 v5.9 (c) 2007 Scott Baxter

What is Performance Optimization?

RF200 v5.9 (c) 2007 Scott Baxter

Performance Optimization Phases/Activities

Cover desired area;

Plan cells to effectively cover

Ensure cells properly

Drive-test: coverage, all

All handoffs occur;

Detect, Investigate, Resolve

Ensure present plant

Watch stats: Drops, Blocks,

Watch capacity indicators;

Traffic analysis and

Predict sector and area

RF200 v5.9 (c) 2007 Scott Baxter

RF200 v5.9 (c) 2007 Scott Baxter

RF200 v5.9 (c) 2007 Scott Baxter

The Basic Format of CDMA Messages

NUM_PILOTS occurrences of this field:

RF200 v5.9 (c) 2007 Scott Baxter

Message Vocabulary: Acquisition & Idle States

Sync Channel Msg

General Page Msg

System Parameters Msg

CDMA Channel List Msg

Base Station Acknowledgment

Feature Notification Msg

Page Response Msg

Service Redirection Msg

Status Request Msg

Status Response Msg

SSD Update Msg

TMSI Assignment Msg

Data Burst Msg

Data Burst Msg

RF200 v5.9 (c) 2007 Scott Baxter

Message Vocabulary: Conversation State

Reverse Traffic Channel

Service Request Msg

Service Request Msg

Service Response Msg

Service Response Msg

TMSI Assignment Msg

Service Connect Msg