ETSI ETS 300 605 ed.1 (1995-02)
European digital cellular telecommunications system (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.10)
European digital cellular telecommunications system (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.10)
DE/SMG-030910P
Evropski digitalni celični telekomunikacijski sistem (faza 2) – Preslikava elementov informacije med mobilno postajo in sistemom baznih postaj (MS-BSS) ter sistemom baznih postaj – komutacijo mobilnih storitev (BSS-MSC) – Postopki signalizacije in del za mobilne aplikacije (MAP) (GSM 09.10)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 605 E1:2003
01-december-2003
(YURSVNLGLJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ±3UHVOLNDYDHOHPHQWRY
LQIRUPDFLMHPHGPRELOQRSRVWDMRLQVLVWHPRPED]QLKSRVWDM 06%66 WHU
VLVWHPRPED]QLKSRVWDM±NRPXWDFLMRPRELOQLKVWRULWHY %6606& ±3RVWRSNL
VLJQDOL]DFLMHLQGHO]DPRELOQHDSOLNDFLMH 0$3 *60
European digital cellular telecommunications system (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.10)
Ta slovenski standard je istoveten z: ETS 300 605 Edition 1
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
SIST ETS 300 605 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 605 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 605 E1:2003
EUROPEAN ETS 300 605
TELECOMMUNICATION February 1995
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-030910P
ICS: 33.060.30
European digital cellular telecommunications system, Global System for Mobile communications
Key words:
(GSM)
European digital cellular telecommunications system (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.10)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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.
© European Telecommunications Standards Institute 1995. All rights reserved.
New presentation - see History box
---------------------- Page: 3 ----------------------
SIST ETS 300 605 E1:2003
Page 2
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
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 the address shown on the title page.
---------------------- Page: 4 ----------------------
SIST ETS 300 605 E1:2003
Page 3
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
Contents
Foreword.5
1 Introduction.7
1.1 Scope .7
1.2 Normative references .7
1.3 Definitons and abbreviations.8
2 Classification of interworking cases .8
2.1 Transparent procedures .8
2.2 Non-transparent procedures.8
3 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. 14
3.7 Retrieval of the IMEI from the MS . 14
3.8 Tracing subscriber activity. 15
4 Non-transparent cases. 15
4.1 General. 15
4.2 Outgoing call set-up (MS originating call) . 15
4.3 Incoming call set-up (MS terminating call) . 20
4.4 Cipher mode setting . 22
4.5 Inter-MSC Handover. 22
4.5.1 Basic Inter-MSC Handover. 22
4.5.2 Subsequent Inter-MSC Handover back to MSC-A . 29
4.5.3 Subsequent Inter-MSC Handover to third MSC . 34
4.5.4 BSSAP Messages transfer on E-Interface. 39
4.5.5 Processing in MSC-B, and information transfer on E-interface . 40
4.5.5.1 Encryption Information . 41
4.5.5.2 Channel Type. 42
4.5.5.3 Classmark. 42
4.5.5.4 Downlink DTX-Flag. 43
4.5.5.5 Priority. 43
4.5.5.6 MSC/BSC-Invoke Trace Information Elements. 43
4.5.6 Overview of the Technical Specifications GSM interworking for the Inter-
MSC Handover. 44
History. 45
---------------------- Page: 5 ----------------------
SIST ETS 300 605 E1:2003
Page 4
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
Blank page
---------------------- Page: 6 ----------------------
SIST ETS 300 605 E1:2003
Page 5
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
Foreword
This European Telecommunication Standard (ETS) has been produced by the Special Mobile Group
(SMG) Technical Committee (TC) of the European Telecommunications Standards Institute (ETSI) and is
now submitted for publication.
This ETS describes 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), within the European digital cellular telecommunications system
(Phase 2).
This ETS corresponds to GSM technical specification GSM 09.10 version 4.2.2.
The specification from which this ETS has been derived was originally based on CEPT documentation,
hence the presentation of this ETS may not be entirely in accordance with the ETSI/PNE rules.
NOTE: TC-SMG has produced documents which give the technical specifications for the
implementation of the European digital cellular telecommunications system. Historically,
these documents have been identified as GSM Technical Specifications (GSM-TSs).
These TSs may have subsequently become I-ETSs (Phase 1), or ETSs (Phase 2),
whilst others may become ETSI Technical Reports (ETRs). GSM-TSs are, for editorial
reasons, still referred to in current GSM ETSs.
---------------------- Page: 7 ----------------------
SIST ETS 300 605 E1:2003
Page 6
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 605 E1:2003
Page 7
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
1 Introduction
1.1 Scope
The scope of this Technical 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 Mobility Management parts of TS
GSM 04.08) and parameters contained in MAP services sent over the MSC-VLR interface (TS GSM
09.02) where the MSC acts as a transparent relay of information;
ii) to provide a detailed specification for the interworking between information elements contained in
BSSMAP messages sent on the BSC-MSC interface (TS GSM 08.08) and parameters contained in
MAP services sent over the MSC-VLR interface (TS 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 ii) above when the MSC also
processes the information.
Interworking for supplementary services is given in TS GSM 09.11. Interworking for the short message
service is given in TSs GSM 03.40 and GSM 04.11. Interworking between the call control signalling of TS
GSM 04.08 and the PSTN/ISDN is given in TSs 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 TSs GSM 09.07 and 09.08.
1.2 Normative 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 publications 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.
[1] GSM 01.04 (ETR 100): "European digital cellular telecommunications system
(Phase 2); Abbreviations and acronyms".
[2] GSM 03.09 (ETS 300 527): "European digital cellular telecommunications
system (Phase 2); Handover procedures".
[3] GSM 03.40 (ETS 300 536): "European digital cellular telecommunications
system (Phase 2); Technical realization of the Short Message Service (SMS)
Point to Point (PP)".
[4] GSM 04.08 (ETS 300 557): "European digital cellular telecommunications
system (Phase 2); Mobile radio interface layer 3 specification".
[5] GSM 04.10 (ETS 300 558): "European digital cellular telecommunications
system (Phase 2); Mobile radio interface layer 3 Supplementary services
specification General aspects".
[6] GSM 04.11 (ETS 300 559): "European digital cellular telecommunications
system (Phase 2); Point-to-Point (PP) Short Message Service (SMS) support on
mobile radio interface".
[7] GSM 08.08 (ETS 300 590): "European digital cellular telecommunications
system (Phase 2); Mobile Switching Centre - Base Station System (MSC - BSS)
interface Layer 3 specification".
[8] GSM 09.02 (ETS 300 599): "European digital cellular telecommunications
system (Phase 2); Mobile Application Part (MAP) specification".
---------------------- Page: 9 ----------------------
SIST ETS 300 605 E1:2003
Page 8
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
[9] GSM 09.03 (ETS 300 600): "European digital cellular telecommunications
system (Phase 2); Signalling requirements on interworking between the
Integrated Services Digital Network (ISDN) or Public Switched Telephone
Network (PSTN) and the Public Land Mobile Network (PLMN)".
[10] GSM 09.07 (ETS 300 604): "European digital cellular telecommunications
system (Phase 2); General requirements on interworking between the Public
Land Mobile Network (PLMN) and the Integrated Services Digital Network
(ISDN) or Public Switched Telephone Network (PSTN)".
[11] GSM 09.08 (ETS 300 626): "European digital cellular telecommunications
system (Phase 2); Application of the Base Station System Application Part
(BSSAP) on the E-interface"
[12] GSM 09.11 (ETS 300 606): "European digital cellular telecommunications
system (Phase 2); Signalling interworking for supplementary services".
1.3 Definitons and abbreviations
Abbreviations used in this specification are listed in GSM 01.04.
2 Classification of interworking cases
2.1 Transparent procedures
The following MSC procedures require transparent mapping of BSSAP information elements into MAP
parameters and vice versa (see TS GSM 09.02 for definitions and the use of the procedures):
- update location area;
- detach IMSI;
- forward new TMSI;
- provide IMSI;
- obtain IMEI;
- check IMEI;
- authenticate;
- trace subscriber 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.
---------------------- Page: 10 ----------------------
SIST ETS 300 605 E1:2003
Page 9
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
3 Interworking in the MSC, Transparent 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 (which may forward it
transparently to the MS. The cross reference is deleted when the MSC terminates the MAP procedure.
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 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
(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 TS GSM 09.02 for definitions) is
mapped into a cause value in the required backward BSSAP message. In this case several negative
results of MAP may be mapped into the same BSSAP cause value, i.e. without discrimination between
these negative results.
NOTE: For O & M purposes, the MAP procedure entity in the MSC may require a more
detailed overview of negative results than the MS.
These principles are illustrated in figure 1.
04.08 (08.08) MAP service
forward message request
˜˜˜˜˜˜˜˜˜˜˜˜> ˜˜˜˜˜˜˜˜˜˜˜>
�˜˜˜˜˜˜˜˜˜˜˜¿ �˜˜˜˜˜˜˜˜˜¿
‡information‡ ‡parameter‡
‡ element ‡ ‡ ‡
�˜˜˜˜˜´˜˜˜˜˜� one-to-one �˜˜˜˜´˜˜˜˜�
�˜˜˜˜˜>˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜>˜˜˜˜�
mapping
MAP service
positive ack response
<˜˜˜˜˜˜˜˜˜˜˜˜ <˜˜˜˜˜˜˜˜˜˜˜
�˜˜˜˜˜˜˜˜˜˜˜¿ �˜˜˜˜˜˜˜˜˜¿
‡information‡ ‡parameter‡
‡ element ‡ ‡ ‡
�˜˜˜˜˜´˜˜˜˜˜� one-to-one �˜˜˜˜´˜˜˜˜�
�˜˜˜˜˜<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜<˜˜˜˜�
mapping
negative
negative cause response
<˜˜˜˜˜˜˜˜˜˜˜˜ <˜˜˜˜˜˜˜˜˜˜˜
�˜˜˜˜˜˜˜˜˜˜˜¿ �˜˜˜˜˜˜˜˜˜¿
‡ cause ‡ ‡ cause ‡
�˜˜˜˜˜´˜˜˜˜˜� one-to-one or many-to-one �˜˜˜˜´˜˜˜˜�
�˜˜˜˜˜<˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜<˜˜˜˜�
mapping
Figure 1: Illustration of mapping principles in the MSC
---------------------- Page: 11 ----------------------
SIST ETS 300 605 E1:2003
Page 10
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
For each of the transparent operations listed in section 2.1, the following format is used to show the
mapping.
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 04.08 or 08.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
Forward ‡ MS/BSS to MSC MSC to VLR ‡
message ‡ message name MAP service request ‡
‡ information element 1 <---> parameter 1 ‡
‡ information element 2 <---> parameter 2 ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
Positive‡ MSC to MS/BSS VLR to MSC ‡
result ‡ message name positive response ‡
‡ information element 1 <---> parameter 1 ‡
‡ information element 2 <---> parameter 2 ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
Negative‡ MSC to MS/BSS VLR to MSC ‡
result ‡ message name negative response ‡
‡ cause 1 <---> cause 1 ‡
‡ cause 2 <---> cause 2 ‡
_ _
‡ cause 3 <---> MAP U/P ABORT ‡
_
‡ cause 3 <---> MAP NOTICE ‡
_
‡ cause 3 <---> MAP CLOSE ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜
Equivalent mapping principles apply for operations invoked by the VLR towards the BSS/MS. However,
negative results are generally not received from the BSS/MS but are generated in the MSC. Therefore, for
such operations the interworking for negative results is not normally shown.
---------------------- Page: 12 ----------------------
SIST ETS 300 605 E1:2003
Page 11
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
3.2 Location area updating
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 08.08/04.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _ _
Forward ‡ COMPLETE LAYER 3 INFO MAP UPDATE LOCATION ‡
message ‡ (LOCATION UPDATING AREA request ‡
‡ REQUEST) ‡
‡ ‡
‡ Location area id Previous LA Id ‡
‡ Mobile identity IMSI or TMSI ‡
‡ Mobile station ‡
‡ classmark 1 - ‡ 4
‡ Ciphering key CKSN ‡
‡ seq number ‡
‡ Location update Location update ‡
‡ type type ‡ 3
‡ Cell identifier Target LA Id ‡ 1
‡ Chosen channel - ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Positive‡ DTAP (LOCATION MAP UPDATE LOCATION ‡
results ‡ UPDATING ACCEPT) AREA response ‡
‡ ‡
‡ Location area identity - ‡
‡ Mobile identity - ‡ 5
‡ Follow on proceed - ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Negative‡ DTAP (LOCATION MAP UPDATE LOCATION ‡
results ‡ UPDATING REJECT) AREA response ‡
‡ ‡
‡ IMSI unknown in HLR Unknown subscriber ‡
‡ Network failure Unknown LA ‡ 2
‡ Roaming not allowed: ‡
‡ PLMN not allowed PLMN not allowed ‡
‡ LA not allowed LA not allowed ‡
‡ National roaming not National Roaming ‡
‡ allowed in this LA not allowed ‡
‡ PLMN not allowed Operator ‡
‡ determined barring‡
‡ Illegal MS Illegal subscriber ‡
‡ Illegal ME Illegal equipment ‡
‡ Network failure System Failure ‡
‡ Network failure Unexpected data value‡
_ _
‡ Network failure MAP U/P ABORT ‡
_
‡ Network failure MAP NOTICE ‡
_
‡ Network failure MAP CLOSE ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜
NOTE 1: The Target LA Id parameter is derived by the MSC from the Cell identifier information
element.
NOTE 2: The Unknown LA error is only generated as a result of incorrect information being
inserted by the MSC or BSS.
NOTE 3: This parameter can be used by the VLR to decide whether (eg) Authentication or IMEI
checking is needed.
NOTE 4 As the mobile station classmark (1 or 2) is received by the MSC at the establishment of
every RR connection, this information need not be stored in the VLR, but it is stored in
the MSC as long as the RR connection exists.
NOTE 5 The mobile identity is inserted by the MSC if it is received in a
MAP_FORWARD_NEW_TMSI service. If a TMSI is included, the MS should respond
with a TMSI REALLOCATION COMPLETE message.
---------------------- Page: 13 ----------------------
SIST ETS 300 605 E1:2003
Page 12
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
3.3 Detach IMSI
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 04.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Forward ‡ IMSI DETACH MAP DETACH IMSI ‡
message ‡ INDICATION request ‡
‡ ‡
‡ Mobile identity IMSI or TMSI ‡
‡ ‡
‡ Mobile Station ‡
‡ classmark 1 - ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
Positive‡ ‡
result ‡ ‡ 1
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
Negative‡ ‡
result ‡ ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜
NOTE 1: The forward message is not acknowledged.
Depending on the state of the MS, the IMSI DETACH INDICATION may be carried in either a DTAP
message or a BSSMAP COMPLETE LAYER 3 INFORMATION message.
3.4 Authentication
The message flow for the authentication procedure is shown in figure 2.
MS MSC VLR
_
MAP AUTHENTICATE request
AUTHENTICATION REQUEST <----------------------------------
<-----------------------
AUTHENTICATION RESPONSE
_
-----------------------> MAP AUTHENTICATE response
---------------------------------->
or
_ _
MAP U/P ABORT
---------------------------------->
Figure 2: Authentication operation
The MSC can only act on a MAP_AUTHENTICATE request if an RR connection exists with the MS. If such
a connection does not exist, the MSC shall terminate the MAP procedure with a MAP_U_ABORT. The
same applies if the MS does not respond to an AUTHENTICATION REQUEST message.
---------------------- Page: 14 ----------------------
SIST ETS 300 605 E1:2003
Page 13
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 04.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_
Forward ‡ AUTHENTICATION REQUEST MAP AUTHENTICATE ‡
message ‡ request ‡
‡ ‡
‡ RAND RAND ‡
‡ ‡
‡ Ciphering key seq CKSN ‡
‡ number ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_
Backward‡ AUTHENTICATION REQUEST MAP AUTHENTICATE ‡
result ‡ response ‡
‡ ‡
‡ SRES SRES ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜
If the SRES parameter does not match the value stored in the VLR, then the ongoing MAP procedure shall
be terminated with a cause 'illegal subscriber'. This shall cause the MSC to send an AUTHENTICATION
REJECT message.
3.5 Retrieval of the IMSI from the MS
The VLR may request open identification of an MS with a MAP_PROVIDE_IMSI request.
The mapping of information elements is as follows:
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 04.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Forward ‡ IDENTITY REQUEST MAP PROVIDE IMSI ‡
message ‡ request ‡
‡ Identity type ‡
‡ set to: IMSI ‡ 1
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Backward‡ IDENTITY RESPONSE MAP PROVIDE IMSI ‡
result ‡ Mobile Identity (IMSI) response ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜
NOTE 1: The INVOKE does not carry any parameters. The identity type is inferred from the
invoke name.
The MSC shall return a MAP_PROVIDE_IMSI response with user error "absent subscriber" if:
- there is no RR connection with the MS when the MAP service request is received;
- there is no response from the MS.
---------------------- Page: 15 ----------------------
SIST ETS 300 605 E1:2003
Page 14
ETS 300 605: February 1995 (GSM 09.10 version 4.2.2)
3.6 Reallocation of TMSI
This operation is invoked by the VLR. The MAP_FORWARD_NEW_TMSI request contains the new TMSI
which is forwarded to the MS in the TMSI REALLOCATION COMMAND. When the MS acknowledges the
receipt of the new TMSI, the MSC will return a MAP_FORWARD_NEW_TMSI response to the VLR.
If there is no radio connection to the MS when the MSC receives the MAP service request, the MSC shall
ignore the message.
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 04.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _ _
Forward ‡ TMSI REALLOCATION MAP FORWARD NEW TMSI ‡
message ‡ COMMAND request ‡
‡ ‡
‡ Mobile identity TMSI ‡
‡ ‡
‡ Location area ‡
‡ identification - ‡
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _ _
Backward‡ TMSI REALLOCATION MAP FORWARD NEW TMSI ‡
result ‡ COMPLETE response ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜
3.7 Retrieval of the IMEI from the MS
The VLR may use the MAP_OBTAIN_IMEI service to request the MS to supply its IMEI , or may use the
MAP_CHECK_IMEI service to request the MSC to check the MS's IMEI. For either MAP service the
BSSAP signalling is the same.
The mapping of information elements is as follows:
˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜
‡ 04.08 09.02 ‡Notes
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Forward ‡ (MAP CHECK IMEI request ‡
message ‡ IDENTITY REQUEST ( or ‡
_ _
‡ (MAP OBTAIN IMEI request ‡
‡ Identity type ‡
‡ set to: IMEI ‡ 1
˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜
_ _
Backward‡ (MAP CHECK IMEI response ‡
result ‡ IDENTITY RESPONSE ( or ‡
_ _
‡ (MAP OBTAIN IMEI response ‡
‡ ‡
‡ Mobile Identity IMEI ‡ 2
‡ (IMEI) ‡
˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.