SIST ETS 300 536 E1:2003
(Main)European digital cellular telecommunications system (Phase 2); Technical realization of Short Message Service (SMS) Point-to-Point (PP) (GSM 03.40)
European digital cellular telecommunications system (Phase 2); Technical realization of Short Message Service (SMS) Point-to-Point (PP) (GSM 03.40)
....
Evropski digitalni celični telekomunikacijski sistem (faza 2) – Tehnična realizacija storitev kratkih sporočil (SMS) točka-točka (PP) (GSM 03.40)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
(YURSVNLGLJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ±7HKQLþQDUHDOL]DFLMD
VWRULWHYNUDWNLKVSRURþLO 606 WRþNDWRþND 33 *60
European digital cellular telecommunications system (Phase 2); Technical realization of
Short Message Service (SMS) Point-to-Point (PP) (GSM 03.40)
Ta slovenski standard je istoveten z: ETS 300 536 Edition 1
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 536
TELECOMMUNICATION October 1994
STANDARD
Source: TC-SMG Reference: DE/SMG-040340P
ICS: 33.060.30
European digital cellular telecommunications system, Global System for Mobile communications
Key words:
(GSM)
European digital cellular telecommunications system (Phase 2);
Technical Realization of the Short Message Service (SMS)
Point-to-Point (PP)
(GSM 03.40)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1994. All rights reserved.
New presentation - see History box
Page 2
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
Contents
Foreword.7
0.1 Scope .9
0.2 Normative references .9
0.3 Definitions and abbreviations.10
0.3.1 Key definitions.11
0.3.2 Abbreviations.13
1 Introduction.13
2 Not used. 13
3 Services and service elements . 13
3.1 Basic services.13
3.2 Short Message Service elements .15
3.2.1 Validity-Period.15
3.2.2 Service-Centre-Time-Stamp.15
3.2.3 Protocol-Identifier.15
3.2.4 More-Messages-to-Send.15
3.2.5 Delivery of Priority and non-Priority Messages.16
3.2.6 Messages-Waiting.16
3.2.7 Alert-SC .18
3.2.8 Options concerning MNRF, MCEF and MWD .18
3.2.9 Status report capabilities . 19
3.2.10 Reply Path.19
3.3 Unsuccessful short message TPDU transfer SC -> MS .20
3.3.1 Errors occurring during transfer of TPDU to MS. 20
3.3.2 Errors occurring after TPDU arrives at MS.20
3.4 Unsuccessful short message TPDU transfer MS -> SC .22
3.4.1 Errors occurring during transfer of TPDU to SC .22
3.4.2 Errors occurring after TPDU arrives at SC.22
3.5 Use of Supplementary Services in combination with the Short Message Service.22
3.6 Applicability of Operator Determined Barring to the Short Message Service .22
3.7 Multiple short message transfer .22
4 Network architecture .23
4.1 Basic network structure .23
4.2 Transfer on link 3 .24
5 Service Centre and PLMN interconnection.24
5.1 Service centre connection .24
5.2 Routing requirements. 24
5.2.1 Mobile terminated short message.24
5.2.2 Mobile originated short message.24
6 Service Centre functionality.25
6.1 Service Centre capabilities.25
6.2 SC functional requirements .25
7 MS functionality.26
7.1 MS capabilities .26
7.2 MS configuration.26
8 MSC functionality .27
8.1 MSC functionality related to SM MT .27
Page 4
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
8.1.1 Functionality of the SMS-GMSC .27
8.1.2 Functionality of the MSC .28
8.2 MSC functionality related to SM MO.28
8.2.1 Functionality of the MSC .28
8.2.2 Functionality of the SMS-IWMSC.29
8.3 SMS-IWMSC functionality related to alerting .29
9 Protocols and protocol architecture.30
9.1 Protocol element features .30
9.1.1 Octet and Bit transmission order.30
9.1.2 Numeric and alphanumeric representation.30
9.1.2.1 Integer representation.30
9.1.2.2 Octet representation .31
9.1.2.3 Semi-octet representation .31
9.1.2.4 Alphanumeric representation.32
9.1.2.5 Address fields .32
9.2 Service provided by the SM-TL .34
9.2.1 General .34
9.2.2 PDU Type repertoire at SM-TL.34
9.2.2.1 SMS-DELIVER type.35
9.2.2.1a SMS-DELIVER-REPORT type.37
9.2.2.2 SMS-SUBMIT type .38
9.2.2.2a SMS-SUBMIT-REPORT type .40
9.2.2.3 SMS-STATUS-REPORT type .41
9.2.2.4 SMS-COMMAND type .43
9.2.3 Definition of the TPDU parameters.44
9.2.3.1 TP-Message-Type-Indicator (TP-MTI).44
9.2.3.2 TP-More-Messages-to-Send (TP-MMS).44
9.2.3.3 TP-Validity-Period-Format (TP-VPF).44
9.2.3.4 TP-Status-Report-Indication (TP-SRI) .44
9.2.3.5 TP-Status-Report-Request (TP-SRR).45
9.2.3.6 TP-Message-Reference (TP-MR) .45
9.2.3.7 TP-Originating-Address (TP-OA) .45
9.2.3.8 TP-Destination-Address (TP-DA) .45
9.2.3.9 TP-Protocol-Identifier (TP-PID).45
9.2.3.10 TP-Data-Coding-Scheme (TP-DCS).47
9.2.3.11 TP-Service-Centre-Time-Stamp (TP-SCTS).47
9.2.3.12 TP-Validity-Period.47
9.2.3.13 TP-Discharge-Time (TP-DT).48
9.2.3.14 TP-Recipient-Address (TP-RA).48
9.2.3.15 TP-Status (TP-ST).48
9.2.3.16 TP-User-Data-Length (TP-UDL).50
9.2.3.17 TP-Reply-Path (TP-RP).50
9.2.3.18 TP-Message-Number (TP-MN) .50
9.2.3.19 TP-Command-Type (TP-CT).51
9.2.3.20 TP-Command-Data-Length (TP-CDL).51
9.2.3.21 TP-Command-Data (TP-CD).51
9.2.3.22 TP-Failure-Cause (TP-FCS) .51
9.3 Service provided by the SM-RL .52
9.3.1 General .52
9.3.2 Protocol element repertoire at SM-RL.53
9.3.2.1 RP-MO-DATA .53
9.3.2.2 RP-MT-DATA.54
9.3.2.3 RP-ACK.54
9.3.2.4 RP-ERROR.54
9.3.2.5 RP-ALERT-SC .55
9.3.2.6 RP-SM-MEMORY-AVAILABLE .55
10 Fundamental procedures within the point-to-point SMS.55
10.1 Short message mobile terminated.56
Page 5
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
10.2 Short message mobile originated. 64
10.3 Alert transfer .68
11 Mapping of error causes between RP layers.72
11.1 Mobile Terminated short message transfer . 72
11.2 Memory available notification .72
11.3 Mobile Originated short message transfer.73
Annex 1 (informative): PROTOCOL STACKS FOR INTERCONNECTING SCs AND MSCs.74
Annex 2.75
Annex 3 (informative): SHORT MESSAGE INFORMATION FLOW.76
Annex 4 (informative): MOBILE STATION REPLY PROCEDURES.94
1 Introduction.94
2 The scope of applicability.94
3 Terminology.94
4 The reply path requesting procedure.95
5 The reception of an original MT SM.95
6 The submission of the reply MO SM.95
7 Usage of SCs for replying.96
8 Replying possibilities for phase 1 mobile stations.96
9 The resulting service for originating SMEs.96
History.97
Page 6
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
Blank page
Page 7
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
Foreword
This European Telecommunication Standard (ETS) has been produced by the Special Mobile Group
(SMG) Technical Committee (TC) of the European Telecommunications Standards Institute (ETSI).
This ETS defines the technical realization of the Point-to-Point (PP) Short Message Service (SMS) for the
European digital cellular telecommunications system (Phase 2). This ETS corresponds to GSM Technical
Specification (GSM-TS) GSM 03.40 version 4.9.1.
The specification from which this ETS has been derived was originally based on CEPT documentation,
hence the presentation of this ETS may not be entirely in accordance with the ETSI/PNE rules.
Reference is made within this ETS to GSM-TSs.
NOTE: TC-SMG has produced documents which give the technical specifications for the
implementation of the European digital cellular telecommunications system. Historically,
these documents have been identified as GSM Technical Specifications (GSM-TSs).
These TSs may have subsequently become I-ETSs (Phase 1), or ETSs (Phase 2),
whilst others may become ETSI Technical Reports (ETRs). GSM-TSs are, for editorial
reasons, still referred to in current GSM ETSs.
Page 8
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
Blank page
Page 9
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
0.1 Scope
This specification describes the point-to-point Short Message Service (SMS) of the GSM PLMN system. It
defines:
- the services and service elements,
- the network architecture,
- the Service Centre functionality,
- the MSC functionality (with regard to the SMS),
- the routing requirements,
- the protocols and protocol layering,
for the Teleservices 21 and 22, as specified in the GSM 02.03.
The use of radio resources for the transfer of short messages between the MS and the MSC is described
in GSM 04.11 'Point-to-Point Short Message Service Support on Mobile Radio Interface', and is dealt with
in that specification.
The network aspects of Short Message Service provision are outside the scope of this specification (i.e.
the provision of network connectivity between the PLMN subsystems). The required and assumed network
service offered to the higher layers is defined in this specification.
The Cell Broadcast Short Message Service (Teleservice 23) is a separate service, and is described in
GSM 03.41 'Technical Realization of the Short Message Service - Cell Broadcast'.
0.2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply
to this ETS only when incorporated in it by amendment or revision. For undated references, the latest
edition of the publication referred to applies.
[1] GSM 01.04 (ETR 100): "European digital cellular telecommunication system
(Phase 2); Definitions, abbreviations and acronyms".
[2] GSM 02.03 (ETS 300 502): "European digital cellular telecommunication system
(Phase 2); Teleservices supported by a GSM Public Land Mobile Network
(PLMN)".
[3] GSM 02.04 (ETS 300 503): "European digital cellular telecommunication system
(Phase 2); General on supplementary services".
[4] GSM 02.41 (ETS 300 513): "European digital cellular telecommunication system
(Phase 2); Operator determined barring".
[5] GSM 03.02 (ETS 300 522): "European digital cellular telecommunication system
(Phase 2); Network architecture".
[6] GSM 03.08 (ETS 300 526): "European digital cellular telecommunication system
(Phase 2); Organisation of subscriber data".
[7] GSM 03.11 (ETS 300 529): "European digital cellular telecommunication system
(Phase 2); Technical realization of supplementary services".
[8] GSM 03.15 (ETS 300 533): "European digital cellular telecommunication system
(Phase 2); Technical realization of operator determined barring".
Page 10
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
[9] GSM 03.38 (ETS 300 537): "European digital cellular telecommunication system
(Phase 2); Alphabets and language-specific information".
[10] GSM 03.41 (ETS 300 537): "European digital cellular telecommunication system
(Phase 2); Technical realization of Short Message Service Cell Broadcast
(SMSCB)".
[11] GSM 03.47 (ETR 106): "European digital cellular telecommunication system
(Phase 2); Example protocol stacks for interconnecting Service Centre(s) (SC)
and Mobile-services Switching Centre(s) (MSC)".
[12] GSM 04.08 (ETS 300 557): "European digital cellular telecommunication system
(Phase 2); Mobile radio interface layer 3 specification".
[13] GSM 04.11 (ETS 300 559): "European digital cellular telecommunication system
(Phase 2); Point-to-Point (PP) Short Message Service (SMS) support on mobile
radio interface".
[14] GSM 07.05 (ETS 300 585): "European digital cellular telecommunication system
(Phase 2); Use of Data Terminal Equipment - Data Circuit terminating Equipment
(DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast
Service (CBS)".
[15] GSM 09.02 (ETS 300 599): "European digital cellular telecommunication system
(Phase 2); Mobile Application Part (MAP) specification".
[16] GSM 11.11 (ETS 300 608): "European digital cellular telecommunication system
(Phase 2); Specification of the Subscriber Identity Module - Mobile Equipment
(SIM - ME) interface".
[17] CCITT Recommendation E.164 (Blue Book): "Numbering plan for the ISDN era".
[18] CCITT Recommendation E.163 (Blue Book): "Numbering plan for the
international telephone service".
[19] CCITT Recommendation Q.771: "Specifications of Signalling System No.7;
Functional description of transaction capabilities".
[20] CCITT Recommendation T.100 (Blue Book): "International information exchange
for interactive videotex".
[21] CCITT Recommendation T.101 (Blue Book): "International interworking for
videotex services".
[22] CCITT Recommendation X.121 (Blue Book): "International numbering plan for
public data networks".
[23] CCITT Recommendation X.400 (Blue Book): "Message handling system and
service overview".
0.3 Definitions and abbreviations
Note: Use of hyphens and full stops:
Care is needed when reading this specification as names containing words separated by hyphens
have different meaning than when separated with full stops. E.g. TS-Status-Report-Request is a
parameter within a TS-Submit primitive, whilst TS-Status-Report.Request is a primitive in its own
right.
Page 11
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
0.3.1 Key definitions
Active MS: A switched-on mobile station with a SIM module attached.
Alert-SC: Service element provided by a GSM PLMN to inform an SC which has previously initiated
unsuccessful short message delivery attempt(s) to a specific MS, that the MS is now recognized by the
PLMN to have recovered operation.
Status Report: SC informing the originating MS of the outcome of a short message submitted to an SME.
Gateway MSC for Short Message Service (SMS-GMSC): A function of an MSC capable of receiving a
short message from an SC, interrogating an HLR for routing information and SMS info, and delivering the
short message to the VMSC of the recipient MS.
Interworking MSC for Short Message Service (SMS-IWMSC): A function of an MSC capable of receiving
a short message from within the PLMN and submitting it to the recipient SC.
Messages-Waiting (MW): Service element that makes a PLMN store information (Messages-Waiting-
Indication), listing those SCs that have made unsuccessful short message delivery attempts to MSs in that
PLMN.
Messages-Waiting-Indication (MWI): Data to be stored in the HLR and VLR with which an MS is
associated, indicating that there is one or more messages waiting in a set of SCs to be delivered to the
MS (due to unsuccessful delivery attempt(s)).
Messages-Waiting-Data (MWD): A part of the MWI to be stored in the HLR. MWD consists of an address
list of the SCs which have messages waiting to be delivered to the MS.
Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF): A part of the MWI to be stored in the HLR.
MCEF is a boolean parameter indicating if the address list of MWD contains one or more entries because
an attempt to deliver a short message to an MS has failed with a cause of MS Memory Capacity
Exceeded.
Mobile-Station-Not-Reachable-Flag (MNRF): The part of the MWI to be stored in the VLR and the HLR.
MNRF is a boolean parameter indicating if the address list of MWD contains one or more entries because
an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber.
More-Messages-to-Send (MMS): Information element offering an MS receiving a short message from an
SC the information whether there are still more messages waiting to be sent from that SC to the MS.
Priority: Service element enabling the SC or SME to request a short message delivery attempt to an MS
irrespective of whether or not the MS has been identified as temporarily absent.
Protocol-Identifier: Information element by which the originator of a short message (either an SC or an
MS) may refer to a higher layer protocol.
Reply Path Procedure: A mechanism which allows an SME to request that an SC should be permitted to
handle a reply sent in response to a message previously sent from that SME to another SME. This may
happen even though the SC may be unknown to the SME which received the initial message.
Report: Response from either the network or the recipient upon a short message being sent from either
an SC or an MS. A report may be a delivery report, which confirms the delivery of the short message to
the recipient, or it may be a failure report, which informs the originator that the short message was never
delivered and the reason why.
When issued by the Service Centre, the delivery report confirms the reception of the Short Message by the
SC, and not the delivery of the Short Message to the SME.
When issued by the Mobile Station, the delivery report confirms the reception of the Short Message by the
Mobile Station, and not the delivery of the Short Message to the user.
Page 12
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
Replace Short Message Type:
A range of values in the Protocol Identifier which allows an indication to be sent with a short message (MT
or MO) that the short message is of a particular type allowing the receiving MS or the SC to replace an
existing message of the same type held in the SC, the ME or on the SIM, provided it comes:
- in MT cases: from the same SC and originating address;
- in MO cases: from the same MS.
Service Centre (SC): Function responsible for the relaying and store-and-forwarding of a short message
between an SME and an MS. The SC is not a part of the GSM PLMN, however MSC and SC may be
integrated.
Short Message: Information that may be conveyed by means of the Short Message Service described in
this specification.
Short Message Entity (SME): An entity which may send or receive Short Messages. The SME may be
located in a fixed network, an MS, or an SC.
SMS-STATUS-REPORT: Short message transfer protocol data unit informing the receiving MS of the
status of a mobile originated short message previously submitted by the MS, i.e. whether the SC was able
to forward the message or not, or whether the message was stored in the SC for later delivery.
SMS-COMMAND: Short message transfer protocol data unit which enables an MS to invoke an operation
at the SC. An MS may then, for example, delete a short message, cancel a Status Report Request,
enquire about the status of a short message or request another function to be performed by the SC.
The type of operation is indicated by the TS-Command-Type and the particular SM to operate on is
indicated by the TS-Message-Number. The response to an SMS-COMMAND is an SMS-STATUS-
REPORT, the outcome of the operation being passed in its TS-status field.
SMS-DELIVER: Short message transfer protocol data unit containing user data (the short message),
being sent from an SC to an MS.
SMS-SUBMIT: Short message transfer protocol data unit containing user data (the short message), being
sent from an MS to an SC.
Service-Centre-Time-Stamp (SCTS): Information element offering the recipient of a short message the
information of when the message arrived at the SM-TL entity of the SC. The time of arrival comprises the
year, month, day, hour, minute, second and time zone.
Validity-Period (VP): Information element enabling the originator MS to indicate the time period during
which the originator considers the short message to be valid.
Page 13
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
0.3.2 Abbreviations
In addition to those below, definitions used in this specification are listed in GSM 01.04.
E.163 CCITT Rec. E.163 (Blue Book)
E.164 CCITT Rec. E.164 (Blue Book)
ACSE Association Control Service Element
SM MT Short Message Mobile Terminated Point-to-Point
SM MO Short Message Mobile Originated Point-to-Point
SM-AL Short Message Application Layer
SM-TL Short Message Transfer Layer
SM-RL Short Message Relay Layer
SM-LL Short Message Lower Layers
SM-TP Short Message Transfer Layer Protocol
SM-RP Short Message Relay Layer Protocol
SM-TS Short Message Transfer Service
SM-RS Short Message Relay Service
T.100 CCITT Rec. T.100 (Blue Book)
T.101 CCITT Rec. T.101 (Blue Book)
TPDU Transfer protocol data unit
X.121 CCITT Rec. X.121 (Blue Book)
X.400 CCITT Rec. X.400 (Blue Book)
1 Introduction
The Point-to-Point Short Message Service (SMS) provides a means of sending messages of limited size to
and from GSM mobiles. The provision of SMS makes use of a Service Centre, which acts as a store and
forward centre for short messages. Thus a GSM PLMN needs to support the transfer of short messages
between Service Centres and mobiles.
Two different point-to-point services have been defined: mobile originated and mobile terminated. Mobile
originated messages will be transported from an MS to a Service Centre. These may be destined for other
mobile users, or for subscribers on a fixed network. Mobile terminated messages will be transported from
a Service Centre to an MS. These may be input to the Service Centre by other mobile users (via a mobile
originated short message) or by a variety of other sources, e.g. speech, telex, or facsimile.
2 Not used
3 Services and service elements
The SMS provides a means to transfer short messages between a GSM MS and an SME via an SC. The
SC serves as an interworking and relaying function of the message transfer between the MS and the SME.
This specification describes only the short message point-to-point services between the MS and SC. It
may, however, refer to possible higher layer applications.
3.1 Basic services
The short message point-to-point services comprise two basic services:
SM MT (Short Message Mobile Terminated Point-to-Point),
SM MO (Short Message Mobile Originated Point-to-Point).
Page 14
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
SM MT denotes the capability of the GSM system to transfer a short message submitted from the SC to
one MS, and to provide information about the delivery of the short message either by a delivery report or a
failure report with a specific mechanism for later delivery; see Figure 03.40/1.
SM MO denotes the capability of the GSM system to transfer a short message submitted by the MS to
one SME via an SC, and to provide information about the delivery of the short message either by a delivery
report or a failure report. The message must include the address of that SME to which the SC shall
eventually attempt to relay the short message; see Figure 03.40/2.
The text messages to be transferred by means of the SM MT or SM MO contain up to 140 octets.
Short message delivery
�˜˜˜˜¿ �˜˜˜˜¿
‡ ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜>˜˜˜˜˜˜˜˜˜˜˜˜˜˜ ‡ ‡
‡ SC ‡ ‡ MS ‡
‡ ‡ ˜˜˜˜˜˜˜˜<˜˜˜˜˜˜˜˜ ‡ ‡
�˜˜˜˜� �˜˜˜˜�
Report
Figure 03.40/1 The Short Message Service mobile terminated, point-to-point.
Short message submission
�˜˜˜˜¿ �˜˜˜˜¿
‡ ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜<˜˜˜˜˜˜˜˜˜˜˜˜˜˜ ‡ ‡
‡ SC ‡ ‡ MS ‡
‡ ‡ ˜˜˜˜˜˜˜˜>˜˜˜˜˜˜˜˜ ‡ ‡
�˜˜˜˜� �˜˜˜˜�
Report
Figure 03.40/2 The Short Message Service mobile originated, point-to-point.
An active MS shall be able to receive a short message TPDU (SMS-DELIVER) at any time, independently
of whether or not there is a speech or data call in progress. A report will always be returned to the SC;
either confirming that the MS has received the short message, or informing the SC that it was impossible
to deliver the short message TPDU to the MS, including the reason why.
Page 15
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
An active MS shall be able to submit a short message TPDU (SMS-SUBMIT) at any time, independently of
whether or not there is a speech or data call in progress. A report will always be returned to the MS;
either confirming that the SC has received the short message TPDU, or informing the MS that it was
impossible to deliver the short message TPDU to the SC, including the reason why.
Note: When the transmission or reception of a short message coincide with a change of state
in the MS, i.e. from busy to idle or from idle to busy, or during a handover, the short
message transfer might be aborted.
It is also possible for two short messages to be received in sequence having the same
originating address and identification, i.e. message reference number (MO) or SC
Timestamp (MT). Such a situation may be due to errors at the RP or CP layers (e.g.
during inter MSC handover) where it may be a duplicated message or otherwise it may
be a valid new message.
The receiving entity should therefore make provision to check other parameters
contained in the short message to decide whether the second short message is to be
discarded.
3.2 Short Message Service elements
The SMS comprises 7 elements particular to the submission and reception of messages:
Validity-Period
Service-Centre-Time-Stamp
Protocol-Identifier
More-Messages-to-Send
Priority
Messages-Waiting
Alert-SC
3.2.1 Validity-Period
The Validity-Period is the information element which gives an MS submitting an SMS-SUBMIT to the SC
the possibility to include a specific time period value in the short message (TP-Validity-Period field, see
section 9). The TP-Validity-Period parameter value indicates the time period for which the short message
is valid, i.e. for how long the SC shall guarantee its existence in the SC memory before delivery to the
recipient has been carried out.
3.2.2 Service-Centre-Time-Stamp
The Service-Centre-Time-Stamp is the information element by which the SC informs the recipient MS
about the time of arrival of the short message at the SM-TL entity of the SC. The time value is included in
every SMS-DELIVER (TP-Service-Centre-Time-Stamp field, see section 9) being delivered to the MS.
3.2.3 Protocol-Identifier
The Protocol-Identifier is the information element by which the SM-TL either refers to the higher layer
protocol being used, or indicates interworking with a certain type of telematic device.
The Protocol-Identifier information element makes use of a particular field in the message types SMS-
SUBMIT, SMS-DELIVER and SMS-COMMAND TP-Protocol-Identifier (TP-PID).
3.2.4 More-Messages-to-Send
The More-Messages-to-Send is the information element by which the SC informs the MS that there is one
or more messages waiting in that SC to be delivered to the MS. The More-Messages-to-Send information
element makes use of a boolean parameter in the message SMS-DELIVER, TP-More-Messages-to-Send
(TP-MMS).
Page 16
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
3.2.5 Delivery of Priority and non-Priority Messages
Priority is the information element provided by an SC or SME to indicate to the PLMN whether or not a
message is a priority message.
Delivery of a non-priority message will not be attempted if the MS has been identified as temporarily
absent (see section 3.2.6).
Delivery of a non-priority message will be attempted if the MS has not been identified as temporarily
absent irrespective of whether the MS has been identified as having no free memory capacity (see section
3.2.6).
Delivery of a priority message will be attempted irrespective of whether or not the MS has been identified
as temporarily absent, or having no free memory capacity.
3.2.6 Messages-Waiting
The Messages-Waiting is the service element that enables the PLMN to provide the HLR and VLR with
which the recipient MS is associated with the information that there is a message in the originating SC
waiting to be delivered to the MS. The service element is only used in case of previous unsuccessful
delivery attempt(s) due to temporarily absent mobile or MS memory capacity exceeded. This information,
denoted the Messages-Waiting-Indication (MWI), consists of Messages-Waiting-Data (MWD), the Mobile-
Station-Not-Reachable-Flag (MNRF) and the Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF)
located in the HLR, and the Mobile-Station-Not-Reachable-Flag (MNRF) located in the VLR. Figure 03.40/3
shows an example.
HLR;
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ MWD: ‡
‡ �˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜´.´˜˜˜˜˜˜˜˜˜˜˜˜˜¿ ‡
‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡
‡ ‡ MSIsdn-Alert ‡ SC address ‡ SC address ‡ ‡ SC address ‡ ‡
1 2 n
‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡
‡ �˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜`.`˜˜˜˜˜˜˜˜˜˜˜˜˜� ‡
‡ �˜˜˜˜˜˜˜˜˜˜¿ �˜˜˜˜˜˜˜˜˜˜˜¿ ‡
‡ ‡ ‡ ‡ ‡ ‡
‡ ‡ MNRF ‡ ‡ MCEF ‡ ‡
‡ �˜˜˜˜˜˜˜˜˜˜� �˜˜˜˜˜˜˜˜˜˜˜� ‡
‡ ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
VLR;
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ ‡
‡ �˜˜˜˜˜˜˜˜˜¿ ‡
‡ ‡ ‡ ‡
‡ ‡ MNRF ‡ ‡
‡ �˜˜˜˜˜˜˜˜˜� ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
Figure 03.40/3: Example of how information on one MS can be put in relation to SC(s) in order
to fulfil the requirement of Alert-SC mechanism.
Page 17
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
The MWD shall contain a list of addresses (SC-Addr) of SCs which have made previous unsuccessful
delivery attempts of a message (see section 5). In order to be able to send alert messages to every SC
which has made unsuccessful delivery attempts to an MS, the HLR shall store the MSIsdn-Alert (see
section 3.2.7) together with references to the SC addresses. The requirements placed upon the HLR are
specified in GSM 03.08. The description of how the HLR is provided with SC and MS address information
is given in GSM 09.02.
The Mobile-Station-Memory-Capacity-Exceeded-Flag (MCEF) within the HLR is a boolean parameter with
the value TRUE when the list MWD contains one or more list elements because an attempt to deliver a
short message to an MS has failed with a cause of MS Memory Capacity Exceeded, and with the value
FALSE otherwise.
The Mobile-Station-Not-Reachable-Flag (MNRF) within the HLR and the VLR is a boolean parameter with
the value TRUE when the list MWD contains one or more list elements because an attempt to deliver a
short message to an MS has failed with a cause of Absent Subscriber, and with the value FALSE
otherwise.
The MWD, MCEF and MNRF are updated in the following way:
1a. When a mobile terminated short message delivery fails due to the MS being temporarily
absent (i.e. either IMSI DETACH flag is set or there is no response from the MS to a paging
request), the SC address is inserted into the MWD list (if it is not already present) and the
MNRF is set (if it is not already set), as described in section 10.
1b. When a mobile terminated short message delivery fails due to the MS memory capacity being
exceeded, the SC address is inserted into the MWD list (if it is not already present) and the
MCEF is set (if it is not already set), as described in section 10.
1c. If the MSIsdn used by the SC to address the recipient MS for alerting purposes is different
from the MSIsdn-Alert of the MS (see section 3.2.7), the HLR returns the MSIsdn-Alert to the
SC within the failure report, see "1c Failure report" in figures 03.40/15 and /16.
2a. When either the HLR or VLR detects that the MS (with a non-empty MWD and the MCEF
clear in the HLR and the MNRF set in the VLR) has recovered operation (e.g. has responded
to a paging request), the HLR directly or on request of the VLR will invoke operations to alert
the SCs within the MWD (see section 3.2.7 and section 10). Once the Alert SC operations
have been invoked, the MNRF is cleared. After each SC is alerted by the HLR, the address
for that SC is deleted from the MWD. If the MCEF is set in the HLR, the HLR clears the
MNRF, but does not invoke operations to alert the SCs within the MWD and data are not
cleared from the MWD.
2b. When the HLR receives (via the MSC and the VLR) a notification that the MS (with a non-
empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or
more short messages, the HLR will invoke operations to alert the SCs within the MWD (see
section 3.2.7 and section 10). Once the Alert SC operations have been invoked, the MNRF is
cleared in the VLR and the MCEF and MNRF are cleared in the HLR. After each SC is alerted
by the HLR, the address for that SC is deleted from the MWD.
2c. When the HLR receives from the SMS-GMSC a notification that a short message has been
successfully delivered from an SC to an MS for which the MCEF is set and the MWD are not
empty, the HLR will invoke operations to alert other SCs within the MWD (see section 3.2.7
and section 10). Once the Alert SC operations have been invoked, the MCEF and MNRF are
cleared in the HLR. After each SC is alerted by the HLR, the address for that SC is deleted
from the MWD. The SC which successfully delivered the message is also deleted from the
MWD, if present.
2d. When the HLR receives (via the MSC and the VLR) a notification that the MS has memory
capacity available to receive one or more short messages but the MCEF is not set and the
MWD are empty, the HLR acknowledges the notification but does not alert any service
centre.
Page 18
ETS 300 536: October 1994 (GSM 03.40 version 4.9.1)
3.2.7 Alert-SC
The Alert-SC is the service element, which may be provided by some GSM PLMNs, to inform the SC that
an MS
1) to which a delivery attempt has failed because the MS is not reachable or because the MS memory
capacity was exceeded
and
2) which is now recognized by the PLMN:
a) to have resumed operation (e.g. to have responded to a paging request) or
b) to have memory newly available (which implies that the mobile is reachable)
is again ready to receive one or more short messages. The SC may - on reception of an Alert-SC - initiate
the delivery attempt procedure for the queued messages destined for this MS.
To each MS there may be allocated several MSIsdns. When the HLR is to alert an SC that an MS is again
attainable it will use a specific MSIsdn value for this purpose; in this specification called MSIsdn-Alert.
Note: Repeated delivery attempts from the SC may be of two types:
i) A repeated delivery attempt because the SC has been informed that the MS is
active and available to receive short messages.
ii) An autonomous repeated delivery attempt by the SC.
The application of these two options is defined by the providers of the SC and the
network.
3.2.8 Options concerning MNRF, MCEF and MWD
Setting the Mobile-Station-Not-Reachable-Flag (MNRF) in the VLR is mandatory. It is also mandatory for
the VLR to send the 'MS Present' message (see section 10) to the HLR when the MS has been detected
as becoming active and then to clear MW
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...