Alert Subscriber (ALERT_NOTIFICATION)

Alert Subscriber
-------------------

Alert subscriber message usually was sent when the user didn't switch on the mobile phone. It was received by SMSC and will store to the database and wait for send retry.

MOBILE USER(off) ---- (ALERT_NOTIFICATION) ----> MAPSMS ----> MTSL ---->Database

There will be another mechanism to query out the retry table sms and send it out trough mapsms.

Database -----------> Message Dispatcher --------> Mapsms -------> Mobile User

* There no response message needed for the alert notification message.

Global Title Translation

Global Title Translation

A Global Title (GT) is an address used in the SCCP protocol for routing signaling messages on telecommunications networks. In theory, a global title is a unique address which refers to only one destination, though in practice destinations can change over time.

GTES
- will change according to the length of the GT Address.
- If the length == odd number, then set GTES to 1
- If the length == even number, then set GTES to 2

for MO_SM
- will be using remote service centre address(RSC_SCCP_ADDR) as the GT Address value.

for MT_SM
- will be using msc address as the GT Address value

for SRISM
- will be using the HLR SCCP Adreess as tyhe GT Address value.

TCAP : Long SMS Handling

TCAP Layer Long SMS Handling

Long sms handling for tcap layer would be like follow

-> DLG_BEGIN + EMPTY_COMP
<- DLG_CONTINUE + EMPTY_COMP
-> DLG_CONTINUE + INVOKE_COMP
<- DLG_END + ResultLast_COMP

- Whenever a long sms is send, it will send by a dialogue begin and a empty component.
- The receiver will need to response by sending a continue dialogue and a empty component.
- After the continue dialogue is sent, the sender will start sending the message content by sending continue dialogue and a invoke component.
- After receiver received, it will response a end dialogue and the resultlast component.

MO_SM and MT_SM : Address Defination

MO_SM
-----------
-When mobile user submit_sm to mapsms, so it msisdn would be the originating address(sm_rp_oa).
- The message will send to SMSC, so the service centre address would be the destination address(sm_rp_da).
- The destination address would pack to the sm_rp_ui.

Service Centre Address
- Own mapsms address
- pack to sm_rp_da

MSISDN
- Message Source Address
- pack to sm_rp_oa

sm_rp_ui
- pack in message destination address

- MO_SM message will not need to send SRISM to the message service center.


MT_SM
----------
- Whenever mapsms wish to send an deliver_sm, the originating address would be the service center address.
- The destination address would be retrieve from the srism process to get the destination imsi.
- the sm_rp_ui user information would pack in the msisdn(source addresss).

Service Centre Address
- would be the mapsms own address also.
- will be pack to the sm_rp_oa

MSISDN
- would be the message source address
- will be pack to the sm_rp_ui

sm_rp_da
- will be using the destination imsi.
- the destination imsi was get from the srism request.

- MTSM would need to send SRISM to get the route information.