telecom hall hunter definition en-us 110523

Using Tools for getting Best Results in Telecom Networks

Hunter Methodology

Objective

• Presenting an Overview of how to work better with any cellular network.– Regardless of the technology, the use of appropriate tools

and procedures result in greater productivity.• In general, involving all activities, since Planning, Design,

Optimization, Maintenance & Operation, among others.

• Although there is no general rule to follow, the suggestions presented here can be exploited by any professional, or even by students and enthusiasts of the area.

Friday, April 7, 2023 telecomHall.com 2

What should be observed?

• Every wireless network has one thing in common: they have a huge amount of elements, and they must be continuously observed.– Any fault in any of these elements, results in degradation

of quality, and consequently affects customers.


But how?

• In addition to the procedures, an important way to achieve best results is using all possible and available tools.– In this case, the development of customized tools becomes

a key differentiator, with the possibility to achieve amazing results.


• Developing Custom Tools is very common: almost everyone has made a 'macro' using Microsoft© Excel©.

Tools

• It is common to use Vendor’s Proprietary Tools, purchased for certain purposes, as well as Systems/Tools developed by Operators.

• However, 'local‘users can go further and develop their own local tools.– The most important thing is that they do follow

some criteria, such as integrating with the existing tools, aiming only at what isn’t available for use. In other words, avoid reworking.


Hunter

• In this line of 'home‘ tools , we present a complete methodology, which ultimately ends up being not as homely as well.– We prefer to understand as a set of suggestions to be followed,

including standardization and also tools to enable a better work and efficiency of each professional.


ESULTSENHANCEDOOL FORETWORKSEROME

Modules

• Commercials Tools generally follow one important rule: modularization. This allows the use of parts of the system (modules), or the complete system (all modules).– This feature also allows for scalability, or you can go to evolve over

time, always adding new modules to adapt to changing.

• And in Hunter Methodology it is not different.– Although Hunter is not specifically a tool, it has focus on standardized

modules.– The goal is to allow any professional to create new modules, according

to the availability of software & applications, and their specific needs.• The Hunter is a Methodology and its standardization is free, as

well as the creativity of each one to create and / or extend their own modules.


Hunter Modules

• Following it’s free customization structure, Hunter allows the development of a very large number of modules.


Others

Drive Test GIS

HUNTER

OSS’s

KPI

Parameters

Others

Physical

• Speaking of all of them would be virtually impossible.

• At center figure, we see some of the standardized modules.

• Following, we give examples of them.

Software Used

• But before speaking of some modules, which software can be used to create Hunter Modules?

• All that we have available and licensed for use!– In particular, the Microsoft Office© Suite, especially

Microsoft Access©, and VBA programming language - the same one used to write macros in Microsoft Excel©.

– And other complementary Software.• Especially the one for geo-referenced analysis , as

MapInfo©, from Pitney Bowes Business Insight © and Google Earth©, from Google©.


Structure

• The Hunter Methodology has its structure and standard pre-defined, facilitating the integration of different modules, by the definition of it’s default directories.


• The first, and main directory is 'C:\Hunter '.

• From this directory, we create all the modules - the name of each directory is the name of the module.

• Each module, in turn, follows a standard nomenclature for its subdirectories, organizing the data. For example, the ‘database’ directory contains an ‘.mdb’ file to store the tables and all code from this module.

• A major advantage of following a standardized structure like this, is that any module can access information from all others. For example, a macro can access the data from Network module (network physical data) and add to the information on KPI module, plotting indicators in Mapinfo and / or Google Earth.

Hunter Network

• Now we can speak of some modules, to exemplify.– One of the most important, of course, is the module that contains the

information of the physical data network, such as latitude, longitude, antennas, azimuth, etc ...


Network_DB

• This module is very important, but it is quite simple. Basically, it gathers all the tables with information from physical data network.• Thereafter, the data is accessed by other modules.

Hunter Parameters

• The aim of the Parameters module is to gather all information from the network configuration parameters in a single database.– From this database, we can create several other useful modules. For

example Hunter Audit (audit of the network configuration) and Hunter Journal (check what parameters have changed in the network).


• Brief Summary: raw files of the OSS's: dump configuration parameters - (txt, csv, xls, etc. ..) are downloaded, for example via FTP or client.• They are then processed (macro)

and stored in a database.

Parameters_DB

Hunter KPI

• Just as the Parameters, the KPI module gathers information in a database. This time, stores the key Performance Indicators, such as Call Drop Rate Falls, Overflows, Traffic and Handover.– From this module we have others: Hunter KPI Reports (generating

automated reports), Hunter Chart and KPI Dashboard (related to analysis through graphs), etc.


• Brief Summary: raw files of the OSS's with counters (txt, csv, xls, etc. ..) are downloaded, for example via FTP or client.• They are then processed (macro)

and stored in a database. KPI_DB

Key Databases

• The three modules presented were some of the Hunter Key Databases. That's because with the Information of Network (physical data, azimuths ...), Performance KPI (drops, traffic ...) and information on Configuration Parameters, we already have enough information to various types of analysis.– Note: we do not attempt here to delve for example in the VBA code,

scripts, algorithms, and analysis reports available or even the standardization process.

• We intend only to demonstrate how custom tools can be used, and bring great benefits to our work.

• Besides the key modules, several modules may and has been developed for various other applications.– We will see below some of these additional modules.


Hunter GE Drive Test

• Google Earth© is undoubtedly the best browser for existing geo-referenced data. The file format that it reads is KML that can be created for example by using VBA with our existing data.– Based on this, we have modules like GE Hunter

Drive Test.• Module Summary: From any Drive Test software , we can

export the collected data to a plain text format.Running a macro, we have several types of possible analysis.


Hunter GE (...)

• Also in relation to Google Earth , several other modules can be created, like the Hunter GE Network (plotting information from Network_DB) and also the Hunter GE KPI (plotting information from Network_DB – eg azimuth – with KPI_DB), as seen below.


• Clicking on a cell, we quickly access it’s information, such as antenna and Tilt!

• Easily identify the sectors with problems!

Hunter Update

• An interesting module, and also quite useful, is the Update module.

• The information of key modules can be exported - via macros - for several specific formats of various other software and databases and tools.

• For example, we can update all data Prediction Tools, Frequency Planning, Archives of Cells to Drive Tests, etc.

– This ensures our data is always updated, and automated.


Hunter Operators

• As an example of auxiliary modules, we have for example the Operators: gather information from all carriers in one place.– This information can be used for

example to identify opportunities for site sharing (antennas).


Hunter Network (Sites)

• Another use of Auxiliary modules are for example to help some very specific task, like this one, used to improve procedures of Folder Structure for Telecom Documents.– For example, the methodology Hunter standardizes

the Directory Structure, Organizing Files and all documents (designs, photos, etc ...)

• We can create a simple interface to facilitate the search for data.


Other Modules

• We presented just a few suggestions of modules according to the Hunter Methodology.

• However, the amount of existing and possible modules is much more!– Consequently, very hard to show everything here.

• Also, it was just an introduction for some modules.– Each has a number of peculiarities and tricks, as the best

procedures for each task.

• The idea is to allow each professional to use their skills, and be able to create a complete system as shown.


IMPORTANT

• Hunter Methodology is not intended to replace any tool or existing database.

• Rather, it should be used as a complement to all the facilities that are not available to the professional.

• Its use however, naturally leads to better results.– Examples: automation through macros, faster execution of tasks,

better reporting, data up to date, organization, etc...

• All this will contribute to improving the network overall performance.


Conclusion

• This was a brief introduction to the methodology Hunter, a set of customized tools and concepts, with the goal of helping professionals in IT and Telecom (and even other areas where the concept can be applied) to achieve greater productivity and efficiency in their daily work!
