D.1 Introduction

04.113GPPPoint-to-Point (PP) Short Message Service (SMS) support on mobile radio interfaceRelease 1996TS

This annex contains an SDL‑description of the Short Message Relay Layer in terms of the Short Message Service Support. The Short Message Relay Layer provides services to Short Message Transfer Layer.

The SDLs contain a mixture of peer to peer messages and conceptual primitives between the layers SM‑TL, SM‑RL and CM, as viewed by the SMR entities. SDL‑1/2/3 show the SMR entity on MS‑side, and SDL‑4/5 on the network side.

The lower layers (below CM) are transparent to an SMR entity.

SMR-entity on MS-side
MO Short Message transfer
SDL‑1

SMR-entity on MS-side
MT Short Message transfer
SDL‑2

SMR-entity on MS-side
Memory Available Notification
SDL‑3

SMR-entity on MS-side
State transition diagram

SMR-entity on Network-side
MT Short Message transfer
SDL‑4

SMR-entity on Network-side
MO Short Message and Notification transfer
SDL‑5

SMR-entity on Network-side
State transition diagram

Annex E (informative):
Cause definition

E‑1: CP‑cause definition

Cause no. 17: "Network failure"

This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.

Cause no. 22: "Congestion"

This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).

Cause no. 81: "Invalid Transaction Identifier"

This cause indicates that the equipment sending this cause has received a message with a Transaction Identifier which is currently not use on the MS ‑ network interface.

Cause no. 95: "Semantically incorrect message"

This cause is used to report the receipt of a message with semantically incorrect content.

Cause no. 96: "Invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message with non‑semantical mandatory information element errors.

Cause no. 97: "Message type non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

Cause no. 98: "Message not compatible with short message protocol state"

This cause indicates that the equipment sending this cause has received a message not compatible with the Short Message protocol state.

Cause no. 99: "Information element non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause.

However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause no. 111: "Protocol error, unspecified"

This cause is used to report a protocol error event only when no other cause applies.

E‑2: RP‑cause definition mobile originating SM‑transfer

Cause no. 1: "Unassigned (unallocated) number"

This cause indicates that the destination requested by the Mobile Station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

Cause no. 8: "Operator determined barring"

This cause indicates that the MS has tried to send a mobile originating short message when the MS’s network operator or service provider has forbidden such transactions.

Cause no. 10: "Call barred"

This cause indicates that the outgoing call barred service applies to the short message service for the called destination.

Cause no. 21: "Short message transfer rejected"

This cause indicates that the equipment sending this cause does not wish to accept this short message, although it could have accepted the short message since the equipment sending this cause is neither busy nor incompatible.

Cause no. 27: "Destination out of service"

This cause indicates that the destination indicated by the Mobile Station cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off‑line, etc.

Cause no. 28: "Unidentified subscriber"

This cause indicates that the subscriber is not registered in the PLMN (i.e. IMSI not known).

Cause no. 29: "Facility rejected"

This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.

Cause no. 30: "Unknown subscriber"

This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not allocated to a subscriber).

Cause no. 38: "Network out of order"

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be successful.

Cause no. 41: "Temporary failure"

This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost immediately.

Cause no. 42: "Congestion"

This cause indicates that the short message service cannot be serviced because of high traffic.

Cause no. 47: "Resources unavailable, unspecified"

This cause is used to report a resource unavailable event only when no other cause applies.

Cause no. 50: "Requested facility not subscribed"

This cause indicates that the requested short message service could not be provided by the network because the user has not completed the necessary administrative arrangements with its supporting networks.

Cause no. 69: "Requested facility not implemented"

This cause indicates that the network is unable to provide the requested short message service.

Cause no. 81: "Invalid short message transfer reference value"

This cause indicates that the equipment sending this cause has received a message with a short message reference which is not currently in use on the MS‑network interface.

Cause no. 95: "Invalid message, unspecified"

This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Cause no. 96: "Invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message where a mandatory information element is missing and/or has a content error (the two cases are indistinguishable).

Cause no. 97: "Message type non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

Cause no. 98: "Message not compatible with short message protocol state"

This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the short message transfer state.

Cause no. 99: "Information element non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause.

However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause no. 111: "Protocol error, unspecified"

This cause is used to report a protocol error event only when no other cause applies.

Cause no. 127: "Interworking, unspecified"

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being send cannot be ascertained.

E‑3: RP‑cause definition mobile terminating SM‑transfer

Cause no. 22: "Memory capacity exceeded"

This cause indicates that the mobile station cannot store the incoming short message due to lack of storage capacity.

Cause no. 81: "Invalid short message reference value"

This cause indicates that the equipment sending this cause has received a message with a short message reference which is not currently in use on the MS‑network interface.

Cause no. 95: "Invalid message, unspecified"

This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Cause no. 96: "Invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message where a mandatory information element is missing and/or has a content error (the two cases are indistinguishable).

Cause no. 97: "Message type non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

Cause no. 98: "Message not compatible with short message protocol state"

This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the short message transfer state.

Cause no. 99: "Information element non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause.

However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause no. 111: "Protocol error, unspecified"

This cause is used to report a protocol error event only when no other cause applies.

E‑4: RP‑Cause definition memory available notification

Cause no. 30: "Unknown Subscriber"

This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not allocated to a subscriber).

Cause no. 38: "Network out of order"

This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be successful.

Cause no. 41: "Temporary failure"

This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost immediately.

Cause no. 42: "Congestion"

This cause indicates that the short message service cannot be serviced because of high traffic.

Cause no. 47: "Resources unavailable, unspecified"

This cause is used to report a resource unavailable event only when no other cause applies.

Cause no. 69: "Requested facility not implemented"

This cause indicates that the network is unable to provide the requested memory available notification service.

Cause no. 95: "Invalid message, unspecified"

This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Cause no. 96: "Invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message where a mandatory information element is missing and/or has a content error (the two cases are indistinguishable).

Cause no. 97: "Message type non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

Cause no. 98: "Message not compatible with short message protocol state"

This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the short message transfer state.

Cause no. 99: "Information element non‑existent or not implemented"

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause.

However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

Cause no. 111: "Protocol error, unspecified"

This cause is used to report a protocol error event only when no other cause applies.

Cause no. 127: "Interworking, unspecified"

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being send cannot be ascertained.

Annex F (informative):
LAPDm SAPI 3 handling for short message service

This annex describes several typical SMS message transfer scenarios.

Case A: Mobile originating short message transfer, no parallel call.

The mobile station side will initiate SAPI 3 establishment by a SABM command on the SDCCH after the cipher mode has been set. If no hand over occurs, the SAPI 3 link will stay up until the last CP‑ACK is received by the MSC, and the clearing procedure is invoked.

Case B: Mobile terminating short message transfer, no parallel call.

The network side, i.e. the BSS will initiate SAPI3 establishment by a SABM command on the SDCCH when the first CP‑Data message is received from the MSC. If no hand over occurs, the link will stay up until the MSC has given the last CP‑ack and invokes the clearing procedure.

Case C: Mobile originating short message transfer, parallel call.

The mobile station will send a SABM command on the SACCH when a CM_SERV_ACC message has been received from the network, allowing the short message transfer to start. If no hand over occurs the link will stay up until the MSC orders a explicit release, or the clearing procedure is invoked. If the parallel call is cleared before the short message transfer is finalized, the MSC will delay the clearing procedure toward the BSS, i.e. the channel release procedure is delayed.

Case D: Mobile terminating short message transfer, parallel call.

The network side, i.e. the BSS will initiate SAPI3 establishment by a SABM command on the SACCH when the first CP‑DATA message is received from the MSC. The further handling is exactly as described for case C.

Case E: Mobile terminating short message transfer together with Inter‑MSC hand over, parallel call.

The MAP procedures "Forward access signalling" and "Process access signalling" will be used between the two MSCs to transfer the CP‑DATA, CP‑ACK and CP‑ERROR messages.

Case F: Mobile terminating short message transfer on SDCCH channel together with Inter‑MSC hand over.

The MAP procedures "Forward access signalling" and "Process access signalling" will be used between the two MSC’s to transfer the CP‑DATA, CP‑ACK and CP‑ERROR messages.

Figure F1/GSM 04.11: Mobile originated Short Message on SDCCH

Figure F2/GSM 04.11: Mobile terminated Short Message on SDCCH

Figure F3/GSM 04.11: Mobile originated Short Message on SACCH

Figure F4/GSM 04.11: Mobile terminated Short Message on SACCH

Figure F5/GSM 04.11: Inter/MSC handover during Short Message transfer on SACCH

Figure F6/GSM 04.11: Inter/MSC handover during Short Message transfer on SDCCH

Annex G (informative):
Change history

TSG#

TSG TD

WG TD

Spec

CR

Rev

Ph

Cat

Vers
Old

Vers
New

Subject

Notes

NP-09

NP-000440

N1-000940

04.11

A020

R96

F

5.2.1

5.3.0

Corrections of CP/RP-DATA IE lengths.

NP-09

04.11

5.2.1

5.3.0

Converted to 3GPP document format