1、STD-ETSI TR 101 635-ENGL 1777 W 3400855 04403b3 T34 ETSI TR 1 O1 635 V7.0.0 (1999-08) Technica f Report Digital cellular telecommunications system (Phase 2+); Example protocol stacks for interconnecting Service Centre(s) (SC) and Mobile-services Switching Centre(s) (MSC) (GSM 03.47 version 7.0.0 Rel
2、ease 1998) (GSM 03.47 version 7.0.0 Release 1998) 2 ETSI TR 101 635 V7.0.0 (1999-08) Reference RTR/SMG-04034707 (f5003i04. PDF) Keywords Digital cellular telecommunications system, Global System for Mobile communications (GSM) ETSI Postal address F-O6921 Sophia Antipolis Cedex - FRANCE Office addres
3、s 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Siret No 348 623 562 O001 7 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) No 7803/88 Tel,: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Internet secretariat 8 etsi.fr Individual copies of this ETSI deliv
4、erable can be downloaded from http:/w.etsi.org If you find errors in the present document, send your comment to: editoretsi.fr Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
5、 O European Telecommunications Standards Institute 1999. All rights reserved. (GSM 03.47 version 7.0.0 Release 1998) 3 ETSI TR 1 O1 635 V7.0.0 (1 999-08) Contents Intellectual Property Rights . 4 Foreword 4 1 1.2 1.3 2 2.1 2.2 2.3 2.3.1 2.3.2 2.4 2.5 3 3.1 3.2 3.3 3.3.1 3.3.2 3.4 3.5 4 4.1 4.2 4.2.1
6、 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.2.7 4.3 Scope 5 References Abbreviations . . 6 An OS1 Protocol Stack For Interconnecting SCs and MSCs . 6 Service elements on the application layer 7 Detailed specification of the SMRSE services 7 Application rules for avoiding collisions between SMR-UNBIND and the o
7、ther SMRSE operations 14 Application rule set 1 Semi-permanent symmetric connection . 15 Application rule set 2 Transient asymmetric connection 15 Timing terminology . 16 Error Cause Mapping . 17 A Protocol Stack which utilises an Application-Network Layer convergence function for interconnecting SC
8、s and MSCs . 18 SMRSE Defini tion . 18 ASN1 Specification . . 20 Application Rules for Avoidance of Collision of SMRSE Operations 23 Semi-permanent Connections . 23 Transient Connection . . 23 phases 23 SS7 Protocol Stacks . 24 Non Support of 128 bytes of NS-user-data in Network Connection and Netwo
9、rk Connection Release Error Cause Mapping 24 Introduction . 24 Application Layer Protocol SMS-MAP . . 24 Introduction 24 Protocol Stack 25 SMS-MAP Version Handling . 25 Operations 25 SMS-MAP SIGNALLING SEQUENCES . 34 Errors . 37 SMS-MAP Parameter Data Types 40 Support of Application Layer Specified
10、by section 2 of GSM 03.47 . 42 Annex A (informative): Change Request History . 43 History 44 (GSM 03.47 version 7.0.0 Release 1998) 4 ETSI TR 1 O1 635 V7.0.0 (1 999-08) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The in
11、formation pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in SR 000 3 14: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notijied to ETSI in respect ofETSf srandards“, which is available free of cha
12、rge from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/www.etsi.org/ipr). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in SR O00 3
13、14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by the Special Mobile Group (SMG). The present document describes three approaches to the specification of protocol stacks of commu
14、nication protocols for the purpose of relaying short messages and alerts between Short Message Service Centres and GatewayAnterworking MSCs (GMSC) for the Short Message Service (SMS) within the digital cellular telecommunication system. The present document is an informative document resulting from
15、SMG studies which are related to the digital cellular telecommunication system. The present document is used to publish material which is of an informative nature, relating to the use or the application of ENS and is not suitable for formai adoption as an EN. The specification from which the present
16、 document has been derived was originally based on CEFT documentation, hence the presentation of the present document may not be entirely in accordance with the ETSIPNE rules. The contents of the present document is subject to continuing work within SMG and may change following formal SMG approval.
17、Should SMG modify the contents of the present document it will be re-released with an identifying change of release date and an increase in version number as follows: Version 7.x.y where: 7 indicates Release 1998 of GSM Phase 2+ x the second digit is incremented for all changes of substance, i.e. te
18、chnical enhancements, corrections, updates, etc. y the third digit is incremented when editorial only changes have been incorporated in the specification. STDmETSI TR 101 635-ENGL 1999 = 3400855 04403bb 7V3 m _ (GSM 03.47 version 7.0.0 Release 1998) 5 ETSI TR 1 O1 635 V7.0.0 (1 999-08) 1 Scope No ma
19、ndatory protocol between the Service Centre (SC) and the Mobile Switching Centre (MSC) below the transfer layer is specified by GSM; this is a matter of agreement between SC and PLMN operators. The present document specifies three approaches to the specification of protocol stacks of communication p
20、rotocols for the purpose of relaying short messages and alerts between Short Message Service Centres and Gatewayhterworking MSCs (GMSC) for the Short Message Service (SMS). One approach is based upon use of the complete OS1 reference model (see X.200), another approach is based upon the use of only
21、the lower three OS1 layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700). Alternative protocol stacks are specified via ASN.l encoding rules (see X.208 and X.209). These alternative protocol stacks are examples for the implementation of the Short Message Re
22、lay Layer (SM-RL). The requirements placed upon the Short Message Relay Layer are briefly described in clause 9 of GSM 03.40. Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantageddisadvantages of implementation is intentionally om
23、itted. 1.2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, s
24、ubsequent revisions do not apply. For a non-specific reference, the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. For this Release 1998 document, references to GSM documents are for Release 1998 vers
25、ions (version 7.x.y). il Pl GSM 01.04: “Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms“. GSM 03.40: “Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point-to-Point (PP)“. GSM 09.02: “Digital cellular te
26、lecommunications system (Phase 2+); Mobile Application Part (MAP) specification“. GSM 12.20: “Digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages“. CCITT Recommendation E. 164: “Numbering plan for the ISDN era“. CCITT Recommendation Q.700: “Introducti
27、on to CCITT Signalling System No.7“. CCITT Recommendation Q.93 1 : Integrated services digital network.(ISDN) User-Network interface layer 3 specification for basic control“. CCITT Recommendation 4.932: “Generic procedures for the control of ISDN supplementary services“. 31 41 i51 i61 71 i81 191 lo1
28、 CCITT Recommendation 4.941 : “ISDN user-network interface protocol profile for management“. CCITT Recommendation Q. 1400: “Architecture framework for the development of signalling and organisation, administration and maintenance protocols using OS1 concepts“. CCITT Recommendation X.2 ( 1988): “Inte
29、rnational data transmission services and optional user facilities in public data networks and ISDNs“. ill STDSETSI TR 101 635-ENGL 1999 3400855 0440367 b8T - (GSM 03.47 version 7.0.0 Release 1998) 6 ETSI TR 1 O1 635 V7.0.0 (1 999-08) CCITT Recommendation X.200: “Reference Model of Open Systems Inter
30、connection for CCITT Applications“. CCITT Recommendation X.208: “Specification of basic encoding rules for Abstract Syntax Notation One (ASN. 1)“. CCITT Recommendation X.209: “Specification of Abstract Syntax Notation One (ASN. 1)“. CCITT Recommendation X.2 15: “Session service definition for open s
31、ystems interconnection for CCITT applications“. CCITT Recommendation X.216: “Presentation service definition for open systems interconnection for CCITT applications“. CCITT Recommendation X.217: “Association control service definition for open systems interconnection for CCITT applications“. CCITT R
32、ecommendation X.219: “ Remote operations: model, notation and service definition“. CCITT Recommendation X.223: “Use of X.25 to provide the OS1 connection-mode network service for CCITT Applications“. CCITT Recommendation X.224: “Transport protocol specification for Open Systems Interconnection for C
33、CITT Applications“. CCITT Recommendation X.225: “Session protocol specification for Open Systems Interconnection for CCITT Applications“. CCITT Recommendation X.226: “Presentation protocol specification for Open Systems Interconnection for CCITT Applications“. CCITT Recommendation X.227: “Informatio
34、n technology - Open Systems Interconnection - protocol specification for the association“. CCITT Recommendation X.229: “Remote operations Protocol specification“. Abbreviations Abbreviations used in the present document are listed in GSM 01.04. 2 An OS Protocol Stack For Interconnecting SCs and MSCs
35、 This clause specifies a stack of communication protocols in terms of the OS1 Reference Model (see X.20) and therefore makes use of all seven layers for the purpose of relaying short messages and alerts between SC and MSC for the Short Message Service. The SMS application layer (layer 7) is mapped t
36、o the Presentation Layer via ACSE (see X.217 and X.227) and ROSE (see X.219 and X.229). Only the Kernel functional unit of the Presentation Layer is used. Only Kernel and Duplex functional units are used in the Session Layer (see X.215 and X.225). STD-ETSI TR 303 b35-ENGL 1999 = 3400855 O440368 5Lb
37、(GSM 03.47 version 7.0.0 Release 1998) 7 ETSI TR 1 O1 635 V7.0.0 (1999-08) 2.1 Service elements on the application layer An association (class 3) between SMRSEs is formed via ACSE and ROSE operations (class 2 and 5) are used to implement the Short Message Relay Layer described in clause 9 of GSM 03.
38、40. This results into a asynchronous symmetric situation where both (the application entity in) the SC and (the application entity in) the MSC can invoke a SMRSE operation at any time. The new SMRSE service element is first defined in this section, and then specified in ASN. 1 notation in section 2.
39、2. SMRSE definition This service element defines the following services: SMR-BIND This operation must be invoked by that party which established the application association; only after that may the remaining SMRSE services be used. This operation reports either success or failure (result or error).
40、SMR-MO-DATA This operation may be invoked by the application entity in the MSC; it is used to relay one SMS transfer layer PDU from the IWMSC to the SC. This operation reports either success or failure. SMR-MT-DATAThis operation may be invoked by the application entity in the SC; it is used to relay
41、 one SMS transfer layer PDU from the SC to the GMSC, to be further relayed to the MS addressed. This operation reports either success or failure, after the full relay attempt to the MS. This operation may be invoked by the application entity in the MSC. It is used as the GMSC-to-SC indication of the
42、 fact that an MS which was previously unattainable has recovered operation. This operation does not report any outcome. SMR-UNBIND Thi operation must be invoked by that party which invoked the SMR-BIND operation, as the last SMR-ALERT SM x SE operation before releasing the application association. T
43、his operation reports success only. Of the services defined above, SMR-MO-DATA and SMR-MT-DATA semantically mean the relay of short messages across the SC-MSC-connection; SMR-ALERT similarly implements the alerting operation. The SMR-BIND service is used to exchange identifications, passwords, etc.,
44、 and in order to negotiate the usage of the other services. The SMR- UNBIND service prepares for the release of the application association. 2.2 Detailed specification of the SMRSE services On the following pages, the new SMRSE service element is specified with the ASN. 1 notation, together with the
45、 entire SM-RL protocol. The Abstract Syntax Notation of the Short Message Relay Service Element SMRSE NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name “etsi“ is adopted from GSM 12.20 but the value 040 is arbitrary, and the last three arcs are allocated in this m
46、odule. 1st module of 3: SMS-UsefulDefinitions SMS-usefulDefinitions is0 identified-organization etci(040) mobile-domain(0) gsm-rnessaging(4) gcm-smslil0) usefulDefinitions(0) 1 DEFINITIONS IMPLICIT TAGS STD-ETSI TR 101 635-ENGL 1999 m 3400855 04403b9 452 m (GSM 03.47 version 7.0.0 Release 1998) 8 ET
47、SI TR 101 635 V7.0.0 (1999-08) : := BEGIN EXPORTS id-ot-SC, id-ot-MSC, id-port, id-ac-so, id-ac-st, id-SMRSE, id-as-CMRSE; IMPORTS ID := OBJECT IDENTIFIER root for all sms allocations mobile-domain ID := iso identified-organization etsi40) mobile-domain(0) I gsm-messaging ID := mobile-domain gsm-mes
48、saging(4) gsm-smsl ID := gsm-messaging gsm-smsll0) categories id-mod ID := ( gsm-messaging 1 1 - modules id-ot ID := ( gsm-messaging 2 1 - object type id-pt ID := ( gsm-messaging 3 1 - port types id-ac ID := ( gsm-messaging 4 1 - appi. contexts id-ase ID := ( gsm-messaging 5 1 - ASES id-as ID := gcm
49、-messaging 6 1 - abstract syntaxes modules usefulDefinitions ID := ( gcm-smsl O ) relayprotocol ID := ( gsm-smsl 1 ) relayAbstractService ID := 1. gsm-smsl 2 1 object types id-ot-SC ID := ( id-ot O ) id-ot-MSC ID := ( id-ot 1 I port types id-port ID := ( id-pt O ) application contexts id-ac-so ID := id-ac O 1 - SC does BIND id-ac-st ID := ( id-ac 1 I - MSC does BIND application service elements id-SMRSE ID := ( id-ase O 1 abstract syntaxes id-as-SMRSE ID := id-as O . i _. i END 2nd module of 3 Relay Abstractser
