ETSI GSM 03 49-1998 Digital Cellular Telecommunications System (Phase 2+) Example Protocol Stacks for Interconnecting Cell Broadcast Centre (CBC) and Base Station Controller (BSC)《.pdf

《ETSI GSM 03 49-1998 Digital Cellular Telecommunications System (Phase 2+) Example Protocol Stacks for Interconnecting Cell Broadcast Centre (CBC) and Base Station Controller (BSC)《.pdf》由会员分享，可在线阅读，更多相关《ETSI GSM 03 49-1998 Digital Cellular Telecommunications System (Phase 2+) Example Protocol Stacks for Interconnecting Cell Broadcast Centre (CBC) and Base Station Controller (BSC)《.pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、GSM GSM 03.49 July 1998 Version 5.7.0 Source: SMG Reference: RGTS/SMG-O40349QR5 ICs: 33.020 Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM) Digital cellular telecommunications system (Phase 2+); Example protocol stacks for interconnecting Cell Bro

2、adcast Centre (CBC) and Base Station Controller (BSC) (GSM 03.49 version 5.7.0 Release 1996) ETSI Eu ropean Telecom mun cat ions Standards Institute ETSI Secretariat Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE

3、Internet: secretariat etsi.fr - http:/www.etsi.fr - http:/www.etsi.org Tel.: 43 4 92 94 42 O0 - Fax: +33 4 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 ali media. O Euro

4、pean Telecommunications Standards Institute 1998. Ail rights reserved. Page 2 GSM 03.49 version 5.7.0 Release 1996: July 1998 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 concernin

5、g its accuracy, please write to “ETSI Standards Making Support Dept.“ at the address shown on the title page. Page 3 GSM 03.49 version 5.7.0 Release 1996: July 1998 Contents Foreword . 5 Introduction 5 Scope 7 1.1 References . 7 1.2 Abbreviations 8 A protocol stack which utilises an application-netw

6、ork layer convergence function for interconnecting CBC and BSC 8 2.1 CBSE Definition . 9 2.2 ASN1 Specification 11 2.3 2.4 Application Rules for Avoidance of Collision of CBSE Operations 16 Non Suppor of 128 bytes of NS-user-data in Network Connection and Network Connection Release phases 16 An OS1

7、Protocol Stack For Interconnecting CBC and BSC 18 3.1 Service elements on the application layer 18 3.2 Detailed specification of the CBRSE services . 18 3.3 Application rules . 31 3.3.1 Application rule set 1 Semi-permanent symmetric connection . 31 3.3.2 Application rule set 2 Transient asymmetric

8、connection . 31 An SS7 Protocol Stack For Interconnecting CBC And BSC . 32 Annex A (informative): Change history . 33 History 34 STDmETSI GSM 03.47-ENGL 1798 D 3400855 033270b 72T Feature In Phase 2+ systems the Restart-lnd, Failure-lnd and Set-DRX-Resp PDUs supply consistent cell-list formats Page

9、5 GCM 03.49 version 5.7.0 Release 1996: July 1998 Designator $( Phase2PBscCellLists)$ Foreword This Global System for Mobile communications Technical Specification (GTS) has been produced by the Special Mobile Group (SMG) of the European Telecommunications Standards Institute (ETSI). This GTS specif

10、ies three alternative approaches to the specification of protocol stacks of communication protocols for the purpose of fulfilling the service requirements of the primitives specified for the CBC - BSC interface in GSM 03.41 within the digital cellular telecommunications system (Phase 2/Phase 2+). ,

11、The contents of this GTS are subject to continuing work within SMG and may change following formal SMG approval. Should 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

12、: 5 GSM Release 1996 y the third digit is incremented when editorial only changes have been incorporated in the specif icat io n; the second digit is incremented for all other types of changes, .e. technical enhancements, corrections, updates, etc. x Introduction The present document includes refere

13、nces to features which were introduced into the GSM Technical GTS 03.49 - Version 5.7.0specifications after Release 96 of GSM Phase2+. The text that is relevant, if the feature is supported, is marked with designators. I from the BSC. Previous page is blank STD-ETSI GSM 03.V7-ENGL 1778 3400855 O3327

14、07 Bbb II Page 7 GSM 03.49 version 5.7.0 Release 1996: July 1998 1 scope No mandatory protocol between the Cell Broadcast Centre (CBC) and the Base Station Controller (BSC) is specified by GSM; this is a matter of agreement between CBC and PLMN operators. This Global System for Mobile communications

15、 Technical Specification (GTS) specifies three alternative approaches to the specification of protocol stacks of communication protocols for the purpose of fulfilling the service requirements of the primitives specified for the CBC - BSC interface in GSM 03.41. One approach is based upon the use of

16、the complete OS1 reference model (see X.200), another approach is based upon the use of only the lower 3 OS1 layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700). Specifications are based upon individual contributions. Any judgement concerning functionality

17、, completeness and advantages/disadvantages of implementation is intentionally omitted. 1.1 References This GTS incorporates by dated and undated reference, provisions from other publications. These references are cited at the appropriate places in the text and the publications are listed hereafter.

18、 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. 1 GSM 01.04 (ETR 350): “Digital cellular telecommunica

19、tions system (Phase 2+); Abbreviations and acronyms“. GSM 03.41 (ETS 300 902): “Digital cellular telecommunications system (Phase 2+); Technical realization of Short Message Service Cell Broadcast (SM SC B) I. GSM 12.20 (ETS 300 622): “Digital cellular telecommunication system (Phase 2); Network Man

20、agement (NM) procedures and messages“. CCITT Recommendation Q.700: “Introduction to CCITT Signalling System N0.7“. CCITT Recommendation Q.931: Integrated services digital network.(lSDN) User-Network interface layer 3 specification for basic control“. CCITT Recommendation Q.932: “Generic procedures f

21、or the control of ISDN supplementary services“. CCITT Recommendation Q.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 conce

22、pts“. 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.213: “Information technology

23、 - Network service definition for Open Systems Interconnection“. CCITT Recommendation X.215: “Session service definition for open systems interconnection for CCITT applications“. Previous page is blank STD-ETSI GSM 03-4S-ENGL 1798 I3400855 0332708 7T2 W Page 8 GSM 03.49 version 5.7.0 Release 1996: J

24、uly 1998 CCITT Recommendation X.217: “Association control service definition for open systems interconnection for CCITT applications“. i 31 I 41 CCITT Recommendation X.219: “ Remote operations: model, notation and service definition“. i 51 CCITT Recommendation X.225: “Session protocol specification

25、for Open Systems Interconnection for CCITT Applications“. CCITT Recommendation X.227: “Information technology - Open Systems Interconnection - protocol specification for the association“. 11 71 CCITT Recommendation X.229: “Remote operations Protocol specification“ 1.2 Abbreviations Abbreviations use

26、d in this GTS are listed in GSM 01.04. 2 A protocol stack which utilises an application-network layer convergence function for interconnecting CBC and BSC A convergence function (see Draft CCITT Recommendation Q.941 Report R 22 May 1990) which maps an application entity protocol directly to the Netw

27、ork Layer service defined by X.213 can provide a practical alternative to ACSE, ROSE and OS1 layers 6, 5 and 4. Application Layer - CBS Application Layers 4.5 only after the application association has been established may the remaining CBSE services be used. This operation reports either success (v

28、ia CSE-Bind-Confirm) or failure (via CBSE-Bind-Failure). CBSE-B IN D will be mapped to/f rom N-CONM ECT req uesindication with CBSE-BIND. param eters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-BIND parameters may be carried by the first N-DATA

29、 requesthdication following establishment of the network layer connection - see section 2.4). This operation is retained for backward compatibility with Phase 2 systems. Note: This PDU should be used in the case of a Phase 2+ entity communicating with a Phase 2 entity. CBSE-VBIND This operation must

30、 be invoked by the party which is responsible for establishing the application association; only after the application association has been established may the remaining CBSE services be used. This operation reports either success (via CBSE-Bind-Confirm) or failure (via CBSE-Bind-Failure). CBSE-VBIN

31、D will be mapped to/from N-CONNECT requesthdication with CBSE-VBIND parameters carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-VBIND parameters may be carried by the first N-DATA requestlindication following establishment of the network layer conne

32、ction - see section 2.4). This operation is used in Phase 2+ systems. CBSE-BIND-CONFIRM This operation must be invoked by a party to accept an application association. CBSE-BIND-CONFIRM will be mapped to/from N-CONNECT confirm/response with CBSE-BIND- CONFIRM parameters carried in NS-user-data (if t

33、he network layer does not support NS-user-data of 128 octets then CBSE-BIND-CONFIRM may be carried as the second N-DATA requesindication following establishment of the network layer connection - see Section 2.4). On receipt of a CBSE-BIND PDU, the recipient must assume that the sender is supporting

34、the Phase 2 version of the interface and must reply with an untagged CBSE-BIND-CONFIRM. If a CBSE-VBIND PDU is received, the recipient must reply with a tagged CBSE-BIND-CONFIRM as a substructure of CBSEapdus. CBSE-BIND-FAILURE This operation must be invoked by a party to reject an attempted applica

35、tion association. CBSE-BIND-FAILURE will be mapped to/from N-DISCONNECT requesthdication with CBSE- BIND-FAILURE parameters carried in NS-user-data (if the network layer does not support NS-user- data of 128 octets then CBSE-BIND-FAILURE parameters shall be carried by the N-DATA requesindication pre

36、ceding N-D I SCONN ECT. GSM phase2 compliance: If the network layer does not support NS-user-data of 128 octets then CBSE-BIND-FAILURE parameters will not be carried by the network layer - .e. NS-user-data will be discarded). CBSE-UNBIND Page 10 GSM 03.49 version 5.7.0 Release 1996: July 1998 This o

37、peration must be invoked by a party to release the application association. CBSE-UNBIND will be mapped to/from N-DISCONNECT requestindication with CBSE-UNBIND parameters be carried in NS-user-data (if the network layer does not support NS-user-data of 128 octets then CBSE-UNBIND parameters shall be

38、carried by the N-DATA requestlindication preceding N-DISCONNECT - see Section 2.4 ). GSM phase 2 compliance: If the network layer does not support NS-user-data of 128 octets then reception of N- DISCONNECT shall be interpreted as a CBSE-UNBIND even if the N-DISCONNECT is not preceded by a N-DATA pac

39、ket carrying the CBSE-UNBIND parameters. $start$( Phase2PBscCellLists)$ CBSE-WRITE-REPLACE, CBSE-KILL, CBSE-REPORT, CBSE-STATUS-CBCH-QUERY, CBSE-STATUS-CBCH-QUERY-RESP, CBSE-STATUS-MESS-QUERY, CBSE-STATUS-MESS-QUERY-RESP, CBSE-REJECT, CBSE-RESTART-IND, CBSE-RESTART-IND- PHASE2P, CBSE-RESET, CSE-FAIL

40、URE-IND, CSE-FAILURE-IND-PHASE2P, CBSE-SET-DRX, CBSE- SET-DRX-RESP Application data units CBSE-WRITE-REPLACE, CBSE-KILL, CBSE-REPORT, CBSE-STATUS- CBCH-QUERY, CBSE-STATUS-CBCH-QUERY-RESP, CBSE-STATUS-MESSAGE-QUERY, CBSE-STATUS-MESS-QUERY-RESP., CBSE- REJECT, CBSE -RESTART-IND, CBSE - RESTART-IND-PHA

41、SE2P, CBSE-RESET, CBSE-FAILURE-IND, CBSE-FAILURE-IND-PHASE2P, CBSE-SET-DRX, CBSE-SET-DRX-RESP provide the services specified via primitives Write- Replace, Kill, Report, Status-CBCH, Status-CBCH-Response, Status-Message, Status-Message- Response, Reject, Restart-Indication, Restart-lndication-Phase2

42、P, Reset, Failure-Indication, Failure-lndication-Phase2P, Set-DRX and Set-DRX-Response respectively in GSM 03.41. $end$(P hase2PBscCellLicts)$ These application data units will be mapped to/from N-DATA requestindication. Page 11 GSM 03.49 version 5.7.0 Release 1996: July 1998 2.2 ASN1 Specification

43、The Abstract Syntax Notation of the Cell Broadcast Short Message Service Element CBSE ist module of 2: CBS-UsefulDefinitions CBS-UsefulDefinitions ccitt identified-organization (4) etsi (O) mobile-domain (O) gsm-messaging (4) gsm-sms3 (12) usefulDefinitions (10) 1 DEFINITIONS IMPLICIT TAGS BEGIN . .

44、= ID := OBJECT IDENTIFIER mobile-domain ID := (ccitt identified-organization (4) etsi (O) mobile-domain(0) - root for all sms allocations gsm-messaging ID := ( mobile-domain gsm-messaging(4) 1 -_ categories gcm-sms3 ID := ( gsm-messaging 12 END 2nd module of 2: Application Protocol ApplicationProtoc

45、ol ccitt identified-organization (4) etsi (O) mobile-domain0) gsm-messaging(4) gsm-sms3 (12) applicationProtocol(l1) ) DEFINITIONS IMPLICIT TAGS BEGIN . .- . .- - CBSE-BIND will be carried as N-CONNECT request/indication - CBSE-BIND-Parameters will carried in the User Data field of the N-CONNECT - r

46、equest/indication message. - Note that this structure should be used by Phase 2 systems only. CBSE-BIND-Parameters := SEQUENCE ( initiatorID O Name, password 111 Password OPTIONAL 1 - Above and in CBSE-BIND-CONFIRM -_ initiatorID/respID: identify the initiating/responding telecommunication subsystem

47、 - password: may assist in authentication - CBSE-WIND-Parameters will only be used as an element of CBSEapdus in the - User Data field of the N-CONNECT requestlindication message. - Note that this structure should be used by Phase 2t and higher systems only. CBSE-VBIND-Parameters := SEQUENCE initiat

48、orID i01 Name, password l Password OPTIONAL, version 21 Version Page 12 GSM 03.49 version 5.7.0 Release 1996: July 1998 Version indication _ Above - initiatorID/respID: identify the initiating/responding telecommunication subsystem - password: may assist in authentication - version: identify the int

49、erface version supported, defined below Document Version Name : : = SEQUENCE ( operator O Operator OPTIONAL, bilateralAgreem 111 BilateralAgreem OPTIONAL, dataNetworkAddress 21 X121Address OPTIONAL, iSDNAddress 131 CBS-Address OPTIONst OPTIONAL, channel-indicator 41 Channel OPTIONAL 1 Reject:= SEQUENCE ( cause Failure-Reason, diagnostic Diagnostic-Info OPTIONAL, message-Identifier 71 Message-Identifier OPTIONAL, serial-Number 31 Serial-Number OPTIONAL I - $start$Phase2PBscCellLists)$ - The Restart-Ind PDU is retained fo