PnC Elements Callflow_Diagram_Capacity.pptx
-
Upload
alma-a-aquino -
Category
Documents
-
view
10 -
download
0
Transcript of PnC Elements Callflow_Diagram_Capacity.pptx
Prepaid & Charging Platforms Call flow and Diagram
Network Technical GroupNetwork Service Platform Division
December 18, 2013
NSN-INGHP
NSN IN NETWORK DIAGRAM
C@O3 C@O4
IPD IPD
ApplicationsAMAX, New
Frontier
NSN IN- Valero:
IVR
HTTP
ISUPSigtran
Nokia INAP
Nokia INAP
IP
CMD
C@O5 C@O6 C@O1 C@02
IPD IPDNSN IN-Aurora
IVR
HTTP
ISUP
Nokia INAP
IP
CMD
SMSC
C@O7
IPD
NSN IN-San Juan
IP
Nokia INAPSG7000
MSC/MSS
4
NSN IN Platform Capacity
NSN IN 1-6 NSN IN7
Total SS7 Hits Capacity 5M BHCA 4M BHCA
Total IP Hits Capacity 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 CMD4. Barring/Debarring Server – 4 BDS5. Backup and Restore Server – 4 B&R6. Voucher Ordering Management System – 2 VOMS
HT-OCS / TamarindTM & Unlivoice
TM OCS/TAMARIND Network Diagram
CBP1CBP2
SLB/BMPSLB/BMP
ApplicationsAMAX, New
Frontier
TM OCS- Valero:
IVR
HTTP
ISUP
IP
CBP3 CBP1CBP2
Aurora
IVR
ISUP
IP
San Juan
CBP3 CBP1CBP2
IP
CBP3
SigtranCAP2/3
SG7000 MSC/MSS
CBP4(GHP
Tamarind)
CBP4(GHP
Tamarind)
Lahug
CBP7CBP8
IP
CBP9CBP4
(GHPTamarind)
7
TM OCS Platform Capacity
Licensed Subs Provisioned Subs Capacity
Total Subscriber 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 BMP4. Unified Signal Access Unit (USAU) - 4 USAU (1 per site) 5. Signaling Load balancer – 2 SLB6. General Front-End Point – 16 GFEPs
8• 8
Existing Tamarind Unli-Voice Flow
NSN-IN
SG 7000
HT OCS/Tamarind
TOOLBOX
New Frontier: Provisioning/Deprovisioning of Unli-voice promos.
HT Core Network
New Frontier
BMP
Tamarind/Voice Traffic
1. Voice trigger to Core Network
2. Core Network route the voice transactions to TM OCS/Tamarind platform.
3. Tamarind Platform will check if the subs have UNLI-voice flag.
4. If valid Tamarind subs, NASH will send continue message to Core
9• 9
Existing Tamarind Handover Flow
1. Voice trigger to Core Network
2. Core Network route the voice transactions to Tamarind Platform.
3. Tamarind Platform will check if the subs have UNLI-Voice flag.
4. If NOT valid Tamarind subs, Tamarind will handover the request to IN via SG7000.
5. SG 7000 will route the transactions to correct IN destination.
6. If valid subs on IN, IN will send continue message to Core via SG7000.
Voice call Handover to IN/Toolbox
NSN-IN
SG 7000
HT OCS/Tamarind
TOOLBOX
New Frontier: Provisioning/Deprovisioning of Unli-voice promos.
HT Core Network
New Frontier
BMP
Tamarind/Voice Traffic
Acision DUOVirtual Landline
Acision DUO Network Diagram
HLR
MSSMGW
MSC
TMSC
NGN
IGF
TOLL
Virtual Number Platform
IPBN
FSC
ACE
ALG
INNOVE LEC
Routed to Globelines, PLDT, other
LECs
MO Sparrow
Called Sparrow
IN (C@O)
Acision DUO Platform Capacity
Acision DUO
Total Capacity (TPS) 222 TPS
Subscriber Capacity 1M
Hardwares:1. Acision Charging Engine (ACE) - 2 ACE Servers2. Acision Location Gateway (ALG) - 3 ALG
Servers3. 2 FSC
Existing DUO Service Flow
NSN-IN
Core Network SG 7000
DUO Traffic
HT OCS
TOOLBOX
DUO Service
New FrontierProv/Deprov of DUO Service
Voice call & SMS Handover to IN/Toolbox
Acision DUO
ITP
1. MOC done by Sparrow subscriber.2. MSC(or MSS) will trigger VNP3. 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 A-number 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.
NASHUnli-SMS
NASH (Unli-SMS) Network Diagram
INAP/CAP
HT MSS
BMP
New FrontierSOAP
USAU
SEE
NASH (Unli SMS)
HT OCSNSN IN
SDU
USAU
SDU
Valero Aurora
SEE
SFTPORS/ODS
IP GAIN Network (NE 40)
IP GAIN Network (NE 40)
IPBNIPBN
HT SCP
HT SG7000
NASH Platform Capacity
NASH Valero NASH Aurora BMP Capacity
Total Capacity 14,940 CAPS 14,940 CAPS 750 TPS
Hardwares:1. Service Execution Environment (SEE) - 18 SEE (9 SEE per site)2. Service Data Unit (SDU) - 14 SDU3. Business Management Point (BMP) - 4 BMP DB, 8 BMP APP4. Unified Signal Access Unit (USAU) - 2 USAU (1 per site)
Existing NASH Unli-SMS Flow
NSN-IN
SG 7000
HT OCS
TOOLBOX
UNLI-SMS UNLI-SMS
New Frontier: Provisioning/Deprovisioning of Unli-SMS promos.
HT Core Network
New Frontier
BMP
NASH/SMS Traffic
NASH VALERO NASH AURORA
1. SMS trigger to Core Network
2. Core Network route the SMS transactions to NASH Platform. Load shared on 2 NASH sites.
3. NASH Platform will check if the subs have UNLI-SMS flag.
4. If valid NASH subs, NASH will send continue message to Core
Existing NASH SMS Handover Flow
NSN-IN
SG 7000
HT OCS
TOOLBOX
UNLI-SMS UNLI-SMS
New Frontier: Provisioning/Deprovisioning of Unli-SMS promos.
HT Core Network
New Frontier
BMP
NASH/SMS Traffic
NASH VALERO NASH AURORA
1. SMS trigger to Core Network
2. Core Network route the SMS transactions to NASH Platform. Load shared on 2 NASH sites.
3. NASH Platform will check if the subs have UNLI-SMS flag.
4. If NOT valid NASH subs, NASH will handover the request to IN via Core Network.
5. SG 7000 will route the transactions to correct IN destination.
6. If valid subs on IN, IN will send continue message to Core via SG7000.
Voice call & SMS Handover to IN/Toolbox
RussiaUSSD Menu Browser
Russia UMB Network Diagram / Callflow
• 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.
ITP TARLAC2ITP TARLAC2
Valero
Cluster1MAM1
MAM1
MAM2MAM2
MAM3MAM3
MAM4MAM4
Core
STG1STG1
STG2STG2
STG3STG3
STG4STG4
ITP TARLAC1ITP TARLAC1
ITP AURORA2ITP AURORA2
ITP AURORA1ITP AURORA1
Cluster2MAM5
MAM5
MAM6MAM6
MAM7MAM7
MAM8MAM8
STG5STG5
STG6STG6
STG7STG7
STG8STG8
HLR
AMaxAMax
3PP
NFNF
HTOCSSLB
HTOCSSLB
IN
NSN IN IPD
NSN IN IPD
HT STP
Russia UMB Capacity
Russia UMB
Total Capacity 5000 TPS
Hardwares:1. Signaling Transfer Gateway (STG) – 8 STGs2. Mobile Application Manager (MAM) – 8 MAMs
Eagle / BogeyUSSD TopUp and Callback Service
Eagle Network Diagram
HT TMSS
Eagle Platform
NSN IN
MAP Server
Valero
IP GAIN Network (NE 40)
IP GAIN Network (NE 40)
IPBNIPBN
HT STP
HLR
ControlServer
TelcoBridge
SMS Server
TDM
SigTran
Eagle Capacity
Eagle CBS
Total Capacity 474,000 BHCA
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)
Eagle Service Call Flow
StevenShort Codes / Smart Call Assistant
Steven Network Diagram
HT TMSS Valero
SC/SCA Platform
Marikina
HT TMSS Bacoor
RWAPP1
RWAPP2
Steven Capacity
Short Codes Smart Call Assistant
Total Capacity 40,000 BHCA 40,000 BHCA
Hardwares:1. 2 OM Servers2. 2 SC/SCA Servers
Steven Service Flow
Skittles Service Flow
GLRGateway Location Register /Inbound Roaming Manager
GLR Diagram
Home Network Home Network Home Network
HLRHLR HLRHLR HLRHLR
Visited Network
VLRVLR
VLRVLR
SGSNSGSN
IntelliGate GLR
Pseudo HLR
Pseudo VLR/SGSN
HPMN Subscriber
GLR Diagram
SRMSRM
TMSC CANEROTMSC CANERO
Valero
Core
TMSC AURORATMSC AURORA FEP Active
FEP Active
GLR StndByGLR StndBy
SRMSRM
FEP ActiveFEP Active
GLR ActiveGLR Active
GLR Capacity
Location Updates/Sec
Total Capacity 480
Hardwares:1. 2 SRM (Signaling Relay Module)2. 1 Database Server3. 1 Provisioning Server
VLRIntelliGate GLR (IRM)
HLR
VPMN HPMN
12
3
45
6 7
89
10
1. Mobile subscriber initiates a location update to the VPMN VLR.2. VPMN VLR sends an UpdateLocation (UL) MAP message to IRM.3. IRM passes the UL message to the HPMN HLR (VLR address passed on to HLR is IRM).4. HPMN HLR returns an InsertSubscriberData (ISD) message back to the visited network.5. IRM passes the message to the VLR.6. VLR sends a response message to the IRM.7. IRM passes the response message to the HPMN HLR.8. HPMN HLR sends an ISD RESP message to IRM.9. IRM records the subscriber information obtained from the HLR’s UL message in its database. IRM
passes the message to VLR.10. VLR sends the UL RESP to MS.
IRM flow (Initial Registration)
NEW VLRIntelliGate GLR (IRM)
HLR
VPMN HPMN
OLD VLR
12
345
6
78
1. Mobile subscriber moves to a new location and initiates a location update to the new VLR.2. New VLR sends an UpdateLocation (UL) MAP message to IRM.3. IRM, utilizing the stored subscriber data, creates and sends a CancelLocation message towards the
Old VLR.4. Old VLR returns a CancelLocation RESP message to IRM.5. IRM then creates and sends an InsertSubscriberData (ISD) message to the new VLR.6. New VLR sends a response message to the IRM.7. IRM sends an UL RESP message to the new VLR.8. New VLR sends the UL RESP to MS.
IRM flow (Subsequent Registrations)