ETSI TS 100 942 v7.o.o (1999-08)
`
`Technical Specification
`
`Digital cellular telecommunications system (Phase 2+);
`Point-to-Point (PP) Short Message Service (SMS)
`support on mobile radio interface
`(GSM 04.11 version 7.0.0 Release 1998)
`
`
`
`GSI':'El;
`
`GLOBAL SYSTEM FOR
`MOBILE COMMUNICATIONS
`
`€s@
`
`
`
`1
`
`M2M
`
`Ex. 2006
`
` 1
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`2
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`Reference
`
`RTS/SMG-030411Q7 (8q003i03.PDF)
`
`
`Keywords
`Digital cellular telecommunications system,
`Global System for Mobile communications (GSM)
`
`ETSI
`
`
`Postal address
`
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`
`Office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 4716
`Siret N“ 348 623 562 00017 — NAF 742 0
`Association a but non lucratif enregistrée a la
`Sous—Préfecture de Grasse (06) N“ 7803/88
`
`Internet
`
`
`secretariat@etsi.fr
`Individual copies ofthis ETSI deliverable
`can be downloaded from
`http://www.etsi.org
`If you find errors in the present document, send your
`comment to: editor@etsi.fr
`
`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 1999.
`All rights reserved.
`
`ETSI
`
`2
`
`M2M
`
`EX. 2006
`
` 2
`
`M2M
`Ex. 2006
`
`

`
`ETSI TS 100 942 V7.0.0 (1999-08)
`3
`(GSM 04.11 version 7.0.0 Release 1998)
`
`
`Contents
`
`Intellectual Property Rights .............................................................................................................................. ..7
`
`Foreword .......................................................................................................................................................... ..7
`
`Scope ...................................................................................................................................................... ..8
`References ...................................................................................................................... .. 8
`Abbreviations ................................................................................................................................................... .. 8
`
`Overview of Short Message Service (SMS) support ............................................................................. ..8
`Protocols and protocol architecture ....................................................................................................... .. 9
`Use of channels ................................................................................................................... .. 10
`Layer 2 SAPI 3 handling for circuit switched GSM ..... ..
`........ .. 10
`Layer 2 (LLC) GPRS support ........................................................................................................................ .. 10
`
`
`
`Service definition .......................................................................................................................... ..1 1
`
`General .................................................. ..
`Service provided by the CM-sublayer .................................................................. ..
`. . . . . . . . . . . . . . . .. 12
`Definition of primitives on the MS side . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . .
`. . . . . . . . . . . . . . . .. 12
`. . . . . . . . . . .
`MNSMS-ABORT-REQuest . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . .
`............... .. 12
`MNSMS—DATA-REQuest .......................................................................... ..
`MNSMS-DATA-lNDication ................................................................................................. .. 12
`MNSMS—ESTab1ish-REQuest ............. ..
`
`1
`1 .1
`
`2
`2.1
`2.2
`2.3
`2.4
`
`3
`3.1
`
`3.2
`3.2.1
`3.2.1.1
`3.2.1.2
`3.2.1.3
`3.2.1.4
`3.2.1.5
`
`
`
`
`
`
`MNSMS-ERROR-INDication .................................................................................................. .. 13
`MNSMS—RELease-REQuest....................... ..
`..... .. 13
`Definition of primitives on the network side ............................................................................................ .. 13
`MNSMS-ABORT-REQuest ............................................................................................................... .. 13
`MNSMS-DATA-REQuest ............ ..
`MNSMS—DATA-INDication .... ..
`MNSMS-ESTablish-REQuest ................. ..
`MNSMS—ESTablish-INDication . . . . .
`. . . . . . . . . ..
`MNSMS-ERROR-INDication
`......... ..
`MNSMS-RELease-REQuest. . . . . . .
`. . . . . . . . . ..
`Service provided by SM-RL ............................................ ..
`Definition of primitives on the MS side .......................................... ..
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 15
`SM-RL-DATA-REQuest . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . .
`SM-RL—DATA-INDication................................................................................ ..
`15
`SM-RL—MEMORY—AVAILABLE-REQuest............................................................ ..
`15
`SM-RL—REPORT-REQest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . .
`. . . . . . . . . ..
`16
`SM-RL-REPORT-INDication ............................................................................................ ..
`16
`Definition of primitives on the network side ............................................................................ ..
`16
`SM-RL-DATA-REQuest . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . ..
`16
`SM-RL—DATA—INDication................................................................................................................. .. 16
`SM-RL-MEMORY-AVAILABLE-1NDication .................................................................................. .. 16
`SM-RL-REPORT—REQuest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . .. 17
`SM-RL-REPORT—INDicati0n ............................................................................................................ .. 17
`
`
`
`
`3.2.1.6
`3.2.1.7
`3.2.2
`3.2.2.1
`3.2.2.2
`3.2.2.3
`3.2.2.4
`3.2.2.5
`3.2.2.6
`3.2.2.7
`3.3
`3.3.1
`3.3.1.1
`3.3.1.2
`3.3.1.3
`3.3.1.4
`3.3.1.5
`3.3.2
`3.3.2.1
`3.3.2.2
`3.3.2.3
`3.3.2.4
`3.3.2.5
`
`4
`
`[Spare] .................................................................................................................................................. .. 17
`
`CM—procedures ..................................................................................................................................... .. 17
`
`................ .. 17
`Short Message Control states ................................................................................................................... .. 17
`SMC-CS states at the MS side of the radio interface ......................................................................... .. 17
`Mobile Originating Case ........................................................ ..
`17
`MO—ldle (State 0) ....................................................................................................... .. 17
`MO-MM-connection pending (State 1) ................................................................... .. 17
`MO-Wait for CP-ACK (State 2) ...................................................... ..
`17
`MO-MM-connection established (State 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . .. 18
`Mobile Terminating case .................................................................................................................... .. 18
`
`
`
`
`
`5
`5.1
`5.2
`5.2.1
`5.2.1.1
`5.2.1.1.1
`52.1.1.2
`5.2.1.13
`5.2.1.1.4
`5.2.1.2
`
`ETSI
`
`3
`
`M2M
`
`EX. 2006
`
` 3
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`4
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`MT-Idle (State 0) .......................................................................................................................... .. 18
`MT-Wait for CP-ACK (State 2) .................................................................................................... .. 18
`MT-MM-connection established (State 3) ................................................................................ .. 18
`
`.... .. 18
`SMC-GP states at the MS side of the radio interface ........ ..
`
`Mobile Originating Case ..................................................................................................................... .. 18
`MO-Idle (State 0) .......................................................................................................................... .. 18
`
`. . . . . .. 18
`MO-Wait for CP-ACK (State 1) . . . . . .
`MO-Wait for CP-Data (State 2) .................................................................................................... .. 18
`Mobile Terminating case .................................................................................................................... .. 18
`MT-Idle (State 0) . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . .. 19
`MT-Wait for RP-ACK (State 1) ............................................................................. .. 19
`MT-Wait for CP-ACK (State 2) .................................................................................................... .. 19
`SMC-CS states at the network side of the radio interface . . . . . . . . . . . . .
`. . . . . . . . . ..
`19
`Mobile Originating Case ........................................................................................ .. 19
`MO-Idle (State 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 19
`MO-Wait for CP-ACK (State 2) .......................................................................... .. 19
`MO-MM-connection established (State 3) . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . .
`. . . . . . . . . . . . .. 19
`Mobile Terminating Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . ..
`............ .. 19
`MT-Idle (State 0) ............................................................................................................. .. 19
`MT-MM-connection pending (State 1) ............................................................................ .. 19
`MT-Wait for CP-ACK (State 2) .................. ..
`MT-MM-connection established (State 3) .................................................................................... .. 20
`SMC-GP states at the network side of the radio interface ........................................................................ .. 20
`Mobile Originating Case ................................................. ..
`MO-Idle (State 0) ....................... ..
`MO-Wait for RP-ACK (State 1) ................................................................................................... .. 20
`MO-Wait for CP—ACK(State 2) .... ..
`Mobile Terminating Case
`MT-Idle (State 0) ....................... ..
`MT-Wait for CP-ACK (State 1) .... ..
`MT-Wait for CP DATA (State 2)
`Short Message Control procedures ...................................................... ..
`MM—connection establishment for circuit switched GSM ....... ..
`RPDU transfer for circuit switched GSM ............... ..
`. . . . . . . . . ..
`RPDU transfer for GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`Release of MM and CM connections ....................................................... ..
`Abnormal cases ........................................................................................ ..
`Concatenating short message or notification transfers ................................................................................... .. 23
`
`
`
`
`
`5.2.1.2.l
`5.2.1.2.2
`5.2.1.2.3
`5.2.2
`5.2.2.1
`5.2.2.1.1
`5.2.2.1.2
`5.2.2.1.3
`5.2.2.2
`5.2.2.2.]
`5.2.2.2.2
`5.2.2.2.3
`5.2.3
`5.2.3.1
`5.2.3.1.1
`5.2.3 . 1 .2
`5.2.3.1.3
`5.2.3.2
`5.2.3.2.1
`5.2.3.2.2
`5.2.3.2.3
`5.2.3.2.4
`5.2.4
`5.2.4.1
`5.2.4.1.1
`5.2.4.1.2
`5.2.4.1.3
`5.2.4.2
`5.2.4.2.1
`5.2.4.2.2
`5.2.4.2.3
`53
`5.3.1
`5.3.2.1
`5.3.2.2
`5.3.3
`5.3.4
`5.4
`
`6
`6.1
`6.2
`6.2.1
`6.2.1.1
`6.2.1.2
`6.2.1.3
`6.2.2
`6.2.2.1
`6.2.2.2
`6.2.2.3
`6.3
`6.3.1
`6.3.2
`6.3.3
`6.3.3.1
`6.3.3.1.1
`6.3.3.1.2
`6.3.3.1.3
`6.3.3.2
`6.3.3.2.l
`6.3.3.2.2
`
`SM—RL—procedures ............................................................................................................................... ..24
`
`................................................................... .. 24
`
`Transition states of SMR entity ......................................................................................................... .. 24
`. . . . . . . . . ..
`SMR-states at the MS-side of the radio interface . . . . . . . .
`Idle (State 0) ................................................................... ..
`Wait for RP-ACK (State 1) . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . ..
`Wait for RETRANS TIMER (State 4) ..................................... ..
`SMR-states at the network side of the radio interface ................... ..
`Idle (State 0) ........................................................... ..
`Wait for RP-ACK (State 1) ............................................................................................ ..
`Wait to send RP-ACK (State 3) ..................................................................................... ..
`
`Short Message Relay procedures ............ ..
`
`TPDU relaying ................................................................................................................. .. 25
`[spare] ................................. ..
`Notification relaying ..... ..
`MS side ................... ..
`Idle state .......................... ..
`Wait for RP-ACK state ................ ..
`Wait for RETRANS Timer state
`Network side ...................................... ..
`Idle state ............................................................................. ..
`Wait to Send RP-ACK state ................................................................ ..
`
`
`
`
`
`ETSI
`
`4
`
`M2M
`
`EX. 2006
`
` 4
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`5
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`6.3.4
`
`Abnormal cases ........................................................................................................................................ .. 27
`
`Message functional definitions and content ......................................................................................... ..27
`General ........................................................................................................................................................... .. 27
`
`Messages for short message or notification transfer on CM
`.... .. 27
`. . . . .. 28
`CP-DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`CP-ACK . . . . . . . . . .
`. . . . .. 28
`CP-ERROR .............................................................................................................................................. .. 28
`Messages for short message and notification transfer on SM-RL .................................................................. .. 28
`RP-DATA .............................................................................. ..
`28
`RP-DATA (Network to Mobile Station) . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 28
`RP-DATA (Mobile Station to Network) . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 29
`RP-SMMA ............................................................................................................................................... .. 29
`RP-ACK ................................................................................................................................................... .. 29
`RP-ERROR .............................................................................................................................................. .. 29
`
`
`
`7
`7.1
`7.2
`7.2.1
`7.2.2
`7.2.3
`7.3
`7.3.1
`7.3.1.1
`7.3.1.2
`7.3.2
`7.3.3
`7.3.4
`
`Message format and information elements coding .............................................................................. ..30
`CP-messages .................................................................................................................................................. .. 30
`General .................................................................. ..
`30
`Protocol Discriminator and Transaction Identifier . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 30
`Message type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 30
`Other required information elements ........................................................................................................ .. 31
`CP-User data element ......................................................................................................................... .. 31
`CP-Cause element .............. ..
`31
`RP-messages ................................. ..
`32
`General .................................... ..
`32
`Message type indicator (MTI) ........................................................................................... ..
`32
`Message reference ............................................................................................................. ..
`32
`[Spare] ............................................... ..
`33
`Other required information elements...
`....................................................................... .. 33
`Originator address element ................................................................................... .. 33
`Destination address element .......................................................................... ..
`33
`RP-User data element .................................................................................... ..
`34
`RP-Cause element ............................................................................................................................... .. 34
`
`
`
`8
`8.1
`8.1.1
`8.1.2
`8.1.3
`8.1.4
`8.1.4.1
`8.1.4.2
`8.2
`8.2.1
`8.2.2
`8.2.3
`8.2.4
`8.2.5
`8.2.5.1
`8.2.5.2
`8.2.5.3
`8.2.5.4
`
`Handling of unknown, unforeseen, and erroneous protocol data ........................................................ ..36
`General ................................................................................................................................ ..
`36
`CP Error Handling ........................ ..
`36
`Message too short ................................................................................................................. .. 37
`Unknown or unforeseen transaction identifier...................................................................... .. 37
`Unknown or unforeseen message type ....................................................................... ..
`37
`Non-semantical mandatory information element errors.............................................. ..
`37
`Messages with semantically incorrect contents ............... ..
`38
`RP Error Handling .............................................................................................................. .. 38
`
`Message too short ........................................................................................................................... .. 38
`
`Unknown or unforeseen Message Reference .................................................... ..
`38
`Unknown or unforeseen message type ............................................................. ..
`38
`
`Non-semantical mandatory information element errors....
`39
`Messages with semantically incorrect contents ........................................................................................ .. 39
`
`
`
`
`
`9
`9.1
`9.2
`9.2.1
`9.2.2
`9.2.3
`9.2.4
`9.2.5
`9.3
`9.3.1
`9.3.2
`9.3.3
`9.3.4
`9.3.5
`
`ETSI
`
`5
`
`M2M
`
`EX. 2006
`
` 5
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`6
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`10
`
`Timers ................... ..
`
`............................................................................................................................. ..39
`
`Annex A (informative):
`
`Arrow diagrams ........................................................................................... ..40
`
`Annex B (normative):
`
`SDL-description of the CM-layer............................................................... ..43
`
`B.1
`
`Introduction ............ ..
`
`............................................................................................................................ ..43
`
`Annex C (informative):
`
`Arrow diagrams ........................................................................................... ..55
`
`Annex D (normative):
`
`SDL-description of the short message relay layer .................................... ..61
`
`D.1
`
`Introduction ........... ..
`
`............................................................................................................................. ..61
`
`Annex E (informative):
`
`Cause definition ........................................................................................... ..69
`
`Annex F (informative):
`
`LAPDm SAPI 3 handling for short message service ................................ ..74
`
`Annex G (informative):
`
`Change history ............................................................................................. ..81
`
`History ............................. ..
`
`............................................................................................................................. ..82
`
`ETSI
`
`6
`
`MZM
`
`EX. 2006
`
` 6
`
`M2M
`Ex. 2006
`
`

`
`ETSI TS 100 942 V7.0.0 (1999-08)
`7
`(GSM 04.11 version 7.0.0 Release 1998)
`
`
`Intellectual Property Rights
`
`IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
`pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
`in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETS] in respect
`ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
`ETSI Web server (http://www.etsi.org/ipr).
`
`Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
`can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
`which are, or may be, or may become, essential to the present document.
`
`
`
`Foreword
`
`This Technical Specification (TS) has been produced by the Special Mobile Group (SMG).
`
`This TS defines the Short Message Service (SMS) support on mobile radio interface within the digital cellular
`telecommunications system (Phase 2+).
`
`The contents of this TS are subject to continuing work within SMG and may change following formal SMG approval.
`Should SMG modify the contents of this TS it will then be republished by ETSI with an identifying change of release
`date and an increase in version number as follows:
`
`Version 7.x.y
`
`where:
`
`7 GSM Phase 2+ Release 1998;
`
`y
`
`x
`
`the third digit is incremented when editorial only changes have been incorporated in the specification;
`
`the second digit is incremented for all other types of changes,
`updates, etc.
`
`i.e.
`
`technical enhancements, corrections,
`
`ETSI
`
`7
`
`M2M
`
`EX. 2006
`
` 7
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`8
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
` 1
`
`Scope
`
`This Technical Specification (TS) 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) for both circuit switched GSM
`and GPRS.
`
`1 .1
`
`References
`
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`
`0 References are either specific (identified by date of publication, edition number, version number, etc.) or
`non-specific.
`
`I For a specific reference, subsequent revisions do not apply.
`
`0 For a non-specific reference, the latest version applies.
`
`0 A non—specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
`number.
`
`0 For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
`
`[1]
`
`[2]
`
`[3a]
`
`[3]
`
`[4]
`
`[5]
`
`[6a]
`
`[6]
`
`GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and
`acronyms".
`
`GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the
`Short Message Service (SMS) Point-to-Point (PP)".
`
`GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio
`Service (GPRS); Service description; Stage 2".
`
`GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station — Base
`Station System (MS - BSS) interface Data Link (DL) layer specification".
`
`GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface
`signalling layer 3; General aspects".
`
`GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer
`3 specification".
`
`GSM 04.64: "Digital cellular telecommunications system (Phase 2+); General Packet Radio
`Service (GPRS); Logical Link Control (LLC)".
`
`ISO 7498: "Information processing systems - Open Systems Interconnection - Basic Reference
`Model".
`
`1.2
`
`Abbreviations
`
`Abbreviations used in this TS are listed in GSM 01.04.
`
` 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 (MS) 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 ETS describes the procedures necessary to support the Short Message Service between the MS and the MSC or
`SGSN and vice versa, as described in GSM 03.40.
`
`ETSI
`
`8
`
`M2M
`
`EX. 2006
`
` 8
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`9
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`The procedures are based on services provided by the Mobility Management sublayer as described in GSM 04.07/04.08
`for GSM services and the Logical Link Control layer described in GSM 04.64 for GPRS services
`
`2.1
`
`Protocols and protocol architecture
`
`The hierarchical model in Figure 2.1a shows the layer structure of the MSC and the MS.
`
`MSC
`
`SM-AL
`
`SM-TL
`
`SM-RL
`CM-sublayer
`MM-sublayer
`
`RR-sublayer
`
`SMR
`SMC
`
`<_.j— SM-RP protocol ———>
`<_j—— SM-CP protocol ——-—>
`
`Figure 2.1aIGSM 04.11: Protocol hierarchy for circuit switched service
`
`The hierarchical model in Figure 2.lb shows the layer structure of the SGSN and the MS.
`
`SM-AL
`
`SM-TL
`
`SM-RL
`
`CM-sublayer
`
`LLC-sublayer
`
`GRR-sublayer
`
`SMR <4 SM-RP protocol >—_>
`
`SMC <:—j SM-CP protocol ————>
`
`SMR
`
`SMC
`
`Figure 2.1b/GSM 04.11: Protocol hierarchy for GPRS
`
`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 or SGSN), 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
`SM-TL
`SM-RL
`SM-RP
`SMR
`CM-sub
`SM-CP
`SMC
`MM-sub:
`RR-sub:
`LLC-sub
`GRR-sub
`
`Short Message Application Layer
`Short Message Transfer Layer
`Short Message Relay Layer
`Short Message Relay Protocol
`Short Message Relay (entity)
`Connection Management sublayer
`Short Message Control Protocol
`Short Message Control (entity)
`Mobility Management sublayer
`Radio Resource Management sublayer
`Logical Link Control sublayer
`GPRS Radio Resource sublayer
`
`ETSI
`
`9
`
`M2M
`
`EX. 2006
`
` 9
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`10
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`2.2
`
`Use of channels
`
`Table 2.1/GSM 04.11 summarizes the use of channels for the short message service for circuit switched GSM. Arrows
`indicate changes of channel.
`
`Table 2.1/GSM 04.11: Channels used for short message transfer over circuit switched GSM
`
`
`
`Channel used
`
`SDCCH
`SDCCH -> SACCH
`SACCH
`SACCH -> SACCH ot. SDCCH“
`
`
`
`
`
`Channel de endenc
`TCH not allocated
`TCH not allocated -> TCH allocated
`TCH allocated
`TCH allocated -> TCH not allocated
`
`
`
`The short message service for GPRS shall be supported by a PDTCH.
`
`2.3
`General rule:
`
`Layer 2 SAPI 3 handling for circuit switched GSM
`
`The Radio Resource Management (RR reference 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, see GSM 04.06) or indirectly by channel release (see 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.
`
`2.4
`
`Layer 2 (LLC) GPRS support
`
`It shall be possible for a GPRS—attached MS of any class (A, B, C) to send and receive short messages over GPRS radio
`channels.
`
`GPRS shall use the unacknowledged mode of LLC frame transfer as described in GSM 04.64, and shall use SAPI 7 to
`identify the SMS Logical Link Entity within the LLC layer.
`
`A description of the different GPRS MS classes can be found in 03.60, and a brief overview is given below:-
`
`- Class A/B MSs may be able to send and receive short messages using either the MM sublayer (using SACCH or
`SDCCH) or the LLC layer (using PDTCH).
`
`- Class C MSs may be able to send and receive short messages using only the LLC layer (using the PDTCH). The
`capability for GPRS—attached class-C MSs to receive and transmit SMS messages is optional.
`
`The GSMS entity for GPRS class A/B MS is shown in Figure 3. The GSMS shall communicate with the MM entity via
`the GMMSMS-SAP for GPRS Class A/B MO SMS, in order to ascertain which transport service to use.
`
`SMS delivery via GPRS is normally a more radio resource efficient method than SMS delivery via CS GSM. The
`delivery path for M0 SMS is selected by the MS.
`
`ETSI
`
`10
`
`M2M
`
`EX. 2006
`
`
`10
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`11
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`MNSMS SAP
`
`
`
`
`
`MMSMS SAP
`
`
`
`GMMSMS-SAP
`
`Figure 3IGSM 04.11: GSMS entity for GPRS Class AIB MS
`
` 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 fimctions 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 or SGSN 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 per service type (i.e.
`two for CS GSM and two for GPRS