Gait C 1 1 2 0

GSM/ANSI-136 Interoperability Team Specification Document: GAIT-C-1-1-2-0
GSM Hosted SMS Teleservice Specification

Phase 1, Version 2.0
May 24, 2000
Setting the pace of Global

Wireless Communications.
Title: GSM Hosted SMS Teleservice Specification, Phase 1, Date: May 24, 2000
Version 2.0
Table of Contents
1. REVISION HISTORY ......................................................................................................................................1
2. GENERAL DESCRIPTION.............................................................................................................................1
2.1 MOBILE EQUIPMENT REQUIREMENTS..................................................................................................... 1
2.2 NETWORK REQUIREMENTS ...................................................................................................................... 2
3. GHOST HIGHER LAYER PROTOCOL IDENTIFIER ..............................................................................4
4. GSM SMS TRANSFER PDU REQUIREMENTS .........................................................................................4
5. END-TO-END REQUIREMENTS ..................................................................................................................5

5.1 MOBILE TERMINATED SERVICE FOR ANSI-136 FOREIGN MODE ......................................................... 5
5.2 MOBILE ORIGINATED SERVICE FOR ANSI-136 FOREIGN MODE .......................................................... 6
5.3 MOBILE TERMINATED SERVICE FOR GSM FOREIGN MODE ................................................................. 6
5.4 MOBILE ORIGINATED SERVICE FOR GSM FOREIGN MODE .................................................................. 7
5.5 MOBILE TERMINATED AND MOBILE ORIGINATED SERVICE FOR ANSI-136 NATIVE MODE ............ 7
6. GHOST TELESERVICE MAPPING..............................................................................................................8
6.1 MAPPING IN ANSI-136 NETWORKS ......................................................................................................... 8
6.2 DETAILED MAPPING IN THE MOBILE STATION .................................................................................... 11
7. IIF MAPPING IN THE NETWORK ............................................................................................................13
7.1 GSM AND ANSI-41 MAPPING ................................................................................................................. 13
7.2 IDENTIFICATION OF THE IIF SS7 ADDRESS FOR MOBILE ORIGINATED SERVICES .......................... 15
8. FAILURE/REJECT CAUSE CODE MAPPING .........................................................................................16
8.1 MOBILE TERMINATED SHORT MESSAGING ACKNOWLEDGEMENTS ................................................. 16
8.2 MOBILE ORIGINATED SHORT MESSAGING ACKNOWLEDGEMENTS .................................................. 20
8.3 PROVISIONING AND UNSUPPORTED FEATURE ERRORS ...................................................................... 21
9. ABBREVIATIONS..........................................................................................................................................22
Copyright© 1999 Universal Wireless Communications Consortium and North American GSM Alliance i
All Rights Reserved
Version 2.0
1 1. Revision History
Phase Version Sub-Version Reason for Change Based on CR Date
1 1 0 Initial publication. None N/A
1 2 0 In section 3, corrected 2000-24 5/16/00
Teleservice Protocol
Identifier subfield of
the GHOST HLPI to
align with TIA
standards.
2
3 2. General Description
4 The GSM Hosted SMS Teleservice (GHOST) is used to deliver GSM SMS transfer packet data
5 units (PDUs) to and from a GAIT mobile station operating in an ANSI TIA/EIA-136 network,
6 either through an Interworking and Interoperability Function (IIF) or directly through a Message
7 Center (MC). GHOST may be used in either ANSI-136 foreign or native mode. Refer to GSM
8 03.40 for a full description of the GSM SMS PDUs. The GAIT mobile station shall be capable of
9 receiving and originating the GHOST teleservice while on a Digital Control Channel (DCCH) or a
10 Digital Traffic Channel (DTC), in accordance with the rules described in ANSI TIA/EIA-136
11 Parts 123 and 133. The IIF shall be capable of performing protocol interworking and mapping
12 short messages between a GSM SMS PDU and an ANSI-41 SMDPP GHOST teleservice SMS.
13 The IIF shall also be capable of performing protocol interworking and mapping for SMS delivery
14 information messages. A Message Center that supports GHOST shall be capable of formatting
15 GSM SMS messages and packaging them within the GHOST teleservice, and shall be capable of
16 mapping between ANSI-136 Cellular Messaging Teleservice (CMT) and GHOST.
17 2.1 Mobile Equipment Requirements

18 Figure 1 shows the protocol stack to support GHOST in a GAIT mobile station. The Short
19 Message Entity within the GAIT mobile equipment shall be capable of using two relay layers, the
20 ANSI-136 R-DATA layer and the GSM Relay Layer, depicted as SM-RL-136 and SM-RL-GSM,
21 respectively.
22 Figure 1. Protocol Stack in Mobile Equipment to Support GHOST.
SM-AL
SM-TL (GSM SMS PDUs)
SM-RL-136 SM-RL-GSM
ANSI-136 Lower Layers GSM Lower Layers

23
24 The short message transfer layer (SM-TL), consisting of GSM SMS PDUs, shall have two service
25 access points (SAPs), one SAP for SM-RL-136 and another for SM-RL-GSM. The SAP to be
26 used shall be derived by the knowledge of the air-interface the mobile station is operating on. If
1
Version 2.0
1 the mobile station is using the GSM air interface, then the SAP to the SM-RL-GSM layer shall be
2 used. If the mobile station is using the ANSI-136 air interface, then the SAP to the SM-RL-136
3 layer shall be used. The primitives as defined in GSM 03.40 shall be used.
4 2.2 Network Requirements

5 Figure 2 shows an example of the protocol stack for the origination and delivery of a SMS PDU
6 for a GAIT GSM native mobile in a foreign mode using GHOST. In this description, the Short
7 Message Service Gateway MSC (SMS-GMSC) and the Short Message Service Interworking MSC
8 (SMS-IWMSC) functions in the GSM network are combined into a GSM SMS Centre (SMSC).
9 This description of the processing of a GHOST teleservice is meant to provide a high level view
10 of the workings of the network elements, including the mobile station, and is not meant to
11 mandate a particular processing algorithm.
12
2
Version 2.0
2 Figure 2. GHOST Example Protocol Stack for ANSI-136 Foreign

3 Mode.
SM-AL SM-AL
GSM SMS PDU

GSM SMS PDU
(SM-TL)
IWF
GHOST
GHOST
(SM-RL)
TSAR (optional)
TSAR FSM FSM
(SM-RL)
IWF
R-DATA
R-DATA SMDPP SMDPP
(SM-RL)
TIA/EIA-136 Layers 1 & 2

TIA/EIA-41 Layers 1 & 2 GSM MAP Layers 1 & 2
(SM-LL)
MS ANSI-136 BMI IIF GSM SMSC

4
5
7 for a GAIT ANSI-136 native mobile station in a foreign mode using GHOST.
8 Figure 3. GHOST Example Protocol Stack for GSM Foreign Mode.
SM-AL SM-AL
GSM SMS PDU GSM SMS PDU

(SM-TL) (SM-TL)
IWF
IWF
GHOST GHOST
SM-RL GSM FSM TSAR TSAR

GSM
04.11 09.02
SMDPP SMDPP
GSM MAP Layers 1 & 2 TIA/EIA-41 Layers 1 & 2
MS GSM MSC IIF ANSI-41 MC

9
10
11
3
Version 2.0
2 for a mobile station in ANSI-136 native mode using GHOST.
3 Figure 4. GHOST Example Protocol Stack for ANSI-136 Native

4 Mode.
SM-AL SM-AL
GSM SMS PDU GSM SMS PDU

(SM-TL) (SM-TL)
GHOST
GHOST
(SM-RL)
TSAR (optional)
TSAR
(SM-RL)
IWF
R-DATA
R-DATA SMDPP SMDPP
(SM-RL)
TIA/EIA-136 Layers 1 & 2 TIA/EIA-41 Layers 1 & 2
MS ANSI-136 BMI ANSI-41 MC

5
6 3. GHOST Higher Layer Protocol Identifier

7 GHOST shall use the HLPI shown in Table 1. TSAR may or may not be applied to the GHOST
8 teleservice.
9 Table 1. HLPI for GHOST.

HLPI Subfield Coding
Teleservice Type Indicator Subfield Carrier Specific Teleservice
Teleservice Segmentation and Reassembly May or may not have TSAR sub-
Subfield layer
Teleservice Protocol Identifier Subfield 00 0111 (GHOST)
10
11 4. GSM SMS Transfer PDU Requirements

12 GHOST supports the following GSM PDUs:
13 • SMS-DELIVER (BMI Æ MS). Support per GSM 03.40 and 04.11.
4
Version 2.0
1 • SMS-SUBMIT (MS Æ BMI). Support per GSM 03.40 and 04.11, except that if the
2 Validity Period is included, it must be set to an integer value (1 octet instead of 7 in
3 length) when the SMS-SUBMIT is sent as part of GHOST. This guarantees that the
4 transfer PDU can fit within one ANSI-136 R-DATA message and one ANSI-41 SMDPP
5 message.
6 • SMS-STATUS-REPORT (BMI Æ MS). Support per GSM 03.40 and 04.11.
7 The SMS-COMMAND PDU (MS Æ BMI), SMS-DELIVER-REPORT (MS Æ BMI), and SMS-
8 SUBMIT-REPORT (BMI Æ MS) are not supported by GHOST. (Note: The SMS-DELIVER-
9 REPORT and SMS-SUBMIT-REPORT transfer PDUs are carried within RP-ACK or RP-ERROR
10 relay PDUs within GSM, and there is no equivalent within ANSI-136 and ANSI-41.)
11 GHOST supports concatenation of multiple PDUs of the same type, as described in GSM 03.40.
12 5. End-to-End Requirements
13 5.1 Mobile Terminated Service for ANSI-136 Foreign Mode
14 When a GAIT mobile station is operating in ANSI-136 Foreign Mode and a mobile terminated
15 short message is received by the Interworking and Interoperability Function (IIF) via a GSM
16 MAP FORWARD SHORT MESSAGE (MAP FSM), the IIF:
17 • Extracts the GSM SMS PDU from the GSM FSM message.
18 • Adds the GHOST header to the GSM SMS PDU to formulate a GHOST teleservice.
19 • Formulates an ANSI-41 SMSDeliveryPointToPoint (SMDPP) Invoke message as follows:
20 • Inserts the GHOST teleservice in the SMDPP message within the SMS_BearerData
21 parameter.
22 • Perform TSAF to TSAH mapping per Section 7.2.
23 • Maps additional GSM FSM message parameters to ANSI-41 SMDPP message
24 parameters per Section 7.1.
25 • Sends the SMDPP message to the BMI (ANSI-136 Base Station-MSC Interworking
26 Function) for delivery to the mobile station.
27 The IIF may optionally add Teleservice Segmentation and Reassembly (TSAR) to the GHOST
28 teleservice prior to encapsulation by the SMDPP message.
29 The ANSI-136 MSC (BMI) converts the ANSI-41 SMDPP message to an ANSI-136 R-DATA
30 message for delivery of the GHOST teleservice to the GAIT mobile station without opening the
31 SMS_BearerData.
32 At the mobile station, the R-DATA message is received at layer 3. The mobile station then:
33 • Extracts the R-Data Unit from the R-DATA message.
34 • Identifies from the Higher Layer Protocol Identifier (HLPI) if TSAR is applied to the
35 teleservice message and processes the transport layer accordingly.
36 • Identifies from the HLPI that this is a GHOST teleservice.
37 • Processes the GSM SMS PDU according to the relevant GSM standard.
5
Version 2.0
1 An R-DATA ACCEPT message is sent to the BMI which in turn returns a SMDPP Return Result
2 message to the IIF. Note that in Figure 2, R-DATA, TSAR, and GHOST are all part of the SM-
3 RL-136 layer as depicted in Figure 1.
4 5.2 Mobile Originated Service for ANSI-136 Foreign Mode

5 When a GAIT mobile station is operating in ANSI-136 Foreign Mode and it is required that it
6 transmit a GSM SMS mobile originated short message, then the mobile station proceeds as
7 follows:
8 • Formulates a GSM SMS PDU.
9 • Adds the GHOST header to the GSM SMS PDU.
10 • Adds the TSAR header to the GHOST teleservice, if TSAR is used.
11 • Inserts the GHOST teleservice into the Higher Layer Protocol Data Unit of the R-Data Unit
12 and adds the GHOST HLPI.
13 • Formulates an R-DATA message and sends it to the ANSI-136 BMI.
14 The ANSI-136 MSC translates the R-DATA message to an ANSI-41 SMDPP Invoke message
15 and sends it to the destination specified in the Teleservice Server Address. The MSC does not
16 open the Higher Layer Protocol Data Unit, but converts it directly to SMS_BearerData.
17 For the GAIT mobile station in ANSI-136 Foreign Mode, the Teleservice Server Address shall
18 indicate that the home Teleservice Server is the IIF. The IIF proceeds as follows:
19 • Extracts the SMS_BearerData from the SMDPP message.
20 • Processes the transport layer, if TSAR is supported and applied.
21 • Identifies that this is a GHOST teleservice by examining the HLPI.
22 • Removes the GHOST header from the GSM SMS PDU.
23 • Formulates a GSM Forward Short Message (FSM) message as follows:
24 • Inserts the GSM SMS PDU into the GSM FSM message.
26 • Maps additional ANSI-41 SMDPP message parameters to GSM FSM message
28 • Sends the GSM FSM message to the originator’s designated SMSC.
29 5.3 Mobile Terminated Service for GSM Foreign Mode

30 When a GAIT mobile station is operating in GSM Foreign Mode and a mobile terminated short
31 message is received by the Interworking and Interoperability Function (IIF) via an ANSI-41
32 SMDPP message, the IIF:
33 • Extracts the GHOST Teleservice from the SMDPP message.
34 • Removes the SMS_Teleservice Identifier parameter identifying the GHOST teleservice.
35 • Formulates a GSM Forward Short Message as follows:
36 • Inserts the GSM SMS PDU into the Forward Short Message.
6
Version 2.0
1 • Maps additional ANSI-41 SMDPP message parameters to GSM FSM message

3 • Sends the GSM Forward Short Message for delivery to the mobile station per GSM 09.02 and
4 GSM 04.11.
5 5.4 Mobile Originated Service for GSM Foreign Mode

6 When a GAIT mobile station is operating in GSM Foreign Mode and it is required that it
7 originates a short message, then the mobile station proceeds as follows:
8 • Formulates a GSM SMS PDU per GSM 04.11.
9 • Sends the CP-DATA message to the GSM MSC.
10 The GSM MSC processes and forwards this message per GSM 09.02.
11 For the GAIT mobile station in GSM Foreign Mode, the Service Center Address shall indicate
12 that the home Teleservice Server is the IIF. The IIF proceeds as follows:
13 • Extracts the GSM SMS PDU from the GSM FSM message.
14 • Adds the GHOST header to the GSM SMS PDU to formulate a GHOST teleservice.
15 • Formulates an ANSI-41 SMSDeliveryPointToPoint (SMDPP) Invoke message as follows:
16 • Inserts the GHOST teleservice in the SMDPP message within the SMS_BearerData
17 parameter.
19 • Maps additional GSM FSM message parameters to ANSI-41 SMDPP message
21 • Sends the SMDPP message to the originator’s designated SMSC.
22 5.5 Mobile Terminated and Mobile Originated Service for ANSI-136

23 Native Mode
24 GHOST may be used to deliver teleservices from a short message entity to a mobile station
25 operating in ANSI-136 Native Mode without the involvement of an IIF. In this case, normal
26 ANSI-41 procedures are used to deliver the GHOST teleservice to the mobile station.
27 GHOST may be used to deliver teleservices from a mobile station operating in ANSI-136 Native
28 Mode to a short message entity without the involvement of an IIF. In this case, the mobile station
29 proceeds as follows:
30 • Formulates a GSM SMS PDU.
31 • Adds the GHOST header to the GSM SMS PDU.
32 • Adds the TSAR header to the GHOST teleservice, if TSAR is used.
33 • Inserts the GHOST teleservice into the Higher Layer Protocol Data Unit of the R-Data Unit
34 and adds the GHOST HLPI.
35 • Formulates an R-DATA message and sends it to the ANSI-136 BMI.
7
Version 2.0
1 The ANSI-136 MSC translates the R-DATA message to an ANSI-41 SMDPP Invoke message
2 and sends it to the destination specified in the Teleservice Server Address. The MSC does not
3 open the Higher Layer Protocol Data Unit, but converts it directly to SMS_BearerData.
4 For the GAIT mobile station in ANSI-136 Native Mode, the Teleservice Server Address shall
5 indicate that the home Teleservice Server is the home Message Center.
6 6. GHOST Teleservice Mapping

7
8 6.1 Mapping in ANSI-136 Networks

9 Figure 5 and Figure 6 depict the mapping of the GSM SMS transfer PDU into a GHOST
10 teleservice for relay across the ANSI-136 and ANSI-41 network. Note that some optional
11 parameters are shown for completeness, and are not necessary for GHOST (e.g., subaddressing).
8
Version 2.0
1 Figure 5. Mapping for Mobile Terminated GHOST Teleservice.

ANSI-41 SMDPP R-DATA HLPI
Protocol R-Data Unit Teleservice Type
SMS_Bearer Data M Discriminator M Indicator
00 Length Indicator 1
in (N) (in octets)
8 Bits Teleservice
Message Type XXXXXXXX Segmentation and
SMS_TID M M Reassembly Indicator
01 1010
Higher Layer 1 or 0
Protocol
R-Transaction Identifier Teleservice Protocol
ESN O Identifier M 8 Bits Identifier
XXXXXXXX
Higher Layer 00 0011 (GHOST)
Protocol Data
R-Data Unit Unit
MIN O 16 ~ 16+8*(N-1) M 8 * (N-1)
GSM SMS PDU

SMS_Charge Teleservice
Indicator
O Server Address
O
Per GSM 03.40
SMS_Destination User Destination

Address
O O
Address
SMS_Message User Destination

Count O Subaddress
O
SMS_Notification User Originating

Indicator
O O
Address
SMS_Orig User Originating

Destination Address
O Subaddress
O
SMS_Orig User Originating

Destination O Address Presentation O
Subaddress Indicator
Multilingual
SMS_Orig
Origination Address
O Teleservice O
Server Address
SMS_Orig Multilingual User

Originating O Destination O
Subaddress Address
SMS_Originating Multilingual User

Address
O Originating O
Address
2
9
Version 2.0
1 Figure 6. Mapping for Mobile Originated GHOST Teleservice.

R-DATA ANSI-41 SMDPP
HLPI Protocol
Teleservice Type Discriminator M SMS_Bearer Data M
Indicator 00
1
Teleservice R-Data Unit Message Type
M SMS_TID M
Segmentation and 01 1010
Reassembly Indicator Length Indicator
1 or 0 in (N) (in octets)
8 Bits R-Transaction
XXXXXXXX Identifier M ESN O
Teleservice Protocol
XXXXXXXX
Identifier Higher Layer
00 0011 (GHOST) Protocol
Identifier R-Data Unit
8 Bits 16 ~ 16+8*(N-1)
M MIN O
Higher Layer
Protocol Data Teleservice Server
Unit SMS_Charge
Address O Indicator
O
8 * (N-1)
GSM SMS PDU
User Destination SMS_Destination
Address
O Address
O
Per GSM 03.40
User Destination SMS_Message

Subaddress O Count O
User Originating SMS_Notification

Address
O Indicator
O
User Originating SMS_Orig

Subaddress
O Destination Address
O
User Originating SMS_Orig

Address Presentation O Destination O
Indicator Subaddress
Multilingual
SMS_Orig
Teleservice Server O Origination Address
O
Address
SMS_Orig
Multilingual User
O Originating O
Destination Address
Subaddress
Multilingual User
SMS_Originating
Originating Address O Address
O
(Optional)
2
10
Version 2.0
1 6.2 Detailed Mapping in the Mobile Station

2 The following sub-sections show the mapping for the GSM PDUs into the ANSI-136 relay layer
3 (R-DATA) in the mobile station. The abbreviations used in the diagrams are listed below.
4 DA Destination Address
5 DCS Data Coding Scheme
6 DT Discharge Time
7 HL-PDU Higher Layer Protocol Data Unit
8 HLPI Higher Layer Protocol Identifier
9 L Length
10 MMS More Messages to Send
11 MT Message Type
12 MTI Message Type Indicator
13 OA Originating Address
14 PD Protocol Discriminator
15 PID Protocol Identifier
16 RA Recipient Address
17 RDU R-Data Unit
18 R-ID R-Transaction Identifier
19 RP Reply Path
20 SCTS Service Centre Time Stamp
21 SCA Service Centre Address
22 SM Short Message
23 SMI Short Message Identifier
24 SRI Status Report Indication
25 ST Status
26 TSA Teleservice Server Address
27 UD User Data
28 UDA User Destination Address
29 UDL User Data Length
30 UOA User Originating Address
31 VP Validity Period
32 VPF Validity Period Format
33
11
Version 2.0
2 Figure 7. Mobile Terminated GSM SMS-DELIVER via GHOST.

SMI SRI OA SCA RP PID DCS MMS SCTS SM
GSM SMS-DELIVER
MTI MMS RP SRI OA PID DCS SCTS UDL UD
L HLPI HL-PDU
PD MT R-ID RDU TSA UDA UOA R-DATA
4 Figure 8. Mobile Originated GSM SMS-SUBMIT via GHOST.

SMI SRI DA SCA RP PID DCS VP SM
GSM SMS-SUBMIT
MTI VPF RP SRI MR DA PID DCS VP UDL UD
L HLPI HL-PDU
R-DATA
PD MT R-ID RDU TSA UDA UOA
6 Figure 9. Mobile Terminated GSM SMS-STATUS-REPORT via

7 GHOST.
SMI SRI OA SCA RP PID DCS MMS SCTS SM
GSM SMS-STATUS-REPORT
MTI MR MMS RA SCTS DT ST
L HLPI HL-PDU
R-DATA
PD MT R-ID RDU TSA UDA UOA
12
Version 2.0
1 7. IIF Mapping in the Network

2 In order to support mobile originated and terminated teleservices it is necessary to perform (1)
3 protocol mediation, (2) SS7 address determination for the home network MC, and (3) mapping of
4 ANSI TCAP to GSM TCAP and vice versa.
5 In order to achieve the above requirements, an IIF can be used. The IIF shall be capable of
6 receiving teleservice server addresses for ANSI-41/136 and mapping them into teleservice server
7 addresses for GSM and vice versa for GAIT subscribers. The IIF is required to perform SS7
8 address mapping only on message invokes, since the originating node address can be stored and
9 later used to determine the Called Party Address in the Return Result.
10 7.1 GSM and ANSI-41 Mapping

11 When the IIF receives a MAP FSM destined for an MS roaming in an ANSI-136/41 network, it
12 stores the originating Service Centre address locally, and replaces the Service Centre Address in
13 the outgoing SMDPP message with the E.164 address of the IIF. Upon receipt of an SMDPP
14 Return Result from the serving ANSI-136/41 MSC, the IIF converts it to a MAP_FSM_ACK, and
15 places the previously stored Originating Service Centre address in the Destination Address. See
16 Table 2.
17 Table 2. Mapping of Forward Short Message to SMDPP for

18 Mobile Terminated GHOST Teleservice.
Message
MAP MT FSM ANSI-41 SMDPP Invoke
Parameter Parameter
sm-RP-DA
IMSI (Note 1) Original Destination Address (MIN)
NoSM-RP-DA No mapping required
sm-RP-OA
Service centre address OA (Note 1) No mapping required
NoSM-RP-OA No mapping required
sm-RP-UI
RP-User-Data SMS_BearerData BearerData (IIF
adds length, GHOST teleservice ID)
TP-Originating-Address SMS_OriginalOriginatingAddress
More Messages to Send No equivalent mapping
19
20 Note 1: If present, map parameters as indicated.

21 When the IIF receives an SMDPP Invoke from an ANSI-136/41 SMSC for an ANSI-136/41
22 GAIT MS roaming in a GSM network, it stores the Originating MC address, converts the SMDPP
23 to a MAP_FSM, replaces the Originating Address by the address of the IIF, and sends the
24 message to the serving GSM MSC. Upon receipt of the MAP_FSM_ACK from the serving MSC,
25 the IIF converts the message to an SMDPP Return Result, replaces the Originating Address with
26 its own address and replaces the Destination Address with the previously stored address of the
27 ANSI-136/41 SMSC. See Table 3.
28
13
Version 2.0
1 Table 3. Mapping of SMDPP to Forward Short Message for

2 Mobile Terminated GHOST Teleservice.
Message
ANSI-41 SMDPP Invoke MAP MT FSM
Parameter Parameter
Identifier
Length Locally set
SMS Bearer Data RP-User Data (minus length
parameter)
SMS Teleservice ID Not used
ESN No equivalent mapping
MIN IIF mapped to associated IMSI in
RP-Destination-Address
SMS_Charge Indicator No equivalent mapping
SMS_Destination Address Not used
SMS_Message Count No equivalent mapping
SMS_Notification Indicator Not used
SMS_OriginalDestinationAddress IIF mapped to associated IMSI in
RP-Destination-Address
SMS_Original Destination Sub No equivalent mapping
Address
SMS_Original Originating TP-Originating-Address within
Address the RP-User Data.
SMS_Original Originating No equivalent mapping
Address Sub Address
SMS_Originating Address Service centre addressOA within
the RP-Originating Address
3
4 When the IIF receives a MAP_FSM for a MS roaming in an GSM network, it stores the Visited
5 MSC (VMSC) address locally and replaces the VMSC address in the outgoing SMDPP message
6 by the E.164 address of the IIF. Upon receipt of an SMDPP Return Result from the MC, the IIF
7 converts it to a MAP_FSM_ACK and places the previously stored VMSC address in the SCCP
8 Called Party Address. See Table 4.
9 Table 4. Mapping of Forward Short Message to SMDPP for

10 Mobile Originated GSM SMS Messages Mapped to
11 GHOST Teleservice.
Message
MAP MO FSM ANSI-41 SMDPP Invoke
Parameter Parameter
sm-RP-DA
Service Center Address DA IIF maps TSAF to TSAH into
SMS_DestinationAddress
NoSM-RP-DA No mapping required
sm-RP-OA
MSISDN SMS_OriginalOriginating Address
NoSM-RP-OA No mapping required
sm-RP-UI
RP-User-Data SMS_BearerData (IIF adds length,
GHOST teleservice ID)
14
Version 2.0
TP-Destination-Address SMS_OriginalDestination Address

1
2 When the IIF receives a SMDPP Invoke for a MS roaming in an GSM network, it stores the
3 VMSC address locally and replaces the VMSC address in the outgoing SMDPP message by the
4 E.164 address of the IIF. It also internally maps the TSAF from the SMS_Destination Address into
5 the TSAH and places it in the RP-Destination Address per Section 7.2. Upon receipt of an SMDPP
6 Return Result from the MC, the IIF converts it to a MAP_FSM_ACK and places the previously
7 stored VMSC address in the SCCP Called Party Address. See Table 5.
8 Table 5. Mapping of SMDPP to Forward Short Message for

9 Mobile Originated GHOST Teleservice.
Message
ANSI-41 SMDPP Invoke MAP MT FSM
Parameter Parameter
Identifier
Length Locally set
SMS Bearer Data RP-User Data (minus length
parameter)
SMS Teleservice ID Not used
ESN No equivalent mapping
MIN TP-Destination Address within
the RP-User-Data
SMS_Charge Indicator No equivalent mapping
SMS_Destination Address Service Center Address DA
within RP-Destination Address
SMS_Message Count No equivalent mapping
SMS_Notification Indicator Not used
SMS_Original Destination TP-Destination Address within
Address the RP-User-Data
SMS_Original Destination Sub No equivalent mapping
Address
SMS_Original Originating MSISDN within the RP-
Address Originating Address
SMS_Original Originating No equivalent mapping
Address Sub Address
SMS_Originating Address Not used
10
11 7.2 Identification of the IIF SS7 Address for Mobile Originated

12 Services
13 The following SS7 address mapping scheme is defined in order to resolve the ambiguity that
14 occurs when a roaming GAIT subscriber attempts to invoke Mobile Originated Teleservices.
15 Specifically, instead of using only a single Teleservice Server Address as the SS7 SCCP Called
16 Party Address, a pair of E.164 addresses are defined for each Teleservice Address Center (e.g.,
17 MC or SMSC). This pair of addresses (native and a foreign mode TSAs) is used to enable the
18 routing of incoming messages to the IIF from the serving foreign network, while messages that
19 originate in a network that uses the same technology as the home network bypass the IIF and are
20 routed directly to the MC. The native mode address can be translated using global title translation
21 to the actual SS7 address (DPC and SSN) of the MC while the foreign mode address is a virtual
22 address that points (via global title translation) to the IIF. There is a one-to-one mapping in the IIF
15
Version 2.0
1 between the home and foreign mode addresses for each MC, as shown in Table 6. Note that there
2 is a many-to-one relationship between the virtual addresses and the actual IIF address.
3 While roaming in foreign mode, the GAIT terminal uses the foreign mode address in order to
4 ensure that messages are first routed to the IIF. The IIF performs message translation, and inserts
5 the native mode address, i.e., an E.164 number that is translatable by the network to the actual MC
6 destination SS7 address.
7 Table 6. Teleservice Server Address Mapping in IIF

Home Technology Address Foreign Technology Address
TSAH1 ↔ TSAF1
TSAH2 ↔ TSAF2
TSAH3 ↔ TSAF3
8
9 8. Failure/Reject Cause Code Mapping

10 Within GSM there are multiple levels of acknowledgement for GSM SMS messages, as described
11 in GSM 03.40. The lower layer acknowledgement is provided via the CP-ACK or CP-ERROR
12 message. The relay layer acknowledgement is provided via the RP-ACK or RP-ERROR message.
13 Included in an RP-ERROR message is an RP-Cause value that gives the failure reason. RP-Cause
14 values are shown in Table 7. A transfer layer acknowledgement may be provided via a transfer
15 PDU, where transfer layer errors are reported in the TP-Failure-Cause parameter within an SMS-
16 DELIVER-REPORT or SMS-SUBMIT-REPORT message.
17 Within ANSI-136, there is one acknowledgement for the lower layer and the relay layer, R-DATA
18 ACCEPT or R-DATA REJECT. Included in an R-DATA REJECT is an R-Cause code that gives
19 the reason for failure to transfer or process an R-DATA message. R-Cause codes are shown in
20 Table 8. Since GHOST does not support the GSM SMS-DELIVER-REPORT or SMS-SUBMIT-
21 REPORT transfer PDUs, there is not an explicit transfer layer acknowledgement with GHOST.
22 8.1 Mobile Terminated Short Messaging Acknowledgements

23 A GAIT mobile station shall respond to a received GHOST teleservice after processing the relay
24 layer. If the relay layer generates a failure, then the mobile station shall map the resulting RP-
25 Cause value into its equivalent R-Cause code according to Table 9.
26 At the ANSI-136 MSC, the R-Cause code returned by a mobile station is mapped into a
27 corresponding ANSI-41 SMS_CauseCode for inclusion in an SMDPP Return Result message
28 according to Table 10. At the IIF, the ANSI-41 SMS_CauseCode is mapped to a return error in
29 the GSM MAP_FSM_ACK message according to Table 11.
16
Version 2.0
1 Table 7. RP-ERROR Causes and Meanings.

Code
Cause Description Direction Decimal Binary
Unassigned (unallocated) number B → MS 1 000 0001
Operator determined barring B → MS 8 000 1000
Call barred B → MS 10 000 1010
Reserved B → MS 11 000 1011
Short message transfer rejected B → MS 21 001 0101
Memory capacity exceeded MS → B 22 001 0110
Destination out of order B → MS 27 001 1011
Unidentified subscriber B → MS 28 001 1100
Facility rejected B → MS 29 001 1101
Unknown subscriber B → MS 30 001 1110
Network out of order B → MS 38 010 0110
Temporary failure B → MS 41 010 1001
Congestion B → MS 42 010 1010
Resources unavailable, unspecified B → MS 47 010 1111
Requested facility not subscribed B → MS 50 011 0010
Requested facility not implemented B → MS 69 100 0101
Invalid short message transfer reference both 81 101 0001
value
Semantically incorrect message both 95 101 1111
Invalid mandatory information both 96 110 0000
Message type nonexistent or not both 97 110 0001
implemented
Message not compatible with short message both 98 110 0010
protocol state
Information element nonexistent or not both 99 110 0011
implemented
Protocol error, unspecified both 111 110 1111
Interworking, unspecified B → MS 127 111 1111
2
17
Version 2.0
2 Table 8. R-Cause Codes and Meanings.

Code
Cause Description Direction Decimal Binary
Unassigned (unallocated) number B → MS 1 000 0001
No Route to Transit Network B → MS 2 000 0010
R-DATA message too long B → MS 3 000 0011
Identified HLPI not supported both 4 000 0100
Call barred B → MS 10 000 1010
Short message transfer rejected B → MS 21 001 0101
Memory capacity exceeded MS → B 22 001 0110
Destination out of service B → MS 27 001 1011
Unidentified subscriber B → MS 28 001 1100
Facility rejected B → MS 29 001 1101
Unknown subscriber B → MS 30 001 1110
Network out of order B → MS 38 010 0110
Temporary failure B → MS 41 010 1001
Congestion B → MS 42 010 1010
Resources unavailable, unspecified B → MS 47 010 1111
Requested facility not implemented Β → ΜS 69 100 0101
Invalid short message transfer reference value B → MS 81 101 0001
Invalid message, unspecified B → MS 95 101 1111
Mandatory information element error both 96 110 0000
Message type non-existent or not both 97 110 0001
implemented
Message not compatible with short message B → MS 98 110 0010
transfer state or message type non-existent or
not implemented
Information element non-existent or not both 99 110 0011
implemented
Invalid information element contents both 100 110 0100
Message not compatible with the short both 101 110 0101
message transfer state
Protocol error, unspecified both 111 110 1111
Interworking, unspecified B → MS 127 111 1111
3
18
Version 2.0
1 Table 9. Mapping of RP-ERROR Cause to R-Cause for Mobile

2 Station Response to Mobile Terminated Transfer
3 Attempt.
GSM RP-ERROR Cause ANSI-136 R-Cause
Memory capacity exceeded (22) Memory capacity exceeded (22)
Invalid short message transfer reference Invalid short message transfer reference
value (81) value (81)
Semantically incorrect message(95) Invalid message, unspecified (95)
Invalid mandatory information (96) Mandatory information element error (96)
Message type nonexistent or not Message type non-existent or not
implemented (97) implemented (97)
Message not compatible with short message Message not compatible with the short
protocol state (98) message transfer state (101)
Information element nonexistent or not Information element non-existent or not
implemented (99) implemented (99)
Protocol error, unspecified (111) Protocol error, unspecified (111)
Interworking, unspecified (127) Interworking, unspecified (127)
4
5 Table 10. Mapping of ANSI-136 R-Cause to ANSI-41

6 SMS_CauseCode.
ANSI-136 R-Cause ANSI-41 SMS_CauseCode
Memory capacity exceeded (22) Destination resource shortage (35)
Invalid short message transfer reference Other radio interface problem (66)
value (81)
Invalid message, unspecified (95) Other radio interface problem (66)
Mandatory information element error (96) Unrecognized parameter value (104) or
Encoding problem (96)
Message type non-existent or not Other radio interface problem (66)
implemented (97)
Message not compatible with the short Radio interface incompatibility (65) or
message transfer state (101) Other terminal problems (39)
Information element non-existent or not Unrecognised parameter value (104) or
implemented (99) Encoding problem (96)
Protocol error, unspecified (111) Unrecognised parameter value (104) or
Encoding problem (96)
Interworking, unspecified (127) Other radio interface problem (66)
7
19
Version 2.0
1 Table 11. Mapping of ANSI-41 SMS_CauseCode to Forward Short

2 Message Ack Return Error.
ANSI-41 SMS_CauseCode Return Error in Forward Short Message Ack
Destination resource shortage (35) SM-DeliveryFailure with cause
“MemoryCapacityExceeded”
Other radio interface problem (66) SM-DeliveryFailure with cause
“equipmentProtocolError”
Unrecognized parameter value (104) or SM-DeliveryFailure with cause
Encoding problem (96) “equipmentProtocolError”
Radio interface incompatibility (65) or SM-DeliveryFailure with cause
Other terminal problems (39) “equipmentProtocolError”
3
4 8.2 Mobile Originated Short Messaging Acknowledgements

5 When a GAIT mobile station has originated a GHOST teleservice in ANSI-136 Foreign Mode,
6 the IIF is responsible for mapping GSM MAP_FSM_ACK Return Errors to ANSI-41
7 SMS_CauseCodes according to Table 12. At the ANSI-136 MSC, the ANSI-41
8 SMS_CauseCodes are mapped to ANSI-136 R-DATA REJECT R-Cause codes according to
9 Table 13. The mobile station in turn maps that R-Cause codes to RP-ERROR Causes according to
10 Table 14.
11 Table 12. Mapping of Forward Short Message Ack Return Error to

12 ANSI-41 SMS_CauseCode for Network Response to
13 Mobile Originated Transfer Attempt.
Return Error in Forward Short Message Ack ANSI-41 SMS_CauseCode
DataMissing Network failure (3)
UnexpectedDataValue Other network problems (5)
TeleserviceNotProvisioned SMS origination denied (97)
CallBarred – barringServiceActive SMS origination denied (97)
CallBarred – operatorBarring SMS origination denied (97)
FacilityNotSupported SMS not supported (100)
SM-DeliveryFailure cause: unknownSC Address translation failure (1)
SM-DeliveryFailure cause: SC-Congestion Network resource shortage (2)
SM-DeliveryFailure cause: invalid SME-Addr Address translation failure (1)
SM-DeliveryFailure SMS origination denied (97)
cause: subscriberNotSC-Subscriber
Local or lower layer failure (e.g., reject Other network problems (5)
condition, timer expired or transaction abort)
14
20
Version 2.0
1 Table 13. Mapping ANSI-41 SMS_CauseCode to ANSI-136 R-Cause

2 Code.
ANSI-41 SMS_CauseCode ANSI-136 R-Cause
Network failure (3) Network out of order (38)
Other network problems (5) Network out of order (38)
SMS origination denied (97) Unidentified subscriber (28) or
Facility rejected (29)
SMS not supported (100) Requested facility not implemented (69)
Address translation failure (1) Destination out of service (27) or
Unknown subscriber (30)
Network resource shortage (2) Congestion (42)
3
4 Table 14. Mapping of ANSI-136 R-Cause Code to RP-ERROR

5 Cause within the Mobile Station.
ANSI-136 R-Cause RP-ERROR Cause
Destination out of service (27) Destination out of service (27)
Unidentified subscriber (28) Unidentified subscriber (28)
Facility rejected (29) Facility rejected (29)
Unknown subscriber (30) Unknown subscriber (30)
Network out of order (38) Network out of order (38)
Congestion (42) Congestion (42)
Requested facility not implemented (69) Requested facility not implemented (69)
6
7 8.3 Provisioning and Unsupported Feature Errors
8 Incoming MAP_FSM:
9 If the IIF receives a request to deliver a short message to a subscriber who:
10 a) Is not provisioned in the IIF, then the IIF shall send a MAP_FSM_ACK back to the
11 originating SMSC with the following error cause: Unidentified subscriber.
12 b) Does not have SMS support, then the IIF shall send a MAP_FSM_ACK back to the
13 originating SMSC with the following error cause: Facility not supported.
14 Incoming SMDPP:
15 If the IIF receives a request to deliver a short message to a subscriber who:
16 a) Is not provisioned in the IIF, then the IIF shall send an SMDPP Return Result back to the
17 originating SMSC with SMS_CauseCode#1 “Address Translation Failure”.
18 b) Does not have SMS support, then the IIF shall send an SMDPP Return Result back to the
19 originating SMSC with SMS_CauseCode #100 “SMS Not Supported”.
21
Version 2.0
1 9. Abbreviations
2 BMI Base Station, MSC and Interworking Function
3 DA Destination Address
4 DCS Data Coding Scheme
5 DT Discharge Time
6 DTC Digital Traffic Channel
7 ESN Electronic Serial Number
8 FSM Forward Short Message
9 GAIT GSM ANSI-136 Interoperability Team
10 GHOST GSM Hosted SMS Teleservice
11 GMSC Gateway Mobile Service switching Centre
12 GTA Global Title Address
13 HL-PDU Higher Layer Protocol Data Unit
14 HLPI Higher Layer Protocol Identifier
15 IIF Interworking and Interoperability Function
16 IWMSC InterWorking Mobile Services switching Centre
17 L Length
18 MAP Mobile Application Part
19 MC Message Center
20 MIN Mobile Identification Number
21 MMS More Messages to Send
22 MS Mobile Station
23 MSC Mobile Switching Center
24 MT Message Type
25 MTI Message Type Indicator
26 OA Originating Address
27 PD Protocol Discriminator
28 PDU Packet Data Unit
29 PID Protocol Identifier
30 RA Recipient Address
31 RDU R-Data Unit
32 R-ID R-Transaction Identifier
33 RP Reply Path
34 SAP Service Access Point
35 SCTS Service Centre Time Stamp
22
Version 2.0
1 SCA Service Centre Address

2 SM Short Message
3 SMDPP Short Message Delivery Point to Point
4 SMI Short Message Identifier
5 SMS Short Message Service
6 SMSC SMS Centre
7 SM-RL Short Message Relay Layer
8 SM-TL Short Message Transfer Layer
9 SRI Status Report Indication
10 ST Status
11 TSA Teleservice Server Address
12 TSAR Teleservice Segmentation and Reassembly
13 UD User Data
14 UDA User Destination Address
15 UDL User Data Length
16 UOA User Originating Address
17 VP Validity Period
18 VMSC Visited Mobile Switching Center
19 VPF Validity Period Format
20
23

Gait C 1 1 2 0

Uploaded by

Copyright:

Available Formats

Gait C 1 1 2 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Gait C 1 1 2 0

Uploaded by

Copyright:

Available Formats

GSM/ANSI-136 Interoperability Team Specification Document: GAIT-C-1-1-2-0

GSM Hosted SMS Teleservice Specification

Setting the pace of Global

4. GSM SMS TRANSFER PDU REQUIREMENTS .........................................................................................4

5. END-TO-END REQUIREMENTS ..................................................................................................................5

17 2.1 Mobile Equipment Requirements

22 Figure 1. Protocol Stack in Mobile Equipment to Support GHOST.

SM-TL (GSM SMS PDUs)

ANSI-136 Lower Layers GSM Lower Layers

4 2.2 Network Requirements

2 Figure 2. GHOST Example Protocol Stack for ANSI-136 Foreign

GSM SMS PDU

TIA/EIA-136 Layers 1 & 2

MS ANSI-136 BMI IIF GSM SMSC

8 Figure 3. GHOST Example Protocol Stack for GSM Foreign Mode.

GSM SMS PDU GSM SMS PDU

SM-RL GSM FSM TSAR TSAR

GSM MAP Layers 1 & 2 TIA/EIA-41 Layers 1 & 2

MS GSM MSC IIF ANSI-41 MC

3 Figure 4. GHOST Example Protocol Stack for ANSI-136 Native

GSM SMS PDU GSM SMS PDU

TIA/EIA-136 Layers 1 & 2 TIA/EIA-41 Layers 1 & 2

MS ANSI-136 BMI ANSI-41 MC

6 3. GHOST Higher Layer Protocol Identifier

9 Table 1. HLPI for GHOST.

11 4. GSM SMS Transfer PDU Requirements

4 5.2 Mobile Originated Service for ANSI-136 Foreign Mode

29 5.3 Mobile Terminated Service for GSM Foreign Mode

1 • Maps additional ANSI-41 SMDPP message parameters to GSM FSM message

5 5.4 Mobile Originated Service for GSM Foreign Mode

22 5.5 Mobile Terminated and Mobile Originated Service for ANSI-136

6 6. GHOST Teleservice Mapping

8 6.1 Mapping in ANSI-136 Networks

1 Figure 5. Mapping for Mobile Terminated GHOST Teleservice.

GSM SMS PDU

SMS_Destination User Destination

SMS_Message User Destination

SMS_Notification User Originating

SMS_Orig User Originating

SMS_Orig User Originating

SMS_Orig Multilingual User

SMS_Originating Multilingual User

1 Figure 6. Mapping for Mobile Originated GHOST Teleservice.

User Destination SMS_Message

User Originating SMS_Notification

User Originating SMS_Orig

User Originating SMS_Orig

1 6.2 Detailed Mapping in the Mobile Station

2 Figure 7. Mobile Terminated GSM SMS-DELIVER via GHOST.

MTI MMS RP SRI OA PID DCS SCTS UDL UD

PD MT R-ID RDU TSA UDA UOA R-DATA

4 Figure 8. Mobile Originated GSM SMS-SUBMIT via GHOST.

MTI VPF RP SRI MR DA PID DCS VP UDL UD

PD MT R-ID RDU TSA UDA UOA

6 Figure 9. Mobile Terminated GSM SMS-STATUS-REPORT via

1 7. IIF Mapping in the Network

10 7.1 GSM and ANSI-41 Mapping

17 Table 2. Mapping of Forward Short Message to SMDPP for

20 Note 1: If present, map parameters as indicated.