rf200

August, 2007 RF200 - 1RF200 v5.9 (c) 2007 Scott Baxter

Wireless CDMA RF Performance Optimization

Wireless CDMA RF Performance Optimization

Course RF200


Contents

Chapter 1. Introduction2. Foundation Topics

Layer-3 MessagingCall ProcessingPerformance Indicators and Problem SignaturesPN Planning and Search Windows

2. Analyzing System PerformanceSystem Data and Analysis Techniques

3. Mobile Field Tools and Data Analysis Autonomous Mobile Data CollectionConventional Field Data Collection Tools

4. Multiple Carrier Systems: Operating Principles and Analysis5. Applied Optimization 6. 1xRTT Optimization IssuesAppendix I. Cell Loading ExampleAppendix II. CDMA/3g1x Books, Publications, Web Resources


Introduction to Performance Optimization

Introduction to Performance Optimization

Course RF200


Welcome to Course RF200

Course RF100 is an introduction to RF and CDMA principles. Aftercompleting it, you should be familiar with:

• General RF system design principles• CDMA technology - principles, channels, network basics• key fundamentals of Messaging and Call Processing

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 you’ll see


Good Performance is so Simple!!

One, Two, or Three good signals in handoff• Composite Ec/Io > -10 db

Enough capacity• No resource problems – I’ve got what I

need

BTS BTS

BTS

Pilot

Paging

TrafficChannels

In use

availablepower

Sync

BTS

A

BTS

B

BTS

C

Ec/Io -10

FORWARDLINK

A


Good Performance is so Simple!!

One, Two, or Three good signals in handoff• Composite Ec/Io > -10 db

Enough capacity• No resource problems – I’ve got what I

need

BTS BTS

BTS

Pilot

Paging

TrafficChannels

In use

availablepower

Sync

BTS

A

BTS

B

BTS

C

Ec/Io -10

FORWARDLINK

In principle, a COW next door can solve almost any CDMA problem!

Reality Check: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.


Bad Performance Has Many CausesWeak Signal / Coverage HolePilot Pollution

• Excessive Soft HandoffHandoff 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

Pilot “Surprise” ambush; Slow HandoffsPN Plan errorsSlow Data Problems: RF or IP congestionImproper cell or reradiator configurationHardware and software failuresBut on analysis, all of these problems’ bad effects happen because the simple few-signal ideal CDMA environment isn’t possible.

360

+41

+8

360+33cA

BBTS

BTS

BTS BPN 99

BTS APN 100

1 mile 11 miles

ACTIVE SEARCH WINDOW

xPilot

PagingSync

TrafficChannels

In Use

NoAvailablePower!B

TS Sector Transmitter

CEsVocodersSelectors

BTS Rx PwrOverload


What is Performance Optimization?

The words “performance optimization” mean different things to different people, viewed from the perspective of their own jobsSystem Performance Optimization includes many different smaller processes at many points during a system’s life

• recognizing and resolving system-design-related issues (can’t 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


Performance Optimization Phases/Activities

hello

RF Design and Cell Planning

New Cluster Testing and

Cell Integration

Solve SpecificPerformance

Problems

Well-System Performance Management

Capacity Optimization

Growth Management:

Optimizing both Performance and Capital

Effectiveness

Cover desired area; have capacity for anticipated traffic

Ensure cells properly constructed and

configured to give normal performance

Identify problems from complaints or statistics; fix them!

Ensure present ‘plant’is giving best possible

performance

Manage congested areas for most

effective performance

Overall traffic increases and congestion;

competition for capital during tight times

Phase Drivers/Objectives Activities Main Tools Success Indicators

Plan cells to effectively cover as needed and divide traffic

load appropriately

Drive-test: coverage, all handoff boundaries, all call

events and scenarios

Detect, Investigate, Resolve performance problems

Watch stats: Drops, Blocks, Access Failures; identify/fix hot

spots

Watch capacity indicators; identify problem areas, tune parameters & configuration

Predict sector and area exhaustion: plan and validate effective growth plan, avoid

integration impact

Prop. Models,Test Transmitters,

planning tools Model results

Drive-test tools;cell diagnostics and

hardware test

All handoffs occur; all test cases

verified

Drive-test tools, system stats,

customer reports

Identified problems are

resolved

System statisticsAcceptable levels and good trends for all indicators

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


CDMA2000 Layer 3 MessagesCDMA2000 Layer 3 Messages

Course RF200


Messages in CDMA

In CDMA, most call processing events are driven by messagesSome CDMA channels exist for the sole purpose of carrying messages; they never carry user’s 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

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 doAll CDMA messages have very similar structure, regardless of thechannel on which they are sent


The Basic Format of CDMA Messages

CDMA messages on both forward and reverse traffic channels are normally sent via dim-and-burstMessages include many fields of binary dataThe first byte of each message identifies message type: this allows the recipient to parse the contentsTo ensure no messages are missed, all CDMA messages bear serial numbers and important messages contain a bit requesting acknowledgmentMessages not promptly acknowledged are retransmitted several times. If not acknowledged, the sender may release the callField data processing tools capture and display the messages for study

MSG_TYPE (‘00000110’)

ACK_SEQ

MSG_SEQ

ACK_REQ

ENCRYPTION

ERRORS_DETECTED

POWER_MEAS_FRAMES

LAST_HDM_SEQ

NUM_PILOTS

PILOT_STRENGTH

RESERVED (‘0’s)

8

3

3

1

2

5

10

2

4

6

0-7

NUM_PILOTS occurrences of this field:

Field Length (in bits)

EXAMPLE: A POWER MEASUREMENT

REPORT MESSAGE

t


Message Vocabulary: Acquisition & Idle StatesSync Channel

Sync Channel Msg

Pilot Channel

No Messages

Paging Channel

Access Parameters Msg

System Parameters Msg

CDMA Channel List Msg

Extended SystemParameters Msg

Extended NeighborList Msg

Global ServiceRedirection Msg

Order Msg•Base Station Acknowledgment

•Lock until Power-Cycled• Maintenance required

many others…..

AuthenticationChallenge Msg

Status Request Msg

Feature Notification Msg

TMSI Assignment Msg

Channel AssignmentMsg

SSD Update Msg

Service Redirection Msg

General Page Msg

Null Msg Data Burst Msg

Access Channel

Registration Msg

Order Msg• Mobile Station Acknowldgment• Long Code Transition Request

• SSD Update Confirmationmany others…..

Origination Msg

Page Response Msg

Authentication ChallengeResponse Msg

Status Response Msg

TMSI AssignmentCompletion Message

Data Burst Msg

BTS


Message Vocabulary: Conversation State

Reverse Traffic Channel

Order Message• Mobile Sta. Acknowledgment

•Long Code Transition Request

• SSD Update Confirmation• Connect

Authentication ChallengeResponse Msg

Flash WithInformation Msg

Data Burst Message

Pilot StrengthMeasurement Msg

Power MeasurementReport Msg

Send Burst DTMF Msg

OriginationContinuation Msg

Handoff Completion Msg

Parameters ResponseMessage

Service Request Msg

Service Response Msg

Service ConnectCompletion Message

Service Option ControlMessage

Status Response Msg

TMSI AssignmentCompletion Message

Forward Traffic ChannelOrder Msg

• Base Station Acknowledgment • Base Station Challenge

Confirmation• Message Encryption Mode

AuthenticationChallenge Msg

Alert WithInformation Msg

Data Burst Msg

Analog HandoffDirection Msg

In-Traffic SystemParameters Msg

Neighbor ListUpdate Msg

Send Burst DTMF Msg

Power ControlParameters Msg.

Retrieve Parameters Msg

Set Parameters Msg

SSD Update Msg

Flash WithInformation Msg

Mobile StationRegistered Msg

Status Request Msg

Extended HandoffDirection Msg

Service Request Msg

Service Response Msg

Service Connect Msg

Service OptionControl Msg

TMSI Assignment Msg


CDMA Call Processing BasicsCDMA Call Processing Basics

Course RF200


Troubleshooting Call Processing

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

Troubleshooting focuses on the desired call events• What is the desired sequence of events?• Compare the actual sequence of events.

– What’s missing or wrong? Why did it happen?Messaging is a major blow-by-blow troubleshooting toolRF indications reveal the transmission risks and the channel configurations

Bottom Line: To troubleshoot effectively, you’ve got to know call processing steps and details AND the RF basis of the transmission


Let's Acquire The System!Let's Acquire The System!

Course RF200


ACCESS CHANNEL

SYNC CHANNEL

PAGING CHANNEL

System Acquisition Messaging

PROBE INFORMATION

SYNC CHANNEL MESSAGE

SYSTEM PARAMETERSMESSAGE

ACCESS PARAMETERSMESSAGE

NEIGHBOR LISTMESSAGE

EXTENDED SYSTEMPARAMETERS MSG

CDMA CHANNEL LISTMESSAGE

GLOBAL SERVICEREDIRECTION MSG REGISTRATION

MESSAGE


What’s In a Handset? How does it work?

ReceiverRF SectionIF, Detector

TransmitterRF Section

Vocoder

Digital Rake Receiver

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

Pilot SearcherPN xxx Walsh 0

Viterbi Decoder,Convl. Decoder,Demultiplexer

CPUDuplexer

TransmitterDigital Section

Long Code Gen.

Open Loop Transmit Gain Adjust

Messages

Messages

Audio

Audio

Packets

Symbols

SymbolsChips

RF

RF

AGC

time-

alig

ned

su

mm

ing

pow

er

Traffic CorrelatorPN xxx Walsh xx

∆tcont

rol

bits


The Task of Finding the Right System

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

HISTORYLIST/MRU

Last-used:FreqFreqFreqFreqFreqetc.

FREQUENCY LISTS:PREFERREDROAMINGLIST/PRL

System1System2System3System4System5etc.

Forward Link Frequencies(Base Station Transmit)

A D B E F C unlic.data

unlic.voice A D B E F C

1850MHz. 1910MHz. 1990 MHz.1930MHz.

1900 MHz. PCS Spectrum

824 MHz. 835 845 870 880 894

869

849

846.5825

890

891.5

Paging, ESMR, etc.A B A B

800 MHz. Cellular Spectrum

Reverse Link Frequencies(Mobile Transmit)


The System Determination AlgorithmAt turnon, Idle mobiles use proprietary System Determination Algorithms (SDA) to find the initial CDMA carrier intended for them to useThe 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

Go to last frequency from MRU

Strongest PN, read

SyncIs SID

permitted?

No Signal

Preferred Only Bit 0

Denied SIDRead

Paging Channel

Is better SID

available?

PRLMRU Acq IdxYes

No

Steps from the CDMA standards

Steps from proprietary

SDAs

Proprietary SDA

databases

Start

LegendTypical MobileSystem Determination Algorithm

Best System Found! Begin Normal Paging Channel Operation

Last Resort:GEO escape

Or Analog


1xRTT Acquisition On the Current Frequency: Find Strongest Pilot, Read Sync Channel

001594, Time 16:33:58.838, Record 71913, QcpCdmaLogMsgSyncChanMSG_LENGTH: 28 octetsMSG_TYPE: Sync Channel MessageP_REV: IS-2000 Revision 0MIN_P_REV: J-STD-008SID: 5216 NID: 0PILOT_PN: 168LC_STATE: 0x02 90 9D 0B 49 ACSYS_TIME: 01/25/2006 09:01:15LP_SEC: 14LTM_OFF: -600 minutesDAYLT: NoPRAT: 9600 bpsCDMA_FREQ: 425EXT_CDMA_FREQ: 425SR1_BCCH_SUPPORTED: NoSR3_INCL: No DS_INCL: NoRESERVED: 0


Rake Fingers

Reference PN

Active Pilot

Ec/

Io

00

32K512

ChipsPN

1. Pilot Searcher Scans the Entire Range of PNs

All PN Offsets0

-20

2. Put Rake finger(s) on strongest available PN, decode Walsh 32, and read Sync Channel Message

Handset Rake Receiver

RF≈ x ≈

LO Srch PN??? W0

F1 PN168 W32F2 PN168 W32F3 PN168 W32

Is this the right system

to use?Check the

PRL!


Climbing the GEO Group

When traveling the first signal found is usually not the best one to useWhen the SID and NID are looked up in the PRL, they are far down the list of available choicesThe 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

ROAMING LIST

Roaming List Type: IS-683APreferred Only: FALSEDefault Roaming Indicator: 0Preferred List ID: 10018

ACQUISITION TABLE

INDEX ACQ TYPE CH1 CH2 CH3 CH4 CH5 CH6 CH7 CH8 CH90 6 500 425 825 575 850 325 6251 6 575 625 500 4252 6 50 100 75 475 825 850 175 2503 6 25 200 350 375 725 50 475 175 2504 1 Both5 6 450 500 350 575 6506 6 675 500 600 575 4757 6 250 50 1758 6 550 375 425 6259 6 75 50 175 250

10 6 200 250 175 5011 6 425 500 575 25 325 65012 6 500 575 475 25 67513 6 500 625 350 50 375 775 575 725 42514 6 650 500 675 25 75 425 50 57515 6 25 50 375 350 250 17516 6 425 550 225 725 750 77517 6 200 50 175 375 25018 6 825 850 92519 6 350 325 375 675 25 1175 725 600 10020 6 750 725 77521 6 325 725 350 750 375 775 425 575 62522 6 1150 117523 6 350 875 325 375 117524 6 25 1175 825 200 75 175 25025 6 50 200 25 100 250 7526 6 500 1075 850 82527 1 A28 1 B29 5 A30 5 B31 5 C32 5 D33 5 E34 5 F35 4 A36 4 B37 4 Both38 6 350 82539 6 25 10040 6 675 600 750 850 1175 77541 6 85042 6 65043 6 450 47544 6 325 350 375 1025 1050 107545 6 150 475 625 67546 6 1025 1050 1075

SYSTEM TABLE

INDEX SID NIDNEG/ PREF GEO PRI

ACQ INDEX

ROAM IND

296 4144 65535 Pref NEW SAME 13 1297 4812 65535 Pref SAME MORE 21 1298 205 65535 Pref SAME SAME 4 0299 208 65535 Pref SAME MORE 37 0300 208 65535 Pref SAME SAME 4 0301 342 65535 Pref SAME MORE 37 0302 342 65535 Pref SAME SAME 4 0303 478 65535 Pref SAME SAME 4 0304 1038 65535 Pref SAME SAME 4 0305 1050 65535 Pref SAME SAME 4 0306 1058 65535 Pref SAME SAME 4 0307 1375 65535 Pref SAME SAME 4 0308 1385 65535 Pref SAME MORE 4 0309 143 65535 Pref SAME MORE 37 0310 143 65535 Pref SAME MORE 4 0311 4103 65535 Pref NEW SAME 3 1312 4157 65535 Pref SAME MORE 2 1313 312 65535 Pref SAME SAME 4 0314 444 65535 Pref SAME MORE 37 0315 444 65535 Pref SAME SAME 4 0316 1008 65535 Pref SAME SAME 4 0317 1012 65535 Pref SAME SAME 4 0318 1014 65535 Pref SAME SAME 4 0319 1688 65535 Pref SAME MORE 4 0320 113 65535 Pref SAME MORE 37 0321 113 65535 Pref SAME SAME 4 0322 179 65535 Pref SAME MORE 37 0323 179 65535 Pref SAME SAME 4 0324 465 65535 Pref SAME SAME 4 0325 2119 65535 Pref SAME MORE 4 0326 2094 65535 Pref SAME MORE 4 0327 1005 65535 Pref SAME SAME 4 0328 1013 65535 Pref SAME SAME 4 0

a G

EO G

RO

UP

a G

EO G

RO

UP

Clim

b!

PRL: Preferred Roaming ListProgrammed into each phone by the system

operator; can be updated over the air.


Found it! Now we’re on the Right System

Rake Fingers

Ref.PN

Active Pilot

Ec/

Io

00

32K512

ChipsPN

1. Pilot Searcher Scans the Entire Range of PNs

All PN Offsets0

-20

98/05/24 23:14:09.817 [SCH] MSG_LENGTH = 208 bitsMSG_TYPE = Sync Channel MessageP_REV = 3MIN_P_REV = 2SID = 179NID = 0PILOT_PN = 168Offset IndexLC_STATE = 0x0348D60E013SYS_TIME = 98/05/24 23:14:10.160LP_SEC = 12LTM_OFF = -300 minutesDAYLT = 0PRAT = 9600 bpsRESERVED = 1

2. Put Rake finger(s) on strongest available PN, decode Walsh 32, and read Sync Channel Message



RF≈ x ≈

LO Srch PN??? W0

F1 PN168 W32F2 PN168 W32F3 PN168 W32

If PRL shows:This is the Best

Available System!

Go to thePaging

Channel!


After finding the right system:Normal Paging Channel Operation

After finding the right system:Normal Paging Channel Operation

Course RF200


The Configuration Messages

After reading the Sync Channel, the mobile is now capable of reading the Paging Channel, which it now monitors constantlyBefore it is allowed to transmit or operate on this system, the mobile must collect a complete set of configuration messagesIn IS-95, the configuration messages are sent on the Paging Channel, repeated every 1.28 secondsIn CDMA2000 systems, the configuration messages may be sent on the separate F-BCH channel

• This would be indicated as SR1_BCCH_SUPPORTED = 1There are six possible types of configuration messages; some areoptional; and they may happen in any orderThe 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


Reading the Configuration Messages

Rake Fingers

Reference PN

Active Pilot

Ec/

Io

00

32K512

ChipsPN

All PN Offsets0

-20

Keep Rake finger(s) on strongest available PN, monitor Walsh 1,

the Paging Channel

Read the Configuration Messages

Access Parameters Msg

System Parameters Msg

CDMA Channel List Msg

Extended SystemParameters Msg (*opt.)

(Extended*) NeighborList Msg

Global ServiceRedirection Msg (*opt.)

Now we’re ready to operate!!


RF≈ x ≈

LO Srch PN??? W0

F1 PN168 W01F2 PN168 W01F3 PN168 W01


01/18/2006 16:19:51MSG_LENGTH: 19 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Access Parameters MessagePILOT_PN: 4ACC_MSG_SEQ: 4ACC_CHAN: 1 Access Channel(s)NOM_PWR: 0 dB INIT_PWR: 0 dBPWR_STEP: 4 dBNUM_STEP: 5 Probe(s)MAX_CAP_SZ: 10 ACH FramesPAM_SZ: 4 ACH Frame(s)PSIST(0-9): 0PSIST(10): 0PSIST(11): 0PSIST(12): 0PSIST(13): 0PSIST(14): 0PSIST(15): 0MSG_PSIST: 1.00REG_PSIST: 1.00PROBE_PN_RAN: 127 PN chip(s)ACC_TMO: 320 msPROBE_BKOFF: 1 Slot(s)BKOFF: 1 Slot(s)MAX_REQ_SEQ: 2MAX_RSP_SEQ: 2AUTH_MODE: 0NOM_PWR_EXT: -8 to 7 dB inclusivePSIST_EMG_INCL: NoRESERVED: 0

1xRTT Access Parameters MessageACCESS PARAMETERS MESSAGE

BTS

Any Access Msg

MSProbing

Basic Access Procedure

a Probe Sequencean Access Attempt

Success!

an Access Probe

The Access Parameters message controls all the steps mobiles must perform when they transmit on the Access ChannelMobiles perform a trial-and-error process called “Probing” to get their messages through


Phone Operation on the Access Channel

A sector’s 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!On the access channel, phones are not yet under BTS closed-loop power control!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!The Access Parameters message on the paging channel announces values of all related parameters

ACCESS

RV TFC

BTS

Channel Assnmt. Msg.

Origination Msg

Base Sta. Acknlgmt. Order

TFC frames of 000s

TFC preamble of 000s


Mobile Sta. Ackngmt. Order

Service Connect Msg.

Svc. Connect Complete Msg


Call is Established!

MSProbing

PAGING

FW TFC

PAGING

RV TFC

FW FC

RV TFC

FW TFC

FW TFC

Successful Basic Access Attempt

a Probe Sequencean Access Attempt

Success!

an Access Probe


1xRTT System Parameters Message

000029, Time 15:28:37.607, Record 6330, QcpCdmaLogMsgPagingChanPD: P_REV_IN_USE < 6MSG_TYPE: System Parameters MessagePILOT_PN: 36CONFIG_MSG_SEQ: 1SID: 4379 NID: 15 REG_ZONE: 6TOTAL_ZONES: 3 ZONE_TIMER: 1 minMULT_SIDS: No MULT_NIDS: No BASE_ID: 2155BASE_CLASS: Public PCS SystemPAGE_CHAN: 1 MAX_SLOT_CYCLE_INDEX: 1HOME_REG: Yes FOR_SID_REG: Yes FOR_NID_REG: YesPOWER_UP_REG: Yes POWER_DOWN_REG: YesPARAMETER_REG: NoREG_PRD: 30.89 minBASE_LAT: 37D18'35.00NBASE_LONG: 079D15'19.00WREG_DIST: 0 SRCH_WIN_A: 60 chipsSRCH_WIN_N: 60 chips SRCH_WIN_R: 80 chipsNGHBR_MAX_AGE: 0PWR_REP_THRESH: 2 Bad Frame(s)PWR_REP_FRAMES: 113 frame(s)PWR_THRESH_ENABLE: YesPWR_PERIOD_ENABLE: NoPWR_REP_DELAY: 4 framesRESCAN: No T_ADD: -14.0 dB T_DROP: -16.0 dBT_COMP: 4.0 T_TDROP: 4 secEXT_SYS_PARAMETER: Yes EXT_NGHBR_LIST: YesGEN_NGHBR_LIST: No GLOBAL_REDIRECT: YesPRI_NGHBR_LIST: No USER_ZONE_ID: NoEXT_GLOBAL_REDIRECT: NoEXT_CHAN_LIST: YesRESERVED: 0

SYSTEM PARAMETERS MESSAGE

Who Registers?Why & When?

Search WindowWidths

Handoff Thresholds

# Paging Channels, Slotted Mode period

What other optionalconfiguration messages

exist?


Configuration Messages:Extended System Parameters Message

QcpCdmaLogMsgPagingChan01/18/2006 16:19:51MSG_LENGTH: 21 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Extended System Parameters MessagePILOT_PN: 4 CONFIG_MSG_SEQ: 25DELETE_FOR_TMSI: No USE_TMSI: NoPREF_MSID_TYPE: IMSI and ESNMCC: 1134 IMSI_11_12: 813TMSI_ZONE_LEN: 1 octet TMSI_ZONE: 0BCAST_INDEX: Disable Periodic Broadcast PagingIMSI_T_SUPPORTED: NoP_REV: IS-2000 Revision 0 MIN_P_REV: J-STD-008SOFT_SLOPE: 0 ADD_INTERCEPT: 0 dBDROP_INTERCEPT: 0 dBPACKET_ZONE_ID: 33 MAX_NUM_ALT_SO: 0RESELECT_INCLUDED: No PILOT_REPORT: NoNGHBR_SET_ENTRY_INFO: NoNGHBR_SET_ACCESS_INFO: NoBROADCAST_GPS_ASST: NoQPCH_SUPPORTED: YesNUM_QPCH: 1 QPCH_RATE: 9600 bpsQPCH_POWER_LEVEL_PAGE: 3 dB below Pilot Channel Transmit PowerQPCH_CCI_SUPPORTED: YesQPCH_POWER_LEVEL_CONFIG: 3 dB below Pilot Channel Transmit PowerSDB_SUPPORTED: NoRLGAIN_TRAFFIC_PILOT: 0.000000 dBREV_PWR_CNTL_DELAY_INCL: NoAUTO_MSG_SUPPORTED: No

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


Configuration Messages:Variations of the Neighbor List Message

QcpCdmaLogMsgPagingChan04/03/2002 22:17:52 MSG_LENGTH: 24 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Neighbor List MessagePILOT_PN: 44CONFIG_MSG_SEQ: 47PILOT_INC: 4NGHBR_CONFIG: 0 NGHBR_PN: 216NGHBR_CONFIG: 0 NGHBR_PN: 384NGHBR_CONFIG: 0 NGHBR_PN: 304NGHBR_CONFIG: 0 NGHBR_PN: 472NGHBR_CONFIG: 0 NGHBR_PN: 368NGHBR_CONFIG: 0 NGHBR_PN: 224NGHBR_CONFIG: 0 NGHBR_PN: 324NGHBR_CONFIG: 0 NGHBR_PN: 492NGHBR_CONFIG: 0 NGHBR_PN: 152NGHBR_CONFIG: 0 NGHBR_PN: 24RESERVED: 0

QcpCdmaLogMsgPagingChan04/16/2003 19:08:07MSG_LENGTH: 42 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Extended Neighbor List MessagePILOT_PN: 213CONFIG_MSG_SEQ: 10PILOT_INC: 3NGHBR_CONFIG: 0 NGHBR_PN: 45 SEARCH_PRIORITY: Very High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 381 SEARCH_PRIORITY: Very High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 300 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 198 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 363 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 195 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 27 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 177 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 219 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 207 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 375 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 237 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 21 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 357 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 189 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 210 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 378 SEARCH_PRIORITY: High FREQ_INCL: NoNGHBR_CONFIG: 0 NGHBR_PN: 42 SEARCH_PRIORITY: High FREQ_INCL: NoRESERVED: 0


Configuration Messages:More Variations of the Neighbor List Message

QcpCdmaLogMsgPagingChan04/03/2002 22:43:16MSG_LENGTH: 33 octets PD: P_REV_IN_USE < 6MSG_TYPE: General Neighbor List MessagePILOT_PN: 380 CONFIG_MSG_SEQ: 8 PILOT_INC: 4NGHBR_SRCH_MODE: Search PrioritiesNGHBR_CONFIG_PN_INCL: YesFREQ_FIELDS_INCL: No USE_TIMING: NoNUM_NGHBR: 12NGHBR_CONFIG: 0 NGHBR_PN: 212 SEARCH_PRIORITY: Very HighNGHBR_CONFIG: 0 NGHBR_PN: 40 SEARCH_PRIORITY: Very HighNGHBR_CONFIG: 0 NGHBR_PN: 504 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 428 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 32 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 372 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 132 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 448 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 12 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 352 SEARCH_PRIORITY: HighNGHBR_CONFIG: 0 NGHBR_PN: 260 SEARCH_PRIORITY: MediumNGHBR_CONFIG: 0 NGHBR_PN: 184 SEARCH_PRIORITY: MediumNUM_ANALOG_NGHBR: 0 SRCH_OFFSET_INCL: NoADD_PILOT_REC_INCL: No, No, No, No, No, No, No, No, No, No, No, NoSRCH_OFFSET_NGHBR: 0 BCCH_IND_INCL: NoRESQ_ENABLED: No RESQ_DELAY_TIME: 0RESQ_ALLOWED_TIME: 0 RESQ_ATTEMPT_TIME: 0RESQ_CODE_CHAN: 0 RESQ_QOF: 0RESQ_MIN_PERIOD_INCL: No RESQ_MIN_PERIOD: 0 RESQ_NUM_TOT_TRANS_INCL: 0 RESQ_NUM_TOT_TRANS_20MS: 0RESQ_NUM_TOT_TRANS_5MS: 0 RESQ_NUM_PREAMBLE_RC1_RC2: 0RESQ_NUM_PREAMBLE: 0 RESQ_POWER_DELTA: 0NGHBR_RESQ_CONFIGURED: No, No, No, No, No, No, No, No, No, No, No, No


Configuration Messages:CDMA Channel List Message

QcpCdmaLogMsgPagingChan04/03/2002 22:17:52MSG_LENGTH: 11 octetsPD: P_REV_IN_USE < 6MSG_TYPE: CDMA Channel List MessagePILOT_PN: 44CONFIG_MSG_SEQ: 47CDMA_FREQ: 384CDMA_FREQ: 425RESERVED: 0

QcpCdmaLogMsgPagingChan04/03/2002 22:17:52MSG_LENGTH: 10 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Extended CDMA Channel List MessagePILOT_PN: 44CONFIG_MSG_SEQ: 47NUM_FREQ: 1CDMA_FREQ: 384RC_QPCH_SEL_INCL: NoTD_SEL_INCL: NoRESERVED: 0

The CDMA Channel List message lists all carrier frequencies equipped on the current sector for use by IS-95 mobilesThe Extended Channel List message lists all carrier frequencies equipped on the current sector for use by 1xRTT mobilesAfter 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.This set of messages provides a simple way to evenly distribute idle mobiles among the available carriers for traffic balancing reasons


How Hashing Works

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

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


Hashing Examples

Try your own phone in the spreadsheet Hashing.xls (in utilities folder)

Hashing Examples Time between active slots, seconds:v2. 1-28-2000 1.28 2.56 5.12 10.24 20.48 40.96 81.92 163.84

Number of Slots in Mobile's Cycle:16 32 64 128 256 512 1024 2048

Key in red-shadedHow Many

Frequencies?How Many Paging

Channels? Slot Cycle Index:values 2 1 0 1 2 3 4 5 6 7

10 Digit IMSI Use Freq. # Use PCH # Slot# Slot# Slot# Slot# Slot# Slot# Slot# Slot#6153000124 1 1 15 31 63 127 127 383 895 895

6153000125 1 1 11 27 27 27 27 27 539 1563

6153000126 1 1 5 5 5 69 69 69 69 69

6153000127 1 1 3 3 3 67 195 451 451 1475

6153000128 2 1 8 24 24 24 152 152 152 1176

6153000129 2 1 9 25 25 25 25 25 25 25

6153000130 1 1 11 27 27 27 27 27 539 1563

6153000131 2 1 1 1 33 97 225 225 737 737

6153000132 1 1 8 8 40 40 40 40 552 552

6153000133 1 1 3 19 51 115 243 243 755 755


Configuration Messages:Global Service Redirection Message

QcpCdmaLogMsgPagingChan01/05/2005 19:20:09MSG_LENGTH: 15 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Global Service Redirection MessagePILOT_PN: 6 CONFIG_MSG_SEQ: 35REDIRECT_ACCOLC (ACCOLC_0): YesREDIRECT_ACCOLC (ACCOLC_1): YesREDIRECT_ACCOLC (ACCOLC_2): YesREDIRECT_ACCOLC (ACCOLC_3): YesREDIRECT_ACCOLC (ACCOLC_4): YesREDIRECT_ACCOLC (ACCOLC_5): YesREDIRECT_ACCOLC (ACCOLC_6): YesREDIRECT_ACCOLC (ACCOLC_7): YesREDIRECT_ACCOLC (ACCOLC_8): YesREDIRECT_ACCOLC (ACCOLC_9): YesREDIRECT_ACCOLC (ACCOLC_10): NoREDIRECT_ACCOLC (ACCOLC_11): NoREDIRECT_ACCOLC (ACCOLC_12): NoREDIRECT_ACCOLC (ACCOLC_13): NoREDIRECT_ACCOLC (ACCOLC_14): NoREDIRECT_ACCOLC (ACCOLC_15): NoRETURN_IF_FAIL: No DELETE_TMSI: NoEXCL_P_REV_MS: NoRECORD_TYPE: Redirection to An Analog SystemRECORD_LEN: 3 octetsEXPECTED_SID: 0 IGNORE_CDMA: NoSYS_ORDERING: Attempt To Obtain Service On Either System

A Or System B. If Unsuccessful, Attempt Alternate SystemMAX_REDIRECT_DELAY: 0 sec

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


Summary: How Idle Mobiles Choose CDMA CarriersAt turnon, Idle mobiles use proprietary System Determination Algorithms (SDA) to find the initial CDMA carrier intended for them to useOn the paging channel of the idle mobile’s 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)

Go to last frequency from MRU

Strongest PN, read

SyncIs SID

permitted?

No Signal

Preferred Only Bit 0

Denied SIDRead

Paging Channel

CDMA Ch List Message

Global Svc Redir Msg

HASH using IMSI

my ACCOLC? redirect

Is better SID

available?

PRLMRU Acq IdxYes

NoF1F2F3

to Analog

to another CDMA frequency or system

ConfigMessages:

remain

Steps from the CDMA standards

Steps from proprietary

SDAs

Proprietary SDA

databases

Start

Legend

System Determination Algorithm

Last Resort:GEO escape

Or Analog

Idle Mode Carrier Selection


Idle Mode Handoff(“Reselection” by the Mobile)

An idle mobile always uses the best available signal• In idle mode, it isn’t 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 can’t combine sectors, the mobile can only try to stay on top of the strongest one

The mobile’s pilot searcher is constantly checking neighbor pilotsA Mobile might change pilots for either of two reasons:

• It notices another pilot at least 3 db stronger than the currentactive 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

On the new paging channel, if the mobile notices a different SID, NID, or other reason for registration, it re-registers


Idle Mode on the Paging Channel: Meet the Neighbors, track the Strongest Pilot

Ec/

IoAll PN Offsets

00

32K512

ChipsPN

0

-20

Neighbor Set

The phone’s pilot searcher constantly checks the pilots listed in the Neighbor List Message

If the searcher ever notices a neighbor pilot 3 db stronger thanthe 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.

Rake Fingers

Reference PN

Active Pilot

SRCH_WIN_A

SRCH_WIN_N

Mobile Rake RX

Srch PN??? W0

F1 PN168 W01F2 PN168 W01F3 PN168 W01


Improved Reliability for the Access Process

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.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 setupACCESS ENTRY HANDOFF

• mobile can switch sectors after receiving a page but before sending its first probe in response

ACCESS HANDOFF• mobile can switch sectors after successful access while waiting for

traffic channel assignmentChannel Assignment into Soft Handoff (Lucent “CAMSHO”)

• the system can set up the mobile’s initial traffic channel assignment on multiple sectors, allowing the call to begin already in soft handoff


The Access Handoff List

ACCESS_HO_LIST is the key to all the techniques of handoff in access modeAn 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 pilotThe 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”)


Access Handoff, Access Entry HandoffQcpCdmaLogMsgAccessChan 04/16/2003 19:06:56MSG_LENGTH: 42 octets D: P_REV_IN_USE >= 6MSG_ID: Origination Message LAC_LENGTH: 13 octetsACK_SEQ: 7 MSG_SEQ: 5 ACK_REQ: 1VALID_ACK: 0 ACK_TYPE: 0MSID_TYPE: IMSI and ESN MSID_LEN: 9 octetsESN: D:06916245430 H:45F7E2B6IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S includedRESERVED: 0 IMSI_S: 6015737284AUTH_MODE: 0 LAC_PADDING: 0ACTIVE_PILOT_STRENGTH: -9.00 dBFIRST_IS_ACTIVE: Yes FIRST_IS_PTA: No NUM_ADD_PILOTS: 1PILOT_PN_PHASE: PN:189 + 0 chipsPILOT_STRENGTH: -12.50 dB ACCESS_HO_EN: YesACCESS_ATTEMPTED: No MOB_TERM: YesSLOT_CYCLE_INDEX: 5.12 MOB_P_REV: IS-2000 Revision 0SCM: Band Class 1, Dual Mode, Slotted, Continuous, Class IIIREQUEST_MODE: CDMA Only SPECIAL_SERVICE: YesSERVICE_OPTION: Standard: EVRC (8 kbps) PM: NoDIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: NoNUM_FIELDS: 10 CHARi: 6 6 2 3 2 8 9 0 3 9 NAR_AN_CAP: NoPACA_REORIG: User Directed Origination RETURN_CAUSE: Normal AccessMORE_RECORDS: No PACA_SUPPORTED: NoNUM_ALT_SO: 0 DRS: No UZID_INCL: NoCH_IND: Fundamental Channel SR_ID: 1OTD_SUPPORTED: No QPCH_SUPPORTED: YesENHANCED_RC: Yes FOR_RC_PREF: 3 REV_RC_PREF: 3FCH_SUPPORTED: Yes FCH_FRAME_SIZE: Supports only 20 ms Frame SizesFOR_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: Yes RC6: NoREV_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: No RC6: NoDCCH_SUPPORTED: No GEO_LOC_INCL: No REV_FCH_GATING_REQ: Yes RESERVED: 0

In this Origination Message, a mobile is asking for Access Handoff with two sectors:

• its current Active sector• PN189

Access Attempted: NO means it has not sent a probe yet to PN189If 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 insteadIf Channel Assignment into Soft Handoff is enabled, an Extended Channel Assignment Message will assign traffic channels on both the current active PN and PN189


Let’s Register!Let’s Register!

Course RF200


Registration

Registration is the process by which an idle mobile lets the system know it’s awake and available for incoming calls

• this allows the system to inform the mobile’s home switch of the mobile’s 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

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


Mobile Registration Messaging

ACCESS CHANNEL

SYNC CHANNEL

PAGING CHANNEL

PROBE INFORMATION


SYSTEM PARAMETERSMESSAGE

ACCESS PARAMETERSMESSAGE

NEIGHBOR LISTMESSAGE

EXTENDED SYSTEMPARAMETERS MSG

CDMA CHANNEL LISTMESSAGE

GLOBAL SERVICEREDIRECTION MSG REGISTRATION

MESSAGE


Mobile Registration

QcpCdmaLogMsgAccessChan09/22/2004 14:03:08MSG_LENGTH: 21 octetsPD: P_REV_IN_USE < 6MSG_ID: Registration MessageACK_SEQ: 7 MSG_SEQ: 7 ACK_REQ: 1VALID_ACK: 0 ACK_TYPE: 2MSID_TYPE: IMSI and ESNMSID_LEN: 9 octetsESN: D:25411321874 H:FEACC212IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S includedRESERVED: 0 IMSI_S: 8436840009AUTH_MODE: 0REG_TYPE: Zone-BasedSLOT_CYCLE_INDEX: 2.56MOB_P_REV: J-STD-008EXT_SCM: Band Class 1 RESERVED: 0SLOTTED_MODE: Yes RESERVED: 0MOB_TERM: Yes RESERVED: 0

Access Probe Info 09/22/2004 14:03:08Access Probe Sequence Number: 1 Access Probe Number: 1Access Channel Number: 0 PN Randomization delay: 10 Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 1Rx Power: -81.248 Tx Power (Est): 8.248 Tx Gain Adjust: 0

The Registration Message is sent in the form of one or more probes on the Access ChannelMost 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


Feature Notification:You Have Voicemail!Feature Notification:You Have Voicemail!


ACCESS CHANNELPAGING CHANNEL

Voicemail Notification Messaging

PROBE INFORMATION

FEATURE NOTIFICATIONMESSAGE (MSG WTG) MOBILE STATION

ACK. ORDER


QcpCdmaLogMsgRevTrafChan 04/03/2002 22:44:05MSG_LENGTH: 7 octets MSG_TYPE: Order MessageACK_SEQ: 7 MSG_SEQ: 4 ACK_REQ: NoENCRYPTION: Encryption DisabledMSID_TYPE: IMSI and ESN MSID_LEN: 9 octetsESN: D:11600081479 H:74013E47IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0 IMSI_S: 9145899573ORDER: Mobile Station Acknowledgement OrderADD_RECORD_LEN: 0 octet RESERVED: 0

Feature Notification

QcpCdmaLogMsgPagingChan04/03/2002 22:44:05MSG_LENGTH: 16 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Feature Notification MessageACK_SEQ: 2 MSG_SEQ: 7 ACK_REQ: YesVALID_ACK: YesADDR_TYPE: IMSIADDR_LEN: 5 octetsIMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S includedRESERVED: 0IMSI_S: 9145899573RELEASE: NoRECORD_TYPE: Message WaitingRECORD_LEN: 1 octetMSG_COUNT: 1 RESERVED: 0

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.

The mobile confirms it has received the notification by sending a Mobile Station Acknowledgment Order on the access

channel.

Access Probe Info Time Stamp: 04/03/2002 22:44:05Access Probe Sequence Number: 1 Access Probe Number: 1Access Channel Number: 0 PN Randomization delay: 10Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 0Rx Power: -70.9147 Tx Power (Est): -3.08533 Tx Gain Adjust: 2

Test equipment connected to the mobile may show the Access Probe Info,

confirming that a probe was actually sent.


Let’s Receive an IncomingCall!

Let’s Receive an IncomingCall!

Example 4


Receiving an Incoming Call

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


Mobile Termination Messaging

ACCESS CHANNEL

REVERSE TRAFFIC CHANNELFORWARD TRAFFIC CHANNEL

PAGING CHANNEL

PROBE INFORMATIONBASE STATIONACK. ORDER

PAGE RESPONSE MESSAGE

CHANNEL ASSIGNMENTMESSAGE

BASE STATIONACK. ORDER

MOBILE STATIONACK. ORDER

LAYER 2 HANDSHAKE

LAYER 2 HANDSHAKE

SERVICE CONNECTMESSAGE

SERVICE CONNECT COMPLETE MESSAGE

GENERAL PAGEMESSAGE

ALERT WITH INFORMATIONMESSAGE

MOBILE STATIONACK ORDER

CONNECTMESSAGE



Call Termination Messaging (1)QcpCdmaLogMsgPagingChan09/22/2004 13:33:56MSG_LENGTH: 16 octetsPD: P_REV_IN_USE < 6MSG_TYPE: General Page MessageCONFIG_MSG_SEQ: 2ACC_MSG_SEQ: 1CLASS_0_DONE: YesCLASS_1_DONE: YesTMSI_DONE: NoORDERED_TMSIS: NoBROADCAST_DONE: YesRESERVED: 0ADD_LENGTH: 0 octetsPAGE_CLASS: Page With Class 0 IMSIPAGE_SUBCLASS: 0MSG_SEQ: 1IMSI_S: 8436840009SPECIAL_SERVICE: YesSERVICE_OPTION: QUALCOMM: Voice 13K

QcpCdmaLogMsgAccessChan 09/22/2004 13:33:56MSG_LENGTH: 23 octets PD: P_REV_IN_USE < 6MSG_ID: Page Response MessageACK_SEQ: 1 MSG_SEQ: 1 ACK_REQ: 1 VALID_ACK: 1 ACK_TYPE: 2MSID_TYPE: IMSI and ESN MSID_LEN: 9 octetsESN: D:25411321874 H:FEACC212IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0IMSI_S: 8436840009AUTH_MODE: 0 MOB_TERM: YesSLOT_CYCLE_INDEX: 2.56MOB_P_REV: J-STD-008EXT_SCM: Band Class 1 RESERVED: 0SLOTTED_MODE: Yes RESERVED: 0REQUEST_MODE: Either Wide Analog or CDMA OnlySERVICE_OPTION: QUALCOMM: Voice 13KPM: No NAR_AN_CAP: No RESERVED: 0

Access Probe Info Time Stamp: 9/22/2004 13:33:56.000Access Probe Sequence Number: 1 Access Probe Number: 1Access Channel Number: 0 PN Randomization delay: 10Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 0Rx Power: -70.9147 Tx Power (Est): -3.08533 Tx Gain Adjust: 2


Call Termination Messaging (2)

QcpCdmaLogMsgPagingChan 09/22/2004 13:33:57MSG_LENGTH: 13 octets PD: P_REV_IN_USE < 6MSG_TYPE: Order MessageACK_SEQ: 1 MSG_SEQ: 0 ACK_REQ: NoVALID_ACK: Yes ADDR_TYPE: ESN ADDR_LEN: 4 octetsESN: D:25411321874 H:FEACC212ORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets

QcpCdmaLogMsgPagingChan 09/22/2004 13:33:57MSG_LENGTH: 18 octets PD: P_REV_IN_USE < 6MSG_TYPE: Channel Assignment MessageACK_SEQ: 1 MSG_SEQ: 1 ACK_REQ: NoVALID_ACK: Yes ADDR_TYPE: ESN ADDR_LEN: 4 octetsESN: D:25411321874 H:FEACC212ASSIGN_MODE: Extended Traffic Channel AssignmentADD_RECORD_LEN: 5 octets FREQ_INCL: Yes RESERVED: 0BYPASS_ALERT_ANSWER: NoDEFAULT_CONFIG: Multiplex Option 1 and Radio Config 1 For Both FTC and RTCGRANTED_MODE: MS use Service Configuration of default Multiplex Option and Transmission RatesCODE_CHAN: 36 FRAME_OFFSET: 12.50 msENCRYPT_MODE: Encryption DisabledBAND_CLASS: 1.850 to 1.990 GHz BandCDMA_FREQ: 1175 C_SIG_ENCRYPT_MODE_INCL: NoRESERVED: 0

The Base Station Acknowledgment Order tells the mobile to stop sending probesThe Channel Assignment Message tells the mobile the walsh code and other details of its traffic channel



QcpCdmaLogMsgForTrafChan09/22/2004 13:33:57MSG_LENGTH: 8 octetsMSG_TYPE: Order MessageACK_SEQ: 7 MSG_SEQ: 0 ACK_REQ: YesENCRYPTION: Encryption DisabledUSE_TIME: No ACTION_TIME: 0 msORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

QcpCdmaLogMsgRevTrafChan09/22/2004 13:33:57MSG_LENGTH: 10 octetsMSG_TYPE: Pilot Strength Measurement MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: YesENCRYPTION: Encryption DisabledREF_PN: 8 PILOT_STRENGTH: -9.00 dB KEEP: YesPILOT_PN_PHASE: PN:0 + 0 chips PILOT_STRENGTH: -8.00 dB KEEP: YesRESERVED: 0

The base station is alreadysending blank frames on

the forward channel,using the assigned Walsh code.

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 acknowledges receiving the mobile’s preamble.

The mobile station acknowledges receiving the Base Station’s 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.



QcpCdmaLogMsgForTrafChan09/22/2004 13:33:57MSG_LENGTH: 21 octetsMSG_TYPE: Service Connect MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: NoENCRYPTION: Encryption DisabledUSE_TIME: No ACTION_TIME: 0 msSERV_CON_SEQ: 0 RESERVED: 0RECORD_TYPE: Service ConfigurationRECORD_LEN: 12 octetsFOR_MUX_OPTION: 2 REV_MUX_OPTION: 2RS2_14400_FOR: Supports 276 bits per F-FCH frameRS2_7200_FOR: Supports 125 bits per F-FCH frameRS2_3600_FOR: Supports 55 bits per F-FCH frameRS2_1800_FOR: Supports 21 bits per F-FCH frameRESERVED: 0RS2_14400_REV: Supports 276 bits per R-FCH frameRS2_7200_REV: Supports 125 bits per R-FCH frameRS2_3600_REV: Supports 55 bits per R-FCH frameRS2_1800_REV: Supports 21 bits per R-FCH frameRESERVED: 0 NUM_CON_REC: 1RECORD_LEN: 5 octets CON_REF: 1SERVICE_OPTION: QUALCOMM: Voice 13KFOR_TRAFFIC: SO Uses Primary Traffic On FTCREV_TRAFFIC: SO Uses Primary Traffic On RTC

QcpCdmaLogMsgRevTrafChan09/22/2004 13:33:57MSG_LENGTH: 6 octetsMSG_TYPE: Service Connect Completion MessageACK_SEQ: 0 MSG_SEQ: 1 ACK_REQ: YesENCRYPTION: Encryption DisabledRESERVED: 0 SERV_CON_SEQ: 0 RESERVED: 0

The Service Connect Message is the system’s proposal to the mobile specifying the technical details of the call:

• Radio Configuration• Multiplex options• Service Option, Vocoder

type• Traffic type to be carried

The mobile can accept by sending a Service Connect Complete Message, or propose something different with a Service Response Message



QcpCdmaLogMsgForTrafChan09/22/2004 13:33:57MSG_LENGTH: 10 octetsMSG_TYPE: Alert With Information MessageACK_SEQ: 1 MSG_SEQ: 2 ACK_REQ: YesENCRYPTION: Encryption DisabledRECORD_TYPE: SignalRECORD_LEN: 2 octetsSIGNAL_TYPE: IS-54B AlertingALERT_PITCH: Medium Pitch SIGNAL: LongRESERVED: 0 RESERVED: 0

QcpCdmaLogMsgRevTrafChan09/22/2004 13:33:58MSG_LENGTH: 7 octetsMSG_TYPE: Order MessageACK_SEQ: 2 MSG_SEQ: 2 ACK_REQ: NoENCRYPTION: Encryption DisabledORDER: Mobile Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

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

The mobile acknowledges the Alert With Information Message, indicating it is now ringing



QcpCdmaLogMsgRevTrafChan09/22/2004 13:33:58MSG_LENGTH: 7 octetsMSG_TYPE: Order MessageACK_SEQ: 3 MSG_SEQ: 3 ACK_REQ: YesENCRYPTION: Encryption DisabledORDER: Connect OrderADD_RECORD_LEN: 0 octetsRESERVED: 0

QcpCdmaLogMsgForTrafChan09/22/2004 13:33:58MSG_LENGTH: 8 octetsMSG_TYPE: Order MessageACK_SEQ: 3 MSG_SEQ: 5 ACK_REQ: NoENCRYPTION: Encryption DisabledUSE_TIME: No ACTION_TIME: 0 msORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octetsRESERVED: 0

Now the switch completes the audio circuit and the two callers can talk!

When the mobile user presses SEND or opens their mouthpiece, the phone sends a Connect Order and the switch connects the trunks for audio


Let’s Make An Outgoing Call!Let’s Make An Outgoing Call!

Course RF200


Placing an Outgoing Call

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


ACCESS CHANNEL


PAGING CHANNEL

Call Origination Messaging

PROBE INFORMATION


ORIGINATION MESSAGE




LAYER 2 HANDSHAKE

LAYER 2 HANDSHAKE




Call Origination Messaging (1)QcpCdmaLogMsgAccessChan 04/03/2002 22:43:16MSG_LENGTH: 43 octets PD: P_REV_IN_USE >= 6MSG_ID: Origination Message LAC_LENGTH: 17 octetsACK_SEQ: 7 MSG_SEQ: 5 ACK_REQ: 1 VALID_ACK: 0 ACK_TYPE: 0MSID_TYPE: IMSI and ESN MSID_LEN: 9 octets ESN: D:11600081479 H:74013E47IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S includedRESERVED: 0 IMSI_S: 4349419020AUTH_MODE: 1 AUTHU: 195061 RANDC: 122 COUNT: 0LAC_PADDING: 0 ACTIVE_PILOT_STRENGTH: -4.00 dBFIRST_IS_ACTIVE: Yes FIRST_IS_PTA: No NUM_ADD_PILOTS: 0MOB_TERM: Yes SLOT_CYCLE_INDEX: 2.56 MOB_P_REV: IS-2000 Revision 0SCM: Band Class 0, Dual Mode, Slotted, Continuous, Class IIIREQUEST_MODE: CDMA Only SPECIAL_SERVICE: YesSERVICE_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 7NAR_AN_CAP: No PACA_REORIG: User Directed OriginationRETURN_CAUSE: Normal Access MORE_RECORDS: NoENCRYPTION_SUPPORTED: Basic Encryption Supported PACA_SUPPORTED: NoNUM_ALT_SO: 0 DRS: No UZID_INCL: No CH_IND: Fundamental Channel SR_ID: 1OTD_SUPPORTED: No QPCH_SUPPORTED: YesENHANCED_RC: Yes FOR_RC_PREF: 3 REV_RC_PREF: 3FCH_SUPPORTED: Yes FCH_FRAME_SIZE: only 20 ms Frame SizesFOR_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: Yes RC6: NoREV_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: No RC6: NoDCCH_SUPPORTED: No GEO_LOC_INCL: YesGEO_LOC_TYPE: Reserved REV_FCH_GATING_REQ: No

Access Probe Info 4/3/2002 22:43:16.000Access Probe Sequence Number: 1 Access Probe Number: 1Access Channel Number: 0 PN Randomization delay: 10 Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 1Rx Power: -81.248 Tx Power (Est): 8.248 Tx Gain Adjust: 0

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

Most message capture test equipment also displays the mobile’s internally-generated “Access Probe Info”, showing technical details of each probe


Call Origination Messaging (2)QcpCdmaLogMsgPagingChan04/03/2002 22:43:16MSG_LENGTH: 13 octets PD: P_REV_IN_USE < 6 MSG_TYPE: Order MessageACK_SEQ: 5 MSG_SEQ: 0 ACK_REQ: No VALID_ACK: Yes ADDR_TYPE: ESNADDR_LEN: 4 octets ESN: D:11600081479 H:74013E47ORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

QcpCdmaLogMsgPagingChan04/03/2002 22:43:16MSG_LENGTH: 29 octets PD: P_REV_IN_USE < 6MSG_TYPE: Extended Channel Assignment MessageACK_SEQ: 5 MSG_SEQ: 1 ACK_REQ: No VALID_ACK: YesADDR_TYPE: ESN ADDR_LEN: 4 octets ESN: D:11600081479 H:74013E47RESERVED_1: 0 ADD_RECORD_LEN: 15 octetsASSIGN_MODE: Enhanced Traffic Channel AssignmentRESERVED_2: 0 FREQ_INCL: YesBAND_CLASS: 800 MHz Cellular Band CDMA_FREQ: 384BYPASS_ALERT_ANSWER: NoGRANTED_MODE: MS use Service Configuration of default Multiplex Option and

Transmission RatesDEFAULT_CONFIG: ReservedFOR_RC: RC 3 REV_RC: RC 3 FRAME_OFFSET: 12.50 msENCRYPT_MODE: Encryption DisabledFPC_SUBCHAN_GAIN: 0.0 dB RLGAIN_ADJ: 0 dB NUM_PILOTS: 0 PilotsCH_IND: Fundamental Channel CH_RECORD_LEN: 7 octetsFPC_FCH_INIT_SETPT: 7.000 dBFPC_FCH_FER: 0.5% - 10% (in units of 0.5%)FPC_FCH_MIN_SETPT: 3.000 dB FPC_FCH_MAX_SETPT: 8.000 dBPILOT_PN: 380 ADD_PILOT_REC_INCL: No PWR_COMB_IND: NoCODE_CHAN_FCH: 33 QOF_MASK_ID_FCH: 0 3X_FCH_INFO_INCL: NoREV_FCH_GATING_MODE: No 3XFL_1XRL_INCL: No RESERVED: 0

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

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


Call Origination Messaging (3)

QcpCdmaLogMsgForTrafChan04/03/2002 22:43:17MSG_LENGTH: 8 octetsMSG_TYPE: Order MessageACK_SEQ: 7MSG_SEQ: 0ACK_REQ: YesENCRYPTION: Encryption DisabledUSE_TIME: NoACTION_TIME: 0 msORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

QcpCdmaLogMsgRevTrafChan04/03/2002 22:43:17MSG_LENGTH: 10 octetsMSG_TYPE: Pilot Strength Measurement MessageACK_SEQ: 0MSG_SEQ: 0ACK_REQ: YesENCRYPTION: Encryption DisabledREF_PN: 380PILOT_STRENGTH: -4.50 dB KEEP: YesPILOT_PN_PHASE: PN:212 + 0 chipsPILOT_STRENGTH: -13.50 dB KEEP: YesRESERVED: 0




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 mobile station acknowledges the base station’s 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.



QcpCdmaLogMsgForTrafChan 04/03/2002 22:43:17 MSG_LENGTH: 31 octetsMSG_TYPE: Service Connect MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: NoENCRYPTION: Encryption Disabled USE_TIME: No ACTION_TIME: 0 msSERV_CON_SEQ: 0 RESERVED: 0 USE_OLD_SERV_CONFIG: 0 SYNC_ID_INCL: NoRECORD_TYPE: Service Configuration RECORD_LEN: 15 octetsFOR_MUX_OPTION: 1 REV_MUX_OPTION: 1RS1_9600_FOR: Supports 172 bits per F-FCH frameRS1_4800_FOR: Supports 80 bits per F-FCH frameRS1_2400_FOR: Supports 40 bits per F-FCH frameRS1_1200_FOR: Supports 16 bits per F-FCH frameRESERVED: 0RS1_9600_REV: Supports 172 bits per R-FCH frameRS1_4800_REV: Supports 80 bits per R-FCH frameRS1_2400_REV: Supports 40 bits per R-FCH frameRS1_1200_REV: Supports 16 bits per R-FCH frameRESERVED: 0 NUM_CON_REC: 1 RECORD_LEN: 6 octets CON_REF: 1SERVICE_OPTION: Standard: EVRC (8 kbps)FOR_TRAFFIC: SO Uses Primary Traffic On FTC REV_TRAFFIC: SO Uses Primary Traffic On RTCUI_ENCRYPT_MODE: User Information Encryption Disabled SR_ID: 1RLP_INFO_INCL: No QOS_PARMS_INCL: No RESERVED: -- FCH_CC_INCL: YesFCH_FRAME_SIZE: Supports only 20 ms Frame SizesFOR_FCH_RC: RC 3 REV_FCH_RC: RC 3DCCH_CC_INCL: No FOR_SCH_CC_INCL: No REV_SCH_CC_INCL: No RESERVED: 0RECORD_TYPE: Non-Negotiable Service ConfigurationRECORD_LEN: 5 octets FPC_INCL: Yes FPC_PRI_CHAN: No FPC_MODE: 0FPC_OLPC_FCH_INCL: Yes FPC_FCH_FER: 0.5% - 10% (in units of 0.5%)FPC_FCH_MIN_SETPT: 3.000 dB FPC_FCH_MAX_SETPT: 8.000 dBFPC_OLPC_DCCH_INCL: No GATING_RATE_INCL: No FOR_SCH_INCL: No REV_SCH_INCL: NoLPM_IND: Use the default Logic-to-Physical Mapping NUM_REC: 0 USE_FLEX_NUM_BITS: NoUSE_VAR_RATE: No LTU_INFO_INC: No USE_OLD_PARTITION_TABLE: No RESERVED: --

The Service Connect Message is the system’s proposal for the technical details of the call including service option, multiplexing, and type of traffic



000036, Time 22:43:17.131, Record 264, QcpCdmaLogMsgRevTrafChan1/32 Chip Counter: 492481.25 msec Counter: 04/03/2002 22:43:17MSG_LENGTH: 6 octetsMSG_TYPE: Service Connect Completion MessageACK_SEQ: 0MSG_SEQ: 1ACK_REQ: YesENCRYPTION: Encryption DisabledRESERVED: 0SERV_CON_SEQ: 0RESERVED: 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.

The Service Connect Complete Message is the mobile’s confirmation that it accepts the mode of operation the system has proposed


Access Failures

In an access failure, the mobile never hears an acknowledgment of its probes by the base stationFrom 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 station’s 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)

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


ACCESS CHANNEL

Access Failure Messaging

PROBE INFORMATIONORIGINATION MESSAGE








SYNC CHANNEL



Access Failure Messaging (1)

This is a sequence of messages leading up to an access failureThe 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

01:40:12.273 QcpCdmaLogMsgPagingChanMSG_LENGTH: 19 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Access Parameters MessagePILOT_PN: 4 ACC_MSG_SEQ: 0ACC_CHAN: 1 Access Channel(s)NOM_PWR: 0 dBINIT_PWR: 0 dBPWR_STEP: 3 dBNUM_STEP: 4 Probe(s)MAX_CAP_SZ: 5 ACH FramesPAM_SZ: 4 ACH Frame(s)PSIST(0-9): 0PSIST(10): 0PSIST(11): 0PSIST(12): 0PSIST(13): 0PSIST(14): 0PSIST(15): 0MSG_PSIST: 1.00REG_PSIST: 1.00PROBE_PN_RAN: 0 PN chip(s)ACC_TMO: 400 msPROBE_BKOFF: 1 Slot(s)BKOFF: 2 Slot(s)MAX_REQ_SEQ: 2MAX_RSP_SEQ: 2AUTH_MODE: 0NOM_PWR_EXT: -8 to 7 dB inclusivePSIST_EMG_INCL: NoRESERVED: 0



The mobile sends this origination message, attempting to get acknowledgment from the systemEach time this message is sent, we will see a Probe Information report from the mobile’s processor confirming the time that probe was sent, the power level, and other details

01:40:12.455 QcpCdmaLogMsgAccessChanMSG_LENGTH: 29 octetsPD: P_REV_IN_USE < 6MSG_ID: Origination MessageACK_SEQ: 7 MSG_SEQ: 6 ACK_REQ: 1VALID_ACK: 0 ACK_TYPE: 0MSID_TYPE: IMSI and ESNMSID_LEN: 9 octetsESN: D:00113967208 H:01D51F68IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S includedRESERVED: 0 IMSI_S: 9723333534AUTH_MODE: 0 MOB_TERM: YesSLOT_CYCLE_INDEX: 5.12 MOB_P_REV: J-STD-008EXT_SCM: Band Class 1 RESERVED: 0SLOTTED_MODE: Yes RESERVED: 0REQUEST_MODE: CDMA Only SPECIAL_SERVICE: YesSERVICE_OPTION: QUALCOMM: Voice 13K PM: NoDIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: NoNUM_FIELDS: 10 CHARi: 5 0 2 2 0 7 0 2 9 9NAR_AN_CAP: No RESERVED: 0



Here are the probe reports for the first probe sequence.No acknowledgment was received from the systemProbing continues into the second probe sequence on the next page

01:40:12.564 Access Probe InfoAccess Probe Sequence Number: 1 Access Probe Number: 1Access Channel Number: 0 PN Randomization delay: 0Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 1Rx Power: -63.248 Tx Power (Est): -12.752

01:40:13.442 Access Probe InfoAccess Probe Sequence Number: 1 Access Probe Number: 2Access Channel Number: 0 PN Randomization delay: 0Sequence Backoff: 0 Probe Backoff: 1 Persistence Tests Performed: 0Rx Power: -65.9147 Tx Power (Est): -7.08533 Tx Gain Adjust: 3


01:40:15.269 Access Probe InfoTime Stamp: 8/8/2000 01:40:16.000 Access Probe Sequence Number: 1Access Probe Number: 4 Access Channel Number: 0PN Randomization delay: 0 Sequence Backoff: 0Probe Backoff: 1 Persistence Tests Performed: 0Rx Power: -69.5813 Tx Power (Est): 2.58133 Tx Gain Adjust: 9



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

The mobile access attempt failed, so it restarts the system acquisition process





01:40:19.500 QcpCdmaLogMsgSyncChanMSG_LENGTH: 26 octetsMSG_TYPE: Sync Channel MessageP_REV: J-STD-008 MIN_P_REV: J-STD-008SID: 4139 NID: 41 PILOT_PN: 116LC_STATE: 0x02 B9 77 D6 59 D0SYS_TIME: 08/14/2000 00:31:49LP_SEC: 13 LTM_OFF: -660 minutesDAYLT: No PRAT: 4800 bps CDMA_FREQ: 50


Setup Failures

A setup failure is a failure to arrive successfully on a traffic channel despite the base station hearing and acknowledging the mobiles probes.The problem can occur in any of the steps after the base stationacknowledgment:

• 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, butthe mobile cannot hear the channel assignment message due to forward link problems

• the mobile or the base station may fail to hear the other duringinitialization of the traffic channel (this is called a TrafficChannel Confirmation Failure ‘TCCF’ in Lucent systems)


Setup Failure Messaging

ACCESS CHANNEL


PAGING CHANNEL


ORIGINATION MESSAGE




LAYER 2 HANDSHAKE

LAYER 2 HANDSHAKE

ANY OF THE STRIPED STEPS MAY NOT OCCUR,

STOPPING THE SETUP PROCESS


Setup Failure Messaging (1)

The mobile’s first probe is acknowledged, and the mobile now waits for a traffic channel assignment.If the mobile does not hear a channel assignment message within 12 seconds, it will abort.

01:46:51.263 QcpCdmaLogMsgPagingChanMSG_LENGTH: 16 octetsPD: P_REV_IN_USE < 6MSG_TYPE: Order MessageACK_SEQ: 5 MSG_SEQ: 0 ACK_REQ: NoVALID_ACK: Yes ADDR_TYPE: IMSIADDR_LEN: 7 octets IMSI_CLASS: 0IMSI_CLASS_0_TYPE: IMSI_S, IMSI_11_12, and MCC

included RESERVED: 0MCC: 310 IMSI_11_12: 00 IMSI_S: 9723333534ORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

01:46:50.714 QcpCdmaLogMsgAccessChanMSG_LENGTH: 29 octets PD: P_REV_IN_USE < 6MSG_ID: Origination MessageACK_SEQ: 7 MSG_SEQ: 5 ACK_REQ: 1 VALID_ACK: 0 ACK_TYPE: 0MSID_TYPE: IMSI and ESN MSID_LEN: 9 octetsESN: D:00113967208 H:01D51F68IMSI_CLASS: 0 IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0IMSI_S: 9723333534 AUTH_MODE: 0 MOB_TERM: YesSLOT_CYCLE_INDEX: 5.12 MOB_P_REV: J-STD-008EXT_SCM: Band Class 1 RESERVED: 0 SLOTTED_MODE: YesRESERVED: 0 REQUEST_MODE: CDMA Only SPECIAL_SERVICE: YesSERVICE_OPTION: QUALCOMM: Voice 13K PM: NoDIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: No NUM_FIELDS: 10CHARi: 5 0 2 2 0 7 0 2 9 9 NAR_AN_CAP: No RESERVED: 0

01:46:50.980 Access Probe InfoAccess Probe Sequence Number: 1 Access Probe Number: 1Access Channel Number: 0 PN Randomization delay: 0Sequence Backoff: 0 Probe Backoff: 0 Persistence Tests Performed: 1Rx Power: -81.9147 Tx Power (Est): 5.91467 Tx Gain Adjust: 0


01:46:51.474 QcpCdmaLogMsgPagingChanMSG_LENGTH: 21 octets PD: P_REV_IN_USE < 6MSG_TYPE: Channel Assignment MessageACK_SEQ: 5 MSG_SEQ: 1 ACK_REQ: No VALID_ACK: YesADDR_TYPE: IMSI ADDR_LEN: 7 octets IMSI_CLASS: 0IMSI_CLASS_0_TYPE: IMSI_S, IMSI_11_12, and MCC includedRESERVED: 0 MCC: 310 IMSI_11_12: 00 IMSI_S: 9723333534ASSIGN_MODE: Extended Traffic Channel AssignmentADD_RECORD_LEN: 5 octets FREQ_INCL: Yes RESERVED: 0BYPASS_ALERT_ANSWER: NoDEFAULT_CONFIG: Multiplex Option 1 and Radio Config 1 For

Both FTC and RTCGRANTED_MODE: MS use Service Configuration of default

Multiplex Option and Transmission RatesCODE_CHAN: 9 FRAME_OFFSET: 5.00 msENCRYPT_MODE: Encryption DisabledBAND_CLASS: 1.850 to 1.990 GHz BandCDMA_FREQ: 50 C_SIG_ENCRYPT_MODE_INCL: NoRESERVED: 0

Setup Failure Messaging

If the mobile never hears the channel assignment message, the setup fails and the mobile reacquires the system.

XXor

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.Steps in traffic channel initialization:Forward link layer 2 handshakeReverse link layer 2 handshakeL3 base station ack. orderL3 mobile ack. orderFailure of any one is a TCCF


Dropped Calls

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

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


A Beautiful End to a Normal Call

008091, Time 17:39:26.108, Record 167760, QcpCdmaLogMsgRevTrafChanMSG_TYPE: Order MessageACK_SEQ: 4MSG_SEQ: 1ACK_REQ: NoENCRYPTION: Encryption DisabledORDER: Release Order (Normal Release)ADD_RECORD_LEN: 0 octetsRESERVED: 0

MOBILE RELEASE ORDER

BASE STATION ACKNOWLEDGMENT008090, Time 17:39:26.020, Record 167747, QcpCdmaLogMsgForTrafChanMSG_TYPE: Order MessageACK_SEQ: 1MSG_SEQ: 5ACK_REQ: NoENCRYPTION: Encryption DisabledUSE_TIME: NoACTION_TIME: 0 msORDER: Release Order (No Reason Given)ADD_RECORD_LEN: 0 octetsRESERVED: 0

The mobile left the traffic channel, scanned to find the best pilot, and read

the Sync Channel Message.

008092, Time 17:39:26.514, Record 167820, QcpCdmaLogMsgSyncChanMSG_TYPE: Sync Channel MessageP_REV: IS-95BMIN_P_REV: IS-95ASID: 179NID: 0PILOT_PN: 468LC_STATE: 0x02 87 7C F3 7F BASYS_TIME: 06/29/2002 06:15:19LP_SEC: 13LTM_OFF: -660 minutes




Dropped Call Messaging

SYNC CHANNEL


ANY COMBINATION OF NORMAL MESSAGES MAY OCCUR ON THE FORWARD AND

REVERSE TRAFFIC CHANNELS, BUT NO “RELEASE – NORMAL” IS SENT.


Dropped Call MessagingIn a normal call end, there will be a “Release –Normal” message from one side and a “Release –No Reason” message from the other.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 QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 13 octets MSG_TYPE: Pilot Strength Measurement MessageACK_SEQ: 0 MSG_SEQ: 2 ACK_REQ: YesENCRYPTION: Encryption Disabled REF_PN: 284PILOT_STRENGTH: -18.00 dB KEEP: YesPILOT_PN_PHASE: PN:447 + 45 chipsPILOT_STRENGTH: -18.50 dB KEEP: YesPILOT_PN_PHASE: PN:196 + 10 chipsPILOT_STRENGTH: -10.00 dB KEEP: YesRESERVED: 0

13:37:23.188 QcpCdmaLogMsgSyncChanMSG_LENGTH: 26 octetsMSG_TYPE: Sync Channel MessageP_REV: Unknown (3) MIN_P_REV: IS-95ASID: 22 NID: 0 PILOT_PN: 196LC_STATE: 0x02 9E 9B E4 EE C4SYS_TIME: 03/27/1998 06:01:32LP_SEC: 8 LTM_OFF: -660 minutesDAYLT: No PRAT: 9600 bps CDMA_FREQ: 777

13:37:13.733 QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 10 octetsMSG_TYPE: Power Measurement Report MessageACK_SEQ: 0 MSG_SEQ: 1 ACK_REQ: NoENCRYPTION: Encryption DisabledERRORS_DETECTED: 2 PWR_MEAS_FRAMES: 5LAST_HDM_SEQ: 3 NUM_PILOTS: 2PILOT_STRENGTH: -18.50 dBPILOT_STRENGTH: -18.00 dB


Normal End of Call

When a call ends normally, it is because the caller on one side of the conversation decided to hang upThe side ending the call sends a “Release – Normal” orderThe other side sends a “Release – No reason” order

• It may send an acknowledgment first, if it cannot give the release order immediately

After the system receives a release order from the mobile, it releases the resources it used for the callAfter the mobile receives a release order from the base station, it stops listening to the traffic channel and freshly reacquires the system

BTS

W1

W32

W0

W23

PAGING

SYNC

PILOT

TRAFFIC

ACCESS CHANNEL

TRAFFIC CHANNEL

SSSSSSSSSSSSSSSSSSSSSSSSSSS

GK KS P C GP K KSAGK KSAK

Voice

Voice

RELnorm

RELnoRsn

NNKG K SGP SA

SYN SYN SYN

ACK

SYN SYN SYN SYNSYN

ChASN

SYN

SYS CHN XSYS NBR

Ref TimeRef Time

MOBILE REACQUIRES SYSTEM NORMALLY

SCANTIME


Abnormal End of Call – Forward Link Failure

The mobile is always counting and tracking the bad frames it receives on the forward linkForward Link Fade Timer: If the mobile does not receive any goodframes during a 5-second period, it aborts the callIf 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 After a call ends for any reason, the mobile tries to reacquire the system, making an independent cold start

BTS

W1

W32

W0

W23

PAGING

SYNC

PILOT

TRAFFIC

ACCESS CHANNEL

TRAFFIC CHANNEL



Voice

Voice

NNKG K SGP SA

SYN SYN SYN

ACK

SYN SYN SYNSYN

ChASN

SYN

SYS CHN XSYS

Ref TimeRef Time

MOBILE REACQUIRES SYSTEM, if available

SCAN

Mute! No pc

All bad frames5s timer

5s timer

TIME


S

Abnormal End of Call – Reverse Link Failure

The BTS is always counting and tracking the bad frames it receives on the reverse link from the mobileReverse Link Fade Timer: If the BTS does not receive any good frames during a 5-second period, it releases the callAfter a call ends for any reason, the mobile tries to reacquire the system, making an independent cold start

BTS

W1

W32

W0

W23

PAGING

SYNC

PILOT

TRAFFIC

ACCESS CHANNEL

TRAFFIC CHANNEL


Voice

Voice

NNKG K SGP SA

All bad frames

5s timer

SYN SYN SYN

ACK

SYN SYN SYNSYN

ChASN

SYN

SYS CHN XSYS

Ref TimeRef Time

MOBILE REACQUIRES SYSTEM, if available

SCAN

RELnoRsn

A

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

KS NK GP SA

TIME


Let’s Do A Soft Handoff!Let’s Do A Soft Handoff!

Example 8


Basic Rules of Soft Handoff

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)

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

The System may set up all requested handoffs, or it may apply special manufacturer-specific screening criteria and only authorize some

65

Remaining

ActiveCandidateNeighbor 20

PILOT SETS

Min. M

embers

Req’d. B

y Std.

T_COMPT_ADD T_DROPT_TDROP

HANDOFF PARAMETERS

Exercise: How does a pilot in one set migrate into another set, for all cases? Identify the trigger, and the messages involved.


The Call is Already Established. What Next?E

c/Io

All PN Offsets

0

032K

512Chips

PN

0

-20

Neighbor Set

The call is already in progress. PN 168 is the only active signal,and also is our timing reference.

Continue checking the neighbors.

If we ever notice a neighbor with Ec/Io above T_ADD,ask to use it! Send a Pilot Strength Measurement Message!

T_ADD

Rake Fingers

Reference PN

Active Pilot

10752

16832002

50014080

220

! !

Mobile Rake RX

Srch PN??? W0

F1 PN168 W61F2 PN168 W61F3 PN168 W61


Basic Soft/Softer Handoff

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 it’s already using has faded to the point of uselessness, it tells the system in a Pilot Strength Measurement Message (PSMM)

The system normally makes the changes requested by a mobile• some systems have algorithms for intelligent “screening” of the

mobile’s requests, and may not give everything requested



Soft Handoff Messaging


PILOT STRENGTHMEASUREMENT MSG.

EXTENDED HANDOFFDIRECTION MSG.


HANDOFF COMPLETIONMESSAGE


NEIGHBOR LISTUPDATE MESSAGE.



Soft Handoff Messaging (1)

Soft Handoff begins with a request – the Pilot Strength Measurement Message from the mobile

QcpCdmaLogMsgForTrafChan04/03/2002 22:43:17MSG_LENGTH: 18 octetsMSG_TYPE: General Handoff Direction MessageACK_SEQ: 0 MSG_SEQ: 1 ACK_REQ: YesENCRYPTION: Encryption Disabled USE_TIME: NoHDM_SEQ: 1 SEARCH_INCLUDED: YesSRCH_WIN_A: 40 chipsSRCH_WIN_N: 100 chipsSRCH_WIN_R: 4 chipsT_ADD: -14.0 dB T_DROP: -16.0 dBT_COMP: 2.0 T_TDROP: 4 secSOFT_SLOPE: 0ADD_INTERCEPT: 0 dB DROP_INTERCEPT: 0 dBEXTRA_PARMS: NoSUP_CHAN_PARAMS_INCLUDED: NoUSE_PWR_CNTL_STEP: NoNUM_PILOTS: 2 PilotsPILOT_PN: 380 PWR_COMB_IND: NoFOR_FUND_CODE_CHAN: 33PILOT_PN: 212 PWR_COMB_IND: YesFOR_FUND_CODE_CHAN: 56FPC_SUBCHAN_GAIN: 0.0 dBUSE_PC_TIME: No REV_FCH_GATING_MODE: No

QcpCdmaLogMsgRevTrafChan04/03/2002 22:43:17MSG_LENGTH: 10 octetsMSG_TYPE: Pilot Strength Measurement MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: YesENCRYPTION: Encryption DisabledREF_PN: 380 PILOT_STRENGTH: -4.50 dB KEEP: YesPILOT_PN_PHASE: PN:212 + 0 chipsPILOT_STRENGTH: -13.50 dB KEEP: YesRESERVED: 0

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


Soft Handoff Messaging (2)

The mobile acknowledges receiving the Handoff Direction MessageAfter double-checking that the requested sectors are still usable, the mobile accepts them by sending a Handoff Completion Message QcpCdmaLogMsgRevTrafChan

04/03/2002 22:43:17MSG_LENGTH: 8 octetsMSG_TYPE: Handoff Completion MessageACK_SEQ: 1 MSG_SEQ: 2 ACK_REQ: YesENCRYPTION: Encryption DisabledLAST_HDM_SEQ: 1 PILOT_PN: 380 PILOT_PN: 212RESERVED: 0

QcpCdmaLogMsgRevTrafChan04/03/2002 22:43:17MSG_LENGTH: 7 octetsMSG_TYPE: Order MessageACK_SEQ: 1 MSG_SEQ: 0 ACK_REQ: NoENCRYPTION: Encryption DisabledORDER: Mobile Station Acknowledgement OrderADD_RECORD_LEN: 0 octetsCON_REF_INCL: No RESERVED: 0


Soft Handoff Messaging (3)QcpCdmaLogMsgForTrafChan04/03/2002 22:43:18MSG_LENGTH: 38 octetsMSG_TYPE: Extended Neighbor List Update MessageACK_SEQ: 2 MSG_SEQ: 3 ACK_REQ: YesENCRYPTION: Encryption DisabledPILOT_INC: 4NGHBR_SRCH_MODE: Search PrioritiesSRCH_WIN_N: 100 chipsUSE_TIMING: No NUM_NGHBR: 20NGHBR_PN: 40 SEARCH_PRIORITY: Very HighNGHBR_PN: 32 SEARCH_PRIORITY: HighNGHBR_PN: 372 SEARCH_PRIORITY: HighNGHBR_PN: 132 SEARCH_PRIORITY: HighNGHBR_PN: 448 SEARCH_PRIORITY: HighNGHBR_PN: 12 SEARCH_PRIORITY: HighNGHBR_PN: 260 SEARCH_PRIORITY: HighNGHBR_PN: 184 SEARCH_PRIORITY: HighNGHBR_PN: 504 SEARCH_PRIORITY: HighNGHBR_PN: 428 SEARCH_PRIORITY: HighNGHBR_PN: 352 SEARCH_PRIORITY: HighNGHBR_PN: 280 SEARCH_PRIORITY: HighNGHBR_PN: 108 SEARCH_PRIORITY: HighNGHBR_PN: 408 SEARCH_PRIORITY: HighNGHBR_PN: 136 SEARCH_PRIORITY: HighNGHBR_PN: 476 SEARCH_PRIORITY: HighNGHBR_PN: 360 SEARCH_PRIORITY: HighNGHBR_PN: 336 SEARCH_PRIORITY: MediumNGHBR_PN: 344 SEARCH_PRIORITY: MediumNGHBR_PN: 176 SEARCH_PRIORITY: MediumSRCH_OFFSET_INCL: NoADD_PILOT_REC_INCL: None RESERVED: 0

QcpCdmaLogMsgRevTrafChan04/03/2002 22:43:18MSG_LENGTH: 7 octetsMSG_TYPE: Order MessageACK_SEQ: 3 MSG_SEQ: 5 ACK_REQ: NoENCRYPTION: Encryption DisabledORDER: Mobile Station Acknowledgement OrderADD_RECORD_LEN: 0 octetsCON_REF_INCL: No RESERVED: 0

The system takes the pilots accepted by the mobile in the Handoff Completion Message and builds a new combined list of all their neighborsThe new blended neighbor list is sent to the mobile in an Extended Neighbor List Update Message, which the mobile acknowledgesThe handoff is now in effect!


Handoff Now In Effect, but still check Pilots!E

c/Io

All PN Offsets

0

032K

512Chips

PN

0

-20

Neighbor Set

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!

T_ADD

Rake Fingers

Reference PN

Active Set

10752

16832002

50014080

220

T_DROP

Mobile Rake RX

Srch PN??? W0

F1 PN168 W61F2 PN500 W50F3 PN220 W20


The Complete Picture of Handoff & Pilot Sets

T_ADD

Ec/

IoAll PN Offsets

00

32K512

ChipsPN

0

-20

Neighbor Set

SRCH_WIN_N

Active Set

Candidate SetT_DROP

SRCH_WIN_A

Remaining SetT_ADD

SRCH_WIN_R

SRCH_WIN_A

T_DROP

Rake Fingers

Reference PN

Pilots of sectors now used for communication

Pilots requested by mobile but not set up by system

Pilots suggested by system for more checking

All other pilots divisible by PILOT_INC but not presently in Active, Candidate, or Neighbor sets

Mobile Rake RX

Srch PN??? W0

F1 PN168 W61F2 PN500 W50F3 PN220 W20


Improved Soft Handoff Controlin 1xRTT

Improved Soft Handoff Controlin 1xRTT


The IS-95 Situation

IS-95 handoff is driven by fixed thresholds of pilot strength (Ec/Io)If the mobile notices a new pilot stronger than T_Add, it asks for it immediatelyIf an active pilot drops below T_Drop and stays below for T_Tdrop seconds, the mobile asks for permission to stop using itThe mobile has no discretion – the T_Addand T_Drop values apply no matter what

0

-5

-10

-15

-20

Ec/Io

TH

RES

HO

LDS,

db

T_ADD

T_DROP


Disadvantages of Standard Handoff Triggers

Mobile requests soft handoff with all pilots above T_Add• This occasionally leads to some

rigid, less-than-optimum decisions!Problem Situation 1• One dominant, strong signal and a

lot of weak ones:– Mobile asks for them all, but

only one is really needed!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!!

Pilo

t Stre

ngth

(Ec/

Io, d

b)

-3

-20

All Six sectors in

soft handoff!

T_AddActive

Active

ActiveActiveActiveActive

Pilo

t Stre

ngth

(Ec/

Io, d

b)

-3

-20

Only One Sector in soft

handoff!

T_AddActive


1xRTT Allows Dynamic Handoff Thresholds

A handoff process more intelligent than fixed thresholds• Handoff events driven by smarter, situation-influenced triggers

Candidate Set Removal: if that sector isn’t worth adding anymore

Neighbor-to-Active transition: only if it’s a worthwhile improvement

Removal from Active Set: if that sector isn’t needed anymore


Standard Equation of a Line

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

y = mx + b

slop

e

inte

rcep

t

x

y

b


CombinedEc/Io

of ExistingActive Pilots

0

-5

-10

-15

-20

-5-10-15-20COMBINED Ec/Io, db

Ec/Io

TH

RES

HO

LDS,

db

+5

+10

The Dynamic Handoff Threshold Line

AddIntercept

T_Add

DropIntercept

T_Drop


CombinedEc/Io


0

-5

-10

-15

-20


Ec/Io

TH

RES

HO

LDS,

db

+5

+10

Weak-Signal, Pilot-Pollution Conditions

AddIntercept

T_Add

DropIntercept

T_Drop

T_Add and T_Drop can be greatly reduced to allow soft handoff under pilot pollution

conditions


CombinedEc/Io


0

-5

-10

-15

-20


Ec/Io

TH

RES

HO

LDS,

db

+5

+10

Strong-Signal Conditions

AddIntercept

T_Add

DropIntercept

T_Drop

Low T_Add and T_Drop will not cause excessive soft

handoff when good signals are available


Deeper Handoff Details:Search Windows & TimingDeeper Handoff Details:

Search Windows & Timing

Section G


The Pilot Searcher’s Measurement Process

The searcher checks pilots in nested loops, much like meshed gears. Actives and candidatesoccupy the fastest-spinning wheel. Neighbors are next, advancingone pilot for each Act+Cand. revolution.Remaining is slowest, advancing one pilot each time the Neighbors revolve.

CURRENT PILOT SET CONTENTSA A A

C

N N N N N N N N N N N N

R R R R R R R R R R R R









R R R R

31

12112

A

N

R

R

R

R

R

R

R

NN

N

N

NN N N

AA

PILOT SEARCHER VIEWED IN SEQUENCE: Typical Elapsed Time = 4 secondsA A A C N

R

A A A C A A A C A A A C A A A C A A A C A A A CN N N N N N

A A A C N A A A C A A A C A A A C A A A C A A A C

A A A C

N N N N N

A A A C NA A A C A A A C A A A C A A A C A A A C A A A CN N N N N N

NA A A C A A A C A A A CN N N RA A A C

N

A A A C A A A C

A A A

N N

CA A A C A A A C NN N

R

A A A C N A A A C A A A C A A AN N C A A AN

CA A A C N

A A A C

NA A AC CA A A Only 3 of 112 remaining set pilotshave been checked thus far!


Meet the CDMA Performance Indicators

Meet the CDMA Performance Indicators


CDMA Performance IndicatorsA Flight Data Recorder logs aircraft operational settings. Its CDMA equivalent is a file of RF performance indicators captured by drive-test equipment.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

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


Indicator #1: FER

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

FER%

0 2 5 100Forward

Reverse

FER is the end-result of the whole transmission link• if FER is good, then any other problems aren’t having much

effect• if FER is bad, that’s 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


Indicator #2: I0, Total Mobile Receive Power

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, notjust RF from serving BTS

-40

-90

-105

<<to

o w

eak

ove

rload

>>

I0

≈ x

LO

≈

RX Level(from AGC)

IFLNA

BW~30

MHz.

BW1.25MHz.

Handset Receiver

R

R

R

S

Rake

Receive power is important, but it’s exact value isn’t critical• too much received signal (-35 dbm or higher) could drive the

phone’s sensitive first amplifier into overload, causing intermodand 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


Indicator #3, EC/I0 - What does it mean?

Why can’t we just use the handset’s received power level to guide handoffs?

• Because it is a simple total RF power measurement, the total of all sectors reaching the mobile

≈ x

LO

≈

RX Level(from AGC)

IFLNA

BW~30

MHz.

BW1.25MHz.

Handset Receiver

R

R

R

S

Rake

We need a way to measure the signal strength of each sector individually, and we must be able to measure it quickly and simplyThe solution is to use each sector’s 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 won’t be able to get much benefit from using a traffic channel on thatsector


Light Traffic Loading

Heavily Loaded

How EC/I0 Varies with Traffic Loading

Each sector transmits a certain amount of power, the sum of:

• pilot, sync, and paging• any traffic channels in use

at that momentEc/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.

Ec/Io = (2/4)= 50%

= -3 db.

Ec/Io = (2/10)= 20%

= -7 db.

2w

1.5w

Pilot

PagingSync

I0

EC

Traffic Channels

6w

0.5w

2w

1.5w

Pilot

PagingSync I0EC

0.5w


Many Sectors, Nobody Dominant

One Sector Dominant

How EC/I0 varies with RF Environment

In a “clean situation”, one sector is dominant and the mobile enjoys an Ec/Io just as good as it was when transmittedIn “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 sector’s pilot

• The large Io overrides the weak Ec; Ec/Io is low!

Io = -90 dbmEc = -96 dbmEc/Io = -6 db

Io = 10 signalseach -90 dbm

= -80 dbmEc of any onesector = -96

Ec/Io = -16 db

2w

1.5w

Pilot

PagingSync

I0

ECTraffic

Channels

4w

0.5w

BTS1

I0

EC

BTS2

BTS3

BTS4

BTS5

BTS6

BTS7

BTS8

BTS9

BTS10

PilotSync & Paging

TrafficPilot

Sync & PagingTraffic

PilotSync & Paging

TrafficPilot


PilotSync & Paging

TrafficPilot


PilotSync & Paging

TrafficPilot


PilotSync & Paging

TrafficPilot



Indicator #4: Handset Transmitter PowerTXPO 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

• can’t exceed handset’s maximum (typ. +23 dBm)

TXPODUP x ≈ IF

LNA

Subscriber Handset

R

R

R

S

Rake

Σ ViterbiDecoder

Vocoder

∼

FECOrthMod

Long PN

xx

xIF Mod

I

Q

x ~LO Open Loop

LO

Closed Loop Pwr Ctrl

IF

Receiver>>

<<Transmitter

PA

BTS

Typical TXPO:+23 dBm in a coverage hole0 dBm near middle of cell-50 dBm up close to BTS

TXPO = -(RXdbm) -C + TXGAC = +73 for 800 MHz. systems= +76 for 1900 MHz. systems

What is the right power TX level? Whatever the BTS asks for!• As long as closed loop control is working, the phone’s opinion

isn’t 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)


Indicator #5: Transmit Gain Adjust

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 station’s latest new

decision: mobile is too strong, or mobile is too weak -- there is no cumulative error, since each decision is “fresh”

0 dB

-10 dB

-20 dB

Typical Transmit Gain Adjust

Time, Seconds

TXPO = -(RXdbm) -C + TXGAC = +73 for 800 MHz. systems= +76 for 1900 MHz. systems


Closed Loop Power Control Dynamics

The figures at right show the power control reactions to a sudden change in path lossThe sudden change in path loss causes a sudden change in handset received signalBoth open loop and closed loop control race to get the phone back to the right new power and succeed in about 10 millisecondsOpen loop continues to approach the correct value better and better on its own40 milliseconds later, no net closed loop correction is needed.


Problem “Signatures”Problem “Signatures”


“Signatures” of Common Conditions

The key CDMA RF Performance Indicators provide powerful clues in cause-and-effect analysis for understanding problem conditions

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

We will use the simplified format shown at right to display the key indicators for each of several interesting cases.

SIGNATURE: GOOD CALL

FFER I0 EC/IO TxGa TxPo

BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90

-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10

-20

-40

-50

-30

+10

0


Signature of a Successful Call

If the mobile station originates successfully, remains in service area, and makes normal release, data will show:

• Low forward FER• Receive power > -100 dBm• Good Ec/Io (> -12 dB)• Normal Transmit Gain Adjust

(actual value depends on site configurations, loading & NOM_PWR setting)

• Transmit power < +20 dBm• Good Messaging

• Parsed message files will contain a full set of normal messages.

SIGNATURE: GOOD CALL


BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90

-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10

-20

-40

-50

-30

+10

0


Signature of a Dropped Call in Poor Coverage

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:

• 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

SIGNATURE: DROPPED CALL, BAD COVERAGE


BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90

-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10

-20

-40

-50

-30

+10

0


Signature of Forward Link Interference

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


BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90

-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10

-20

-40

-50

-30

+10

0


A CDMA Drop Example: Forward Link Case

A mobile using Site A comes down the highway and suddenly begins to see the signal of Site BIf the mobile begins soft handoff with site B, everything continues to go wellIf the mobile cannot begin handoff with B for any reason, the call is doomed

• site B’s signal will override site A’s signal, making it unreadable

• as soon as the FER goes too high, a fade timer will start the the mobile will eventually die

A

BBTS

BTS

FORWARD LINK DIES

Obstructio

ns

Travel

B grows stronger and stronger.Mobile’s 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 can’t hear power control bits, and a fade timer or message timer kills the call in a few seconds.


Signature of Reverse Link Interference

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, you’ll see repeats of messages on the forward link and reverse link

SIGNATURE: REVERSE LINK INTERFERENCE


BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90

-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10

-20

-40

-50

-30

+10

0


A CDMA Drop Example: Reverse Link Case

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

BBTS

Obstructio

ns

Travel

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 couldn’t 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.

REVERSE LINK DIES


Solving the #1 Death Scenario: Failed Handoff

Why didn’t the mobile ask for handoff?• New sector not on neighbor list• Neighbor Search Window too Small?• BTS in “island mode”, wrong PN?

Why didn’t the BTS set up the handoff?• Old BTS didn’t hear mobile – rev link

interf?• No resources available on new BTS?• T-1 unstable, messages lost

Why didn’t the mobile do the handoff?• Couldn’t hear BTS, Fwd link interf?

BBTS Obstru

ctions

Travel

REVERSE LINK DIESAB

BTS

BTS

FORWARD LINK DIES

Obstructio

ns

TravelSteps in the Handoff ProcessMobile’s searcher notices the needed new pilot

Mobile sends PSMM requesting handoff

System sets up the handoff:•channel elements•forward power•space in packet pipesSimulcasting begins!

System tells mobile how to hear the new sectors: Handoff Direction Message

Mobile confirms completion:Handoff Completion MessageSystem makes new neighbor list, sends to mobile: Neighbor List Update Message

Now the mobile can hear the system better, too!

Now the system can hear the mobile better!

see

ask

tell

do

ok!

tell

BTS

BTS

BTS

What Went Wrong??!


Pilot Pollution

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

The cure for pilot pollution is to eliminate unneeded signals which really weren’t intended to serve this location anyway, and to boost the one or a few signals which were intended to serve this locationSee the first page of the workbook ECIOPLAY.XLS

Io

Ec/Io value at each BTS TX

-80.0 -3

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

1 2 3 4 5 6 7 8 9 10

Io

Ec/Io value at each BTS TX

-73.9 -3


-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

Ec/Io of Multiple CDMA Signals

1 2 3 4 5 6 7 8 9 10


Pilot Pollution/Handoff/Composite Ec/Io Demo

See the second page of the workbook ECIOPLAY.XLS

Ec/Io, Handoff, and Rake Finger Pilot Status

%Pilot Power

% Over-head Power

Nominal Max Power W

Sum RF Power Io

Composite Ec/Io

Max # Lockable Rake Fingers

Max # Pilots in Soft Handoff T_ADD

10% 20% 12 -86.2 -3.0 3 6 -12

Traffic Loading %

Transmitted Ec/Io

Path Loss, dB


0% -3.0 120 -86.2 -3.0 Rake Locked Handoff 10% -3.0 200 -166.2 -83.0 Interferor 20% -3.0 200 -166.2 -83.0 Interferor 30% -3.0 200 -166.2 -83.0 Interferor 40% -3.0 200 -166.2 -83.0 Interferor 50% -3.0 200 -166.2 -83.0 Interferor 60% -3.0 200 -166.2 -83.0 Interferor 70% -3.0 200 -166.2 -83.0 Interferor 80% -3.0 200 -166.2 -83.0 Interferor 90% -3.0 200 -166.2 -83.0 Interferor 100% -3.0 200 -166.2 -83.0 Interferor 110% -3.0 200 -166.2 -83.0 Interferor 120% -3.0 200 -166.2 -83.0 Interferor 130% -3.0 200 -166.2 -83.0 Interferor 14

Only grey-shaded fields can be changed. Other fields calculate automatically.To unlock all cells, select TOOLS>PROTECTION>UNPROTECT SHEET.

Relative Energies of Multiple CDMA Signals

0

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

1

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Ind ivid ual Sig nals

Pilot Energy Sync, Paging, Traf f ic


Basic PN Planning andSearch Window Considerations

Basic PN Planning andSearch Window Considerations

System Performance Optimization


Introduction to PN Planning and Search Windows

In PN planning and setting Search Windows, several pitfalls mustbe avoided. These slides explain most of the basic facts, background, principles, and practical considerations involved.


Short PN Basics: PN Offsets Distinguish Sectors

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

A

B

C

D

≈ x

LO

IFLNA

BPF

PhoneRake Receiver

≈BPF

PN A Walsh X

PN B Walsh Y

PN C Walsh Z

Pilot Searcher

∑ Decoding Vocoderx


A Practical "Rule of Thumb" to Remember

The signal of a base station roughly 10 miles distant will SEEM to be one PN higher than it was transmitted

Transmitted:PN 100

6,400 chips offset

BTS

ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890abcdefghijkmnopqrstuvwxyz!@#$%^&*()_+

9.70 miles = 64 chips = 1 PN

Mobile

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.

Received:PN 101

6,464 chips delay


Propagation Delay changes apparent PN Offset

Base stations transmit signals on assigned, fixed short PN delays called PN OffsetsTransmitted signals encounter additional delay traveling to the mobile

• ~6.7 chips/mile = ~4.1 chips/kilometerThese 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

10 KM41 chips

2 KM8 chips

PN200

PN360


Mobile Timing: the Reference PN

Mobile System Acquisition ProcessScan entire range of PNsLock to strongest Pilot found

• Put rake fingers on multipaths• Earliest arriving multipath is "reference PN"

Read sync channel message• Learn what PN this is!

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!

Rake Fingers

Reference PN

Active Pilot

Ec/

Io

00

32K512

ChipsPN

Pilot Searcher Scans All PNs

All PN Offsets0

-20

98/05/24 23:14:09.817 [SCH] MSG_LENGTH = 208 bitsMSG_TYPE = Sync Channel MsgP_REV = 3, MIN_P_REV = 2SID = 179 NID = 0PILOT_PN = 168 Offset IndexLC_STATE = 0x0348D60E013SYS_TIME = 98/05/24 3:14:10.160LP_SEC = 12LTM_OFF = -300 minutesDAYLT = 0, PRAT = 9600 bps


UNKNOWN EXTRA PROPAGATION DELAY

How many chips????


What are "Search Windows"?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

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 measureThese "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

Search windows are chosen by RF engineers and transmitted to the mobile in messages from the BTS

10 KM41 chips

2 KM8 chips

PN200

PN360

360

+41

+8

360+33c

SRCH_WIN_N


What are the Available Search Window Values?

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

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

SRCH_WIN_val0123456789

101112131415

Width, Chips4 (±2)6 (±3)8 (±4)

10 (±5)14 (±7)20 (±10)28 (±14)40 (±20)60 (±30)80 (±40)

100 (±50)130 (±65)160 (±80)226 (±113)330 (±165)452 (±226)


Search Window Settings: Neighbor Set

The neighbor search window must be set wide enough to include the energy of any needed neighbor pilotThe mobile at right is using PN200 as its reference (and only active) pilotTo the mobile, the pilot of neighbor sector PN360 seems 33 chips late SRCH_WIN_N must be set to at least 2 x 33 = 66 chips wide so the PN360 pilot can be noticed by the mobileThe closest search window setting above 66 chips is SRCH_WIN_N = 9, which is 80 chips wide

10 KM41 chips

2 KM8 chips

PN200

PN360

360

+41

+8

360+33c

SRCH_WIN_N

Neighbor Search WindowExample

ActiveSector

NeighborSector


Worst-Case Wide Neighbor Window Situation

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 handoffThis 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!

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

BTS A

BTS B

12 miles

1/2mile


Safe Initial Neighbor Search Window ValueExamine a cell map for an area of your systemIdentify the farthest-apart pair of cells likely to be used in soft handoff• Their distance separation determines

maximum timing skew a mobile could ever possibly encounter in this part of the system

Calculate the timing skew in chips• 6.7 chips times miles or 4.1 chips times

kilometers• Safe required window size = two times the

skewRefer to table to convert required window size in chips to required value of SRCH_WIN_NAfter thorough drive-test data is available, it may be possible to reduce SRCH_WIN_N if observed delay spread is significantly narrower than the window

Determining Safe Initial SRCH_WIN_N

Required Window= 4.1 x 11.5 x 2 = 94.3 chips

SRCH_WIN_N = 10If locations exist near site A where mobiles are in handoff with site F, mobiles could encounter neighbor pilot timing skews as large as the A-F distance. If locked to A, F looks late by this amount. If locked to F, A looks early by this amount. Window must be twice the skew value.

11.5 KM

A

B

C

E

FD


Search Window Settings: Remaining Set

Remaining set search window size is determined by maximum possible timing skew in the same way as for neighbor set windowRecommended SRCH_WIN_R is one or two steps greater than SRCH_WIN_NRemaining 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 cross-reference for identification of their base stationsThere 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

11.5 KM

A

B

C

E

FD


Search Window Initial Settings: Active Set

Neighbor and Remaining search window centers are indexed against the mobile’s Reference PNEach active search window is different – a “floating” window centered over the earliest observed multipath energy during the previous mobile searcher scan of that individual pilotActive search windows need not accommodate distance-based timing skews – they float centered on their respective pilots!The only timing variations they must accommodate are multipath delay spreadsMultipath delay spreads are determined by terrain and clutter-driven scattering and reflection of the signalMeasurements are better than predictions to set SRCH_WIN_A

The earliest arriving multipathseen 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.

Earliest Detected Multipath

Active Search Window

40 chips wide (typical)

0 +20-20

Ec/Io


SRCH_WIN_A Settings from Measurements

Typical active set delay spread from actual drive-testsNotice the narrow distribution of energy!28-chip width, SRCH_WIN_A = 6, is enough for this caseDrive-test your own system to determine your own value of spread• It is determined by the signal-scattering characteristics of your terrain


SRCH_WIN_A Special Consideration

There is a dynamic relationship between mobile reference timing stability and the active and neighbor search window sizesThe chart above shows which combinations of SRCH_WIN_A and SRCH_WIN_N are safe and stable for all mobiles

SRCH_WIN_A, Chips

2010No

14No

20No

28No

40No

60No

28 No No No No No No40 No No No No Yes No60 No No No Yes Yes Yes80 No No No Yes Yes Yes100 No Yes Yes Yes Yes Yes130 Yes Yes Yes Yes Yes Yes160 Yes Yes Yes Yes Yes Yes226 Yes Yes Yes Yes Yes Yes

SR

CH

_WIN

_N, C

hips

Active set delay spread is very narrow –can the active search window be set narrow too?Mobile reference timing occasionally “jumps” due to false early-window detection of the reference pilot


The Potential for PN Problems and Conflicts

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:Two same-PN base stations with areas of coverage overlap

• Mobiles can't distinguish them, experience horrible FERCombining unintended signals into the handoff mix being heard

• The new signals cause interference instead of helpingMistaken identity of signals when requesting handoff

• The wrong base station is added, the mobile can't hear itRunning out of available PNs due to bad parameter choices

Fortunately, these problems can be avoided by careful planning!


Co-Active PN Demodulation Errors

Mobile is midway between two BTSs with the same PN, in a call on BTS APN energy of BTS A and B is indistinguishable in active search windowRake 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!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.

BTS BPN 142

BTS APN 142

x miles x miles



Adjacent-Active-PN Demodulation Errors

Mobile is in a call on BTS A from 1 mile away; A is the reference PNThe signal from BTS B on PN 99 travels 11 miles to the mobile and is approximately as strong as BTS A due to terrain effectsDue 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 callSolution: The PNs of the two BTSs are too close together. Use a different PN offset for BTS B.

BTS BPN 99

BTS APN 100

1 mile 11 miles



PILOT_INC Helps Avoid PN Problems

Imagine a network with base stations spaced approximately 10 miles apart - this is 1 PN offset!Recall if we use adjacent PNs for adjacent base stations, there will be locations where their PNs are close together or even indistinguishableIt would be smart to assign PNs farther apart!If properly set, PILOT_INC can prevent this problem

• Only PNs divisible by PILOT_INC are allowed to be assigned to sectors

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

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

D


Adjacent-Neighbor PN Recognition Errors

Mobile is in a call on BTS A, PN 100Mobile checks neighbor PN 200 to see if handoff needed with BTS FEnergy 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 FThe system sets up a traffic channel on BTS F - but mobile hears G!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!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

BTS APN 100

BTS

BTS

mountains

BTS

BTS FPN 200

BTS GPN 198

X

20 miles

NEIGHBOR SEARCH WINDOW


Sector PN Assignments:Consecutive Assignment

Use only PNs divisible by PILOT_INC.• PILOT_INC is chosen large enough to

prevent aliasing of pilots in adjacent cellsAssign PNs in sequence to the sectors of all the base stationsCommon Usage: This is the typical default method used in Nortel and Motorola CDMA networksAdvantage

• 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

4

8

12

16

20

24

28

32

36

40

44

48

52

56

60

64

68

72

76

80

84

88

92

96

100

104

108

112

116

120


Sector PN Assignments:Segment Assignment

Assign only PNs divisible by PILOT_INC• PILOT_INC is chosen to avoid aliasing

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

Although 512/3 = 170.666, the value 168 is usually used for the inter-sector PN incrementCommon Usage: default in Lucent networksAdvantage: In the field, interference is suddenly noticed from PN 468. Quickly, what is the source of it?

• Definitely some cells gamma sector!

4

172

340

8

176

344

12

180

348

16

184

352

20

188

356

24

192

360

28

196

364

32

200

368

36

204

372

40

208

376


PN Reuse ExplorationsA


PN Reuse – Symmetrical N=37 PatternA


PN Symmetrical N=37 Reuse Pattern Exploded View A


Introduction to CDMAPerformance Data

Introduction to CDMAPerformance Data

Course RF200 Section II.


What Data is Available for Performance Study?

CDMA data for analysis flows from three sources:• Switch, CDMA peripherals and base stations, and the Handset

Various software and hardware tools are available for collection and analysis of each of these streams of dataData contains messages and various indicators of RF performance

Access Mgr./BSC-BSMSwitch BTS

CDSU DISCO

Ch. Card ACC

ΣαΣβΣχ

TFU1GPSR

CDSUCDSU

DISCO 1DISCO 2

SBSVocodersSelectors

CDSUCDSUCDSUCDSUCDSUCDSU

CMSLM

LPP LPPENET

DTCs

DMS-BUS

Txcvr ATxcvr BTxcvr C

RFFE ARFFE BRFFE C

TFU1GPSR

IOC

BSM

Data AnalysisPost-Processing

Tools

IS-95/J Std 8 Messages

IS-95/J Std 8 Messages

NOIS Messages

QC-Specific Messages

Switch OMs,pegs, logs

Mobile DataPost-Processing

Tools

Mobile Data Capture ToolsSelector

Logs

NMIS Messages

HandsetMessages

ExternalAnalysis

Tools

PC-based

PC-based

Unix-based,PC-basedVarious

CDMA NETWORK EQUIPMENT HANDSET


Resources on System and Switch Data

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 softwareThe 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 cutting-edge hardware and software releases

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

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


System Data andStatistical AnalysisSystem Data and

Statistical Analysis


Statistical CDMA Performance Indicators

Dropped Call StatisticsFailed Access AttemptsBlocking Statistics

• BTS sector level• BSC resource level• Switch resource level• PSTN trunking level

Counts of specific call processing error events

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.


MTA

-Nam

e

Per

iod

Cel

ls

Cal

l-Att.

Cal

l-Suc

c.

%-S

ucc.

Tot

al-B

lock

%To

t-Blo

ck

RF

Acc-

Fail s

%R

F A

cc-F

ail

Cal

ls-D

rop

%-D

rop

Scr

een

Calls

% S

cree

n Ca

l

Example H Week ALL 1,147,447 1,123,308 97.9% 443 0.04% 12,429 1.1% 20,015 1.7% 11,229 1.0%Average of Others 96.1% 2.1% 2.8% 2.1% 0.6%

Comparing All Systems Sorted By Daily Traffic LevelExample System D Day All 1,338,386 1,240,937 92.7% 44,593 3.33% 35,329 2.64% 30,576 2.28% n/a n/aExample System E Day All 355,247 347,325 97.8% n/a n/a 7,922 2.23% n/a n/a n/a n/aExample System B Day All 227,257 222,425 97.9% 388 0.17% 4,444 1.96% n/a n/a n/a n/aExample System C Day All 220,707 205,766 93.2% 6,312 2.86% 6,090 2.76% 5,088 2.31% n/a n/aExample System A Day All 209,621 205,461 98.0% n/a n/a n/a n/a 3,297 1.60% 1,327 0.6%Example System F Day All 206,482 198,945 96.4% n/a n/a 7,537 3.65% 4,556 2.29% n/a n/aExample System H Day ALL 163,921 160,473 97.9% 63 0.04% 1,776 1.1% 2,859 1.7% 1,604 1.0%Example System G Day All 148,765 143,633 96.6% n/a n/a 5,132 3.45% 3,074 2.14% n/a n/a

Typical Network Performance

Here is a comparison of typical network performance in the industry against a new rural wireless system with light loadingHow does your system compare against the industry norms? Against the lightly loaded rural system?


Another Network Performance Example


Lucent System Data Examples




Sys/ECP/Ce ll/Name/Labe l TOTALS

179 2 67 SMIT HSPRING

S 179 2 10 BOBCAT

179 2 28 INGLEWOO

D

179 2 30 NOLENSVIL

LE

179 2 121 CLARKSVILLE/BRILEY

179 2 1 T EXT RON

179 2 45 FARMERS

%CDMA Est Ca lls 96.83 93.55 93.58 94.18 94.36 94.44 94.67 94.73ReAcquir e d_Ca lls 2.84 3.22 2.61 3.89 2.38 5.26 2.65 2.06

CCE erlangs 6,580.44 62.60 128.68 71.45 63.54 36.16 76.37 115.21CDMA_CE Usage 2,368,959 22,535 46,323 25,722 22,873 13,016 27,494 41,476Prim_CS CE_Use 1,451,816 9,300 19,788 13,689 11,113 8,448 15,965 23,219

%Prim_CS CE_Use 61.28 41.27 42.72 53.22 48.59 64.90 58.07 55.98Sec_CS CE_Use 917,143 13,235 26,535 12,033 11,760 4,568 11,529 18,257%CDMA SoftHO Use 38.72 58.73 57.28 46.78 51.41 35.10 41.93 44.02%CDMA SUFa il 2.79 6.14 5.68 5.44 3.62 3.68 4.64 5.04CDMA Lost_Ca ll 1,722 15 42 20 10 64 15 35

%CDMA Lost Ca lls 1.17 1.67 2.18 1.18 0.89 5.98 0.98 1.44T otCDMA Fa ilures 7,856 95 208 143 77 108 102 206CDMAT otl Origins 5,069 65 143 89 47 73 67 141CDMAT otl T ermins 2,787 30 65 54 30 35 35 65

CDMA Maint Busy 0 0 0 0 0 0 0 0CDMAOnly PrfSz 80 0 0 0 1 0 0 0CDMA_Org T rm_Ovf 713 0 0 0 0 0 0 0

CDMA Org_Sz 109,076 680 1,500 1,236 771 828 1,229 1,862CDMA Org_Asn 105,970 659 1,454 1,197 752 786 1,192 1,824CDMA Pg_Rsp_Sz 46,720 313 611 640 445 369 430 755CDMA T rm_Asn 44,951 301 590 603 412 329 414 736CDMA Req_Alg 4,426 32 55 73 29 63 44 54


Lucent Overload Data Examples from Autopace

Sys/ECP/Ce ll/Name /Ante nna ID/Ant_Na me TOTALS

179 2 1 T EXT RON 1

Ante nna :1

179 2 1 T EXT RON

2 Ante nna:2

179 2 1 T EXT RON

3 Antenna :3

179 2 2 BELMONT

1 Ante nna:1

179 2 2 BELMONT

2 Ante nna:2

179 2 2 BELMONT

3 Antenna :3CDMA_Acs Chn_Oc 5,921 30 28 10 27 13.00 13.00CDMA_Avg Sq_DG 1,123,466 6,187 6,157 6,088 6,168 5,016.00 4,818.00CDMA_Fwd PCOLdur 581 12 4 2 0 0.00 0.00CDMA_Fwd PCOLcnt 339 4 4 1 0 0.00 0.00

CDMA Intcpt_Msg 0 0 0 0 0 0.00 0.00CDMA_Pg Ch_Ocpn 489,506 2,771 2,763 2,754 2,795 2,756.00 2,766.00CDMA_Pk Acs_ChOc 91,989 985 563 281 563 422.00 281.00CDMA_Pk Pg_ChOc 555,984 3,264 3,140 3,197 3,125 3,120.00 3,155.00

CDMA_Re v PCOLdur 305 0 0 0 0 0.00 0.00CDMA_Re v PCOLcnt 6 0 0 0 0 0.00 0.00

CDMA Re orde r_Msg 2 0 0 0 0 0.00 0.00CDMA_T f CdCh_Usg 245,143 1,360 1,188 980 953 821.00 862.00

CDMA_Jmr Det_Dur 0 0 0 0 0 0.00 0.00


Nortel System Data Examples

Nortel System Data Examples


Nortel BTSC MO Attributes

Attribute Name DataType

Seq.Number

Access,Range Description

BlockedOriginationsNoTCE word16 0x0002A42

Pfull

Number of originations blocked because no idle channel elements were available

BlockedOriginationsNoFwdCap 0x0002B43

Number of originations blocked due to lack of BTS forward link excess capacity

BlockedOriginationsNoRevCap 0x0002C44

Number of originations blocked due to lack of reverse link capacity

BlockedHandoffsNoTCE 0x0002D45

Number of handoffs blocked because no idle channel elements were available

BlockedHandoffsNoFwdCap 0x0002E46

Number of handoffs blocked due to lack of BTS forward link excess capacity

BlockedHandoffsNoRevCap 0x0002F47

Number of handoffs blocked due to lack of reverse link capaicty

SuccessfulOriginations 0x0003048 Number of successful originations

SuccessfulHandoffs 0x0003149 Number of successful handoffs

word16

word16

word16

word16

word16

word16

word16

Pfull

Pfull

Pfull

Pfull

Pfull

Pfull

Pfull

Each attribute is a periodic counter maintained during the 15-minute automatic logging period.


Nortel FA MO AttributesEach attribute is a periodic counter maintained during the 15-minute automatic logging period.

FA MO Sequence Number OM name

FA MO Sequence Number OM name

16 TCEUtilMaximum 2D soft4softer1Alpha17 NumOfTCsConfigured 2E soft4softer1Beta18 soft1softer1Alpha 2F soft4softer1Gamma19 soft1softer1Beta 30 soft4softer2AlphaBeta1A soft1softer1Gamma 31 soft4softer2BetaGamma1B soft1softer2AlphaBeta 32 soft4softer2GammaAlpha1C soft1softer2BetaGamma 33 soft4softer31D soft1softer2GammaAlpha 34 soft5softer1Alpha1E soft1softer3 35 soft5softer1Beta1F soft2softer1Alpha 36 soft5softer1Gamma20 soft2softer1Beta 37 soft5softer2AlphaBeta21 soft2softer1Gamma 38 soft5softer2BetaGamma22 soft2softer2AlphaBeta 39 soft5softer2GammaAlpha23 soft2softer2BetaGamma 3A soft6softer1Alpha24 soft2softer2GammaAlpha 3B soft6softer1Beta25 soft2softer3 3C soft6softer1Gamma26 soft3softer1Alpha 3D TimeNotInUse27 soft3softer1Beta28 soft3softer1Gamma29 soft3softer2AlphaBeta2A soft3softer2BetaGamma2B soft3softer2GammaAlpha2C soft3softer3


Nortel BTSC MO Events

Event Report Name TypeEvent Report

Seq.Number Description

Each event counter is maintained during the 15-minute automatic logging period.

BTSCPerformanceData PerformanceData 0x000?0?

Includes as parameters all attributes with P access documented in the attribute table for

this MO.

FA MO Events

Event Report Name TypeEvent Report

Seq.Number Description

Each event counter is maintained during the 15-minute automatic logging period.

FAPerformanceData PerformanceData 0x000?0?

Includes as parameters all attributes with P access documented in the attribute table for

this MO.


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|


Nortel Selector Log File Example

=====================================================Status : OLFLR_OKRecord Type : NEIGHBOR_LIST_TUNING_DATA_ARRAYFile Offset : 414 (octal)Time Stamp : 97/10/29-00:29:25.380Record Length : 72Header Length : 51Source 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 0x2cfe821IMSI : NumDigits 15 Digits 134006043294814 (123-63-251-3692bf)ESN : 0x9f0d02acPFFlags : 0x1fSecondary Agent Id : 0x8a40FramingBytes : 0xfaaeSequence Number : 57AttributeType : 0x0256AttributeInstance : 0x0030

Log Attr -> Type : LogSBSNeighborListTuningDataArray Seq Num : 0030

LogData object contents:Data Type : NEIGHBOR_LIST_TUNING_DATA_ARRAYResource Type : OCC_SBS_RESOURCETimeStamp : 97/10/29-00:29:25.380Count : 2

Ext'dBaseId PowerCombineBit PilotStrength PNOffset+++++=========================++++=========================+++++0x018002a3 1 8 0x01040x018002a1 1 19 0x01a4=====================================================


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|


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.088 1 3 426.3 146.2 154 150 2.6 10 10 0.0 3 1.9 156.088 1 4 456.9 146.2 160 156 2.5 22 22 0.0 7 3.9 150.688 1 5 448.2 146.2 163 162 0.6 18 18 0.0 4 2.2 148.688 1 6 439.5 146.2 162 159 1.9 20 20 0.0 2 1.1 144.988 1 7 439.9 146.2 160 157 1.9 14 14 0.0 5 2.9 151.788 1 8 351.6 146.2 186 182 2.2 23 23 0.0 5 2.4 100.988 1 9 397.4 146.2 164 161 1.8 20 20 0.0 3 1.7 129.688 1 10 422.5 146.2 177 174 1.7 15 15 0.0 2 1.1 132.088 1 11 402.2 146.2 183 179 2.2 22 22 0.0 1 0.5 117.788 1 12 398.2 146.2 179 176 1.7 13 13 0.0 5 2.6 124.488 1 13 447.5 146.2 163 161 1.2 26 26 0.0 11 5.9 142.188 1 14 263.5 146.2 290 83 71.4 31 19 38.7 5 4.9 49.388 1 15 307.8 146.2 264 68 74.2 36 9 75.0 3 3.9 61.588 2 2 403.1 105.9 165 162 1.8 14 14 0.0 1 0.6 135.188 2 3 477.0 105.9 163 158 3.1 18 18 0.0 3 1.7 158.188 2 4 419.4 105.8 166 161 3.0 24 24 0.0 2 1.1 132.488 2 5 445.8 105.8 174 171 1.7 14 14 0.0 7 3.8 142.388 2 6 525.1 105.8 157 155 1.3 17 17 0.0 3 1.7 181.188 2 7 422.0 105.8 165 161 2.4 18 17 5.6 1 0.6 138.488 2 8 430.3 105.8 188 183 2.7 14 14 0.0 7 3.6 127.888 2 9 419.9 105.8 167 166 0.6 12 11 8.3 6 3.4 140.788 2 10 391.0 105.3 165 164 0.6 22 22 0.0 4 2.2 125.588 2 11 443.5 105.3 174 168 3.4 11 11 0.0 5 2.8 143.888 2 12 412.5 105.3 177 171 3.4 21 21 0.0 4 2.1 125.088 2 13 394.2 105.3 196 192 2.0 16 16 0.0 6 2.9 111.688 2 14 432.0 105.3 141 139 1.4 18 18 0.0 5 3.2 163.088 2 15 388.5 105.3 178 176 1.1 17 17 0.0 2 1.0 119.5


Analyzing System DataAnalyzing System Data


Total Blocked Call Percentage Example

This is an example of a cumulative system-wide total blocked call percentage chart maintained in one market

Total Block Call Percentage

1.0%1.5%2.0%2.5%3.0%3.5%4.0%4.5%5.0%5.5%6.0%6.5%7.0%7.5%8.0%

Date

Perc

ent

Blkd


Dropped Call Percentage Tracking Example

Dropped call percentage tracking by one market

Total Drop Call Percentage

0.0%

0.5%

1.0%

1.5%

2.0%

2.5%

3.0%

3.5%

4.0%

4.5%

5.0%

Date

Perc

ent

%Drops


Total System Daily MOU Example

Total system daily MOU plotted by one market

Daily Total System MOU

0

50000

100000

150000

200000

250000

300000

Date

MO

U

Daily Total System MOU


“Top Ten” Performance Tracking Example

Many markets use scripts or spreadsheet macros to produce ranked lists of sites with heavy traffic, performance problems, etc.

Call Attempts

Eng Site

MSC Site Call Att

Call Succ

%Call Succ

Block Calls

%Blck Calls

Acc Fail

%Acc Fail

Drop Calls

%Drop Calls Call Attempts

6.1 13X 2561 2234 87.2 130 5.1 130 5.1 145 5.72.1 2X 2244 2017 89.9 101 4.5 101 4.5 93 4.11.2 1Y 1922 1743 90.7 83 4.3 83 4.3 66 3.464.3 93Z 1833 1549 84.5 137 7.5 136 7.4 110 6.0108.2 30Y 1740 1589 91.3 46 2.6 45 2.6 83 4.81.3 1Z 1630 1495 91.7 31 1.9 31 1.9 81 5.063.2 57Y 1623 1486 91.6 49 3.0 49 3.0 66 4.1102.2 4Y 1615 1495 92.6 18 1.1 18 1.1 70 4.3108.1 30X 1490 1387 93.1 27 1.8 27 1.8 54 3.643.3 42Z 1488 1410 94.8 4 0.3 4 0.3 53 3.6

0

500

1000

1500

2000

2500

3000

6.1

2.1

1.2

64.3

108.

2

1.3

63.2

102.

2

108.

1

43.3

Sector

Cal

ls

% Blocked Calls September 5, 1997Eng Site

MSC Site Call Att

Call Succ

%Call Succ

Block Calls

%Blck Calls

Acc Fail

%Acc Fail

Drop Calls

%Drop Calls % Blocked Calls

64.3 93Z 1833 1549 84.5 137 7.5 136 7.4 110 6.06.1 13X 2561 2234 87.2 130 5.1 130 5.1 145 5.763.3 57Z 1282 1098 85.7 65 5.1 65 5.1 90 7.02.1 2X 2244 2017 89.9 101 4.5 101 4.5 93 4.11.2 1Y 1922 1743 90.7 83 4.3 83 4.3 66 3.463.2 57Y 1623 1486 91.6 49 3.0 49 3.0 66 4.164.1 93X 1027 926 90.2 30 2.9 30 2.9 58 5.726.3 35Z 855 698 81.6 24 2.8 24 2.8 112 13.1108.2 30Y 1740 1589 91.3 46 2.6 45 2.6 83 4.81.3 1Z 1630 1495 91.7 31 1.9 31 1.9 81 5.0

0.01.02.03.04.05.06.07.08.0

64.3 6.1

63.3 2.1

1.2

63.2

64.1

26.3

108.

2

1.3

Sector%


“Bracketing”: Fault Notification and Alarming

Some operators develop their own software for monitoring and tracking performance dataEach new 30-minute period is compared against a six-week average for that day and timeIf the new value is outside user-selectable tolerances (typically +/- 30%), an alarm is sent to operations personnel

• By SMS or pagerThe tolerance values can be adjusted to produce reasonable numbers of alarms

• Typically 20-40 alarms per day 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.

+30%

-30%

+30%

-30%

+30%

-30%

TOO LOW NORMAL TOO HIGH

6-week average

SMTWT F S SMTWT F S SMTWT F S SMTWT F S SMTWT F S SMTWT F S SMTWT F S23222120191817161514131211109876543210Historic Performance Data and Automatic Alarming


CDMA System ParametersCDMA System Parameters


Lucent BTS Parameters Example

SysID 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179 179ECPID 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2CellID 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2Antenna 1 1 1 1 1 1 2 2 2 2 2 2 3 3 3 3 3 3 1 1 1CDMAPilotPN 4 4 4 4 4 4 172 172 172 172 172 172 340 340 340 340 340 340 8 8 8CDMAPilotDrpThrsh -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15 -15CDMAPilotDetThrsh -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13 -13CDMACompThrsh 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2.5 2 2 2CDMADropTimer 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3CDMASrchWinActCand 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7CDMASrchWinNbr 9 9 9 9 9 9 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7CDMASrchWinRemain 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0CDMAPilotGain 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108 108CDMAPageGain 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64 64CDMASyncGain 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34CDMABCRAtt 6 6 6 6 6 6 6 6 6 6 6 6 8 8 8 8 8 8 8 8 8SectorSize_ceqfaceBBAMaxPower 33.5 33.5 21 21 33.5 33.5 33.5 33.5 21 21 33.5 33.5 33.5 33.5 21 21 33.5 33.5 25 25 25CDMAMinTrfChnlGain_R2CDMAMaxTrfChnlGain_R2CDMATrafGain_R2CDMAFwdFrmErrRate_R2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1CDMARevFrmErrRate_R2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1CDMANomEbNoSetPt_R2 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8CDMAMinEbNoSetPt_R2 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8 3.8CDMAMaxEbNoSetPt_R2 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8 8.8Srchwincell 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32


Nortel System Parameters Example

Nortel parameters are built in files on the BSM, then downloadedto BTS and SBS locations

Proto type datafill for 1900 CDMA System Parameters

Parameter Name Range Recommended Value Remarks

1. CDMA Channel ParametersSystem Determination and Acquisition

CDMA_ AVAIL 0 - 1 1CDMA_FREQ (CDMA_CHAN) 0 - 2047 See Remarks As determined by the local MTABAND_CLASS 0 - 31 1 1900 MHz

System Acquisition (Sync channel Information)P_REV 0-255 1MIN_P_REV 0-255 1SID 0 - 32,767 See Remarks As determined by the local MTANID 0 - 65,535 See Remarks As determined by the local MTAPILOT_PN 0 - 511 See Remarks As determined by the local MTALC_STATE See Remarks Determined by the system. TBASYS_TIME TFU_1 or TFU_2 See Remarks As detetermined by the System timePRAT 0-3 1 LP_SEC 0-255 13 TBALTM_OFF 0-63 16 TBADAYLT 0 - 1 0 or 1 Depending on whether Daylight saving is On/Off



Parameters here determine contents of Access Parameters Message on the Paging Channel

2. Access ParametersRequest Response Parameters

PSIST(0-9) 0 - 63 0 ACCOLC(0 -9) are all permitted to transmitPSIST(10-15) 0 - 7 0 ACCOLC(10 -15) are all permitted to transmitMAX_CAP_SZ 0 - 7 3 3 Frames messagePAM_SZ 0 - 15 4 4 Frames preambleREG_PSIST 0 - 7 0MSG_PSIST 0 - 7 0PROBE_PN_RAN 0 - 15 0ACC_CHAN 0 - 31 0 1 Access channelACC_TMO 0 - 15 (x80 ms) 3 (2+1), 240 msPROBE_BKOFF 0 - 15 0 (0 + 1) slot delayBKOFF 0 - 15 1 (0 + 1) slot delayMAX_REQ_SEQ 0 - 15 2MAX_RSP_SEQ 0 - 15 2AUTH 0 - 3 0 No standard AuthenticationRAND 0-(232-1) 0 Not applicable without Authentication



Parameters here determine the contents of the registration fields of the System Parameters Message on the paging channel

Registaration ParametersSID 0 - 32,767 See Remarks As determined by the local MTANID 0 - 65,535 See Remarks As determined by the local MTAREG_ZONE 0 - 4095 As determined by the network Zone Registration not currently supportedTOTAL_ZONES 0 - 7 0 Zone Registration not currently supportedZONE_TIMER 0 - 7 0 Zone Registration not currently supportedMULTI_SIDS 0 - 1 0 If roaming is permitted, this should be set to 1 MULTI_NIDS 0 - 1 0 If roaming or more than one NID in the MTA, set to 1BASE_ID 0 - 65,535 See Remarks As determined by the local MTABASE_CLASS 0 - 15 0 Public macro cellular systemPAGE_CHAN 0 - 7 1 One paging channelMAX_SLOT_CYCLE_INDEX 0 - 7 5HOME_REG 0 - 1 1FOR_SID_REG 0 - 1 1FOR_NID_NEG 0 - 1 1POWER_UP_REG 0 - 1 1POWER_DOWN_REG 0 - 1 1PARAMETER_REG 0 - 1 1REG_PRD 0 - 127 0 Periodic registration every 2621 sec (43 min)BASE_LAT -1296000, +1296000 See Remarks As determined by the local MTABASE_LONG -2592000, +2592000 See Remarks As determined by the local MTAREG_DIST 0 No distance based registrationRESCAN 0-2047 0



These parameters are communicated to the mobile in the overhead messages on the Paging Channel.

3. Power Control ParametersOpen Loop

NOM_PWR 0 -15 8 8' = 0 dBINIT_PWR 0 - 31 16 16' = 0 dBPWR_STEP 0 - 7 3 3 dBNUM_STEP 0 - 15 6 (6 +1) access probes per sequence

Forward Power ControlPWR_REP_THRESH 0 - 31 2 Only applicable to RateSet1 (8 kbps) dataPWR_REP_FRAMES 0 - 15 7 Only applicable to RateSet1 (8 kbps) dataPWR_THRESH_ENABLE 0 - 1 1 Only applicable to RateSet1 (8 kbps) dataPOWER_PERIOD_ENABLE 0 -1 0 Only applicable to RateSet1 (8 kbps) dataPOWER_REP_DELAY 0 - 31 1 4 frames, only applicable to RateSet1 (8 kbps) data

4. Handoff ParametersPilot Search Parameters

PILOT_PN 0-1 1 As determined by the local MTASEARCH_WIN_A 0 - 15(4 - 452 PN Chps) 8 60 PN chipsSEARCH_WIN_N 0 - 15(4 - 452 PN Chps) 10 100 PN chipsSEARCH_WIN_R 0 - 15(4 - 452 PN Chps) 10 100 PN chipsNGHBR_MAX_AGE 0 - 15 2PILOT_INC 0 - 15 4NGHBR_CONFIG 0 - 7 0

Pilot Strength ParametersT_ADD 0 - 63(-0.5x dB) 28 -14 dBT_DROP 0 - 63(-0.5x dB) 32 -16 dBT_TDROP 0 - 15 (=< 0.1 - 319 sec) 3 4 secT_COMP 0 - 15 (x0.5 dB) 5 2.5 dB


Nortel System Parameters ExampleNMIS Parameter Range Recommended Value Remarks

Acquisition

AccessChannelAcquisitionSearchWidth 25 - 4095 TBA Used by the BTS for the revese linkAccessChannelDemodulationSearchWidth 25 - 4095 TBA Used by the BTS for the revese linkTrafficChannelAcquisitionSearchWidth 25 - 4095 TBA Used by the BTS for the revese linkTrafficChannelDemodulationSearchWidth 25 - 4095 TBA Used by the BTS for the revese link

PowerControl RateSet1Data, RateSet2Data

PrRXerror (FER %)Full 1/16 - 256/16 16/16 1%Half 1/16 - 256/16 80/16 5%Quarter 1/16 - 256/16 80/16 5%Eighth 1/16 - 256/16 80/16 5%Unknown 1/16 - 256/16 16/16 1%RRXincreaseFull 1/256 - 4095/256 42/256Half 1/256 - 4095/256 7/256Quarter 1/256 - 4095/256 7/256Eighth 1/256 - 4095/256 7/256Unknown 1/256 - 4095/256 14/256

RateSet1Data PRXlower (Ew/Nt) 1/256 - 4095/256 2048/256 (8 - 10log2) = 5 dB Eb/Nt PRXupper (Ew/Nt) 1/256 - 4095/256 3328/256 (11 - 10log2) = 8 dB Eb/Nt PRXstart (Ew/Nt) 1/256 - 4095/256 2688/256 (10.5 - 10log2) = 7.5 dB Eb/Nt

RateSet2Data PRXlower (Ew/Nt) 1/256 - 4095/256 2509/256 (10 - 10log3) = 5.2 dB Eb/Nt PRXupper (Ew/Nt) 1/256 - 4095/256 3789/256 (13 - 10log3) = 8.2 dB Eb/Nt PRXstart (Ew/Nt) 1/256 - 4095/256 3149/256 (12.5 - 10log3) = 7.7 dB Eb/Nt

RateSet1Data PrTXerror 1/16 - 256/16 16 1% RTXincrease 1/256 - 4095/256 20/256 PTXlower -4095/256 - 0/256 -2304/256 -9 dB PTXupper -4095/256 - 0/256 -768/256 -3 dB PTXstart -4095/256 - 0/256 -1536/256 -6 dB

RateSet2Data PrTXerror 1/16 - 256/16 16 1% RTXincrease 1/256 - 4095/256 133/256 PTXlower -4095/256 - 0/256 -3072/256 -12 dB PTXupper -4095/256 - 0/256 -256/256 -1 dB PTXstart -4095/256 - 0/256 -1536/256 -6 dB

PowerControlGainOffset -127 to 128 0



Wilting and blossoming are techniques for gracefully taking a sector from service or returning it to service without dropping traffic.

Wilting, Blossoming and Breathing Parameters

WiltBlossStepSize 0/16 - 255/16 dB (0-255) 4/16 dB (4) Rate should be 1 dB/secWiltBlossStepTime 1 - 20 (units of 100 ms) 1 100 msecWiltBlossEnabled 0 - 1 1BreathingStepSize 1/16 - 255/16 dB/ms 4/16 dB/ms Rate should be 1 dB/secBreathingStepTime 1 - 20 (units of 100 ms) 1 100 msecBreathingDelta 0/16 - 255/16 dB (0-255) 192/16 (4 dB [64] or more) 12 dB rise over the noise floorBreathingEnabled 0 - 1 0 DisabledRecPowerEstimationFilterRate 2 - 40 (units of 5 ms) 4 Steps of 5 ms. 4 =20 msRecPowerDecayExponential 0 - 16 6TXAttenNormal 0-70 (0/16 - 1120/16 dB) See Remarks As given by the installtion & calibrationTXPowerMax 384/16 - 736/16 dBm 672/16 42 dBm(16 W)TXAttenAntenna 0-6 (0/16 - 96/16 dB) 0 As determined by Pilot Channel calibration process. As measureTPEFilterDecayExponential 0 - 16 5ReverseLinkCapacityEstimationRate 20*5 to 255*5 ms 100 (20*5) Not supportedHandoffBlockingThreshold 0-100 % 5? Not supportedCallBlockingThreshold 0-100 % 10? Not supportedRXFEGain RcvrA 0/16 - 480/16 dB See Remarks As given by the installtion & calibration RCVRB 0/16 - 480/16 dB See Remarks As given by the installtion & calibrationRXFENoiseFigure RCVRA 0/16 - 160/16 dB See Remarks As given by the installtion & calibration RCVRB 0/16 - 160/16 dB See Remarks As given by the installtion & calibrationRXCableAtten According to above cable loss of antenna path for the specific ap RcvrA 0/16 - 480/16 dB See Remarks As given by the installtion & calibration RCVRB 0/16 - 480/16 dB See Remarks As given by the installtion & calibrationRXCableNoiseFigure Close to RxCableAtten According to noise figure intro'd due to cable loss of antenna pat RCVRA 0/16 - 160/16 dB See Remarks As given by the installtion & calibration RCVRB 0/16 - 160/16 dB See Remarks As given by the installtion & calibrationRXCardNoiseFigureMin 0/16 - 1120/16 5 dB for 800, 4 dB for 1900 As given by the Rx card calibrationRXCardNoiseFigureMax 0/16 - 1120/16 960/16 60 dB



These parameters set the power levels of the overhead channels.

Pilot Data BasePilotChannel

CDMACenterFrequency ?? See Remarks As determined by the Preferred Channel SetExtendedBaseId word32 See Remarks BandClass, CDMAFreq,BASE_ID,SectorAvailable 0 -1 1QuickRepeat 0 -1 0 disabledBlankAndBurst 0 -1 0 Not usedForwardGain 0 - 255 TBAPilotGain 0 - 255 216 216 for 800 MHzMinPilotToTotalPwrRatio -255/16 to 0/16 dB -7 20% of HPA powerNeighborList word32Array, up to 20 nieghb See Remarks As determined by the RF designCellType CELL_STANDARD, CELL_P CELL_STANDARD If no HHO in the cell

CELL_BORDERSyncChannel

SyncGain 0 - 255 68 10 dB down from pilot for 800 MHz

PagingChannelPagingGain 0 - 255 130 4.4 dB down from pilot for 800 MHz


Motorola System Parameters

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.This document gives descriptions of most system parameters and many operational peg counts and valuable guidance for setting parameters.



Forward Pwr Ctrl Sector 1 Sector 2 Sector 3 Default

C1 C1 C1

PilotPn 66 237 408 0

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 2 2 2 Frm

PwrThreshEna 1 1 1 1

PwrPeriodEna 0 0 0 0

PwrRepThresh 3 3 3 3 Frm

PwrRepFrames 7 7 7 7 Frm

PwrRepDelay 12 12 12 12 Frm



Reverse Pwr Ctrl Sector 1 Sector 2 Sector 3 Default

C1 C1 C1

NomPwr 3 3 3 3 dB

InitPwr -3 -3 -3 -3 dB

PwrStep 5 5 5 5 dB

NumStep 4 4 4 4

RPCMaxEbNo 12.5 12.5 12.5 12.5 dB

RPCNomEbNo 9 9 9 9 dB

RPCMinEbNo 6 6 6 6 dB

RPCThrshNom 1930 1930 1930 0

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 6 6 6 10 km



Handoff Sector 1 Sector 2 Sector 3 Default

C1 C1 C1

SrchWinA 6 6 6 6 chp

SrchWinN 8 8 8 8 chp

SrchWinR 9 9 9 9 chp

TAdd -14 -14 -14 -14 dB

TDrop -16 -16 -16 -16 dB

TComp 4 4 4 4 dB

TTDrop 3 3 3 3


Motorola System ParametersTCH Gain Sector 1 Sector 2 Sector 3 Default

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 5 StepDown 1 1 1 1 DeltaTime 7 7 7 7 FrmStepDownDel 21 21 21 21 FrmOrigDelay 100 100 100 100 FrmTchWCCnt 42 42 42 42 TCH


Motorola System ParametersN-Way Sector 1 Sector 2 Sector 3 Default

C1 C1 C1 HoConstr 1 1 1 1 MaxActSetSz 6 6 6 6 MaxCEPerCall 3 3 3 3 TcompEnaThr -14.5 -14.5 -14.5 -14.5 MaxBTSLegs1 3 3 3 3 MaxBTSLegs2 2 2 2 3 MaxBTSLegs3 2 2 2 2 AggActLimit1 35 35 35 35 AggActLimit2 43 43 43 43 AggActLimit3 51 51 51 51 EnableSofter Enable Enable Enable 0 EnableBTS Enable Enable Enable 0 EnableSoft Enable Enable Enable 0 AggrStr1 0 0 0 -6 dB AggrStr2 -7 -7 -7 -8 dB AggrStr3 -9 -9 -9 -10 dB NumCandidate 10 10 10 10 XCTComp 3 3 3 4 dB SofterShuff 3 3 3 3 dB BTSShuffleC 3 3 3 0 dB SoftShuffle 3 3 3 3 dB


Introduction toOptimization Tools

Introduction toOptimization Tools

Course RF200 Section III


Introduction To CDMA Field Tools: Topics

Two Important Concepts• The Department Store Analogy - Tops-Down vs. Bottoms-Up• The Aeronautical Analogy - Accident Investigation Resources

Survey of CDMA Field Tools• Mobile Tools• Handsets - Maintenance Displays


Department Store Analogy: Tops-Down, Bottoms-Up

Some things are easier to measure from the customer side!

Complex!!! Simpler

System Phone

Neighbor ListsData Analysis

SoftwareTrans-

mission

Configuration

Provisioning

PSTN Trunking

Dropped Calls

CoverageAccess Failures

Switch

BTS

CBSC

InterferenceAdministration

Data CaptureField Tools

Profits

Complex!!! Simpler

Management Test Shopper

Labor Relations

Cost

sTaxe

s Insurance

Suppliers

Leases

Capital

Stocking

Distribution

Loss

esAdvertis

ing

Selection

ConveniencePrice

Service


Aeronautical Analogy: Tools for Problem Investigation

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.

Control & Parameters Messaging

BTS

1150011500

114.50118.25130.75

AeronauticalCase

CDMA Case

Flight Data Recorder Cockpit Voice Recorder

Temporal Analyzer Data Layer 3 Message Files


Sources of CDMA Data and Tools for Processing

CDMA optimization data flows from three places:• Switch• CDMA peripherals (CBSC & BTS)• Handset

Each stream of data has a family of software and hardware tools for collection and analysis

CBSCSwitch BTS

CDSU DISCO

Ch. Card ACC

ΣαΣβΣχ

TFU1GPSR

CDSUCDSU

DISCO 1DISCO 2

SBSVocodersSelectors

CDSUCDSUCDSUCDSUCDSUCDSU

CMSLM

LPP LPPENET

DTCs

DMS-BUS

Txcvr ATxcvr BTxcvr C

RFFE ARFFE BRFFE C

TFU1GPSR

IOC

BSM

Data AnalysisPost-Processing

Tools

IS-95/J-STD-008 Messages

IS-95/J-STD-8 Messages

Switch Datapegs, logs

Mobile DataPost-Processing

Tools

Mobile Data Capture Tools

HandsetMessages

ExternalAnalysis

Tools

PC-based

PC-based

Unix-based,PC-basedVarious

CDMA NETWORK EQUIPMENT HANDSET

System Internal Messages


Autonomous Data CollectionBy Stowaway Mobiles

Autonomous Data CollectionBy Stowaway Mobiles


Stowaway Mobiles

Some operators are using “stowaway” mobiles in courier vehicles or public transport (under agreement, of course)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

The data collection begins anytime the vehicle is driven Collected data is uploaded to a server on the systemThe central server also provides post-processing functions via a web interface, allowing remote users to examine data for their areas


Autonomous Data CollectionBy Subscriber Handsets

Autonomous Data CollectionBy Subscriber Handsets


Using Autonomous Collection

A Server downloads software to a large population of subscriber mobilesMobiles collect on custom profiles

• all or groups of mobiles can be enabled/disabled• new triggers can be rapidly developed and downloaded when desired

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.Server manages data, provides filtering and reportingPerformance optimizers use terminals and post-processing software

t1t1 vSELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent

BackboneNetworkInternet

VPNs

PSTN

T TSECURE TUNNELSAuthentication

AuthorizationAccounting

AAABTS

(C)BSC/Access ManagerSwitch

Collection Server•software download•collected data upload•data management, analysis

BTS

BTS

BTS


Advantages of Autonomous Collection

Mobile-reported data can be location-binned

• post-processing provides visual identification of problem areas

Collection can be rapidly enabled per cell or area for immediate investigation of problem reportsRequires less employee drive time for collectionCustomer mobiles cover area more densely than drivetestersCustomer mobiles include in-building populationsIndividual mobile identification can be included with customer permission for direct customer service interaction


Current Issues in Autonomous Collection

Requires extensive software capability to develop/manage• current progress is from specialty application consulting houses

Requires cooperation of handset vendor to effectively integrate software onto handset platform

• caution required to avoid negative call processing side-effectsPrivacy issues involved if any user-specific data trackingAdditional network capacity required for large-scale reporting

t1t1 vSELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs

PSTN

T TSECURE TUNNELSAuthentication

AuthorizationAccounting

AAABTS

(C)BSC/Access ManagerSwitch

Collection Server•software download•collected data upload•data management, analysis

BTS

BTS

BTS


Conventional Field ToolsConventional Field Tools


CDMA Field Test ToolsField Collection Tools using Handset Data

There are many commercial CDMA field test toolsCharacteristics 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

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!

QualcommMDM, CAIT

Andrew

Comarco

TouchWave

EricssonTEMS

Motorola

PN Scanners

Agilent

Agilent BerkeleyVaritronics

Andrew Qualcomm

DTI TouchWave


Qualcomm’s MDM: Mobile Diagnostic Monitor

The Qualcomm Mobile Diagnostic Monitor was the industry’s first field diagnostic tool

• used industry-wide in the early deployment of CDMA

• pictures at right from Sprint’s first 1996-7 CDMA trials in Kansas City

Qualcomm’s Mobile Diagnostic Monitor • CDMA handset (customer provided)• Proprietary connecting cable• PC software for collection and field pre-

analysis– Temporal analyzer display mode– Messaging


Andrew’s Invex3G Tool

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


Touchwave Tools

The BlueRose platform can manage multiple phones and collect data

• Internal processor manages test operations independently for stand-alone operation

• Internal PCMCIA flash card provides storage

• An external PC can display collected data during or after data collection


Agilent Drive-Test Tools

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

CDMA phones• A very flexible digital receiver

with several modesPN Scanner

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

Spectrum Analyzer• Can scan entire 800 or 1900

mHz. BandsBase-Station Over-Air Tester (BOAT)

• Can display all walsh channel activity on a specific sector

• Useful for identifying hardware problems, monitoring instantaneous traffic levels, etc.

Post-Processing tool: OPAS32


IS-95 Busy SectorSnapshot of Walsh Usage


1xRTT Busy SectorWalsh Code Usage


Comarco Mobile Tools

X-Series Units for more data-intensive collection activities

• Multiple handsets can be collected

• Data is displayed and collected on PC

LT-Series provides integrated display and logging"Workbench" Post-Processing tool analyzes drive-test files


PN ScannersWhy PN scanners? Because phones can’t scan remaining set fast enough, miss transient interfering signalsBerkeley Varitronics

• high-resolution, GPS-locked– full-PN scan speed 26-2/3 ms.

• 2048 parallel processors for very fast detection of transient interferors

Agilent (formerly Hewlett-Packard)• high resolution, GPS-locked

– full-PN scan speed 1.2 sec.• Integrated with spectrum analyzer and

phone call-processing toolAndrew

• 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


Post-Processing Tools

Post-Processing tools display drive-test files for detailed analysis - Faster, more effective than studying data playback with collection tools aloneActix Analyzer

• Imports/analyzes data from almost every brand of drive-test collection tool

Andrew (formerly Grayson) Interpreter• Imports/analyzes data from Andrew Invex3G

Nortel RF Optimizer• Can merge/analyze drive-test and Nortel CDMA

system dataXceed Technologies Windcatcher

• Imports/analyzes data from almost every brand of drive-test device

Xceed Technologies Vortex• Provides automated analysis of data from manual,

autonomous, and stand-alone sourcesVerizon/Airtouch internal tool “DataPro”

Analyzer Interpreter

Windcatcher

Vortex


Drive-Testing

Some General GuidelinesSome General Guidelines


Safety Considerations

Don’t worry for the company’s loss due to your accidental death• Qualified and eager replacements have resumes on file• We’re constantly buying more drive-test vehicles• We were going to replace that old drive-test equipment soon• We’re not really sure we needed your last drive test, anyway• Your death will serve as a warning to others, so it’s not in vain

It’s OK to be careful and continue living for your own sake if you wish!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

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 activityIf the PC freezes, the power cord pops out, or any other problem occurs while collecting, don’t try to deal with it or correct it while driving

• Just pull over to the next really safe place to assess and correct


Physical Considerations

Be sure the connections (power, phone, PC and GPS cables) are secure so they won’t dislodge during collection and distract youBe sure the equipment is physically restrained so it won’t go flying around and hit you in case of a panic stop or sudden swerveSome GPS antennas are not weatherproof. Try to avoid getting them drenched in heavy rainThe GPS antennas should be mounted where they have a view of the sky as unobstructed as possibleExternal 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


Operational Concerns

The ideal length for drive-test files is 30 minutes to an hour• You’d 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, it’s nice if they are in

small files that can be easily processed and storedAlways make sure you have at least 2 or 3 GB of free hard drive space before you start a new drive-test collection

• Don’t 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 you’re collecting and transferring big files

Don’t retrace large parts of your travel path during a drive-test run• It’s harder to distinguish what happened on each run when analyzing

drives that cruise the same road multiple timesAlways stop the test call before you stop recording -- otherwise, post-processing software may misinterpret calling events


Getting Location Data into Drive-Test Files

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:GPS Global Positioning System

• This is the least expensive and most popular source of location information for drive-testing since 1992

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

LORAN• MF Loran transmissions are only reliable in some coastal areas

and are being phased out


GPS BasicsGPS (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.

Other Global Navigation Systems:• Europe: Galileo (not yet launched) • Russia: GLONASS (in poor repair)

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 user’s elevation already known• GPS reception is often blocked in cities, under bridges, dense forests,

or wherever obstacles interrupt the signal pathDead Reckoning is a method of supplementing GPS with independentlocation information when GPS can’t be receivedDifferential GPS is a technique adding independent corrections to received GPS data for better accuracy. GPS civilian accuracy wasimproved in May, 2000. DGPS hasn’t been widely used since then


Dead-Reckoning Systems

Dead-reckoning systems normally use a combination of magnetic compass and wheel rotation sensors to augment GPSThe manufacturer’s 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


Maintenance Features of CDMA Handsets

Maintenance Features of CDMA Handsets

Drive-Tests: Phones


Handsets as Tools: Simple but always Available!

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:

Enter the maintenance mode by special sequence of keystrokesDisplayed Parameters

• PN Offset, Handset Mode, Received RF Level , Transmit Gain AdjustMaintenance Display Applications

• best serving cell/sector• simple call debugging (symptoms of weak RF, forward link

interference, etc.)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


Interpreting Samsung Maintenance Display:Acquisition, Idle, and Access States

Debug ScreenS04274 SI2 2T-56 D070-04P0060 CH0350PR6 RC0 0Z11

V206T144L:02

Reference PN Offset

0 - Pilot Channel Acquisition Substate1 - Sync Channel Acquisition Substate2 - MS Idle State3 - System Access State4 - Traffic Channel State5,6,7 - various call service options

Processing StateReceive Power,

dbm

Transmit Gain Adjust,

db

Display toggles between:System Identifier (SID)Network Identifier (NID)

Carrier Freq.(Channel #)

Ec/Io, db(primary PN only)

Slot Cycle Index

System ProtocolRevision Level

Packet Zone IDRadio Configuration(Idle mode = 0, 0)


Interpreting Samsung Maintenance Display:Traffic Channel State

Debug ScreenTE8 RE8 40 6T-10 D070-04P0060 CH0350PR6 RC33 Z11SO00003 G207F001.54%L:02

PN Offset

0 - Pilot Channel Acquisition Substate1 - Sync Channel Acquisition Substate2 - MS Idle State3 - System Access State4 - Traffic Channel State5,6,7 - various call service options

Processing StateReceive Power,

dbm

Transmit Gain Adjust,

db

Carrier Freq.(Channel #)

Ec/Io, db(primary PN only)

FCH Walsh Code

System ProtocolRevision Level

Packet Zone ID

Transmit (RL)Vocoder Rate

1 = 1/82 = 1/44 = 1/28 = Full

Receive (FL)Vocoder Rate

Radio Configuration(RC3, RC3 common)

Live CumulativeFER

Service Option


Denso Maintenance Display

CBV: 3957ABV: 3954 ABT: 031ARF: 0000 CCL: 01SID: 04157NID: 00001CH: 0100 RSSI: 093DPN: 084 TX:-46BFRM:0000000968TFRM:0000135712FER:% 000.71LT: 036:06:36LG: -086:45:36EC: -16 -63 -63PN: 084 084 084FNGLK: Y Y NWLSH: 01 01 01ACT: 084 484 096-01 -01 200CND: 220 332 200200 332 NGH: 076080 340 068 196O56 320 220 316344 488 196 200392 124 128 084224 008 084

DCharging Battery Voltage

Average Battery Voltage Average Battery Temperature

System IDNetwork ID

RF Channel FrequencyDigital PN Offset

Received Signal StrengthEstimated Transmitter

Power OutputNumber of Bad Frames

Number of Good Frames Frame Erasure Rate, PercentBase Station coordinates

Current status of Rake Fingers

Active Pilot Set

Candidate Pilot SetNeighbor Pilot Set


Sanyo SPC-4500 Maintenance Display

Choose the following:DISPLAYOK0OKEnter Code: 0 0 0 0 0 0Debug MenuSCREENOK


Sanyo SPC-4900 Maintenance Display

##040793select MENU/OK buttonscroll to save Phone #select

PN offset

Call Proc. StateReceivePower

Io

ChannelFrequency


The Motorola 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 displayGetting Out of Maintenance Mode:

• Press “EXIT” at bottom of “Field Test Mode” screen


Maintenance Display on the Motorola Q:The CDMA Parameters

CDMA 111 60 1 20 P 50186 120 0 IDL CE84 H N/A 0.00 0NA 4139 43 6 2 0

EVDO 100 120 0x785B64D2 5111 79 -77 -128 128 7OPN ACC 0 70.11.225.186

Strongest Active PilotPN Ec/Io (-)

Number ofActives

Number ofNeighbors

Number ofCandidates

Strongest Neighbor PilotPN Ec/Io (-)

CarrierChannel #

Band:P=PCS, C=800

Call ProcessingState

Reason LastCall Ended

Receive Power, dbm

Current Service Option

Transmit Power, dbm

Avg. FER

# dropped calls

# total calls

SID NID


Maintenance Display on the Motorola Q:CDMA Call Proc. States, Call End Reasons

Last Call End IndicatorNI No Indication yetMR Mobile ReleaseBR Base Sta. ReleaseTC Traffic Channel LostL2 Layer 2 Ack FailNC No Channel Assn MsgN5 N5M failureBS BS Ack failureWO L3 WFO State TimeoutMP Max Probe FailurePC Paging Channel lossRR Reorder or Release on PCH?? Unknown Condition

Call Processing StatesCP CP ExitRST CP RestartRTC RestrictedPLT Pilot AcquisitionSYN Sync AcquisitionTIM Timing ChangeBKS Background SchIDL IdleOVD OverheadPAG PagingORG Call OriginationSMS Short Message SvcORD Order ResponseREG RegistrationTCI Tfc Ch InitializationWFO Waiting for OrderWFA Waiting for AnswerCON Conversation stateREL ReleaseNON No State

Current Service Option8V 8K voice originalIL 8K loopback8EV 8K EVRC8S 8K SMS13L 13K loopback13S 13K SMS8MO 8K Markov OldDAT Data8M 8K Markov New13M 13K Markov New13V 13K Voice


Maintenance Display on the Motorola Q:The EVDO Parameters

CDMA 111 60 1 20 P 50186 120 0 IDL CE84 H N/A 0.00 0NA 4139 43 6 2 0

EVDO 100 120 0x785B64D2 5111 79 -77 -128 128 7OPN ACC 0 70.11.225.186

PN

CarrierChannel #

UATI

Receive Power, dbm

HDR Session State

IP Address


Entering Maintenance Mode: Motorola StarTacContact your service provider to obtain your phone’s Master

Subscriber entity Lock (MSL). Then enter the following: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. Don’t delay -continue quickly and enter:

FCN 0 0 * * T E S T M O D E STO • The display will briefly show US then just '.

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.

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.)Now press STO to accept the entry and exit back to the ' prompt.Power off and back on.You should now be in test mode!


RX Power BatteryCondition

N5 N5M failureBS BS Ack failureWO L3 WFO State TimeoutMP Max Probe FailurePC Paging Channel lossRR Reorder or Release on PCH?? Unknown Condition

ChannelNumber

#Neighbors

Local Time#

ActivesStrongest Active

PN Ec/IoStrongest NeighborPN Ec/Io

# Cand-idates Call Proc

StateLast Call

Exit Reason# Drops

# CallsLast Call FER%

NIDSIDRx Powerdbm (Io)

Tx Powerdbm

CurrentService Option

Last Call IndicatorNI No Indication yetMR Mobile ReleaseBR Base Sta. ReleaseTC Traffic Channel LostL2 Layer 2 Ack FailNC No Channel Assn Msg

Current Service Option8V 8K voice originalIL 8K loopback8EV 8K EVRC8S 8K SMS13L 13K loopback

13S 13K SMS8MO 8K Markov OldDAT Data8M 8K Markov New13M 13K Markov New13V 13K Voice

Call Processing StatesCP CP ExitRST CP RestartRTC RestrictedPLT Pilot AcquisitionSYN Sync AcquisitionTIM Timing ChangeBKS Background SchIDL IdleOVD OverheadPAG Paging

ORG Call OriginationSMS Short Message SvcORD Order ResponseREG RegistrationTCI Tfc Ch InitializationWFO Waiting for OrderWFA Waiting for AnswerCON Conversation stateREL ReleaseNON No State


Motorola V120C Series

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


Motorola V60C

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


Nokia 6185 Maintenance Display

Enter *3001#12345# MENUScroll down to Field testPress SelectScroll up to EnabledPress OKPower the phone off and onYou should now be in Field test mode


Novatel Merlin C201 1xRTT Data Card

Enter # # D E B U G to enter maintenance mode.To exit, just click “OK” box in the Debug window.


Audiovox Thera Maintenance Mode Screens

How to enterDebug Mode:

[ctrl] [D] [enter]

Advanced Usr Pwd:##DEBUG [enter]

Protocol Statistics


Sierra 580 1xEV-DO Rev 0 Aircard

To enter the maintenance display, hover your cursor over the Connection Manager main indicator window or the Start button and type “##debug”.

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.


Novatel S720 EV-DO Rev. A Aircard:Entering Debug Mode

To enter the maintenance display, hover your PC’s cursor over the Connection Manager main indicator window or the Go button and type “##debug”.


Novatel S720 EV-DO Rev. A AircardDebug Display


Multi-Carrier Operationand Its Complications

Multi-Carrier Operationand Its Complications

RF200 Section IV


A CDMA network with 5 carriers


It’s A Multi-Carrier/Multi-System/Multi-Manufacturer

World!

Systems are forced to use multiple carriers to achieve needed traffic capacity

• It’s important that the traffic load be divided between carriersPhysically adjacent friendly systems often desire to allow seamless mobile operation across their borders, although they use different carrier frequenciesEven within one large network, seamless mobile operation is desired across serving switch boundariesThese 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

handoffMulti-Carrier Operation is a complex sport


Transitions at System Boundaries

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!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)

IDLE

IN-CALL

IDLE

IN-CALL


Foundation for Transition Troubleshooting

Multi-carrier and intersystem boundary transitions are complex relationships between mobile, air interface, and system

• to solve problems, it’s necessary to understand the basic actions of mobile and the system

– this information comes from the standard, summarized in the nextfew slides

The mobile’s 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

For in-call transition troubleshooting, the system’s 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 operator’s own network design


The Mobile View:When Do I Change Frequencies?

The Mobile View:When Do I Change Frequencies?


Multi-Carrier Operation:Mobiles Change Frequencies. When/Why/How?

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

Fortunately, there are defined triggers for all of these situations

Idle ModeFinding the System Call Start In-Call Operation



Finding the System

102565025

125250175384100375675625825

MRU PRLXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXX

Start at topOf MRU andCheck until A signal is

found

Look up foundSignal in PRL

And try to climbTo more preferredSignal if available

A



Idle Mode

Channel List Message

50, 125, 175Hash and go!

A



Idle Mode

Global ServiceRedirection Message

ACCOLC:1111100000100000GO TO CH. 225

If your ACCOLC is ON,Go where they tell you!

A



Idle Mode

Neighbor List Message

F1 PN240 F1 PN232F1 PN168 F2 PN240F1 PN336 F2 PN272F1 PN500 F3 PN240F1 PN372 F2 PN474

Check neighbors on Other frequencies during

Unused paging slots.If stronger than currentActive, do idle mode

Handoff to new frequencuy

A



Idle Mode


50, 125, 175Hash and go!


ACCOLC:1111100000100000GO TO CH. 225







A



Call Start

Getting Started:Mobile sends

Page Response orOrigination Message

System evaluatesPresent loading on

Each carrier andPrepares a trafficChannel on the

Carrier it prefers.System sends channelAssignment message

To the mobile

Mobile goes to theFrequency it is told

Nortel: MCTALucent: Pooling

Motorola: Pooling

A



In-Call Operation

NORMAL SOFT HANDOFFSMobile monitors pilotsAnd sends PSMM to

Request handoffs When it desires

No Frequency Changes

A



In-Call Operation

HARD HANDOFFSMobile cannot see signals

On other frequencies.System must use special

“traps” to triggerAnd decide handoffs:

Pilot Beacons

PILOTDATABASE

A



In-Call Operation




Round-Trip Delay, orEc/Io and Quality Triggers

Border CellsRTD rings

A



In-Call Operation






Pilot Beacons



PILOTDATABASE

A



Idle Mode


50, 125, 175Hash and go!


ACCOLC:1111100000100000GO TO CH. 225







Finding the System

102565025

125250175384100375675625825

MRU PRLXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXXXXX XXX XXX XXX XXX

Start at topOf MRU andCheck until A signal is

found

Look up foundSignal in PRL

And try to climbTo more preferredSignal if available

Call Start

Getting Started:Mobile sends

Page Response orOrigination Message

System evaluatesPresent loading on

Each carrier andPrepares a trafficChannel on the

Carrier it prefers.System sends channelAssignment message

To the mobile

Mobile goes to theFrequency it is told

Nortel: MCTALucent: Pooling

Motorola: Pooling

In-Call Operation






Pilot Beacons



PILOTDATABASE


Hard Handoffs

Soft Handoff is the preferred mode in CDMA. Its diversity provides excellent reliability and resistance to fading.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)

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 linksNotice that if the new target sector is on a different frequency than the mobile’s current call, the mobile will not even see its pilot and will not know to request a handoff!


Triggering Hard Handoffs in Traffic

Hard Handoffs during a mobile’s 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 system’s 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


NEW FORWARD TRAFFIC CH. NEW REVERSE TRAFFIC CH.

Hard Handoff Messaging(Beacon Trigger)



PILOT STRENGTH MEAS.MSG. (BEACON SEEN)







IN-TRAFFIC SYS. PARAM.MESSAGE (OPTIONAL)


NEW FORWARD TRAFFIC CH. NEW REVERSE TRAFFIC CH.

Hard Handoff Messaging(RTD Trigger)








IN-TRAFFIC SYS. PARAM.MESSAGE (OPTIONAL)


Hard Handoff in Traffic Messaging (1)

QcpCdmaLogMsgForTrafChan11/09/2002 00:07:55MSG_LENGTH: 17 octetsMSG_TYPE: Extended Handoff Direction MessageACK_SEQ: 5 MSG_SEQ: 3 ACK_REQ: YesENCRYPTION: Encryption DisabledUSE_TIME: YesACTION_TIME: 240 msHDM_SEQ: 3SEARCH_INCLUDED: YesSRCH_WIN_A: 130 chipsT_ADD: -9.0 dBT_DROP: -11.0 dBT_COMP: 2.5T_TDROP: 2 secHARD_INCLUDED: YesFRAME_OFFSET: 5.00 msPRIVATE_LCM: No RESET_L2: YesRESET_FPC: Yes SERV_NEG_TYPE: YesENCRYPT_MODE: Encryption DisabledNOM_PWR_EXT: NoNOM_PWR: 0 dBNUM_PREAMBLE: 7BAND_CLASS: 800 MHz Cellular BandCDMA_FREQ: 384ADD_LENGTH: 0PILOT_PN: 360PWR_COMB_IND: NoCODE_CHAN: 48RESERVED: 0

QcpCdmaLogMsgRevTrafChan11/09/2002 00:07:55MSG_LENGTH: 7 octetsMSG_TYPE: Order MessageACK_SEQ: 3 MSG_SEQ: 4 ACK_REQ: NoENCRYPTION: Encryption DisabledORDER: Mobile Station Acknowledgement OrderADD_RECORD_LEN: 0 octetsRESERVED: 0

Increasing RTD or perhaps a PSMM with a Beacon listed has alerted the system to the need for the hard handoffThe EHDM at left is sent to the mobileNotice the “Hard Included” terms like those normally seen when setting up a traffic channel initiallyNotice also the larger Srch_Win_Aand unusually high T_Add and T_Drop


Hard Handoff in Traffic Messaging (2)

QcpCdmaLogMsgForTrafChan 11/09/2002 00:07:56MSG_LENGTH: 11 octetsMSG_TYPE: Neighbor List Update MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: Yes ENCRYPTION: Encryption DisabledPILOT_INC: 6NGHBR_PN: 348 NGHBR_PN: 354 NGHBR_PN: 390NGHBR_PN: 408 RESERVED: 0

QcpCdmaLogMsgRevTrafChan 11/09/2002 00:07:56MSG_LENGTH: 7 octetsMSG_TYPE: Handoff Completion MessageACK_SEQ: 7 MSG_SEQ: 0 ACK_REQ: YesENCRYPTION: Encryption DisabledLAST_HDM_SEQ: 3 PILOT_PN: 360 RESERVED: 0

QcpCdmaLogMsgForTrafChan 11/09/2002 00:07:56MSG_LENGTH: 18 octetsMSG_TYPE: In-Traffic System Parameters MessageACK_SEQ: 0 MSG_SEQ: 1 ACK_REQ: YesENCRYPTION: Encryption DisabledSID: 1382 NID: 5SRCH_WIN_A: 60 chips SRCH_WIN_N: 130 chipsSRCH_WIN_R: 320 chipsT_ADD: -14.0 dB T_DROP: -16.0 dBT_COMP: 1.0 T_TDROP: 4 secNGHBR_MAX_AGE: 0 P_REV: IS-2000 Revision 0SOFT_SLOPE: 0 ADD_INTERCEPT: 0 dB DROP_INTERCEPT: 0 dBPACKET_ZONE_ID: Base Station Does Not Support A Packet Data

Service ZoneEXTENSION: No RESERVED: 0

After arrival on the new frequency and traffic channel, the mobile is given a new Neighbor List Update MessageThe mobile is also given new system parameters including more normal search windows and handoff parameters appropriate to the new environment of the mobile

The mobile acknowledges upon arrival on the new traffic channel by sending a Handoff Completion Message


Many Network/Carrier Configurations are Possible!

f1

f2

f3

f4

Basic Multi-CarrierOperation

IS-95

IS-95

IS-95

IS-95 f1

f2

f3

f4

Non-originating carrierscan carry more traffic!

IS-95

IS-95

IS-95

IS-95 f1

f2

f3

f4

Some Carriers maysupport 1xRTT

1xRTT

IS-95

IS-95

IS-95

w32

Sync

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

fic

W0

Pilo

t

w32

Sync

w1

Pagi

ngw

aTr

affic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

32Sy

nc

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

32Sy

nc

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

fic

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

aTr

affic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

aTr

affic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

fic

w32

Sync

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

cTr

affic

wc

Traf

ficw

cTr

affic

w32

Sync

wa

Dat

a

wx

Traf

ficw

yTr

affic

wz

Traf

fic

w32

Sync

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

fic

wa

Traf

fic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

aTr

affic

wx

Traf

ficw

yTr

affic

wz

Traf

fic

wb

Traf

ficw

cTr

affic

wc

Traf

fic

W0

Pilo

tw

1Pa

ging

W0

Pilo

tw

1Pa

ging

W0

Pilo

tw

1Pa

ging

W0

Pilo

tW

0 P

ilot

W0

Pilo

tW

0 P

ilot

w1

Pagi

ng

W0

Pilo

tW

0 P

ilot

W0

Pilo

tW

0 P

ilot

w1

Pagi

ngw

1Pa

ging

w32

Sync

w32

Sync

w32

Sync

w32

Sync

w32

Sync


CDMA/Analog Overlay ConsiderationsCDMA/Analog Overlay Considerations


CDMA/AMPS Overlays: Idle CDMA Acquisition

System acquisition is primarily controlled by the mobile• dual-mode mobiles look for CDMA first, then AMPS if needed

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

Most operators request handset manufacturers to add feature of periodic rechecking by idle handsets seeking to acquire CDMA

CDMA Overlay

AMPS Existing System

GSRM GSRM


CDMA/AMPS Overlays: Analog Handdown

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

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

Once a CDMA phone hands down to analog, it cannot be handed back up during the same call (due to long CDMA acquisition time)

CDMA Overlay

AMPS Existing System


1xRTT Data Introduction:Radio Configurations,

Variable Length Walsh Codes

1xRTT Data Introduction:Radio Configurations,

Variable Length Walsh Codes

RF200


The Original IS-95 CDMA Code Channels

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

FORWARD CHANNELS

BTS

W0: PILOT

W32: SYNC

W1: PAGING

Wn: TRAFFIC

REVERSE CHANNELS

ACCESS

TRAFFIC


1xRTT Code Channels, Rev. 0

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.

Includes PowerControl Subchannel

Enhanced Access Channel

CommonControl Channel

DedicatedControl Channel

Reverse FundamentalChannel (IS95B comp.)

Reverse Supplemental Channel

Access Channel(IS-95B compatible)

R-TRAFFIC

REVERSE CHANNELS

R-Pilot

R-CCCH

R-DCCH

R-FCH

R-SCH

R-EACH

1

1

0 or 1

0 or 1

0 to 2

R-ACH or

1

BTS

Dedicated Control Channel

Same coding as IS-95B,Backward compatible



Broadcast Channel

Quick Paging Channel

Common Power Control Channel

Common Assignment Channel

Common Control Channels

Forward Traffic Channels

Fundamental Channel

SupplementalChannels IS-95B only

SupplementalChannels RC3,4,5

F-TRAFFIC

FORWARD CHANNELS

F-Pilot

F-Sync

PAGING

F-BCH

F-QPCH

F-CPCCH

F-CACH

F-CCCH

F-DCCH

1

1

1 to 7

0 to 8

0 to 3

0 to 4

0 to 7

0 to 7

0 or 1

F-FCH

F-SCH

F-SCH

1

0 to 7

0 to 2

IS-95B only

Users:Users:0 to many0 to many

How manyPossible:

See Course 332 for more details.


Spreading Rates & Radio ConfigurationsRadio

Configuration

RC1

RC2

RC3

RC4

RC5

RC6

RC7

RC8

RC9

SpreadingRate

SR11xRTT1 carrier1.2288MCPS

SR33xRTT

Fwd:3 carriers

1.2288MCPSRev:

3.6864MCPS

Forward Link

Required. IS-95B CompatibleNo CDMA2000 coding features

Compatible with IS-95B RS2No CDMA2000 coding features

Quarter-rate convolutional or Turbo Coding, base rate 9600

Half-rate convolutional or Turbo Coding, base rate 9600

Quarter-rate convolutional or Turbo Coding, base rate 14400

1/6 rate convolutionalor Turbo coding, base rate 9600

Required. 1/3 rate convolutionalor Turbo coding, base rate 9600

¼ or 1/3 rate convolutional orTurbo coding, base rate 14400

½ or 1/3 rate convolutional or Turbo encoder, base rate 14400

DataRates

9600

14400

9600153600

9600307200

14400230400

9600307200

9600614400

14400460800

144001036800

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

Quarter rate convolutional or Turbo Coding, base rate 14400

Required. ¼ or 1/3 convolutionalor Turbo coding, base rate 9600

¼ or ½ convolutional or Turboencoding, base rate 14400

Required. IS-95B CompatibleNo CDMA2000 coding features

Compatible with IS-95B RS2No CDMA2000 coding features

RC1

RC2

RC3

RC4

RC5

RC6

9600

14400

9600

153600

307200

14400230400

9600

307200

614400

14400

460800

1036800

Reverse LinkDataRates

RadioConfiguration


SR1, RC1 9,600 bps F-FCH (IS-95-Compatible)

Same sym

bols go on both I and Q!

PowerControl

Puncturing

Data Bits

8.6 kbps

+CRC &Tail bits

9.6 kbps

1/2 rateConv Encoder Interleaver

User Long Code Mask

Long CodeGenerator

Long CodeDecimator

Power CtrlDecimator

PCPunc

Pwr CtrlBits

GainGain

19.2 ksps

I Short Code

QShort Code

FIRLPF

FIRLPF

II

QQ

OrthogonalSpreading

1228.8 kbps /W

800 bps

800 bps

19.2 ksps

1228.8 kcps

1228.8 kcps

SymbolRepetition Σ

ΣBTS Walsh 64Generator

1228.8 kcps


SR1, RC2 14,400 bps F-FCH (IS-95-Compatible)

Same sym

bols go on both I and Q!

PowerControl

Puncturing

Data Bits

13.35 kbps

+CRC &Tail bits

14.4 kbps


User Long Code Mask

Long CodeGenerator

Long CodeDecimator

Power CtrlDecimator

PCPunc

Pwr CtrlBits

GainGain

19.2 ksps

I Short Code

QShort Code

FIRLPF

FIRLPF

II

QQ

OrthogonalSpreading

1228.8 kbps /W

800 bps

800 bps

19.2 ksps

1228.8 kcps

1228.8 kcps

SymbolRepetition

SymbolPuncturing

28.8 ksps

2 of 6

Σ

ΣBTS Walsh 64Generator

1228.8 kcps


SR1, RC3 F-FCH (9,600 bps)

The stream of symbols is divided into two parts: one on logical I and one on logical Q

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.

PowerControl

PuncturingFull RateData Bits8.6 kbps

+CRC &Tail bits

9.6 kbps


User Long Code Mask

Long CodeGenerator

Long CodeDecimator

Power CtrlDecimator

PCPunc

Pwr CtrlBits

GainGain

Serial toParallel

Walsh 64Generator

I

Q

38.4 ksps

I Short Code

QShort Code

FIRLPF

FIRLPF

I

II

Q QQ

OrthogonalSpreading

ComplexScrambling

+

-

+

+Power control informationmay be carried as shown

or on the F-DCCH

1228.8 kbps /W/2

800 bps

800 bps

19.2 ksps

19.2 ksps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

38.4 ksps

Σ

ΣBTS

Doubled power efficiency, but still only 64 walsh codes


SR1, RC4 F-FCH (9,600 bps)






PowerControl

PuncturingFull RateData Bits8.6 kbps

+CRC &Tail bits

9.6 kbps


User Long Code Mask

Long CodeGenerator

Long CodeDecimator

Power CtrlDecimator

PCPunc

Pwr CtrlBits

GainGain

Serial toParallel

Walsh 128Generator

I

Q

19.2 ksps

I Short Code

QShort Code

FIRLPF

FIRLPF

I

II

Q QQ

OrthogonalSpreading

ComplexScrambling

+

-

+

+Power control informationmay be carried as shown

or on the F-DCCH

1228.8 kbps /W/2

800 bps

800 bps

9.6 ksps

9.6 ksps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

19.2 ksps

Σ

ΣBTS

Double the walsh codes, but no better power efficiency.


SR1, RC3 F-SCH (153,600 bps)






PayloadData Bits

152.4 kbps

+CRC &Tail bits

153.6 kbps


User Long Code Mask

Long CodeGenerator

Long CodeDecimator

GainSerial toParallel

Walsh 4Generator

I

Q

614.4 kspsI

Short Code

QShort Code

FIRLPF

FIRLPF

I

II

Q QQ

OrthogonalSpreading

ComplexScrambling

+

-

+

+

1228.8 kbps /W/2

307.2 ksps

307.2 ksps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

614.4 ksps

614.4 ksps

Σ

ΣBTS


SR1, RC4 F-SCH (307,200 bps)






PayloadData Bits

304.8 kbps

+CRC &Tail bits

307.2 kbps


User Long Code Mask

Long CodeGenerator

Long CodeDecimator

GainSerial toParallel

Walsh 4Generator

I

Q

614.4 kspsI

Short Code

QShort Code

FIRLPF

FIRLPF

I

II

Q QQ

OrthogonalSpreading

ComplexScrambling

+

-

+

+

1228.8 kbps /W/2

307.2 ksps

307.2 ksps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

1228.8 kcps

614.4 ksps

614.4 ksps

Σ

ΣBTS


The Famous Walsh Codes from IS-95 Days

64 “Magic” Sequences, each 64 chips longEach Walsh Code is precisely Orthogonal with respect to all other Walsh Codes and their opposites too!

• it’s simple to generate the codes, or• they’re small enough to use from ROM

WALSH CODES# ---------------------------------- 64-Chip Sequence ------------------------------------------0 00000000000000000000000000000000000000000000000000000000000000001 01010101010101010101010101010101010101010101010101010101010101012 00110011001100110011001100110011001100110011001100110011001100113 01100110011001100110011001100110011001100110011001100110011001104 00001111000011110000111100001111000011110000111100001111000011115 01011010010110100101101001011010010110100101101001011010010110106 00111100001111000011110000111100001111000011110000111100001111007 01101001011010010110100101101001011010010110100101101001011010018 00000000111111110000000011111111000000001111111100000000111111119 0101010110101010010101011010101001010101101010100101010110101010

10 001100111100110000110011110011000011001111001100001100111100110011 011001101001100101100110100110010110011010011001011001101001100112 000011111111000000001111111100000000111111110000000011111111000013 010110101010010101011010101001010101101010100101010110101010010114 001111001100001100111100110000110011110011000011001111001100001115 011010011001011001101001100101100110100110010110011010011001011016 000000000000000011111111111111110000000000000000111111111111111117 010101010101010110101010101010100101010101010101101010101010101018 001100110011001111001100110011000011001100110011110011001100110019 011001100110011010011001100110010110011001100110100110011001100120 000011110000111111110000111100000000111100001111111100001111000021 010110100101101010100101101001010101101001011010101001011010010122 001111000011110011000011110000110011110000111100110000111100001123 011010010110100110010110100101100110100101101001100101101001011024 000000001111111111111111000000000000000011111111111111110000000025 010101011010101010101010010101010101010110101010101010100101010126 001100111100110011001100001100110011001111001100110011000011001127 011001101001100110011001011001100110011010011001100110010110011028 000011111111000011110000000011110000111111110000111100000000111129 010110101010010110100101010110100101101010100101101001010101101030 001111001100001111000011001111000011110011000011110000110011110031 011010011001011010010110011010010110100110010110100101100110100132 000000000000000000000000000000001111111111111111111111111111111133 010101010101010101010101010101011010101010101010101010101010101034 001100110011001100110011001100111100110011001100110011001100110035 011001100110011001100110011001101001100110011001100110011001100136 000011110000111100001111000011111111000011110000111100001111000037 010110100101101001011010010110101010010110100101101001011010010138 001111000011110000111100001111001100001111000011110000111100001139 011010010110100101101001011010011001011010010110100101101001011040 000000001111111100000000111111111111111100000000111111110000000041 010101011010101001010101101010101010101001010101101010100101010142 001100111100110000110011110011001100110000110011110011000011001143 011001101001100101100110100110011001100101100110100110010110011044 000011111111000000001111111100001111000000001111111100000000111145 010110101010010101011010101001011010010101011010101001010101101046 001111001100001100111100110000111100001100111100110000110011110047 011010011001011001101001100101101001011001101001100101100110100148 000000000000000011111111111111111111111111111111000000000000000049 010101010101010110101010101010101010101010101010010101010101010150 001100110011001111001100110011001100110011001100001100110011001151 011001100110011010011001100110011001100110011001011001100110011052 000011110000111111110000111100001111000011110000000011110000111153 010110100101101010100101101001011010010110100101010110100101101054 001111000011110011000011110000111100001111000011001111000011110055 011010010110100110010110100101101001011010010110011010010110100156 000000001111111111111111000000001111111100000000000000001111111157 010101011010101010101010010101011010101001010101010101011010101058 001100111100110011001100001100111100110000110011001100111100110059 011001101001100110011001011001101001100101100110011001101001100160 000011111111000011110000000011111111000000001111000011111111000061 010110101010010110100101010110101010010101011010010110101010010162 001111001100001111000011001111001100001100111100001111001100001163 0110100110010110100101100110100110010110011010010110100110010110

EXAMPLE:Correlation of Walsh Code #23 with Walsh Code #59

#23 0110100101101001100101101001011001101001011010011001011010010110#59 0110011010011001100110010110011010011001011001100110011010011001Sum 0000111111110000000011111111000011110000000011111111000000001111

Correlation Results: 32 1’s, 32 0’s: Orthogonal!!

Unique Properties:Mutual Orthogonality


IS-95 Busy SectorSnapshot of Walsh Usage


Walsh Codes in 1xRTT

Data Rates are different, butChip Rates must stay the same!

2G VOICE AND DATAOne Symbol of Information

64 chips of Walsh Code1,228,800 walsh chips/second

19,200 symbols/secondDATA

SYMBOLS

WALSHCODE

3G 153.6 kb/s DATA One Symbol of Fast Data

4 Chips of Walsh Code 1,228,800 walsh chips/second

307,200 symbols/secondDATA

SYMBOLS

WALSHCODE


Families of the Walsh Codes

All Walsh codes can be built to any size from a single zero by replicating and invertingAll Walsh matrixes are square -- same number of codes and number of chips per code


10 001100111100110000110011110011000011001111001100001100111100110011 011001101001100101100110100110010110011010011001011001101001100112 000011111111000000001111111100000000111111110000000011111111000013 010110101010010101011010101001010101101010100101010110101010010114 001111001100001100111100110000110011110011000011001111001100001115 011010011001011001101001100101100110100110010110011010011001011016 000000000000000011111111111111110000000000000000111111111111111117 010101010101010110101010101010100101010101010101101010101010101018 001100110011001111001100110011000011001100110011110011001100110019 011001100110011010011001100110010110011001100110100110011001100120 000011110000111111110000111100000000111100001111111100001111000021 010110100101101010100101101001010101101001011010101001011010010122 001111000011110011000011110000110011110000111100110000111100001123 011010010110100110010110100101100110100101101001100101101001011024 000000001111111111111111000000000000000011111111111111110000000025 010101011010101010101010010101010101010110101010101010100101010126 001100111100110011001100001100110011001111001100110011000011001127 011001101001100110011001011001100110011010011001100110010110011028 000011111111000011110000000011110000111111110000111100000000111129 010110101010010110100101010110100101101010100101101001010101101030 001111001100001111000011001111000011110011000011110000110011110031 011010011001011010010110011010010110100110010110100101100110100132 000000000000000000000000000000001111111111111111111111111111111133 010101010101010101010101010101011010101010101010101010101010101034 001100110011001100110011001100111100110011001100110011001100110035 011001100110011001100110011001101001100110011001100110011001100136 000011110000111100001111000011111111000011110000111100001111000037 010110100101101001011010010110101010010110100101101001011010010138 001111000011110000111100001111001100001111000011110000111100001139 011010010110100101101001011010011001011010010110100101101001011040 000000001111111100000000111111111111111100000000111111110000000041 010101011010101001010101101010101010101001010101101010100101010142 001100111100110000110011110011001100110000110011110011000011001143 011001101001100101100110100110011001100101100110100110010110011044 000011111111000000001111111100001111000000001111111100000000111145 010110101010010101011010101001011010010101011010101001010101101046 001111001100001100111100110000111100001100111100110000110011110047 011010011001011001101001100101101001011001101001100101100110100148 000000000000000011111111111111111111111111111111000000000000000049 010101010101010110101010101010101010101010101010010101010101010150 001100110011001111001100110011001100110011001100001100110011001151 011001100110011010011001100110011001100110011001011001100110011052 000011110000111111110000111100001111000011110000000011110000111153 010110100101101010100101101001011010010110100101010110100101101054 001111000011110011000011110000111100001111000011001111000011110055 011010010110100110010110100101101001011010010110011010010110100156 000000001111111111111111000000001111111100000000000000001111111157 010101011010101010101010010101011010101001010101010101011010101058 001100111100110011001100001100111100110000110011001100111100110059 011001101001100110011001011001101001100101100110011001101001100160 000011111111000011110000000011111111000000001111000011111111000061 010110101010010110100101010110101010010101011010010110101010010162 001111001100001111000011001111001100001100111100001111001100001163 0110100110010110100101100110100110010110011010010110100110010110

WALSH CODES# ----------- 32-Chip Sequence -------------0 000000000000000000000000000000001 010101010101010101010101010101012 001100110011001100110011001100113 011001100110011001100110011001104 000011110000111100001111000011115 010110100101101001011010010110106 001111000011110000111100001111007 011010010110100101101001011010018 000000001111111100000000111111119 01010101101010100101010110101010

10 0011001111001100001100111100110011 0110011010011001011001101001100112 0000111111110000000011111111000013 0101101010100101010110101010010114 0011110011000011001111001100001115 0110100110010110011010011001011016 0000000000000000111111111111111117 0101010101010101101010101010101018 0011001100110011110011001100110019 0110011001100110100110011001100120 0000111100001111111100001111000021 0101101001011010101001011010010122 0011110000111100110000111100001123 0110100101101001100101101001011024 0000000011111111111111110000000025 0101010110101010101010100101010126 0011001111001100110011000011001127 0110011010011001100110010110011028 0000111111110000111100000000111129 0101101010100101101001010101101030 0011110011000011110000110011110031 01101001100101101001011001101001

WALSH# ---- 16-Chips -------0 00000000000000001 01010101010101012 00110011001100113 01100110011001104 00001111000011115 01011010010110106 00111100001111007 01101001011010018 00000000111111119 0101010110101010

10 001100111100110011 011001101001100112 000011111111000013 010110101010010114 001111001100001115 0110100110010110

WALSH# 8-Chips 0 000000001 010101012 001100113 011001104 000011115 010110106 001111007 01101001

WALSH# 4-Chips 0 00001 01012 00113 0110

WALSH# 2-Chips 0 001 01

WALSH# 1-Chip0 0

64x64

32x32

16x16

8x84x42x2

Walsh Level MappingThe 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 Code NamesW1232 = “Walsh Code #12, 32 chips long.”


Walsh Code Trees and Interdependencies

Entire Walsh matrices can be built by replicating and inverting -- Individual Walsh codes can also be expanded in the same way.CDMA adds each symbol of information to one complete Walsh codeFaster symbol rates therefore require shorter Walsh codesIf 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 signalsTherefore, the supply of available Walsh codes on a sector diminishes greatly while a fast data channel is being transmitted!CDMA2000 Base stations can dip into a supply of quasi-orthogonal codes if needed to permit additional channels during times of heavy loading

0110

1001

0110

0110

0110

0110 0110 0110 0110

0110 0110 1001 1001

10010110 10010110

10010110 1001 011010010110 1001 0110 10010110 1001 0110

10010110 1001 0110 1001 0110 10010110

10010110 10010110

10010110 10010110

10010110 10010110

100101101001 0110

0110 0110 1001 1001

0110 0110 1001 1001 0110 0110 1001 1001

0110 01101001 1001

0110 0110 0110 0110 0110 0110 0110 0110

0110 0110 0110 0110 1001 1001 1001 1001

W34

W38

W78

W716

W1116

W316

W1516

W732

W2332

W1532

W3132

W2732

W1132

W1932

W332 W364

W3564

W1964

W5164

W1164

W4364

W2764

W5964

W764

W3964

W2364

W5564

W1564

W4764

W3164

W6364


Walsh Code Families and ExclusionsConsider a forward link supplemental channel being transmitted with a data 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

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

The BTS controller managing this sector must track the precluded walsh codes and ensure they aren’t assigned


10 001100111100110000110011110011000011001111001100001100111100110011 011001101001100101100110100110010110011010011001011001101001100112 000011111111000000001111111100000000111111110000000011111111000013 010110101010010101011010101001010101101010100101010110101010010114 001111001100001100111100110000110011110011000011001111001100001115 011010011001011001101001100101100110100110010110011010011001011016 000000000000000011111111111111110000000000000000111111111111111117 010101010101010110101010101010100101010101010101101010101010101018 001100110011001111001100110011000011001100110011110011001100110019 011001100110011010011001100110010110011001100110100110011001100120 000011110000111111110000111100000000111100001111111100001111000021 010110100101101010100101101001010101101001011010101001011010010122 001111000011110011000011110000110011110000111100110000111100001123 011010010110100110010110100101100110100101101001100101101001011024 000000001111111111111111000000000000000011111111111111110000000025 010101011010101010101010010101010101010110101010101010100101010126 001100111100110011001100001100110011001111001100110011000011001127 011001101001100110011001011001100110011010011001100110010110011028 000011111111000011110000000011110000111111110000111100000000111129 010110101010010110100101010110100101101010100101101001010101101030 001111001100001111000011001111000011110011000011110000110011110031 011010011001011010010110011010010110100110010110100101100110100132 000000000000000000000000000000001111111111111111111111111111111133 010101010101010101010101010101011010101010101010101010101010101034 001100110011001100110011001100111100110011001100110011001100110035 011001100110011001100110011001101001100110011001100110011001100136 000011110000111100001111000011111111000011110000111100001111000037 010110100101101001011010010110101010010110100101101001011010010138 001111000011110000111100001111001100001111000011110000111100001139 011010010110100101101001011010011001011010010110100101101001011040 000000001111111100000000111111111111111100000000111111110000000041 010101011010101001010101101010101010101001010101101010100101010142 001100111100110000110011110011001100110000110011110011000011001143 011001101001100101100110100110011001100101100110100110010110011044 000011111111000000001111111100001111000000001111111100000000111145 010110101010010101011010101001011010010101011010101001010101101046 001111001100001100111100110000111100001100111100110000110011110047 011010011001011001101001100101101001011001101001100101100110100148 000000000000000011111111111111111111111111111111000000000000000049 010101010101010110101010101010101010101010101010010101010101010150 001100110011001111001100110011001100110011001100001100110011001151 011001100110011010011001100110011001100110011001011001100110011052 000011110000111111110000111100001111000011110000000011110000111153 010110100101101010100101101001011010010110100101010110100101101054 001111000011110011000011110000111100001111000011001111000011110055 011010010110100110010110100101101001011010010110011010010110100156 000000001111111111111111000000001111111100000000000000001111111157 010101011010101010101010010101011010101001010101010101011010101058 001100111100110011001100001100111100110000110011001100111100110059 011001101001100110011001011001101001100101100110011001101001100160 000011111111000011110000000011111111000000001111000011111111000061 010110101010010110100101010110101010010101011010010110101010010162 001111001100001111000011001111001100001100111100001111001100001163 0110100110010110100101100110100110010110011010010110100110010110

0110W34

Which Walsh Codes get tied up by another?Wxxyyties up every YYth Walsh Code starting with #XX.


Forward Link Walsh Codes in 1xRTT

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

Paging 7

Paging 3

Paging 5

Paging

PCH

6

PCH

2

PCH

4

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k

76.8ksps

This way of arranging Walsh codes is called “bit reversal order”. It shows each Walsh code’s parents and children. Remember, we cannot use any Walsh code if

another Walsh code directly above it or below it is in use.


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.

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

19.2k19.2kS

yncPilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k ???????Traffic Channels

Voice or Data9.6k/14.4k

76.8ksps

38.4k


Mixed IS-95 / 1xRTT RC3 Voice Typical Usage: Pilot, Paging Sync, up to 61 Voice Users

FCHs of 1xRTT RC3 users consume less power, so more total users are possible than inIS-95. The BTS will probably have enough forward power to carry calls on all 61 walsh codes!

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

19.2k19.2kS

yncPilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k

F-FCHs mixedRC1,2,3 Voice

76.8ksps

??


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!

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k

F-SCH 153K RC3

F-FCHs 9.6kRC3 Data

F-FCHs 9.6kRC3 Voice


76.8kspsWasteful, since many of these users are

not actively sending or receiving data


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.

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k




F-FCH

sD

ata

F-SCH 153K RC3

76.8ksps


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.

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k




F-FCH

sD

ata

F-SCH 153K RC3

F-DC

CH

s76.8ksps


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!

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k



F-FCH

sD

ata

F-SCH 153K RC3

F-DC

CH

s

F-SCH 153K RC3

76.8ksps


1xRTT Busy SectorWalsh Code Usage


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.

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k




F-FCH

sD

ataF-SCH

76K RC3F-D

CC

Hs

F-SCH

38K

F-SCH

38K76.8ksps


1xRTT RC4 Voice Only:Pilot, Paging Sync, up to 118 Voice Users

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.

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k

F-FCHs 9.6k RC4 Voice



F-FCHs 9.6k RC4 Voice???????

76.8ksps


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!

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

Sync

Pilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k

F-SCH 307K RC4



F-FCHs 9.6k RC4 Voice????

F-FCH

sF-D

CC

Hs

76.8ksps


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 Users16 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!

9,6004,8002,400sps

307200sps

153,600sps

76,800sps

38,400sps

19,200sps

Code#

Code#

Code#

Code#

Code#

Code#

128 chips4 chips

8 chips16 chips

32 chips64 chips

Code#

Code#

Code#

Code#

Code#

Code#

73516240

3120

1571131359114610212480

311523727111932913215259171301422626101822812204248160

54

12763953111147791511955872310339717123599127107437511115518319993567312561932910945771311753852110137695121578925105417391134981189733651126629430110467814118862210238706122589026106427410114508218983466212460922810844761211652842010036684120568824104407281124880169632640

0 32 16 48 8 40 24 56 4 36 20 52 12 44 28 60 2 34 18 50 10 42 26 58 6 38 22 54 14 46 30 62 1 33 17 49 9 41 25 57 5 37 21 53 13 45 29 61 3 35 19 51 11 43 27 59 7 39 23 55 15 47 31 63

QPC

HQ

PCH

QPC

HTX

Div PIlot

19.2k

19.2k

19.2k

19.2k

Paging

19.2k

19.2k

19.2k

19.2k19.2kS

yncPilot

38.4k

38.4k38.4k

38.4k

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

76.8ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH153.6 ksps

F-SCH307.2 ksps

F-SCH307.2 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

19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k19.2k19.2k19.2k

19.2k19.2k19.2k19.2k

F-SCH 153K RC3or

F-SCH 307K RC4







F-FCH

sF-D

CC

Hs

Or Combinations

????

76.8ksps


1xRTT Data Operation1xRTT Data Operation


1xRTT Data Call States

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.1xRTT packet data traffic comes in many types, ranging from verybursty scattered packets to heavy almost-continuous data flows when large files are involvedIf 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 dataThe 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.


T_active orRelease

Current and Future 1xRTT Call States

Initialization

Null

Reconnect

Dormant

Control Hold(DCCH)

Suspended

Packet ServiceRequest

Packet ServiceDeactivated

PPP TerminatedRelease Sent!

PPP TerminatedRelease Sent!

Service OptionConnected

Control Channel Exists

Service OptionConnected

Control ChannelExists

Traffic channelExists

Active

T_hold

Control Channelexists

T_suspend

Have New Datato send!


MAC States Implemented in 1xRTT Phase 0State

R-ACH

F-TRAFFICF-FCH

F-SCH

R-TRAFFICR-FCH

R-SCHSCH driven

by trafficSCH driven

by trafficCESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs T TSECURE TUNNELSAuthentication

AuthorizationAccounting AAA

BTS

(C)BSC/Access Manager

SELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




BTS


PAGING

intermittent

ChannelElement

Selector/Svc Cfg (RLP) PPPIP

Session

ACTIVEexit timer:

a few seconds

DORMANTexit timer: minutes, hours

between data bursts

Dormanttimer

exceeded

ReleaseNormal Mobile has

data forSystem

Origination

System hasdata forMobile

GeneralPage

PageResponse


Future MAC States in 1xRTT Phase 1State

R-CCCH

R-EACH

F-TRAFFICF-FCH

F-SCH

R-TRAFFICR-FCH

R-SCHSCH driven

by trafficSCH driven

by traffic

F-TRAFFIC R-TRAFFIC

intermittent

F-DCCH R-DCCH

CESELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




BTS


CESELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




BTS


CESELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




BTS


SELt1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent




BTS


PAGING

R-CCCH

R-EACH

PAGING

intermittent

intermittent

ChannelElement

Selector/Svc Cfg (RLP) PPPIP

Session

ACTIVEexit timer:

a few seconds

CONTROLHOLD

(Optional State)exit timer: a few seconds

very fast return to active state

SUSPENDED(Optional State)

exit timer: a few secondsbetween data bursts

DORMANTexit timer: minutes, hours

between data bursts


Mobile-Originated Packet Data Call Flow

ACCESS CHANNEL


PAGING CHANNEL


ORIGINATION MESSAGE

EXTENDED CHANNEL ASSIGNMENT MSG



LAYER 2 HANDSHAKE

LAYER 2 HANDSHAKE

STATUS REQUESTMESSAGE

STATUS RESPONSEMESSAGE




Packet Session Origination Messaging (1)22:17:59.282 QcpCdmaLogMsgAccessChanMSG_LENGTH: 43 octets PD: P_REV_IN_USE >= 6MSG_ID: Origination Message LAC_LENGTH: 17 octetsACK_SEQ: 7 MSG_SEQ: 7 ACK_REQ: 1 VALID_ACK: 0 ACK_TYPE: 0MSID_TYPE: IMSI and ESN MSID_LEN: 9 octetsESN: D:25405233216 H:FE4FDA40 IMSI_CLASS: 0IMSI_CLASS_0_TYPE: IMSI_S included RESERVED: 0IMSI_S: 5402304897 AUTH_MODE: 1 AUTHU: 147354 RANDC: 120COUNT: 0 LAC_PADDING: 0 ACTIVE_PILOT_STRENGTH: -4.50 dBFIRST_IS_ACTIVE: Yes FIRST_IS_PTA: No NUM_ADD_PILOTS: 1PILOT_PN_PHASE: PN:216 + 0 chipsPILOT_STRENGTH: -14.50 dB ACCESS_HO_EN: NoACCESS_ATTEMPTED: No MOB_TERM: YesSLOT_CYCLE_INDEX: 2.56 MOB_P_REV: IS-2000 Revision 0SCM: Band Class 0, Dual Mode, Slotted, Continuous, Class IIIREQUEST_MODE: CDMA Only SPECIAL_SERVICE: YesSERVICE_OPTION: Standard: 144kbps PacketData, Internet or ISO ProtocolPM: Yes DIGIT_MODE: 4-bit DTMF Codes MORE_FIELDS: No NUM_FIELDS: 4CHARi: # 7 7 7 NAR_AN_CAP: NoPACA_REORIG: User Directed Origination RETURN_CAUSE: Normal AccessMORE_RECORDS: No ENCRYPTION_SUPPORTED: Basic Encryption SupportedPACA_SUPPORTED: No NUM_ALT_SO: 0 DRS: Yes UZID_INCL: NoCH_IND: Fundamental Channel SR_ID: 1 OTD_SUPPORTED: NoQPCH_SUPPORTED: Yes ENHANCED_RC: YesFOR_RC_PREF: 3 REV_RC_PREF: 3 FCH_SUPPORTED: YesFCH_FRAME_SIZE: Supports only 20 ms Frame SizesFOR_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: Yes RC6: NoREV_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: No RC6: NoDCCH_SUPPORTED: No GEO_LOC_INCL: No REV_FCH_GATING_REQ: Yes RESERVED: 0

22:17:59.551 Access Probe InfoAccess Probe Sequence Number: 1 Access Probe Number: 1 Access Channel Number: 0PN Randomization delay: 0 Sequence Backoff: 0 Probe Backoff: 0Persistence Tests Performed: 1 Rx Power: -77.9 Tx Power (Est): 4.9 Tx Gain Adjust: 0

The mobile sends an origination message on the Access ChannelThe Access Probe Information record shows the time when the message was sent and the power level


Packet Session Origination Messaging (2)22:17:59.782 QcpCdmaLogMsgPagingChanMSG_LENGTH: 13 octets PD: P_REV_IN_USE < 6 MSG_TYPE: Order MessageACK_SEQ: 7 MSG_SEQ: 0 ACK_REQ: No VALID_ACK: YesADDR_TYPE: ESN ADDR_LEN: 4 octets ESN: D:25405233216 H:FE4FDA40ORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

22:17:59.942 QcpCdmaLogMsgPagingChanMSG_LENGTH: 29 octets PD: P_REV_IN_USE < 6MSG_TYPE: Extended Channel Assignment MessageACK_SEQ: 7 MSG_SEQ: 1 ACK_REQ: No VALID_ACK: YesADDR_TYPE: ESN ADDR_LEN: 4 octets ESN: D:25405233216 H:FE4FDA40RESERVED_1: 0 ADD_RECORD_LEN: 15 octetsASSIGN_MODE: Extended Traffic Channel AssignmentRESERVED_2: 0 FREQ_INCL: Yes BAND_CLASS: 800 MHz Cellular BandCDMA_FREQ: 384 BYPASS_ALERT_ANSWER: YesGRANTED_MODE: MS use Service Configuration of default Multiplex Option and

Transmission RatesDEFAULT_CONFIG: Reserved FOR_RC: RC 3 REV_RC: RC 3FRAME_OFFSET: 7.50 ms ENCRYPT_MODE: Encryption DisabledFPC_SUBCHAN_GAIN: 0.0 dB RLGAIN_ADJ: 0 dB NUM_PILOTS: 0 PilotsCH_IND: Fundamental Channel CH_RECORD_LEN: 7 octetsFPC_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 dBPILOT_PN: 44 ADD_PILOT_REC_INCL: No PWR_COMB_IND: NoCODE_CHAN_FCH: 33 QOF_MASK_ID_FCH: 0 3X_FCH_INFO_INCL: NoREV_FCH_GATING_MODE: No 3XFL_1XRL_INCL: No RESERVED: 0

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

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


Packet Session Origination Messaging (3)

22:18:00.491 QcpCdmaLogMsgForTrafChanMSG_LENGTH: 8 octetsMSG_TYPE: Order MessageACK_SEQ: 7 MSG_SEQ: 0 ACK_REQ: YesENCRYPTION: Encryption DisabledUSE_TIME: No ACTION_TIME: 0 msORDER: Base Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0

22:18:00.509 QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 10 octetsMSG_TYPE: Pilot Strength Measurement MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: YesENCRYPTION: Encryption DisabledREF_PN: 44 PILOT_STRENGTH: -5.50 dB KEEP: YesPILOT_PN_PHASE: PN:216 + 0 chips PILOT_STRENGTH: -7.00 dB KEEP: YesRESERVED: 0




the forward channel, and concludes this is the right traffic channel. It starts sending good blank frames of its own on the

reverse traffic channel.


The mobile station acknowledges the base station’s 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 it’s time to negotiate the service option to be used.


Packet Session Origination Messaging (4)22:18:00.741 QcpCdmaLogMsgForTrafChanMSG_LENGTH: 9 octets MSG_TYPE: Status Request MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: NoENCRYPTION: Encryption Disabled QUAL_INFO_TYPE: NoneQUAL_INFO_LEN: 0 octets NUM_FIELDS: 2RECORD_TYPE: Channel ConfigurationCapability InformationRECORD_TYPE: Reserved

The system asks for the mobile’s Channel Configuration Capability Information

22:18:00.875 QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 44 octets MSG_TYPE: Status Response MessageACK_SEQ: 0 MSG_SEQ: 0 ACK_REQ: No ENCRYPTION: Encryption DisabledQUAL_INFO_TYPE: None QUAL_INFO_LEN: 0 octetsRECORD_TYPE: Extended Multiplex Option InformationRECORD_LEN: 24 octets NUM_MO_FOR_FCH: 2 MO_FOR_FCH: 1RS1_9600_FOR: RS1_4800_FOR: RS1_2400_FOR: RS1_1200_FOR: MO_FOR_FCH: 2RS2_14400_FOR: RS2_7200_FOR: RS2_3600_FOR: RS2_1800_FOR:RESERVED: 0 NUM_MO_REV_FCH: 2 MO_REV_FCH: 1RS1_9600_REV: RS1_4800_REV: RS1_2400_REV: RS1_1200_REV:RESERVED: 0 MO_REV_FCH: 2RS2_14400_REV: RS2_7200_REV: RS2_3600_REV: RS2_1800_REV:RESERVED: 0 NUM_MO_FOR_DCCH: 0 NUM_MO_REV_DCCH: 0NUM_MO_FOR_SCH: 2 FOR_SCH_ID: 0 MO_FOR_SCH: 2337FOR_SCH_ID: 0 MO_FOR_SCH: 2081 NUM_MO_REV_SCH: 2REV_SCH_ID: 0 MO_REV_SCH: 2321 REV_SCH_ID: 0 MO_REV_SCH: 2065RESERVED: 0RECORD_TYPE: Channel Configuration Capability InformationRECORD_LEN: 9 octets OTD_SUPPORTED: No FCH_SUPPORTED: YesFCH_FRAME_SIZE: Supports only 20 ms Frame SizesFOR_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: Yes RC6: NoREV_FCH_LEN: 2 RC1: Yes RC2: Yes RC3: Yes RC4: Yes RC5: No RC6: NoDCCH_SUPPORTED: No FOR_SCH_SUPPORTED: Yes FOR_SCH_LEN: 2RC1: No RC2: No RC3: Yes RC4: Yes RC5: No RC6: NoFOR_SCH_NUM: 1 FOR_TURBO_SUPPORTED: NoFOR_CONV_SUPPORTED: YesFOR_MAX_CONV_BLOCK_SIZE: Rate Set 1: 3048, Rate Set 2: 4584FOR_FRAME_40_SUPPORTED: No FOR_FRAME_80_SUPPORTED: NoFOR_MAX_RATE: 9.6 kbps or 14.4 kbps REV_SCH_SUPPORTED: YesREV_SCH_LEN: 1 RC1: No RC2: No RC3: Yes REV_SCH_NUM: 1REV_TURBO_SUPPORTED: No REV_CONV_SUPPORTED: YesREV_MAX_CONV_BLOCK_SIZE: Rate Set 1: 3048, Rate Set 2: 4584REV_FRAME_40_SUPPORTED: No REV_FRAME_80_SUPPORTED: NoREV_MAX_RATE: 9.6 kbps or 14.4 kbps STS_SUPPORTED: No3X_CCH_SUPPORTED: No RESERVED: 0 RESERVED: 0


Packet Session Origination Messaging (5)

22:18:01.118 QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 6 octetsMSG_TYPE: Service Connect Completion MessageACK_SEQ: 1 MSG_SEQ: 2 ACK_REQ: YesENCRYPTION: Encryption Disabled RESERVED: 0SERV_CON_SEQ: 0 RESERVED: 0

The system proposes the service connection parameters and the mobile accepts

22:18:01.089 QcpCdmaLogMsgForTrafChanMSG_LENGTH: 46 octets MSG_TYPE: Service Connect MessageACK_SEQ: 0 MSG_SEQ: 1 ACK_REQ: NoENCRYPTION: Encryption Disabled USE_TIME: No ACTION_TIME: 0 ms SERV_CON_SEQ: 0RESERVED: 0 RECORD_TYPE: Service ConfigurationRECORD_LEN: 30 octets FOR_MUX_OPTION: 1 REV_MUX_OPTION: 1RS1_9600_FOR: RS1_4800_FOR: RS1_2400_FOR: RS1_1200_FOR:RESERVED: 0RS1_9600_REV: RS1_4800_REV: RS1_2400_REV: RS1_1200_REV:RESERVED: 0NUM_CON_REC: 1 RECORD_LEN: 12 octets CON_REF: 1SERVICE_OPTION: Standard: 144kbps PacketData, Internet or ISO ProtocolFOR_TRAFFIC: SO Uses Primary Traffic On FTCREV_TRAFFIC: SO Uses Primary Traffic On RTCRESERVED: -- -- 6 65 193 178 153 76 0 134 53 2 72 72RESERVED: 96 40 18 34 67 0 19 5 132 67 7 10 0


Session Transition to Dormant State


PAGING CHANNEL

RELEASE -- NORMAL

RELEASE – NO REASON

SYNC CHANNEL


NORMAL OPERATION CONTINUES,BUT NO DATA HAS BEEN SENT

IN EITHER DIRECTIONDURING THE DORMANT TIMER PERIOD

THE MOBILE READS THE CONFIGURATION MESSAGES. THE SYSTEM IS UNCHANGED,

SO NO NEW REGISTRATION IS NEEDED.


Session Return from Dormant StateDue to Data at System

ACCESS CHANNEL

REVERSE FUNDAMENTALTRAFFIC CHANNEL

FORWARD FUNDAMENTALTRAFFIC CHANNEL

PAGING CHANNEL

PROBE INFORMATION

GENERAL PAGE MESSAGE

PAGE RESPONSE MESSAGE


LAYER 2 HANDSHAKE

LAYER 2 HANDSHAKE








THE DATA CALL IS BACK IN ACTIVE STATE.NORMAL MESSAGING AND DATA TRANSFER

CONTINUE.


Session Return from Dormant StateDue to Data at Mobile

ACCESS CHANNELPAGING CHANNEL

PROBE INFORMATION


ORIGINATION MESSAGE


REVERSE FUNDAMENTAL CHANNEL

FORWARD FUNDAMENTAL CHANNEL

LAYER 2 HANDSHAKE

LAYER 2 HANDSHAKEBASE STATIONACK. ORDER






THE DATA CALL IS BACK IN ACTIVE STATE.NORMAL MESSAGING AND DATA TRANSFER

CONTINUE.


Forward Link SCH Scheduling

The main bottleneck is the forward link itself: restricted by available transmitter power and walsh codesEach 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

CESELt1

R-PInterface

PDSN/Foreign Agent

BTS

(C)BSC/Access ManagerWireless

Mobile Device

data

FCH orFCH + SCH?

Buffer

BTSC

My F-SCHData Rate

PCF


Forward Link Supplemental Channel Burst

REVERSE FUNDAMENTAL TRAFFIC CHANNEL

FORWARD FUNDAMENTAL TRAFFIC CHANNEL

EXTENDED SUPPL. CHAN.ASSIGNMENT MSG.


FORWARD SUPPLEMENTAL

CHANNELDATA BURST


Forward Supplemental Channel Assignment

BTS

W1

W32

W0

W23

PAGING

SYNC

PILOT

F-FCH

ACCESS CHANNEL

R-FCH


GK KS P C GP K KSAGK KSAK NNKG K SGP SA GK KS P C GP K KSAGK KSAK NNKG K SGP SA GK KS P CP KGK KSAK NNKG K SGP SA

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

ESCAM

PN 168

TIME

W2 F-SCH SupplementalChannel Burst

ESCAM

SupplementalChannel Burst

Mobile: Watch Walsh Code 2

Starting in 320 ms For 1000 ms.

Mobile: Watch Walsh Code 2



Forward Link Supplemental Channel Burst Messaging

22:39:41.508 QcpCdmaLogMsgForTrafChanMSG_LENGTH: 20 octetsMSG_TYPE: Extended Supplemental Channel

Assignment MessageACK_SEQ: 7 MSG_SEQ: 0 ACK_REQ: NoENCRYPTION: Encryption DisabledSTART_TIME_UNIT: 0 ms REV_SCH_DTX_DURATION: 200 msUSE_T_ADD_ABORT: No USE_SCRM_SEQ_NUM: NoADD_INFO_INCL: YesFPC_PRI_CHAN: Forward Fundamental Channel inner loop

estimationREV_CFG_INCLUDED: No NUM_REV_SCH: 0FOR_CFG_INCLUDED: Yes FOR_SCH_FER_REP: YesNUM_FOR_CFG_RECS: 0 FOR_SCH_ID: 0 SCCL_INDEX: 0FOR_SCH_NUM_BITS_IDX: RC 1,3,4,6,7=744; RC 2,5,8,9=1128;

12 CRC bitsNUM_SUP_SHO: 0 PILOT_PN: 12ADD_PILOT_REC_INCL: No CODE_CHAN_SCH: 2QOF_MASK_ID_SCH: 0 (rot 256 bit)NUM_FOR_SCH: 1 FOR_SCH_ID: 0FOR_SCH_DURATION: 2560 msFOR_SCH_START_TIME_INCL: YesFOR_SCH_START_TIME: 28 SCCL_INDEX: 0FPC_INCL: Yes FPC_MODE_SCH: 1FPC_SCH_INIT_SETPT_OP: FPC_SCH_INIT_SETPT has Offset

value of initial F-SCH Eb/Nt setpointFPC_SEC_CHAN: 0 NUM_SUP: 1 SCH_ID: 0FPC_SCH_FER: 0.5% - 10% (in units of 0.5%)FPC_SCH_INIT_SETPT: 3.500 dBFPC_SCH_MIN_SETPT: 2.000 dBFPC_SCH_MAX_SETPT: 8.000 dBFPC_THRESH_SCH_INCL: No RPC_INCL: No3X_SCH_INFO_INCL: No CCSH_INCLUDED: NoFOR_SCH_CC_INCL: No REV_SCH_CC_INCL: NoRESERVED: 0

22:39:42.250, Record 224546, QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 7 octetsMSG_TYPE: Order MessageACK_SEQ: 0 MSG_SEQ: 2 ACK_REQ: NoENCRYPTION: Encryption DisabledORDER: Mobile Station Acknowledgement OrderADD_RECORD_LEN: 0 octets RESERVED: 0


Reverse Link Supplemental Channel Burst

REVERSE FUNDAMENTAL TRAFFIC CHANNEL

FORWARD FUNDAMENTAL TRAFFIC CHANNEL

EXTENDED SUPPL. CHAN.ASSIGNMENT MSG.


REVERSE SUPPLEMENTAL

CHANNELDATA BURST

EXTENDED SUPPL. CHAN.REQUEST MSG.


Reverse Supplemental Channel Assignment

BTS

W1

W32

W0

W23

PAGING

SYNC

PILOT

F-FCH

ACCESS CHANNEL

R-FCH


GK KS P C GP K KSAGK KSAK NNKG K SGP SA GK KS P C GP K KSAGK KSAK NNKG K SGP SA GK KS P CP KGK KSAK NNKG K SGP SA

SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

ESCAM

PN 168

TIME

R-SCH SupplementalChannel Burst

ESCAM

SupplementalChannel Burst

SCRM SCRM

Mobile: Send Walsh Code 1


Mobile: Send Walsh Code 1


System: I need toSend you the

Following blocks:

System: I need toSend you the

Following blocks:


Reverse Link Supplemental Channel Burst Messaging

22:31:47.229 QcpCdmaLogMsgForTrafChanMSG_LENGTH: 12 octetsMSG_TYPE: Extended Supplemental Channel

Assignment MessageACK_SEQ: 7 MSG_SEQ: 4 ACK_REQ: NoENCRYPTION: Encryption DisabledSTART_TIME_UNIT: 0 msREV_SCH_DTX_DURATION: 200 msUSE_T_ADD_ABORT: No USE_SCRM_SEQ_NUM: NoADD_INFO_INCL: YesFPC_PRI_CHAN: Forward Fundamental Channel inner

loop estimationREV_CFG_INCLUDED: Yes NUM_REV_CFG_RECS: 0REV_SCH_ID: 0REV_WALSH_ID: Forward Dedicated Control Channel

inner loop estimationREV_SCH_NUM_BITS_IDX: RC 1,3,5=1512; RC 2,4,6=2280;

12 CRC bitsNUM_REV_SCH: 1 REV_SCH_ID: 0REV_SCH_DURATION: ReservedREV_SCH_START_TIME_INCL: YesREV_SCH_START_TIME: 30REV_SCH_NUM_BITS_IDX: RC 1,3,5=1512; RC 2,4,6=2280;

12 CRC bitsFOR_CFG_INCLUDED: No NUM_FOR_SCH: 0FPC_INCL: No RPC_INCL: YesRPC_NUM_SUP: 0 SCH_ID: 0RLGAIN_SCH_PILOT: 1.000000 dB3X_SCH_INFO_INCL: NoCCSH_INCLUDED: NoFOR_SCH_CC_INCL: error: 1 bit field, 0 bits availableREV_SCH_CC_INCL: error: no bits available

22:31:47.102 QcpCdmaLogMsgRevTrafChanMSG_LENGTH: 17 octetsMSG_TYPE: Supplemental Channel Request MessageACK_SEQ: 7 MSG_SEQ: 4 ACK_REQ: NoENCRYPTION: Encryption DisabledSIZE_OF_REQ_BLOB: 3 bytesREQ_BLOB: 228REQ_BLOB: 39REQ_BLOB: 255USE_SCRM_SEQ_NUM: NoREF_PN: 132 PILOT_STRENGTH: -3.00 dB NUM_ACT_PN: 2ACT_PN_PHASE: PN:304 + 0 chips ACT_PILOT_STRENGTH: -14.50 dBACT_PN_PHASE: PN:372 + 22 chips ACT_PILOT_STRENGTH: -21.00 dBNUM_NGHBR_PN: 0REF_PILOT_REC_INCL: No PILOT_REC_INCL: No PILOT_REC_INCL: No


Protocol Stack and Connection Setup Scenarios

After setup of the basic traffic channels for a mobile session, the appropriate TCP-IP connections must be establishedThe following figures show the protocol stack from the perspective of the 1xRTT system, as well as from a more general TCP-IP view.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 system’s Foreign Agent PDSN can set up a new tunneling relationship with the Home Agent PDSN to continue the session.


Simple IP and Mobile IP 1x Networks

In Simple IP, a single PDSN manages the user’s connection to the outside IP/VPN worldIn 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 themobile’s current system.

• The FA PDSN establishes a “tunnel” with the HA PDSN for forwarding the mobile’s packets

If the mobile hands into a different system, the new system’s FA PDSN will establish its own tunnel to the HA PDSN, allowing the mobile’s session to continue.

Simple IP Network View

t1t1v CESEL

t1

R-P

PDSN

AAA BSC

USER

BTS

SW

IP/VPN

PSTN

Mobile IP Network View

t1t1v CESEL

t1

R-P

PDSNFA

PDSN HA AAA BSC

USER

BTS

SW

IP/VPN

PSTN

Backbone


1xRTT Wireless Data Protocol Stack

Protocol Stack View

APP

LLA

CPL

ICF

PLD

CF

PLD

CF

MU

X/Q

OS

SYSTEM

Inst 3L3 Sig

SRBP SRLP RBP RLP

PLDCF MUX / QoS

Physical - RLAC

Inst 2User Pkts

Inst 1Voc Bits

IS95L2Sig

1xL2Sig

OtherL2Sig

PktDataL2

NullL2

CktDataL2

IS95L3Sig

1xL3Sig

OtherL3Sig

PktDataSvc

VoiceSvc

CktDataSvc

Frames

MOBILE

Inst 3L3 Sig

SRBP SRLP RBP RLP

PLDCF MUX / QoS

Physical - RLAC

Inst 2User Pkts

Inst 1Voc Bits

IS95L2Sig

1xL2Sig

OtherL2Sig

PktDataL2

NullL2

CktDataL2

IS95L3Sig

1xL3Sig

OtherL3Sig

PktDataSvc

VoiceSvc

CktDataSvc


Simple IP Protocol Stack

Appli-cation

CDMAPL

MAC

LAC

PL

R-P

CDMAUpper Layers

HLProtocols

HTTPTCPUDP

IP

PPP

LAC

MAC

CDMAPL PL PL

R-P

PPP

IP

LinkLayer

PL

LinkLayer

IP

TCPUDP

HLProtocols

HTTP

Appli-cations

MobileStation RAN

PDSN HA

Logical (software) connections established

End Host(Internet,intranet)

AN AN

User Data: application/bearer and control

Gat

eway

Rou

ters


Mobile IP Protocol Stack – Application Data

Appli-cations

ULProtocols

(HTTP)TCPUDP

IP

PPP

LAC

MAC

CDMAPL

CDMAPL

MAC

LACR-P

PL

IP

PPP

R-P

PL

LinkLayer

PL

CDMA U.L.

IP

LinkLayer

LinkLayer

PL PL

Appli-cations

ULProtocols

(HTTP)

TCPUDP

IP

LinkLayer

PL

MobileStation RAN

PDSN HA

Logical conn. Mobile--RAN

End Host(Internet,intranet)

Gat

eway

Rou

ters

Gat

eway

Rou

ters

AN

AN

Logical connections Mobile—PDSN for PPP

Logical connections Mobile—End Host

Mobile IP User Application Data


Mobile IP Protocol Stack – Control Signalling

CDMAPL

MAC

LAC

PL

R-P

MobileIP

UDP

IP

PPP

LAC

MAC

CDMAPL PL PL

R-P

PPP

Mobile IP

LinkLayer

PL

LinkLayer

IP

UDP

MobileIP

UDP

IP

MobileStation RAN PDSN HA

Mobile IP control signalling


Simple IP Setup (PAP Authentication) (1)

The mobile sends an LCP Configure Request message to the PDSN. This starts setup of the data–link layer connection between mobile and PDSN.The PDSN sends an LCP Configure Request – PAP authentication seeking the mobile’s data–link layer and authentication information.The mobile sends an LCP Configure Acknowledgement – PAP authentication message to the PDSN, containing configuration information the PDSN uses to set up the connection.The PDSN sends an LCP Configure Acknowledgement – PAP authentication to the mobile, acknowledging it received the message.The Mobile-PDSN data–link layer connection is now configured; now set up the network–layer connection.Mobile requests AAA authentication from the PDSN, sending a PAP Authentication Request message.The PDSN receives the message and sends an Access Request message to the Foreign AAA server, including the mobile subscriber’s MSID@domain (also called an NAI) and Password to the AAA.The Foreign AAA server sends an Access Accept message to the PDSN, providing a dynamic IP address assignment for the mobile.


Simple IP Setup (PAP Authentication) (2)

The PDSN receives the Access Accept message and sends a PAP authentication Acknowledgement to the mobile.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)The PDSN assigns an dynamic IP address to the mobile by sending an IPCP Configure Nak message.The mobile receives the IPCP Configure Nak message sends an IPCP Configure request message to the PDSN, accepting the IP address.The PDSN associates the MAC address of the PDSN with the mobile’s assigned IP address.The PDSN sends an IPCP Configure Acknowledgement message to the mobile. This message indicates that the network–layer connection is complete.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 ahome or broker AAA.

• The mobile and PDSN can start exchanging packets.


Simple IP Setup – CHAP Authentication (1)

The mobile sends an LCP Configure Request message to the PDSN to initiate setup of the data–link layer connection between the mobile and the PDSN.The PDSN requests the mobile’s data–link layer and authentication information by sending an LCP Configure Request – CHAP authentication.Mobile replies by sending an LCP Configure Acknowledgement – CHAP authentication message to PDSN, containing configuration information PDSN uses to set up the connection.The PDSN sends an LCP Configure Ack – CHAP authentication to the mobile to acknowledge receiving the response. The mobile-PDSN data–link layer connection is configured; set up the network–layer connection.The PDSN sends a CHAP challenge to the mobile, containing a challenge value used for authentication.The mobile sends a CHAP response to the PDSN with:

• Username=MSID@domain (MSID= mobile station’s ID)• CHAP response value• CHAP ID

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


Simple IP Setup – CHAP Authentication (2)

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.The Foreign AAA server sends an Access Accept message to the PDSN, providing a dynamic IP address assignment for the mobile.The PDSN receives the Access Accept message and sends a CHAP Success message to the mobile indicating that it was authenticated.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).The PDSN sends an IPCP Configure Nak message to the mobile, containing the dynamic IP address assignment for the mobile (from the Foreign AAA).The mobile sends an IPCP Configure request message to the PDSN, indicating that the mobile’s IP address is now assigned/accepted.The PDSN now associates the MAC address of the PDSN with the mobile’s assigned IP address.The PDSN sends an IPCP Configure Acknowledgement message to the mobile. The network–layer configuration is complete.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.


Mobile IP Setup (1)

The mobile sends an LCP Configure Request message to the PDSN, initiating setup of the data–link layer connection between the mobile and the PDSN.The PDSN sends an LCP Configure Acknowledgment – No Authentication message to the PDSN. “No authentication” means the PDSN won’t authenticate the mobile during PPP setup.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 IP–Address 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 IP–Address Configuration option during the IPCP phase of the PPP negotiations.The PPP session is established between the mobile and PDSN.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 mobile’s HA located in its home network which may be a home ISP, a private network, a home access provider network, etc.The PDSN sends a Mobile IP based Agent Advertisement message with a “Foreign Agent Challenge” to authenticate the mobile.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 mobile’s 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.


Mobile IP Setup (2)The PDSN sends an Access Request to the Foreign AAA. The message contains the Foreign Agent Challenge Response authentication information.The Foreign AAA accepts or denies the Access Request using services of a home or broker AAA server.The Foreign AAA server sends an Access Accept message to the PDSN to indicate that the mobile user can access the services.The PDSN sends a Mobile IP based Registration Request to the mobile’s 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.The HA sends a Mobile IP based Registration Reply to the PDSN.The PDSN sends a Mobile IP based Registration Reply to the mobile.The PDSN sends a AAA Accounting Start message to the Foreign AAA.Foreign AAA forwards accounting messages to the user’s home/broker network AAA server.The mobile IP user now accesses Internet/Intranet via connection between PDSN and the HA.

• The PDSN–HA tunnel enables the sending and receiving of IP packets to andfrom the correspondent Internet node.

• The HA receives packets from the Internet/Intranet node corresponding with the mobile, and redirects them to the current PDSN.

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.


Proxy Mobile IP SetupPPP portion of the call setup is same as in Simple IP scenarios.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

Foreign AAA server will accept or deny Access Request or use a home network AAA server or a broker network AAA server.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.

PDSN sends a Mobile IP protocol Registration Request to the HA.HA uses the information in the Registration Request to form the binding record for the mobile station and allow internet access.PDSN starts sending accounting records to the Foreign AAA.Foreign AAA forwards accounting records to broker or home AAA.The Proxy mobile IP user can now access the Internet/Intranet through the connection set up between the PDSN and the HA.


CDMA2000 1xRTT DataSystem Performance Optimization

CDMA2000 1xRTT DataSystem Performance Optimization

Course RF200


The Big Picture:

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 worldsRadio environment portion

• Problems: FER, drops, access failures, capacity woes• Causes: mainly in the RF world, because of mainly RF problems

Packet environment• Problems: Setup failures, dropped connections, low throughput• Causes: could be IP-related, or could be RF related

IP D

ata

Envir

onm

entCDMA RF Environment

CDMA IOS PPPTraditional Telephony

IP Data Environment

t1t1 v CESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs

PSTN

T TSECURE TUNNELS

AuthenticationAuthorization

Accounting AAA

BTS

(C)BSC/Access ManagerSwitch WirelessMobile Device

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


Optimization Issues

Network Design and Configuration• Coverage holes, excessive coverage overlap

Call Processing Problems due to Misconfiguration• Neighbor Lists• Search Windows• Power control parameters

Physical Problems/Hardware Problems• Mismatched multicarrier sector coverage

Capacity Issues• Forward and Reverse Power Control Overload• Physical resource congestion

– Channel elements, packet pipes– IP network congestion

Managing A New Dimension: circuit-switched and IP traffic blend• QoS-related competitive issues


Optimizing in Two Worlds

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

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


Managing Forward Link Sector Loading vs. Time

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

Sect

or T

otal

TX

Pow

er o

r Thr

ough

put

Time, Seconds

Sector Maximum TX Power, Maximum Throughput

Voice Traffic

Packet Data Traffic


#6 Indicator: Data Latency

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

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

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

IP D

ata

Envir

onm



IP Data Environment

t1t1 v CESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs

PSTN

T TSECURE TUNNELS


Accounting AAA

BTS




#7 Indicator: Data Throughput

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

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

IP D

ata

Envir

onm



IP Data Environment

t1t1 v CESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs

PSTN

T TSECURE TUNNELS


Accounting AAA

BTS




System-Side 1xRTT ToolsSystem-Side 1xRTT Tools

Course RF200


Basic Philosophy of System Data

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

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 requiredIn-Class activity: view manufacturer documentation and examples


Information on System-Side Statistics

Lucent• Technical Reference: Watchmark Prospect for Lucent, v17.0

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 GuideMotorola

• “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, 2007RF200 v5.9 (c) 2007 Scott BaxterTechnical Introduction to Wireless -- ©1997 Scott Baxter - V0.0 342

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.

76.8kb/s

Mobile Tool: Andrew Invex Playback Example


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.

153.6kb/s


August, 2007RF200 v5.9 (c) 2007 Scott BaxterTechnical Introduction to Wireless -- ©1997 Scott Baxter - V0.0 344

F-SCH rates 153.6 kbps; R-SCH 76.8kbps

PN Scanner Data

Current Data Task StatusLayer-3 Messages

CDMA Status



Data Flow Management:MAC/LAC Layer OperationData Flow Management:

MAC/LAC Layer Operation

Course RF200


Forward Link SCH Scheduling

The main bottleneck is the forward link itself: restricted by available transmitter power and walsh codesEach 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

CESELt1

R-PInterface

PDSN/Foreign Agent

BTS

(C)BSC/Access ManagerWireless

Mobile Device

data

FCH orFCH + SCH?

Buffer

BTSC

My F-SCHData Rate

PCF


Forward Link Events in a Typical User Session

1.2

9.6

19.2

38.4

76.8

153.6

0

Dat

a R

ate,

kbp

s

Channel Legend:

DataIdle Data

FundamentalSupplemental

Session begins.No data, FCH idle, 1200 bps

Data in PDSNbuffer. Data flow beginson FCH

Data volume in PDSNbuffer triggers SCH assignment. SCH rate isdriven 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.


No data, FCH idle,1200 bps

FCHidle1200bps


QOS algorithmgives SCH to another userbriefly. Datameanwhileflows on FCH.

Data volume in buffer low, SCH released. Flow continues on FCH.


Activetimerruns out!FCH drops.Session isdormant.

TA



Data volume in buffer low, SCH released.Data flow continues on FCH until complete.


Mobileendssession.

Init

NullRcon

Dorm

CHldSusp

Act

STATE


1x Data Tests and Optimization1x Data Tests and Optimization

Course RF200


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

Some sessions are tormented by long latency and slow throughputWhere is the problem? Anywhere between user and distant host:

• Is the mobile user’s data device mis-configured and/or congested?• Is the 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 operator’s backbone (‘OSSN’) network?• Congestion in the PDSN HA?• Congestion in the outside-world internet or Private IP network?• Is the distant host congested, with long response times?

IP D

ata

Envir

onm



IP Data Environment

t1t1 v CESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs

PSTN

T TSECURE TUNNELS


AccountingAAA

BTS




Finding Causes of Latency and Low Throughput

IP network performance can be measured using test serversProblems between mobile a local test server? The problem is local

• check RF conditions, stats: poor environment, SCH blocking?• if the RF is clean, investigate BSC/PCU/R-P/PDSN-FA

Local results OK, problems accessing test server at PDSN-HA?• problem is narrowed to backbone network, or PDSN-HA

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

IP D

ata

Envir

onm



IP Data Environment

t1t1 v CESEL

t1

R-P Interface

PDSN/Foreign Agent

PDSNHome Agent


VPNs

PSTN

T TSECURE TUNNELS


AccountingAAA

BTS



TestServer

TestServer

TestServer


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).

HTTP GET A standard web page “browse” request. If Raw Download is unavailable, testing downlink throughput; modeling typical customer use.

HTTP POST A web-based upload (similar to how web-based email sites allow users to upload files as “attachments”).

If Raw Upload is unavailable, testing uplink throughput.

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

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

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

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

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

Modeling typical customer use.

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


Protocol-Layer-Specific DataProtocol-Layer-Specific Data

Course RF200


Watching Throughput in Real-Time

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


Protocol Stack Message Tracing

Some collection tools can display and track messages between layers of the protocol stack

• PAP, HDLC, IPCP, TCP, IP

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


TCP Application Flow and Timing Measurements

Test equipment tools include software for automatically attempting IP connectionsProcesses can be automatically measured for performance

• Throughput– Peak– average

• Latency– Minimum– Average– Peak

Tests can be conducted end-to-end at various levels of the protocol stack

Send ConnectRequest

ConnectResponseReceived?

Start

Timeout?

Transfer Data(Application-Specific)

Send TerminateRequest

TerminateResponseReceived?

Timeout?

Finish

Application throughput amount and timing begins and ends within

this block

Task Timing Ends Here

Task Timing Begins Here


Course RF200 Section V.

Applied OptimizationApplied Optimization


Starting Optimization on a New SystemRF Coverage Control

• try to contain each sector’s coverage, avoiding gross spillover into other sectors

• tools: PN Plots, Handoff State Plots, Mobile TX plotsNeighbor List Tuning

• try to groom each sector’s neighbors to only those necessary but be alert to special needs due to topography and traffic

• tools: PSMM data from mobiles; propagation predictionSearch 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 speedAccess 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.


Performance Monitoring/Growth ManagementBenchmark Existing Performance

• Dropped Call %, Access Failure %, traffic levelsIdentify Problem Cells and Clusters

• weigh cells and clusters against one anotherLook for signs of Overload

• TCE or Walsh minutes -- excessive ? Soft handoff excessive?• Required number of channel elements -- excessive?• Forward Power Overloads: Originations, Handoffs blocked

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.


CDMA Problems, Causes, and Cures

PROBLEMSExcessive Access FailuresExcessive Dropped CallsForward Link InterferenceSlow HandoffHandoff Pilot Search Window IssuesPN Planning ConsiderationsExcessive Soft HandoffGrooming Neighbor ListsSoftware Bugs, Protocol Violations

EXAMPLESNormal CallDropped Call - CoverageDropped Call - Neighbor ListDropped Call - Search Window


Solving CDMA Performance Problems

CDMA optimization is very different from optimization in analog technologies such as AMPS

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

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

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.


Troubleshooting Access FailuresTroubleshooting Access Failures


Investigating Access Failures

An access attempt failure can occur at any point in the process:Access probes exhausted (not received by system)Access probes exhausted (seen by system but ACK not reaching mobile station)Ack received by mobile station but Channel Assignment Message not seenChannel Assignment Message seen at mobile but mobile station does not acquire Forward Traffic ChannelMobile station acquires Forward Traffic Channel but system does not acquire Reverse Traffic ChannelSystem acquires Reverse Traffic Channel but Service Connect Message is not seen at mobile station.

BTS


Origination Msg


TFC frames of 000s








MSProbing

ACCESS

PAGING

FW TFC

PAGING

RV TFC

FW FC

RV TFC

FW TFC

RV TFC

FW TFC

Successful Access Attempt


Troubleshooting Access Failures & TCCFs

Troubleshooting access failures (Traffic Channel Confirmation Failures) can be difficult There are many steps in the access process

• Finding which step failed is not easyRarely, circumstantial evidence points clearly to the problemUsually, 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

The following slides describe the steps in the access process, where they take place, and some of the factors which may cause them to failThis 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


Troubleshooting Access Failures (1)

Paging Channel Access ChannelSteps in the Access ProcessBTS

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.

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 can’t 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 mobile’s origination or not

Troubleshooting Comments

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.

The mobile keeps probing until NUM_STEP probes have been sent, then repeats the probe sequence again until Max_Probe_Sequences have been sent.



Paging Channel Access ChannelThe Access ProcessBTS

Reorder

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


Mobile beeps and displays “Call Failed - System Busy”

One Dreaded Possibility:



Paging Channel Access ChannelThe Access ProcessBTS

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

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.


Channel AssignmentMessage

Base StationAcknowledgment

STOP! Leave the Paging Channel, and don’t transmit again on the access channel.The mobile now goes to try to hear the Forward Traffic Channel.



FWD Traffic Channel REV Traffic ChannelThe Access ProcessBTS

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).


Mobile beeps and displays “Call Failed”

000000000000000000000000000000000000000000000000000000000000

000000000000000000000000000000000000000000000000000000000000

If the mobile hears the required number of good empty frames, it starts transmitting its own “Reverse Traffic Channel Preamble” of empty all-zero 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.


Mobile StationAcknowledgment

If the BTS does NOT hear the mobile’s 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).”

If the BTS DOES hear the mobile’s 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.



FWD Traffic Channel REV Traffic ChannelThe Access ProcessBTS

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.


Service ConnectMessage

Service ConnectComplete Message

This is still just an ongoing access attempt


Now this is officially a call in progress


Access Failure/TCCF TroubleshootingAccess Attempt Failed

Were any probes acknowledged?

Yes,Reorder

Weak Signal/Coverage Hole?

Strong Fwd interf / pollution?

yes

yes

no

Is T-1unstable/blocking?

no

Add coverage

Identify, eliminate

Report/repair

BlockingForward Power

Channel ElementsRev. Link Noise

Optmz Fpwr DGUsAdd chan cards

Identify, fix source

No,Nothing

Yes,BS Ack

Paging Channel faded, lost

Check System Logs. Was mobile heard?

Was Channel Assignment Message heard?

no Rev Link Overload? Identify, fix source

Num_Step, Pwr_Stepappropriate?

Ensure reasonable values

Sector Size, Acq Width appropriate?

Ensure reasonable values for cell size

Check System Logs. Was CH ASN sent?

yes

System Problem.Investigate why

Software problem

Resource blockingDid mobile see N5M good

frames on F-TCH?

yes

no

Check System Logs.CH EL initialized OK?

noyes

Check System Logs. DidBTS see mobile preamble? no

yes

Did mobile see BS Ack?

Rev. Link Noise Identify, fix source

no Weak Signal/Coverage Hole?Strong Fwd interf / pollution?


Improve coverageIdentify, eliminate

Report/repair

F-TFC Channel faded, lostyes

Check System Logs.Did BTS see mobile Ack?

OK

no Weak Signal/Coverage Hole?Strong Rev Noise?


Improve coverageIdentify, eliminate

Report/repair

R-TFC Channel faded, lost

Init TCH DGU large enough? Raise DGU


1. If the failures occur in areas where one BTSis dominant, suspect BTS hardware problems.2. Plot the access failures to see if they correlatewith areas of BTS overlap. If so, suspectforward link problems. This is probablebecause the mobile does not have the normaladvantage it would get from soft handoff on atraffic channel. During access, it must successfully demodulate all five BTS messageswithout the benefit of soft handoff. If thehandset is in an area of multiple BTS overlapsor weak signal, this can be risky. In such cases,try to make the serving BTS more dominant. Also check the access/probing parameters.

If the base station never sees the mobile’s probes,the cause is probably coverage-related. If it happensin strong signal areas, suspect BTS hardware. Alsocheck datafill for proper NOM_PWR and PWR_INC.Be sure the BTS datafill access channel acquisition and demodulation search windows are adequate.

Reducing Access Failures

BTS


Origination Msg


TFC frames of 000s








MSProbing

ACCESS

PAGING

FW TFC

PAGING

RV TFC

FW FC

RV TFC

FW TFC

RV TFC

FW TFC

Access Attempt


Troubleshooting Dropped CallsTroubleshooting Dropped Calls


Dropped Call Troubleshooting - Mobile SideJust arrived on sync channel!

Is this a drop?

Were there release messages?

OK, normal end of call

This is a drop!

yes

no

Was the Sync Channel PNActive before the drop? Check

for:

yes Weak Signal/Coverage Hole?

Strong Fwd/Rev interference?no

Did mobile request Sync CH PN in PSMM before drop? Why didn’t handoff happen?

no

yes

Weak Signal/Coverage Hole?

FER already too bad?

Border configuration problems

Fast-rising pilot, slow reaction

PN not in neighbor list

Is PN in neighbor list?yes

Is SRCH_WIN_N adequate?

noAdd PN to Neighbor List!

BlockingForward Power

Channel ElementsRev. Link Noise

yes

Is cell in “island Mode”?yes

Repair/Re-initialize Cell!

no

Is T-1unstable/blocking?Is T-1unstable/blocking?


noWiden SRCH_WIN_N!

More information needed.Collect system logs and merge with mobile data,

analyze

Improve coverage

Identify, eliminate

Report/repair

Add PN to Nbr List!

Add coverage

Push earlier

Debug, reconfigure

Incr Sector OverlapSpeed up searcher

Optmz Fpwr DGUsAdd chan cards

Identify, fix source

Report/repair


Investigating Dropped Calls

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.

Each category has its own causes and solutions

Dropped call analysis can consume a considerable amount of time. Using good post-processing 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

BAD COVERAGE

FFER RXL EC/IO TxGa TxPo

BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10-20

-40-50

-30

+100

FWD. INTERFERENCE


BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10-20

-40-50

-30

+100

REV. INTERFERENCE


BTS Messaging


-110

-30100%

50%

0%

10%5%2%

-40

-90-100

-20

0

-6

-10

-15

-25

+25

+10

0

-10

-20

+23

-10-20

-40-50

-30

+100


Handoff Problems: “Window” Dropped Calls

Calls often drop when strong neighbors suddenly appear outside the neighbor search window and cannot be used to establish soft handoff.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 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

A

B

1 mi.7 Chips

BTS

BTS

SITUATION 1 Locked to distant site, can’t see

one nearby12 miles80 ChipsSRCH_WIN_N = 130BTS A is reference.BTS B appears (7-80) chipsearly due to its closer distance.This is outside the 65-chip window.Mobile can’t see BTS B’s pilot, but its strong signal blinds us and the call drops.

Travel

mountains

A

B

1 mi.7 Chips

BTS

BTS

SITUATION 2Locked to nearby

site, can’t see distant one12 miles80 Chips

Travel

SRCH_WIN_N = 130BTS B is reference.BTS A appears (80-7) chipslate due to its farther distance.This is outside the 65-chip window.Mobile can’t see BTS A’s pilot.

mountains


Optional: Quick Primer on Pilot Search WindowsThe phone chooses one strong sector and “locks” to it, accepting its offset at “face value”and interpreting all other offsets by comparison to itIn messages, system gives to handset a neighbor list of nearby sectors’ PNsPropagation delay “skews” the apparent PN offsets of all other sectors, making them seem earlier or later than expectedTo 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”) Search window values can be datafilledindividually for each Pilot set: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 One chip is 801 feet or 244.14 m

1 mile=6.6 chips; 1 km.= 4.1 chips

PROPAGATION DELAYSKEWS APPARENT PN OFFSETS

BTSBTSA

B

33Chips

4 Chips

If the phone is locked to BTS A, thesignal from BTS B will seem 29 chipsearlier than expected.If the phone is locked to BTS B, thesignal from BTS A will seem 29 chipslater than expected.


Pilot Search Order, Speed, and Implications

Actives & candidates have the biggest influence.• Keep window size as small as possible• During soft handoff, this set dominates searcher

– Minimize excessive Soft HO!Neighbor set is second-most-important

• Keep window size as small as possible• Keep neighbor list as small as possible• But don’t miss any important neighbors!

Remaining Set: pay your dues, but get no reward• You must spend time checking them, but the system can’t assign one to you

Rem

aini

ng

Act

ive+

Can

d

Nei

ghbo

rPILOT SEARCHING IN NESTED LOOPS:

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.

WINDOW SIZEIN CHIPS AND DATA UNITS

Window Size (Chips)

14 (±7)

20 (±10)

40 (±20)

60 (±30)

80 (±40)

100 (±50)

130 (±65)

160 (±80)

226 (±113)

28 (±14)

320 (±160)

452 (±226)

DatafillValue

4

5

7

8

9

10

11

12

13

6

14

15


Treating Drops with Poor-Coverage SymptomsUsing a post-processing tool, display a map of the locations of 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

Verify this type of drop is not occurring in good-coverage areas

• If so, suspect and investigate hardware at the serving site

Coverage related drops occurring in poor-coverage areas are to be expected; additional RF (usually from new BTSs) is the only solution except in rare cases

These drops are probably normal due to their locations in a predicted weak-signal area.

Drops with weak-signal symptoms happened in predicted strong-signal area. Suspect bad BTS hardware.


Treating Drops with Forward-Link ProblemsPlot 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 conflictsAnother 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)

The call on sector A dropped here, apparently due to interference from sector B. Find out why soft handoff with B did not occur.

A

B

Sync Channel Messagep_rev 1, bit_len: 170min_p_rev 1sid 4139 nid 41pilot_pn 0x164 = 356 ( RMCZ )lc_state 1ED595B9632sys_time 189406BE8lp_sec 13ltm_off 0x10 (8.0 hours)daylt 0 prat 1cdma_freq 50


“Optimizable” Dropped Calls: Slow Handoff

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 correlatormust first notice the new pilot and send a PSMM to the system.

• The system must set up the soft handoff and notify the mobile.

• The mobile must acquire the new signal by locking a finger

BTS

BTS

x


Sources of Delay Causing Slow Handoff

Every step in the handoff process can suffer delay if we’re not careful to control conditions: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 handoffsMobile reports PSMM to system.

• Reverse link noisy, PSMM must be re-requested & repeatedSystem sets up handoff, sends EHDM to mobile

• Resource congestion: no TCEs, or other problems• Forward link is noisy, mobile doesn’t hear EHDM, must repeat

Fortunately, these problems do not have to happen.


Auditing System Handoff Setup Time

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

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”

0 100 200 300 400 5000%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

Time (milliseconds)

Cum

ulat

ive

Dis

trib

utio

n Fu

nctio

n

Typical Handoff Setup Time


Setting Pilot Search Window Sizes

When the handset first powers up, it does an exhaustive search for the best pilot and no windows apply to this process.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.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.The window size for active and candidate pilots doesn’t 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!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.Neighbor and Remaining search windows should be set based on intercelldistances as described in a preceding slide.


Maximum Timing Budget for CDMA Cells

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 berecognized. Search windows are the main concern.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.The mobile is not restricted on acquiring the system forward channels but its pilot search windows are limited to 452 chips. Neighbor pilots couldn’t be recognized if coming from a cell more than 34.3 miles closer or farther than the cell to which the mobile is locked.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.General Observation: If your cell radius exceeds 30 miles, be careful.


A Word About Soft Handoff for Former AMPS/TDMA Personnel

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 bestavailable sector, but also pressure not to do many handoffs. Ping-pong is unpopular in AMPS/TDMA.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.

So, to former AMPS/TDMA folks, don’t fear. “Use the force, Luke!” And to our GSM friends, “Resistance is futile…...”


How Much Soft Handoff is Normal?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 sector’s 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 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.


Dangerous Environments

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


Identifying Causes of Excessive Soft Handoff

RF Drive Test data (preferred) or Propagation Prediction runs (second choice) can be used to identify the excessive coverage overlaps which cause soft handoff.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 sector’s 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.


Grooming Neighbor Lists

Earlier we described a general technique for creating initial neighbor lists. During initial optimization, and especially after your system generates data from commercial traffic, you’ll want to revisit and groom the neighbor lists.Use your post-processing tool to show you all handoff transitions requested by mobiles on a per-sector basis. If you don’t have a fancy software tool, you can still do it with fairly simple scripts parsing captured pilot strength measurement messages.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). 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).


TX Gain Adjust as a Per-Site Debugging ToolCollect Transmit Gain Adjust StatisticsFor an unloaded system, the average should be -7 to -12 db. and should be fairly constant throughout the coverage areaLook for big “jumps” in TX GA from sector to sector. Look for hardware problems (antennas OK, RX noise figure OK?, etc.)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. Other parameters can have similar uses; compare and study.

0 dB

-10 dB

-20 dB

Typical Mobile Station Transmit Gain Adjust

Time, Seconds


Case Study: Sudden Heavy Sector Loading

Case Study: Sudden Heavy Sector Loading

RF200 Appendix I


Runaway Class turns to Dark Side of the Force

A major PCS operator often holds technical classes in an attractive conference center on the south side of Kansas CityIn 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 happenData collection equipment was on hand to record the event from the mobile sideSystem operations personnel were available to retrieve system-side statistics for the periodLet’s see what happened!


The BTS at the BTA Conference Center

The classroom is about 500 feet northwest of the three-sector BTSThe BTS’ gamma face is the dominant sector for the classroom, at PN 212.

Looking northwest

212

208

204

N

Classroom

BTS

from RFCAD

from IQAnalyzer


What to Expect:Loading Effects on the Forward Link

On the forward link, the overhead channels (Pilot, Sync, and Paging) remain constantEach new traffic channel consumes additional transmit powerTotal transmit power increases as traffic increasesEc/Io decreases as traffic increases (Ec stays the same, but Io is driven up)


Ec/Io = (2/4)= 50%

= -3 db.

2w

1.5w

Pilot

PagingSync I0EC

0.5w

BTSTransmit

Power

Heavily Loaded

Ec/Io = (2/10)= 20%

= -7 db.

2w

1.5w

Pilot

PagingSync

I0

EC

Traffic Channels

6w

0.5w

BTSTransmit

Power


What to Expect:Loading Effects on the Reverse Link

On a lightly-loaded sector, the noise floor is relatively low and an individual mobile can be heard at comfortably low powerWhen the forward power goes up, each mobile’s open-loop power control will try to decrease mobile power outputOn a heavily loaded sector each mobile is competition against the others, so the BTS must raise each mobile’s power to remain competitiveClosed Loop power control takes a “double hit” – correcting for both increased noise and the mobile’s incorrect power control instincts

Lightly Loaded Sector

ThermalNoise

Mobile

BTSReceivePower

Heavily Loaded Sector

ThermalNoise

Other

Mobiles

BTSReceivePower

Mobile

“I can hear it coming in the air tonight…..”--Phil Collins



Heavily Loaded

BTS Loading Effects on the Reverse Link

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

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

Mobile transmit power increases substantially during heavy-traffic periods! 2w

1.5w

Pilot

PagingSync

I0

EC

Traffic Channels

6w

0.5w

2w

1.5w

Pilot

PagingSync I0EC

0.5w


All Phones in Idle Mode

Test Mobile C

all Begins

25+ Mobiles

Calls begin

Test Mobile call has ended,Other mobile calls continue

A Sudden Change!!


Test Mobile Receive Power

Average-76.5 dbm

With one user

Average-70.5 dbm

With max users

As expected, the additional calls increase the total power

output of the sector. This causes received power to

increase at the test mobile.


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.


Test Mobile Closed-Loop Power Control (TXGA)

Average-16 db

With only thisUser active

Average-6 db

while max usersactive

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.

About 6 db of this increase is necessary to counteract the

mobile’s own open-loop instinct to power down due to increased BTS power.

The rest is needed to keep the mobile’s signal competitive at

the BTS.


Test Mobile Transmit Power

Average-16 dbm

With this user only

Average-10 dbm

While max users active

Responding to the BTS closed-loop power control

instructions, the test mobile operates at a higher transmit power while competing with

many other users.

Why does all this data bounce around so much?

1. Random motion of users2. Rayleigh fading

3. Users’ varying vocoder rates4. Interference from elsewhere


System-Side Data: Channel Element Usage

BTS DateStart Time End Time MOU CE

MOU Traffic CE/User

MOU Alpha

MOU Beta

MOU Gamma %SHO Max TCE

196 11/3/98 7:00:00 7:30:00 256.73 130.11 1.97 37.2 58.52 34.38 49.32 23196 11/3/98 8:00:00 8:30:00 265.42 145.49 1.82 45.22 62.49 37.78 45.18 17196 11/3/98 8:30:00 9:00:00 342.7 186.94 1.83 52.01 90.66 44.28 45.45 18196 11/3/98 9:00:00 9:30:00 317.5 172.02 1.85 43.67 79.94 48.4 45.82 21196 11/3/98 9:30:00 10:00:00 408.81 245.55 1.66 78.35 92.33 74.87 39.93 22196 11/3/98 10:00:00 10:30:00 288.33 138.41 2.08 46.61 60.9 30.91 52 16196 11/3/98 10:30:00 11:00:00 334.61 195.06 1.72 59.71 81.78 53.58 41.71 22196 11/3/98 10:30:00 11:00:00 289.53 161.27 1.8 60.04 60.48 40.75 44.3 18196 11/3/98 11:00:00 11:30:00 366.75 210.19 1.74 70.51 91.65 48.03 42.69 21196 11/3/98 12:00:00 12:30:00 299.25 156.26 1.92 53.34 63.01 39.91 47.78 18196 11/3/98 12:00:00 12:30:00 343.03 196.39 1.75 60.06 83.54 52.79 42.75 22196 11/3/98 13:00:00 13:30:00 327.2 225.23 1.45 71.01 78.72 75.51 31.16 31196 11/3/98 13:00:00 13:30:00 316.68 168.14 1.88 54.19 68.32 45.62 46.9 18196 11/3/98 13:30:00 14:00:00 270.9 163.34 1.66 57.55 55.8 49.99 39.7 18196 11/3/98 14:00:00 14:30:00 266.42 137.25 1.94 42.92 48.73 45.6 48.48 17196 11/3/98 15:00:00 15:30:00 323.56 193.92 1.67 56.77 79.3 57.85 40.07 20196 11/3/98 15:00:00 15:30:00 427.2 269.9 1.58 83.71 100.68 85.52 36.82 23196 11/3/98 15:30:00 16:00:00 316.61 191.03 1.66 56.15 82.61 52.27 39.66 21196 11/3/98 16:00:00 16:30:00 458.76 274.99 1.67 77.06 123.62 74.31 40.06 23196 11/3/98 17:00:00 17:30:00 444.98 244.12 1.82 81.45 94.16 68.51 45.14 24196 11/3/98 17:30:00 18:00:00 414.68 233.43 1.78 84.75 86.33 62.35 43.71 24196 11/3/98 18:00:00 18:30:00 354.47 180.47 1.96 66.13 74.77 39.57 49.09 19

Totals for 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.


System-Side Data: BTS Blocks

Cell Start DateStart Time End Time

Blocks No TCE

Blocks No Fwd

Blocks No Rev

SHO Blk No TCE

SHO Blk No Fwd

SHO Blk No Rev

Succ Calls

Succ SHO

196 11/3/98 8:00:00 8:30:00 0 0 0 0 0 0 66 988196 11/3/98 8:30:00 9:00:00 0 0 0 0 0 0 112 934196 11/3/98 9:00:00 9:30:00 0 0 0 0 0 0 126 907196 11/3/98 9:30:00 10:00:00 0 0 0 0 0 0 160 1099196 11/3/98 10:00:00 10:30:00 0 0 0 0 0 0 77 853196 11/3/98 10:30:00 11:00:00 0 0 0 0 0 0 121 1009196 11/3/98 10:30:00 11:00:00 0 0 0 0 0 0 102 924196 11/3/98 11:00:00 11:30:00 0 0 0 0 0 0 132 905196 11/3/98 12:00:00 12:30:00 0 0 0 0 0 0 102 885196 11/3/98 12:00:00 12:30:00 0 0 0 0 0 0 105 852196 11/3/98 13:00:00 13:30:00 0 20 0 0 0 0 172 1018196 11/3/98 13:00:00 13:30:00 0 0 0 0 0 0 97 913196 11/3/98 13:30:00 14:00:00 0 0 0 0 0 0 117 744196 11/3/98 14:00:00 14:30:00 0 0 0 0 0 0 83 953196 11/3/98 15:00:00 15:30:00 0 0 0 0 0 0 132 924196 11/3/98 15:00:00 15:30:00 0 0 0 0 0 0 149 1103196 11/3/98 15:30:00 16:00:00 0 0 0 0 0 0 119 828196 11/3/98 16:00:00 16:30:00 0 0 0 0 0 0 129 1064196 11/3/98 17:00:00 17:30:00 0 1 0 0 0 0 128 1044196 11/3/98 17:30:00 18:00:00 0 0 0 0 0 0 129 914196 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.


System-Side Data: BTS Blocks, Access Failures

Site Call Call % Total % Tot BTS %BTS Acc. %Acc. Screen %Scr. Calls %Att. Succ. Succ. Block Block Block Block Fail Fail Calls Calls Drop Drop

===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== ===== =====196X 55 54 98.18 1 1.82 0 0 0 0 0 0 0 0196Y 111 110 99.1 0 0 0 0 1 0.9 0 0 4 3.64196Z 95 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.


CDMA Information ResourcesBibliography - Web Links

CDMA Information ResourcesBibliography - Web Links

RF200 Appendix II


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 Kitka488pp. 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 RamjeePrasad. 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.


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, well-organized, and understandable exploration of UMTS. Includes radio interface, channel explanations, link budgets, network architecture, service types, ipnetwork 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).


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 you’re not already strong in TCP/IP, you’ll 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.


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 ArtechHouse, 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 IS-634. 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 collector’s item.


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 Lee’s latest/greatest reference work on all of wireless; well done.


Web Links and Downloadable ResourcesScott Baxter: http://www.howcdmaworks.com

Latest versions of all courses are downloadable. Category - Username - PasswordIntro - (none required) - (none required)RF/CDMA/Performance - shannon - hertz3G - generation - thirdGrayson - telecom - allenAgilent - nitro - viper

Dr. Ernest Simo’s Space2000: http://www.cdmaonline.com/ andhttp://www.3Gonline.com/

CDG: http://www.cdg.org (check out the digiventsmultimedia viewable sessions)The IS-95 and IS-2000 CDMA trade marketing webside, CDMA cheerleaders.

GSM: http://www.gsmworld.comThe 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.comWireless Industry trade publication - regulatory, technical, business, marketing news.Subscribers can access text archives of past articles; very handy in researching events.


More Web Links3GPP: 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 IS-95-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/

rf200

Documents