Details for RA Control Implementation

1. Background
Roaming may be defined as an ability of subscriber to access all services while traveling outside
the coverage area of their home network by using services of the visiting network. When RJIL
subscribers roam in a Partner Network Operator’s (‘PNO’) network, the subscribers are termed as
out-roamers. RJIL will receive TAPINs from PNO for subscriber’s usage in their network. When a
PNO’s subscriber roams on RJIL network, he/she is termed as an in-roamer and RJIL shall send
his/her usage records noted on RJIL network as TAPOUTs to PNO.

Figure 1 – Data and Voice in-roaming CDR processing:

R1 R3

Voice usage
INTEC Roam
system – TAP
Processing

R1 R3
R2 R2 TAPOUTs to Roaming Partner
Data usage In-roamer
DCH Operator

Mediation system

PGW – For data

Services

ERP

Revenue Booking

MCC MNC is unique combination of digits which are used for identifying an operator and are
configured on OSS BSS. MCC-MNC (Mobile Country Code & Mobile Network Code) are used in
combination to uniquely identify a mobile phone operator. MCC & MNC are primarily first five
digits of IMSI series and are configured in all network elements like Switch and IT systems like
mediation/billing system. A mobile network is able to identify the profile / home network of any
in-roamer on the basis of MCC-MNC code.

2. Risks covered:
 Impact
Risk
Risk Root Cause Customer Revenue / Others Severity
#
Experience Leakage
In roamer MCC MNC code not
subscriber not able configured in
R1 to use services Network(IMS and   High
PGW)
TAPOUTs not MCC and MNC not
generated for configured or
R2 services used by in- incorrect configured   High
roaming in INTEC Roam
subscribers system / Mediation
Un authorised in- Incorrect
roamer subscriber configuration on
R3 able to used network(IMS and   High
network services PGW)

3. Control Name:
MCC MNC reconciliation (Master vs. Mediation vs. Network(PGW/IMS) vs. INTEC ROAM
system) – Bi Monthly reconciliation

4. Control Objective:
The objective of the control is to check if all MCC MNC codes of in-roaming operator
subscribers are configured in network and billing as per business rules. Any discrepancy will
lead to revenue loss.

5. Control Description:
Operator identifies an in-roaming subscriber based on its IMSI. The IMSI series i.e MCC MNC
code of all the in-roaming operators should be as per the agreement and configured in
Network (PGW and IMS) accordingly. The MCC MNC series is also configured in Mediation
system, where roaming CDRs are filtered and passed to roam billing system for generating
TAPOUTs.

This control is a 4-way reconciliation between Business Master vs. Mediation vs. Network and
INTEC Roam.

In case the MCC MNC configuration on any of the system is incorrect the same shall result in
either non-maturing of calls for in-roamers or incorrect routing of calls. To prevent this, MCC
MNC configuration on the MSC / Mediation and Billing systems need to be cross checked with
the MCC MNC list obtained from marketing (corresponding to the roaming agreements that
serving ope rator has entered into).

6. Frequency of the Activity:

This activity is a manual activity and should be performed bi-monthly on a periodic basis. This
activity can be automated in RA tool.
7. Data Sources to be used:

Source Network
# Data Description Function Name SPOC
Element

1 MCC MNC Dump INTEC Roam System IT Operations <TBD>

2 MCC MNC Dump Network (PGW and IMS) IT Operations <TBD>

3 MCC MNC Dump Passive Mediation IT Operations <TBD>

4 Business master MCC MC Business Business <TBD>

8. Activity Overview:
This control is a 4way reconciliation between Business Master vs. Mediation vs. Network and
INTEC Roam to ensure that all MCC MNC codes of in-roaming operator subscribers are
configured in network and billing as per the agreement and business requirement.

9. Probable Exceptions:
 Present in IMS/PGW but missing in Master (Agreement in Test or no agreement)
 Present in IMS/PGW missing in INTEC ROAM or Mediation
 Present in INTEC Roam but missing in IMS/PGW and Mediation
 Present in INTEC Roam/ Mediation and missing in Master.
 Present in Master but missing Mediation and INTEC Roam system
 Present in Master but Missing in IMS/PGW
 Service Type Mismatch between INTEC billing system and Business master.

10. Reference file and Information:

Network TADIG
code MCC MNC codes
 11. Work-steps for control execution:
A. Data Validation and Normalization:
Following fields must be present in the data requested:
 Marketing MCC MNC List – TADIG, MCC-MNC, Operator Name, Launch date,
Roaming Type (Bilateral, Only In roaming, Only Out roaming)
 IMS & PGW MCC MNC List – IMS & PGW wise MCC-MNC code
 Mediation MCC MNC List – MCC-MNC code
 INTEC Roam Billing MCC MNC List – TADIG, MCC-MNC, Operator Name,
Roaming Type (Bilateral, Only In roaming, Only Out roaming)

RA to follow up and ensure data is obtained in time. The data obtained should be
in the required format

B. After the rate is received and verified, data analysis is carried out, MCC MNC reconciliation is
performed in between
a. IMS, Mediation, Business Master and billing for Voice services
b. PGW, Mediation, Business Master and Billing for data services
C. Take out the unique MCC-MNC codes from IMS/PGW and map it keeping the base with
Business master, Mediation and INTEC Roam system.
D. Escalate all the following issues:
a. Present in IMS/PGW but missing in Master (Agreement in Test or no agreement)
b. Present in IMS/PGW missing in INTEC ROAM or Mediation
E. Take the full MCC MNC dump from INTEC Roam and compare the same with business Master
for the services as per the agreement (Only out-roaming, Only In-roaming and Bilateral)
F. Escalate cases where commercial agreements are not present or marked as Test but still live
in the INTEC Roam system.
G. Escalate all the cases where the service type is incorrectly updated in ROAM system.
H. Take the INTEC Roam dump and compare the same with Mediation and IMS/PGW and
escalate the following cases:
a. Present in Billing but missing in IMS/PGW and Mediation
I. Take the Business master as base and map INTEC Roam system, IMS/PGW and Mediation
dumps for reconciliation. This will provide the following exceptions:
a. Present in Master but missing Mediation and INTEC Roam system
b. Present in Master but Missing in IMS/PGW.
J. Following are all the exceptions:
a. Present in IMS/PGW but missing in Master (Agreement in Test or no agreement)
b. Present in IMS/PGW missing in INTEC ROAM or Mediation
c. Present in INTEC Roam but missing in IMS/PGW and Mediation
d. Present in INTEC Roam/ Mediation and missing in Master.
e. Present in Master but missing Mediation and INTEC Roam system
f. Present in Master but Missing in IMS/PGW
g. Service Type Mismatch between INTEC billing system and Business master.

12. Exceptions reports generated :

a. Present in IMS/PGW but missing in Master: Agreement for these cases are not
prepared or made live but configured in the Network. RA to confirm the status of
these agreements and clean these cases from Network.
b. Present in IMS/PGW missing in INTEC ROAM or Mediation: These cases need
to be send to IT operations to rectify as here the in-roamers can use the service but
the CDRs are rejected in Mediation or billing. After verifying the agreement these
cases need to be configured in Mediation and billing system.
c. Present in INTEC Roam but missing in IMS/PGW: These cases need to be send
to IT operations to rectify. After verifying the agreement these cases need to be
removed from Mediation and Network system.
d. Present in INTEC Roam or Mediation but missing in Master: These cases
need to be send to IT operations to rectify. After verifying the agreement these
cases need to be removed from INTEC Roam or Mediation.
e. Present in Master but missing in all system or any system: These cases need
to be sent to network and IT operation for rectification. After verifying the
agreements these cases to be sent to configure in all the system.
f. Service Type Mismatch between INTEC billing system and Business master:
These cases need to be sent to network and IT operation for rectification. After
verifying the agreements these cases to be updated as per the cases.