data analysis

1. Created by Julio Velo 05/06/2006 Hands On Omega Tool
Data Analysis using
TEMS
and
Omega Tool

2. Created by Julio Velo 05/06/2006 Hands On Omega Tool
Introduction
1. The purpose of presentation is to explain how to use
Omega Tool, TEMS investigation and UETR for
tuning.
2. Different cases of drop call and access failure will be
discussed during the presentation

3. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASES
1. Drop Call – Voice
2. Drop Call – Missing ASU message
3. Drop Call – Drive Tester Error
4. Drop Call – PS / Pilot Pollution
5. Drop Call – IUR
6. Drop Call – IRAT
7. Missing Neighbour
8. Access Failure – N300, T300 expires

4. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 1: Drop Call - Voice
TEMS LOG: DA_CSPS_CL1_20060323_12.log (VOICE, MS2)
UETR: UTC: 24/3/2006 RECORDING DATA: FRBNTXMWRNC001
IMSI_FILTER=310410048871945
OMEGA EXPLANATION: Possible Interference at Problem area
SYMPTOMS:
 Low Ec/No before the drop
 Good RSCP
 Closer sector to Ue should be in the AS but is not. Sector
defined as a neighbour
DIAGNOSIS: Interference
REASON: Soft handover did not happen soon enough. Sector
DXU3013Z overshooting.

5. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 2: Drop Call – Missing ASU
message
TEMS LOG: DA_CSPS_CL1_20060323_17.log (VOICE, MS2)
UETR: UTC: 24/3/2006 RECORDING DATA: FRBNTXMWRNC001
IMSI_FILTER=310410048871945
OMEGA EXPLANATION: Missing Active Set Update Message;
Possible Interference
SYMPTOMS:
 Bad Ec/No
 Good RSCP
 Many e1a event sent but not ASU
DIAGNOSIS: Abnormal release most likely due to ASU timer
REASON: ASU Complete is not received. UETR said that RNC sent the
ASU message but Ue did not received it. Notice that e1d message
should not be sent, only one pilot on the Active Set.

6. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 3: Drop Call - Drive Tester Error
TEMS LOG: DA_CL12_CSPS_SOUTH_032306_07.FMT.log
OMEGA EXPLANATION: Possible Interference at Problem area
SYMPTOMS:
 Good RSCP (end of first log)
 Good Ec/Io (end of first log)
 Idle mode (beginning of second log)
DIAGNOSIS: problem with the log
REASON: Drive tester did not finish the call before closing the log
and began the next log with the Ue in idle mode

7. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 4: Drop Call – PS / Pilot Pollution
TEMS LOG: DA_CSPS_CL1_20060323_12.log (PACKET, MS4)
OMEGA EXPLANATION: Possible Interference at Problem area
SYMPTOMS:
 Bad Ec/Io
 Good RSCP
 Dedicated to Idle
DIAGNOSIS: Interference – Pilot Pollution.
REASON: the same problem than case 1. The dropped call
happened in the same area. It looks like Sector DXU3013Z
is overshooting.

8. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 5: IUR
TEMS LOG: DA_CSPS_CL1_20060323_17.log (PACKET, MS4)
OMEGA EXPLANATION: IUR
SYMPTOMS:
 Radio Bearer Reconfiguration – CELL FACH
 Cell Update
 RRC Connection Release
DIAGNOSIS: Not problem
REASON: IUR

9. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 6: IRAT
TEMS LOG: I20W_Forward -Drop before IRAT.log (VOICE, MS3)
SYMPTOMS:
 Bad RSCP
 Bad Ec/No
 Event e2d, e2f, e3a
DIAGNOSIS: IRAT problem
REASON: Event 3a generated, but quality is too bad, that IRAT did not
happened and Call dropped

10. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 7: Missing Neighbour
TEMS LOG: DA_CL12_CSPS_SOUTH_032306_10.log (VOICE, MS2)
OMEGA EXPLANATION: N/A
SYMPTOMS:
 Good RSCP
 Bad Ec/No
 Detected neighbour with better RSCP / Ec/No
DIAGNOSIS: A detected neighbour with better conditions than service cell
REASON: Neighbour relation DXU4211Z - DXU0286Z

11. Created by Julio Velo 05/06/2006 Hands On Omega Tool
CASE 8: Access Failure – N300, T300 expires
TEMS LOG: MA_C10_A2_20051125_11 access failure.log (VOICE, MS2)
OMEGA EXPLANATION: N/A
SYMPTOMS:
 Multiple retries
DIAGNOSIS: N300 expires.
REASON: The block call is reported after 5 retries