MNP CAll Flow

Confidentiality level on slide master

Version number on slide master

Confidentiality level on title master

Version number on title master

MNP FLOW (STP)

Prepared by

Nilesh Patil



Presentation title in footer2

19 April 2023

MSS MSS

IDP ( Called GT= IN gt, Calling GT=MSS gt, CdPN)

SPGTRUL:SPGTTRL=IDPM_INT table (Called GT= IN gt Present )

PRETRUL table (Normalization of CdPN to International number)

1)NPENTRY table( CdPN=TPROF No)2)TPROF table ( TPRON No =LRN) LRN inserted before CdPN

IDP ( Called GT= IN gt, Calling GT=MSS gt, LRN+CdPN)

SPGTRUL:SPGTTRL= INTINT table (Called GT= IN gt routed to IN)

ININ

Connect (LRN+CdPN)

MOC

PREPAID Call FLOW.

SPRDOMSCCP Routing Domain. IDPM_DOM

SPCLDPAA /ECalled Party AddressSSN-SPC selector

SPCLDPAA /ECalled Party AddressSSN-SPC

SPGTPARTPartition Parts(Select GT translator IDPM_INT)

SERVPROF (select service logic sequence and how the call control shell formats response message)

NP SERVICE LOGIC

SERVSEL (will match SSID,ACN,Service Key,Event detection point and select Assoc. service prof “Idpm”)

STP



PREPAID Call FLOW.1) When a prepaid customer makes MO call , IDP is generated by MSS with Called party address(CdPA) as “IN GT” and Calling party address(CgPA) as “MSS GT”

and it also contains Called party number ( CdPN).

2) When STP receives the Message , it forwards to SPRDOM (SCCP routing domain ) table for traffic partitioning.

3) In SPRDOM table, domain “IDPM_DOM” is selected as SPRDOM type “ Local sccp Linkage “ is selected which mean all SCPs of the network belong to this domain, except for those defined in SPRDOM type “ Remote sccp Linkage”. In Next analysis step, further routing on called party address (SPCLDPAA table = IDPM) is specified.

4) In SPCLDPAA table, next step analysis as “default routing” is defined for messages which do not fulfill any conditions in SPCLDPAAE table of the SPCLDPA.

5) In SPCLDAPAAE table “list of Called SSN” is specified with next step analysis as SPUOCA table. If Called SSN of the messages is present in the list , the defined SPUOCA(User operation codes) is selected else default routing is performed.

6) In SPUOCA table, next step analysis as “default routing” is defined for messages which do not fulfill any conditions in SPUOCAE table of the SPUOCA.

7) SPUOCAE table specifies list of “operation codes “ which are taken into account during this step with next step analysis as SPGTPART table. In this case Operation Code “ IDP “ is considered .

8) In SPGTPART ,on basis of SPUOCAE “IDPM” partition is selected and SPGTTRL “IDPM_INT” is selected.



PREPAID Call FLOW Continued….

9) In SPGTRUL table , IN GT is defined with SPGTTRL “IDPM_INT” and routed to SELF#4 i.e own database. Message is then sent to SERVSEL table.

10) In SERVSEL table, depending upon below parameter service profile (SERVPROF=IDPm) is selected.

a) Subsystem Identifier – Depends upon "called SSN and SSN-SSID relationship defined in SPSSN .

b) ACN Selector - Depends upon Application context name found in TCAP and AC name – AC selector relationship defined in “ ACN “ table.

c) Service Key - Depends upon parameter “service key “found in the operation Initial DP.

d) Event Detection Point - Depends upon parameter “event type BCSM” found in Initail DP.

11) Depending upon serivice profile “IDPm “properties , Cause value and Service no are selected.

12) Service No defines the service logic to be used. For prepaid call, Service No ”6” is used which indicates “ Manipulate service, IN IDP messages are relayed onwards after substitution of CdPN.” Then it is sent to NP application.

13) In PRETRUL table , Normalization of CdPN takes place to International Number and CdPN is sent to NPENTRY table . In NPENTRY table, CdPN (prefix or complete) will be associated with TPROF No.

14) In TPROF table ,LRN associated with TPROF No will be dipped in CdPN ( 91+LRN+CdPN.)

15) IDP is relayed to IN with CdPA as “IN GT” and CgPA as “MSS GT” and Called party number as “91+LRN+old CdPN”.

16) IN will send a “Connect “ message in Reply with Called party number as “91+LRN+old CdPN.”



POSTPAID Call FLOW.

MSS MSS

IDP ( Called GT= STP gt, Calling GT=MSS gt, CdPN)

Connect (LRN+CdPN)

MOCIAM

SRI to HLR

SPRDOMSCCP Routing Domain. IDPM_DOM


SPGTPARTPartition Parts(Select GT translator IDPM_INT)

SPGTRUL:SPGTTRL=IDPM_INT table (Called GT= STP gt Present )

SERVSEL(will match SSID,ACN,Service Key,Event detection point and select Assoc. service prof “QOD”)

SERVSEL(will match SSID,ACN,Service Key,Event detection point and select Assoc. service prof “Idpm”)

NP SERVICE LOGIC

PRETRUL table( Normalization of CdPN to International number)

1)NPENTRY table( CdPN=TPROF No)2)TPROF table ( TPRON No =LRN) LRN inserted before CdPN

SPGTRUL:SPGTTRL= INTINT table (Called GT= MSS gt routed to IN) STP



Postpaid Call FLOW.1) When a Postpaid customer makes MO call , IDP is generated by MSS with Called party address(CdPA) as “STP GT” and Calling party address(CgPA) as “MSS

GT” and it also contains Called party number ( CdPN).


3) In SPRDOM table, domain “IDPM_DOM” is selected as SPRDOM type “ Local sccp Linkage “ is selected which mean all SCPs of the network belong to this domain, except for those defined in SPRDOM type “ Remote sccp Linkage”. In Next analysis step, further routing on called party address (SPCLDPAA table = IDPM) is specified.


5) In SPCLDAPAAE table “list of Called SSN” is specified with next step analysis as SPUOCA table. If Called SSN of the messages is present in the list , the defined SPUOCA(User operation code) is selected else default routing is performed.






Postpaid Call FLOW Continued….

9) In SPGTRUL table , STP GT is defined with SPGTTRL “IDPM_INT” and routed to SELF#4 i.e. own database. Message is then sent to SERVSEL table.

10) In SERVSEL table, depending upon below parameter service profile (SERVPROF=QOD) is selected.

a) Subsystem Identifier – Depends upon "called SSN and SSN-SSID relationship defined in SPSSN .

b) ACN Selector - Depends upon Application context name found in TCAP and AC name – AC selector relationship defined in “ ACN “ table.

c) Service Key - Depends upon parameter “service key “found in the operation Initial DP.

d) Event Detection Point - Depends upon parameter “event type BCSM” found in Initial DP.

11) Depending upon service profile “QOD “properties , Cause value and Service no are selected.

12) Service No defines the service logic to be used. For prepaid call, Service No “0” is used which indicates “ QOD service, handling the trigger event Query on digits.” Then it is sent to NP application.

13) In PRETRUL table , Normalization of CdPN takes place to International Number and CdPN is sent to NPENTRY table . In NPENTRY table, CdPN (prefix or complete) will be associated with TPROF No.

14) In TPROF table ,LRN associated with TPROF No will be dipped in CdPN ( 91+LRN+CdPN.)

15) STP will send a “Connect “ message in Reply with Called party number as “91+LRN+old CdPN.”




19 April 2023

SMSCSMSC

MSS MSS

MO forwardSM

MO forwardSM

SRI for SMRequest

SPRDOM SCCP Routing Domain.) SRI_DOM


SPGTPARTPartition Parts(Select GT translator SRI_SM_INT)

SPGTRUL( SPGTTRL Name=SRI_SM_INT,GT Address Info.=919/918/917,SPGTCRUL Name=TT0TOTT11,SPGTTRLREF Name=SRI_SM_INT11

SPGTCRUL : SPGTCRUL Name=TT0TOTT11,Addr.Info Conv.Rule=+1DT, TTID=TTID : TTID : Translation Type 11;( TT 0 converted to TT 11 and “1D“ prefixed to CdPA)

SPGTRUL : SPGTTRL Name=SRI_SM_INT11,GT Address Info.=1D,Possible Ported No.=TRUE;

PRETRUL table( 1D is removed from CdPA )

1) NPENTRY table( CdPA=TPROF No)

2)TPROF table ( TPRON No =ownLRN)own LRN inserted before CdPASPGTRUL( SPGTTRL

Name=SRI_SM_INT11,GT Address Info.=91,SPGTCRUL Name=TT11TOTT0SPGTTRLREF Name=SRI_SM_INT

SPGTCRUL : SPGTCRUL Name=TT11TOTT0, TTID=TTID : TTID : Translation Type =unknown;( TT 11 converted to TT 0)

SPGTCRUL : SPGTCRUL Name=CANGT, Addr.Info Conv.Rule=.S; ( Called Party address removed from SRI Req )

SRI for SMRequest

HLRHLR

SPGTRUL( SPGTTRL Name=SRI_SM_INT,GT Address Info.=91+ownLRN+NDC Prefix,SPGTCRUL Name=CANGT,SPENS=route towards HLR;

SRI for SMResponse

MT_FSMSMS Call flow ( To Own

subscriber)



1) When a customer makes MO SMS ,” MO forwardSM” request is sent to SMSC by MSS via STP . SMSC then sends “SRI for SM “ to HLR via STP.( CdPA = B party no, CgPA = SMSC GT,CdPN)


3) In SPRDOM table, domain “SRI_DOM” is selected as for SPRDOM type “ Remote sccp Linkage” SMSC SPC is defined for SRI_DOM. In Next analysis step, further routing on called party address (SPCLDPAA table = SRI_CLD) is specified.




7) SPUOCAE table specifies list of “operation codes “ which are taken into account during this step with next step analysis as SPGTPART table. In this case Operation Code “Short message gateway services “ is considered .

8) In SPGTPART ,on basis of SPUOCAE “SRI_AC” partition is selected and SPGTTRL “SRI_SM_INT” is selected.

SMS Call flow ( To Own subscriber)



9) In SPGTRUL table, for SPGTTRL “SRI_SM_INT”, 919,918 and 917 are defined with GT translation rule(SPGTCRUL) “TT0TOTT11 “and referenced to SPGTTRL “SRI_SM_INT11”.

10) In SPGTCRUL table , as per “TT0TOTT11” rule translation type is changed from TT0 to TT11 and “1D” is prefixed to Called Party Address (CdPA).

11) In SPGTRUL table for SPGTTRL “SRI_SM_INT11” for GT Add Info “ 1D”,Possible ported No flag is assigned TRUE . So the message is sent to NP application for dipping.

12) In PRETRUL table “1D “ is removed from the received CdPA and sent to NPENTRY table . In NPENTRY table, CdPA (prefix or complete) will be associated with TPROF No.

13) In TPROF table ,LRN associated with TPROF No will be dipped in CdPA and new Called party address will be “91+ownLRN+CdPA.”

14) In SPGTRUL table for “SRI_SM_INT11 “,GT Add info “91” is defied with SPGTCRUL “TT11TOTT0 “and referenced to SPGTTRL “SRI_SM_INT”.

15) In SPGTCRUL table , as per “TT11TOTT0” rule translation type is changed from TT110 to TT0.

16) In SPGTRUL table for SPGTTRL “SRI_SM_INT “ ,”91+OWN LRN +NDC” will be routed to respective HLR with SPGTCRUL “CANGT” i.e. LRN is removed before routing to HLR.

17) SRI Request is forwarded to HLR .


3) In SPRDOM table, domain “IDPM_DOM” is selected as SPRDOM type “ Local sccp Linkage “ is selected which mean all SCPs of he network belong to this domain, except for those defined in SPRDOM type “ Remote sccp Linkage”. In Next analysis step, further routing on called party address (SPCLDPAA table = IDPM) is specified.


5) In SPCLDAPAAE table “list of Called SSN” is specified with next step analysis as SPUOCA table. If Called SSN of the messages is present in the list , the defined SPUOCA(User operator is selected else default routing is performed.




SMS Call flow ( To Own subscriber) Continued….




19 April 2023

SMSCSMSC

MSS MSS

MO forwardSM

MO forwardSM

SRI for SMRequest

SPRDOM SCCP Routing Domain.) SRI_DOM


SPGTPARTPartition Parts(Select GT translator SRI_SM_INT)

SPGTRUL( SPGTTRL Name=SRI_SM_INT,GT Address Info.=919/918/917,SPGTCRUL Name=TT0TOTT11,SPGTTRLREF Name=SRI_SM_INT11

SPGTCRUL : SPGTCRUL Name=TT0TOTT11,Addr.Info Conv.Rule=+1DT, TTID=TTID : TTID : Translation Type 11;( TT 0 converted to TT 11 and “1D“ prefixed to CdPA)

SPGTRUL : SPGTTRL Name=SRI_SM_INT11,GT Address Info.=1D,Possible Ported No.=TRUE;

PRETRUL table( 1D is removed from CdPA )

1) NPENTRY table( CdPA=TPROF No)2)TPROF table ( TPRON No =LRN)LRN inserted before CdPA

SPGTRUL( SPGTTRL Name=SRI_SM_INT11,GT Address Info.=91,SPGTCRUL Name=TT11TOTT0SPGTTRLREF Name=SRI_SM_INT

SPGTCRUL : SPGTCRUL Name=TT11TOTT0, TTID=TTID : TTID : Translation Type =unknown;( TT 11 converted to TT 0)

SRI for SMRequest

GMSCGMSC

SPGTRUL( SPGTTRL Name=SRI_SM_INT, GT Address Info.=91LRN, SPRNS= routed towards GMSC

SMS Call flow ( To Foreign subscriber)

SRI for SMRequest

POI



1) When a customer makes MO SMS ,” MO forwardSM” request is sent to SMSC by MSS via STP . SMSC then sends “SRI for SM “ to HLR via STP.( CdPA = B party no, CgPA = SMSC GT,CdPN)


3) In SPRDOM table, domain “SRI_DOM” is selected as for SPRDOM type “ Remote sccp Linkage” SMSC SPC is defined for SRI_DOM. In Next analysis step, further routing on called party address (SPCLDPAA table = SRI_CLD) is specified.




7) SPUOCAE table specifies list of “operation codes “ which are taken into account during this step with next step analysis as SPGTPART table. In this case Operation Code “Short message gateway services “ is considered .

8) In SPGTPART ,on basis of SPUOCAE “SRI_AC” partition is selected and SPGTTRL “SRI_SM_INT” is selected.

SMS Call flow ( To Foreign subscriber)



9) In SPGTRUL table, for SPGTTRL “SRI_SM_INT”, 919,918 and 917 are defined with GT translation rule(SPGTCRUL) “TT0TOTT11 “and referenced to SPGTTRL “SRI_SM_INT11”.

10) In SPGTCRUL table , as per “TT0TOTT11” rule translation type is changed from TT0 to TT11 and “1D” is prefixed to Called Party Address (CdPA).

11) In SPGTRUL table for SPGTTRL “SRI_SM_INT11” for GT Add Info “ 1D”,Possible ported No flag is assigned TRUE . So the message is sent to NP application for dipping.

12) In PRETRUL table “1D “ is removed from the received CdPA and sent to NPENTRY table . In NPENTRY table, CdPA (prefix or complete) will be associated with TPROF No.

13) In TPROF table ,LRN associated with TPROF No will be dipped in CdPA and new Called party address will be “91+LRN+CdPA.”

14) In SPGTRUL table for “SRI_SM_INT11 “,GT Add info “91” is defied with SPGTCRUL “TT11TOTT0 “and referenced to SPGTTRL “SRI_SM_INT”.

15) In SPGTCRUL table , as per “TT11TOTT0” rule translation type is changed from TT110 to TT0.

16) In SPGTRUL table for SPGTTRL “SRI_SM_INT “ ,”91+LRN” will be routed to core node with which POI is present.

17) SRI Request is forwarded to respective core node which will further process it .


3) In SPRDOM table, domain “IDPM_DOM” is selected as SPRDOM type “ Local sccp Linkage “ is selected which mean all SCPs of he network belong to this domain, except for those defined in SPRDOM type “ Remote sccp Linkage”. In Next analysis step, further routing on called party address (SPCLDPAA table = IDPM) is specified.


5) In SPCLDAPAAE table “list of Called SSN” is specified with next step analysis as SPUOCA table. If Called SSN of the messages is present in the list , the defined SPUOCA(User operator is selected else default routing is performed.




SMS Call flow ( To Own subscriber) Continued….

MNP CAll Flow

Documents

Transcript of MNP CAll Flow