Details for RA Control Implementation

1. Background:

RJIL Network for Voice & messaging is based on new generation IMS Architecture. In IMS domain
all the breakout traffic, viz. Local [Mobile/Fixed], NLD and ILD are handled by MGCF/MGW. The
POI would be realized by having an MGW in the Network. Multiple types of access network such
as LTE and FTTX etc. would be served by IMS Network and they will be interconnected for
different type of incumbent operators such as UASL, Basic, NLD, & ILD. For traffic terminating on
other operators network and traffic provided for to carrier to terminate the same to other
operator, these carrier/ terminating operator will raise invoice for the network used based on the
usage made. These invoices has to be settled within due dates.

Figure 1 – Voice Call flow

Detailed Flow:

Architecturally the Network node planned at Regional Level, e.g. Eastern, Northern, Western and
Southern, as it would only handle the signaling switching and MGWs would be placed at every
Circle level [AG3/AG2 locations], as it carries the Bearer Traffic to enable POI within JIO and with
other operator. B-table information is collated from all the Network nodes and compared against
the NPE master to ensure proper routing of call.

2. Risks covered:

Impact
Risk
Risk Root Cause Customer Revenue / Others Severity
#
Experience Leakage
Missing Level Level Information not
Configuration available from other
operators.
R1
Level missed to    High
configure in network
nodes.
Overflow Traffic / Frequent overflow for
Congestion a specific code/POI,
switch needs to
R2 action as per the   High
standard procedure.
 3. Control Name:

B-Number and Routing Validation – NSS B-table master vs NPE master.

4. Control Objective:

To ensure accurate rating is carried out by NSS.

5. Control Description:

This Activity is very essential for accurate routing by implementing appropriate routing rules and
number levels in NSS systems which helps in mitigating revenue leakage and routing issues.

6. Frequency of the Activity:

Monthly

7. Data Sources to be used:

Source Network
# Data Description Function Name SPOC
Element

1 NSS B-table master NSS IT Operations <TBD>

2 NPE master ROCRA IT Operations <TBD>

8. Activity Overview:

 Following activities are automated in RA Tool (SUBEX)

o Count and record of NSS B number Vs. Network master B Number

o NSS Routing Table vs Network Routing master.

9. Probable Exceptions:

 Incorrect/ Missing configurations by the MGCF/TAS Team

 Deviation due to technical reasons like Link failure etc.

10. Reference file and Information:

11. Work-steps for control execution:

` Reconciliation:
  B table Dump is taken from NSS Network team for all nodes and sent to ROCRA with basic
information like destination code/B number and the primary - secondary routing Carrier
information.
 Latest Network master table for B number and LCR need to be taken from NPE and Carrier
Business team respectively which is then sent to ROCRA.
 ROCRA will perform reconciliation with the following defined matching keys and Business
rules :
o TREE – the field value denotes the ton type
 International - 8,10,12 & 20
 NLD – 3,5 & 7
 Toll free and Special service codes - 2021
o DIGITS – the field denotes the b-number value
o NDEST – the field denotes the trunk group used for routing
o NSDEST – The field denotes the service category indicator like – Call-forwarding,
National roaming, Bearer Call etc.
 If deviation is observed for any dialled digit routing, exceptions are reported to network team for
necessary action like configuration or routing correction.

12. Exceptions reports generated

 Missing configurations in NSS

o These usually occur due to B Number information present in NPE network master and
missing in NSS. Analyst should check whether the number level information was sent to
network operation team for configuration and in case of discrepancy report it to the
Network operation team.
 Missing configurations in NPE – Network master:
o These usually occur due to B Number information missing in NPE network master
and present in NSS. Analyst should check whether the number level information was sent to
network operation team for deletion and missed by network operation team.
 Mismatch in Routing configuration:
o These usually occur due to routing information present in both NPE network master
and in NSS but discrepancy in business rules. Analyst should check root cause of the
mismatch and provide appropriate action to respective teams for correction.