(GSM 04.11 version 7.0.0 Release 1998)
`
`38
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`9.2.5 Messages with semantically incorrect contents
`
`When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of
`GSM 04.11 are performed. If however no such reactions are specified, the mobile station shall proceed as follows:
`
`- When the corresponding SM transfer is not seen as successfully transferred, the mobile station shall ignore the
`message and return a CP-ERROR message with cause value #95 "semantically incorrect message", if an
`appropriate connection exists.
`
`— When the SM transfer is seen as successfully transferred, the mobile station shall ignore the message and enter
`the Idle State.
`
`-
`
`In the case that the message received is a CP-ERROR message, the mobile station shall ignore the message and
`enter the Idle State.
`
`The network may follow the same procedure.
`
`9.3
`
`RP Error Handling
`
`Upon receiving or sending an RP-ERROR message the SMR entity shall behave as described in the procedural
`description in clause 6.
`
`9.3.1
`
`Message too short
`
`When a message is received that is too short to contain a complete message type information element and Message
`Reference, that message shall be ignored.
`
`9.3.2
`
`Unknown or unforeseen Message Reference
`
`Whenever any RP-ACK message is received specifying a Message Reference which is not associated with an active SM
`transfer, the mobile station shall discard the message and return an RP-ERROR message with cause #81, "Invalid short
`message transfer reference value" using the received Message Reference, if an appropriate connection exists.
`
`When an RP-ERROR message is received specifying a Message Reference which is not associated with an active SM
`transfer, the mobile station shall discard the message.
`
`When the mobile station's SMR entity is not in the Idle state, and it receives an RP—DATA message specifying a
`Message Reference which is not associated with the active SM transfer, then it shall either:
`
`-
`
`-
`
`send an RP-ERROR message with cause #81, "lnvalid short message transfer reference value" using the received
`Message Reference, if an appropriate connection exists; or
`
`behave as described below for the receipt of an message not consistent with the protocol state.
`
`The same procedures may apply to the network.
`
`9.3.3
`
`Unknown or unforeseen message type
`
`If the Mobile Station receives a RP—message indicating a value of the message type indicator (MTI) defined as reserved,
`it shall ignore the message and return an RP-ERROR message with cause #97 "message type non-existent or not
`implemented", if an appropriate connection exists.
`
`If the Mobile Station receives a message (except RP-ERROR) not consistent with the protocol state, the Mobile Station
`shall ignore the message and return a RP-ERROR message with cause #98 "Message type not compatible with Short
`Message protocol state", if an appropriate connection exists.
`
`If the Mobile Station receives an RP-ERROR message not consistent with the protocol state, the Mobile Station shall
`ignore the message.
`
`The network may follow the same procedures.
`
`ETSI
`
`38
`
`M2M
`
`Ex. 2006
`
`
`38
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`39
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`9.3.4
`
`Non—semantica| mandatory information element errors
`
`When on receipt of a message:
`
`—
`
`-
`
`an "imperative message part" error; or
`
`a "missing mandatory IE" error;
`
`is diagnosed or when a message containing a syntactically incorrect mandatory IE is received, the mobile station shall
`(except for the case of a reserved value of the MTI as defined above) proceed as follows:
`
`- when the message is an RP-DATA or RP-ACK, the mobile station shall ignore the message and return an
`RP-ERROR message with cause #96 "invalid mandatory information", if an appropriate connection exists;
`
`- when the message is an RP-ERROR, the mobile station shall treat the message as an RP-ERROR message
`carrying RP-Cause value 1 11 without any diagnostic field, and with no RP-User Data.
`
`The network may follow the applicable procedures defined in this subclause.
`
`9.3.5 Messages with semantically incorrect contents
`
`When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of
`GSM 04.1 1 are performed. If however no such reactions are specified then:
`
`-
`
`-
`
`if the message was not an RP-ERROR message, the MS shall ignore the message and return an RP-ERROR
`message with cause value #95 "semantically incorrect message", if an appropriate connection exists; while
`
`if the message was an RP-ERROR message, the mobile station shall treat the message as an RP-ERROR message
`carrying RP-Cause value #111 without any diagnostic field, and with no RP-User Data.
`
`The network may follow the same procedure.
`
`
`
`10
`
`Timers
`
`The present document places the following requirements on the timers described in this ETS:
`
`—
`
`-
`
`-
`
`timer TRIM shall be greater than 35 seconds and less than 45 seconds;
`
`the value of timer TRAM shall be greater than 25 seconds and less than 35 seconds;
`
`timer TRZM shall be greater than 12 seconds and less than 20 seconds.
`
`ETSI
`
`39
`
`M2M
`
`EX. 2006
`
`
`39
`
`M2M
`Ex. 2006
`
`

`
`40
`(GSM 04.11 version 7.0.0 Release 1998)
`
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`Annex A (informative):
`Arrow diagrams
`
`Arrow diagram A1:
`
`The diagram shows CS GSM MO-message transfer by means of interlayer service primitives and the actual messages
`being transferred between the layer entities
`
`Arrow diagram A2:
`
`The diagram shows CS GSM MT-messaging by means of interlayer service primitives and the actual messages being
`transferred between the layer entities
`
`Arrow diagram A5:
`
`The diagram shows GPRS MO-message transfer by means of interlayer service primitives and the actual
`messages being transferred between the layer entities.
`
`MNSMS-primitives indicate services provided by CM to SM—RL.
`
`LLSMS-primitives indicate services provided by LLC to CM.
`
`CP-DATA is the CM—message carrying SM-RP data units.
`
`CP-ACK acknowledge CP-DATA reception on CM.
`
`Arrow diagram A6:
`
`The diagram shows GPRS MT-message transfer by means of interlayer service primitives and the actual
`messages being transferred between the layer entities.
`
`MNSMS-primitives indicate services provided by CM to SM—RL.
`
`LLSMS-primitives indicate services provided by LLC to CM.
`
`CP-DATA is the CM—message carrying SM-RP data units.
`
`CP-ACK acknowledge CP-DATA reception on CM.
`
`ETSI
`
`40
`
`M2M
`
`EX. 2006
`
`
`40
`
`M2M
`Ex. 2006
`
`

`
`
`
`
`
`
`
`._w>m_n:m-_2ocomc_mmmmos__§m=_m_.o250.2wm_n_0
`
`
`
`8°58:32>«E2:mp_m»m_.¢
`
`
`
`32:33$.3::o_w..o>2.3smo.
`
`
`
`2Eo.n_EE_-5m_.ms_mz
`
`
`
`E.-<»<nEz:.._._
`
`22¢n_O._._.E
`
`
`
`229gov255no.:.E5.0.:
`
`
`
`com-<._.<nEz3.._._
`
`2.5ioéoz%_wcozsmo__nos_
`
`E-_m_>_482E-_m
`
`
`
`<Eo-n_mvcmm-»wm_-m_>_mz_>_
`
`gm.E<o:z:.j
`
`c_o<no._._.E5.0.:
`
`
`
`
`
`<»<E_z:-._._29..n_0._._.EE-
`
`
`
`
`
`c_o<.n§$m-<F<o.ws_wzSm-<k<o:z:-4._
`
`$3mm-m_2mzs_
`
`
`
`as-<._<o:z3-.:
`
`Qo<no__._.Eu9.._m_m.2,_mzs_
`
`2:3no,_._E
`
`
`
`25$no__._.EE-<p<nEz:-._._
`
`
`
`3m.<»<o:z:.j
`
`Qo<n_O._._.E
`
`
`
`o_o<.n_mVE_.<Eo-ms_mz
`
`
`
`m<Em._mm_u>>o._._<
`
`RAW
`
`41
`
`M2M
`
`Ex. 2006
`
`
`41
`
`M2M
`Ex. 2006
`
`
`
`
`
`
`
`
`

`
`
`
`83%:33>N32:.mp_m._.m
`
`
`
`«v32:.88.3.93:o_m.o>2.3Ema.
`
`
`
`._o>m_n:m-s_ocom:_mmmwws_c3m:_E.o.r250.2mm_n_0
`
`
`
`
`
`2:3n_mvEm-»mm_.ws_mzs_
`
`_8m-<»<o:z:.._._
`
`<53go3.:5o._._
`AV2:5no.:.E
`
`<Eonoas.<._.<E._z3.._..
`
`._m-s_m
`
`
`
`s_ooioi_>_o._m-_>_m
`
`«EmEoéoz
`
`22¢cozsm230.2
`
`Qo<my;2;.<»<o.ms_mzs_
`
`8Em_m.ms_wz_2
`
`
`
`Em-<._.<n_._._zD.._._
`
`5.0.3
`
`xo<no
`
`
`
`as-<»<nEz:-._._
`
`v_o<n_O._._._._.
`
`$_.._mm.ws_mz_>_
`
`
`
`22n_O._jtE-<»<E_z:.j
`
`
`
`255no._._.EE-<._.<n:._z:.._._
`
`
`
`Em.<Eo:z3..:
`
`xo<n_O,_._.:
`
`2&3my;us-»mm.w_>_mz_>_
`
`<59no_._._._.
`
`Sm.<p<E_z:.j
`
`Qo<navEm.<»<o.ms_mz
`
`
`
`o<Eflmflu>>O._._<
`
`ELM
`
`42
`
`M2M
`
`Ex. 2006
`
`
`42
`
`M2M
`Ex. 2006
`
`
`
`
`
`
`
`
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`43
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`
`
`Annex B (normative):
`SDL-description of the CM-layer
`
`B.1
`
`Introduction
`
`This annex contains an SDL-description of the Connection Management Sublayer in terms of the Short Message Service
`Support. The CM- sublayer provides services to Short Message Relay Layer.
`
`The SDLs contain a mixture of peer to peer messages and conceptual primitives between the layers SM-RL, CM, MM
`and LLC, as viewed by the SMC entities. SDL-l/2/3 show the CS GSM SMC entity on MS-side for Mobile Originated
`(MO) short message transfer, SDL-4/5/6 show the CS GSM SMC entity on MS-side for Mobile Terminated (MT) short
`message transfer, SDL—7/8/9 show the CS GSM SMC entity on the network side for Mobile Originated (MO) short
`message transfer, and SDL-10/l 1/12 show the CS GSM SMC entity on the network side for Mobile Terminated (MT)
`short message transfer.
`
`SDL-13/14/15 show the GPRS SMC entity on MS-side for Mobile Originated (MO) short message transfer,
`SDL—l6/ 17/ l 8 show the GPRS SMC entity on MS-side for Mobile Terminated (MT) short message transfer,
`SDL-19/20/21 show the GPRS SMC entity on the network side for Mobile Originated (MO) short message transfer, and
`SDL-22/23/24 show the GPRS SMC entity on the network side for Mobile Terminated (MT) short message transfer.
`
`The lower layers (below MM and LLC) are transparent to an SMC entity.
`
`MO-IDLE
`
`MNSMS-
`EST-Req
`(RP DATA)
`
`CP DATA
`
`Set TC1M
`
`M0-SMC-GP entity on MS-side for GPRS
`SDL-13
`
`ETSI
`
`43
`
`M2M
`
`EX. 2006
`
`
`43
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`44
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`Reset TC1 M
`
`Ind
`
`retx = retx+1
`
`
`
`
`CP DATA
`
`
`
`Set retx = Zero
`
`MO-IDLE
`
`
`
`MO-SMC-GP entity on MS-side for GPRS
`SDL-14
`
`ETSI
`
`44
`
`M2M
`
`EX. 2006
`
`
`44
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`45
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`CP ERROR
`
`
`
`for
`
`CP DATA
`
`CP DATA
`
`
`
` MO-IDLE
`
`
`
`MO-SMC-GP entity on MS-side for GPRS
`SDL-15
`
`1
`
`
`
`
`
`MO_Wait
`for CP ACK
`
`
`
`
`
`MO_Wait
`for CP DATA
`
`
`
`2
`
`MO-SMC-GP entity on MS-side for GPRS
`State transition diagram
`
`ETSI
`
`45
`
`M2M
`
`EX. 2006
`
`
`45
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`46
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`ir{dL®5 HDIATA)
`
`1 MT — Wait
`
`MT-SMC-GP entity on MS-side for GPRS
`SDL-16
`
`ETSI
`
`46
`
`M2M
`
`EX. 2006
`
`
`46
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`47
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`
`
`RP ACK
`
`MT-Wait
`for
`
`
`
`CP ERROR
`
`
`
`MNSMS-
`
`DATA-Req
`
`(RP ACK)
`
`
`> C
`
`P DATA
`
`Set TC1M
`
`6)
`
`2 MT-Wait
`for
`CP ACK
`
`a
`
`MT-SMC-GP entity on MS-side for GPRS
`SDL-17
`
`ETSI
`
`47
`
`M2M
`
`EX. 2006
`
`
`47
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 70.0 Release 1998)
`
`48
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`Reset TC1 M
`
`
`
` retx = retx+1
`
`Set retx = Zero
`
`
`
`
`Set retx = Zero
`
`MT-IDLE
`
`MT-SMC-GP entity on MS-side for GPRS
`SDL-18
`
`ETSI
`
`48
`
`M2M
`
`EX. 2006
`
`
`48
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`49
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`2
`
`
`
`MT_Wait
`for CP ACK
`
`MT-SMC-GP entity on MS-side for GPRS
`State transition diagram
`
`Ind-(CP DAT
`
`MO-SMC-GP entity on Network side for GPRS
`SDL-19
`
`ETSI
`
`49
`
`M2M
`
`EX. 2006
`
`
`49
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`50
`
`ETSI TS 100 942 V7.0.0 (1999-O8)
`
`
`
`MNSMS—
`DATA-Req
`(RP ACK)
`
`
`®——>
`
`CF’ DATA
`
`CP ERROR
`
`Set TC1N
`
`
` MT-IDLE
`
`
`
`
`MO-SMC-GP entity on Network side for GPRS
`SDL-20
`
`ETSI
`
`50
`
`M2M
`
`EX. 2006
`
`
`50
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`51
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`
`
` Reset TC1 N
`
`Set retx = Zero
`
`retx = retx+1
`
`
`
`Set retx = Zero
`
`
`
`
`MO-IDLE
`
`
`MO-SMC-GP entity on Network side for GPRS
`SDL-21
`
`ETSI
`
`51
`
`M2M
`
`EX. 2006
`
`
`51
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`52
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`1
`
`
`
`
`
`MO_Wait
`for RP ACK
`
`
`
`
`
`
`
`2
`
`MO_Wait
`for CP ACK
`
`MO-SMC-GP entity on Network-side for GPRS
`State transition diagram
`
`MT-IDLE
`
`CP DATA
`
`Set TC1N
`
`MT-SMC-GP entity on Network-side for GPRS
`SDL-22
`
`ETSI
`
`52
`
`M2M
`
`EX. 2006
`
`
`52
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`53
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
` Set reb( = Zero
`
`
`retx = retx+1
`
`
`
`CP DATA
`
`Set retx = Zero
`
`®
`
`MT-SMC-GP entity on Network-side for GPRS
`SDL-23
`
`ETSI
`
`53
`
`M2M
`
`EX. 2006
`
`
`53
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`54
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`CP DATA
`
`
`
`
`CP DATA
`
`
`
` MT—|DLE
`
`
`
`CP ERROR
`
`MT-SMC-GP entity on Network-side for GPRS
`SDL-24
`
`
`
`1
`
`
`
`
`
`MTjNfit
`mrCPACK
`
`
`
`ZMTjNmt
`mrCPDATA
`
`2
`
`
`
`MT-SMC-GP entity on Network-side for GPRS
`State transition diagram
`
`ETSI
`
`54
`
`M2M
`
`EX. 2006
`
`
`54
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`55
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`
`
`Annex C (informative):
`Arrow diagrams
`
`Arrow diagram Cl :
`
`The diagram reflects MO-message transfer by means of interlayer service primitives and the actual messages being
`transferred between the layer entities.
`
`-
`
`SM-RL-primitives indicate services provided by SM-RL to SM-TL and RL (* see note).
`
`- MNSMS-primitives indicate services provided by CM to SM-RL.
`
`-
`
`RP—DATA is the SM-RL message carrying SM—TP data units.
`
`- RP-ACK acknowledges RP—DATA reception on SM-RL.
`
`Arrow diagram C2:
`
`The diagram reflects MT-messaging by means of interlayer service primitives and the actual messages being transferred
`between the layer entities.
`
`-
`
`SM-RL-primitives indicate services provided by SM-RL to SM-TL and RL (* see note).
`
`- MNSMS-primitives indicate services provided by CM to SM-RL.
`
`-
`
`RP—DATA is the SM-RL message carrying SM—TP data units.
`
`- RP-ACK acknowledges RP—DATA reception on SM-RL.
`
`Arrow diagram C3:
`
`The diagram reflects memory available notification transfer by means of interlayer service primitives and the actual
`messages being transferred between the layer entities.
`
`-
`
`SM-RL-primitives indicate services provided by SM-RL to SM-TL and RL (* see note).
`
`- MNSMS-primitives indicate services provided by CM to SM-RL.
`
`- RP-SMMA is the SM-RL message indicating that the mobile has memory available to receive one or more short
`messages.
`
`- RP-ACK acknowledges RP-SMMA reception on SM-RL.
`
`- RP-ERROR reports a failure in the notification procedure on the network side.
`
`ETSI
`
`55
`
`M2M
`
`EX. 2006
`
`
`55
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`56
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`Arrow diagram C4:
`
`The diagram reflects the abort of any retransmission of a memory available notification by SM-RL by means of the
`SM-RL-MEMORY-AVAILABLE interlayer service primitive request with the SM-MEM-NOTIF-ABORT parameter
`present. The use of this primitive and the associated parameter are, of course, local to the mobile station.
`
`SM-RL-primitives indicate services provided by SM-RL to SM-TL and RL (note).
`
`MNSMS-primitives indicate services provided by CM to SM-RL.
`
`RP—SMMA is the SM-RL message indicating that the mobile has memory available to receive one or more short
`messages.
`
`RP-ACK acknowledges RP-SMMA reception on SM-RL.
`
`RP-ERROR reports a failure in the notification procedure on the network side.
`
`The SM-RL being the upper layer in the MSC, an interworking function between SM-RL-procedures and
`MAP-procedure is necessary. The term "RL" is used in the diagrams to indicate this function (see figure).
`
`
`
`Interw. func.
`
`NOTE:
`
`ETSI
`
`56
`
`M2M
`
`EX. 2006
`
`
`56
`
`M2M
`Ex. 2006
`
`

`
`
`
`398a:93>«.32:my_mE
`
`mm
`
`
`
`32:88$.3::o_m._w>2.3smov
`
`
`
`
`
`._m_-s_wcom:_mmmmos_u.2a:_m_.O230.2
`
`
`
`E_2m5m.m2@E_.E<o.._m.2m
`
`$m.Eo$m.E._>_m
`
`wEmfozzmz
`
`2.5Szsm2_€s_
`
`E$-55
`
`2020
`
`2.55H_.._2w
`
`<_.<n_.nE
`
`Ti
`
`
`
`E_2m:m.m_2@u§.<Zn.._m.2m
`
`
`
`F0Em._mm_u>>o.:<
`
`ism
`
`E_.Eon_mm.#_.s_w
`
`57
`
`M2M
`
`EX. 2006
`
`
`57
`
`M2M
`Ex. 2006
`
`
`

`
`
`
`8.38:33>N32:9.am.
`
`mm
`
`
`
`$2:mmmoam2::o_2o>2.3.23.
`
`
`
`
`
`|_Mu5_WCOm:_mmmwws__u0uNC_:.:0.—.o__no_2
`
`ou_mfozzoz
`
`3.5Szsm¢__€s_
`
`JE._m.s_w
`
`soso
`
`
`
`.E-_>_m._._.._2w
`
`
`
`:m_>_da.ms_w._;m.S<o.._m._2m
`
`E__-Eonmm.§-_)_m
`
`<29“;
`
`v_o<-n_w_
`
`
`
`NoEm._mm__u>>o:<
`
`ELM
`
`$m-Eon_m_m.#_.s_m
`
`
`
`Em>_._mo.ws@E_.<:B.._m.s_m
`
`58
`
`M2M
`
`Ex. 2006
`
`
`58
`
`M2M
`Ex. 2006
`
`
`
`

`
`
`
`893...:32>N32:mp_w..m
`
`an
`
`
`
`82:$3.»:33co_2o>3.3swo.
`
`
`
`
`
`._m.s_m:0co_.8_Eoz2%__m><roams.
`
`._m
`
`«Emfozawz
`
`.E.s_m
`
`soso
`
`
`
`._m._>_m._._.._2m
`
`2.;Scam¢__%s_
`
`u:_.m._m<.:<><.>m
`os_m2.§.2m
`
`$m-Eon_$_.#_.s_w
`
`<s:>_m.nE
`
`mo$m_..E\v_o<.n_m
`
`
`
`noEEmm__u.so.:<
`
`ism
`
`>mo_>_E>_.E-_2m
`
`$m-m:m_fi_<><
`
`2_.Eo$m.#_._>_m
`
`59
`
`M2M
`
`EX. 2006
`
`
`59
`
`M2M
`Ex. 2006
`
`

`
`
`
`8o.$m:33>«E2:m»_.....E
`
`8
`
`
`
`$2:$8.3.SEco_ma>3.3saw.
`
`
`
`._m.s_w:0tone.:o_.S_.=ozm_%__a><>._oEm_2
`
`
`
`
`
`.E
`
`oEmfozzoz
`
`._m.s_m
`
`20E0
`
`._~_
`.s_m
`
`.:.s_m
`
`2.5.s_§m2_€s_
`
`.:__.B9:_<><.Eo_E_2.E._2w
`
`$m.Eonmm.E.s_w
`
`mo$m_-nE\v_o<.nE
`
`Eosms_.#_._2w
`
`$~_-m_._mE_<><
`
`Cmom_<¢:oz.s_m_2.ws_mV
`
`Eosms_.#_._2m
`
`$m.m:m,:_<><
`
`E_.Eon_mx.._m.2m
`
`60
`
`
`
`voEm._mm__u>>o.:<
`
`ELM
`
`
`
`
`
`
`
`
`
`.cm>_mmm;ummzuw.tonmcmsmzofi:m>m.Ewwan>mEfir:mwmmwmwEw2mo_uc_mm:__umcmmo
`
`
`
`
`
`
`
`
`
`MFOZ
`
`M2M
`
`EX. 2006
`
`
`60
`
`M2M
`Ex. 2006
`
`
`
`
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`61
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`
`
`Annex D (normative):
`SDL-description of the short message relay layer
`
`D.1
`
`Introduction
`
`This annex contains an SDL-description of the Short Message Relay Layer in terms of the Short Message Service
`Support. The Short Message Relay Layer provides services to Short Message Transfer Layer.
`
`The SDLs contain a mixture of peer to peer messages and conceptual primitives between the layers SM-TL, SM-RL and
`CM, as viewed by the SMR entities. SDL—l/2/3 show the SMR entity on MS—side, and SDL-4/5 on the network side.
`
`The lower layers (below CM) are transparent to an SMR entity.
`
`ETSI
`
`61
`
`M2M
`
`EX. 2006
`
`
`61
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`62
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`SM-RL-
`
`REPORT-
`
`Ind
`
`
`
`
`
`
`SMR-entity on MS-side
`MO Short Message transfer
`SDL-1
`
`ETSI
`
`62
`
`M2M
`
`EX. 2006
`
`IDLE
`
`SM-RL-
`DATA-Req
`(SMS-SUBMIT)
`
`MNSMS-
`EST-Req
`(RP—DATA)
`
`
`
`SET TR1M
`
`
`
`RESET
`TR1M
`
`
`
`REL-Req
`
`
`
`
`62
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`63
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`MNSMS-
`EST-Ind
`(RP-DATA)
`
`RP-DATA
`Accepted
`?
`
`SM-RL-
`DATA-Ind
`
`SET TRZM
`
`RP-ERROR
`
`(RP-DATA)
`
`
`
`SM-RL-
`REPORT-
`Req (RP-ACK)
`
`SM-RL-
`REPORT-Req
`(RP-ERROR)
`
`RESET TR2M
`
`RESET TRZM
`
`RESET TR2M
`
`J
`
`MNSMS-
`
`SM-RL-
`REPORT-
`Ind
`
`
`
`
`
`RP-ERROR
`
`SM R-entity on MS-side
`MT Short Message transfer
`SDL-2
`
`ETSI
`
`63
`
`M2M
`
`EX. 2006
`
`
`63
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`64
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`YES
`AVAILABLE-Rec
` RETRANS
`(RP-SMMA)
`
`
`
`MNSMS»
`EST-Req
`
`
`SETRETRANS
`FLAG,TRAM
`RESET TR1M
`
`RESET
`
`FLAG,TR1M
`
`SM-RL-MEMORY
`
`VAILABLE-Req
`
`
`(SMS—MEM-
`NOTIF-ABORT
`
`
`
`RESET
`RETRANS
`FLAG,TRAM
`
`
`
`
`SM-RL-
`MEMORW
`
`
`
`IDLE
`
`
`
`WAHFOR
`
`RETRANS'HMER
`
`SETTR1M
`
`
`
`CNAYER
`|Nl§|R()|:\(TE()N
`
` j_
`
`SM-RLMEMORY
`VAILABLE Re‘
`‘i
`(SMS‘MEM'
`NOTIF-ABORT
`
`
`
`
`
`RP-ERROR
`
`
`
`SET
`
`RETRANS
`FLAG
`
`
`
`
`TEMP
`NETWORK RESET
`
`TR1M and
`
`RETRANSFLAG
`
`
`
`
`
`SMR-entity on MS-side
`Memory Available Notification
`SDL-3
`
`ETSI
`
`64
`
`M2M
`
`EX. 2006
`
`
`64
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`65
`
`ETSI TS 100 942 V7.0.0 (1999-O8)
`
` 4
`
`Wait for
`RETRANS
`Timer
`
`SM R-entity on MS-side
`State transition diagram
`
`ETSI
`
`65
`
`M2M
`
`Ex. 2006
`
`
`65
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`66
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`RP—ERROR
`
`SM—RL-
`Ind
`REPORT-
`
`SM R-entity on Network-side
`MT Short Message transfer
`SDL-4
`
`ETSI
`
`66
`
`h42h4
`
`EX.2OO6
`
`IDLE
`
`SM—RL-
`DATA—Req
`(RP-DATA)
`
`MNSMS-
`EST-Req
`(RP-DATA)
`
`
`
`SET TR1N
`
`
`
`RESET
`mm
`
`MNSMS—
`REL_Req
`
`IDLE
`
`
`66
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`67
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`
`
`RPDU
`Accepted
`?
`
`
`NO
`
`SM-RL-
`
`
`DATA-Ind
`(RP-DATA
`or RP-SM MA
`
`
`SET TRZN
`
`
`
`RF’—ERROR
`
`
` —I
`(RP-ERROR)
`
`
`
`RESET TR2N
`
`RESET TR2N
`
`RESET TR2N
`
`SM-RL—
`REPORT.
`Ind
`
`
`
`Rp_ACK
`
`RP-ERROR
`
`MNSMS-
`REL-Req
`
`SM R-entity on Network-side
`M0 Short Message and Notification transfer
`SDL-5
`
`ETSI
`
`67
`
`M2M
`
`EX. 2006
`
`SM-RL-
`REPORT-Req
`
`mm
`
`MNSMS-
`
`SM-RL—
`
`REPORT-
`
`Req (RP-ACK)
`
`
`
`
`
`
`
`67
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`68
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`SM R-entity on Network-side
`State transition diagram
`
`ETSI
`
`68
`
`M2M
`
`EX. 2006
`
`
`68
`
`M2M
`Ex. 2006
`
`

`
`ETSI TS 100 942 V7.0.0 (1999-08)
`69
`(GSM 04.11 version 7.0.0 Release 1998)
`
`
`Annex E (informative):
`Cause definition
`
`E-I: CP-cause definition
`
`Cause no. 17: "Network failure"
`
`This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g.
`problems in MAP.
`
`Cause no. 22: "Congestion"
`
`This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility
`busy/congested etc.).
`
`Cause no. 81: "Invalid Transaction Identifier"
`
`This cause indicates that the equipment sending this cause has received a message with a Transaction Identifier
`which is currently not use on the MS - network interface.
`
`Cause no. 95: "Semantically incorrect message"
`
`This cause is used to report the receipt of a message with semantically incorrect content.
`
`Cause no. 96: "lnvalid mandatory information"
`
`This cause indicates that the equipment sending this cause has received a message with non—semantical
`mandatory information element errors.
`
`Cause no. 97: "Message type non—existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message with a message type it does not
`recognize either because this is a message not defined or defined but not implemented by the equipment sending
`this cause.
`
`Cause no. 98: "Message not compatible with short message protocol state"
`
`This cause indicates that the equipment sending this cause has received a message not compatible with the Short
`Message protocol state.
`
`Cause no. 99: "Information element non—existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message which includes information
`elements not recognized because the information element identifier is not defined or it is defined but not
`implemented by the equipment sending the cause.
`
`However, the information element is not required to be present in the message in order for the equipment sending
`the cause to process the message.
`
`Cause no. 111: "Protocol error, unspecified"
`
`This cause is used to report a protocol error event only when no other cause applies.
`
`E—2: RP-cause definition mobile originating SM-transfer
`
`Cause no. 1: "Unassigned (unallocated) number"
`
`This cause indicates that the destination requested by the Mobile Station cannot be reached because, although the
`number is in a valid format, it is not currently assigned (allocated).
`
`Cause no. 8: "Operator determined barring"
`
`This cause indicates that the MS has tried to send a mobile originating short message when the MS's network
`operator or service provider has forbidden such transactions.
`
`ETSI
`
`69
`
`M2M
`
`EX. 2006
`
`
`69
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`70
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`Cause no. 10: "Call barred"
`
`This cause indicates that the outgoing call barred service applies to the short message service for the called
`destination.
`
`Cause no. 21: "Short message transfer rejected"
`
`This cause indicates that the equipment sending this cause does not wish to accept this short message, although it
`could have accepted the short message since the equipment sending this cause is neither busy nor incompatible.
`
`Cause no. 27: "Destination out of service"
`
`This cause indicates that the destination indicated by the Mobile Station cannot be reached because the interface
`to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling
`message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the
`remote user, user equipment off-line, etc.
`
`Cause no. 28: "Unidentified subscriber"
`
`This cause indicates that the subscriber is not registered in the PLMN (i.e. IMSI not known).
`
`Cause no. 29: "Facility rejected"
`
`This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.
`
`Cause no. 30: "Unknown subscriber"
`
`This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not
`allocated to a subscriber).
`
`Cause no. 38: "Network out of order"
`
`This cause indicates that the network is not functioning correctly and that the condition is likely to last a
`relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be
`successful.
`
`Cause no. 41: "Temporary failure"
`
`This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long
`period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost
`immediately.
`
`Cause no. 42: "Congestion"
`
`This cause indicates that the short message service cannot be serviced because of high traffic.
`
`Cause no. 47: "Resources unavailable, unspecified"
`
`This cause is used to report a resource unavailable event only when no other cause applies.
`
`Cause no. 50: "Requested facility not subscribed"
`
`This cause indicates that the requested short message service could not be provided by the network because the
`user has not completed the necessary administrative arrangements with its supporting networks.
`
`Cause no. 69: "Requested facility not implemented"
`
`This cause indicates that the network is unable to provide the requested short message service.
`
`Cause no. 81: "Invalid short message transfer reference value"
`
`This cause indicates that the equipment sending this cause has received a message with a short message reference
`which is not currently in use on the MS-network interface.
`
`Cause no. 95: "Invalid message, unspecified"
`
`ETSI
`
`70
`
`M2M
`
`EX. 2006
`
`
`70
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`71
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`This cause is used to report an invalid message event only when no other cause in the invalid message class
`applies.
`
`Cause no. 96: "Invalid mandatory information"
`
`This cause indicates that the equipment sending this cause has received a message where a mandatory
`information element is missing and/or has a content error (the two cases are indistinguishable).
`
`Cause no. 97: "Message type non—existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message with a message type it does not
`recognize either because this is a message not defined or defined but not implemented by the equipment sending
`this cause.
`
`Cause no. 98: "Message not compatible with short message protocol state"
`
`This cause indicates that the equipment sending this cause has received a message such that the procedures do not
`indicate that this is a permissible message to receive while in the short message transfer state.
`
`Cause no. 99: "Information element non—existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message which includes information
`elements not recognized because the information element identifier is not defined or it is defined but not
`implemented by the equipment sending the cause.
`
`However, the information element is not required to be present in the message in order for the equipment sending
`the cause to process the message.
`
`Cause no. 1 1 1: "Protocol error, unspecified"
`
`This cause is used to report a protocol error event only when no other cause applies.
`
`Cause no. 127: "Interworking, unspecified"
`
`This cause indicates that there has been interworking with a network which does not provide causes for actions it
`takes; thus, the precise cause for a message which is being send cannot be ascertained.
`
`E-3: RP-cause definition mobile terminating SM-transfer
`
`Cause no. 22: "Memory capacity exceeded"
`
`This cause indicates that the mobile station cannot store the incoming short message due to lack of storage
`capacity.
`
`Cause no. 81: "Invalid short message reference value"
`
`This cause indicates that the equipment sending this cause has received a message with a short message reference
`which is not currently in use on the MS-network interface.
`
`Cause no. 95: "Invalid message, unspecified"
`
`This cause is used to report an invalid message event only when no other cause in the invalid message class
`applies.
`
`Cause no. 96: "Invalid mandatory information"
`
`This cause indicates that the equipment sending this cause has received a message where a mandatory
`information element is missing and/or has a content error (the two cases are indistinguishable).
`
`Cause no. 97: "Message type non—existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message with a message type it does not
`recognize either because this is a message not defined or defined but not implemented by the equipment sending
`this cause.
`
`Cause no. 98: "Message not compatible with short message protocol state"
`
`ETSI
`
`71
`
`M2M
`
`EX. 2006
`
`
`71
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`72
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`This cause indicates that the equipment sending this cause has received a message such that the procedures do not
`indicate that this is a permissible message to receive while in the short message transfer state.
`
`Cause no. 99: "Information element non-existent or not implemented“
`
`This cause indicates that the equipment sending this cause has received a message which includes information
`elements not recognized because the information element identifier is not defined or it is defined but not
`implemented by the equipment sending the cause.
`
`However, the information element is not required to be present in the message in order for the equipment sending
`the cause to process the message.
`
`Cause no. 111: "Protocol error, unspecified"
`
`This cause is used to report a protocol error event only when no other cause applies.
`
`E-4: RP-Cause definition memory available notification
`
`Cause no. 30: “Unknown Subscriber"
`
`This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not
`allocated to a subscriber).
`
`Cause no. 38: "Network out of order"
`
`This cause indicates that the network is not functioning correctly and that the condition is likely to last a
`relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be
`successful.
`
`Cause no. 41: "Temporary failure"
`
`This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long
`period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost
`immediately.
`
`Cause no. 42: "Congestion"
`
`This cause indicates that the short message service cannot be serviced because of high traffic.
`
`Cause no. 47: "Resources unavailable, unspecified"
`
`This cause is used to report a resource unavailable event only when no other cause applies.
`
`Cause no. 69: "Requested facility not implemented"
`
`This cause indicates that the network is unable to provide the requested memory available notification service.
`
`Cause no. 95: "Invalid message, unspecified"
`
`This cause is used to report an invalid message event only when no other cause in the invalid message class
`applies.
`
`Cause no. 96: "Invalid mandatory information"
`
`This cause indicates that the equipment sending this cause has received a message where a mandatory
`information element is missing and/or has a content error (the two cases are indistinguishable).
`
`Cause no. 97: "Message type non-existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message with a message type it does not
`recognize either because this is a message not defined or defined but not implemented by the equipment sending
`this cause.
`
`Cause no. 98: "Message not compatible with short message protocol state"
`
`ETSI
`
`72
`
`M2M
`
`EX. 2006
`
`
`72
`
`M2M
`Ex. 2006
`
`

`
`(GSM 04.11 version 7.0.0 Release 1998)
`
`73
`
`ETSI TS 100 942 V7.0.0 (1999-08)
`
`This cause indicates that the equipment sending this cause has received a message such that the procedures do not
`indicate that this is a permissible message to receive while in the short message transfer state.
`
`Cause no. 99: "Information element non-existent or not implemented"
`
`This cause indicates that the equipment sending this cause has received a message which includes information
`elements not recognized because the information element identifier is not defined or it is defined but not
`implemented by the equipment sending the cause.
`
`However, the information element is not required to be present in the message in order for the equipment sending
`the cause to process the message.
`
`Cause no. 111: "Protocol error, unspecified"
`
`This cause is used to report a protocol error event only when no other cause applies.
`
`Cause no. 127: "lnterworking, unspecified"
`
`This cause indicates