ETSI GSM 03 47-1994 European Digital Cellular Telecommunications System (Phase 2) Example Protocol Stacks for Interconnecting Service Centre(s) (SC) and Mobile-Services Switching C.pdf

1、ETSI GSM*O3.47 94 3400855 000430b bL9 Released: October 1994 GSM 03.47 Version: 4.3.0 Date: 7 October, 1994 Source: ETSI TC-SMG Reference: GSM 03.47 UDC: 621.396.21 Key words: European digital cellular telecommunications system, Global System for Mobile communications (GSM) European digital cellular

2、 telecommunication system (Phase 2); Example protocol stacks for interconnecting Service Centre(s) (SC) and Mobile-services Switching Centre(s) (MSC) (GSM 03.47) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address

3、: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 94 42 O0 - Fax: + 33 93 65 47 16 European Telecommunications Standards Institute 1993. All rights reserved. No part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on r

4、eproduction extend to all media in which the information may be embodied. ETSI GSM803.47 94 W 3400855 0004307 555 W Page 2 GSM 03.47 version 4.3.0 Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you ha

5、ve comments concerning its accuracy, please write to “ETSI Editing and Standards Approval Dept.“ at the address shown on the title page. ETSI GSM*O3-47 74 3400855 0004308 471 . Page 3 GSM 03.47 version 4.3.0 Contents Foreword . 5 1.1 Scope . 7 1.2 References 7 1.3 Definitions and abbreviations . 8 2

6、 An OS1 Protocol Stack For Interconnecting SCs and MSCs . 8 2.1 Service elements on the application layer . 9 2.2 Detailed specification of the SMRSE services . 10 2.3 Application rules for avoiding collisions between SMR-UNBIND and the other SMRSE operations 23 2.3.1 Application rule set 1 Semi-per

7、manent symmetric connection . 23 2.3.2 Application rule set 2 Transient asymmetric connection . 23 2.4 Timing terminology . 24 2.5 Error Cause Mapping 25 3 A Protocol Stack Which Utilises an Application-Network Layer Convergence Function For Interconnecting SCs and MSCs . 26 3.1 SMRSE Definition . 2

8、6 3.2 ASN 1 Specification 28 3.3 Application Rules for Avoidance of Collision of SMRSE Operations 33 3.3.1 Semi-permanent Connections 34 3.3.2 Transient Connection . 34 Network Connection Release phases . 34 Error Cause Mapping 35 3.4 Non Support of 128 bytes of NS-user-data in Network Connection an

9、d 3.5 4 SS7 Protocol Stacks 36 4.1 Introduction . 36 4.2 4.2.1 Introduction 36 4.2.2 Protocol Stack 36 4.2.3 SMS-MAP Version Handling 36 4.2.4 Operations . 37 4.2.5 SMS-MAP SIGNALLING SEQUENCES . 46 4.2.6 Errors 50 4.2.7 SMS-MAP Parameter Data Types . 53 Support of Application Layer Specified by sec

10、tion 2 of GSM 03.47 . 55 Application Layer Protocol SMS.MAP 36 4.3 Number of pages: . ETSI GSM*O3-47 94 m 3400855 0004309 328 m Page 5 GSM 03.47 version 4.3.0 Foreword This section is reserved for the ETR version of this document. Previous page is blank ETSI GSM*O3.47 94 = 3400855 0004310 OUT Page 7

11、 GSM 03.47 version 4.3.0 1.1 Scope No mandatory 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. This report specifies three approaches to the specification of pro

12、tocol stacks of communication protocols for the purpose of relaying short messages and alerts between Short Message Service Centres and Gateway/lnterworking MSCs (GMSC) for the Short Message Service (SMS). One approach is based upon use of the complete OS1 reference model (see X.200), another approa

13、ch is based upon the use of only 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.1 encoding rules (see X.208 and X.2091. These alternative protocol stacks are examples for the imple

14、mentation of the Short Message Relay Layer (SM- RL). The requirements placed upon the Short Message Relay Layer are briefly described in Section 9 of GSM 03.40. Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantages/disadvantages o

15、f implementation is intentionally omitted. 1.2 References This ETR 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 a

16、mendments to or revisions of any of these publications apply to this ETR only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. i1 1 i21 i31 I41 GSM O1 .O4 : “European digital cellular telecommunication system (Phase

17、2); Definitions, abbreviations and acronyms“. GSM 03.40 : “European digital cellular telecommunication system (Phase 2); Technical realization of the Short Message Service (SMS) Point to Point (PP)“. GSM 09.02 : “European digital cellular telecommunication system (Phase 2); Mobile Application Part (

18、MAP) specification“. GSM 12.20 : “European digital cellular telecommunication system (Phase 2); Network Management (NM) procedures and messages“. i51 CCITT Recommendation E.164: “Numbering plan for the ISDN era“. i61 i71 i81 i91 CCITT Recommendation Q.700: “Introduction to CCITT Signalling System No

19、.7“. CCITT Recommendation Q.931: Integrated services digital network.(lSDN) User-Network interface layer 3 specification for basic control“. CCITT Recommendation 0.932: “Generic procedures for the control of ISDN supplementary services“. CCITT Recommendation Q.941: “ISDN user-network interface proto

20、col profile for management“. CCITT Recommendation Q. 1400: “Architecture framework for the deveiopement of signalling and organisation, administration and maintenance protocols using OS1 concepts“. Previous page is blank Page 8 GSM 03.47 version 4.3.0 i111 11 21 i1 31 i1 41 i1 51 i1 61 i1 71 i181 i2

21、01 i21 I i221 i231 CCITT Recommendation X.2 (1 988): “International data transmission services and optional user facilities in public data networks and ISDNs“. CCITT Recommendation X.200: “Reference Model of Open Systems Interconnection for CCITT Applications“. CCITT Recommendation X.208: “Specifica

22、tion of basic encoding rules for Abstract Syntax Notation One (ASN. 1 1 “ . CCITT Recommendation X.209: “Specification of Abstract Syntax Notation One (ASN.1)“. CCITT Recommendation X.215: “Session service definition for open systems interconnection for CCITT applications“. CCITT Recommendation X.2

23、16: “Presentation service definition for open systems interconnection for CCITT applications“. CCITT Recommendation X.2 17: “Association control service definition for open systems interconnection for CCITT applications“. CCITT Recommendation X.219: “ Remote operations: model, notation and service d

24、efinition“. , 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 CCITT Applications“. CCITT Recommendation X.225: “Session protocol sp

25、ecification 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: “Information technology - Open Systems Interconnection - protocol specification

26、 for the association“. i241 CCITT Recommendation X.229: “Remote operations Protocol specification“. 1.3 Definitions and abbreviations Abbreviations used in this report are listed in GSM 01.04. 2 An OS1 Protocol Stack For Interconnecting SCs and MSCs This section specifies a stack of communication pr

27、otocols in terms of the OS1 Reference Model (see X.200) 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 to the Presentation Layer via ACSE (see X.217 and

28、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). ETSI GSM+03.47 74 3400855 0004312 912 Page 9 GSM 03.47 version 4.3.0 2.1 Service elements on the appl

29、ication 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 Section 9 of GSM 03.40. This results into a asynchronous symmetric situation where both (the application entity in) the SC and

30、 (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.l notation in section 2.2. SMRSE definition This service element defines the following services: SMR-BIND This operation must be in

31、voked 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). SMR-MO-DATA This operation may be invoked by the application entity in the MSC; it is used to relay one SMS

32、 transfer layer PDU from the IWMSC to the SC. This operation reports either success or failure. SM R-MT-DATA SMR-ALERT This operation may be invoked by the application entity in the SC; it is used to relay one SMS transfer layer PDU from the SC to the GMSC, to be further relayed to the MS addressed.

33、 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 fact that an MS which was previously unattainable has recovered operation. This operation does

34、 not report any outcome. SMR-UNBIND This operation must be invoked by that party which invoked the SMR-BIND operation, as the last SMRSE operation before releasing the application association. This operation reports success only. Of the services defined above, SMR-MO-DATA and SMR-MT-DATA semanticall

35、y 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., and in order to negotiate the usage of the other services. The SMR-UNBIND service prepares for the releas

36、e of the application association. ETSI GSM*O3-47 94 = 3400855 0004313 859 Page 10 GSM 03.47 version 4.3.0 2.2 Detailed specification of the SMRSE services On the following pages, the new SMRSE service element is specified with the ASN.l notation, together with the entire SM-RL protocol. The Abstract

37、 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 this module. -._ 1st module of 3: SMS-UsefulD

38、efinitions SMS-usefulDefinitions is0 identified-organization etsi(040) mobile-domain(0) gsm-messaging(4) DEFINITIONS gsm-smsl(10) usefulDefinitions(0) IMPLICIT TAGS - - BEGIN EXPORTS id-ot-SC, id-ot-MSC, id-port, id-ac-so, id-ac-st, id-SMRSE, id-as-SMRSE; IMPORTS ID : = OBJECT IDENTIFIER root for al

39、l sms allocations mobile-domain ID : = so identified-organization etsi(40) mobile-domain(01 gsm-messaging ID : = mobile-domain gsm-messaging(4) gsm-smsl ID : = gsm-messaging gsm-smsl(1 O) categories id-mod id-pt id-ac id-ase id-as ID := gsm-messaging 1 - modules ID : = gsm-messaging 3 - port types I

40、D : = gsm-messaging 4 - appl. contexts ID := gsm-messaging 5 - ASES ID : = gsm-messaging 6 - abstract syntaxes id-Ot ID L - gsm-messaging 2 - object type ETSI GSMx03.47 94 3400855 0004314 795 m Page 11 GSM 03.47 version 4.3.0 - modules usefulDefinitions ID : = gsm-smsl O relay Protocol relayAbstract

41、Service ID := gsm-smsl 1 ID := gsm-smsl 2 - object types id-ot-SC id-ot-MSC ID : = id-ot O ID := id-Ot 1 - port types - application contexts id-ac-so ID : = id-ac O - SC does BIND id-ac-st ID := id-ac 1 - MSC does BIND - application service elements id-SMRSE ID := id-ase O - abstract syntaxes id-as-

42、SMRSE ID : = id-as O END ETSI GSMa03-47 94 M 3irOOB.55 0004335 621 M Page 12 GSM 03.47 version 4.3.0 2nd module of 3 RelayAbstractService RelayAbstractService is0 identified-organization etsi(040) mobile-domainlo) gsm-messaging(4) DEFINITIONS gsm-smsl(1 O) relayAbstractService(2) IMPLICIT TAGS - - B

43、EGIN - EXPORTS everything IMPORTS BIND, UNBIND FROM Remote-Operations-Notation joint-iso-ccitt remote-operations(4) notation(0) OBJECT, PORT, ABSTRACT-BIND, ABSTRACT-UNBIND, ABSTRACT-OPERATION, ABSTRACT-ERROR FROM AbstractServiceNotation joint-iso-ccitt mhs-motis(6) asdc(2) modules(0) notation( 1) i

44、d-ot-SC, id-ot-MSC, id-port FROM SMS-UsefulDefinitions is0 identified-organization etsi(O40) mobile-domain(0) gsm-messaging(4) gsm- smsl(10) usefulDefinitions(0) ; - upper bound settings ub-operator-name-length INTEGER : = 20 ub-agreem-name-length INTEGER : = 20 ub-X121Address-length INTEGER : = 15

45、ub-password-length INTEGER := 20 ETSI GSMx03.47 94 m 3400855 0004336 568 m Page 13 GSM 03.47 version 4.3.0 - Objects - - - respectively). The SC and the MSC are modelled as atomic objects, sC-Object and MSC-Object. Each object has one port for the interconnection. (SI and CI indicate supply and cons

46、umption of services, sC-O bject mSC-O bject - Port sMR-port OBJECT PORTS MR-port CI : = id-Ot-SC OBJECT PORTS sMR-port SI : = id-ot-MSC PORT CONSUMER INVOKES Forward-MS-Terminated-Short-Message SUPPLIER INVOKES Forward-MS-Originated-Short-Message, Alert- sc 1 - Bind SMR-Bind := ABSTRACT-BIND TO MR-p

47、ort BIND ARGUMENT SMR-Bind-Parameters RESULT SMR-Bind-confirm BIND-ERROR SMR-Bind-failure - Unbind - _ - - - losses of operations occur. The UNBIND is a harsh release of the association: all outstanding operations are aborted, and SMR-ALERT requests may be lost if they collide with the SMR-UNBIND re

48、quest. The SC and the MSC should negotiate (during SMR-BIND) the use of services on the association (the operations parameter - list of operation types for the association) in such a way that no harmful SMR-Unbind : = ABSTRACT-UNBIND FROM sMR-port UNBIND ARGUMENT Time-when-connected RESULT Time-when

49、-disconnected ETSI GSM*03.47 94 m 3400855 0004337 4T4 m Page 14 GSM 03.47 version 4.3.0 - Association control parameters SMR-Bind-Parameters : = SEQUENCE initiatorlD O Name, password 11 I Password OPTIONAL, pswNeeded I21 BOOLEAN, iniType 31 Teiecom-System-Type, operations 4 List-of-Operations Above and in SMR-Bind-confirm initiatorlD/resplD: identify the initiating/responding telecommunication subsystem passwor