Details for RA Control Implementation

1. Background

For charging of data usage over LTE, PGW (Packet Data Network Gateway) generates session-based
Credit Control Request (CCR). This is sent to OCS via mediation through Diameter Routing Agent
(DRA) over Diameter Gy interface. Mediation will convert CCR and mediate input diameter requests
into suitable format for OCS (SAP CC). Upon CCR validation, OCS deducts appropriate credit from
subscriber’s account and responds back with Credit Control Answer (CCA). This acknowledgement will
have the granted quota in case the requested service is authorized via mediation. Mediation will
respond back to the network element by converting the response from OCS (SAP CC) i.e CCA into
suitable diameter answers. Otherwise, the service could be rejected with error result code.

Figure 1 – LTE data flow

Network Mediation Billing

HSS

R3
SAP OCS
R1 R2 CCR
Diameter Gy Active MZ-CC API SAP CC SAP CI
PGW
Mediation
CCA Aggregator of CC
Rating of CDRS
Diameter Gx CDRs

<< Policy rule <<

PCRF
<< Status <<

2. Risks covered:
a. LTE data Services:

Impact
Risk Customer Revenue Others
Risk Root Cause
# Experience /
Leakage
Data usage by Failure in Network node to
subscriber without interrogate with charging
getting charged or system or data session
R1 billed connected for delayed 
response of insufficient
balance from charging
system.
Incorrect Volume Mismatch in volume
charged to recorded between network
subscriber leading node and charging system
R2
to revenue loss or leading to incorrect  
customer invoicing
dissatisfaction
3. Control Name: Usage Reconciliation for LTE Network (PGW - Network vs. OCS -Charging) –
Daily Analysis

4. Control Objective:

The objective of the control is to ensure accuracy in transfer of usage records between networks
(PGW) and charging node (OCS SAP CC). The count and volume of PGW CDRs should be equal to
OCS CDRs in case of LTE data usage

5. Control Description:

It is very essential for a telecom organization to capture all the network CDRs and rate/bill all the
billable CDRs to the customer to generate revenue. The total count of billable network CDRs and
volume should be exactly equal to OCS rated CDRs. In case there is mismatch it means all the
network CDRs are not billed leading to revenue loss.

6. Frequency of the Activity:

This activity is automated on the Subex ROC RA tool and is performed on a daily basis. The
reconciliation is 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
PGW – Passive
1 PGW CDR IT Operations TBD
Mediation

2 OCS CDRs SAP CC IT Operations TBD

8. Activity Overview:

 Following activities are automated in RA Tool (SUBEX)

o Circle wise summary of PGW CDRs Volume and Volume of OCS charged CDR
o Count of PGW CDRs Vs. Charged OCS (LTE) CDRs (Two way reconciliation)
o Volume of PGW CDRs Vs. Charged OCS (LTE) CDRs (Two way reconciliation)

9. Probable Exceptions and Concerned Function/Team:

 Mismatch in CDR count as per PGW CDR and OCS LTE CDR
 Mismatch in volume of CDRs as per PGW and PCS LTE CDR
10. Exceptions reports generated

 Count of CDR present in OCS but missing in PGW

o These exceptions may be because of duplicate CDR generated in OCS or due to
incomplete upload of all PGW CDRs.

During root cause analysis, if it is established that CDRs have been correctly
uploaded than these exceptions need to be sent OCS team to check for generation of
duplicate CDRs. Another reason may be due to incomplete field (charging id, rating
group) getting reflected in OCS CDRs.

 Count of CDRs present in PGW and missing in OCS

o These exceptions need to be sent to OCS and PGW team to analyze if
 OCS has not rated the session. It may so happen that a particular CDR is
rated but not recorded. This will lead in revenue loss or incorrect recording of
CDRs.
 Subscribers not configured or in disconnected state on OCS but are active on
all network nodes.
 The data session was initiated at network end despite being tagged as
unauthorized by OCS. This will lead to creation of CDR at PGW but not in
OCS.
 Any specific url which is bypassing OCS without business approval.

 Volume mismatch between PGW CDRs and OCS CDRs

o These exceptions need to be sent to PGW team and OCS team to analyze the
difference in volume reflecting in CDR. Following are possible root causes for
mismatch between AAA CDR Volume and OCS CDR volume:
 Session disconnected at OCS end but continued at PGW end leading to
mismatch in volume of data usage.
 AAA and OCS system time not synchronized leading to difference CDR cutoff
during midnight leading to volume difference between recodes generated by
both systems.
 Difference of rounding logic between PGW CDRs and OCS CDRs