Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 23.040
Short Message Service (SMS)

3GPP‑Page   ETSI‑search   eToC↓   LoFT↓   CONTENT →
V18.0.0 (PDF)  2024/03  221 p.
V17.3.0  2023/06  221 p.
V16.0.0  2020/06  220 p.
V15.3.0  2019/03  219 p.
V14.0.0  2017/03  218 p.
V13.2.0  2016/09  216 p.
V12.2.0  2013/12  211 p.
V11.5.0  2013/03  208 p.
V10.0.0  2011/04  204 p.
V9.3.0  2010/09  204 p.
V8.6.0  2009/09  203 p.
V7.2.0  2009/03  201 p.
V6.9.0  2008/06  193 p.
V5.9.0  2008/06  183 p.
V4.10.0  2008/06  130 p.
V3.11.0  2008/06  128 p.
GSM Rel-98 v7.5.0  2001/12  120 p.
GSM Rel-97 v6.2.0  2001/12  114 p.
GSM Rel-96 v5.8.1  1998/06  113 p.
GSM Phase-2 v4.13.0  1996/03  106 p.
GSM Phase-1 v3.7.0  1994/01  119 p.
Rapporteur:
Mr. Nassar, Mohamed Amin
Nokia Germany
3GPP 23.040 - SMS Architecture

essential Table of Contents for  TS 23.040  Word version:  18.0.0

each title, in the "available" or "not available yet" area, links to the equivalent title in the CONTENT
Here   Top

Up   Top

List of Figures and Tables

Figure 1The Short Message Service mobile terminated
Figure 2The Short Message Service mobile originated
Figure 3Example of how information on one MS can be put in relation to SC(s) in order to fulfil the requirement of Alert-SC mechanism
Figure 3aStructure of the MT Correlation ID
Table 1Error indications related to mobile terminated short message transfer which may be transferred to the originating SC
Table 1aAssignment of values to reasons for absence (values must be in the range of 0 to 255, see 3GPP TS 29.002 [15])
Figure 4Entities involved in the provision of SM MT and SM MO
Figure 5The main network structure serving as a basis for the short message transfer
Figure 6Reference configuration of the MS which apply to the SMS
Figure 7Protocol layer overview for the Short Message Service
Figure 821 bits from the octets 5, 6, 7, and 8 in a short message α) shall represent an integer as shown in β), and shall be transmitted in an order as shown in Γ)
Figure 9.1.2.3-1Example of Semi-octet representation
Figure 9.1.2.5-1Address field format
Figure 9.1.2.5-2Type-of-Address field format
Table 9.2.2.1-1Basic elements of the SMS-DELIVER type
Figure 9.2.2.1-1Layout of SMS-DELIVER
Table 9.2.2.1a-1Basic elements of the SMS-DELIVER-REPORT type for RP-ERROR
Figure 9.2.2.1a-1Layout of SMS-DELIVER-REPORT for RP-ERROR
Table 9.2.2.1a-2Basic elements of the SMS-DELIVER-REPORT type for RP-ACK
Figure 9.2.2.1a-2Layout of SMS-DELIVER-REPORT for RP-ACK
Table 9.2.2.2-1Basic elements of the SMS-SUBMIT type
Figure 9.2.2.2-1Layout of SMS-SUBMIT
Table 9.2.2.2a-1Basic elements of the SMS-SUBMIT-REPORT type for RP-ERROR
Figure 9.2.2.2a-1Layout of SMS-SUBMIT-REPORT for RP-ERROR
Table 9.2.2.2a-2Basic elements of the SMS-SUBMIT_REPORT type for RP-ACK
Figure 9.2.2.2a-2Layout of SMS-SUBMIT-REPORT for RP-ACK
Table 9.2.2.3-1Basic elements of the SMS-STATUS-REPORT type
Figure 9.2.2.3-1Layout of SMS-STATUS-REPORT
Table 9.2.2.4-1Basic elements of the SMS-COMMAND type
Figure 9.2.2.4-1Layout of SMS-COMMAND
Table 9.2.3.11-1
Table 9.2.3.19-1
Table 9.2.3.22-1
Figure 9.2.3.24-a
Figure 9.2.3.24-b
Figure 9.2.3.24-c
Figure 9.2.3.24.1-aConcatenation of a Compressed short message
Figure 9.2.3.24.10.1.13
Figure 9.2.3.24.10.1.15
Figure 9.2.3.24.10.1.15.1.aLZSS compressed data format
Figure 9.2.3.24.10.1.15.1.bLiteral block identifier
Figure 9.2.3.24.10.1.15.1.cSlice Descriptor
Figure 9.2.3.24.11-a
Figure 9.2.3.24.11-b
Figure 9.2.3.24.11-c
Table 9.2.3.24.13.1-1
Table 9.2.3.24.13.2-1
Figure 14Interfaces involved in the Short message mobile terminated procedure. GSM TS 43.002 [5]. X is the interface between an MSC and an SC as defined in clause 5
Figure 15aSuccessful short message transfer attempt via the MSC or the SGSN
Figure 15aaSuccessful short message transfer attempt via the SMS Router, and the MSC or SGSN
Figure 15bShort message transfer attempt failing due to error at the SMS-GMSC
Figure 15cShort message transfer attempt failing due to negative outcome of HLR information retrieval
Figure 15caShort message transfer attempt via the SMS Router failing due to negative outcome of HLR information retrieval
Figure 15dShort message transfer attempt failing due to error at the MSC or SGSN
Figure 15eShort message transfer attempt failing due to negative outcome of VLR information retrieval
Figure 15fShort message transfer attempt failing due to erroneous message transfer on the radio path
Figure 15gShort message transfer attempt failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC)
Figure 15gaShort message transfer attempt via the SMS Router failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC)
Figure 15hShort message transfer attempt failing over the first path (e.g. SGSN) and over the second path (e.g. MSC)
Figure 16a"Send information for MT SMS" procedure; error free case
Figure 16b"Send information for MT SMS" procedure; erroneous case: absent subscriber (e.g. IMSI DETACH or GPRS DETACH)
Figure 16c"Send information for MT SMS" procedure; erroneous case: Absent subscriber (e.g. no paging response)
Figure 16d"Send information for MT SMS" procedure; incorrect authentication
Figure 17aSuccessful short message transfer attempt via the MSC, SGSN or MME, with short message retransmission by the SMS-GMSC at the time requested by the MSC, SGSN or MME
Figure 17bSuccessful short message transfer attempt via the MSC, SGSN or MME, with short message retransmission by the SMS-GMSC upon MS originated signalling prior to the retransmission time requested by the MSC, SGSN or MME
Figure 17cSuccessful short message transfer attempt via the MSC, SGSN or MME, with short message retransmission by the SMS-GMSC upon MS mobility to a new serving node prior to the retransmission time requested by the MSC, SGSN or MME.
Figure 17Interfaces involved in the Short message mobile originated procedure GSM TS 43.002 [5]. X is the interface between an MSC or an SGSN and an SC as defined in clause 5.
Figure 18aSuccessful short message transfer attempt
Figure 18bShort message transfer attempt failing due to error at the MSC or SGSN
Figure 18cShort message transfer attempt failing due to negative outcome of VLR information retrieval
Figure 18dShort message transfer attempt failing due to error at the SMS-IWMSC
Figure 18eShort message transfer attempt failing due to error at the SC
Figure 18fShort Message transfer Successful due to the existence of an SMS Interworking agreement
Figure 18gShort Message transfer attempt failing due to non-existence of an SMS Interworking agreement
Figure 18hShort Message transfer attempt failing due to negative outcome of HLR information retrieval
Table 10.2-1
Figure 19Interfaces involved in the Alert procedure. X is the interface between an SC and an MSC as defined in clause 5
Figure 20aThe alert procedure when the MS becomes reachable, MNRF, MNRG or both are set and MCEF is not set
Figure 20bThe alert procedure when the MS becomes reachable, MNRF, MNRG or both are set and MCEF is set
Figure 20cThe alert procedure when the MS notifies the network that it has memory available to receive one or more short messages and MCEF is set
Table 11.1-1
Table 11.2-1
Table 11.3-1
Table 11.3-2
Figure C.1Mobile terminated short message
Figure C.2Mobile terminated short message
Figure C.3Mobile terminated short message
Figure C.4Mobile terminated short message
Figure C.5Acknowledgement in the MT case
Figure C.6Acknowledgement in the MT case
Figure C.7Acknowledgement in the MT case
Figure C.8Acknowledgement in the MT case
Figure C.9Mobile originated short message
Figure C.10Mobile originated short message
Figure C.11Mobile originated short message
Figure C.12Mobile originated short message
Figure C.13Acknowledgement in the MO case
Figure C.14Acknowledgement in the MO case
Figure C.15Acknowledgement in the MO case
Figure C.16Acknowledgement in the MO case
Figure F.1Illustration of "Implicit Dictionary" compression methods
Figure F.2Sample input buffer (16 octets long)
Figure F.3Output buffer after initial literal block is written
Figure F.4Output buffer after the first slice descriptor is written
Figure F.5Second literal block is written into output buffer
Figure F.6Octet match slice descriptor is written into output buffer
Figure F.7Octet match slice descriptor is written into output buffer: the final output buffer
Figure G.1.3.1-1
Figure G.1.3.1-2
Figure G.1.3.2-1
Figure G.2.1.2-1
Figure G.2.1.4-1
Figure G.2.3.2-1
Figure G.2.4-1
Figure G.2.4-2
Table I.1Mapping between architecture and reference points for SMS in MME and the present specification
Table J.1Mapping between architecture and reference points for SMS over SGSN using Diameter interface and the present specification
Table K.1Mapping between architecture and reference points for SMS in 5GS and the present specification

Top