postproctool up to w11 user guide rev f

Ericsson Internal1 (24)

Prepared (also subject responsible if other) No.

TEI/OCC/Y Pietro Volpe TEI-09:001158 UenApproved Checked Date Rev Reference

2011-09-22 F

PostProcTool_up toW11 _RNC User Guide




2011-09-22 F

Contents

1 Introduction.........................................................................................31.1 Revision history...................................................................................31.2 Related documentation.......................................................................41.3 Scope..................................................................................................41.4 Open Issues........................................................................................51.5 Limitations...........................................................................................52 PostProcTool overview.......................................................................63 PostProcTool......................................................................................83.1 Post Processing Area.........................................................................93.1.1 Step1: Rename ROP..........................................................................93.1.2 Step2 : Post processing....................................................................103.1.3 Step 3: Final Step.............................................................................123.1.4 Results..............................................................................................123.1.5 TemplateGraphDB2 worksheet description......................................143.1.5.1 Load Graphs sheets..........................................................................153.1.5.2 Parameters.......................................................................................183.1.5.3 pmCounters worksheets...................................................................213.1.5.4 Event Intensities KPIs.......................................................................213.1.5.5 Event Load........................................................................................213.1.5.6 Model................................................................................................213.1.6 TemplateGraph worksheet description.............................................223.1.7 List Counters.....................................................................................233.1.8 Create a new List of all counters.......................................................244 References........................................................................................24




2011-09-22 F

1 Introduction

This document provides the reader with some basic instructions about how to use the PostProcTool Excel workbook and its related tools and templates.

1.1 Revision history

Rev. Date Author

A 2009-03-04TEI/NRR P. Volpe

TEI/RFN M. Marone

Changes compared to P5 doc (TEI-08:003992):

New counters for channel switching and RNC capacity added (Iub throughput and Users) and paging

RNC module structure changed. User plane pool for DC, CC and PDR considered. New counters for processor Load added.

No alert file for stand-by processor

Utility area added in ComputeloadP6 tool

Folder example added to practice and become confident with the tool

B 2009-04-07TEI/NRR P.Volpe

TEI/RFN M.MaroneDetailed description of new TemplateGraphDB2 file

C 2009-12-15 TEI/NRR P. Volpe Discovering HW release removed, manual insert

Counter aggregation made on Node level

Modified the Output .txt adding number of processors

Counters list updated




2011-09-22 F

Tool robustness added for duplicated counters in ROP files

TemplateDB2graph modified

D 2010-08-04

New release for RNC 3820. All file renamed with the suffix RNC3820

New graphs added in the component method. CPI GPB load and DC load implemented

E 2011-01-31

New release for handling both RNC type.

RANAP/RNSAP and DC load analysis implemented

F 2011-09-21 TEI ….P. Volpe

Tool layout and core processing tool restyling

CPI dimensioning formula introduced

Traffic model summary introduced

Automatic calculation of cells and Iublinks

1.2 Related documentation

The PostProcTool Excel workbook (tool was renamed) has now been updated to support Ericsson Consultants in the delivery of the TNO RNC Load Monitoring Service Module for WCDMA RAN in SW releases up to W11.

TNO related documentation is available on the BUGS website.

1.3 Scope

RNC 3820 HW Releases R2 and RNC 3810 R5/5.1 are supported.

The tool is also able to handle different naming convention of ROP files.

The main tool action is to group information at Node level because RNC SW implements full pooling concept for both User and Control plane.




2011-09-22 F

The same tool is now able to handle both RNC 3810 and 3820 and to perform cost analysis for RANAP/RNSAP processors and DC processors.

The new tool was restyled by improving the performance about 20/30 times and so reducing the processing time from some minutes per ROP to few seconds.

Moreover the formulas reported in the CPI dimensioning guideline are implemented, in order to help the tuning of CPI formulas (i.e. to identify the correction factor as indicated in the post-launched dimensioning document).

Please observe that in this document when referring to “component formula” it means that the processor load is calculated multiplying the intensity of UTRAN procedures, obtained by counters, by the cost of the procedures; while when referring to the “CPI formula” represents the simplified component method version as reported in the RNC dimensioning guideline.

Please note that the costs reported for all boards are the one available at the end of September 2011 since no W11 measurement campaign was performed by PDU.

1.4 Open Issues

-

1.5 Limitations

Mixed HW for GPB module roles are supported and has to be manually specified by the user.

DC HW type has to manually specify after the post-processing phase.

Any comment for improving the tool is more than welcome.

Any initiative to improve it will be highly appreciated.




2011-09-22 F

2 PostProcTool overview

The basic function of this home-made MS Excel is to group GPBs and SPBs load information at node level in order to have a compact view of the RNC performances as shown in Figure 1 below.

Figure 1 RNC Load performances compact view

Additional features have been then added in order to group specific counters at node level and help to identify the correlation between the load generated in the node and the UTRAN intensity procedures.

The MS Excel based tool is composed of several MS Excel workbooks and text files (templates and outputs) even if only one user interface was created to hide the functionality implemented in the different workbooks:




2011-09-22 F

MS Excel workbooks

PostProcTool

TemplateGraph

TemplateGraphDB2

Text files (.txt)pmcountersandSheet

pmcounters

Exe file rncRop_B

zipdll.dll

Table 1 Tool structures: MS Excel workbooks and txt templates

The MS Excel workbook PostProcTool is the core of the tool; it relies upon some .txt templates to perform its tasks and to create the pm counters databases where the aggregation at Node level is performed.

Please note that all the listed files must be placed in the same directory.

The other MS Excel workbooks are the database where all pmcounters and KPI load formula are reported and graphically displayed. The TemplateGraphDB2 and TemplateGraph will be the output of post processing and have to be renamed before saving in order to avoid the template corruption.

Note: In order to better understand how to use the tool please use the ROP file in the example directory to become confident with the tool functionalities. In the example folder there are also some files to be used to perform tool testing: the Read Me.txt file contains the relevant instructions.




2011-09-22 F

3 PostProcTool

This MS Excel workbook is a collection of macros to post-process ROP files in order to create database text files.

Different functions can be carried out; each of them can be initiated by means of its dedicated action button in the GUI, as shown in Figure 2. All action buttons include a brief description of the function and indicate the relevant inputs.

Figure 2 PostProcTool GUI and available tasks

The GUI groups the functionalities in two different Areas:

1. Post Processing Area

2. Utility Area




2011-09-22 F

3.1 Post Processing Area

There are three steps to follow in the sequential order. Only step 1 can be skipped if the ROP files have already the naming convention required.

3.1.1 Step1: Rename ROP

In order to improve tool performance an .exe post process routine (rncRop_B.exe) was introduced. This requires that ROP files have the same naming convention used by RNC when the ROP is generated i.e A<Year><Month><Day>.<start time>->stop time>.1.<xml/zip> for example A20110908.1745-1800.1.

It’s common that ROP files are extracted by OSS where they are typically renamed.

Scope of the function is to rename files according to the naming convention required. Please note that the only format supported is

Folder\A20110908.1615+<Time Zone>-1630+<Time Zone>_<Full RNC distinguish name>.xml

In case of other format then please provide the renaming in any other way.

Figure 3 ROP renaming




2011-09-22 F

All the files in the selected folder that need to be post processed will be selected and renamed.

3.1.2 Step2 : Post processing

This function allows the selection of specific ROP files list to be post processed.

Figure 4 Step 2 button

Upon pressing the button a pop-up window appears.

The first and last ROP file will be specified using the “Browse” button to search the folder.

Than in the bottom of the pop up window the RNC name can be optionally inserted and the type of RNC (3810 or 3820) selected.

It is strongly suggested to left unchanged all the other options that are simply pointers to the .txt files containing the list of counter to extract.

The tool assumes that all the template files are in the same directory where the excel tool was located.

Pressing the OK button will start the post processing phase.




2011-09-22 F

Figure 5 Pop up for ROP selection

A dos widow appears showing the parsing phase for each ROP.

.

Figure 6 DOS windows showing post processing status

The execution status can be checked in two ways:

1. reading in the dos windows the ROP name currently in elaboration




2011-09-22 F

2. Using explorer application to check how many Text files are already created, since a .txt file will be created for each ROP.

Figure 7 Step 2 progressing status

At the end of the process the TemplatedGraphDB2 will be partially populated with all counters that can be aggregated, for KPI scope, at Node level. Moreover the original folder containing the ROP will be populated with .txt files (one per ROP). These created files are in text format and they are simply a text conversion of xml ROP files.

3.1.3 Step 3: Final Step

This function allows the user to fill the first DB (TemplateGraph) that contains all the processor load information and complete to fill the second database DB (TemplateGraphDB2).

When the Step 3 button is pressed it is simply required to select the txt file created in the previous phase.

Figure 8 Step3 final step

At the end of the processing all the .txt files will be removed and the original ROP .xml files will be kept. This suggests a way to check the running status simply counting the number of .txt file discarded in the selected directory.

3.1.4 Results

The created output file (i.e. the TemplateGraphDB2) must be soon renamed and saved. It is composed of the following worksheets:

1. mMP_Load Graphs




2011-09-22 F

2. R&R C2_Load Graphs

3. DC dev_Load Graphs

4. Parameters

5. Model

6. UeRc

7. RNL Proc

8. RAB

9. HO

10. Node Capacity

11. Load Reject

12. Volume

13. PDR

14. Ch Sw

15. HardHO

16. Irat

17. Paging

18. Signalling

19. mMP_Event intensities

20. mMP_Event Load

21. DC dev_Event intensities

22. DC dev_Event Load

23. R&R C2_Event intensities

24. R&R C2_Event Load

25. Erlang

The tool automatically fills down all the formulas up to the row containing the counters value.




2011-09-22 F

Please note that the grey sheets are not anymore used in the tool.

3.1.5 TemplateGraphDB2 worksheet description

DB2 worksheet includes the following sheets sets:

1. Output worksheets, yellow tab set: this set contains tool output and parameters to be set in order to get RNC load monitoring analysis and dimensioning:

i. mMP_Load Graphs

ii. R&R C2_Load Graphs

iii. DC dev_Load Graphs

iv. Parameters

2. pmCounters worksheets, red tab set: this set contains pmCounters used to develop Event Intentesity KPIs. Pmcounters are divided in KPIs families:

UeRc

RNL Proc

RAB

HO

Node Capacity

Load Reject

Volume

PDR

Ch Sw

HardHO

Irat

Paging

Signalling

Please note that in case a counter is not found inside a ROP file the corresponding column is reported in pink to remark that the relevant formula where counter is used will be wrongly calculated. This is a way to understand if a counter has to be activated too.




2011-09-22 F

Figure 9 missing counters

3. Calculated Load worksheets, blue tab set: this set contains formulas to calculate Event intensities and relevant load:

mMP_Event intensities

mMP_Event Load

DC dev_Event intensities

DC dev_Event Load

R&R C2_Event intensities

R&R C2_Event Load

4. Erlang worksheets, grey tab set are currently deactivated:

Erlang

3.1.5.1 Load Graphs sheets

These worksheets provide the user with different pre-organized charts:

o Calculate MP Load (component and CPI formula) vs Mesured MP Load

o Calculate MP Load vs Mesured MP Load plus the different components of the MP load

o Measured MP RANAP RNSAP Load vs calculated one using the formula reported in the internal guideline.




2011-09-22 F

o Measured DC Load vs DC calculated load using the formula reported in the internal guideline and CPI guideline.

The following picture shows an example of the first four graphs. In order to have a better understanding of correlation between GPB load and users or Iub throughput different graphs are created.

In case there is no good match between measured and calculated load then it is suggested to add the line of pmNoOfSwDownNgAdm counter that can be found in the “Load reject” Worksheet. It was already observed that the soft congestion can raise the GPB average load from few to main load points.

The first picture in figure below (top on the left) it’s a summary of GPB and DC load components calculation compared with the measured values and mMP CPI calculation. From this picture the reliability of load estimation calculation can be evaluated.

Figure 10 mMp_Load Graph

The following Pie graph can be found always in the mMP_Load Graphs sheet, it shows the weight of each procedure in a selected time frame. So please remember to correctly choose the ROP time frame by identifying the correct row corresponding to the wanted period in the mMP_Event Load sheet and then updating the graph. So, for example, if the time period into the graph (the Busy hour) is 18:00, then, by checking in the mMP_Event Load sheet we discover (this is only an example but a real row number has to be found) that counters related to 18:00 are reported in row 74.




2011-09-22 F

Click on the graph and change the row in the formula like the depicted figure below.

Figure 4 UTRAN components

Figure 5 RANAP/RNSAP load

The last pictures show the comparison between the measured average DC load and the calculated DC load and RANAP /RNSAP load using the internal guidelines.




2011-09-22 F

Figure 6DC load

For DC load both CPI formula and internal guideline (component method) is applied. It is recalled that the CPI formula for DC is divided in two parts: the Control Plane calculation (Load CPI CP DC) and User Plane calculation (Load CPI UP DC). Once the graph of component calculation overlaps the measured load it is possible to tune both CPI formulas. The correct tuning has to provide a good overlap between:

1. Load CPI CP DC and CP Internal

2. Load CPI UP DC and UP Internal

3. Measured DC Load and Total Load CPI and DC load calculated

3.1.5.2 Parameters

This worksheet represents a collection of all constants, variables and user inputs that are needed to calculate the events’ intensities, the events’ load, the calculated MP, DC and Ranap/Rnsap load.




2011-09-22 F

Figure 7 Parameters worksheet screenshot

Green cells are input cells; light green cells are advanced input cells (i.e. basic event costs).

The inputs to be specified by the user are:

o BH start and stop time for both morning and afternoon (Cancelled Function from the W10 release tool)

o The scaling factor for GPB event cost. These values can be changed in order to enable the overlap between the calculated and measured load lines in the previously explained graphs.

o Number of mMP per subrack and HW release must be specified in cells B27:F27. The sum of inserted mMP has to be equal to the value reported in cell B33. Moreover in case of mixed HW it is not really mandatory to fill the information of right boards number in the right subrack, what is really important is that the total numbers of boards in all subracks matches the B33 Cell value.

Please observe that all reported costs are valid per HW type while the SW dependency is understood to be less influent. However if new cost measurement will be available by the PDU the tool update will consist only in the update of the table B1:D20.




2011-09-22 F

Figure 15 DC and RANAP RNSAP cost area

In the right area of Parameters sheet the cost for each UTRAN procedure is reported for SPB type (DC cost) and MP type (for RANAP & RNSAP cost).

The number of DC per SPB type must be manually reported in cells K31,K32 and K33 and the sum has to be equal to the value in cell D31.

In cells Q14, R14, S14 the value has to be set to 1, according to the HW release for GPB used in RANAP/RNSAP position. (Only one cell has to be set to 1, while the others to 0). Then if the calculated and measured load graph does not overlap the 1 value has to be scaled until the graph overlap takes place.

Figure 8 Parameters worksheet screenshot




2011-09-22 F

Still on the right it is added the new table implementing the CPI formula. The cells Z26 and Z27 are used to tune the CPI formula has explained in the previous paragraph.

Please observe that the Control Plane tuning part (cell Z26) is typically >1,5 since DC CP CPI formula is not reliable.

3.1.5.3 pmCounters worksheets

pmCounters worksheets are used to display the results of the Node-based aggregation performed by the tool (when applicable) in a column format: different colors are used to differentiate among events.

In particular in the sheet Load Reject more counters are reported in case there is the need to deeply understand the reject cause.

3.1.5.4 Event Intensities KPIs

These worksheets makes use of the aggregated info available in the pmCounters worksheets (see section 3.1.5) to calculate the intensities of the events listed in reference [1] on Node basis.

3.1.5.5 Event Load

In these worksheets the previously calculated event intensities are here multiplied by the corresponding event cost; the correct (i.e. tied to the specific HW Release) cost is determined in the Parameters worksheet.

This worksheet aggregates the different event load into components and calculated the MP DC and R&R load, at node level.A comparison with the measured load (available in the Node Capacity worksheet) is also carried out.

3.1.5.6 Model

This is a new sheet that enables the user to gain the traffic model.

Using the scroll down button it is possible to select the Busy Hour. This action will trigger a sum of counters to create the KPI for traffic model for 4 consecutive ROPs (1 hour).

In the green cell (I2) the number of users has to be inserted. If not known it is suggested to insert a number of subscriber that provide 20 mE voice (O3) or any other value if it is known this parameter in the network under analysis.

To easily find the number of subscribers it is suggested to use the excel function goal seek setting to 20 the target cell O2 by changing cell I2.




2011-09-22 F

Figure 9Traffic Model worksheet screenshot

The Erlang evaluation per each service used in this section is implemented in the UeRc sheet. Since the formulas are a bit complex the summary of involved UeRc state is summarized in the attached excel file.

3.1.6 TemplateGraph worksheet description

DB worksheet includes sheets reporting processor load for mMP, DC, CC and PDR.

Moreover it is created one sheet for each subrack in order to report the pmprocessorload in each slot. This counter is a platform counter that show the last average 5 minutes processor load and it is valid for each board.




2011-09-22 F

Utility Area

The functionalities offered in this area are used to assist the user in the creation of pmcounters list needed for post processing analysis.

3.1.7 List Counters

The macro will create a report in the Utility worksheet listing all counters contained in the selected file (pmcountersandSheet.txt file).The purpose is to check the information contained in the file and/or perform some changes.

Figure 10 Utility Area

The following picture shows the result of the macro:

o Column A will state the MO name

o Column B will show the counter name

o Column C will state the worksheet where the counters will be placed during the cost method preparation process.

o Column D will state the column in the specified previously indicated sheet where the value will be placed.

Figure 19 List of counters in the Utility sheet




2011-09-22 F

3.1.8 Create a new List of all counters

The macro will create a new pmcountersandSheet.txt file in the tool directory starting from a map created in the Utility worksheet. When pressing the button the number of rows in the Utility table that will be saved into the file is required.

4 References

[1] RNC Load Monitoring Technical Guide

postproctool up to w11 user guide rev f

Documents

new tool

rnc sw

scope rnc

new counters

rnc type

mergeformat postproctool

new list

new release