1、GSM 04.1 1 March 1996 Version 5.1.0 Source: ETSI TC-SMG Reference: TS/SMG-030411 QR ICs: 33.060.50 . Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM) GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS Digital cellular telecommunication system (Phase 2+); Poin
2、t-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-O6921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400:
3、 c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat Qetsi.fr Tel.: +33 92 94 42 O0 - Fax: +33 93 65 47 16 Copyright Notification: No pari may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O Europea
4、n Telecommunications Standards Institute 1996. All rights resewed. * ETSI *GSM*:OLi*LL Yb E 3480855 0093932 402 Page 2 GSM 04.1 1 Version 5.1 .O March 1996 Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur.
5、If you have comments concerning its accuracy, please write to “ETSI Editing and Committee Support Dept.“ at the address shown on the title page. . 0093933 . = Page 3 GSM 04.11 Version 5.1.0 March 1996 Contents Foreword . 7 1 Scope 9 1.1 Normative references 9 1.2 Abbreviations 9 2 Overview of Short
6、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 3 Service definition . 12 3.1 General 12 3.2 Service provided by the CM-sublayer 12 Definition of primitives on the MS side 13 3.2.1.1 MNSMS-ABORT-REQuest 13 3.2.1.2 MN
7、SMS-DATA-REQuest . 13 3.2.1.3 MNSMS-DATA-INDication . 13 3.2.1.4 MNSMS.ESTablish.REQuest . 13 3.2.1.5 MNSMS-ESTablish-INDication . 14 3.2.1.6 MNSMS-ERROR-INDication 14 3.2.1.7 MNSMS-RELease-REQuest 14 3.2.2.1 MNSMS-ABORT-REQuest 14 3.2.2.2 MNSMS-DATA-REQuest . 14 3.2.2.3 MNSMS-DATA-INDication . 15 3
8、.2.2.4 MNSMS-ESTablish-REQuest . 15 3.2.2.5 MNSMS-ESTablish-INDication . 15 3.2.2.6 MNSMS-ERROR-INDication 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-INDication . 16 3.3.1.3 SM-R
9、L-MEMORY-AVAILABLE-REQuest . 16 3.3.1.4 SM-RL-REPORT-REQest . 17 3.3.1 -5 SM-RL-REPORT-INDication 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-INDication . 17 3.3.2.3 SM-RL-MEMORY-AVAILABLE-INDication 17 3.3.2.4 SM-RL-REPORT-REQuest . 18 3.3.2
10、.5 SM-RL-REPORT-INDication 18 3.2.1 3.2.2 Definition of primitives on the network side . 14 3.3 3.3.2 4 Spare . 18 5 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 5.2.1.1.2
11、MO-MM-connection pending (State 1) . 19 5.2.1.1.3 MO-Wait for CP-ACK (State 2) . 19 MO-Idle (State O) . 19 5.2.1.2 5.2.2.2 5.2.1.1.4 MO-MMconnection established (State 3) 19 Mobile Terminating case 19 5.2.1.2.1 MT-Idle (State O) 19 5.2.1.2.2 MT-Wait for CP-ACK (State 2) 20 5.2.1.2.3 MT-MM-connection
12、 established (State 3) 20 SMC states at the network side of the radio interface . 20 5.2.2.1 Mobile Originating Case 20 5.2.2.1.1 MO-Idle (State O) . 20 5.2.2.1.2 MO-Wait for CP-ACK (State 2) . 20 5.2.2.1.3 MO-MMconnection established (State 3) 20 Mobile Terminating Case . 20 5.2.2.2.1 MT-Idle (Stat
13、e O) 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) 20 5.2.2.2.4 MT-MM-connection established (State 3) 20 5.2.2 5.3 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 2
14、2 5.3.4 Abnormal cases . 22 5.4 Concatenating short message or notification transfers 23 6.2.2 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 6.2.1.1 Idle (State O) 24 6.2.1.2 Wait for RP-ACK (State 1) 24 6.2.1.
15、3 Wait for RETRANS TIMER (State 4) 24 SMR-states at the network side of the radio interface . 24 6.2.2.1 Idle (State O) 24 6.2.2.2 Wait for RP-ACK (State 1) 24 6.2.2.3 Wait to send RP-ACK (State 3) . 25 Short Message Relay procedures . 25 6.3.1 TPDU relaying 25 6.3.2 spare . 26 6.3.3 Notification re
16、laying . 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 6.3.3.2 Network side 27 6.3.3.2.1 Idle state . 27 6.3.3.2.2 Wait to Send RP-ACK state 27 6.3.4 Abnormal cases . 27 6.3 7 Message functional definitions and conten
17、t 28 7.1 General 28 7.2 Messages for short message or notification transfer on CM . 28 7.2.1 CP-DATA . 28 7.2.2 CP-ACK . 29 7.2.3 CP-ERROR . 29 7.3.1 RP-DATA . 29 7.3 Messages for short message and notification transfer on SM-RL 29 RP-DATA (Network to Mobile Station) 29 RP-DATA (Mobile Station to Ne
18、twork) 30 7.3.1.1 7.3.1.2 7.3.2 RP-SMMA . 30 7.3.3 RP-ACK 30 7.3.4 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 Message type 31 8.1.4 8.1.4.1 CP-User data element . 32 8.1.
19、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 Other required information elements 32 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 addre
20、ss 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 General 38 CP Error Handling . 38 9.2.1 Message too short . 38 9.2.2 Unknown or unforeseen transaction identifier 38 9.2.3 Unknown or unforeseen message type
21、. 38 9.2.4 Non-semantical mandatoty information element errors . 39 9.2.5 Messages with semantically incorrect contents . 39 RP Error Handling . 39 9.3.1 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
22、errors . 40 9.3.5 Messages with semantically incorrect contents . 40 9.1 9.2 9.3 Message too short . 39 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 Annex D (normative): SDL-description of the s
23、hort message relay layer 69 D.1 Introduction . 69 Annex E (informative): Cause definition 17 Annex F (informative): LAPDm SAPI 3 handling for short message service . 83 History . 90 Page 6 GSM 04.1 1 Version 5.1 .O March 1996 Blank page ETSI *GSM*4.L1, 9b 3400855 0093937 T4 Page 7 GSM 04.1 1 Version
24、 5.1 .O 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
25、on mobile radio interface within the digital cellular telecommunications system (Phase Whase 2+). This GTS is a TC-SMG approved GSM technical specification version 5, which contains GSM Phase 2+ enhancementsfeatures to the version 4 GSM technical specification. The ETS from which this Phase 2+ GTS h
26、as evolved is Phase 2 GSM ETS 300 559 edition 3 (GSM 04.1 1 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 fornial ETSI standards approval procedure to become European Telecommunications Standards (ETS).
27、 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. S
28、hould 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 the third digit is incremented when editorial only changes have been incorporated in the specif ication; x
29、the second digit is incremented for all other types of changes, .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 ETSI
30、 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-T
31、Ss). These TSs may have subsequently become I-ETSs (Phase l), 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 versio
32、n 5.x.x GSM Technical Specifications may be referred to as GTSs. ETSI *GSM*OLn*L-Ii 4h W 3400855 0093938 920 M Page 8 GSM 04.1 1 Version 5.1 .O March 1996 Blank page 1 Scope This Global System for Mobile communications Technical Specification (GTS) specifies the procedures used across the mobile rad
33、io 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 t
34、he 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. 131
35、141 151 GSM 01.04 (ETR 100): “Digital cellular telecommunication system (Phase 2); Abbreviations and acronyms“. GSM 03.40 (ETS 300 536): “Digital cellular telecommunication system (Phase 2); Technical realization of the Short Message Service (SMS) Point to Point (PP)“. _ GSM 04.06 (ETS 300 555): “Di
36、gital cellular telecommunication system (Phase 2); Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification“. GSM 04.07 (ETS 300 556): “Digital cellular telecommunication system (Phase 2); Mobile radio interface signalling layer 3 General aspects“. GSM 04.08 (ETS
37、300 557): “Digital cellular telecommunication system (Phase 2); Mobile radio interface layer 3 specification“. IS0 7498: “Information processing systems - Open Systems Interconnection - Basic Reference Model“. 1.2 Abbreviations Abbreviations used in this specification are listed in GSM 01.04. ETSI x
38、GSV*04.aiL 96 3400855 0073940 587 Page 10 GSM 04.1 1 Version 5.1 .O 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
39、 described fl TS 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
40、 vice versa, as described in TS GSM 03.40. The procedures are based on services provided by the Mobility Management sublayer as described in TS GSM 04.07/04.08. 2.1 Protocols and protocol architecture The hierarchical model shows the layer structure of the MSC and the MS. -_ SM-AL SM-TL SM-RL CM-sub
41、layer MM-sublayer RR-sublayer r-i t-1 . SM-RP protocol SM-CP protocol - -I Figure 2.1IGSM 04.1 1 : 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
42、the Short Message Transfer Layer. The Short Message Relay Layer is the upper layer on the network side (MSC), and the SM-user information elements are mapped to TCAP/MAP. The peer protocol between two SMC entities is denoted SM-CP, and between two SMR entities, SM-RP. Abbreviations: SM-AL Short Mess
43、age Application Layer SM-TL Short Message Transfer Layer SM-RL Short Message Relay Layer SM-RP Short Message Relay Protocol SMR Short Message Relay (entity) CM-sub Connection Management sublayer SM-CP Short Message Control Protocol SMC Short Message Control (entity) MM-sub : Mobility Management subl
44、ayer Page 11 GSM 04.1 1 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
45、allocated during a short message transaction on an SDCCH, the short message transaction will stop and continue on the SACCH associated with the TCH; - If a TCH is allocated for the short message service, the short message service will use the associated SACCH; - When an entity using a TCH finishes i
46、ts 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.1 1 summarizes the use of chhnels for the- short message service. Arrows indicate changes of channel. Table S.l/GSM 04.1 1 : Channels used fo
47、r short message transfer I Channel dependency I Channel used I 7 SDCCH TCH not allocated - TCH allocated SDCCH - SACCH TCH not allocated I TCH allocated - TCH not allocated I SACCH - SACCH opt. SDCCH TCH allocated I 2.3 Layer 2 SAPI 3 handling General nile: The Radio Resource Management (RR ref. TS.
48、 GSM 04.08) in the Mobile Station and on the network side (.e. in the BSC) shall establish the acknowledged mode of operation on SAPI 3 whenever needed, .e. when a message requiring SAPI 3 transfer shall be transmitted. RR shall control the layer 2 also for SAPI 3, and keep knowledge of the mode. Th
49、e network side may initiate release of the acknowledged mode for SAPI 3 either explicitly (by the use of DISG- 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; - the network side will initiate establishment of SAPI 3 acknowledged mode in the case of mobile terminating short message transfer; - the network side may choose to keep the channel and the acknowledged mode of operation t
