1 / 24

Hands On Omega Tool

Hands On Omega Tool. Introduction.

eshana
Download Presentation

Hands On Omega Tool

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hands On Omega Tool

  2. Introduction Omega Tool is used for post-processing the drive test logfiles from a cluster drive to obtain the KPIs from the drive and to extract meaningful data for analysis. The purpose of this presentation is to describe the functionalities available in the Omega Tool. Omega Tool supports drive test logs from TEMS investigation and Agilent.

  3. Index Omega Tool Installation Post Processing Overview Input data preparation Exporting Drive test logs from TEMS Exporting Drive test logs from Agilent Merging Files Setting Working Environment Performing Analysis Process Batch Report Combining UETR Files Defining Exclusion Zone Process Team Reference

  4. 1. Omega Tool Installation The first time, you will need to install the whole Omega installation package. The latest installation package is for version 5.1. (\\cingular_umts1\cingular umts\Tools\07_Omega Tool\Ver 5.1 Installer). First, run the registation.bat that is located in the PIA folder. If any error happens during the run of the batch file then stop the installation and please contact the process team. Second, run the setup.exe to install the tool. Be sure that Omega is installed in the default folder. Finally, update Omega to the latest available version. This process is explained in the next slide

  5. 1. Omega Tool Installation cont’ The latest available version at the moment of this presentation is Omega Tool 6.20. It is place in (\\cingular_umts1\cingular umts\Tools\07_Omega Tool\\Ver 6.20 DLLs and ReferenceFiles) Copy all the files and folders from the patch folder to C:\OmegaTool For future release repeat the same procedure unless something else is recommended in the release notes.

  6. TiW OSS Drivetest logfiles UETR logging (OSS) .txt .log Nexplorer Export Logfiles Convert UETR Text files .FMT Omega Tool Create database (merge FMT) Set Environment for Analysis Run Analysis / Run Batch Processing .txt .mif Wordpad, Excel, MapInfo output text files MapInfo analysis .mdb 2. Post Processing Overview Input Data Preparation (creating database) Export Drive test logfiles and UETR textiles Merge Files Set Omega Tool working Environment in main window Run Analysis / Batch processing Analyze output files / Import mif files in MapInfo for further analysis

  7. FMT export Template (.tex) file required Agilent export Template (.epf) file required 3. Input data preparation TEMS or Agilent logs for cluster drive collected. TEMS log files exported to FMT and agilent log exported to TXT Exported filesMerged database created (.mdb) Merge exported Files FMTCombined database created (.mdb) UETR files parsed with Nexplorer (.mdb file) Combine corresponding UETR files with Merged FMT files for Uplink measurements Optional Steps Final FMT merged or combined database created. (.mdb) MIF file with rectangular areas marked for exclusion Filter out the areas to be excluded from FMT Merged or combined database.

  8. 4. Exporting Drive test logs from TEMS Load the .tex Template provided with the tool - export_template_v6_revC.tex Do not select the merge file option in TEMS Open the exportation wizard on TEMS. You have to set the format as text file.

  9. 5. Exporting Drive test logs from Agilent Open the Agilent Drive Test file (*.sd5). The select Tools\Export Wizard… to open the export wizard.

  10. 5. Exporting Drive test logs from Agilent cont’ On this screen, click on select multiple sd5 files, to process several drive test logs. Select the Export plan (.epf). Then add the drive test logs files to be processed. Finally, press next to go to the next screen.

  11. 5. Exporting Drive test logs from Agilent cont’ Here you select the devices that you want to export. Notice that, due to limitation of Agilent, you can only export one Ue at the time. When you finish your selection, define Export to File(s)… A screen will appear showing the status of the exportation. The exportation will be done when this screen is closed. You will have to repeat this process for each Ue.

  12. 6. Merging Files Select the TYPE of log (TEMS or Agilent) For this example, we selected TEMS Select the folder where the files to be processed are located Highlight the files that you want to process Press this bottom if you want to process all the logs Select the name of the .omt files. This file will contain the information about the database that will be created from the logs. The first step when using Omega is to merge the drive test log files. Omega tools create several databases, at least one per Ue, and save all the data from the logs. Those databases, specified on the .omt file (target file) are the ones used to do the analyzes.

  13. 7. Setting Working Environment Select DL File: Browse and select the Merged OMT File (*.omt) to analyze. Select Combined File: use when combined UETR + Drive Test Logs are going to be analyzed Set Working Folder: select a folder where all output files will be created. (Note that same filename is generated when user run the same analysis, which will overwrite any previous output files. To avoid this, select a different folder for every analysis session) Purge All: Reset working environment set above; start analysis session for new cluster.

  14. 8. Setting Working Environment 8.1 KPI Analysis BLER Call Setup Success Rate / Time Dropped Call Rate IRAT KPI (not used) Packet Throughput CS/PS Level 2 KPI HSDPA Application-GNG (go – no go)

  15. Example Pilot Polution 8. Setting Working Environment 8.2 Scanner Scanner Data Evaluation Scanner Neighbours

  16. 8. Setting Working Environment 8.3 Statistics CPICH Ec / No Distribution (reported to Cingular) Carrier RSSI Distribution UL App Throughput Distribution Scanner CPICH Ec Distribution DL SIR Distribution Scanner CPICH Ec/Io Distribution DL App Throughput Distribution CPICH RSCP Distribution (reported to Cingular) Active Set Distribution UE TX Power Distribution Scanner Io Distribution Transport Channel Throughput Distribution UE CQI Distribution RBS Uplink SIR Distribution RBS TX Power for DCH Distribution RBS RTWP Distribution

  17. These plots are used in the Summary Report 8. Setting Working Environment 8.4 Plot Best Server Plot Downlink Application Throughput Plot UE TX Power Plot Uplink Application Throughput Plot (with UETR) Downlink DCH SIR Plot UE Carrier RSSI Plot Active Set Size Plot Uplink DCH SIR Plot RBS Downlink TX Code Power UE Event Data UE RLC and Transport Channel UE RF Data Application Level Data - UE on WCDMA (HSDPA) UE RF Data Plot (HSDPA) HS-DSCH Serving Cell Plot HSDPA Application Throughput Plot

  18. 9. Process Batch Batch processing of KPIs have been implemented to calculate several KPIs in one run. The batch processing form has the option to select the KPIs to be calculated and then it proceeds to the individual KPI input forms that were selected. The user can input the required parameters for each KPI.

  19. 10. Report The reporting tool is be used to generate two kind of reports. The first one is the Summary report that includes a summary of the KPIs for the cluster, CDF/PDF charts of different measurements and MapInfo plots. The second report is the GNG report based on the Cingular template.

  20. 11. Combining UETR files Select database from UETR Explorer Select database from UETR Explorer Select current .omt Select FMT files to be combined Set the date Define the time offset Finally, define the output file and press continue In order to include the measurements from UETR, the UETR files from the OSS need to be post processed using the UETR explorer tool. The UETR explorer will create an access database (.mdb) file with the requested messages and a GMT timestamp. This database is used as input to the combining process along with the OMT file created as explained in the previous section. The Combining input form requires the user to input a time offset that is Offset calculated as follows

  21. 12. Exclusion Zone The tool has a functionality to exclude data from these areas prior to KPI calculation. The areas are indicated through a MIF file and currently have to be rectangular areas. It has to be noted that excluding part of a call will automatically void the whole call or session as incomplete if the call ended as dropped one.

  22. 12. Exclusion Zone cont’ MIF file with the areas to be excluded. Use rectangles shapes only This screen shows the different rectangles defined in the MIF files Select the omt file where you want the areas to be excluded Select FMT merged or Combined if your omt file includes UETR data Set the MSs Define the new omt without exclusion zones

  23. 13. Process Team Julio Velo (julio.velo@ericcson.com) Bharat Reddy (bharatreddy15@yahoo.com) Priyanka Parekh (parekh.priyanka@gmail.com) Rajvi Bhatt (rajvi1@gmail.com) Maneesh Khare (maneeshkhare@yahoo.com)

  24. 14. Reference Installation package and DLL’s (Check for latest version): (\\Cingular_UMTS1\Cingular UMTS\Tools\07_Omega Tool\) User guide: \\Cingular_UMTS1\Cingular UMTS\Tools\07_Omega Tool\Omega Tool User Guide.doc A presentation about the tool is available at: \\Cingular_UMTS1\Cingular UMTS\Tools\07_Omega Tool\Steps to follow for Omega Tool.ppt Tool Specifications: \\Cingular_umts1\Cingular Umts\Tools\07_Omega Tool\Spec for Cingular UMTS Drive Test Data Analysis Tool.doc

More Related