24.011 v3.2.0 (2000-03)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Core Network;
`Point-to-Point (PP) Short Message Service (SMS)
`support on mobile radio interface
`(Release 1999)
`
`
`
`{r
`
`The present document has been developed within the 3”‘ Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
`The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners’ Publications Offices.
`
` 1
`
`M2M
`
`Ex. 2015
`
`1
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`2
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`Keywords
`3GPP, CN, SMS-PP
`
`3GPP
`
`Postal address
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne — FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`
`http://www.3gpp.org
`
`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.
`
`© 2000 3GPP Organizational Partners (ARIB, CWTS, ETSI, Tl, TTA,TTC).
`All rights reserved.
`
`392'”
`
`M2M
`
`Ex. 2015
`
`2
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`3
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`u
`
`Contents
`
`Foreword .......................................................................................................................................................... .. 7
`
`1
`1 .1
`
`2
`2.]
`2.2
`2.3
`2.4
`2.5
`
`Scope ....................................................................................................................................................... 8
`References ....................................................................................................................................................... .. 8
`Abbreviations ................................................................................................................................................... .. 8
`
`Overview of Short Message Service (SMS) support ............................................................................. .. 9
`Protocols andprotocol 9
`Use of channels (GSM only).......................................................................................................................... .. 10
`Layer 2 SAP] 3 handling for circuit switchedGSM1l
`Layer 2 (LLC) GPRS support (GSM only) .................................................................................................... ..
`l l
`GSMS entity in UMTS
`12
`
`.
`
`
`
`......
`
`Service definition ................................................................................................................................ .. 13
`3
`General .......................................................................................................................................................... .. 13
`3.1
`Service provided by the CM-sublayer ............
`............................................................................................. .. 13
`3.2
`
`Definition ofprimitives on the MS side....
`13
`3.2.1
`14
`3.2.1.1
`14
`3.2.1.2
`...... .. 14
`T3:2:1§TMNSMS-DA51"-A-lNDication-......... ..
`14
`3.2.1.4
`MNSMS-ESTab1ish-lNDication ........................................................................................................ .. 14
`3.2.1.5
`MNSMS-ERROR-1NDication ............................................................................................................ .. 14
`3.2.1.6
`MNSMS-RELease-REQuest .............................................................................................................. .. 14
`3.2.1.7
`Definition of primitives on the network side ............................................................................................ .. I4
`3.2.2
`3.2.2.1 MNSMS-ABORT-REQuest 15
`3.2.2.2
`MNSMS-DATA-REQuest .................................................................................................................. .. 15
`3.2.2.3
`15
`3.2.2.4
`MNSMS-ESTablish-REQuest ............................................................................................................ .. 15
`3.2.2.5
`MNSMS-ESTablish-INDication
`15
`3.2.2.6
`I6
`3.2.2.7
`16
`3.3
`16
`3.3.]
`16
`3.3.1.1
`16
`3.3.1.2
`17
`SM-RL-DATA-1NDication
`3.3.1.3
`17
`SM—RL-MEMORY-AVAILABLE—REQuest
`3.3.1.4
`SM-RL-REPORT—REQest.................................................................................................................. .. 17
`3.3.1.5
`SM-RL-REPORT—INDication ............................................................................................................ .. 17
`3.3.2
`Definition of primitives on the network
`17
`3.3.2.1
`SM-RL-DATA-REQuest ............... ..
`18
`3.3.2.2
`SM-RL-DATA-1NDication ................................................................................................................ .. 18
`3.3.2.3
`SM=RL=-MEMORY-AVAILABLE-INDication.................................................................................... 18
`3.3.2.4
`18
`3.3.2.5
`18
`
`Service provided by
`Definition ofprimitives on the MS
`
`
`
`4
`
`[Void] .................................................................................................................................................. .. 18
`
`CM-procedures .................................................................................................................................... .. 18
`5
`5.1 General 18
`5.2
`Short MessageControl 18
`5.2.1
`SMC-CS states at the MS side ofthe radio interface
`19
`5.2.1.1
`Mobile OriginatingCase 19
`5.2.1.1.l MO-1d1e(State19
`5.2.1.1.2
`MO-MM—connection pending (State1) 19
`5.2.1.1.3
`MO-Wait for CP-ACK (State
`19
`5.2.1.1.4
`MO-MM—connection established (State
`19
`5.2.1.2
`Mobile Terminating
`19
`
`363”
`
`M2M
`
`Ex. 2015
`
`3
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`4
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`5.2.1 .2.1
`5.2.1.2.2
`5.2.1 .2.3
`5.2.2
`5.2.2.1
`5.2.2.1.]
`5.2.2.1.2
`5.2.2.1.3
`5.2.2.1.4
`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.]
`5.2.3.1.2
`5.2.3.] .3
`5.2.3.2
`5.2.3.2.1
`5.2.3.2.2
`5.2.3.2.3
`5_.;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.]
`5.2.4.2.2
`5.2.4.2.3
`5.3
`5.3.1
`5.3.2.1
`5.3.2.2
`5.3.3
`5.3.4
`5.4
`
`19
`MT-Idle (State 0)
`MT-Wait for CP-ACK (State2) 19
`MT-MM-connection established (State
`19
`SMC—GP states at the MS side ofthe radio
`19
`Mobile Originating Case .................................................................................................................... .. 19
`MO-Idle (State 0) ............................................................................................................................ 20
`MO-GMM-connection pending (State 1) (UMTS
`20
`MO-Wait for CP-ACK (State2) 20
`MO-Wait for CP—Data (State
`20
`Mobile Terminating
`20
`MT-Idle (State
`20
`MT—Wait for RP-ACK (State 1) ................................................................................................... .. 20
`MT-Wait for CP-ACK (State2) 20
`SMC-CS states at the network side of the radio interface ........................................................................ .. 20
`Mobile Originating Case
`20
`MO-Idle (State
`20
`MO-Wait for CP-ACK (State2) 20
`MO-MM-connection established (State
`20
`21
`Mobile Terminating
`21
`MT-Idle (State
`21
`MT—MM-connection pending (State
`21
`MT-Wait for CP-ACK (State 2) ................................................................................................... ..
`21
`MT-MM-connection established (State 3) .................................................................................... ..
`21
`SMC—GP states at the network side of the radio interface....
`
`21
`Mobile OriginatingCase
`21
`MO-Idle (State
`21
`MO-Wait for RP-ACK (State 1) ................................................................................................... ..
`21
`MO-Wait for CP-ACK(State2)
`21
`Mobile Terminating Case ................................................................................................................... ..
`MT-Idle (State 0) .......................................................................................................................... .. 21
`MT-Wait for CP-ACK (State 1)
`22
`MT-Wait for CP DATA (State2) 22
`Short Message Control procedures
`22
`MM-connection establishment for circuit switched service ..................................................................... .. 22
`RPDU transfer for circuit switched service ........................................................................................ .. 22
`RPDU transfer for
`23
`Release ofMM and CM
`24
`Abnormal cases ........................................................................................................................................ .. 24
`Concatenating short message or notification
`25
`
`SM-RL-procedures ................................................................................................................................ 25
`6
`General25
`6.1
`Transition states of SMR entity25
`6.2
`SMR-states at the MS-side ofthe radio25
`6.2.1
`Idle(State O) ....................................................................................................................................... .. 26
`6.2.1.1
`Wait for RP-ACK (State 1)
`26
`6.2.1.2
`Wait for RETRANS TIMER (State 4) ............................................................................................... .. 26
`6.2.1.3
`SMR-states at the network side of theradio 26
`6.2.2
`Idle(State26
`6.2.2.1
`Wait for RP-ACK (State 1)
`26
`6.2.2.2
`Wait to send RP-ACK (State
`26
`6.2.2.3
`Short Message Relay
`26
`6.3
`TPDU
`26
`6.3.1
`[Void] ....................................................................................................................................................... .. 27
`6.3.2
`Notification relaying
`27
`6.3.3
`MS
`27
`6.3.3.1
`6.3.3.1.] Idle 27
`6.3.3.1.2
`Wait for RP-ACK state ................................................................................................................. .. 27
`6.3.3.1.3
`Wait for RETRANS Timer state ................................................................................................... .. 28
`6.3.3.2
`Network
`28
`6.3.3.2.]
`Idle state ........................................................................................................................................ .. 28
`
`~"Q1"°
`
`M2M
`
`Ex. 2015
`
`4
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`5
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`6.3.3.2.2
`6.3.4
`
`Wait to Send RP-ACK state .......................................................................................................... .. 28
`Abnormal28
`
`Message functional definitions and content ........................................................................................ .. 28
`General .......................................................................................................................................................... .. 28
`Messages for short message or notification transfer on CM .......................................................................... .. 29
`
`CP-ACK ................................................................................................................................................... .. 29
`CP-ERROR .............................................................................................................................................. .. 29
`Messages for short message and notification transfer on
`30
`
`RP-DATA (Network to MobileStation) 30
`RP-DATA (Mobile Station toNetwork) 30
`
`RP-ACK ................................................................................................................................................... .. 30
`
`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 .............................................................................. .. 31
`CP-messages .................................................................................................................................................... 31
`General ..................................................................................................................................................... .. 3]
`Protocol Discriminator and Transaction31
`Message
`32
`Other required infonnation elements ................................................................................................ ..
`32
`
`~
`GP—User-data-element?...................................................... ..
`.
`_
`32
`CP—Causeelement 32
`33
`33
`Message type indicator (MTI) .................................................................................................................. .. 33
`Message
`34
`34
`Other required information elements........................................................................................................ .. 34
`Originator address
`34
`Destination address
`35
`RP-User data element ......................................................................................................................... .. 35
`RP-Causeelement 36
`
`
`
`8 8
`
`.1
`8.1.1
`8.1.2
`8.1.3
`8.1.4
`8.-114'.-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 ........................................................ .. 37
`General
`37
`CP Error Handling ........................................................................................................................................... 38
`Message too short ...................................................................................................................................... 38
`Unknown or unforeseen transaction identifier
`38
`Unknown or unforeseen message type
`38
`Non-semantical mandatory information element errors ........................................................................... .. 39
`Messages with semantically incorrect contents
`39
`RP Error
`39
`Message tooshort 39
`Unknown or unforeseen Message Reference
`40
`Unknown or unforeseen message type
`40
`Non-semantical mandatory information element errors ........................................................................... .. 40
`Messages with semantically incorrect contents ........................................................................................ .. 40
`
`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
`
`M2M
`
`EX. 2015
`
`5
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`6
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`10
`
`Timers .................... ..
`
`............................................................................................................................ .. 4]
`
`Annex A (informative):
`
`Arrow diagrams ............................................................................................ 42
`
`Annex B (normative):
`
`SDL-description of the CM-layer ................................................................ 49
`
`B. 1
`
`Introduction ........... ..
`
`............................................................................................................................ .. 49
`
`Annex C (informative):
`
`Arrow diagrams ............................................................................................ 78
`
`Annex D (normative):
`
`SDL-description of the short message relay layer ..................................... 84
`
`D.l
`
`Introduction ........... ..
`
`............................................................................................................................ .. 84
`
`Annex E (informative):
`
`Cause definition ........................................................................................... .. 92
`
`Annex F (informative):
`
`LAPDm SAPI 3 handling for short message service ................................. 97
`
`Annex G (informative):
`
`Change history ............................................................................................ 104
`
`History ...........
`
`................ ..
`
`............................................................................ .. Error! Bookmark not defined.
`
`365'”
`
`'
`
`M2M
`
`EX. 2015
`
`6
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`7
`
`I
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`
`
`Foreword
`
`This Technical Specification (TS) has been produced by the 3"’ Generation Partnership Project (3GPP).
`
`The present document defines the Short Message Service (SMS) support on mobile radio interface within the 3GPP
`system.
`
`The contents of the present document are subject to continuing work within the TSG and may change following formal
`TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
`identifying change of release date and an increase in version number as follows:
`
`Version x.y.z
`
`where:
`
`x
`
`the first digit:
`
`1
`
`2
`
`3
`
`presented to TSG for information;
`
`presented to TSG for approval;
`
`or greater indicates TSG approved document under change control.
`
`y
`
`the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
`etc.
`
`z
`
`the third digit is incremented when editorial only changes have been incorporated in the document.
`
`367"’
`
`M2M
`
`Ex. 2015
`
`7
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`8
`
`3G TS 24.011 V3.2.0 (2000-03)
`
` 1
`
`Scope
`
`The present document 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.
`
`0 For a specific reference, subsequent revisions do not apply.
`
`0 For a non-specific reference, the latest version applies.
`
`[l_]
`
`[la]
`
`[2]
`
`[3a]
`
`[3]
`
`[4]
`
`[5]
`
`[6a]
`
`[6]
`
`[7]
`
`GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and
`acronyms".
`
`TR 21.905: "Vocabulary for 3GPP Specifications".
`
`TS 23.040: "Technical realization ofthe Short Message Service (SMS) Point-to-Point (PP)".
`
`TS 23.060: "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".
`
`TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
`
`TS 24.008: "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".
`
`GSM 04.18: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer
`3 specification; Radio Resource Control Protocol".
`
`1.2
`
`Abbreviations
`
`Abbreviations used in the present document are listed in GSM 01.04 and 3G TR 21.905, except below:
`
`RR connection: A R connection is a dedicated physical circuit switched domain connection used by the two RR or
`RRC peer entities to support the upper layers‘ exchange of information flows.
`
`PS signalling connection: is a peer to peer UMTS connection between MS and CN packet domain node.
`
`GPRS: Packet Services for GSM and UMTS system.
`
`The label (GSM only): indicates this section or paragraph applies only to GSM system. For multi system case this is
`determined by the current serving radio access network.
`
`The label (UMTS only): indicates this section or paragraph applies only to UMTS system. For multi system case
`this is determined by the current serving radio access network.
`
`In GSM,...: Indicates this paragraph applies only to GSM System. For multi system case this is determined by the
`current serving radio access network.
`
`“%P
`
`I
`
`NDNI
`
`Ex20U
`
`8
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`9
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`In UMTS,...: Indicates this paragraph applies only to UMTS System. For multi system case this is determined by the
`current serving radio access network.
`
`SIM: Subscriber Identity Module (see TS GSM 02.17). This specification makes no distinction between SIM and
`USIM.
`
`MS: Mobile Station. This specification makes no distinction between MS and UE.
`
` 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 TS 23.040. The terms "MO" - Mobile
`Originating - and "MT" - Mobile Terminating - are used to indicate the direction in which the short message is sent.
`
`The present document describes the procedures necessary to support the Short Message Service between the MS and the
`MSC or SGSN and vice versa, as described in TS 23.040.
`
`The procedures are based on services provided by the Mobility Management sublayer as described in TS24.007/24.008
`for GSM CS and UMTS CS/PS 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 ofthe MSC and the MS in GSM. The hierarchical model
`in Figure 2.] c shows the layer structure of the SGSN and the MS in UMTS.
`
`Msc
`
`E
`
`SM-AL
`
`SM-TL
`
`EM SMR M SM—RP protocolL SMR
`
` <——— SM-CP protocol ——>
`
`SMC
`
`
`
`Figure 2.1aITS 24.011: Protocol hierarchy for circuit switched service
`
`The hierarchical model in Figure 2.lb shows the layer structure ofthe SGSN and the MS.
`
`E
`
`E
`
`SM-AL
`
`SM-TL
`
`Sail/TL_—
`
`MIMI?“
`
` T‘
`
`GRR-sublayer
`
`SMR
`
`SMC
`
`<—— SM-RP protocol ——_>
`
`<._j— SM-CP protocol ——>
`
`SMR
`
`SMC
`
`3°?”
`
`M2M
`
`Ex. 2015
`
`9
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`10
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`Figure 2.1bITS 24.011: Protocol hierarchy for GPRS in GSM
`
`E
`
`SM-AL
`
`SM-TL
`
`SMR
`SM-RL
` SMC
`GMM-sublayer
`
`<
`.=
`
`SM—RP protocol —————> W
`SM-CP protocol ———>
`
`Figure 2.1c/24.011: Protocol hierarchy for packet switched service in UMTS
`
`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.
`
`T-he-peer—protocel-bet-vveen -two- SMC-entities-is-denoted-SM-ClZ,-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 sublayerGMM-sub:
`Radio Resource Management sublayer
`Logical Link Control sublayer
`GPRS Radio Resource sublayer in GSM
`
`GPRS Mobility Management sublayer
`
`2.2
`
`Use of channels (GSM only)
`
`Table 2.1/TS 24.011 summarizes the use of channels for the short message service for circuit switched GSM. Arrows
`indicate changes of channel.
`
`Table 2.1lTS 24.011: Channels used for short message transfer over circuit switched GSM
`
`Channel used
`
`SDCCH
`SDCCH —> SACCH
`SACCH
`SACCH -> SACCH ot. SDCCH“
`
`
`
`Channel deendenc
`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.
`
`BAZRJ
`
`EX.2015
`
`10
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`2.3
`General rule:
`
`11
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`Layer 2 SAPI 3 handling for circuit switched GSM
`
`The Radio Resource Management (RR reference GSM 04.18) in the Mobile Station and on the network side (ie. 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 ofthe mode.
`
`The network side may initiate release ofthe acknowledged mode for SAP] 3 either explicitly (by the use of DlSC- and
`UA-frames, see GSM 04.06) or indirectly by channel release (see GSM 04.18).
`
`This means:
`
`-
`
`-
`
`-
`
`the Mobile Station side will initiate establishment of SAPI 3 acknowledged mode in the case ofmobile
`originating short message transfer;
`
`the network side will initiate establishment of SAPI 3 acknowledged mode in the case of mobile terminating Sl’lOI't
`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
`resiEie_ifihFM'S'C.
`
`2.4
`
`Layer 2 (LLC) GPRS support (GSM only)
`
`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 ofthe different GPRS MS classes can be found in 23.060, and a briefoverview 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.
`
`31G1PP
`
`WM
`Ex. 2015
`
`11
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`12
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`MNSMS SAP
`
`
`
`
`
`
`
`
`LLSMS SAP
`
`MMSMS SAP
`
`Figure 2.2/TS 24.011: GSMS entity for GPRS Class AIB M8
`
`2.5
`
`GSMS entity in UMTS
`
`It shall be possible for a PS-attached MS of any mode of operation to send and receive short messages over UMTS radio
`channels.
`
`A description ofthe different mode of operation UMTS MS can be found in 23.060, and a brief overview is given
`below:-
`
`- CS/PS mode ofoperation MSs may be able to send and receive short messages using either the MM sublayer or
`the GMM sublayer.
`
`-
`
`PS mode of operation MSs may be able to send and receive short messages using only GMM sublayer.
`
`The GSMS entity for CS/PS mode of operation MS is shown in Figure 2.3. The GSMS shall communicate with the MM
`entity via the GMMSMS-SAP for UMTS CS/PS mode of operation MO SMS, in order to ascertain which transport
`service to use.
`
`The delivery path for M0 SMS is selected by the MS.
`
`
`
`GMMS S-SAP
`
`Figure 2.3ITS 24.011: GSMS entity for CS/PS mode of operation MS in UMTS
`
`34'?’
`
`M2M
`
`Ex. 2015
`
`12
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`13
`
`3G TS 24.011 V3.2.0 (2000-03)
`
` 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 ofa primitive and the initials of them are in line with the 24-series of 3G 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 ofa 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 oft'vvo SMC entities per service type
`(i.e. two for CS GSM and two for GPRS). This enables the MS to receive MT messages during an M0 message transfer.
`
`To ensure that an MS having the minimum oftwo SMC entities is able to receive MT messages during an M0 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 subclause 5.4.
`’
`
`The MSC or SGSN shall have a minimum oftwo SMC entities available each during an MT message transfer to a
`mobile station, one being reserved for M0 message transfer. In an M0 message transfer, the MSC or SGSN shall have
`one SMC entity reserved for handling of an MT message.
`
`3.2.1
`
`Definition of primitives on the MS side
`
`This subclause defines the service primitives used on the MS side. Table 3.1/TS 24.0] 1 gives an overview ofthe service
`primitives and main parameter linked to the primitives. All necessary control parameters to be used in the Short Message
`Service are defined in clause 7. All MNSMS service primitives defined in this subclause are passed to an SMC-entity.
`
`Table 3.1/TS 24.011: MNSMS service primitives on the MS-side
`
`SERVICE PRIMITIVES
`NAME
`MNSMS-A50“
`MNSMS—DATA
`
`PARAMETER
`
`MT RPDU
`
`§&E
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`MNSMS-ES? E_IEI
`
`
`EE
`
`
`
`sdP3=
`
`M2M
`
`Ex. 2015
`
`13
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`14
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`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 ofthe lower layer services.
`
`NOTE: Afier 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-|NDiCation
`
`An indication used by the SMC entity to pass the user information element (RPDU) ofa received CP—DATA message to
`SM-RL.
`
`NOTE‘.*Th'e'RPDU'is'typ"i'cally'an'RP$€K'or'an-RP=ERROR7Normally-this-service-is-used-to-report-theeutcemee
`of either a MO message transfer attempt or a mobile station memory available notification attempt.
`
`3.2.1.4
`
`MNSMS-ESTab|ish-REQuest
`
`A request from an SMR entity to establish a CM-connection. The request contains a RP-DATA UNIT as a parameter. It
`implies the:
`
`-
`
`-
`
`—
`
`establishment of a CM-connection for this SMR entity;
`
`forming ofthe CP—DATA message containing the RPDU; and
`
`passing of CP—DATA to the MM-sublayer.
`
`3.2.1.5
`
`MNSMS-ESTab|ish-INDiCation
`
`An indication used by the SMC entity to pass the SM-user information (RPDU) of a received CP—DATA message to
`SM-RL. It implies completion ofthe establishment ofthe CM-connection for this SMR entity.
`
`3.2.1.6
`
`MNSMS-ERROR-|NDiCation
`
`An indication used by the SMC entity to pass error information to SM-RL. The error information may be local or
`relayed by the CP-ERROR message.
`
`Use ofthis service primitive implies release of both CM and MM-connection.
`
`3.2.1.7
`
`MNSMS-RELease-REQuest
`
`A request to release the CM-connection (if it still exists).
`
`Use of this service primitive implies release ofthe associated CM and MM-connections.
`
`3.2.2
`
`Definition of primitives on the network side
`
`This subclause defines the service primitives used on the network side.
`
`Table 3.2/TS 24.01 1 gives an overview of the service primitives and linked main parameter. All MNSMS service
`primitives defined in this subclause are passed to an SMC—entity.
`
`W4’
`
`M2M
`
`Ex. 2015
`
`14
`
`M2M
`Ex. 2015
`
`

`
`Release 1999
`
`15
`
`3G TS 24.011 V3.2.0 (2000-03)
`
`Table 3.2lTS 24.011: MNSMS service primitives on the network side
`
`
`
`
`
`
`E E
`
`
`
`MNSMS-ERR°R-
`MNSMS-REL-
`
`
`
`
`
`3.2.2.1
`
`MNSMS-ABORT-REQuest
`
`A request from an SMR entity to release a CM-connection in abnormal cases.
`
`W