ETSI ETS 300 559 ed.4 (1996-09)

Digital cellular telecommunications system (Phase 2) (GSM); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface (GSM 04.11)

RE/SMG-030411PR3

Digitalni celični telekomunikacijski sistem (faza 2) – Storitev kratkih sporočil (SMS) točka-točka (PP) kot podpora vmesniku mobilnega radia (GSM 04.11)

General Information

• Status: Published
• Publication Date: 17-Sep-1996
• Technical Committee: SMG 3 - Network Aspects
• Current Stage: 12 - Completion
• Due Date: 13-Sep-1996
• Completion Date: 18-Sep-1996
• Ref Project: SIST ETS 300 559 E4:2003 - Digital cellular telecommunications system (Phase 2) (GSM); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface (GSM 04.11)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 559 E4:2003
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHPID]D±6WRULWHYNUDWNLKVSRURþLO606
WRþNDWRþND33NRWSRGSRUDYPHVQLNXPRELOQHJDUDGLD*60
Digital cellular telecommunications system (Phase 2) (GSM); Point-to-Point (PP) Short
Message Service (SMS) support on mobile radio interface (GSM 04.11)
Ta slovenski standard je istoveten z: ETS 300 559 Edition 4
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
SIST ETS 300 559 E4:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 559 E4:2003

---------------------- Page: 2 ----------------------

SIST ETS 300 559 E4:2003
EUROPEAN ETS 300 559
TELECOMMUNICATION September 1996
STANDARD Fourth Edition
Source: ETSI TC-SMG Reference: RE/SMG-030411PR3
ICS: 33.060.50
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2);
Point-to-Point (PP) Short Message Service (SMS)
support on mobile radio interface
(GSM 04.11)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
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 1996. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 559 E4:2003
Page 2
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
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: 4 ----------------------

SIST ETS 300 559 E4:2003
Page 3
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
Contents
Foreword .7
1 Scope .9
1.1 Normative references .9
1.2 Abbreviations .9
2 Overview of Short Message Service (SMS) support.10
2.1 Protocols and protocol architecture .10
2.2 Use of channels .11
2.3 Layer 2 SAPI 3 handling .11
3 Service definition .12
3.1 General .12
3.2 Service provided by the CM-sublayer .12
3.2.1 Definition of primitives on the MS side .13
3.2.1.1 MNSMS-ABORT-REQuest.13
3.2.1.2 MNSMS-DATA-REQuest.13
3.2.1.3 MNSMS-DATA-INDication.13
3.2.1.4 MNSMS-ESTablish-REQuest.13
3.2.1.5 MNSMS-ESTablish-INDication.14
3.2.1.6 MNSMS-ERROR-INDication .14
3.2.1.7 MNSMS-RELease-REQuest .14
3.2.2 Definition of primitives on the network side.14
3.2.2.1 MNSMS-ABORT-REQuest.14
3.2.2.2 MNSMS-DATA-REQuest.14
3.2.2.3 MNSMS-DATA-INDication.15
3.2.2.4 MNSMS-ESTablish-REQuest.15
3.2.2.5 MNSMS-ESTablish-INDication.15
3.2.2.6 MNSMS-ERROR-INDication .15
3.2.2.7 MNSMS-RELease-REQuest .15
3.3 Service provided by SM-RL .15
3.3.1 Definition of primitives on the MS side .15
3.3.1.1 SM-RL-DATA-REQuest.16
3.3.1.2 SM-RL-DATA-INDication.16
3.3.1.3 SM-RL-MEMORY-AVAILABLE-REQuest.16
3.3.1.4 SM-RL-REPORT-REQuest .16
3.3.1.5 SM-RL-REPORT-INDication .17
3.3.2 Definition of primitives on the network side.17
3.3.2.1 SM-RL-DATA-REQuest.17
3.3.2.2 SM-RL-DATA-INDication.17
3.3.2.3 SM-RL-MEMORY-AVAILABLE-INDication.17
3.3.2.4 SM-RL-REPORT-REQuest .17
3.3.2.5 SM-RL-REPORT-INDication .17
4 [Spare].17
5 CM-procedures.18
5.1 General .18
5.2 Short Message Control states .18
5.2.1 SMC states at the MS side of the radio interface.18
5.2.1.1 Mobile Originating Case .18
5.2.1.1.1 MO-Idle (State 0) .18
5.2.1.1.2 MO-MM-connection pending (State 1).18
5.2.1.1.3 MO-Wait for CP-ACK (State 2).18
5.2.1.1.4 MO-MM-connection established
(State 3) .18
5.2.1.2 Mobile Terminating case .18

---------------------- Page: 5 ----------------------

SIST ETS 300 559 E4:2003
Page 4
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
5.2.1.2.1 MT-Idle (State 0) . 18
5.2.1.2.2 MT-Wait for CP-ACK (State 2). 18
5.2.1.2.3 MT-MM-connection established
(State 3). 19
5.2.2 SMC states at the network side of the radio interface . 19
5.2.2.1 Mobile Originating Case. 19
5.2.2.1.1 MO-Idle (State 0). 19
5.2.2.1.2 MO-Wait for CP-ACK (State 2) . 19
5.2.2.1.3 MO-MM-connection established
(State 3). 19
5.2.2.2 Mobile Terminating Case . 19
5.2.2.2.1 MT-Idle (State 0) . 19
5.2.2.2.2 MT-MM-connection pending (State 1). 19
5.2.2.2.3 MT-Wait for CP-ACK (State 2). 19
5.2.2.2.4 MT-MM-connection established
(State 3). 19
5.3 Short message control procedures . 20
5.3.1 MM-connection establishment. 20
5.3.2 RPDU transfer . 20
5.3.3 Release of MM and CM connections. 21
5.3.4 Abnormal cases. 21
5.4 Concatenating short message or notification transfers. 22
6 SM-RL-procedures . 23
6.1 General. 23
6.2 Transition states of SMR entity . 23
6.2.1 SMR-states at the MS-side of the radio interface. 23
6.2.1.1 Idle (State 0). 23
6.2.1.2 Wait for RP-ACK (State 1) . 23
6.2.1.3 Wait for RETRANS TIMER (State 4) . 23
6.2.2 SMR-states at the network side of the radio interface. 23
6.2.2.1 Idle (State 0). 23
6.2.2.2 Wait for RP-ACK (State 1) . 23
6.2.2.3 Wait to send RP-ACK (State 3). 23
6.3 Short Message Relay procedures. 24
6.3.1 TPDU relaying. 24
6.3.2 [spare]. 24
6.3.3 Notification relaying. 24
6.3.3.1 MS side . 24
6.3.3.1.1 Idle state. 24
6.3.3.1.2 Wait for RP-ACK state . 25
6.3.3.1.3 Wait for RETRANS Timer state . 25
6.3.3.2 Network side . 25
6.3.3.2.1 Idle state. 25
6.3.3.2.2 Wait to Send RP-ACK state . 25
6.3.4 Abnormal cases. 26
7 Message functional definitions and content. 26
7.1 General. 26
7.2 Messages for short message or notification transfer on CM. 26
7.2.1 CP-DATA. 26
7.2.2 CP-ACK . 27
7.2.3 CP-ERROR. 27
7.3 Messages for short message and notification transfer on SM-RL . 27
7.3.1 RP-DATA. 27
7.3.1.1 RP-DATA (Network to Mobile Station). 27
7.3.1.2 RP-DATA (Mobile Station to Network). 28
7.3.2 RP-SMMA. 28
7.3.3 RP-ACK . 28
7.3.4 RP-ERROR. 28
8 Message format and information elements coding. 29
8.1 CP-messages. 29

---------------------- Page: 6 ----------------------

SIST ETS 300 559 E4:2003
Page 5
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
8.1.1 General.29
8.1.2 Protocol Discriminator and Transaction Identifier .29
8.1.3 Message type .29
8.1.4 Other required information elements.30
8.1.4.1 CP-User data element .30
8.1.4.2 CP-Cause element .30
8.2 RP-messages .31
8.2.1 General.31
8.2.2 Message type indicator (MTI).31
8.2.3 Message reference.31
8.2.4 [Spare].32
8.2.5 Other required information elements.32
8.2.5.1 Originator address element .32
8.2.5.2 Destination address element .32
8.2.5.3 RP-User data element .33
8.2.5.4 RP-Cause element .33
9 Handling of unknown, unforeseen, and erroneous protocol data.36
9.1 General .36
9.2 CP Error Handling.36
9.2.1 Message too short.36
9.2.2 Unknown or unforeseen transaction identifier.36
9.2.3 Unknown or unforeseen message type.36
9.2.4 Non-semantical mandatory information element errors .37
9.2.5 Messages with semantically incorrect contents .37
9.3 RP Error Handling.37
9.3.1 Message too short.37
9.3.2 Unknown or unforeseen Message Reference.38
9.3.3 Unknown or unforeseen message type.38
9.3.4 Non-semantical mandatory information element errors .38
9.3.5 Messages with semantically incorrect contents .39
10 Timers .39
Annex A (informative): Arrow diagrams .40
Annex B (normative): SDL-description of the CM-layer .45
Annex C (informative): Arrow diagrams .62
Annex D (normative): SDL-description of the short message relay layer.68
Annex E (informative): Cause definition.76
Annex F (informative): LAPDm SAPI 3 handling for short message service.82
History.89

---------------------- Page: 7 ----------------------

SIST ETS 300 559 E4:2003
Page 6
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 559 E4:2003
Page 7
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
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 Short Message Service (SMS) support on mobile radio interface within the digital
cellular telecommunications system (Phase 2).
This ETS has been produced as a result of further work carried out by TC-SMG and correspond to GSM
technical specification, GSM 04.11 version 4.10.0.
The specification from which this ETS has been derived was originally based on CEPT documentation,
hence the presentation of this ETS is not in accordance with the ETSI/PNE rules.
Reference is made within this ETS to GSM Technical Specifications (GSM-TS) (note).
NOTE: TC-SMG has produced documents which give the technical specifications for the
implementation of the digital cellular telecommunications system. Historically, these
documents have been identified as GSM Technical Specifications (GSM-TS). 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.
Transposition dates
Date of adoption of this ETS: 30 September 1996
Date of latest announcement of this ETS (doa): 31 December 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 June 1997
Date of withdrawal of any conflicting National Standard (dow): 30 June 1997

---------------------- Page: 9 ----------------------

SIST ETS 300 559 E4:2003
Page 8
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
Blank page

---------------------- Page: 10 ----------------------

SIST ETS 300 559 E4:2003
Page 9
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
1 Scope
This European Telecommunications Standard (ETS) specifies the procedures used across the mobile
radio interface by the signalling layer 3 function Short Message Control (SMC) and Short Message Relay
function (SM-RL).
1.1 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): "Digital cellular telecommunication system (Phase 2);
Abbreviations and acronyms".
[2] GSM 03.40 (ETS 300 536): "Digital cellular telecommunication system
(Phase 2); Technical realization of the Short Message Service (SMS) Point to
Point (PP)".
[3] GSM 04.06 (ETS 300 555): "Digital cellular telecommunication system
(Phase 2); Mobile Station - Base Station System (MS - BSS) interface Data Link
(DL) layer specification".
[4] GSM 04.07 (ETS 300 556): "Digital cellular telecommunication system
(Phase 2); Mobile radio interface signalling layer 3 General aspects".
[5] GSM 04.08 (ETS 300 557): "Digital cellular telecommunication system
(Phase 2); Mobile radio interface layer 3 specification".
[6] ISO 7498: "Information processing systems - Open Systems Interconnection -
Basic Reference Model".
1.2 Abbreviations
Abbreviations used in this specification are listed in GSM 01.04 [1].

---------------------- Page: 11 ----------------------

SIST ETS 300 559 E4:2003
Page 10
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
2 Overview of Short Message Service (SMS) support
The purpose of the Short Message Service is to provide the means to transfer messages between a GSM
PLMN Mobile Station and a Short Message Entity via a Service Centre, as described in TS GSM 03.40.
The terms "MO" - Mobile Originating - and "MT" - Mobile Terminating - are used to indicate the direction in
which the short message is sent.
This Technical Specification describes the procedures necessary to support the Short Message Service
between the MS and the MSC and vice versa, as described in TS GSM 03.40.
The procedures are based on services provided by the Mobility Management sublayer as described in
TS GSM 04.07/04.08.
2.1 Protocols and protocol architecture
The hierarchical model shows the layer structure of the MSC and the MS.
MSC MS
SM-AL
SM-TL
SM-RL SMR < SM-RP protocol > SMR
CM-sublayer SMC SMC
< SM-CP protocol >
MM-sublayer
RR-sublayer
Figure 2.1/GSM 04.11: Protocol hierarchy
The CM-sublayer, in terms of the Short Message Service Support, provides services to the Short
Message Relay Layer.
On the MS-side the Short Message Relay Layer provides services to the Short Message Transfer Layer.
The Short Message Relay Layer is the upper layer on the network side (MSC), and the SM-user
information elements are mapped to TCAP/MAP.
The peer protocol between two SMC entities is denoted SM-CP, and between two SMR entities, SM-RP.
Abbreviations:
SM-AL Short Message Application Layer
SM-TL Short Message Transfer Layer
SM-RL Short Message Relay Layer
SM-RP Short Message Relay Protocol
SMR Short Message Relay (entity)
CM-sub Connection Management sublayer
SM-CP Short Message Control Protocol
SMC Short Message Control (entity)
MM-sub Mobility Management sublayer
RR-sub Radio Resource Management sublayer

---------------------- Page: 12 ----------------------

SIST ETS 300 559 E4:2003
Page 11
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
2.2 Use of channels
The short message service will be supported by an SDCCH or SACCH, depending on the use of a TCH;
- When a TCH is not allocated, the short message service will use an SDCCH;
- If a TCH is allocated during a short message transaction on an SDCCH, the short message
transaction will stop and continue on the SACCH associated with the TCH;
- If a TCH is allocated for the short message service, the short message service will use the
associated SACCH;
- When an entity using a TCH finishes its transaction, the RR-sublayer may choose to continue an
ongoing short message transfer on the SACCH, or optionally transfer it to an SDCCH.
Table 2.1/GSM 04.11 summarizes the use of channels for the short message service. Arrows indicate
changes of channel.
Table 2.1/GSM 04.11: Channels used for short message transfer
Channel dependency Channel used
TCH not allocated SDCCH
TCH not allocated -> TCH allocated SDCCH -> SACCH
TCH allocated SACCH
TCH allocated -> TCH not allocated SACCH -> SACCH opt. SDCCH
2.3 Layer 2 SAPI 3 handling
General rule:
The Radio Resource Management (RR ref. TS. GSM 04.08) in the Mobile Station and on the network side
(i.e. in the BSC) shall establish the acknowledged mode of operation on SAPI 3 whenever needed, i.e.
when a message requiring SAPI 3 transfer shall be transmitted.
RR shall control the layer 2 also for SAPI 3, and keep knowledge of the mode.
The network side may initiate release of the acknowledged mode for SAPI 3 either explicitly (by the use of
DISC- and UA-frames, ref., TS GSM 04.06) or indirectly by channel release (ref. TS GSM 04.08).
This means:
- the Mobile Station side will initiate establishment of SAPI 3 acknowledged mode in the case of
mobile originating short message transfer;
- the network side will initiate establishment of SAPI 3 acknowledged mode in the case of mobile
terminating short message transfer;
- the network side may choose to keep the channel and the acknowledged mode of operation to
facilitate transfer of several short messages for or from the same Mobile Station. The queuing and
scheduling function for this should reside in the MSC.

---------------------- Page: 13 ----------------------

SIST ETS 300 559 E4:2003
Page 12
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
3 Service definition
3.1 General
The layer service is described as a set of service primitives. These service primitives are abstractions and
attempt to capture only those details of the interaction between the entities that are aspects of the layer
service itself. A service primitive neither specifies nor constrains the implementation of entities or the
interface between them.
The general syntax of a primitive and the initials of them are in line with the 04-series of GSM Technical
Specifications.
NOTE: In order to limit the number of primitives and state definitions to a reasonable amount,
a description method has been chosen which does not claim to be totally in line with
the formal description method of the layered ISO reference model (ISO 7498) for Open
Systems Interconnection.
3.2 Service provided by the CM-sublayer
In order to support the Short Message Service, the CM-sublayer provides services to the Short Message
Relay Layer.
The CM-sublayer services are provided using layer specific functions and lower layer services offered to
the CM-sublayer, controlled by short message service control entities called SMCs.
An SMC entity in the MS communicates with an SMC entity in the MSC by means of a peer protocol,
SM-CP (Short Message Service Control Protocol). The arrow diagrams in annex A give an overview of the
messaging on the CM-sublayer during a short message transfer.
A mobile station supporting the short message service shall have a minimum of two SMC entities. This
enables the MS to receive MT messages during an MO message transfer.
To ensure that an MS having the minimum of two SMC entities is able to receive MT messages during an
MO message transfer, and to send MO messages during MT message transfer, parallel message transfer
in the same direction is prohibited. This means that the SMC entities shall not simultaneously perform
messaging in the same direction. The rules for concatenation of message transfers are described in
section 5.4.
The MSC shall have a minimum of two SMC entities available during an MT message transfer to a mobile
station, one being reserved for MO message transfer. In an MO message transfer, the MSC shall have
one SMC entity reserved for handling of an MT message.

---------------------- Page: 14 ----------------------

SIST ETS 300 559 E4:2003
Page 13
ETS 300 559 (GSM 04.11 version 4.10.0): September 1996
3.2.1 Definition of primitives on the MS side
This section defines the service primitives used on the MS side. Table 3.1/GSM 04.11 gives an overview
of the service primitives and main parameter linked to the primitives. All necessary control parameters to
be used in the short message service are defined in section 7. All MNSMS service primitives defined in
this section are passed to an SMC-entity.
Table 3.1/GSM 04.11: MNSMS service primitives on the MS-side
SERVICE PRIMITIVES
PARAMETER
NAME TYPE
  MNSMS-ABORT- Req  Cause
  MNSMS-DATA- Req  MT RPDU
Ind  MO RPDU
  MNSMS-EST- Req  MO RPDU
Ind  MT RPDU
  MNSMS-ERROR- Ind  Cause
  MNSMS-REL- Req  Cause
3.2.1.1 MNSMS-ABORT-REQuest
A request from an SMR entity to release a CM-connection in abnormal cases.
When the CM-sublayer receives this request, and if the MM connection exists, it shall form and send the
CP-ERROR message. Irrespective of whether or not the CP-ERROR message was sent, the CM-sublayer
shall then release the lower layer services.
3.2.1.2 MNSMS-DATA-REQuest
A request from an SMR entity to send a RPDU on the established CM-connection.
The SMC entity forms the CP-DATA message, the user information element being the RPDU, and
transfers the message by means of the lower layer services.
NOTE: After reception of an incoming RP-DATA, the SMR entity typically returns the
acknowledgement RP-ACK, or an error indication, RP-ERROR, to the Service Centre.
3.2.1.3 MNSMS-DATA-INDication
An indication used by the SMC entity to pass the user information element (RPDU) of a received
CP-DATA message to SM-RL.
NOTE: The RPDU is typically an RP-ACK or
...