EDGE+ TRE problem detection process

Thailand/BKK 10 May 2006

Problem overview

Symptoms of the problem Frequency hopping is activated Only TRAGE , TRADE, and TADHE in indoor or outdoor cabinet Poor RxQual (3-7) only on the odd timeslots although RxLev is good Why we use RMS and Type 5 to detect the problem? RMS can show the RxQual distribution per RxLevel in TRX basis without limitation of cells in the network

Drawback -> Cannot show difference among timeslot , odd vs. even

Type 5 counter shows Mean holding time of each TRX and each timeslot

Drawback -> Cannot activate for all cells at the same time (40 cells/BSC limited) -> In case the TRE faulty only at RxQual = 3-4, theres no difference among timeslot can be noticed.
All rights reserved 2002, Alcatel

TRAGE Problem description April 6th, 2006-Ed.5 Page 2

Problem detection overall process

This process is suitable when the objective is to find out the TREs those have this problem from a whole network in short time
First filter with RMS 1. Activate RMS feature for global network 2. Use RMSAT tool to convert PMRES file into Access database 3. Make a filter and copy the result table into excel sheet (see example filter in page 4) 4. Run macro excel to generate all the TREs in the list into excel files and gif files (e.g. if 500 TREs are detected, macro will generate 500 gif files and 500 excel files with graph) With the gif file, its now easy and fast to manual check by human to see whether its faulty or Interference problem. (see example graph in page 5)

Confirm again with Type 5 counter 5. After manual check, activate Type 5 counter for the cell/TRX in the list 6. Run Type 5 macro to convert raw counter into excel 7. Manual check again (see example graph in page 7)
TRAGE Problem description April 6th, 2006-Ed.5 Page 3
All rights reserved 2002, Alcatel

Problem detection by RMS (1/4)

Use RMSAT tool to detect poor RxQual from 3-7 depending on how much faulty they are.

Import PMRES31 of checked BSCs to the tool. Apply the filter condition to table TRX_RMS_samples in access database for filtering the problem TREs.
Filter Condition
("RMS4a0" divided by "RMS4a7" < 7.5) and ("RMS4a0" divided by "RMS4a1" > 6) and ("RMS4a7" divided by "RMS4a5" > 3.5) Or ("RMS4a0" dividedd by "RMS4a6" < 7.5) and ("RMS4a0" divided by "RMS4a1" > 6) and ("RMS4a4" divided by "RMS4a4" > 3.5) Or ("RMS4a0" divided by "RMS4a5" < 7.5) and ("RMS4a0" divided by "RMS4a1" > 6) and ("RMS4a4" divided by "RMS4a3" > 3.5) Or ("RMS4a0" divided by "RMS4a4" < 6.5) and ("RMS4a0" divided by "RMS4a1" > 6) and ("RMS4a4" divided by "RMS4a2" > 3.5) Or ("RMS4a0" divided by "RMS4a3" < 5.5) and ("RMS4a0" divided by "RMS4a1" > 6) and ("RMS4a3" divided by "RMS4a1" > 3.5)

TRAGE Problem description April 6th, 2006-Ed.5 Page 4

All rights reserved 2002, Alcatel

Problem detection by RMS (2/4)

Example of result from RMSAT tool for the faulty TRE

Rx Quality does not increase not as same as interference problem. . . It increases sharply from 2 to 4 and decreases sharply from 4 to 6 !!

TRAGE Problem description April 6th, 2006-Ed.5 Page 5

All rights reserved 2002, Alcatel

Problem detection by RMS (3/4)

Example of result from RMSAT tool for the normal TRE

Good RxLevel and RxQuality TRE

Bad RxQuality due to poor Rx Level TRE

TRAGE Problem description April 6th, 2006-Ed.5 Page 6
All rights reserved 2002, Alcatel

Problem detection by RMS (4/4)

A macro was created to generate RMS result to excels and pictures for easily manual check.

TRAGE Problem description April 6th, 2006-Ed.5 Page 7

All rights reserved 2002, Alcatel

Problem detection by Type5

Check Type 5 measurements to prioritize the critical of problem. A macro from PCS team was used to analysis of Type5 measurements
Low call duration in Odd TS

TRAGE Problem description April 6th, 2006-Ed.5 Page 8

All rights reserved 2002, Alcatel