Ph0+ Umts Pre-Launch RF Optimization Training: 14th May 2008

PH0+ UMTS
Pre-Launch RF
Optimization
Training
14th May 2008
Confidential and Proprietary Information of T-Mobile USA
Pre-Launch RF Optimization
Topics
Pre-launch RF optimization process overview

UMTS network integrity validation
Drive test validation
Swap sector and SC consistency check
Single cell coverage analysis
Azimuth verification
Pilot pollution analysis
Neighbor analysis
Coverage optimization
Access failure and dropped call analysis
IRAT handover optimization
Pre-launch RF Optimization Process

Overview
Pre-launch RF Optimization Process

Overview
Three rounds of RF optimization after spectrum

verification and site acceptance completion:
Unloaded, Loaded and Market
Unloaded cluster optimization focuses on
resolving major RF issues
Loaded cluster optimization goal is further
improving network in terms of quality and capacity
in simulated real network conditions
Objective is to meet required cluster/market level
KPIs
Unloaded/Loaded Cluster Launch KPIs
Market Launch KPIs
Cluster and Late Sites DT Setup
Market DT Setup
UMTS Network Integrity Validation

UMTS network integrity check includes RNC/RBS
alarm, cell availability and T1 errors status
inspection
UMTS network integrity should be confirmed prior
to any drive test activity
Post drive integrity check data is valuable input for
drive test analysis
Drive Test Preparation Activities

Drive test route design and verification
UMTS network integrity check
Network/route definition data provisioned to drive
test teams (Tems cellfile, DT route, DT sequence)
IMSI traces (UETR, GPEH) turned on for (selected)
test mobiles
Correct DT setup and best practices communicated
with DT teams
10
Drive Test Log Files Validation

Collected DT log files need to be verified before
loaded to Actix for processing
DT log files are checked among others for naming,
route completion, UE setup and technology mode
used, GPS and Scanner integrity, and collected
signal levels
Use attached TI workspace both for LT1 and LT2 DT
setup validation
TI WS
Every DT log file opened in TI and verified

Only DT files for completed and verified subcluster
drive uploaded to NUSC
11

1. Confirm GPS data validity
(UMTS/LT1)
UMTS categories
visible on DT
route for valid
GPS data
Confirm GPS
data validity
12

2. Verify UMTS Scanner data validity
(UMTS/LT1)
Verify UMTS Scanner
frequency (2037) and signal
level; Signal level should be
reasonably good next to
UMTS site (e.g. -50dBm) and
app. 10-15dB higher than the
one measured by in-car UEs
13

3. Verify GSM Scanner data validity
(UMTS/LT1)
Verify that scanned GSM ARFCNs

belong to frequency band used by
T-Mobile (593 to 609)
14

4. Verify CS Short Voice UE
(UMTS/LT1)
Confirm UMTS technology
mode and RRC State
throughout the call
Confirm L3 messages
and events related to
UMTS CS voice mobile
Confirm that CS Short UE is
connected as MS2; Call
duration should be 15s with
10s gap between calls; CS
Short UE should not be Idle
for a longer period of time;
Call setup should be reattempted after blocked call
CPICH RSCP data are

collected for UE in UMTS
mode; Verify MS2 signal
level against UMTS
scanner
15

Typical L3 Call Flow for UMTS CS Voice Call
Setup
Verify UL interference
level prior to RRC
Connection setup
Verify CS voice RRC

establishment cause
Verify SC UE used to
initiate call setup
Verify if CS voice was

locked to UMTS
16

5. Verify CS Long Voice UE (UMTS/LT1)
mode and RRC State
throughout the call
Confirm that CS Long UE

is connected as MS3;
Longer Idle periods
shouldnt exist; Call should
be re-established after
dropped call
Confirm L3 messages
UMTS CS voice mobile
CPICH RSCP data are
level against UMTS
scanner
17

6. Verify PS R99 UE (UMTS/LT1)
Confirm that PS UE is
connected as MS4; UE
should repeatedly
download 2MB file from ftp
server; Confirm R99
throughput and data sum
received at the end of
session (2MB);

mode and RRC State
throughout the call
Confirm L3 messages and
events related to UMTS
PS mobile; Check event
log for any Session Errors
and PDP Context Failures
CPICH RSCP data are

level against UMTS
scanner
18

Typical L3 Call Flow for PS R99 Call
Setup
19

7. Verify CS Short Voice UE (GSM/LT2)
Confirm L3 messages
GSM CS voice mobile
Confirm GSM technology

and channel mode
throughout the call
Confirm that GSM CS Short

UE is connected as MS1;
CS Short UE should not be
Idle for a longer period of
time; Call setup should be
re-attempted after blocked
call
20

8. Verify CS Long Voice UE (GSM/LT2)
Confirm that GSM CS Long

UE is connected as MS2;
Longer Idle periods
shouldnt exist; Call should
be re-established after
dropped call
Confirm L3 messages
GSM CS voice mobile
Confirm GSM technology

and channel mode
throughout the call
21

9. Verify CS Idle UE (GSM/LT2)
Confirm L3 messages
related to Idle mode
Confirm UE is in Idle
(either GSM or UMTS)
mode throughout the call
22

10. Verify DT Log File Name
23
DT Route Completion Verification

In order to verify route completion DT log
files are exported in MapInfo format and
compared against route definition
Use attached MapInfo export setup files
for LT1 (UMTS) and LT2 (GSM) log files
UMTS MEX
GS M MEX
Check DT diary for any

comments (e.g.
explanation for section
of DT route skipped due
to road works)
24

cont.
Export DT logs
in MapInfo
format to verify
route completion
25

cont.
26
DT Analysis Overview
Swap sector and
SC consistency check
Coverage optimization
Single cell coverage analysis
& Azimuth verification
Access failure and
dropped call analysis
Pilot pollution analysis
IRAT handover optimization
Neighbor analysis
27
Swap Sector and SC Consistency

Check
Identify swapped sectors and improper SC data fill using
Scanner Best Server SC plot (CPICH_Scan_SC_SortedbyEcIo_0)
Use Cell Color property based on SC;

Turn on Scanner Best Server SC labels;
Always use Scanner plot since UE could
be impacted by a poor neighbor List
28

Check
Swapped sectors example
UBQ04388A21 swapped
with UBQ04388A31
29

Check
Scanner Where Seen coverage plot used in
ambiguous situations
30

Check
Wrong antenna direction sometimes incorrectly
interpreted as swapped sector

Observe impact of near field obstructions on cell
coverage
UBQ06088I11 azimuth
confirmed 80 instead of
30; High buildings block
coverage north bound
31
Single Cell Coverage Analysis

Used for isolating overshooting, coverage and
wrong antenna direction problems
Scanner Where Seen coverage plot utilized to
determine cell footprint
Change Scanner Best Server
symbol size to minimum (1)
and turn on SC labels to
determine best server serving
zone against where seen
plot;
Overshooting cell coverage
exceeds beyond the 1st and
in some cases even 2nd and
3rd tier cells;
Any tilt or azimuth change
designed to limit pilot
spillover should not
jeopardize best server
coverage.
32

Checking Where Seen coverage plot for each and
every cluster cell can be time consuming
Potential overshooters can be drilled down using
number of cell coverage samples in Cell Coverage
Tab of the Radio Network Explorer Window
Cell coverage is quantified with

number of samples instead of bins
which sometimes can be misleading
33

Overshooters (boomers) greatly contribute to
downlink interference, increase SHO overhead and
packet sharing and are susceptible to uplink
interference which reduces cell capacity
Poor coverage identified relatively close to the site
can be caused by wrong antenna azimuth
implementation, improper EDT/MTD settings or
implementation, near field obstructions, Node B HW
issues or feeder/connector issues
Co-sector GSM data can be used to validate UMTS
cell coverage
If reason for poor cell coverage cannot be
determined FOPS site verification requested
34
Analysis done in parallel with single cell coverage
verification
Scanner Where Seen coverage plot utilized to
assess cell azimuth against RF design
Potential antenna direction problems can be drilled
down using percentage of coverage samples
beyond nominal cell beamwidth
Cells should be filtered
for minimum number of
coverage samples (e.g.
5000) before sorting
table per %>Beam
column;
Cell coverage is
quantified with number
of samples instead of
bins which sometimes
can be misleading
35
Co-sector GSM data can be used to validate UMTS
cell azimuth
FOPS site verification requested if wrong antenna
direction suspected
UBQ04956A31 azimuth
confirmed 315 instead
of 270
36
Pilot Pollution Analysis

Identify areas with pilot pollution and improve
overall Ec/No
Area suffer from pilot pollution when more than 3
pilots are measured within 5dB of strongest one in
acceptable coverage conditions
Spotlight Cell Pilot
Pollution analysis
based on all collected
data samples proven to
be ineffective to identify
pilot pollution problems
37

Initial Tuning Macro used as an alternative to quantify
pilot pollution problems
ITM is Excel tool based on binned Scanner data
Small bin size (5x5m) recommended for dense urban
area while medium bin size (10x10m) is applicable for
other
Two output sheets generated per ITM Polluter
analysis detailed and condensed one
Detailed ITM polluter output sheet have listed data
for every polluted bin, including outbound and
inbound Cell Id, EcNo, RSCP, neighbor definition falg
and distance to bin
Condensed ITM polluter output sheet contains
information aggregated per outbound polluter cell
38
Macro User Interface

User can set EcNo, EcNo delta and RSCP
thresholds used in initial tuning analysis
Polluter and Neighbor analysis are run
separately
Displayed ITM
threshold values
recommended for
unloaded tuning drive
39
Condensed ITM
polluter output sheet
Detailed ITM polluter

output sheet
ITM polluter output

displayed on map
40

Major polluters (cells with highest number of
outbound polluted bins) should be thoroughly
checked
In addition areas with concentrated polluted bins
should be examined to improve signal dominance
and overall EcNo
Affected areas should be checked for UE EcNo to
determine severity of pilot pollution
Typically 3-5dB interferer signal reduction would
resolve pilot pollution issues, while boomer cells
may require further reduction if feasible
Polluter signal level should be incpected both in
interferer and best server zones and compared with
levels measured for other cells
41

Tilt or azimuth changes should be carefully balanced
to reduce pollution and maintain acceptable signal
level at the same time
Outbound polluter best server
zone circled with green line
RSCP better than -70dBm in
compact best server zone;
Polluted bin areas marked with
blue circles note that not all of
spillover bins are identified with
pilot pollution
42

Check terrain profile, height difference, distance
between Tx antenna and polluted area, antenna type
and current tilt implemented to estimate tilt change
needed; If needed use Asset to confirm all changes
43

Check terrain profile, height difference and distance
between Tx antenna and polluted area to estimate tilt
change needed
Inclination angle between Tx

antenna and polluted area
Effective vertical plane
antenna attenuation angle
Tilt Calculator
44

Best server cell is not necessarily preferred/needed
in certain area if neighbor signal levels are
acceptable
UBQ04618B31 Best Server Scanner plot, drive 01
UBQ04006A31 Where Seen Scanner plot, drive 01
Although not best server along Grand Central Pkwy in circled area UBQ04006A31
would provide excellent coverage if UBQ04618B31 coverage was reduced
45

In some cases
several
itterations of tilt
changes
needed to fully
optimize cell
footprint;
Tilt change
execution can
be costly when
MDT is needed
or remote EDT
is not feasible
in such cases
2dB considered
as a minimum
attenuation
change that
validates tilt
alteration
UBQ04618B31 Where Seen Scanner plot,

drive 01, tilt as per design 0+6
UBQ04618B31 Best Server Scanner plot,

drive 01, tilt as per design 0+6

drive 02 after tilt change from 0+6 to 0+7

drive 03 after tilt change from 0+7 to 0+8
46
Neighbor Analysis
Identify missing UMTS neighbors
Missing neighbors one of the major reasons of
dropped calls in early network stages due to
connection release mechanism designed to avoid
excessive UL interference
Spotlight 3G Missing
Neighbors analysis
based on all collected
data samples has
shown issues with
matching sample SC
with Cell Id
47
Neighbor Analysis
Initial Tuning Macro used as an alternative to
identify missing neighbors
Two output sheets generated per ITM Neighbor
analysis detailed and condensed one
Detailed ITM neighbor output sheet have listed data
for every missing neighbor bin, including outbound
and inbound Cell Id, EcNo, RSCP and distance
between cells
Condensed ITM neighbor output sheet contains
information aggregated per missing neighbor
relation
48
Neighbor Analysis
Detailed ITM neighbor

output sheet
Condensed ITM
neighbor output sheet
49
Neighbor Analysis
Missing neighbor relations detected within highest
number of bins should be thoroughly checked
In cases where neighbor relation is missing
between faraway cells containing overshooting
cell(s) should be considered as an alternative
Check for maximum allowed number of UMTS
neighbors should be carried out before neighbor
additions are submitted
Boomer cells tend to have high number of defined
neighbors so keeping optimal neighbor list is
essential
50
Coverage Optimization
Poor DL coverage identified using Scanner Best
Server SC plot (<-105dBm)
Scanner DL signal level should be compared with
the RSCP prediction from the RF design wherever
inferior to the prediction further analysis is required
Poor coverage
measured north of
UBQ06088I site
inferior to the
prediction;
UBQ06088I11
azimuth confirmed
80 instead of 30
with high buildings
blocking coverage
north bound
Scanners RSCP Coverage
Asset RSCP Prediction
51
Main causes for poor coverage can be terrain,
obstructions, azimuth settings, EDT/MDT settings,
high feeder loss, CPICH output power or HW issues
While improving coverage care should be taken not
to increase pilot pollution
If reason for poor cell coverage cannot be
determined FOPS site verification requested
UBQ04870C31
azimuth changed
from 260 to 290
improved signal
level within the
area but didnt
entirely resolve the
problem
Scanner RSCP Coverage Azimuth 260
Scanner RSCP Coverage Azimuth 290
52
Google Earth and Live Maps used as

additional source of mapping
information
53
Poor UL coverage normally corresponds to high UE
Tx Power
Main objective of checking the UE Tx Power is to
verify the Path Balance in areas with acceptable DL
RSCP and high UE Tx Power
UL coverage issues can be caused by TMA, feeder,
antenna or Node B HW issues, improper UL power
control parameters, improper cell (re)selection
parameters, improper Node B parameters
(ulAttenuation, dlAttenuation, TMA insertion loss,
TMA Gain, etc) or external UL interference
High RTWP received at Node B could indicate HW
issues or UL interference
54
Access Failure and Call Drop Analysis

Overview
Identify call failure location
on the map
Inspect L3 message and event flow,

determine at which stage
failure occurred
Determine serving cells and

compare them with cells logged
with Scanner and other UEs
Check terrain profile, area photos and

any other supporting material if needed
Check serving, monitored and

detected cells RSCP and EcNo
within relevant time frame
If Core, HW or UTRAN issues

suspected, confirm alarm, T1, availability,
and parameter values of the cells involved
Check UE Tx power level and

transport channel BLER
within relevant time frame
Check
UE Tx
power
level
and
Check
UETR
and/or
UEH
Exception
logs
to investigate
details
transport
channel
bler of
HW or
UTRANtimeframe
issues
within
relevant
55
Access Failure Analysis

Three essential procedures that need to be
completed before call setup is deemed to be
successful: RACH Access, RRC Connection Setup
and RAB Setup procedures
Signalling connection establishment:
RRC connection setup monitored
based on N300 (5) and T300 (2s)
parameters; Reasons for setup
failure could be PRACH preambules
not detected or detected but
negatively acknowledged, RRC
Connection Request unsuccessfully
detected by the Node B or RRC
Connection Setup unsuccessfully
detected by the UE
CS call setup considered successful
when Alerting/Connect message is
received, while for PS call when
Activate PDP Context Accept
message is received
56

If RRC Connection Request not sent on optimal serving
cell check neighbor definitions and cell reselection
parameters
Typical reasons for access failures

are coverage issues, cell
reselection issues, missing
neighbors, pilot pollution issues,
power balance issues, HW issues,
external interference issues,
capacity issues, core network
issues, synchronization issues, UE
issues, logging issues, processing
issues..
57
Access Failure Example:

Poor radio conditions / High UL RTWP
Increased RTWP at Node B; If consistently reported, Node

B should be checked for UL interference and HW issues
Poor in-car radio conditions in Astoria park area. UE didnt

didnt receive respond on several RRC Connection
Request attempts although transmitting with maximum Tx
power
58

Cell reselection issues
Call setup started on on non-optimal serving cell UBQ04198C21

next to UBQ04947A site due to slow cell reselection. UE couldn't
receive ASU due to poor EcNo in downlink. Check signal
dominance and cell reselection parameters within the area.
59

Lack of signal dominance / Sudden
drop
Lack of dominant server and fast changes of radio conditions in

Broadway St area. EcNo deteriorated severely after UBQ06078B21
SC 321 remained the only cell in the AS. Check signal dominance,
pilot pollution and spillovers within the area. Add missing neighbor
between UBQ06078B21 SC 321 and UBQ06079A11 SC 337.
60

Core issues (MSC)
Call Release received by CS Core

network within excellent radio conditions.
Escalate observed issues if repeatedly
reported.
61

Core issues (SGSN)
Several consecutive PDP Context Rejects

logged due to insufficient resources.
Escalate observed issues if repeatedly
reported.
62

UE issues / Actix processing issues

Normal call setup falsely pegged by Actix due to delayed Radio Bearer
Setup Complete response from the UE (10s comparing to normal
response time of 20-30ms). Uu_wait_timer_Complete should be set to
0 to disable monitoring of radio bearer setup completion in Actix.
63

Tems logging issues (non-genuine failure)
Setup failure falsely pegged by Actix

due to missing Alerting message.
64

Drive test logging issues (non-genuine failure)
Call normally cleared before call setup was

completed at log file swapping.
65
Call Drop Analysis

Similar to access failures, typical reasons for
dropped calls are coverage issues, cell reselection
issues, missing neighbors, pilot pollution issues,
power balance issues, inter RNC handover issues,
HW issues, external interference issues, capacity
issues, core network issues, synchronization
issues, UE issues, logging issues, processing
issues..
66
Call Drop Analysis
Call Drop Example:

Missing neighbor
Call released after conn releaseConnOffset criterion was met
due to missing neighbor UBQ04199A11-UBQ04008C31.
Add missing neighbors.
67
Call Drop Analysis
Call Drop Example:

Poor coverage
Poor coverage area north of I-495 and west of 5th
St. UBQ04022B31 cannot get through due to terrain.
Check possibilities to improve coverage within the
area.
68
Call Drop Analysis
Call Drop Example:

Pilot spillover / Missing
neighbor
UBQ06087B21 SC 374 overshooting and missing neighbors in
in large area between UBQ04003B and UBQ04006A.
Reduce pilot spillover and add missing neighbors.
69
Call Drop Analysis
Call Drop Example:

Fast change of radio conditions / Sudden
drop
UBQ04848B21 signal level suddenly dropped due to shadowing;
UE couldn't update ASU due to bad quality in downlink.
70
Call Drop Analysis
Call Drop Example:

HW issues
UE received Release in downlink with 'Abnormal network'
cause within excellent radio conditions next to UBQ04198C
site. Serving cell was reported with alarms and outages.
71
Call Drop Analysis
Call Drop Example:

UE issues
Faulty UE lost
synchronization with
UTRAN several time
in a row while all other
UEs were reporting
steady good EcNo
72
Call Drop Analysis
Call Drop Example:

Data fill issues
RNC4 cell couldnt add RNC1 neighbor cell UNY01184B21 to the AS in

RNC4 serving area because of wrong external cell definition (UNY01184B21
external SC definition in RNC4 was set to 125 instead of 133.
73
IRAT Handover Optimization

Preparation
Missing IRAT neighbors are one of the major
causes of 3G-2G handover failures so thorough

check of IRAT neighbor definitions is recommended
Consistency of IRAT related UTRAN parameters
(IRAT handover support parameters, thresholds,
hystereses, timers) should be checked
UMTS network need to be well tuned otherwise
poor Ec/No would lead to frequent 3G-2G
handovers, long time spent in Compressed mode,
and/or 3G-2G handovers prevented by sudden
drops on UMTS
74

Common
Problems:
Missing
Neighbors
Missing IRAT
neighbors
problem particularily
affects areas lacking UMTS signal dominance so

UMTS pilot spillover should be minimized
GSM cells located at the end of UMTS network
coverage usually require 2nd tier UMTS cells
defined as neighbors
Balanced approach needed since long IRAT
neighbor lists reduce Compressed mode
measurement accuracy and increase probability for
targeting non-optimal neighbor cell
Prioritization of IRAT neighbors based on STS data
and drive tests is highly recommended to avoid
neighbor truncation
75

Common Problems: Missing Neighbors
In example shown nonoptimal GSM cell IL02503
instead IL02453 was
targeted due to missing
IRAT neighbors handover
attempt failed due to
inability to synchronize to
GSM.
76

Common
Problems:
IRAT Neighbor List
IRAT neighbors
get truncated if combined number
Truncation
of unique neighbors for cells included in Active set
exceeds 32
Same as for missing neighbor problem, IRAT
neighbor list truncation mainly affects areas lacking
UMTS signal dominance
Handover attempt will fail even if IRAT neighbor
gets truncated after e3a is sent UTRAN doesnt
have the mechanism to keep targeted GSM cell
from being truncated
Prioritization of IRAT neighbors based on STS data
and drive tests is essential for overcoming the
problem
77

In example
Common Problems:
shown
Truncation
handover
attempt failed
due to
truncation
e3a reported
handover target
cell IL15428
(129/20) got
truncated from
Measurement
Control list and
replaced with
129/22 after
active set was
updated with
two additional
cells.
IRAT Neighbor List
78

Common
Problems:
Wrong IRAT Parameter
Compressed
mode thresholds highly affect IRAT
Settings
handover performance set to high could lead to
frequent 3G-2G handovers, decreased 3G traffic
level and weaken HSDPA performance, while set to
low could increase 3G DCR and make IRAT
neighbor list hard to maintain
Separate sets of e2d thresholds introduced for
core and fringe cells with increased levels for the
latter should provide balanced approach however
fine tuning of thresholds in certain cases is
necessary
All other IRAT related parameters should be set
consistently to facilitate smooth 3G-2G transition
where is needed
79

Common Problems: Wrong IRAT Parameter
Settings
hoType parameter need to be
set carefully in IF network
border areas set to
IFHO_PREFERRED even for
one of the cells included in
Active set it prevents IRAT
handovers which is a problem
if no suitable IF handover
target exists within the area
80

Common Problems: BSIC Decoding Issues
Non-optimal GSM cell may be
targeted if UE failed to decode
BSIC of all measured cells.
BSIC decoding issues can be
caused by too long IRAT neighbor
list, poor GSM radio conditions or
insufficient time UE spent in
Compressed mode (as in example
shown).
Keeping IRAT neighbor lists at
optimal length and prioritized
should minimize BSIC decoding
issues.
81

Common Problems: SI Decoding Issues
PS mobile is obliged to decode
set of GSM System Information
messages before sending LA
Updating Request.
Time available for completing
handover procedure is limited by
T309 (8s by default).
SI decoding issues can be caused
by poor GSM radio conditions or
UE issues.
82

Common Problems: Poor UMTS Radio
Conditions
Poor UMTS radio conditions may prevent UE to enter

Compressed mode or start measuring GSM frequencies due to
inability to decode Physical Channel Reconfiguration or IRAT
Measurement Control messages.
In cases when UMTS radio signal drops suddenly (e.g.
tunnels) connection may be dropped even before UE reported
e2d which requires fine tuning of IRAT thresholds and/or
channel switching parameters as an interim solution. Long
term solution is improving UMTS coverage within the area.
83

Common
Problems: Physical Channel Failure
Handover attempts failed due to Physical Channel Failure and not caused
by any of previously described problems are caused by UE inability to
access GSM target cell due to poor GSM signal coverage/quality, wrong
BCCH/BSIC definition in UMTS or any other reason.
Physical channel failure may happen in quite few cases with no plausable
explanation, when subsequent handover command succeeds on the very
same target cell within couple of seconds (see example below).
84

Flowchart
1
Check if UE sent e2d measurement report
Check UMTS radio conditions at e2d sent
Check if UE decoded Physical Channel Reconfiguration and IRAT

Measurement Control messages and entered Compressed mode
Check if UE sent e3a measurement report
Check GSM radio conditions at e3a sent; Identify UMTS cells

included in Active set and check IRAT neighbor definitions
Check e3a for measured GSM cells; Identify cells included

in cellToReportList and cells UE failed to decode BSIC for
85
IRAT Troubleshooting Flowchart
Search for IRAT Measurement Control messages backwards

to resolve BCCH and BSIC of cells included in cellToReportList
Search for IRAT Measurement Control messages forward to determine any

change of interRAT CellId due to truncation or UMTS neighbor removal
Confirm BCCH/BSIC of targeted GSM cell from Handover command,

check its location and identify any missing neighbors
10
In case of PS handover attempt check if all

System Information messages are decoded
86
IRAT Handover Optimization Steps

1
Check if UE sent e2d measurement report
In case of missing e2d measurement report

check UMTS radio conditions and determine
if Compressed mode thresholds have been
set correctly
87

Details
Search for IRAT Measurement Control messages backwards
to resolve BCCH and BSIC of cells included in cellToReportList
Actix search
function used
Latest definition of reported

Measurement Control list position
should be located.
In example shown cellToReportList
cell IL15428 (129/20) was defined
at position 17 in IRAT Measurement
Control list.
88

Details
Actix search
function used
In example shown cellToReportList

cell IL15428 (129/20) got truncated
from Measurement Control list and
replaced with 129/22 after active
set was updated with two additional
cells. Handover attempted on
wrong target cell failed due to
Physical Channel Failure.
89

Details
Another possible reason
for targeted interRAT
CellId change is
removal of UMTS
neighbor from the Active
set.
In example shown
targeted interRAT
CellId 1 (169/16) was
replaced with (568/05)
after UMTS neighbor
counterpart ILU01767
(SC 30) was removed
from the Active set.
Handover attempted on
wrong target cell failed
due to Physical Channel
Failure.
90

Details
Confirm BCCH/BSIC of targeted GSM cell from Handover command;
Check targeted GSM cell location and identify any missing neighbors
BCCH/BSIC of targeted GSM
cell should match cell reported
in e3a, otherwise targeted
interRAT CellId has been
changed either due to
truncation or removed UMTS
neighbor.
In example shown 3G-2G
handover was attempted at
optimal 2G handover target cell
IL01232 (146/67).
91

Details In case of PS handover attempt check if all
10
System Information messages are decoded
PS mobile is obliged to
decode set of GSM System
Information messages (Type
1, Type 2, Type 2ter, Type 3,
Type 4 and Type 13) before
initiate LA Update. SI
decoding issues can be
caused by poor GSM radio
conditions or UE issues.
In example shown UE failed
to decode SI Type 13 before
T309 expiry.
92
93

Ph0+ Umts Pre-Launch RF Optimization Training: 14th May 2008

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ph0+ Umts Pre-Launch RF Optimization Training: 14th May 2008

Загружено:

Авторское право:

Доступные форматы

PH0+ UMTS

Confidential and Proprietary Information of T-Mobile USA

Pre-launch RF optimization process overview

Pre-launch RF Optimization Process

Confidential and Proprietary Information of T-Mobile USA

Pre-launch RF Optimization Process

Three rounds of RF optimization after spectrum

Confidential and Proprietary Information of T-Mobile USA

Unloaded/Loaded Cluster Launch KPIs

Confidential and Proprietary Information of T-Mobile USA

Market Launch KPIs

Confidential and Proprietary Information of T-Mobile USA

Cluster and Late Sites DT Setup

Confidential and Proprietary Information of T-Mobile USA

Confidential and Proprietary Information of T-Mobile USA

UMTS Network Integrity Validation

Confidential and Proprietary Information of T-Mobile USA

Drive Test Preparation Activities

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Every DT log file opened in TI and verified

Drive Test Log Files Validation

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Verify that scanned GSM ARFCNs

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

CPICH RSCP data are

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Verify CS voice RRC

Verify if CS voice was

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confirm that CS Long UE

Drive Test Log Files Validation

Confirm UMTS technology

CPICH RSCP data are

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confirm GSM technology

Confirm that GSM CS Short

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confirm that GSM CS Long

Confirm GSM technology

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confidential and Proprietary Information of T-Mobile USA

Drive Test Log Files Validation

Confidential and Proprietary Information of T-Mobile USA

DT Route Completion Verification

Check DT diary for any

DT Route Completion Verification

Confidential and Proprietary Information of T-Mobile USA

DT Route Completion Verification

Confidential and Proprietary Information of T-Mobile USA

Confidential and Proprietary Information of T-Mobile USA

Swap Sector and SC Consistency