Prepaid & Charging Platforms

Call flow and Diagram

Network Technical Group
Network Service Platform Division
December 18, 2013

NSN-IN
GHP

NSN IN NETWORK DIAGRAM

A
Ap
pp
pli
lic
ca
attio
ion
ns
s
A
A
AM
X
MAX,, N
e
New
w
F
Frro
on
nttiie
err

NSN INValero:

SMSC

HTTP

IPD IPD

NSN INAurora

CMD
IP

NSN INSan Juan

HTTP

IPD IPD

CMD

IP

IVR C@O3 C@O4 C@O5 C@O6

IVR C@O3 C@O4 C@O5 C@O6

IPD
IP

IVR C@O1 C@02

IVR C@O1 C@02

C@O7
C@O7

ISUP
ISUP

Sigtran
Nokia INAP
Nokia INAP

SG7000
SG7000
S
SS
//M
MS
C
C
S
S
M
M

Nokia INAP

Nokia INAP

NSN IN Platform Capacity

Total SS7 Hits Capacity

Total IP Hits Capacity

NSN IN 1-6

NSN IN7

5M BHCA

4M BHCA

1.1M BHCA

1M BHCA

Hardwares:
1. Service Execution Point (SEP) - 7 SEP (additional 1 SEP 1Q 2014)
2. IP Dispatcher (IPD) - 5 IPD (16 IPDP routing node)
3. CDR Mediation Device (CMD) 4 CMD
4. Barring/Debarring Server 4 BDS
5. Backup and Restore Server 4 B&R
6. Voucher Ordering Management System 2 VOMS
4

HT-OCS / Tamarind
TM & Unlivoice

TM OCS/TAMARIND Network
Diagram
Ap
App
pli
lic
ca
attiio
on
ns
s
A
M
AMA
X
,
AX, N
e
w
New
F
Frro
on
nttiie
err

TM OCSValero:

HTTP

Aurora

San Juan

SLB/BMP
SLB/BMP
IP

IP

Lahug

IP

IP

CBP4 IVR
CBP4
CBP4
IVRCBP1CBP2CBP3
CBP8 CBP9
CBP1CBP2 CBP3
CBP1CBP2 CBP3
(GHP
(GHP
(GHP CBP7
CBP4
CBP4
CBP4
IVRCBP1CBP2CBP3 (GHP
IVR CBP1CBP2 CBP3 (GHP
Tamarind)
Tamarind)
Tamarind)
CBP1CBP2 CBP3 (GHP
CBP7CBP8 CBP9
Tamarind)

ISUP

Tamarind)

ISUP

Sigtran
CAP2/3

SG7000
SG7000
S
S
SS
M
/
M
/
C
C
S
S
M
M

Tamarind)

TM OCS Platform Capacity

Total Subscriber Capacity

Licensed Subs

Provisioned
Subs Capacity

21M

28.5M

Hardwares:
1. Convergent Billing Point 15 CBPs (12 CBPs for TM & TM
Tamarind, 3 CBPs for GHP Tamarind)
2. Signaling Control Point 28 SCPs
3. Business Management Point (BMP) 19 BMP
4. Unified Signal Access Unit (USAU) - 4 USAU (1 per site)
5. Signaling Load balancer 2 SLB
6. General Front-End Point 16 GFEPs
7

Existing Tamarind Unli-Voice Flow

Tamarind/Voice Traffic

1.
2.
3.
4.

Voice trigger to Core

Network
Core Network route the
voice transactions to TM
OCS/Tamarind platform.
Tamarind Platform will
check if the subs have
UNLI-voice flag.
If valid Tamarind subs,
NASH will send continue
message to Core

HT Core
Network

TOOLB
OX

SG
7000
NSNIN

HT
OCS/Tamarind
BMP

New Frontier:
Provisioning/Deprovisioning
of Unli-voice promos.

New Frontier

Existing Tamarind Handover Flow

Tamarind/Voice Traffic

1.
2.
3.
4.

5.
6.

Voice trigger to Core

Network
Core Network route the
voice transactions to
Tamarind Platform.
Tamarind Platform will
check if the subs have
UNLI-Voice flag.
If NOT valid Tamarind
subs, Tamarind will
handover the request to
IN via SG7000.
SG 7000 will route the
transactions to correct IN
destination.
If valid subs on IN, IN
will send continue
message to Core via
SG7000.

Voice call
Handover to
IN/Toolbox
TOOLBOX

HT Core
Network

SG
7000
NSNIN

HT
OCS/Tamarind
BMP

New Frontier:
Provisioning/Deprovisioning
of Unli-voice promos.

New Frontier

Acision DUO
Virtual Landline

Acision DUO Network Diagram

HLR
ACE
MGW

MSS
FSC
ALG

MS
C

Virtual
Number
Platform

IPBN

MO Sparrow
IGF
IN
(C@O)

TMSC

NGN

Called Sparrow

TOLL
Routed to
Globelines,
PLDT, other
LECs
INNOVE
LEC

Acision DUO Platform Capacity

Acision DUO
Total Capacity (TPS)

222 TPS

Subscriber Capacity

1M

Hardwares:
1. Acision Charging Engine (ACE) - 2 ACE Servers
2. Acision Location Gateway (ALG) - 3 ALG
Servers
3. 2 FSC

Existing DUO Service Flow

1. MOC done by Sparrow subscriber.
2. MSC(or MSS) will trigger VNP
3. FSC will change the A-number MSISDN
to Sparrow landline number. It will
check B-number; if it is Sparrow
landline number then it will change it
to original MSISDN. This will be
passed to ACE.
ACE will check the subscription of Anumber as well as B-number. It will
send location info of A-number to
ALG for matching.
ALG will check if A-subs is in its
registered location. It will also do
MAP ATI to the HLR of B-subs, if the
B-number called is a Sparrow
number.
4.
If all criteria were met, it will send a
call connect back to the MSC, with
A-number change to Sparrow
landline #. B-number will have prefix
if it is a landline number.
5.
MSC will route the call to the TMSC.
6.
TMSC will route the call to NGN if
the B-number is a landline #, if not it
will route it accordingly.
7.
NGN will route the call to the
nearest Innove LEC for it to be
connected to the called number
8.
If criteria are not met, call will be
rerouted to IN for charging if A
number is prepaid. If A is postpaid,
DUO will send a continue message
to MSC.

DUO Traffic

TOOLB
OX

SG
7000

Core Network

Voice call & SMS

Handover to
IN/Toolbox

HT
OCS

ITP
NSN-IN

DUO
Service

Acision DUO

New Frontier

Prov/Deprov of
DUO Service

NASH
Unli-SMS

NASH (Unli-SMS) Network Diagram

NSN IN

NASH (Unli
SMS)

HT OCS

HT SG7000

BMP
IPBN
IPBN

SEE

SDU

SEE

SDU

ORS/ODS
USAU

Valero

USAU

Aurora

SFTP

IPIPGAIN
GAIN
Network
Network(NE
(NE
40)
40)

New Frontier
SOAP
INAP/CAP

HT SCP

HT MSS

NASH Platform Capacity

NASH Valero
Total Capacity

14,940 CAPS

NASH
Aurora

BMP Capacity

14,940 CAPS 750 TPS

Hardwares:
1. Service Execution Environment (SEE) - 18 SEE (9 SEE per site)
2. Service Data Unit (SDU) - 14 SDU
3. Business Management Point (BMP) - 4 BMP DB, 8 BMP APP
4. Unified Signal Access Unit (USAU) - 2 USAU (1 per site)

Existing NASH Unli-SMS Flow

NASH/SMS Traffic

1.
2.

3.
4.

SMS trigger to Core

Network
Core Network route the
SMS transactions to
NASH Platform. Load
shared on 2 NASH sites.
NASH Platform will
check if the subs have
UNLI-SMS flag.
If valid NASH subs,
NASH will send continue
message to Core

TOOLB
OX

HT Core
Network

SG
7000
NSNIN

UNLISMS

UNLISMS

BMP
NASH VALERO

NASH AURORA

New Frontier

New Frontier:
Provisioning/Depro
visioning of UnliSMS promos.

HT
OCS

Existing NASH SMS Handover Flow

NASH/SMS Traffic

1.
2.

3.
4.

5.
6.

SMS trigger to Core

Network
Core Network route the
SMS transactions to
NASH Platform. Load
shared on 2 NASH sites.
NASH Platform will
check if the subs have
UNLI-SMS flag.
If NOT valid NASH subs,
NASH will handover the
request to IN via Core
Network.
SG 7000 will route the
transactions to correct IN
destination.
If valid subs on IN, IN
will send continue
message to Core via
SG7000.

Voice call & SMS

Handover to
IN/Toolbox
TOOLB
OX

HT Core
Network

SG
7000
NSNIN

UNLISMS

UNLISMS

BMP
NASH VALERO

NASH AURORA

New Frontier

New Frontier:
Provisioning/Depro
visioning of UnliSMS promos.

HT
OCS

Russia
USSD Menu Browser

Russia UMB Network Diagram / Callflow

Cluster1

HLR
HT STP

ITP TARLAC1
ITP TARLAC1

Core

ITP TARLAC2
ITP TARLAC2

MAM1
MAM1

STG2
STG2

MAM2
MAM2

STG3
STG3

MAM3
MAM3

STG4
STG4

MAM4
MAM4

NF
NF
AMax
AMax

3PP

Cluster2
ITP AURORA1
ITP AURORA1
ITP AURORA2
ITP AURORA2

STG1
STG1

All traffic is routed via the Common GT 639170000433.

The traffic is load shared between the two current
clusters, Cluster1 (639170000431) and Cluster2
(639170000432). One Cluster consists of 4 STGs and 4
MAMs.

STG5
STG5

MAM5
MAM5

STG6
STG6

MAM6
MAM6

STG7
STG7

MAM7
MAM7

STG8
STG8

MAM8
MAM8

Valero

NSN IN
NSN IN
IPD
IPD
HTOCS
HTOCS
SLB
SLB

IN

Russia UMB Capacity

Russia UMB
Total Capacity

5000 TPS

Hardwares:
1. Signaling Transfer Gateway (STG) 8 STGs
2. Mobile Application Manager (MAM) 8 MAMs

Eagle / Bogey
USSD TopUp and Callback Service

Eagle Network Diagram

Eagle Platform
TDM

TelcoBridge

HLR

HT STP

SigTran

Control
Server

MAP Server

HT TMSS

IPIPGAIN
GAINNetwork
Network
(NE
(NE40)
40)

SMS Server
IPBN
IPBN

Valero
NSN IN

Eagle Capacity

Eagle CBS
Total Capacity

Hardwares:
1. 2 Map Servers (Load Sharing)
2. 2 Control Servers (Active / Standby)
3. 2 SMS Servers (Load Sharing)
4. 2 TelcoBridge (Load Sharing, 48 E1s)

474,000 BHCA

Eagle Service Call Flow

Steven
Short Codes / Smart Call Assistant

Steven Network Diagram

SC/SCA Platform

RWAPP1
HT TMSS
Valero

RWAPP2

HT TMSS
Bacoor

Marikina

Steven Capacity

Short Codes
Total Capacity

Hardwares:
1. 2 OM Servers
2. 2 SC/SCA Servers

40,000 BHCA

Smart Call
Assistant
40,000 BHCA

Steven Service Flow

Skittles Service Flow

GLR
Gateway Location Register /
Inbound Roaming Manager

GLR Diagram

GLR Diagram

SRM
SRM
FEP Active
FEP Active

Core

TMSC CANERO
TMSC CANERO

GLR Active
GLR Active

SRM
SRM
TMSC AURORA
TMSC AURORA

FEP Active
FEP Active

GLR StndBy
GLR StndBy

Valero

GLR Capacity

Location
Updates/Sec
Total Capacity

480

Hardwares:
1. 2 SRM (Signaling Relay Module)
2. 1 Database Server
3. 1 Provisioning Server

IRM flow (Initial Registration)

VPMN
IntelliGate
GLR (IRM)

VLR
1

HPMN
HLR

3
4

6
10

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

7
8

Mobile subscriber initiates a location update to the VPMN VLR.

VPMN VLR sends an UpdateLocation (UL) MAP message to IRM.
IRM passes the UL message to the HPMN HLR (VLR address passed on to HLR is IRM).
HPMN HLR returns an InsertSubscriberData (ISD) message back to the visited network.
IRM passes the message to the VLR.
VLR sends a response message to the IRM.
IRM passes the response message to the HPMN HLR.
HPMN HLR sends an ISD RESP message to IRM.
IRM records the subscriber information obtained from the HLRs UL message in its database. IRM
passes the message to VLR.
VLR sends the UL RESP to MS.

IRM flow (Subsequent Registrations)

VPMN
NEW VLR

OLD VLR

HPMN
IntelliGate
GLR (IRM)

HLR

2
3
5

4
6

8
1.
2.
3.
4.
5.
6.
7.
8.

Mobile subscriber moves to a new location and initiates a location update to the new VLR.
New VLR sends an UpdateLocation (UL) MAP message to IRM.
IRM, utilizing the stored subscriber data, creates and sends a CancelLocation message towards the
Old VLR.
Old VLR returns a CancelLocation RESP message to IRM.
IRM then creates and sends an InsertSubscriberData (ISD) message to the new VLR.
New VLR sends a response message to the IRM.
IRM sends an UL RESP message to the new VLR.
New VLR sends the UL RESP to MS.