Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Performance
Created by Guest
Created on Jul 4, 2022

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”

LTE Cell Name

Band

Cell ID

Sector

JHRTJML_103

L26

103

S3

JHRTJML_102

L26

102

S2

JHRTJML_101

L26

101

S1

JHRTJML_3

L8

3

S3

JHRTJML_2

L8

2

S2

JHRTJML_1

L8

1

S1

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:

RRC User for

LTE Cell

JHRTJML_103

RRC User for

LTE Cell

JHRTJML_3

Aggregated RRC User for

JHRTJML_Sector3

00:15AM

a1

a2

a1 + a2

00:30AM

b1

b2

b1 + b2

00:45AM

c1

c2

c1 + c2

01:00AM

d1

d2

d1 + d2

01:15AM

e1

e2

e1 + e2

01:30AM

f1

f2

f1 + f2

01:45AM

g1

g2

g1 + g2

02:00AM

h1

h2

h1 + h2

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.


Idea priority Urgent