TNPM Wireless Component – Crafting Busy Hour Model (Part 1)
BengSee 270005Y61G Visits (2049)
TNPM Wireless busy hour reports are used to display the wireless service provider network traffic volume and other related KPI measurements. TNPM Wireless computes and stores date for the busiest hour of the day, week, or month based on the designed busy hour determiners.
Since the network traffic is not leveled throughout the day, there are some peak hours in a day (or referenced as busy hour) which are busy and have more traffic than normal hours. During these hours the network traffic is at maximum level.
To visualize the busy hour reports in Cognos layer, Cognos model needs to be created.
This is a series of blog entries which outline the details to create busy hour Cognos model by referring to Tech Pack Nokia BSS.
Listed below are the links to each entry.
Busy Hour Overview
Each busy hour definition provisioned in the system involves the following tables:
sbh_busy_hour_daily (or sbh_
<metric_group> refers to the Tech Pack defined metric group name, which frequently used as table name.
Table views for rollup up definition busy hour metrics
<entity>_dbh_v (or <entity>_wbh_v or <entity>_mbh_v)
[dbh_v] refers to daily busy hour views.
[wbh_v] refers to weekly busy hour views.
[mbh_v] refers to monthly busy hour views.
There is minor difference in the Query Subject definition later.
All of the mentioned tables and views are modeled using Framework Manager to achieve a simpler busy hour model, which eliminates the circular reference within the model generated by Model Maker (version 1.2.x).
Busy Hour Model Overview
It is proposed to categorize the related tables/views into different folders for modeling.
By using Framework Manager, the following folders are created:
The folder ‘TCR Time’ contains subject query imported from BCP package ‘TCRTIME’. No update or modification necessary for TCR Time.
The folder ‘Resources’ contains subject query which represents network entity (or NC table).
Once all related entities are imported into ‘Resources’, the relationships among the entities should be defined. For example, the following shows the overall relationships.
For each relationship between the entities, define the cardinality accordingly. For example, Network < -- > Region is linked by ‘network_id’.
The folder ‘SBH Traffic’ contains subject query which represents busy hour metrics, and its corresponding network entity. Join the traffic table view and its nc table on the primary key.
There is minor difference for rollup busy hour definition and normal busy hour definition (non-rollup).
The example below shows the rollup busy hour definition join, between <entity>_dbh_v and the nc table.
Note that ‘bearer_dbh_v’ is the <entity>_dbh_v, which is the table view for rollup up definition busy hour metrics. It is joined to nc table by its primary key only (eg: bearer_id)
Join between nc table and <entity>_dbh_v :
NC_TABLE.NC_ID = <ENT
The example below shows the normal busy hour definition join, between < metric_group >_dbh_v and the nc table.
Note that ‘nok
Join between nc table and < metric_group >_dbh_v :
NC_TABLE.NC_ID = <ENT
The folder ‘SBH’ contains subject query which represents the stored busy hour definitions. It join the sbh_definition and sbh_busy_hour_daily (or weekly or monthly).
The Query Subject join the sbh_busy_hour_daily and sbh_definition by sbh_id.
Refer definition below:
The folder ‘SBH Definition’ contains subject query which represents the stored busy hour determiner, its entity id, and busy hour metrics. This subject query is to be used for report creation, where report designer can find all stored busy hour related KPIs (including its determiners, metrics, entity id) in a single expansion.
The busy hour model relationships and regular dimensions will be covered in Part 2.