1、 STD-ETSI GSM 09-LO-ENGL 1997 9 3400855 0247282 b57 GSM - PCHNICAL PECIFICATION GSM 09.10 November 1997 Version 5.2.0 Source: SMG Reference: RTS/SMG-03091 OQR1 ICs: 33.020 Key words : Digital cellular telecommunications system, Global System for Mobile communications (GSM) Digital cellular telecommu
2、nications syslem (Phase 2+); Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC) Signalling procedures and the Mobile Application Part (MAP) (GSM 09.1 O version 5.2.0) ETSI European Telecommunicati
3、ons Standards Institute ETSI Secretariat Postal address: F-O6921 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: secretariatQetsi.fr Tel.: 43 4 92 94 42 O0 - Fax: 43 4 93 65 47 16 Co
4、pyright Notification: No part may be reproduced except as authoreed by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 1997. All rights reserved. STD-ETSI GSM 09-LO-ENGL 1777 m 3400855 0247183 573
5、m Page 2 GSM 09.1 O version 5.2.0: November 1997 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
6、 the address shown on the title page. STD-ETSI GSM 07.LO-ENGL 1797 3400855 0247184 q2T W Page 3 GSM 09.10 version 5.2.0: November 1997 Contents Scope . 7 1.1 Normative references . 7 1.2 Abbreviations 8 Classification of interworking cases . 9 2.2 Non-transparent procedures . 9 2.1 Transparent proce
7、dures . 9 Interworking in the MSC. Transparent case . 9 3.1 General . -9 3.2 Location area updating . 11 3.3 Detach IMSI 12 3.4 Authentication 12 3.5 Retrieval of the IMSI from the MS . 13 3.6 Reallocation of TMSI . 13 3.7 Retrieval of the IMEI from the MS . 13 3.8 Tracing subscriber activity 14 Non
8、-transparent cases . 14 4.1 General 14 4.2 Outgoing call set-up (MS originating call) . 14 4.3 Incoming call set-up (MS terminating call) 19 4.4 Cipher mode setting . 20 4.5 Inter-MSC Handover 21 4.5.1 Basic Inter-MSC Handover 21 4.5.2 Subsequent Inter-MSC Handover back to MSC-A . 27 4.5.3 Subsequen
9、t Inter-MSC Handover to third MSC . 31 4.5.4 BSSAP Messages transfer on E-Interface 34 4.5.5 Processing in MSC-6, and information transfer on E-interface 35 4.5.5.1 Encryption Information . 35 4.5.5.2 Channel Type . 36 4.5.5.3 Classmark 37 4.5.5.4 Downlink DTX-Flag . 37 4.5.5.5 Priority . 38 4.5.5.6
10、 Overview of the Technical Specifications GSM interworking for the Inter- MSC Handover . 38 MSCBSC-Invoke Trace Information Elements 38 4.5.6 Foreword . 5 History . 40 STD-ETSI GSM OS-LO-ENGL 1777 W 3400855 0247185 3bb m Page 5 GSM 09.10 version 5.2.0: November 1997 Foreword This Global System for M
11、obile communications Technical Specification (GTS) has been produced by the Special Mobile Group (SMG) of the European Telecommunications Standards Institute (ETSI). This GTS specifieslnformation element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile
12、-services Switching Centre (BSS - MSC) Signalling procedures and the Mobile Application Part (MAP) within the digital cellular telecommunications system (Phase 2/Phase 2+). GTS are produced by SMG to enable the GSM Phase 2+ specifications to become publicly available, prior to submission for the for
13、mal 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. Subclause 4.5.2 has been mod
14、ified in this version 52.0. 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 w ill then be republished by ETSI with an identifying change of release date and an increase in version number as
15、 follows: Version 5.x.y where: y the third digit is incremented when editorial only changes have been incorporated in the specification; x the second digit is incremented for all other types of changes, .e. technical enhancements, corrections, updates, etc. The specification from which this GTS has
16、been derived was originally based on CEPT documentation, hence the presentation of this GTS may not be entirely in accordance with the ETSI rules. Previous page is blank STD-ETSI GSM 07.1O-ENGL 1997 m 1400855 024718b 2T2 W Page 7 GSM 09.10 version 5.2.0: November 1997 1 scope The scope of this Techn
17、ical Specification is: i) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-MSC interface (Call Control and Mob ility Management parts of GSM 04.08) and parameters contained in MAP services sent over the MSC-VLR interfa
18、ce (GSM 09.02) where the MSC acts as a transparent relay of information; i) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC-MSC interface (GSM 08.08) and parameters contained in MAP services sent over the MSC-VLR inte
19、rface (GSM 09.02) where the MSC acts as a transparent relay of information; iii) to provide a detailed specification for the interworking as in i) and i) above when the MSC also processes the information. Interworking for supplementary services is given in GSM 09.11. Interworking for the short messa
20、ge service is given in GSM 03.40 and GSM 04.11. Interworking between the call control signalling of GSM 04.08 and the PSTNIISDN is given in GSM 09.03, GSM 09.07 and GSM 09.08. Interworking between the A and E interfaces for inter-MSC handover signalling is given in GSM 09.07 and 09.08. 1.1 Normative
21、 references This ETS 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 publ
22、ications apply to this ETS only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. i31 41 GSM O1 .O4 (ETR 350): “Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms“. GSM 03.09: “Digital c
23、ellular telecommunications system (Phase 2+); Handover procedures“. GSM 03.40 (ETS 300 901): “Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)“. GSM 04.08 (ETS 300 940): “Digital cellular telecommunications system (Ph
24、ase 2+); Mobile radio interface layer 3 specification“. GSM 04.1 O (ETS 300 941): “Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification General aspects“. GSM 04.1 1 (ETS 300 942): “Digital cellular telecommunications system (Phase
25、 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface“. GSM 08.08: “Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification“. GSM 09.02 (ETS 300 974): “Digital cellular telecomm
26、unications system (Phase 2+); Mobile Application Part (MAP) specification“. Previous page is blank STD*ETSI GSM 07-LO-ENGL 1497 W 3400855 0247387 339 = Page 8 GSM 09.1 O version 5.2.0: November 1997 91 1.2 Abbreviations GSM 09.03: “Digital cellular telecommunications system (Phase 2); Signalling req
27、uirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)“. GSM 09.07 (ETS 300 976): “Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the P
28、ublic Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)“. GSM 09.08: “Digital cellular telecommunications system (Phase 2+); Application of the Base Station System Application Part (BSSAP) on the E-interface“. GSM 09.1 1 : “Digi
29、tal cellular telecommunications system (Phase 2+); Signa Iling interworking for supplementary services“. Abbreviations used in this specification are listed in GSM 01.04. Page 9 GSM 09.10 version 5.2.0: November 1997 2 Classification of interworking cases 2.1 Transparent procedures The following MSC
30、 procedures require transparent mapping of BSSAP information elements into MAP parameters and vice versa (see GSM 09.02 for definitions and the use of the procedures): - update location area; - detach IMSI; - forward new TMSI; - provide IMSI; - obtain IMEI; - checkIMEI; - authenticate; - trace subsc
31、riber activity. 2.2 Non-transparent procedures Procedures in this class require processing in the MSC and information element mapping. These procedures include those related to: - outgoing call Set-up; - incoming call Set-up; - handover; - cipher mode setting. 3 Interworking in the MSC, Transparent
32、case 3.1 General When the MSC receives a forward message from the BSS (possibly forwarded transparently from the MS), it will invoke the desired MAP service and establish a cross reference between the BSSAP procedure and the MAP procedure in order to return the result of the operation to the BSS (wh
33、ich may forward it transparently to the MS. The cross reference is deleted when the MSC terminates the MAP procedu re. Positive or negative results of the MAP procedure are returned in the appropriate BSSAP message. The parameters of the forward BSSAP message are mapped by a one-to-one mapping into
34、the parameters of the MAP service. However, in some cases parameters received on the radio path may be suppressed at the MSC because they are related to another protocol entity, e.g. information related to RR-management may be included in MM-management messages. Similarly, parameters received in the
35、 (positive) MAP service response are mapped one-to-one into parameters of the corresponding backward BSSAP message. A negative outcome, as carried in various MAP services (MAP specific service response, MAP-U-ABORT, MAP-P-ABORT, MAP,-NOTICE and premature MAP-CLOSE, see GSM 09.02 for definitions) is
36、mapped into a cause value in the required backward BSSAP mess age. In this case several negative results of MAP may be mapped into the same BSSAP cause value, .e. without discrimination between these negative results. NOTE: For O ? M purposes, the MAP procedure entity in the MSC may require a more d
37、etailed overview of negative results than the MS. STD-ETSI GSM OS-LO-ENGL 1777 3I00855 0247187 TO1 W Page 10 GSM 09.10 version 5.2.0: November 1997 Forward message Positive result These principles are illustrated in figure 1. 04.08 08.08) forwar d message 04.08 or 08.08 09.02 MS/BSS to MSC MSC to VL
38、R jnforma?+on element i parameter i information element 2 parameter 2 MSC to MS/BSS VLR,to MSC parameter 1 parameter 2 informa ion element 1 positive ack response cause 1 cause 2 MAP U/P ABORT MAP NOTICE MAP CLOSE message name cause 1 cause 2 cause 3 cause 3 cause 3 - mapping negative cause - - - CM
39、 SERVICE ACCEPT . RELEASE COMPLETE MAP PROCESS - ACCESS - REQUEST response - - - _-_- STD-ETSI GSM 09.10-ENGL 1777 9 3Y00855 0247201 337 Page 22 GSM 09.1 O version 5.2.0: November 1997 BSS-B I HANDOVER REQUEST BSC INVOKE TRACE - (* ) -_- SS-A MSC-A BSC INVOKE TRACE MS -B Possible Alloc. of a handove
40、r no. in the VLR-B -A MS -B Possible Alloc. of a handover no. in the VLR-B BSS-B I HANDOVER REQUEST MSC INVOKE TRACE -_-_ (* - Figure 5c: Signalling for Basic Inter-MSC Handover initiation (MSC invoke trace message transferred) (*I: Tracing invocation has been received from VLR. (*): In that case, “
41、DOVER REQUEST and MSC INVOKE TRACE messages are included within the BSS-apdu parameter. MSC INVOKE TRACE is forwarded to BSS-B if supported by MSC-B. (*): STDSETSI GSM 07*LO-ENGL 1777 Sl 3Y00855 O247202 275 Page 23 GSM 09.1 O version 5.2.0: November 1997 Possible Positive outcomes a) successful radi
42、o resources allocation and handover number allocation (if performed): MSC-B BSS-B BSS-A MSC-A MAP PREPARE HANDOVER response - (Note 1) Figure 9: Signalling for Basic Inter-MSC Handover completion (Positive outcome) STDSETSI GSM 09.LO-ENGL 1997 W 3400855 0247204 O48 Page 25 GSM 09.1 O version 5.2.0:
43、November 1997 Negative outcome BSS-A MSC-A MSC-B BSS-B I I I I 1 MAP U/P -ABORT I I I I I_ I I I I ICLEAR COMMAND I I I_ I I I I I I Figure 1 O: Signalling for Basic Inter-MSC Handover completion (Negative outcome) NOTE: From interworking between MAP and BSSMAP point of view. The handover procedure
44、is normally triggered by BSS-A by sending a HANDOVER REQUIRED message on A-Interface to MSC-A. The invocation of the Basic Inter-MSC handover procedure is performed and controlled by MSC-A. The sending of the MAP Prepare-Handover request to MSC-B is triggered in MSC-A upon receipt of the HANDOVER RE
45、QUIRED message. For compatibility reason, the cell identity of the cell where the call is to be handed over in MSC-B area, provided in the HANDOVER REQUIRED message, is mapped into targetcellld MAP parameter and the HANDOVER REQUEST message is encapsulated in the bss-APDU MAP parameter of the Prepar
46、e-Handover MAP request. MSC-B can invoke another operation towards the VLR-B (allocation of the handover number described in GSM 09.02). Additionally, if tracing activity has been invoked, the trace related messages can be transferred on the E- Interface encapsulated in the bss-APDU MAP parameter of
47、 the Prepare-Handover Request. lf transferred, one complete trace related message at a time shall be included in the bss-APDU MAP parameter after the HANDOVER REQUEST message. The interworking between Prepare Handover and HANDOVER REQUIRED is as follows: Forward message Positive result Negative resu
48、lt 08.08 09.02 HANDOVER REQUIRED MAP PREPARE HANDOVER request -ho-NumberNotRequired -bss-APDU ( HANDOVER RE UEST, BSSMAP information -targetCellId e lemen t s BSC INVOKE $ RACE or MSC INVOKE TRACE) MAP PREPARE HANDOVER response -handover number -bss-APDU ( QUEUING INDICATION or HANDOVER REQUEST ACKN
49、OWLEDGE or HANDOVER FAILURE) HANDOVER REQUIRED REJECT MAP PREPARE HANDOVER equipment failure equipment failure equipment failure equipment failure equipment failure equipment failure System Failure No Handover Number available UnexpectedDataValue Data Missing MAP CLOSE MAP U/P -ABORT potes 1 2 3 + 4 5 NOTE 1 : The ho-NumberNotRequired parameter is included by MSC-A, when MSC-A decides not to use any circuit connection with MSC-B. No han
