XL Messaging Manager P2P - TOK

1

<Insert Picture Here>

XL Messaging Manager P2P - TOK

Tri Yanni Karyuliati

Senior Technical Support Engineer

3


Course Agenda

• Hardware Platform

• Software Release

• P2P Configuration

• P2P Services

• P2P Call Flows

• Some of P2A Services

• P2A Call Flows

• Sample of EDR

4


Hardware Platform

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

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

7


Software Release

8

Software Release

• SMS 3.1.2.6

• SLEE 3.2.0.23

• ACS 2.4.3.3

• CCS 3.1.4.1

• EAX 3.0.7.0

• XMS 4.0.3.3

• SIGTRAN 1.2.2

• RIMS 3.1.2.2

• LCP 1.0.5.0

Charging Max 4.3 Software Version with the

following Modul version :

9


P2P Configuration

10

P2P Configuration

• SLEE.cfg – multiple xmsTrigger instances

INTERFACE=xmsIf1 xmsTrigger1.sh /IN/service_packages/XMS/bin EVENT






..

SERVICEKEY=INTEGER 0x1060000002d xmsIf1 #SRI

SERVICEKEY=INTEGER 0x1080000002e xmsIf1 #SMS-MO

SERVICEKEY=INTEGER 0x10800000031 xmsIf1 #AlertSC


SERVICEKEY=INTEGER 0x1080000002c xmsIf1 #SMS-MT

SERVICEKEY=INTEGER 0x108ffffffff xmsIf1

..

SERVICEKEY=INTEGER 0x6060000002d xmsIf6 #SRI

SERVICEKEY=INTEGER 0x6080000002e xmsIf6 #SMS-MO



SERVICEKEY=INTEGER 0x6080000002c xmsIf6 #SMS-MT

SERVICEKEY=INTEGER 0x608ffffffff xmsIf6

11

P2P Configuration

• XMS configuration

allowIncomingMap3 = true

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)

13

P2P Configuration

Scheme/Routing Configuration (2)

14

P2P Configuration


• 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


3rd Submit to Path SMSC 20 Cascade Group; in case of


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

15

P2P Configuration


16


P2P Services

17

P2P Services

• Enhanced MAP MO-ForwardSM (+ Location

Information)

• Location based charging using ATI

• Cascaded MMX

• FDA retry mechanism

18

P2P Services

Enhanced MAP MO-ForwardSM (+ Location Information)

• MSC send MAP v2 enhanced which contains location

information

Location Information:

MCC + MNC + LAC + CI

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

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

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

22

P2P Services

FDA retry mechanism

• FDA retry will be invoked for any release cause which

has “Path Fail” = “No”

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

24


P2P Call Flow

25

P2P Call Flow

FDA Only

26

P2P Call Flow

FDA – Failover SMSC

27

P2P Call Flow

FDA Only (with ATI invocation)

28

P2P Call Flow

FDA – Failover SMSC (with ATI invocation)

29

P2P Call Flow

MMX Cascade

30


P2A Services

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

32


P2A Call Flow

33

P2A Call Flow

Failover to SMSC

34


Sample of EDR

35

Sample of EDR

MMX EDR – P2P

• FDA Succeed

TYPE=1|DATE=20110302075258|IPRN=MAP|OAID=MAP1|MSCA=001001628184450090|OADR=001001628179401039|DADR=

001001628179416567|IPRI=PriorityUrgent|MTYP=0|MSGD=1|SRCL=001001628184424306|MSGR=66|USRD=xxx|ALPH=GSM7

Bit|ULEN=21|TLEN=23|PRID=0|STRR=1|VP=604800|NRQ=1|SEGN=0|SEGT=0|OIMSI=510110210062503|OLOC=510.11.25317.

38984|DLOC=|DELTS=20110302075258|OPRN=MAP|TAID=MAP1|DPATH=MAP_SME_MAP1|MSCA=001001628184450090|O

ADR=001001628179401039|DADR=001001628179416567|OPRI=PriorityUrgent|MSGD=0|PRES=1|SRCL=001001628184424306

|STRR=1|DSTL=001001628184424310|DIMSI=510110204322364|RESL=0

• FDA failover to MMX Cascaded

TYPE=1|DATE=20110302082457|IPRN=MAP|OAID=MAP1|MSCA=001001628184450090|OADR=0010016287734501207|DADR

=0010016285725922636|IPRI=PriorityUrgent|MTYP=0|MSGD=1|SRCL=001001628184424306|MSGR=134|USRD=xxx|ALPH=GS

M7Bit|ULEN=35|TLEN=39|PRID=0|STRR=1|VP=38102400|NRQ=1|SEGN=0|SEGT=0|OIMSI=510111408024801|OLOC=510.11.

25375.24975|DLOC=|DELTS=20110302082457|OPRN=MAP|TAID=MAP1|DPATH=MAP_SME_MAP1|MSCA=001001628184450

090|OADR=0010016287734501207|DADR=0010016285725922636|OPRI=PriorityUrgent|MSGD=0|PRES=1|SRCL=00100162818

4424306|STRR=1|DSTL=001001628160473000|DIMSI=510012541491452|PERR=error-

27|DISTS=20110302082510|DELTS=20110302082510|DSCA=62818445009|DSCGT=628184429000|OPRN=MAP|TAID=MAP1|

DPATH=SMSC 17 MMX

Cascade|MSCA=001001628184450090|OADR=0010016287734501207|DADR=0010016285725922636|OPRI=PriorityUrgent|MS

GD=1|PRES=1|SRCL=001001628184424306|STRR=1|RESL=0

36

Sample of EDR

MMX EDR – P2P (2)

• FDA failover to SMSC

TYPE=1|DATE=20110302083030|IPRN=MAP|OAID=MAP1|MSCA=00100162818445009|OADR=0010016281908290114|DADR=

001001622199379216|IPRI=PriorityNormal|MTYP=0|MSGD=1|SRCL=00100162818445823|MSGR=210|USRD=xxx|ALPH=GSM7

Bit|ULEN=52|TLEN=59|PRID=0|STRR=1|VP=38102400|NRQ=1|SEGN=0|SEGT=0|DELTS=20110302083030|OPRN=MAP|TAID=

MAP1|DPATH=MAP_SME_MAP1|MSCA=00100162818445009|OADR=0010016281908290114|DADR=001001622199379216|O

PRI=PriorityNormal|MSGD=0|PRES=1|SRCL=00100162818445823|STRR=1|DSTL=001001622192600421|DIMSI=51002199379

216|PERR=error-

27|DISTS=20110302083031|DELTS=20110302083031|DSCA=62818445009|DSCGT=62818445897|OPRN=MAP|TAID=MAP1|D

PATH=SMSC 19 Cascade

Group|MSCA=00100162818445009|OADR=0010016281908290114|DADR=001001622199379216|OPRI=PriorityNormal|MSGD=

1|PRES=1|SRCL=00100162818445823|STRR=1|RESL=0

37

Sample of EDR

EAX EDR

SMS Charge request.

Protocol Version . . . . . . . . 210

Message Length . . . . . . . . . 428

Message Type . . . . . . . . . . SMS Charge

Timestamp . . . . . . . . . . . 1299052378 (Wed Mar 2 07:52:58 2011)

SCP ID . . . . . . . . . . . . . 340

Session ID . . . . . . . . . . . 658757370

Request Number . . . . . . . . . 1

Service key . . . . . . . . . . 430

MSC Call ID . . . . . . . . . . 0

Subscriber key type . . . . . . MSISDN

Subscriber key . . . . . . . . . 000-628179401039

Calling Number Address . . . . . 000-628179401039

Destination Number Address . . . 000-628179416567

Original Dialled Digits . . . . 628179416567

Original Cell ID . . . . . . . . 510.11.25317.38984

Terminating Cell ID . . . . . .

Bearer Type . . . . . . . . . . Other

Unit Type . . . . . . . . . . . SMS

Retry Count . . . . . . . . . . 0

Call Start Time . . . . . . . . 1299052378 (Wed Mar 2 07:52:58 2011)

Total Units . . . . . . . . . . 1

Alternate Unit Type . . . . . . Not Defined

Alternate Total Units . . . . . 0

Negotiated QOS . . . . . . . . . <Undefined>

Access Point Name . . . . . . .

User IP Address . . . . . . . .

Refund Indicator . . . . . . . . no

38

Sample of EDR

EAX EDR (2)

SMS Charge response.

Protocol Version . . . . . . . . 210

Message Length . . . . . . . . . 16

Message Type . . . . . . . . . . SMS Charge

Timestamp . . . . . . . . . . . 1299052378 (Wed Mar 2 07:52:58 2011)

SCP ID . . . . . . . . . . . . . 340

Session ID . . . . . . . . . . . 658757370

Response status . . . . . . . . Success

Balance Type . . . . . . . . . . Rupiah

Session Charge . . . . . . . . . 0

Remaining Balance . . . . . . . 11618

39

Thank You

Technology

XL Messaging Manager P2P - TOK