Global Title

##################################
Global Title
##################################

Address used in SCCP ptorocol for routing signaling messages on telecommunication network.
Unique address that refer only one destination, though in practice destination change over time.

@@@ Structure @@@
1) Global title format
- format of global title used

2) Numbering Plan Indicator
- which numbering plan used for global title.

NPI Description Standard
----------------------------------
0 unknown
1 ISDN Telephony E.164
2 generic
3 data X.121
4 telex F.69
5 maritime mobile E.210 and E.211
6 land mobile E.212
7 ISDN/mobile E.214

Bits 3 2 1 0
0 0 0 0 Unknown
0 0 0 1 ISDN/telephone numbering plan (E.164/E.163)
0 0 1 1 Data numbering plan (X.121)
0 1 0 0 Telex numbering plan
1 0 0 0 National numbering plan
1 0 0 1 Private numbering plan
1 0 1 0 ERMES numbering plan (ETSI DE/PS 3 01-3)
1 1 1 1 Reserved for extension
All other values are reserved

3) Type of Number(TON) or Nature of Address Indicator(NAI)
- indicate the scope of the address value.

Type-of-number:
Bits 6 5 4
0 0 0 Unknown 1)
0 0 1 International number 2)
0 1 0 National number 3)
0 1 1 Network specific number 4)
1 0 0 Subscriber number 5)
1 0 1 Alphanumeric, (coded according to GSM TS 03.38 7-bit default alphabet)
1 1 0 Abbreviated number
1 1 1 Reserved for extension

4) Translation Type
- Indicate the preferred method of global title analysis

TCAP Erro Message

ERRORS {
-- systemFailure -- localValue 34,
-- dataMissing -- localValue 35,
-- unexpectedDataValue -- localValue 36,
-- facilityNotSupported -- localValue 21,
-- unknownSubscriber -- localValue 1,
-- teleserviceNotProvisioned -- localValue 11,
-- absentSubscriber -- localValue 27,
-- callBarred -- localValue 13}

TCAP SRI_SM Response Messge Decode

SRI_SM TCAP Message Decode
==========================

Dialogue Request
----------------
Original Message
I00 M tc783 iffff f2d d14 s00 p0400

******Decode Parameter Field******
END Dialogue Ind
04
Msg End Ind
00


Component Request
-----------------
Original Message
I00 M tc781 iffff f2d d14 s00
p09011EA21C020100301702012D301204031032F4A00B810913079188966310406000

******Decode Parameter Field******
Result Successful
09
Component Portion
01
1E
A21C020100301702012D301204031032F4A00B8109130791889663104060
Msg End Ind
00

******Decode Component Portion******
Return Result Last Ind
A2
Component Portion length
1C

Invoke ID Portion
Invoke ID Ind = 02
Invoke ID Length = 01
Invoke ID Value = 00

Result Portion
Result Ind = 30
Result Length = 17
Result Value = 02012D301204031032F4A00B8109130791889663104060

******Decode comp Portion******
Operation Code Portion
02
01
2D
Result Portion
30
12
04031032F4A00B8109130791889663104060

******Decode Result Portion******
IMSI Portion
04
03
1032F4
Network Number Portion
A0
0B
8109130791889663104060

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.