Abis Surfer 2.0.0 Tutorial

Abis Surfer 2.0.
0 Tutorial Release 1
Edixia TeIecom TechnoIogies
-
Abis Surfer 2.0.0 TutoriaI
November 12, 2002 Page 1 of 36
Abis Surfer 2.0.0 Tutorial Release 1
The purpose of this document is to give the user an overview of Abis Surfer in a
short time.
This is not a comprehensive training and therefore we will not go through all the
features/options but will run a typical work session to let you assess the power of
Abis Surfer.
Introduction
About Abis Surfer
Abis Surfer is a post-processing software for fast analysis of Ocean Abis traces.
Abis Surfer provides instant results for several types of analysis based mainly on the
processing of Abis Measurement ResuIt messages.
Abis analysis is used by GSM/DCS operators for radio network troubIeshooting
(detection of interference, hardware faults that cannot be reported by the OMC such
as a loose connector or damaged cable/combiner...) and optimisation (traffic
distribution, link balance, Power Control and Handover parameter tuning...).
1. Abis Surfer environment
Abis Surfer graphical user interface functions are all available in a single main
window.
The main menu gives access to all analysis functions and options.
The most common functions and options are also available through the tooIbar
and/or through contextuaI pop-up menus.
The main window is divided in 2 parts, the selection area (on the left) and the result
area (on the right).
SeIection Area (Object Selection & Neighbor Selection)
- The Object Selection graphical component displays the structure of the Abis
data currently loaded into memory. Data is presented in a hierarchical tree
structure including the following nodes: Abis measurement campaign (highest
node), Ocean Abis trace files, cells, TRX (lowest nodes).
Note: The information displayed may vary depending on availability of specific
Abis messages in the trace file and activation of the options "Use Timeslot
Names" and "Use Network Configuration info".
- The Neighbor Selection table displays the neighbors reported for the
TRX/Cell currently selected in the "Object Selection" tree.
Note: The information displayed may vary depending on availability of specific
Abis messages in the trace file and activation of the option "Use Network
Configuration info".
ResuIt Area
- Results tab (Result Table & Result Chart)
The Result Table displays the results of an analysis for the object currently
selected in the "Object Selection" tree (and the neighbor cell selected in the
"Neighbor Selection" table, if applicable).
The Result Chart displays the graphical results of an analysis for the object
currently selected in the "Object Selection" tree (and the neighbor cell
selected in the "Neighbor Selection" table, if applicable).
- Cell / TRX info tab
This tab displays the Cell/TRX information for the Cell or TRX currently
selected in the "Object Selection" tree.
- Neighbor info (Network Config. file) tab
When option "Use Network Configuration info" is active, this tab displays the
Cell/Neighbor information contained in the "Network Configuration File" for the
Cell or TRX currently selected in the "Object Selection" tree.
- Expert Report tab
This tab displays the results of automatic analysis from the "Expert Report"
feature.
- Warnings tab
This tab is activated when a warning message must be displayed.
Note: When you move the mouse cursor between the selection area and the result
area, it changes from an arrow to a splitter; you can then resize these areas by
clicking the left mouse button.
Similarly, you can also resize:
- "Object Selection" and "Neighbor Selection" areas
- "Result Table" and "Result Chart" areas in the Results tab
2. Loading data into Abis Surfer
v FiIe > Open (.eda, .edb, .edx)
This menu is used to process an Ocean Abis trace file (.eda, .edb, .edx) or a set of
Ocean Abis trace files.
You can process files up to 2 GB in size.
You can represent up to 512 TRX in the "Object Selection" tree.
Abis Surfer can process huge files very quickly: 1 GB of data is processed in Iess
than 6 min with a Pentium 3 - 1.1 GHz computer equipped with 256 MB of RAM.
In addition to this unmatched processing power, Abis Surfer provides an
Export/Import feature that allows the storage and transfer of small pre-processed
result files rather than the original large trace files.
v FiIe > Export / FiIe > Import (.abs)
Once a set of Ocean Abis trace files has been processed you can export all the
results in the compact format of a ResuIt FiIe (.abs), also simply referred to as an
export file. This file includes all possible pre-processed analysis results for all
exported files, including all modifications made in the "Object Selection" tree
(modified TRX power, deleted cells and TRX).
Result files may later be imported in Abis Surfer as if the originaI Abis trace fiIes
were effectiveIy re-processed. All modifications to the "Object Selection" tree
(modified TRX power, deleted TRX or cells) are maintained and do not need to be
re-created.
The process of importing result files is extremely fast (a few seconds or less).
The size of export files does not depend on the size of the original Abis trace files. It
only depends on the number of TRX in the original files.
Each TRX generates approximately 77 KB of data. For example, an Abis trace file
bearing 80 TRX generates a 6 MB export file.
Export files themselves usually compress very well, so that a 6 MB export file can
typically be "zipped" down to approximately 1 MB. This type of file is much easier to
handle than the original 1 GB trace!
Abis Surfer export files can be generated automatically on Ocean probes equipped
with the software. In practice, most users will only transfer and store these smaller
files, rather than the original traces.
3. Abis anaIysis
In this section we will go through major analysis provided by Abis Surfer.
Here are the naming conventions used to identify objects in the "Object Selection"
tree:
- A fiIe is simply identified by its name (ex. FiIe: Demo Trace FiIe 1.edb)
- A ceII is identified by the file it belongs to and its LAC and CI (ex. FiIe: Demo
Trace FiIe 2.edb - CeII: 10500/35451)
- A TRX is identified by the file and the cell it belongs to and its PCM number,
Timeslot number, Sub Timeslot number and TEI (ex. FiIe: Demo Trace FiIe 2.edb -
CeII: 10500/35451 - TRX: 1/2/0/0)
Import the result file Demo Export FiIe 1.abs (FiIe > Import).
This file is located in ..\Program Files\Abis Surfer 2.0.0\Sample Data (or your custom
Installation_Directory\Sample Data).
Note: Demo result files were created with real data from live networks. Network
identifiers (MCC, MNC, LAC, CI, Cell Names...) have been modified for
confidentiality reasons.
We will now review some of the most important analysis capabilities of Abis Surfer.
Measurement AvaiIabiIity
Short description
A "Measurement Result" message always includes uplink measurements (made by
the BTS). Downlink measurements (made by the MS) may be missing or incomplete
(only L1 information included i.e. MS Power and Timing Advance). While a message
is complete it may still be flagged invalid by the MS itself.
This information is summarised in the first 4 rows of the Measurement Availability
report; they are used to assess the quality of measurement reporting.
Note: All other Abis Surfer reports use only complete and valid measurement
messages.
The rest of the report includes statistics about extreme values. An extreme value
represents an open range (e.g. level -110 dBm represents any level below -110
dBm) and can lead to undesirable border effects. Abis Surfer allows the user to filter
out these results (Options > Filter Extreme Values).
Case Study
c Select the following object in the "Object Selection" tree
FiIe: Demo Trace FiIe 2.edb - CeII: 10500/35451
d Select GeneraI AnaIysis > Measurement AvaiIabiIity or right-click on the object
in the "Object Selection" tree to bring up a popup menu that contains commonly
used features and select "Measurement Availability"
Result Table
To go further
Display the same report for the following objects (individual TRX from the cell
described above) and note the differences between them.
FiIe: Demo Trace FiIe 2.edb - CeII: 10500/35451 - TRX: 1/2/0/0
Note: There is no need to re-call the feature when selecting a new object; results are
updated automatically by Abis Surfer upon selection change.
You may click on the new object to select it or use the navigation arrows on your
keyboard to browse through the tree structure.
Radio engineering hints and comments
You will generally notice that the percentage of DL Level greater than -47 dBm is
much more important for a BCCH TRX than for any other TRX of the same cell. This
is due to DL Power Control not being active on a BCCH TRX.
Abis Message Count
Short description
All Abis messages that are transmitted over the Abis interface are counted in this
report. This information is usually retrieved from the OMC at cell level; Abis Surfer
allows the user to split the results at TRX level or to aggregate them up to Campaign
level.
Case Study
FiIe: Demo Trace FiIe 1.edb
d Select GeneraI AnaIysis > Abis Message Count
Result Table
Result Chart
Note: Analysing the table and the chart at the same time is made easy using the
Marker feature (Select Options > Marker or right-click on the "Result Chart" to bring
up the Marker menu or use the button on the toolbar).
The table and the chart are fully synchronised (a new selection in the table updates
the marker position; moving the marker in the chart selects the corresponding row in
the table).
To go further
The "Result Table" can be exported to a comma delimited text file (*.csv) readable by
most spreadsheet tools.
e Select TabIe > Export or right-click on the "Result Table" to bring up the Export
menu
Using exported table data, you can complement Abis Surfer analysis with your
custom indicators and computations at any level (Campaign, File, Cell, and TRX) in a
simple spreadsheet application or other custom data presentation tool.
Radio Engineer hints and comments
Considering a cell with a high drop call rate, you can count, for each TRX, the
"CONNECTION FAILURE" and "ERROR INDICATION" messages to find the TRX
responsible for the drops (if any).
Result file (Export file) Demo Export FiIe 1.abs is already loaded; it contains Ocean
trace files "Demo Trace File 1.edb" and "Demo Trace File 2.edb".
Import the second result file Demo Export FiIe 2.abs (FiIe > Import). It contains
Ocean trace files "Demo Trace File 3.edb", "Demo Trace File 4.edx" and "Demo
Trace File 5.edb".
DownIink LeveI Distribution
Short description
This analysis provides a statistical distribution of the RxLev samples.
Case Study
FiIe: Demo Trace FiIe 4.edx - CeII: 10600/45301
d Select GeneraI AnaIysis > DownIink LeveI Distribution
Result Table
Result Chart
To go further
Analyse this distribution for the 3 TRX of that cell. You will notice a substantial
difference between them.
TRX: 1/5/0/1 RXLev DL (Avg.) = -75.8 dBm
A greater RxLev average value for the BCCH TRX is normal because there is no DL
Power Control on that TRX.
What about the 2 non-BCCH TRX?
To push the analysis a little further, we can cancel the effect of Power Control in the
resulting data using "DL Level Distribution, PC compensated" instead of "DL Level
Distribution" (GeneraI AnaIysis > DownIink LeveI Distribution, PC compensated).
It shows the following results:
TRX 1/5/0/0 behaves abnormally. We will come back to this TRX later on.
To close this topic, you can run these 2 analyses ("DL Level Distribution, PC
compensated" and "DL Level Distribution") on a cell that works properly (e.g. FiIe:
Demo Trace FiIe 2.edb - CeII: 10500/35451).
"DL LeveI Distribution" represents the system behaviour (as perceived by the end
users).
"DL LeveI Distribution, PC compensated" represents the radio propagation
behaviour (the level that would be received without Power Control, as computed by
e.g. a radio-planning tool, or as received by a mobile in idle mode).
DownIink QuaIity Distribution
Short description
This analysis provides a statistical distribution of the RxQual samples.
Case Study
d Select GeneraI AnaIysis > DownIink QuaIity Distribution
Result Table
Result Chart
This analysis provides an easy way to assess TRX quality. This TRX has a
significant number of bad quality samples compared to the BCCH TRX of the cell
(TRX: 1/3/0/2).
TRX: 1/3/0/3 RXQual DL (Avg.) = 0.8
TRX: 1/3/0/2 RXQual DL (Avg.) = 0.2
To go further
The next report (Downlink Interference) will allow us to analyse more precisely the
reasons of this bad quality (lack of coverage, interference...).
Although most of the operators use arithmetic averaging for RxQual values, some
of them prefer to use a Iog averaging which is more consistent with the distribution
of BER ranges.
You can choose the averaging method for RxQual values by enabling/disabling the
"Use RxQual LOG Averaging" option (Options > Use RxQuaI LOG Averaging).
You do not need to re-process the original Abis trace to obtain the results of the new
averaging process, both arithmetic and log averaging results are always available
and saved in the export files.
Note that the use of one averaging method or the other is not necessarily critical in a
global optimisation approach: the method of averaging will impact many analysis in
their absolute results but less so in their relative results. However it is criticaI to
stick to the same averaging method throughout the compIete optimisation
process.
DownIink Sensitivity/Interference (1)
Short description
This analysis provides a bi-dimensional view of quality vs. level, and a statistical
distribution of the samples.
Interference may be identified in the results as peaks of bad quality (higher RxQual)
at relatively high levels.
Case Study
d Select GeneraI AnaIysis > DownIink Sensitivity/Interference
Result Table
Result Chart
This is a typical case of interference (peaks of bad quality at relatively high levels).
Select the BCCH TRX (TRX: 1/3/0/2) to view the same curve for an interference free
TRX.
To go further
Select the following object in the "Object Selection" tree
Here is another case of interference.
This cell has a lot of samples bearing an RxLev greater than -47 dBm (23.8 % - see
Measurement Availability report). It is interesting to filter out these extreme values in
order to analyse this curve more precisely:
Select Options > FiIter Extreme VaIues or use the button on the toolbar.
Note that, as a rule of a thumb, most analysis combining 2 or more measurements
(sensitivity/interference, path balance and link balance, etc.) should always be run
with option Filter Extreme Values active, to avoid undesirable border effects.
Use the statistical distribution of the samples (blue bars) to evaluate if the computed
value is statisticaIIy representative.
DownIink Sensitivity/Interference (2)
Short description
This analysis provides a bi-dimensional view of quality vs. level, and a statistical
distribution of the samples.
In an interference-free trace, the sensitivity corresponds to the minimum receive
level for which the quality is better than 4 (BER<2%), as defined in GSM
specifications.
Case Study
FiIe: Demo Trace FiIe 1.edb
d Select GeneraI AnaIysis > DownIink Sensitivity/Interference
Result Table
Result Chart
Note: Extreme values filtering disabled.
The selected file contains only DCS cells, we can use this curve to measure the
average sensitivity of DCS mobiIes (minimum receive level for which the quality is
better than 4): in this example ~ -102 dBm.
Note: The ability of Abis Surfer to aggregate results at any level makes it easy to
obtain statistically representative results for such analysis.
To go further
Select a GSM cell (for instance FiIe: Demo Trace FiIe 2.edb - CeII: 10500/35450)
and note that the average sensitivity of GSM mobiIes is better than specified in the
GSM recommendation: ~ -104 dBm.
Remember that sensitivity measurement is significant on interference free cells only.
Be careful when aggregating results:
For this analysis, make sure that all cells under the selected object are in the same
frequency band.
For the corresponding uplink measurement (BTS sensitivity), make sure that all cells
under the selected object bear the same equipment configuration.
When tuning your network (e.g. balancing links to compute the optimum transmit
power) you can make the best use of your equipment by referring to measured
values whenever possible (in this example, using -104 dBm for GSM MS sensitivity
instead of -102 dBm as specified by ETSI).
Timing Advance Distribution
Short description
This analysis provides a statistical distribution of the Timing Advance samples.
This represents the spatial distribution of traffic around the cell antenna, in GSM TA
steps (1 TA step ~ 500m).
Case Study
d Select SpatiaI AnaIysis > Timing Advance Distribution
Result Table
Result Chart
The results show that approximately 3% of the cell traffic takes place in a coverage
splash 9 km away from the site. Further investigation is needed to determine the
reason: system tuning (manufacturer dependant), antenna tilt, particular
geographical situation...
To go further
Average RxLev / RxQual values for the coverage splash may be used to get an idea
of its influence on the cell quality.
e Select SpatiaI AnaIysis > DownIink / UpIink QuaIity vs. Timing Advance
SpatiaI AnaIysis > DownIink / UpIink LeveI vs. Timing Advance
RXQual DL (Avg.) = 0.1
RXQual UL (Avg.) = 0.0
RXLev DL (Avg.) = -88.6 dBm
RXLev UL (Avg.) = -97.4 dBm
This coverage splash has no negative impact on cell quality.
Have a look at the Timing Advance distribution for the following object:
There is almost no traffic close to the cell (Timing Advance 0). Again, many reasons
can explain this "unusual" behaviour and local knowledge of the system configuration
(e.g. handover algorithms), the hardware, and the network... is needed to evaluate if
something needs to be changed, and if so, how to do it.
Traffic distribution is often used when deploying new sites for capacity reasons. It
helps radio engineers in detecting traffic hot spots.
Link BaIance Distribution
Short description
This analysis provides a statistical distribution of the delta between downlink and
uplink level, with correction of the Power Control effect.
For the Iinks to be properIy baIanced, the DL-UL IeveI deIta must match the
deIta in sensitivity between the MS and the BTS.
MS Receive Level - BTS Receive Level = MS Sensitivity - BTS Sensitivity
The following formulas are used to calculate the link balance:
For a 1800 MHz cell, a 1W mobile is assumed:
Link Balance = (RxLevDL + 2 * BSPower) - (RxLevUL + 2 * MSPower)
Link Balance = (RxLevDL + 2 * BSPower) - (RxLevUL + 2 * (MSPower-5))
Case Study
d Select BaIance AnaIysis > Link BaIance > Distribution
Result Table
Result Chart
The measured average sensitivity of DCS MS is -102 dBm.
The BTS sensitivity is equal or better than -110 dBm (see Uplink
Sensitivity/Interference report). As -110 dBm is open range, we cannot use
measured values; we are forced to refer to the value provided by the manufacturer
which is -110 dBm in our case.
For the link to be properly balanced the measured Link Balance must be 8 dB; this is
exactly the value we measure in this example.
An unbalanced link can seriously affect handover efficiency and triggering points.
If the Link BaIance is too high, reduce BTS power accordingly.
If the Link BaIance is too Iow, increase BTS power accordingly if possible, or limit
MS maximum transmit power otherwise.
Also bear in mind, before modifying settings as described above, that a hardware
problem can be the cause of an unbalanced link (ex. TMA out of order). See "Path
Balance" report in the next section to find out more about detecting hardware
problems.
Finally, extreme level values may distort Link Balance analysis results; use the "Filter
Extreme Values" option to get rid of these border effects (the same applies to Path
Balance analysis).
Path BaIance Distribution
Short description
This analysis provides a statistical distribution of the delta between downlink path
loss and uplink path loss.
The analysis shows differences in the uplink and downlink path losses. UnIess the
resuIts correspond to weII identified eIements such as TRX combiners or
differences in antenna gains, etc. they point to system maIfunctioning or
tuning probIems.
Path balance analysis is very similar to Link Balance Analysis, except that the MS
and TRX powers are taken into account.
TRX absolute power is not an information contained in Abis messages. It must be
correctly defined by the user for the analysis to be valid (use one of these
commands: TRX > Set Power, CeII > Set Power or FiIe > Set Power).
The following formulas are used to calculate the path loss balance:
Path Balance = PTRX - 2 * BSPower - RxLevDL - 30 + 2 * MSPower + RxLevUL
Path Balance = PTRX - 2 * BSPower - RxLevDL - 43 + 2 * MSPower + RxLevUL
Case Study
FiIe: Demo Trace FiIe 4.edx - CeII: 10600/45301
d Select CeII > Set Power or use the contextual pop-up menu to set the cell power
to 44 dBm (actual transmit power).
e Select BaIance AnaIysis > Path BaIance > Distribution
Result Table
Result Chart
Note: option "Filter Extreme Values" is active.
On this site the differences between the DL Path and the UL Path are:
- Combiner loss in the DL Path: 5.2 dB (manufacturer value)
- Diversity gain in the UL Path: 3 dB (assumed)
The Path Balance should be approximately 8 dB; this is confirmed by the average
value that we can read from the result table. However, the distribution shows a
"bump" on the right part of the curve.
Let us check the Path Balance value for each TRX:
TRX: 1/5/0/1 6.3 dB (acceptable)
TRX: 1/5/0/0 32.2 dB
TRX: 1/5/0/2 6.6 dB (acceptable)
The Path BaIance is too high: either the DL path loss too high, or the UL path loss
is too low (but it is unlikely that an extra gain would appear in the uplink path).
Consequently:
v The actual TRX power is much lower than the power set by the user: TRX is
damaged, or
v there is abnormal loss in the DL Path: combiner, transmit cabIe... is damaged
In the latter case it is likely that all TRX would be affected!
In this example, a BTS check on site revealed that the power amplifier of the
incriminated TRX had a gain 25 dB lower than expected ... without any alarm
reporting to the OMC!
To go further
More frequently we find a Path Balance that is too low.
Path BaIance too Iow points to UL path loss being too high (or DL path loss being
too low, but it is unlikely that an extra gain would appear in the downlink path).
Abnormal loss in the UL Path indicates that a TMA, reception feeder cabIe,
receiver muIticoupIer... is damaged
Note that such a hardware fault affects Link Balance too. So, before deciding to
modify BTS/MS power settings based on Link Balance analysis, always check that
your hardware is OK using Path Balance analysis.
However you may also temporarily adjust the power to reduce the impact of
hardware faults (e.g. lowering the BTS power in case of TMA out of order).
TCH Traffic Distribution per TimesIot
Short description
This analysis provides the number of Abis Measurement Result messages
specifically related to TCH traffic (SDCCH traffic excluded), per Timeslot.
Case Study
d Select Traffic AnaIysis > TCH Traffic Distribution per TimesIot
Result Table
Result Chart
The results depend on the manufacturers channel allocation strategy. This allocation
algorithm must be known to analyse this report properly.
To go further
Select the "Cell / TRX info" tab to determine the timeslots that cannot have TCH
traffic (logical channel other than TCH).
Network Configuration FiIe
Before moving forward with more Abis Surfer analysis, lets have a look at the
"Network Configuration FiIe" option.
Although Abis Surfer presents a cell using its Cell Identity (when sufficient
information is available in the trace file), it is much more convenient for an operator
to use ceII names, especially when the analysis involves cell neighbors. Abis Surfer
provides the "Network Configuration File" option to suit this purpose.
An Abis Surfer configuration file named Demo Configuration FiIe.txt is located in
..\Abis Surfer 2.0.0\Sample Data (or your custom Installation_Directory\Sample
Data).
It is a simple text file that you can open using any text editor (WordPad, Notepad...).
The file format is quite simple:
- A line starting with a ! is ignored (comment line)
- A cell and its neighbors is defined in a single line with the following semicolon
separated fields:
"ServingLAC;ServingCI;ServingName"
+ n times
"NeighborLAC;NeighborCI;NeighborName;NeighborBCCH;NeighborBSIC"
Note: You can define up to 5000 cells with 32 neighbors per cell.
c Open the sample configuration file using Options > Network Configuration FiIe
d Select the "Use Network Configuration info" option (Options > Use Network
Configuration info, or use the button on the toolbar)
All cells defined in the configuration file are presented in the "Object Selection" tree
using their names (see cells in "Demo Trace File 1.edb" and "Demo Trace File
2.edb"). Cells that are not defined in the configuration file are presented in the
classical way using their LAC and CI preceded by a question mark (?) indicating that
the cell could not be found in the file (see cells in "Demo Trace File 3.edb", "Demo
Trace File 4.edx" and "Demo Trace File 5.edb").
An similar principle applies for neighbor cells; Abis surfer shows as much information
as possible.
When a Cell or TRX is selected, we can visualise the related configuration
information in the "Neighbor info (Network Config. fiIe)" tab.
Note: Defining neighbors in the configuration file is optional. If you are not interested
in neighbor analysis you can put together a configuration file supplying only
"ServingLAC;ServingCI;ServingName" for each cell.
Neighbor RxLev
Short description
This analysis provides the average RxLev of all neighbors as well as the number of
reports including this neighbor (count).
Case Study
FiIe: Demo Trace FiIe 1.edb - CeII: BOND-STEET-D (LAC:10500/CI:65011)
d Select Neighbor AnaIysis > Neighbor RxLev, sorted by count
Result Table
Result Chart
Note: option "Filter Extreme Values" is not active.
To go further
Display the same report for the following object:
FiIe: Demo Trace FiIe 2.edb - CeII: BAKER-STREET-G-2 (LAC:10500/CI:35452)
Channel 80 is included in the BAKER-STREET-G2 BA list (this is the list of BCCH
frequencies that the MS will monitor and report for handover purposes) - see Cell /
TRX info tab
BANK-G-0 (LAC:10500/CI:10133/BCCH:80/BSIC:21) cell is defined as a neighbor of
BAKER-STREET-G2 - see Neighbor info (Network Config. file) tab
BCCH:80/BSIC:21 (BANK-G-0) is reported 11 018 times (RxLev Avg. = -88.0 dBm)
BCCH:80/BSIC:20 (This is not a defined neighbor) is reported 68 527 times (RxLev
Avg. = -91.2 dBm)
This is an abnormal situation and we should check the following points:
- Are BCCH frequencies properly defined?
- Should we add BCCH:80/BSIC:20 to BAKER-STREET-G2 neighbor list?
- Should we remove BANK-G-0 from BAKER-STREET-G2 neighbor list?
How does neighbor reporting work?
The MS measures the neighbor signal strength received on the BCCH carriers of its
neighbor cells (from the MS point of view, neighbors are simply defined by the BA
Iist = a list of frequencies).
For the 6 strongest neighbor cells, the MS reports periodically to the BTS:
v the signaI strength,
v the BA Index (the position, starting with 0, of BCCH carrier in the BA list), and
v the BSIC.
Example:
BA List: 10, 15, 20, 25, 30, 35, 40
A measurement on BCCH carrier 30 is reported as: 4 (BA Index) / BSIC / LeveI
How does Abis Surfer use neighbor information?
If BCCH Allocation may be decoded from the trace (if BCCH INFORMATION and
SACCH FILLING messages are sent on a regular basis on the Abis interface this is
manufacturer dependant), this information is used to assign a BCCH to each BA
Index.
If BCCH Allocation is not decoded from the trace AND network configuration
information is available from Network Configuration file, the BA list is built using
network configuration information and a BCCH is assigned to each BA Index.
Otherwise, no BCCH can be allocated to the BA indices and the BCCH information
remains empty.
Note: In case the BA list information is available both from the trace and the Network
Configuration file, you can check that they are consistent using the Expert Report
(see related section).
Server-Neighbor DeIta LeveI distribution
Short description
This analysis provides a statistical distribution of the delta between the serving ceII
RxLev (Power ControI compensated) and the neighbor ceII RxLev.
Case Study
FiIe: Demo Trace FiIe 2.edb - CeII: BAKER-STREET-G-2 (LAC:10500/CI:35452)
d Select CeII: BAKER-STREET-G-0 in the "Neighbor Selection" table
Note: When a "Neighbor RxLev" report is displayed, the "Result Table" and the
"Neighbor Selection" table are synchronised. A neighbor cell can thus easily be
selected directly from the "Result Table".
e Select Neighbor AnaIysis > Server-Neighbor DeIta LeveI distribution
Result Table
Result Chart
This example shows a typical distribution of the delta in level for 2 umbrella cells
where the main handover cause is power budget.
Knowing that the cell power budget handover margin is 6 dB, we see that there are
still some samples reported with Delta Level < -6 dB (to the left of the blue marker
line). This comes from the moving average window mechanism (the HO is not
triggered on a single measurement but on the average of n measurements).
Changing the margin from 6 dB to 0 dB would force the part of traffic charted
between the blue marker line and the red zero line to move from the serving cell to
the neighbor cell (roughly 6%).
To go further
Display the same report for cell FiIe: Demo Trace FiIe 1.edb - CeII: BOND-
STREET-D (LAC:10500/CI:65011) and neighbor CHARING-CROSS-G-1
(LAC:10500/CI:36201).
Here, approximately 50% of the traffic handled by the serving cell has a level that is
lower than the neighbor cell. This type of behaviour is typical of specific handover
algorithms between a serving micro cell and a neighbor umbrella cell, where the slow
moving traffic if forced onto the micro cell.
This analysis can assist the operator in many of its common tasks: Handover margin
tuning, Handover threshold tuning (ex. Directed Retry, Concentric Cell...), hot spot
simulation...
A good knowledge of the handover mechanisms and algorithms (which are
manufacturer dependant) is necessary to analyse this distribution properly.
4. The Expert Report
The Expert Report allows the user to partly automate Abis Trace analysis. Here is a
simple example concerning Frequency Configuration; other types of analysis work
exactly the same way.
Configuration
c Select Expert Report > Configure
First select analysis categories you want to include in the report (Detection of
Problem Cells & TRX, Alarms, TCH Traffic Analysis, Frequency Configuration
Checks).
For each of the selected category, choose the specific analyses that you want
included in the report from the specific category tab.
ResuIts
d Select Expert Report > Run
The selected analyses are performed and the result is displayed in the Expert Report
tab.
Here is a short overview for each type of expert (automatic) analysis available:
v Detection of ProbIem CeIIs & TRX
A Cell or TRX is reported if the deviations from the Campaign or Cell average exceed
the defined thresholds.
v AIarms
Absolute triggers are defined for these analyses.
v TCH Traffic AnaIysis
As for "Detection of Problem Cells & TRX" analyses, relative triggers are used. For
example a TRX is reported idle if the deviation from cell average exceeds the defined
threshold.
v Frequency Configuration Checks
When both decoded and user defined (configuration file) information are available,
run this check to ensure that both data sources are consistent.

Abis Surfer 2.0.0 Tutorial

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Abis Surfer 2.0.0 Tutorial

Enviado por

Direitos autorais:

Formatos disponíveis

Abis Surfer 2.0.

Você também pode gostar