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

....

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
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
ETS 300 559 E3:2003
English language
98 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 559 E3:2003
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ±6WRULWHYNUDWNLKVSRURþLO 606
WRþNDWRþND 33 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 3
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
SIST ETS 300 559 E3:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 559 E3:2003

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

SIST ETS 300 559 E3:2003
EUROPEAN ETS 300 559
TELECOMMUNICATION May 1996
STANDARD Third Edition
RE/SMG-030411PR2
Source: ETSI TC-SMG Reference:
ICS: 33.060.50
Digital cellular telecommunications system, Global System for Mobile communications (GSM)
Key words:
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
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 1996. All rights reserved.

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

SIST ETS 300 559 E3:2003
Page 2
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
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 E3:2003
Page 3
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
Contents
Foreword.7
1 General .9
1.1 Scope .9
1.2 Normative references .9
1.3 Definitions and abbreviations.9
2 Overview of Short Message Service (SMS) support.9
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.14
3.2.1.4 MNSMS-ESTablish-REQuest.14
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 .15
3.2.2.1 MNSMS-ABORT-REQuest.15
3.2.2.2 MNSMS-DATA-REQuest.15
3.2.2.3 MNSMS-DATA-INDication.16
3.2.2.4 MNSMS-ESTablish-REQuest.16
3.2.2.5 MNSMS-ESTablish-INDication.16
3.2.2.6 MNSMS-ERROR-INDication.16
3.2.2.7 MNSMS-RELease-REQuest.16
3.3 Service provided by SM-RL .17
3.3.1 Definition of primitives on the MS side.17
3.3.1.1 SM-RL-DATA-REQuest .18
3.3.1.2 SM-RL-DATA-INDication.18
3.3.1.3 SM-RL-MEMORY-AVAILABLE-REQuest.18
3.3.1.4 SM-RL-REPORT-REQest.18
3.3.1.5 SM-RL-REPORT-INDication.18
3.3.2 Definition of primitives on the network side .19
3.3.2.1 SM-RL-DATA-REQuest .19
3.3.2.2 SM-RL-DATA-INDication.19
3.3.2.3 SM-RL-MEMORY-AVAILABLE-INDication.19
3.3.2.4 SM-RL-REPORT-REQuest .20
3.3.2.5 SM-RL-REPORT-INDication.20
4 [Spare].20
5 CM-procedures.21
5.1 General.21
5.2 Short Message Control states.21
5.2.1 SMC states at the MS side of the radio interface.21
5.2.1.1 Mobile Originating Case .21
5.2.1.1.1 MO-Idle (State 0).21
5.2.1.1.2 MO-MM-connection pending (State 1) . 21

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

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

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

SIST ETS 300 559 E3:2003
Page 5
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
7.3.1.2 RP-DATA (Mobile Station to Network).34
7.3.2 RP-SMMA .35
7.3.3 RP-ACK .35
7.3.4 RP-ERROR .35
8 Message format and information elements coding.36
8.1 CP-messages.36
8.1.1 General . 36
8.1.2 Protocol Discriminator and Transaction Identifier.36
8.1.3 Message type. 36
8.1.4 Other required information elements .37
8.1.4.1 CP-User data element.37
8.1.4.2 CP-Cause element.37
8.2 RP-messages.38
8.2.1 General . 38
8.2.2 Message type indicator (MTI) . 38
8.2.3 Message reference . 39
8.2.4 [Spare]. 39
8.2.5 Other required information elements .39
8.2.5.1 Originator address element .39
8.2.5.2 Destination address element.40
8.2.5.3 RP-User data element.41
8.2.5.4 RP-Cause element.41
9 Handling of unknown, unforeseen, and erroneous protocol data .45
9.1 General.45
9.2 CP Error Handling .45
9.2.1 Message too short . 45
9.2.2 Unknown or unforeseen transaction identifier.45
9.2.3 Unknown or unforeseen message type.46
9.2.4 Non-semantical mandatory information element errors.46
9.2.5 Messages with semantically incorrect contents.46
9.3 RP Error Handling .47
9.3.1 Message too short . 47
9.3.2 Unknown or unforeseen Message Reference.47
9.3.3 Unknown or unforeseen message type.48
9.3.4 Non-semantical mandatory information element errors.48
9.3.5 Messages with semantically incorrect contents.48
10 Timers.49
Annex A (informative): Arrow diagrams.50
Annex B (normative): SDL-description of the CM-layer .55
B1. Introduction.55
Annex C (informative): Arrow diagrams.70
Annex D (normative): SDL-description of the short message relay layer.76
D.1 Introduction.76
Annex E (informative): Cause definition .84
Annex F (informative): LAPDm SAPI 3 handling for short message service.91
History.98

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

SIST ETS 300 559 E3:2003
Page 6
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
Blank page

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

SIST ETS 300 559 E3:2003
Page 7
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
Foreword
This third edition European Telecommunication Standard (ETS) was 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 European
digital cellular telecommunications system (Phase 2).
This third edition ETS has been produced as a result of further work carried out by TC-SMG and
correspond to GSM 04.11, version 4.9.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 European 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 April 1996
Date of latest announcement of this ETS (doa): 20 August 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 18 February 1997
Date of withdrawal of any conflicting National Standard (dow): 18 February 1997

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

SIST ETS 300 559 E3:2003
Page 8
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
Blank page

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

SIST ETS 300 559 E3:2003
Page 9
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
1 General
1.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.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); Abbreviations and acronyms".
[2] GSM 03.40 (ETS 300 536): "European 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): "European 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): "European digital cellular telecommunication system
(Phase 2); Mobile radio interface signalling layer 3 General aspects".
[5] GSM 04.08 (ETS 300 557): "European 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.3 Definitions and abbreviations
Abbreviations used in this specification are listed in GSM 01.04 [1].
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
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 GSM 03.40.
The procedures are based on services provided by the Mobility Management sublayer as described in
GSM 04.07/04.08.

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

SIST ETS 300 559 E3:2003
Page 10
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
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 ‡<˜˜˜˜˜ SM-CP protocol˜˜˜˜˜˜>‡ SMC ‡:
˜˜˜˜˜˜˜˜˜˜˜˜˜   :.ˆ˜˜˜˜˜·.ˆ˜˜˜˜˜·:
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 E3:2003
Page 11
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
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. 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., GSM 04.06) or indirectly by channel release (ref. 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 E3:2003
Page 12
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
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 E3:2003
Page 13
ETS 300 559: May 1996 (GSM 04.11 version 4.9.0)
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       ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.