D.1 Introduction
24.0113GPPPoint-to-Point (PP) Short Message Service (SMS) support on mobile radio interfaceRelease 17TS
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 for circuit switched GSM.
For GPRS SMS transfer, refer to 3GPP TS 23.060 [3a] for channel set up and upper layer message flow.
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/3GPP TS 24.011: Mobile originated Short Message on SDCCH
Figure F2/3GPP TS 24.011: Mobile terminated Short Message on SDCCH
Figure F3/3GPP TS 24.011: Mobile originated Short Message on SACCH
Figure F4/3GPP TS 24.011: Mobile terminated Short Message on SACCH
Figure F5/3GPP TS 24.011: Inter/MSC handover during Short Message transfer on SACCH
Figure F6/3GPP TS 24.011: Inter/MSC handover during Short Message transfer on SDCCH
Annex G (informative):
Change history
|
Change history |
||||||
|---|---|---|---|---|---|---|
|
TSG SA# |
Spec |
Version |
CR |
<Phase> |
New Version |
Subject/Comment |
|
Jun 1999 |
GSM 04.11 |
7.0.0 |
Transferred to 3GPP CN1 |
|||
|
CN#04 |
24.011 |
3.0.0 |
Transferred to TSG CN at ETSI SMG#29. Under TSG TSG CN Change Control |
|||
|
CN#06 |
24.011 |
3.0.0 |
001r6 |
R99 |
3.1.0 |
Using MM sublayer for PS-SMS message transfer |
|
CN#07 |
24.011 |
3.1.0 |
003r1 |
R99 |
3.2.0 |
SMC-GP SDL modification to transfer SMS messages via GMM |
|
CN#07 |
24.011 |
3.1.0 |
004r1 |
R99 |
3.2.0 |
Reintroduction of deleted arrow diagrams |
|
CN#07 |
24.011 |
3.1.0 |
005 |
R99 |
3.2.0 |
Cleaning up the References |
|
TSGN |
TSGN-number |
WG Number |
CR |
Rev |
Rel |
Cat |
Old vers |
New ver |
Title |
WI |
Date |
|
CN#08 |
NP-000273 |
N1-000747 |
006 |
1 |
R99 |
C |
3.2.0 |
3.3.0 |
Alignment of SMS protocol with current MM/GMM integrity protection rules |
Security |
06-2000 |
|
CN#09 |
NP-000440 |
N1-000943 |
008 |
R99 |
A |
3.3.0 |
3.4.0 |
Corrections of CP/RP-DATA IE lengths |
TEI |
09-2000 |
|
|
NP-10 |
NP-000674 |
N1-001376 |
011 |
1 |
R99 |
F |
3.4.0 |
3.5.0 |
Terminology CR |
TEI |
12-2000 |
|
NP-10 |
NP-000673 |
N1-001220 |
012 |
R99 |
F |
3.4.0 |
3.5.0 |
Modifications of references |
TEI |
12-2000 |
|
|
NP-11 |
NP-010206 |
N1-010428 |
022 |
R99 |
F |
3.5.0 |
3.6.0 |
Missing SMR state |
TEI |
03-2001 |
|
|
NP-11 |
NP-010124 |
N1-010066 |
021 |
Rel-4 |
B |
3.6.0 |
4.0.0 |
Multipel SMS for PS in Iu mode |
TEI4 |
03-2001 |
|
|
NP-15 |
NP-020040 |
N1-020266 |
023 |
Rel-4 |
F |
4.0.0 |
4.1.0 |
Fixing references to 04.08 and to other GSM TS/TRs |
TEI4 |
03-2002 |
|
|
NP-16 |
Rel-5 |
4.1.0 |
5.0.0 |
TSGN#16 decided to update this TS also to release 5. |
06-2002 |
||||||
|
NP-18 |
NP-020570 |
N1-022498 |
024 |
2 |
Rel-5 |
F |
5.0.0 |
5.1.0 |
SMS over GPRS disabled |
TEI5 |
12-2002 |
|
NP-20 |
NP-030282 |
N1-030925 |
027 |
2 |
Rel-5 |
F |
5.1.0 |
5.2.0 |
UE behaviour when sending SMS over GPRS |
TEI5 |
06-2003 |
|
NP-21 |
NP-030420 |
N1-031325 |
031 |
Rel-6 |
F |
5.2.0 |
6.0.0 |
Unspecified SAPI value in RANAP message for MT SMS (Iu interface only) |
TEI6 |
09-2003 |
|
|
CP-28 |
CP-050068 |
C1-050546 |
033 |
Rel-6 |
F |
6.0.0 |
6.1.0 |
Multiple SMS via Gb mode |
TEI6 |
06-2005 |
|
|
6.1.0 |
7.0.0 |
Upgraded to Rel-7 by MCC |
06-2007 |
||||||||
|
7.0.0 |
8.0.0 |
Upgraded to Rel-8 by MCC |
12-2008 |
||||||||
|
CP-43 |
CP-090153 |
C1-091384 |
0034 |
2 |
Rel-8 |
B |
8.0.0 |
8.1.0 |
Support for SMS through the EPC |
SAES-CSFB |
03-2009 |
|
CP-43 |
Rel-8 |
8.0.0 |
8.1.0 |
Editorial cleanup by MCC |
03-2009 |
||||||
|
CP-44 |
CP-090404 |
C1-091630 |
0036 |
Rel-8 |
A |
8.1.0 |
8.2.0 |
Wrong implementation of CR 24.011-001 rev 6 |
TEI7 |
06-2009 |
|
|
CP-44 |
CP-090424 |
C1-091863 |
0037 |
Rel-8 |
F |
8.1.0 |
8.2.0 |
Correction to RP-Error handling procedures |
TEI8 |
06-2009 |
|
|
CP-46 |
Rel-9 |
8.2.0 |
9.0.0 |
Upgrade to Rel-9 by MCC |
12-2009 |
||||||
|
Rel-9 |
9.0.0 |
9.0.1 |
Addition of missing fields in the change history |
02-2010 |
|||||||
|
CP-51 |
Rel-10 |
9.0.1 |
10.0.0 |
Upgrade to Rel-10 by MCC |
03-2011 |
||||||
|
CP-56 |
CP-120315 |
C1-122327 |
0038 |
4 |
Rel-11 |
B |
10.0.0 |
11.0.0 |
Support of point to point direct SMS service via the MME |
SIMTC-PS_Only, SAES2-CSFB |
06-2012 |
|
CP-56 |
CP-120315 |
C1-122328 |
0039 |
4 |
Rel-11 |
B |
10.0.0 |
11.0.0 |
MME CM-Layer SDL description when SMS in MME is used |
SIMTC-PS_Only, SAES2-CSFB |
06-2012 |
|
CP-56 |
CP-120315 |
C1-122431 |
0040 |
5 |
Rel-11 |
B |
10.0.0 |
11.0.0 |
Transfer of SMS between the UE and the MME |
SIMTC-PS_only, SAES2-CSFB |
06-2012 |
|
CP-56 |
CP-120309 |
C1-122383 |
0041 |
1 |
Rel-11 |
B |
10.0.0 |
11.0.0 |
Missing CM-Layer SDL description on UE side for supporting SMS over SGs |
TEI11 |
06-2012 |
|
CP-57 |
CP-120589 |
C1-122722 |
0042 |
Rel-11 |
B |
11.0.0 |
11.1.0 |
SMS in MME terminology usage consistency |
SIMTC-PS_Only |
09-2012 |
|
|
CP-65 |
11.1.0 |
12.0.0 |
Upgrade to Rel-12 by MCC |
09-2014 |
|||||||
|
CP-70 |
12.0.0 |
13.0.0 |
Upgrade to Rel-13 by MCC |
12-2015 |
|||||||
|
CP-71 |
CP-160071 |
C1-161533 |
0044 |
5 |
Rel-13 |
B |
13.0.0 |
13.1.0 |
SMS with no combined attach for CIoT device |
CIoT-CT |
03-2016 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2016-09 |
CT#73 |
CP-160489 |
0045 |
2 |
F |
RPDU transfer for EPS using Control Plane CIoT Optimization |
13.2.0 |
|
2016-12 |
CT#74 |
CP-160723 |
0046 |
2 |
F |
SMS timer extension to support NB-S1 mode |
13.3.0 |
|
2017-03 |
CT#75 |
CP-170110 |
0047 |
3 |
F |
SMS timer extension for the MS in WB-S1 mode |
13.4.0 |
|
2017-03 |
CT#75 |
CP-170110 |
0048 |
2 |
B |
CM layer SDL updates for SMS transfer using Control Plane CIoT Optimization |
13.4.0 |
|
2017-03 |
CT#75 |
CP-170110 |
0049 |
F |
SMS arrow diagram for SMS transfer using Control Plane CIoT Optimization |
13.4.0 |
|
|
2017-03 |
SA#75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2017-06 |
CT#76 |
CP-171092 |
0051 |
1 |
F |
Conditions on supporting SMS transfer when MS is attached for PS |
14.1.0 |
|
2017-12 |
CT#78 |
CP-173050 |
0054 |
2 |
A |
Correction to SMS timers in NB-IoT |
14.2.0 |
|
2017-12 |
CT#78 |
CP-173054 |
0056 |
1 |
A |
Correction to SMS timers for CE mode UE |
14.2.0 |
|
2018-03 |
CT#79 |
CP-180077 |
0057 |
1 |
B |
Support for SMS in 5GS |
15.0.0 |
|
2018-06 |
CT#80 |
CP-181058 |
0058 |
1 |
C |
Removal of one-step SMS |
15.1.0 |
|
2018-09 |
CT#81 |
CP-182122 |
0060 |
A |
Correction on state transition diagrams for EPS when packet-switched service is used |
15.2.0 |
|
|
2018-09 |
CT#81 |
CP-182128 |
0061 |
F |
SDL description CM layer for 5G |
15.2.0 |
|
|
2019-03 |
CT#83 |
CP-190100 |
0064 |
1 |
F |
Usage of trigger to establish a PDN connection of non-IP type using the default APN to send indication to ESM entity |
15.3.0 |
|
2020-06 |
CT#88e |
CP-201133 |
0066 |
F |
SMS timer extension for the MS using CP CIoT 5GS optimization |
16.0.0 |
|
|
2020-06 |
CT#88e |
CP-201133 |
0067 |
1 |
F |
RPDU transfer for 5GS using Control Plane CIoT Optimization |
16.0.0 |
|
2020-12 |
CT#90e |
CP-203214 |
0068 |
F |
Removal of the extra occurrence of “Cause Value” in RP-Cause element |
17.0.0 |
|
|
2022-03 |
CT#95e |
CP-220248 |
0070 |
1 |
F |
SMS FSM graphes corrections |
17.1.0 |
|
2022-03 |
CT#95e |
CP-220264 |
0069 |
– |
F |
Correction to parameters of CM-sublayer primitives |
17.1.0 |
|
2022-06 |
CT#96e |
CP-221223 |
0071 |
– |
F |
Correction to primitives on arrow diagrams in Annex A |
17.2.0 |