ETSI
`_\
`
`\
`
`GSM 04.11
`GSM
`March 1996
`TECHNICAL
`Version 5.1.0
`SPECIFICATION
`
`
`Source: ETSI TC-SMG
`
`Reference: TS/SMG-O30411QR
`
`Ics: 33.060.50
`
`Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
`
`GSEITI'
`
`GLOBAL SYSTEM FOR
`MOBILE COMMUNICATIONS
`
`Digital cellular telecommunication system (Phase 2+);
`
`Point-to-Point (PP) Short Message Service (SMS)
`
`support on mobile radio interface
`
`(GSM 04.11)
`
`ETSI
`
`European Telecommunications Standards Institute
`ETSI Secretariat
`
`Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
`Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
`X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
`Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
`
`Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
`foregoing restriction extend to reproduction in all media.
`
`© European Telecommunications Standards Institute 1996. All rights reserved.
`
`Google Ex. 1220, pg. 1
`
`Google Ex. 1220, pg. 1
`
`

`

`Page 2
`GSM 04.11 Version 5.1.0 March 1996
`
`Whilst every care has been taken in the preparation and publication of this document, errors in content,
`typographical or otherwise, may occur.
`If you have comments concerning its accuracy, please write to
`"ETSI Editing and Committee Support Dept." at the address shown on the title page.
`
`Google Ex. 1220, pg. 2
`
`Google Ex. 1220, pg. 2
`
`

`

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

`

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

`

`Page 5
`GSM 04.11 Version 5.1.0 March 1996
`
`7.3.2
`7.3.3
`7.3.4
`
`RP-SMMA ............................................................................................. 30
`RP—ACK ................................................................................................ 30
`RP-ERROR ........................................................................................... 30
`
`8
`
`Message format and information elements coding ...................................................................... 31
`8.1
`CP-messages ........................................................................................................... 31
`8.1.1
`General ................................................................................................. 31
`8.1.2
`Protocol Discriminator and Transaction Identifier....................................... 31
`
`8.1.3
`8.1.4
`
`Message type ........................................................................................ 31
`Other required information elements ........................................................ 32
`8.1.4.1
`CP-User data element..................................................... 32
`8.1.4.2
`CP-Cause element .......................................................... 32
`
`8.2
`
`RP-messages ........................................................................................................... 33
`8.2.1
`General ................................................................................................. 33
`
`8.2.2
`8.2.3
`8.2.4
`8.2.5
`
`Message type indicator (MTI) ................................................................. 33
`Message reference ................................................................................ 34
`[Spare] .................................................................................................. 34
`Other required information elements ........................................................ 34
`8.2.5.1
`Originator address element ............................................. 34
`8.2.5.2
`Destination address element ............................................ 35
`8.2.5.3
`RP-User data element..................................................... 35
`8.2.5.4
`RP-Cause element .......................................................... 36
`
`9
`
`Handling of unknown, unforeseen, and erroneous protocol data .................................................. 38
`9.1
`General .................................................................................................................... 38
`
`9.2
`
`9.3
`
`CP Error Handling ..................................................................................................... 38
`9.2.1
`Message too short ................................................................................. 38
`9.2.2
`Unknown or unforeseen transaction identifier ............................................ 38
`
`Unknown or unforeseen message type ..................................................... 38
`9.2.3
`Non—semantical mandatory information element errors ............................... 39
`9.2.4
`Messages with semantically incorrect contents ......................................... 39
`9.2.5
`RP Error Handling ..................................................................................................... 39
`9.3.1
`Message too short ................................................................................. 39
`9.3.2
`Unknown or unforeseen Message Reference ............................................ 40
`9.3.3
`Unknown or unforeseen message type ..................................................... 40
`9.3.4
`Non—semantical mandatory information element errors ............................... 40
`9.3.5
`Messages with semantically incorrect contents ......................................... 40
`
`10
`
`Timers .................................................................................................................................... 41
`
`Annex A (informative):
`
`Arrow diagrams .......................................................................................... 42
`
`Annex B (normative):
`
`SDL—description of the CM-layer .................................................................. 47
`
`Annex C (informative):
`
`Arrow diagrams .......................................................................................... 63
`
`SDL-description of the short message relay layer .......................................... 69
`Annex D (normative):
`D1
`Introduction ............................................................................................................... 69
`
`Annex E (informative):
`
`Cause definition .......................................................................................... 77
`
`Annex F (informative):
`
`LAPDm SAPI 3 handling for short message service ....................................... 83
`
`History ............................................................................................................................................. 90
`
`Google Ex. 1220, pg. 5
`
`Google Ex. 1220, pg. 5
`
`

`

`_
`Page 6
`GSM 04.11 Version 5.1.0 March 1996
`
`Blank page
`
`Google Ex. 1220, pg. 6
`
`Google Ex. 1220, pg. 6
`
`

`

`Page 7
`GSM 04.11 Version 5.1.0 March 1996
`
`Foreword
`
`This Global System for Mobile communications Technical Specification (GTS) has been produced by the
`Special Mobile Group (SMG) Technical Committee (TC) of the European Telecommunications Standards
`Institute (ETSI).
`
`This GTS defines the Short Message Service (SMS) support on mobile radio interface within the digital
`cellular telecommunications system (Phase 2/Phase 2+).
`
`This GTS is a TC-SMG approved GSM technical specification version 5, which contains GSM Phase 2+
`enhancements/features to the version 4 GSM technical specification. The ETS from which this Phase 2+
`GTS has evolved is Phase 2 GSM ETS 300 559 edition 3 (GSM 04.11 version 4.10.0).
`
`GTS are produced by TC-SMG to enable the GSM Phase 2+ specifications to become publicly available,
`prior
`to submission for
`the formal ETSI
`standards approval procedure to become European
`Telecommunications Standards (ETS). This ensures the earliest possible access to GSM Phase 2+
`specifications for all Manufacturers, Network operators and implementors of the Global System for Mobile
`communications.
`
`The contents of this GTS are subject to continuing work within TC-SMG and may change following formal
`TC-SMG approval. Should TC-SMG modify the contents of this GTS it will then be republished by ETSI
`with an identifying change of release date and an increase in version number as follows:
`
`Version 5.x.y
`
`where:
`
`y
`
`x
`
`the third digit
`specification;
`
`is incremented when editorial only changes have been incorporated in the
`
`the second digit is incremented for all other types of changes, i.e. technical enhancements,
`corrections, updates, etc.
`
`The specification from which this GTS has been derived was originally based on CEPT documentation,
`hence the presentation of this GTS may not be entirely in accordance with the ETS! rules.
`
`Reference is made within this GTS to GSM-TSs (note).
`
`NOTE:
`
`TC—SMG has produced documents which give the technical specifications for the
`implementation of the digital cellular telecommunications system. Historically,
`these
`documents have been identified as GSM Technical Specifications (GSM-TSs). These
`TSs may have subsequently become l-ETSs (Phase 1), or ETSs/ETSI Technical
`Reports (ETRs) (Phase 2). TC-SMG has also produced ETSI GSM TSs which give the
`technical specifications for the implementation of Phase 2+ enhancements of the digital
`cellular telecommunications system. These version 5.x.x GSM Technical Specifications
`may be referred to as GTSs.
`
`Google Ex. 1220, pg. 7
`
`Google Ex. 1220, pg. 7
`
`

`

`Page 8
`GSM 04.11 Version 5.1.0 March 1996
`
`Blank page
`
`Google Ex. 1220, pg. 8
`
`Google Ex. 1220, pg. 8
`
`

`

`Page 9
`GSM 04.11 Version 5.1.0 March 1996
`
`1
`
`Scope
`
`This Global System for Mobile communications Technical Specification (GTS) specifies the procedures
`used across the mobile radio interface by the signalling layer 3 function Short Message Control (SMC) and
`Short Message Relay function (SM-RL).
`
`1.1
`
`Normative references
`
`This GTS incorporates by dated and undated reference, provisions from other publications. These
`normative references are cited at the appropriate places in the text and the publications are listed
`hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply
`to this GTS only when incorporated in it by amendment or revision. For undated references, the latest
`edition of the publication referred to applies.
`
`H]
`
`B]
`
`[3
`
`M]
`
`[a
`
`[W
`
`GSM 01.04 (ETR 100): "Digital cellular telecommunication system (Phase 2);
`Abbreviations and acronyms“.
`
`telecommunication system
`cellular
`"Digital
`GSM 03.40 (ETS 300 536):
`(Phase 2); Technical realization of the Short Message Service (SMS) Point to
`Point (PP)".
`
`telecommunication system
`cellular
`"Digital
`GSM 04.06 (ETS 300 555):
`(Phase 2); Mobile Station — Base Station System (MS - BSS) interface Data
`Link (DL) layer specification".
`
`telecommunication system
`cellular
`"Digital
`GSM 04.07 (ETS 300 556):
`(Phase 2); Mobile radio interface signalling layer 3 General aspects“.
`
`telecommunication system
`cellular
`"Digital
`GSM 04.08 (ETS 300 557):
`(Phase 2); Mobile radio interface layer 3 specification".
`
`ISO 7498: "Information processing systems - Open Systems Interconnection —
`Basic Reference Model".
`
`1.2
`
`Abbreviations
`
`Abbreviations used in this specification are listed in GSM 01.04.
`
`Google Ex. 1220, pg. 9
`
`Google Ex. 1220, pg. 9
`
`

`

`Page 10
`GSM 04.11 Version 5.1.0 March 1996
`
`2
`
`Overview of Short Message Service (SMS) support
`
`The purpose of the Short Message Service is to provide the means to transfer messages between a GSM
`PLMN Mobile Station and a Short Message Entity via
`a Service Centre, as described in
`T8 GSM 03.40. The terms "MO" - Mobile Originating - and "MT" - Mobile Terminating - are used to
`indicate the direction in which the short message is sent.
`
`This Technical Specification describes the procedures necessary to support the Short Message Service
`between the MS and the MSC and vice versa, as described in TS GSM 03.40.
`
`The procedures are based on services provided by the Mobility Management sublayer as described in T8
`GSM O4.07/04.08.
`
`2.1
`
`Protocols and protocol architecture
`
`The hierarchical model shows the layer structure of the MSC and the MS.
`
`MSC
`
`SM-AL
`
`SM-TL
`
`SM—Ro
`
`
`
`MM—sublayer
`
`SM—RP protocol
`
`SM—CP protocol
`
`CM—sublayer
`
`RR—sublayer
`
`Figure 2.1/GSM 04.11: Protocol hierarchy
`
`The CM-sublayer, in terms of the Short Message Service Support, provides services to the Short Message
`Relay Layer.
`
`On the MS-side the Short Message Relay Layer provides services to the Short Message Transfer Layer.
`The Short Message Relay Layer is the upper layer on the network side (MSC), and the SM-user
`information elements are mapped to TCAP/MAP.
`
`The peer protocol between two SMC entities is denoted SM-CP, and between two SMR entities, SM-RP.
`
`Abbreviations:
`
`SM—AL
`SM-TL
`
`SM-RL
`SM-RP
`SMR
`
`CM-sub
`SM—CP
`SMC
`
`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)
`
`MM-sub : Mobility Management sublayer
`
`Google Ex. 1220, pg. 10
`
`Google Ex. 1220, pg. 10
`
`

`

`Page 11
`GSM 04.11 Version 5.1.0 March 1996
`
`RR-sub :
`
`Radio Resource Management sublayer
`
`2.2
`
`Use of channels
`
`The short message service will be supported by an SDCCH or SACCH, depending on the use of a TCH;
`
`—
`
`-
`
`-
`
`-
`
`When a TCH is not allocated, the short message service will use an SDCCH;
`
`if a TCH is allocated during a short message transaction on an SDCCH,
`transaction will stop and continue on the SACCH associated with the TCH;
`
`the short message
`
`If a TCH is allocated for the short message service, the short message service will use the
`associated SACCH;
`
`When an entity using a TCH finishes its transaction, the RR-sublayer may choose to continue an
`ongoing short message transfer on the SACCH, or optionally transfer it to an SDCCH.
`
`Table 2.1/GSM 04.11 summarizes the use of channels for the short message service. Arrows indicate
`changes of channel.
`
`Table 2.1IGSM 04.11: Channels used for short message transfer
`
`Channel dependency
`not allocated
`not allocated —> TCH allocated
`allocated
`allocated —> TCH not allocated
`
`
`
`Channel used
`SDCCH
`SDCCH —> SACCH
`SACCH
`SACCH —> SACCH opt. SDCCH
`
`2.3
`
`Layer 2 SAPI 3 handling
`
`General rule:
`
`The Radio Resource Management (RR ref. TS. GSM 04.08) in the Mobile Station and on the network side
`(i.e.
`in the BSC) shall establish the acknowledged mode of operation on SAPI 3 whenever needed,
`i.e.
`when a message requiring SAPl 3 transfer shall be transmitted.
`
`RR shall control the layer 2 also for SAPI 3, and keep knowledge of the mode.
`
`The network side may initiate release of the acknowledged mode for SAPI 3 either explicitly (by the use of
`DISC- and UA—frames, ref., TS GSM 04.06) or indirectly by channel release (ref. TS GSM 04.08).
`
`This means:
`
`-
`
`-
`
`-
`
`the Mobile Station side will initiate establishment of SAPI 3 acknowledged mode in the case of
`mobile originating short message transfer;
`
`initiate establishment of SAPI 3 acknowledged mode in the case of mobile
`the network side will
`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.
`
`Google Ex. 1220, pg. 11
`
`Google Ex. 1220, pg. 11
`
`

`

`Page 12
`GSM 04.11 Version 5.1.0 March 1996
`
`3
`
`3.1
`
`Service definition
`
`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 (lSO 7498) for Open
`Systems Interconnection.
`
`3.2
`
`Service provided by the CM-sublayer
`
`In order to support the Short Message Service, the CM—sublayer provides services to the Short Message
`Relay Layer.
`
`The CM-sublayer services are provided using layer specific functions and lower layer services offered to
`the CM-sublayer, controlled by short message service control entities called SMCs.
`
`An SMC entity in the MS communicates with an SMC entity in the MSC by means of a peer protocol, SM-
`CP (Short Message Service Control Protocol). The arrow diagrams in annex A give an overview of the
`messaging on the CM-sublayer during a short message transfer.
`
`A mobile station supporting the short message service shall have a minimum of two SMC entities. This
`enables the MS to receive MT messages during an M0 message transfer.
`
`To ensure that an MS having the minimum of two 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
`section 5.4.
`
`The MSC shall have a minimum of two SMC entities available during an MT message transfer to a mobile
`station, one being reserved for M0 message transfer.
`In an M0 message transfer, the MSC shall have
`one SMC entity reserved for handling of an MT message.
`
`Google Ex. 1220, pg. 12
`
`Google Ex. 1220, pg. 12
`
`

`

`Page 13
`GSM 04.11 Version 5.1.0 March 1996
`
`3.2.1
`
`Definition of primitives on the MS side
`
`This section defines the service primitives used on the MS side. Table 3.1/GSM 04.11 gives an overview
`of the service primitives and main parameter linked to the primitives. All necessary control parameters to
`be used in the short message service are defined in section 7. All MNSMS service primitives defined in this
`section are passed to an SMC-entity.
`
`Table 3.1IGSM 04.11: MNSMS service primitives on the MS-side
`
`
`
`
`
`
`
`
`
`SERVICE PRIMITIVES
`
`
`
`
`
`PARAMETER
`
`MNSMS-DA"A-
`
`
`
`MNSMS-ES"—
`
`Req
`
`Ind
`
`Req
`
`Ind
`
`Ind
`
`Req
`
`MO RPDU
`MT RPDU
`
`
`
`
`
`
`
`
`
`
`
`
`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 user information element being the RPDU, and
`The SMC entity forms the CP—DATA message,
`transfers the message by means of the lower layer services.
`
`NOTE:
`
`the SMR entity typically returns the
`reception of an incoming RP-DATA,
`After
`acknowledgement RP-ACK, or an error indication. RP-ERROR, to the Service Centre.
`
`3.2.1.3
`
`MNSMS-DATA-INDication
`
`An indication used by the SMC entity to pass the user information element (RPDU) of a received CP-DATA
`message to SM-RL.
`
`NOTE:
`
`The RPDU is typically an RP—ACK or an RP-ERROR. Normally this service is used to
`report the outcome of either a MO message transfer attempt or a mobile station
`memory available notification attempt.
`
`3.2.1.4
`
`MNSMS-ESTainsh-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 of the CP-DATA message containing the RPDU; and
`
`Google Ex. 1220, pg. 13
`
`Google Ex. 1220, pg. 13
`
`

`

`Page 14
`GSM 04.11 Version 5.1.0 March 1996
`
`-
`
`passing of CP-DATA to the MM-sublayer.
`
`3.2.1.5
`
`MNSMS-ESTablish-lNDication
`
`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 of the establishment of the CM-connection for this SMR entity.
`
`3.2.1.6
`
`MNSMS-ERROR-INDication
`
`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 of this 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 of the associated CM and MM—connections.
`
`3.2.2
`
`Definition of primitives on the network side
`
`This section defines the service primitives used on the network side.
`
`Table 3.2/GSM 04.11 gives an overview of the service primitives and linked main parameter. All MNSMS
`service primitives defined in this section are passed to an SMC—entity.
`
`Table 3.2IGSM 04.11: MNSMS service primitives on the network side
`
`
`
`
`
`
`
`
`
`SERVICE PRIMITIVES
`
`
`
`PARAMETER
`
`MNSMS—DATA-
`
`
`MNSMS-EST-
`
`MNSMS-ERROR—
`
`MO RPDU
`
`
`
`MO RPDU
`
`Cause
`
`eq
`
`
`
`
`
`
`
`
`
`
`3.2.2.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, it may form and send the CP-ERROR message to release
`the connection. Irrespective of whether or not the CP-ERROR message was sent, the CM-sublayer shall
`then release the lower layer services.
`
`3.2.2.2
`
`MNSMS-DATA-REQuest
`
`A request from an SMR entity to send a RPDU on the established CM-connection.
`
`the user information element being the RPDU, and
`The SMC entity forms the CP-DATA message,
`transfers the message by means of the lower layer services.
`
`Google Ex. 1220, pg. 14
`
`Google Ex. 1220, pg. 14
`
`

`

`Page 15
`GSM 04.11 Version 5.1.0 March 1996
`
`NOTE:
`
`After reception of an incoming RP—DATA or RP-SMMA the RPDU typically returns the
`acknowledgement, RP-ACK, or an error indication RP-ERROR, to the Mobile Station.
`
`3.2.2.3
`
`MNSMS-DATA-INDication
`
`An indication used by the SMC entity to pass the user information element (RPDU) of a received CP-DATA
`message to SM-RL.
`
`NOTE:
`
`The RPDU is typically an RP—ACK or an RP-ERROR. Normally this is used to report the
`outcome of a MT messaging attempt.
`
`3.2.2.4
`
`MNSMS-ESTablish-REQuest
`
`A request from an SMR entity to transmit a RPDU, containing the SM-user information element; it implies
`the:
`
`-
`
`-
`
`-
`
`establishment of a CM-connection for this SMR entity;
`
`forming of the CP-DATA message containing the RPDU; and
`
`passing of CP-DATA to the MM-sublayer.
`
`3.2.2.5
`
`MNSMS-ESTainsh-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 of the establishment of the CM—connection for this SMR entity.
`
`3.2.2.6
`
`MNSMS-ERROR-lNDication
`
`An indication used by the SMC entity to pass error information to SM-RL. The error information may be
`local or