Permanent observation report availability

Six levels of observation reports are available on request, according to the observation period:

• bts level

One observation report per cell is available on user request. The report contains the raw cell counters read by BSC applications and the associated synthetic counters.

A report containing the total number of raw and synthetic counters read in all cells of a BSS can also be requested.

• adjacentCellHandOver level

One observation report per neighbor cell is available on user request.

The report contains the raw neighbor cell counters read by BSC applications.

A report containing the total number of raw counters read in all neighbor cells of a BSS can also be requested.

• transceiverZone level

One observation report per zone is available on user request. The report contains the raw counters read by BSC applications related to the allocation of resources and intra-bts handovers in a concentric cell.

• bsc level

One observation report per BSC is available on user request. The report contains the raw and synthetic counters computed from the BSS cell, PCM and radio site raw counters.

• md level

One single md observation report is available on user request, that contains the raw counters read on the active OMC-R agent server.

• manager level

One single omc observation report is available on user request, that contains the raw counters read on the active OMC-R manager and connected workstation servers.

• transcoderUnit level

One observation report per TCU is available on user request. The report contains the raw TCU counters read by BSC applications and the associated synthetic counters. A report containing the total number of raw and synthetic counters read in all TCUs of a BSS can also be requested.

• TDMA level

The feature “PM1270 - TDMA based counters (15405)”, introduced in V16.0, provides TDMA based counters (for BSC 3000 only). These are in addition to having counters at the TDMA class (TransceiverZone) or cell level. The purpose of these TDMA-based counters is to give the operator a more precise view of the quality of the network.

The counters are produced on a multiple of <mdGranularityPeriod> minutes after the exact hour. The following apply:

• If an observation run is started at 13H 50 mn with a 15 minutes collection period, the counters are produced at 14H, 14H 15 mn, 14H 30 mn, etc.

• If an observation run is started at 14H 10 mn with a 30 minutes collection period, the counters are produced at 14H 30, 15H, 15H 30 mn, etc.

If the user changes the collection period, counting is not interrupted, but the time of the next reading is automatically reset to a multiple of

<mdGranularityPeriod> minutes after the exact hour.

The mdObservationDuration value is for each observation record the exact duration of the measurement;

The change may result in collecting the counters after an intermediate period different from the new defined period. The following - illustrated on the figure below - apply:

• If, for example, a 30 minutes period is changed to 5 minutes at 14H 37, counters will be next collected at 14H 40, then at 14H 45, 14H 50, 14H 55, and so on.

• Therefore, there will have two collections at 14H and 14H 30 with a 30 minutes gap, one collection at 14H 40 with a 10 minutes gap, and the following collections with a 5 minutes gap as required.

To complete network monitoring information, additional observation reports are available. They allow activity statistics to be evaluated at short (custom reports), medium (daily reports), and long (busiest day of the month reports) terms.

• custom observation reports (user-defined period)

A custom observation report is available on user request. It contains the totals or mean values (depending on the type of counter) of the measurements collected, on a given date and over a period of time ranging from zero to six hours, on all the permanent bsc, md, or manager observation counters.

The time band defines the number of observation message included in totals and mean value calculations (addition of collection periods).

The OMC-R manager supplies custom observation reports for the present day and the three previous days.

• daily observation reports (day period)

A daily observation report is available when the first of the next day’s messages is received (it is not available for the current day). It contains the totals or mean values (depending on the type of counter) of the measurements of all previous day’s permanent bsc, md, or manager observation counters.

The totals and mean value calculations start at 0h on D-day and are updated in real time as each new observation message is received the same day.

The OMC-R manager can at most supply daily observation reports for the last three days. The availability of the daily observation reports depends on purge configuration at manager level.

• busiest day of the month observation reports

An observation report on the busiest day of the month is the daily observation report generated on the day of the month during which the total values measured on a reference counter over a given reference period were the highest. The reference period can be in the range of 00 to 24 hours (it may be as follows: 08:00 - 19:00). The reference time and counter are statically configured (raw BSS counter, or active OMC-R agent or manager UNIX server counter).

The OMC-R manager supplies the busiest day of the month observation report for the current and previous months. The busiest day of the current month observation report is available as soon as the second day of the month is started and is updated each day until the first day of the following month.

1.12.2.4 Custom report and daily report counter processing