TNPM Wireless Component – Crafting Busy Hour Model (Part 2)
BengSee 270005Y61G Visits (1471)
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.
Define Relationships in Busy Hour Model
Once all the folders and namesapces (in Part 1) are completed, define the relationships between the subject queries. The following diagram shows the overall relationships. The content within each folder is to be explained in details.
To ease explanation, some repeated details are showed in the following diagrams:
TCR Time subject query contains the commonly used predefined time interval. It is to be used as common reference among subject queries.
‘Resources’ contains the subject queries of all entities and the relationships among themselves. This is to be used as the network hierarchy.
‘SBH Traffic’ contains the merged subject queries of busy hour metrics and its nc tables. The sample diagram shows only the merged subject queries of a single busy hour definition for different intervals. There can be more busy hour definitions in a Cognos model.
More about sbh_merge_daily (weekly, monthly)
Key query items in sbh_
Bh_busy_hour : The busiest hour timestamp recorded of the determiner in a busy hour definition.
Bh_key: The busy hour’s focal entity.
Bh_nc_id: The generated unique ids by the system.
Define the relationship between SBH_Merge_Daily and TCR Time
Define the relationship between SBH_Merge_Daily and Resources
Each network entity is uniquely identified by nc_id and its primary key (eg: bearer_id). So these 2 query items are used in the relationship definition.
Define the relationship between SBH_Merge_Daily and SBH Traffic
When there is rollup stored busy hour definition, the busy hour metrics are stored in <entity>_dbh_v. Hence there is merged subject query (eg: nc_m
When there is normal stored busy hour definition, the busy hour metrics are stored in <met
Note the differences of relationships required for rollup stored busy hour and normal stored busy hour.
Regular dimension will be covered in next post.