This chapter describes the Oracle Communications Billing and Revenue Management (BRM) reports that support GPRS Manager.
For general information on how to run reports, see "Running BRM Reports".
Important:
GPRS Manager is an optional component, not part of base BRM.The General Packet Radio Service (GPRS) reports support GPRS Manager. These reports help you identify which GPRS products and services are profitable by tracking the following information:
GPRS usage by access point name (APN). See "GPRS APN Usage Report".
GPRS usage by product. See "GPRS Product Usage Report".
The number of accounts that have subscriptions to particular GPRS products. See "Product Subscriptions Report".
In addition, the GPRS Error Summary Report and GPRS Error Detail Report help you identify GPRS service problems that are causing you to lose revenue.
Note:
You must upload the GPRSAPNUsage.source file that is in the StoredProcedures folder to the database after the GPRS reports are installed. For more information about loading stored procedures, see "Loading Stored Procedures".The GPRS APN Usage report (GPRSAPNUsage.rtf) tracks GPRS usage by access point name (APN), an internally defined name used by a GPRS network to identify an entry point in an external packet data network.
This report enables you to identify the access points in your GPRS network that handle the most traffic and those that generate the most revenue. You can use this report to determine the traffic-to-revenue ratio for each access point.
For each APN listed in the report, the following information is displayed:
Balance Impact: The total income generated during the specified time period by GPRS usage associated with the APN. Income from subscription fees is not included.
Accounts with Usage: The number of accounts for which GPRS usage associated with the APN was reported during the specified time period.
Sessions: The number of GPRS sessions associated with the APN during the specified time period.
Megabytes (MB): The total megabytes transmitted during all GPRS sessions shown in the Sessions column.
Duration (Hours): The total length in hours of all GPRS sessions shown in the Sessions column.
The information shown in this report can be grouped by resource, APN, country, or state.
You can find the SQL query for this report in the following file:
Local_drive:\BIP_Home\xmlp\XMLP\Reports\BRM Reports\GPRS Reports\StoredProcedures\GPRSAPNUsage.source
You can include pie charts that show the percentage of GPRS-related revenue, megabytes, usage time, and sessions handled by each APN during the specified time period.
You can change the following parameters to modify the output of the GPRSAPNUsage report:
State Details
Include Chart
Country
State
Start Date (date only, not date-time)
End Date (date only, not date-time)
If your BRM system does not contain state data, see "When to Modify Formulas for New Values".
For parameter descriptions, see "Understanding the Standard Parameters".
Note:
You must upload the GPRSProductUsage.source file that is in the StoredProcedures folder to the database after the GPRS reports are installed. For more information about loading stored procedures, see "Loading Stored Procedures".The GPRS Product Usage report (GPRSProductUsage.rtf) tracks GPRS usage by product for a time period you specify. By showing both the network traffic and the revenue generated by each GPRS product, this report enables you to determine which GPRS products have the best traffic-to-revenue ratios.
For each product listed in the GPRSProductUsage report, the following information is displayed:
Balance Impact: The total income generated during the specified time period by GPRS usage associated with the product. Income from subscription fees is not included.
Accounts with Usage: The number of accounts for which GPRS usage associated with the product was reported during the specified time period.
Sessions: The number of GPRS sessions associated with the product during the specified time period.
Total Megabytes (MB): The sum of megabytes transmitted during all GPRS sessions shown in the Sessions column.
Average Bytes per Session: The mean number of bytes transmitted during each GPRS session shown in the Sessions column.
Total Duration (Hours): The sum of the length of all GPRS sessions shown in the Sessions column.
Average Session Duration (Hours): The mean length in hours of each GPRS session shown in the Sessions column.
The information shown in this report can be grouped by resource, country, state, or product POID.
You can find the SQL query for this report in the following file:
Local_drive:\BIP_Home\xmlp\XMLP\Reports\BRM Reports\GPRS Reports\StoredProcedures\GPRSProductUsage.source
You can include pie charts that show the percentage of GPRS revenue, megabytes, usage time, and sessions associated with each product during the specified time period.
You can change the following parameters to modify the output of the GPRSProductUsage report:
State Details
Include Chart
Country
State
Product
Start Date (date only, not date-time)
End Date (date only, not date-time)
If your BRM system does not contain state data, see "When to Modify Formulas for New Values".
For information on parameters not described in Table 14-1, see "Understanding the Standard Parameters".
Table 14-1 GPRSProductUsage Parameters
Parameter | Description | Valid Values | Default Value |
---|---|---|---|
Product |
The name of the product whose GPRS usage you want to show. |
Any valid product name or ALL The parameter value list might not include all the product names stored in your BRM database. To add product names to this list, see "Adding Parameters in BI Publisher". |
ALL |
Note:
You must upload the GPRSErrorSummary.source file that is in the StoredProcedures folder to the database after the GPRS reports are installed. For more information about loading stored procedures, see "Loading Stored Procedures".The GPRS Error Summary report (GPRSErrorSummary.rtf) lists GPRS session errors by error type for a time period you specify.
For each error type listed in a report, the following information is displayed:
Balance Impact: The total income lost during the specified time period because of this type of error.
Accounts with Errors: The number of accounts for which this type of error was recorded during the specified time period.
Sessions: The number of GPRS sessions in which this type of error occurred during the specified time period.
Megabytes (MB): The total megabytes transmitted during all GPRS sessions shown in the Sessions column.
Error Duration (Hours): The total length in hours of all GPRS sessions shown in the Sessions column.
The information shown in this report can be grouped by resource, country, state, or termination cause.
You can find the SQL query for this report in the following file:
Local_drive:\BIP_Home\xmlp\XMLP\Reports\BRM Reports\GPRS Reports\StoredProcedures\GPRSErrorSummary.source
No charts are available for this report.
You can change the following parameters to modify the output of the GPRSErrorSummary report:
State Details
Country
State
Start Date (date only, not date-time)
End Date (date only, not date-time)
If your BRM system does not contain state data, see "When to Modify Formulas for New Values".
For parameter descriptions, see "Understanding the Standard Parameters".
Note:
You must upload the GPRSErrorDetail.source file that is in the StoredProcedures folder to the database after the GPRS reports are installed. For more information about loading stored procedures, see "Loading Stored Procedures".The GPRS Error Detail report (GPRSErrorDetail.rtf) lists GPRS session errors by account for a time period you specify.
For each account listed in the report, the following information is displayed:
Error Type: The type of GPRS session error that occurred.
Balance Impact: The total income lost during the specified time period because of this type of error.
Sessions: The number of GPRS sessions in which this type of error occurred during the specified time period.
Megabytes (MB): The total megabytes transmitted during all GPRS sessions shown in the Sessions column.
Error Duration (Hours): The total length in hours of all GPRS sessions shown in the Sessions column.
The information shown in this report can be grouped by resource, country, state, or termination cause.
You can find the SQL query for this report in the following file:
Local_drive:\BIP_Home\xmlp\XMLP\Reports\BRM Reports\GPRS Reports\StoredProcedures\GPRSErrorDetail.source
No charts are available for this report.
You can change the following parameters to modify the output of the GPRSErrorDetail report:
State Details
Country
State
Start Date (date only, not date-time)
End Date (date only, not date-time)
If your BRM system does not contain state data, see "When to Modify Formulas for New Values".
For parameter descriptions, see "Understanding the Standard Parameters".
Some of the column totals displayed in the wireless reports are derived by simply adding the values in the preceding rows. For example, the total for the Sessions column in Figure 14-1 is the sum of the preceding sessions:
The following column totals, however, are derived in less obvious ways:
Accounts with Errors Column (In the GPRS Product Usage and GPRS APN Usage reports)
Accounts with Usage Column (In the GPRS Error Summary report)
Average Bytes per Session or Event Column (In the GPRS Product Usage report)
Average Session or Event Duration Column (In the GPRS Product Usage report)
Error Duration Column (In the GPRS Error Summary and GPRS Error Detail reports)
Megabytes Column (In the GPRS APN Usage, GPRS Error Summary, and GPRS Error Detail reports)
Total Duration Column (In the GPRS Product Usage report)
The Accounts with Errors column total represents all the accounts that had one or more of the errors shown in the preceding rows during the specified time period.
For example, Figure 14-2 lists two error types for the country USA and shows two accounts with errors for each of the error types. Because the total number of accounts with errors for USA is also two, this means the same two accounts reported both types of errors.
Figure 14-2 Accounts with Errors Column Total
The Accounts with Usage column total represents all the accounts that used the APNs, URLs, or products shown in the preceding rows during the specified time period.
For example, Figure 14-3 lists three APNs for the resource US Dollar and shows two accounts with usage for each of the APNs. Because the total number of accounts with usage for US Dollar is also two, this means the same two accounts reported usage for all three APNs.
Figure 14-3 Accounts with Usage Column Totals
The reports use this equation to calculate total average bytes per session or event:
(Total MB x (1,024 x 1,024))/Total sessions or events
Total MB is the nonrounded version of the total shown in the Total Megabytes column. For example, when the equation is applied to the data in Figure 14-4, Total MB is 5.9925470829010009765625.
Figure 14-4 Average Bytes per Session or Event Column Total
The reports calculate the Average Session Duration and Average Event Duration column totals by dividing the total in the Total Duration column by the total number of sessions or events as seen in Figure 14-5. The result is rounded up to two decimals.
Figure 14-5 Average Session or Event Duration Column Total
The Error Duration column contains two types of totals: account totals (circled in blue in the following figure) and geographic totals (circled in red).
The account totals are calculated by adding the nonrounded versions of the preceding error durations. The geographic totals are calculated by adding the nonrounded versions of the preceding account totals as seen in Figure 14-6. In both cases, the results are rounded up to two decimals.
The values displayed in the Megabytes column are rounded to two decimal places from six decimal places stored in the BRM database. Totals for this column are derived by adding the original six-decimal values and then rounding the sum to two decimals. Sometimes, the rounding makes the displayed total look incorrect.
For example, see Figure 14-7. Although the sum of the six-decimal values is correct (0.044999 + 0.004999 = 0.049998), the rounded version of the equation (0.04 + 0.00 = 0.05) looks incorrect.
The Total Duration column total is derived by subtracting the start times of all sessions or events shown in the preceding rows from their end times and then adding the differences. The values displayed in the preceding rows and the sum of those values are rounded versions of the actual values.
For example, in Figure 14-8, the actual values could be 16.533 + 7.184 = 23.717.