5. Hardware Platform
•
•
•
•
•
•
•
•
Oracle SUN SPARC Netra T5220
64Giga RAM
8Core(64Thread) CPU 1.2Ghz
2x300G and 2x146G Disk
Solaris 10 OS
Oracle Database E 10.2.0.4
2xQuad port Gigabit NIC
Located on Bintaro, Cibitung
and Bandung
5
6. Hardware Platform
•
•
•
•
•
•
•
•
Oracle SUN SPARC-T3
64Giga RAM
16Core(128Thread) CPU 1.2Ghz
4x300G Disk
Solaris 10 OS
Oracle Database E 10.2.0.4
2xQuad Port Gigabit NIC
Located on Surabaya
6
12. P2P Configuration
Scheme/Routing Configuration
• MMX Group A – Routing Submit to MMX Group B
Routing configuration for MMX Group A has this following order:
1st FDA; in case of FDA failed then submit to the MMX
Group B (2nd step)
2nd Submit to Path SMSC 17 MMX Cascade; in case of
failed then retry (3rd step)
3rd Submit to Path SMSC 19 MMX Cascade; in case of
failed then message will be dropped
Note: both path SMSC 17 & 19 MMX Cascade are pointed
to MMX Group B Application Group (GT 628184429000)
12
14. P2P Configuration
Scheme/Routing Configuration (3)
• MMX Group B (MMX Cascade) – Routing Submit to SMSC
Routing configuration for MMX Group B has this following order:
1st FDA; in case of FDA failed then submit to SMSC (2nd
step)
2nd Submit to Path SMSC 19 Cascade Group; in case of
failed then retry (3rd step)
3rd Submit to Path SMSC 20 Cascade Group; in case of
failed then retry (4rd step)
4rd Submit to Path SMSC 21 Cascade Group; in case of
failed then message will be dropped
Note: all path SMSC 19, 20, 21 Cascade Group are
pointed to SMSC Comverse & Huawei
14
17. P2P Services
• Enhanced MAP MO-ForwardSM (+ Location
Information)
• Location based charging using ATI
• Cascaded MMX
• FDA retry mechanism
17
18. P2P Services
Enhanced MAP MO-ForwardSM (+ Location Information)
• MSC send MAP v2 enhanced which contains location
information
Location Information:
MCC + MNC + LAC + CI
18
19. P2P Services
Location based charging using ATI
• Configured at control plan
• There will be a checking on control plan to check if
Location Information sent by MSC
• If not then ATI for A-party will be invoked
19
20. P2P Services
Cascaded MMX
• Designated to reduce the load of SMSC
• Before:
Whenever the SMS traffic is failed to be delivered to
the MSC, it will be failed over (submit) to SMSC
20
21. P2P Services
Cascaded MMX (2)
• After:
XL has introduced 2 different groups of MMX which is
described as follow:
MMX Group A : handling FDA & Charging, in case of
failure then message will be failed over to the SMSC. In
this case MMX Group B is configured as the SMSC within
MMX Group A point of view.
MMX Group B (MMX Cascade) : handling Second Delivery
Attempt (without any charging). This groups is configured
within single application group in ITP with GT
628184429000
21
22. P2P Services
FDA retry mechanism
• FDA retry will be invoked for any release cause which
has “Path Fail” = “No”
22
23. P2P Services
FDA retry mechanism (2)
• XL has not applied the FDA retry on Production yet,
this could be shown from picture below : “Retries” and
“Interval” = 0
23
31. P2A Services
• P2A with below SDCs:
SDCs without charging: 4444, 444, 7857, 3935, 5566,
9796, 9797, 9787, 4449, 44449, 5838, 46500, 9767,
97671, 567, 5255, 461, 8484, 6774
SDCs with charging: 5252, 5255, 567, 3399, 799
This message will be routed to SMSC
• Other SDCs besides above SDCs (failed to obey the
ITP MLR Rule):
SMS with empty TCAP_END (>= 140 chars)
Segmented message (> 160 chars)
This message will be routed to A2P/P2A box
This message will not be charged
31
