Sector Busy Hour

Requirements from customer to have Sector Busy Hour calculation.

Using the following small example, where we have the LTE Cells which belong to the same eNodeB “JHRTJML”

In order, to calculate the Sector Busy Hour, we will use the busy hour determiner (from Cell resource type), "RRC User". Where "RRC User" is a metric with counter type as "Intensity".

Using Sector 3 as an example, the table below, shows the example aggregation calculations, for 8 measurement intervals:

The Hourly Summary for Sector 3 (JHRTJML_Sector3), will then be calculated as below:

1:00AM (a1 + a2 + b1 + b2 + c1 + c2 + d1 + d2) / 4

2:00AM (e1 + e2 + f1 + f2 + g1 + g2 + h1 + h2) / 4

....

Busy Hour for Sector 3 (JHRTJML_Sector3) will be the hour segment which has the largest value within the 24 data points.

The Sector’s Busy Hour, need to be tagged to the “child” cell (i.e. JHRTJML_103, JHRTJML_3) so that we can report on the corresponding Sector BH values for the selected Cell metrics (e.g. BH Throughput, BH DL Volume).

e.g. Assuming that the Sector 3’s Busy Hour is at 2:00AM, we should store the corresponding Cell’s hourly summary value @2:00AM for “Throughput, DL Volume” for Cell JHRTJML_103 and Cell JHRTJML_3.

Note:

Configurable aggregation type is expected for the above Sector Busy Hour calculation. As we are using "Sum Over Entity" for the Entity Aggregation. And "Average Over Time" for the Time Aggregation.