Details for RA Control Implementation

1. Background

For LTE voice call PGW will route the call to IMS. IMS will send the charging information via RO
interface to OCS. In OCS SAPCC is responsible for rating the CDRs on real time basis and SAPCI
aggregates the CDR for generating statement of account. SAPCC records/usage CDRs are used for
revenue reporting and providing usage and rating information’s to customers.

Network Mediation Billing

Rating and Billing Revenue
Reporting
Rating of CDRS
PGW R3
MZ-CC API SAP CC
Active ERP
Mediation
Billable CDR Files Aggregator of CC CDRs

Diameter Gy Billable CDR

SAP CI
IMS RAW Billed
CDRs CDRs
Bulk up loader R1 R2

ss

Figure 1 – Processing of CDRs for VOICE service

Detailed Flow:

All the rated CDRs are grouped in files and pushed by SAPCC through a bulk up-loader to SAPCI.
The bulk up-loader uploads the SAPCC CDRs to SAPCI as billable CDR’s. These Billable CDRs are
further classified by SAPCI as ‘billed CDR’s or ‘raw CDRs’. The frequency of upload is user-based
and currently the up-loader is uploading CDRs every one minute.
SAPCI inspects the SAPCC CDR Fields and bills the CDR’s. These CDRs are knows as Billed CDR’s.
Any CDRs rejected by SAPCI are transferred to a separate bucket and these CDRs are known as
‘raw CDRs’. Following are the instances where SAPCI rejects the SAPCC billable CDRs and sent it
to reject bucket.
I. Incomplete fields of CDR transferred by SAPCC to SAPCI.
II. Subscriber not configured in SAPCI but configured on SAPCC.
If bulk up-loader fails to upload the files in SAPCI these CDRs will not reflect in SAPCI but will be
present in SAPCC
2. Risks covered:-
a. IMS Services:

Impact
Risk
Risk Root Cause Customer Revenue Others
#
Experience / Leakage
Incorrect / incomplete Transfer of files /
billing for postpaid records between SAP
customers CC and SAP CI is not
R1 complete due to issue  
with loader bulk up-
loader.

Incorrect statements of Loss of records /

account generated for usage records are
prepaid customers corrupted

R2 Rejection of usage 
records at SAP CI due
to incomplete records
generated at SAPCC

Incorrect reporting of Duplication of records

revenues / decrement at SAP CC and / or
based on SAP CI records SAP CI

R3 Subscriber not 
configured at SAPCI
resulting in CDRs
reject for the
subscriber is SAPCI.

3. Control Name: OCS usage CDRs reconciliation for Voice services (SAP CC vs. SAP CI) – Daily
Analysis

4. Control Objective:

The objective of the control is to ensure accuracy in transfer of usage records between SAP CC and
SAP CI in terms of count and duration of CDRs.

5. Control Description:

The charging for any usage gets triggered from SAP CC based on customer tariff, plan, free usage
quota and current balance. These usage records generated at SAP CC are transferred to SAP CI for
purpose of customer invoice / statement of account generation and reporting of revenues.

All the CDRs need to be rated and correctly recorded for revenue reporting and resolving customer’s
queries relating charging of CDRs. The reconciliation is performed to ensure both count of CDRs and
usage duration is identical in both the systems for usage for Voice.
6. Frequency of the Activity:

These activities are automated on the Subex ROC RA tool and are performed on a daily basis. The
reconciliations are performed on data for (D-2) day on any given day.

7. Data Sources to be used:

Source Network
# Data Description Function Name SPOC
Element
SAP CI USAGE CDR for
1 SAP CI IT Operations TBD
LTE – Voice
SAP CC USAGE CDR for
2 SAP CC IT Operations TBD
LTE – Voice

8. Activity Overview:

 Following activities are automated in RA Tool (SUBEX)

o SAPCC vs. SAPCI usage CDRs for Voice – Count & Volume (Two way reconciliation)

9. Probable Exceptions:

 Mismatch in count of usage CDR between SAP CC and SAP CI for Voice
 Mismatch in volume of CDRs between SAP CC and SAP CI for Voice

10. Reference file and Information:

SAPCC CDRs SAPCI CDRs

11. Work-steps for Data Extraction and Loading/Parsing:

A. Usage CDR reconciliation between SAPCC Vs. SAPCI for LTE Network:
i. This reconciliation activity is configured on RA tool as ‘Recon_A13_SAP CC vs SAP CI
Usage Validation (IMS)’.

12. Exceptions report generated

A. Usage CDR reconciliation between SAPCC Vs. SAPCI for IMS network:

 CDRs present in SAPCC but missing in SAPCI

o These exceptions need to be analyzed before sending it to OCS team for further
analysis. Following preliminary analysis to be done by RAFM team:
 Any known exceptions in file level reconciliation between SAP CC and SAP CI.
  Known business filtration rules (if any) for not processing the respective
CDRs at SAPCI.
o After analyzing the above points the exceptions need to be sent to OCS team or
extract the RAW CDRs from SAPCI to validate if these CDRs are rejected by SAPCI
and are in RAW CDR bucket in SAPCI. These rejects need to be analyzed and
reprocessed in SAPCI. The rejection may be because of the following reasons:
 Invalid Master data provided in the BITS. This can be due to the wrong/missing
data flow from SAP CRM to SAP CI.
 OCS sends invalid / missing data in required fields like Sub process, BIT Type,
Date & time format, etc...  Then check at SAP CI end, if it is not possible to
correct the RAW BIT’s at CI system end, then these RAW BIT’s needs to be
handled at OCS or further upstream system level only.
 If OCS sends valid values in the required fields like Sub process, BIT Type, Date &
time format, etc... Even though BIT received as RAW BIT then SAP CI system
need to correct the BIT by modifying the missing configuration and transfer the
Raw items to Billable item.

 CDRs present in SAPCI but missing in SAPCC

o These exceptions need to be sent to OCS team to check if few recodes are double
processed in SAPCI or SAPCC CDRs are not completely loaded in database.

 Duration mismatch between SAPCC CDR and SAPCI CDR.

o These exceptions need to be sent to OCS team to check if SAP CI is correctly
processing the SAP CC CDR volume.