Scott Baxter 120 - C5

Chapter 5
Multi-Carrier Operation Multi-Carrier Operation 1x Data Performance 1x Data Performance Practical Optimization Practical Optimization Additional Resources Additional Resources
December, 2003
Course 120 (c) 2003 Scott Baxter
5-1
Multi-Carrier/Multi-System/Multi-Manufacturer
World!
Systems are forced to use multiple carriers to achieve needed traffic capacity Its important that the traffic load be divided between carriers Physically adjacent friendly systems often desire to allow seamless mobile operation across their borders, although they use different carrier frequencies Even within one large network, seamless mobile operation is desired across serving switch boundaries These situations are not completely solved in the original IS-95 CDMA vision, so additional standards documents and additional proprietary processes provide the needed functionality IS-95: hashing or GSRMs can distribute idle mobiles among carriers IS-41 - provides intersystem handoffs and call delivery Proprietary algorithms can distribute in-call traffic among carriers RF tricks and network proprietary algorithms can support inter-carrier handoff Multi-Carrier Operation is a complex sport - a quadrathlon or pentathlon!
Its A
December, 2003
5-2
Multi-Carrier Operation: Mobiles Change Frequencies. When/Why/How?

System Acquisition Idle Mode Reselection Call Start: Ch. Assignment In Call: Hard Handoff
f5 f4
Hashing Proprietary Network Algorithms Nortel: MCTA Lucent: Motorola: MFCLMF
f3 f2 f1
MRU SDA
PRL-AI
GSRM MultiFreq Nbrs
Auxiliary Handoff Triggers Beacons Ec/Io, RTD Proprietary Processes
Remember: Different Mechanisms Apply at Different Stages

December, 2003 Course 120 (c) 2003 Scott Baxter 5-3
f1
Basic Multi-Carrier Operation
W0 Pilot w1 Paging wa Traffic wb Traffic w32 Sync wx Traffic wy Traffic wz Traffic W0 Pilot w1 Paging wa Traffic wb Traffic w32 Sync wx Traffic wy Traffic wz Traffic W0 Pilot w1 Paging wa Traffic wb Traffic w32 Sync wx Traffic wy Traffic wz Traffic W0 Pilot w1 Paging wa Traffic wb Traffic w32 Sync wx Traffic wy Traffic wz Traffic W0 Pilot w1 Paging wa Traffic wb Traffic w32 Sync wx Traffic wy Traffic wz Traffic W0 wa wb wc wd wx wy wz
f2
f3
f4
December, 2003
IS-95
IS-95
IS-95
IS-95
Non-originating carriers can carry more traffic!
f1
Pilot Traffic Traffic Traffic Traffic Traffic Traffic Traffic W0 wa wb wc wd wx wy wz
f2
IS-95
f3
Pilot Traffic Traffic Traffic Traffic Traffic Traffic Traffic
W0 wa wb wc wd wx wy wz
f4
IS-95
IS-95
IS-95
Many Network/Carrier Configurations are Possible!

W0 Pilot w1 Paging wa Traffic wb Traffic w32 Sync wx Traffic wy Traffic wz Traffic
f1
5-4
Some Carriers may support 1xRTT
f2
f3
W0 Pilot w1 Paging wa Data w32 Sync wx Traffic wy Traffic wz Traffic
f4
1xRTT
IS-95
IS-95
IS-95
The Big Picture: CDMA Multicarrier System Overlaying Analog System

CDMA F3 CDMA F2 CDMA F1 Analog System
Important Questions: How do idle dual-mode mobiles choose a system? When do they select analog operation? How do idle CDMA mobiles change carrier frequencies? How do CDMA mobiles in a call handoff to other carrier frequencies? Can CDMA mobiles in a call hand down to analog operation? When can a dual mode mobile return from analog to CDMA?
Adjoining CDMA Networks of Different Manufacturers

F3 F2 F1
F2
Brand X System PSTN
Brand Y System
Ordinary Interswitch Trunks (cant transmit packets, so soft handoff impossible)
At present, only Hard Handoffs work between different manufacturers Important Questions: What happens if bordering cells are on the same frequency? Advantages and drawbacks What happens if bordering cells are on different frequencies? Advantages and drawbacks
Adjoining CDMA Networks of the Same Manufacturer

F3 F2 F1
F4
F1
Brand X System PSTN
Brand X System
ATM links between CDMA packet networks (soft handoffs are desired)
At present, most manufacturers support intersystem soft handoff Important Questions: What happens if bordering cells are on the same frequency? Advantages and drawbacks What happens if bordering cells are on different frequencies? Advantages and drawbacks
Basic Principles: System Determination in Idle Mode

CDMA Idle Mode
Mobile has control, follows the System Determination Algorithm Look at most recently used frequency. Find Strongest Pilot > Read Sync > If system denied or not preferred, check other frequencies in PRL. Read Paging/Config Messages If Multiple Frequencies appear in CDMA Channel List Message, Hash and go to proper frequency If GSRM transmitted, go wherever directed Monitor Paging Channel
Analog Idle Mode

Mobile has control, follows procedures of the Standard Find Strongest CCH Monitor Paging Channel Every 3 minutes, rescan for CDMA signal
December, 2003
5-8
Avoiding Unwanted Acquisition of Supplemental CDMA Carriers

CDMA Carrier Frequency 2 GSRM CDMA Carrier Frequency 1 GSRM
System acquisition is primarily controlled by the mobile dual-mode mobiles look for last-used frequency first Distant mobiles may notice weak Carrier 2 signals beyond the edge of Carrier 2 coverage, and originate calls likely to drop system can transmit Global Service Redirection Messages on all out-looking Carrier 2 sectors to immediately force any distant mobiles to reacquire Carrier 1 there will be no F2 originations on outermost F2 sectors! However, still possible to soft-handoff into F2 outer sectors
December, 2003
5-9
System Determination During Call Setup and Call Continuation
CDMA Conversation State

System has control, follows Standard or proprietary procedures Initial channel assignment: system can select which frequency (most common trigger would be congestion on present frequency) Normal handoffs are soft, on same frequency, to mobile-selected pilots Artificial trigger mechanisms can force mobile handoff to different: 1) CDMA frequency, 2) CDMA system, or 3) analog system
Analog Conversation State

System has control, follows procedures of the Standard Mobile can be handed off to different analog cell or even different analog system based on locate receiver measurements No handoff possible to CDMA from ongoing analog call
December, 2003
5 - 10
Interfrequency Hard Handoff

In Call: Hard Handoff
f5 f4 f3 f2 f1
Auxiliary Handoff Triggers Beacons Ec/Io, RTD Proprietary Processes
Mobiles in a call are receiving only their current operating frequency Theyre unaware of the presence or absence of signals on different carrier frequencies, so they dont realize when they need to do intercarrier handoffs Networks use a variety of methods to trick mobiles into appropriate handoffs Pilot beacons - decoy signals on the current frequency that lure the mobile into disclosing needed information Tier-based triggers Round trip delay thresholds Ec/Io and other parameter thresholds
Mobiles in conversation cant see pilots on different carrier frequencies. We must trick these mobiles into handoff by artificial means.
December, 2003 Course 120 (c) 2003 Scott Baxter 5 - 11
Intersystem Hard Handoff Same Frequency causes Interference Problems!

City 2
Frequency 1 BSC1 SW1
Interference
SW2 BSC2
City 1
Consider two adjacent CDMA systems: Same frequency If not equipped for intersystem soft handoff, only hard handoff is possible between them; dragged handoffs become a big problem Handoff Performance Results: Mobiles CAN see pilots from adjoining system, so mobile-directed handoff is possible However, due to hard handoff mobiles can use only one system or the other, not both, and simultaneous shared power control is not possible dragging mobiles cause severe interference in border cells border area has poor capacity, high access failures and dropped calls
Intersystem Soft Handoff: Avoids Border Area Interference Problems

City 2
Frequency 1 BSC1 SW1
no problems!
SW2 BSC2
City 1 Intersystem Soft Handoff ATM link
Consider two adjacent CDMA systems: Same frequency ATM connection between BSCs allows soft handoff Handoff Performance Results: Mobiles CAN see pilots from adjoining system, so mobile-directed handoff is possible Intersystem soft handoff is possible, so simultaneous power control is possible for mobiles in border area Border RF environment is the same as internal RF environment, no special problems
Avoid Interference, Use Different Frequencies?

Hard Handoff Logistical Problems
F2 Mobiles cant see F1 pilots!
Frequency 2 Frequency 1 SW2 BSC2 BSC1 SW1
City 2
City 1
F1 Mobiles cant see F2 pilots!
Consider two adjacent CDMA systems: Suppose intersystem soft handoff is not available Systems are deliberately on different frequencies. This definitely avoids interference in the border area, but causes other complications Conversation-State Handoff Logistical Problems: Mobiles on one system cant see the pilots of adjoining cells on the other system! So, the mobiles will never request trans-border handoff Some method must be employed to force unsuspecting mobiles into transborder handoffs Common solutions: 1) implement intersystem soft handoff, 2) Pilot beacon cells, 3) auxiliary trigger mechanisms (Ec/Io, RTD, etc.)
One Solution to the Multi-Frequency Problem

2-Frequency Trigger Method: Beacon Cells
F2 Mobiles can see F2 beacon
Frequency 2 Frequency 1 SW2 BSC2 BSC1 SW1
City 2
City 1
F1 Mobiles can see F1 beacon
The Beacon Solution A pilot beacon cell is a mannequin -- a signal which can be seen by arriving mobiles from the other system on their own frequency, inducing them to request handoff as soon as it is appropriate When mobiles request soft handoff with the beacon, the old system steps in and instructs the mobiles to do intersystem hard handoff to the real cell which the mobiles are approaching on the other system Special Logistical Concerns with Beacons Of course, its possible for mobiles of one system to wake up looking at the pilot of a beacon cell in the border area, rather than a real cell. Therefore, a beacon cell must transmit not only its pilot, but also a sync channel and a paging channel with global service redirection
Another Solution for Multi-Frequency Handoffs

Bridge Cells, RTD Trigger in Boundary Sectors
BSC1 SW1 Frequency 2 Frequency 1 SW2 BSC2
Boundary Sector Boundary Sector City 1
City 2
All along the intersystem border, a one-cell-thick transition zone is created. The bridge cells in this zone are equipped with dual equipment, one set operating on each system. The outlooking sector of each bridge cell is tagged in the site database as a boundary sector. Whenever a mobile is served exclusively by a boundary sector, the system continuously monitors that mobiles round trip delay (RTD). When the mobiles RTD passes upward through a datafilled threshold, the system steps in and orders a hard handoff to the matching sector of the bridge cell on the other system this ensures the handoffs happen in clean environments with high probability of success disadvantage: more BTS hardware needed than otherwise
Another Solution for Multi-Frequency Handoffs

Arbitrary Ec/Io Trigger Mechanisms
BSC1 SW1 Frequency 2 Frequency 1 SW2 BSC2
Boundary Sector Boundary Sector City 1
City 2
Outlooking sectors of border cells are tagged as boundary sectors in the system database Whenever a mobile is served exclusively by a boundary sector, the system frequently interrogates the mobile with pilot measurement request messages When the mobiles reports the boundary sectors Ec/Io is below a preset threshold, the system immediately commands a hard handoff to a previously defined sector on the other system. Everyone hopes (prays?) that sector is able to hear the mobile for a successful handoff. The Ec/Io trigger threshold is sometimes a fixed value (usually 11 db above the T_Drop in the serving sector, although some networks later software allows an arbitrary trigger level to be set
CDMA2000 1xRTT Systems CDMA2000 1xRTT Systems

Data Performance Optimization Data Performance Optimization
December, 2003
5 - 18
The Big Picture:

IP Data Environment Internet VPNs
T
PDSN/Foreign Agent Backbone Network SECURE TUNNELS Authentication Authorization Accounting
PDSN Home Agent
AAA
R-P Interface
BTS
PSTN
t1
Switch
t1
SEL
CE
t1
CDMA IOS PPP
(C)BSC/Access Manager
Traditional Telephony
Coverage Holes Pilot Pollution Missing Neighbors Fwd Pwr Ovld Rev Pwr Ovld Search Windows Wireless Island Cells Mobile Device Slow Handoff
1xRTT services may include both traditional circuit-switched voice and new fast IP data connections A User's link is in multiple jeopardy, both radio and packet worlds Radio 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 Data Environment
CDMA RF Environment
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
December, 2003
5 - 20
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
December, 2003
5 - 21
Managing Forward Link Sector Loading vs. Time

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

Time, Seconds
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
Basic Forward Link Physical Capacity IS-95

One Carrier, One Sector
I 9.6K 1.2K 40 x 6K 240K
PILOT PAGING SYNC CE CE CE CE CE CE CE CE CE CE CE
CDMA2000 1xRTT
One Carrier, One Sector
I 9.6K 1.2K 40 x 6K 240K
PILOT PAGING SYNC CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE
QPSK Q Modulator
Q Modulator
QPSK
CE CE CE CE CE CE CE CE
~250Kb/s

Active/bursting
CE CE CE CE CE CE CE CE CE CE
~500Kb/s
Dormant
FCH Active 9.6K

Active Dormant
FCH 9.6K +SCH 38K FCH 9.6K +SCH 153K

Active/bursting
FCH 9.6K FCH Active 9.6K
FCH 9.6K
Dormant
Dormant
Active Dormant Dormant
Dormant Dormant Dormant
Dormant
1xRTT throughput is approximately twice IS-95 throughput Extra capacity of 1xRTT sectors can be used for fast data or more voice users
#6 Indicator: Data Latency

T
PDSN Home Agent
AAA
R-P Interface
BTS
PSTN
t1
Switch
t1
SEL
CE
t1
CDMA IOS PPP
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 network Does latency correlate with independent evidence of RF congestion?
IP Data Environment
CDMA RF Environment
#7 Indicator: Data Throughput

T
PDSN Home Agent
AAA
R-P Interface
BTS
PSTN
t1
Switch
t1
SEL
CE
t1
CDMA IOS PPP
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?
December, 2003
5 - 25
IP Data Environment
CDMA RF Environment
System-Side 1xRTT Tools System-Side 1xRTT Tools
December, 2003
5 - 26
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 required In-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 Guide Motorola Performance Analysis 2.16.0 v O , Motorola Inc., January 2002. 1x network Performance Matrix v. 0.1, Motorola Inc., April 2001. CDMA 2000 1x Voice and Data Cellular Application Note , v. 1.1 Draft; Motorola Inc. Impact on CDL and CFC in Version 2.16.0 v.1.4, Part No. 8700SCRP20GCDLCFC-D, Motorola Inc., August 2001 CFC Resolution Document v. 1.3, Motorola Inc Performance Analysis 2.16.0 v O , Motorola Inc., January 2002
December, 2003
5 - 28
Data Flow Management: Data Flow Management: MAC/LAC Layer Operation MAC/LAC Layer Operation
December, 2003
5 - 29
System MAC/LAC Parameters

How is data flow managed? Can I keep my FCH all the time? Will my connection drop in a fade? When is an SCH turned on for me? How long will my SCH burst last? What is the data rate of my SCH? If I cant get a full-rate SCH, can I at least get a lower-rate SCH? Which kinds of traffic have priority? Do some users have higher priority?
Active
T_active or Release
Initialization
Traffic channel Exists Service Option Connected Control Channel Exists
Suspended
T_suspend
Control Channel exists
Control Hold
Packet Service Packet Service Request Deactivated PPP Terminated Release Sent! Service Option Connected Control Channel Exists
T_hold
Null Reconnect
Have New Data to send! PPP Terminated Release Sent!
Dormant
The answers to all these questions are determined by MAC & LAC layer processes and parameters Each network manufacturer implements some subset of the MAC/LAC states and parameters specified in the IS-2000 standard Each manufacturer has its own unique parameter set to control state transitions Most networks begin operation using manufacturer-recommended defaults as networks and applications mature, parameters will be fully optimized A basic knowledge of the manufacturers proprietary parameters gives very useful insights into configuration and performance issues
December, 2003
5 - 30
MAC States
IP Session Internet VPNs Selector/ Channel PPP Svc Cfg (RLP) Element
Backbone Network SECURE TUNNELS
Authentication Authorization Accounting
State
F-TRAFFIC F-FCH
PDSN/ Foreign BTS Agent
PDSN Home Agent
AAA
R-P Interface
SEL
ACTIVE
exit timer: a few seconds
R-TRAFFIC R-FCH
F-SCH
CE
SCH driven by traffic
R-SCH
SCH driven by traffic
(C)BSC/ Access Manager
t1
Internet VPNs

F-TRAFFIC F-DCCH
PDSN Home Agent
AAA
R-P Interface
SEL
CONTROL HOLD
(Optional State)
R-TRAFFIC R-DCCH intermittent
t1
CE
exit timer: a few seconds very fast return to active state
Internet VPNs

PAGING
PDSN Home Agent
AAA
R-P Interface
SEL
SUSPENDED
(Optional State)
exit timer: a few seconds between data bursts
R-EACH R-CCCH intermittent
t1
CE
Internet VPNs

PAGING
PDSN Home Agent
AAA
R-P Interface
SEL
DORMANT
exit timer: minutes, hours between data bursts
R-EACH R-CCCH intermittent
t1
December, 2003
5 - 31
PDSN/Foreign Agent
Forward Link SCH Scheduling

FCH or
data Buffer
R-P Interface
FCH +
SCH?
My F-SCH Data Rate
BTS
PCF SEL
t1
CE
BTSC Wireless Mobile Device
The main bottleneck is the forward link itself: restricted by available transmitter power and walsh codes Each connected data User has a buffer in the PDSN/PCF complex When waiting data in the buffer exceeds a threshold, the PDSN/PCF asks the BTS for an F-SCH. Its data rate is limited by: Available BTS forward TX power; available walsh codes; competition from other users who also need F-SCHs; and mobile capability When the buffer is nearly empty, the SCH ends; FCH alone Occupancy timers and other dynamic or hard-coded triggers may apply QOS (Quality of Service) rules also may be implemented, giving preference to some users and some types of traffic
Forward Link Events in a Typical User Session

Data volume in PDSN buffer triggers SCH assignment. SCH rate is driven by amount of data in buffer and available TX power sector can allocate. Data volume in buffer low, SCH released. Data flow continues on FCH until complete. Data volume in PDSN buffer triggers SCH assignment. SCH rate is driven by amount of data in buffer and available TX power sector can allocate. Data volume in PDSN buffer triggers SCH assignment. SCH rate is driven by amount of data in buffer and available TX power sector can allocate.
Act Init CHld Null Dorm Rcon Susp
153.6
Data volume in buffer low, SCH released. Flow continues on FCH.
Data Rate, kbps
76.8 38.4 19.2 9.6 1.2 0

Active timer runs out! FCH drops. Session is dormant.
Data volume in buffer low, SCH released. Data flow continues on FCH until complete. No data, FCH idle, 1200 bps Mobile ends session.
TA
STATE
Session begins. No data, FCH idle, 1200 bps Data in PDSN buffer. Data flow begins on FCH FCH idle 1200 bps No data, FCH idle, 1200 bps Data in PDSN buffer. Data flow begins on FCH QOS algorithm gives SCH to another user briefly. Data meanwhile flows on FCH. No data, FCH idle, 1200 bps Data in PDSN buffer. Data flow begins on FCH
FundamentalSupplemental Idle Data Data
Channel Legend:
December, 2003
5 - 33
1x Data Tests and Optimization 1x Data Tests and Optimization
December, 2003
5 - 34
So S L O W ! !
T
Wheres My Data?!!
PDSN Home Agent
AAA
R-P Interface
BTS
PSTN
t1
Switch
t1
v SEL
t1
CE
CDMA IOS PPP
Some sessions are tormented by long latency and slow throughput Where is the problem? Anywhere between user and distant host: Is the mobile users data device mis-configured and/or congested? Is the BTS congested, with no power available to produce an SCH? Poor RF environment, causing low rates and packet retransmission? Congestion in the local IP network (PCU, R-P, PDSN FA)? Congestion in the wireless operators backbone (OSSN) network? Congestion in the PDSN HA? Congestion in the outside-world internet or Private IP network? Is the distant host congested, with long response times?
IP Data Environment
CDMA RF Environment
Finding Causes of Latency and Low Throughput

Test Server Test Server IP Data Environment
T
Test Server
PDSN/Foreign Agent
Internet VPNs
Backbone Network SECURE TUNNELS Authentication Authorization Accounting
PDSN Home Agent
AAA
R-P Interface
BTS
PSTN
t1
Switch
t1
v SEL
t1
CE
CDMA IOS PPP
IP network performance can be measured using test servers Problems between mobile a local test server? The problem is local check RF conditions, stats: poor environment, SCH blocking? if the RF is clean, investigate BSC/PCU/R-P/PDSN-FA 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 Data Environment
CDMA RF Environment
Practical Practical CDMA Performance Optimization CDMA Performance Optimization
December, 2003
5 - 37
Good Performance is really Simple!!

One, Two, or Three good signals in handoff Composite Ec/Io > -10 db Enough capacity for the offered traffic No resource problems
In principle, A COW next door Can solve almost any CDMA problem!
BTS
BTS
BTS
Ec/Io
BTS A
BTS B
BTS C
-10
FORWARD available LINK

power Traffic Channels In use Paging Sync Pilot
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.
December, 2003
5 - 38
Bad Performance Has Many Causes

+41 +8
360
A
BTS
360+33c
B
BTS
No Available Power!
Traffic Channels In Use
BTS Rx Pwr Overload
CEs
Vocoders Selectors
Paging Sync Pilot
x
BTS B PN 99
BTS A PN 100 ACTIVE SEARCH WINDOW
1 mile
11 miles
Weak Signal / Coverage Hole Pilot Pollution Excessive Soft Handoff Handoff Failures, Rogue mobiles Missing Neighbors Search Windows Too Small BTS Resource Overload / No Resources No Forward Power, Channel Elements No available Walsh Codes No space in Packet Pipes Pilot Surprise ambush; Slow Handoffs PN Plan errors Slow Data Problems: RF or IP congestion Improper cell or reradiator configuration Hardware and software failures But on analysis, all of these problems bad effects happen because the simple few-signal ideal CDMA environment isnt possible.
5 - 39
BTS Sector Transmitter
December, 2003
What is Performance Optimization?

Performance Optimization involves design and modification of the network, gathering and analysis of data, adjustments to network parameters, and constant evaluation of current network conditions The work includes complex design and simulations, nuts-and-bolts call processing troubleshooting and hardware testing, to growth management and planning System Performance Optimization includes many different smaller processes at many points during a systems life Evaluating the system design with simulation tools to evaluate the performance and capacity of the system Finding workarounds for design issues (cant build a crucial site, too much overlap/soft handoff, coverage holes, etc.) cluster testing and cell integration to ensure new BTS hardware works, datafill is proper, and call processing is normal fine-tuning system parameters for the best possible call performance Fixing root causes of specific problems and customer complaints carefully watching system traffic growth and managing the problems it causes - implementing short-term fixes to ease hot spots, and recognizing problems before they become critical It takes many different skills and perspectives to optimize wireless networks
Early Assessment and RF Optimization Steps

RF Coverage Control try to contain each sectors coverage, avoiding gross spillover into other sectors tools: PN Plots, Handoff State Plots, Mobile TX plots Neighbor List Tuning try to groom each sectors neighbors to only those necessary but be alert to special needs due to topography and traffic tools: PSMM data from mobiles; propagation prediction Search Window Settings find best settings for SRCH_WIN_A, _N, _R especially optimize SRCH_WIN_A per sector using collected finger separation data; has major impact on pilot search speed Repeat as necessary until no large problems remain Access Failures, Dropped Call Analysis finally, iterative corrections until within numerical goals IP Data Performance Assessment Identify, manage, resolve latency and throughput issues Getting these items into shape provides a solid baseline and foundation for comparison, tracking, and planning in the future.
Performance Monitoring/Growth Management

Benchmark Existing Performance from system-side data Dropped Call %, Access Failure %, traffic levels Identify Problem Cells and Clusters weigh cells and clusters against one another Investigate and resolve any problems, using field drive data if needed Look for signs of Overload TCE or Walsh minutes -- excessive ? Soft handoff excessive? Required number of channel elements -- excessive? Forward Power Overloads: Originations, Handoffs blocked 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 Use high-level simulation tools to gain insight into user statistics Compare different cell configurations against statistically generated traffic simulations to identify what works best, and try it out! This process never ends. The community, the system, and the customers are always growing and presenting new problems and capacity needs.
CDMA Problems, Causes, and Cures

PROBLEMS Excessive Access Failures Excessive Dropped Calls Forward Link Interference Slow Handoff Handoff Pilot Search Window Issues PN Planning Considerations Excessive Soft Handoff Grooming Neighbor Lists Software Bugs, Protocol Violations EXAMPLES Normal Call Dropped Call - Coverage Dropped Call - Neighbor List Dropped Call - Search Window
Troubleshooting Access Failures Troubleshooting Access Failures
December, 2003
5 - 44
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 seen Channel Assignment Message seen at mobile but mobile station does not acquire Forward Traffic Channel Mobile station acquires Forward Traffic Channel but system does not acquire Reverse Traffic Channel System acquires Reverse Traffic Channel but Service Connect Message is not seen at mobile station.
December, 2003
Successful Access Attempt

Origination Msg BTS PAGING Base Sta. Acknlgmt. Order FW TFC TFC frames of 000s PAGING Channel Assnmt. Msg. TFC preamble of 000s RV TFC FW FC Base Sta. Acknlgmt. Order Mobile Sta. Ackngmt. Order RV TFC FW TFC Service Connect Msg. Svc. Connect Complete Msg FW TFC Base Sta. Acknlgmt. Order RV TFC MS Probing ACCESS
Call is Established!
5 - 45
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 easy Rarely, circumstantial evidence points clearly to the problem Usually, it is necessary to debug the process leading up to the access failure Consider each step in the access process Get evidence to determine whether this step occurred successfully Move on to the next step and keep checking steps until the unsuccessful step is found Determine why this step failed The following slides describe the steps in the access process, where they take place, and some of the factors which may cause them to fail This narrative might be useful as a template for organizing your own thinking as you investigate access failures you are tracking! Go out and capture actual drive tests of failed origination attempts If possible, also collect system logs (RF call trace, etc.) for the same event
Troubleshooting Access Failures (1)

BTS
Steps in the Access Process

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

BTS
The Access Process

Access Channel
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
Paging Channel
One Dreaded Possibility: Reorder

Mobile beeps and displays Call Failed - System Busy
December, 2003
5 - 48

BTS
The Access Process

Access Channel
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.
Paging Channel
Base Station Acknowledgment
Channel Assignment Message
STOP! Leave the Paging Channel, and dont transmit again on the access channel. The mobile now goes to try to hear the Forward Traffic Channel.
December, 2003
5 - 49

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

00000000000000000000 00000000000000000000 00000000000000000000 Mobile beeps and displays Call Failed
00000000000000000000 00000000000000000000 00000000000000000000
Base Station Acknowledgment Mobile Station Acknowledgment
If the BTS DOES hear the mobiles access preamble, it will send an acknowledgment. The mobile responds with an acknowledgment, or maybe even a pilot strength measurement message if it already needs a handoff.
December, 2003
5 - 50

BTS
The Access Process

Service Connect Message
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.
FWD Traffic Channel REV Traffic Channel
Service Connect Complete Message This is still just an ongoing access attempt Base Station Acknowledgment Now this is officially a call in progress
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.
December, 2003
5 - 51
Access Failure/TCCF Troubleshooting

Access Attempt Failed Were any probes acknowledged? Yes, BS Ack No, Nothing Yes, Reorder Blocking Forward Power Channel Elements Rev. Link Noise Optmz Fpwr DGUs Add chan cards Identify, fix source Add coverage Identify, eliminate Report/repair Identify, fix source Ensure reasonable values Ensure reasonable values for cell size Software problem Resource blocking
Weak Signal/Coverage Hole? Paging Channel faded, lost no Strong Fwd interf / pollution? Is T-1unstable/blocking? Check System Logs. Was mobile heard? yes no Was Channel Assignment Message heard? yes Did mobile see N5M good frames on F-TCH? yes Check System Logs. Did BTS see mobile preamble? yes Did mobile see BS Ack? yes Check System Logs. Did BTS see mobile Ack? OK yes Check System Logs. Was CH ASN sent? no no Check System Logs. CH EL initialized OK? yes no no F-TFC Channel faded, lost Rev Link Overload? Num_Step, Pwr_Step appropriate? Sector Size, Acq Width appropriate? System Problem. Investigate why
no
Rev. Link Noise Init TCH DGU large enough? Weak Signal/Coverage Hole? Strong Fwd interf / pollution? Is T-1unstable/blocking? Weak Signal/Coverage Hole? Strong Rev Noise? Is T-1unstable/blocking?
Identify, fix source Raise DGU Improve coverage Identify, eliminate Report/repair Improve coverage Identify, eliminate Report/repair
no
R-TFC Channel faded, lost
December, 2003
5 - 52
Reducing Access Failures

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

Just arrived on sync channel! Is this a drop? yes Were there release messages? no This is a drop! yes Check for: yes Weak Signal/Coverage Hole? Strong Fwd/Rev interference? Is T-1unstable/blocking? Why didnt handoff happen? PN not in neighbor list Weak Signal/Coverage Hole? FER already too bad? Border configuration problems Fast-rising pilot, slow reaction Forward Power Channel Elements Rev. Link Noise Add PN to Nbr List! Add coverage Push earlier Debug, reconfigure Incr Sector Overlap Speed up searcher Optmz Fpwr DGUs Add chan cards Identify, fix source Report/repair Improve coverage Identify, eliminate Report/repair OK, normal end of call
Was the Sync Channel PN Active before the drop? no Did mobile request Sync CH PN in PSMM before drop? no Is PN in neighbor list? yes no yes Repair/Re-initialize Cell! Is SRCH_WIN_N adequate? yes Is cell in island Mode? no Is T-1unstable/blocking?
no Add PN to Neighbor List!
Widen SRCH_WIN_N!
Blocking
Is T-1unstable/blocking? More information needed. Collect system logs and merge with mobile data, analyze
December, 2003
5 - 55
CDMA Information Resources CDMA Information Resources

Bibliography -- Web Links Bibliography Web Links
December, 2003
5 - 56
Bibliography, 3G Air Interface Technologies

"Wireless Network Evolution 2G to 3G" by Vijay K. Garg. 764pp. 2002 Prentice-Hall, Inc. ISBN 0-13-028077-1. $130. Excellent technical tutorial and reference. The most complete and comprehensive technical detail seen in a single text on all these technologies: IS-95 2G CDMA, CDMA2000 3G CDMA, UMTS/WCDMA, Bluetooth, WLAN standards (802.11a, b, WILAN). Includes good foundation information on CDMA air interface traffic capacity, CDMA system design and optimization, and wireless IP operations. Excellent level of operational detail for IS-95 systems operating today as well as thorough explanations of 2.5G and 3G enhancements. 3G Wireless Demystified by Lawrence Harte, Richard Levine, and Roman Kitka 488pp. Paperback, 2001 McGraw Hill, ISSBN 0-07-136301-7 $50. For both non-technical and technical readers. An excellent starting point for understanding all the major technologies and the whole 3G movement. Comfortable plain-language explanations of all the 2G and 3G air interfaces, yet including very succinct, complete, and rigorously correct technical details. You will still want to read books at a deeper technical level in your chosen technology, and may sometimes turn to the applicable standards for finer details. This book will give you how your technology relates in the big picture, and probably all you care to know about technologies other than your own. "3G Wireless Networks" by Clint Smith and Daniel Collins. 622pp. Paperback. 2002 McGraw-Hill, ISBN 0-07-136381-5. $60. An excellent overview of all 3G technologies coupled with good detail of network architectures, channel structures, and general operational details. Good treatment of both CDMA2000 and UMTS/WCDMA systems. WCDMA: Towards IP Mobility and Mobile Internet by Tero Ojanpera and Ramjee Prasad. 476pp. 2001 Artech House, ISSBN 1-58053-180-6. $100. A complete and definitive work on UMTS (good CDMA2000, too!). CDMA principles, Mobile Internet, RF Design, Air Interface, WCDMA FDD standard, WCDMA TDD, CDMA2000, Performance, Hierarchical Cell Structures, Implementation, Network Planning, Basic IP Principles, Network Architectures, Standardization, Future Directions. December, 2003 Course 120 (c) 2003 Scott Baxter 5 - 57
More Bibliography, 3G Air Interface Technologies

The UMTS Network and Radio Access Technology by Dr. Jonathan P. Castro, 354 pp. 2001 John Wiley, ISBN 0 471 81375 3, $120. An excellent, wellorganized, and understandable exploration of UMTS. Includes radio interface, channel explanations, link budgets, network architecture, service types, ip network considerations, a masterful tour de force through the entire subject area. Very readable, too! WCDMA for UMTS by Harri Holma and Antti Toskala, 322 pp. 2000 Wiley, ISBN 0 471 72051 8, $60. Very good overall treatment of UMTS. Excellent introduction to 3G and summary of standardization activities, every level of UMTS/UTRA. Good overview of CDMA-2000, too! The GSM Network - GPRS Evolution: One Step Towards UMTS 2nd Edition by Joachim Tisal, 227pp. paperback, 2001 Wiley, ISBN 0 471 49816 5, $60. Readable but not overwhelming introduction to GSM in all its aspects (140pp), DECT (11pp), GPRS (6pp), UMTS (7pp), WAP (25pp), EDGE (10pp).
December, 2003
5 - 58
Bibliography, The IP Aspect of 3G

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

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

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

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

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

Scott Baxter 120 - C5

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Scott Baxter 120 - C5

Hochgeladen von

Copyright:

Verfügbare Formate

Chapter 5

Course 120 (c) 2003 Scott Baxter

Course 120 (c) 2003 Scott Baxter

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

GSRM MultiFreq Nbrs

Auxiliary Handoff Triggers Beacons Ec/Io, RTD Proprietary Processes

Remember: Different Mechanisms Apply at Different Stages

Non-originating carriers can carry more traffic!

Many Network/Carrier Configurations are Possible!

Course 120 (c) 2003 Scott Baxter

Some Carriers may support 1xRTT

W0 Pilot w1 Paging wa Data w32 Sync wx Traffic wy Traffic wz Traffic

The Big Picture: CDMA Multicarrier System Overlaying Analog System

Adjoining CDMA Networks of Different Manufacturers

Brand X System PSTN

Ordinary Interswitch Trunks (cant transmit packets, so soft handoff impossible)

Adjoining CDMA Networks of the Same Manufacturer

Brand X System PSTN

Basic Principles: System Determination in Idle Mode

Analog Idle Mode

Course 120 (c) 2003 Scott Baxter

Avoiding Unwanted Acquisition of Supplemental CDMA Carriers

Course 120 (c) 2003 Scott Baxter

System Determination During Call Setup and Call Continuation

CDMA Conversation State

Analog Conversation State

Course 120 (c) 2003 Scott Baxter

Interfrequency Hard Handoff

Intersystem Hard Handoff Same Frequency causes Interference Problems!

Intersystem Soft Handoff: Avoids Border Area Interference Problems

City 1 Intersystem Soft Handoff ATM link

Avoid Interference, Use Different Frequencies?

F1 Mobiles cant see F2 pilots!

One Solution to the Multi-Frequency Problem

F1 Mobiles can see F1 beacon

Another Solution for Multi-Frequency Handoffs

Boundary Sector Boundary Sector City 1

Another Solution for Multi-Frequency Handoffs

Boundary Sector Boundary Sector City 1

CDMA2000 1xRTT Systems CDMA2000 1xRTT Systems

Course 120 (c) 2003 Scott Baxter

The Big Picture:

PDSN Home Agent

Course 120 (c) 2003 Scott Baxter

Optimizing in Two Worlds

Course 120 (c) 2003 Scott Baxter

Managing Forward Link Sector Loading vs. Time

Packet Data Traffic Voice Traffic

Basic Forward Link Physical Capacity IS-95

FCH 9.6K +SCH 38K FCH 9.6K +SCH 153K

FCH 9.6K FCH Active 9.6K

Active Dormant Dormant

Dormant Dormant Dormant

#6 Indicator: Data Latency

PDSN Home Agent

#7 Indicator: Data Throughput

PDSN Home Agent

Course 120 (c) 2003 Scott Baxter

System-Side 1xRTT Tools System-Side 1xRTT Tools

Course 120 (c) 2003 Scott Baxter

Basic Philosophy of System Data

Information on System-Side Statistics