SIST ETS 300 974 E10:2003
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Mobile Application Part (MAP) specification (GSM 09.02 version 5.14.1 Release 1996)
- Abstract
SUBJECT Removal of redundant information from GSM 09.02 Extending the applicability of GMSC Address in ProvideRoamingNumber Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
SIST ETS 300 974 E10:2003 is the Slovenian adoption of ETS 300 974 Edition 10, the ETSI specification for the GSM Mobile Application Part (MAP). It specifies MAP for the Digital cellular telecommunications system (Phase 2+) (GSM), including service definitions, data types, dialogue handling and procedures used by core network nodes such as MSC, HLR, VLR and GMSC.
For engineers, quality managers and buyers, this is the document that tells you how MAP is structured, what information elements it uses, and how the main GSM network procedures are mapped onto transaction-based signalling.
What does SIST ETS 300 974 E10:2003 specify?
SIST ETS 300 974 E10:2003 specifies the MAP protocol for GSM Phase 2+, with the published subject areas of removal of redundant information from GSM 09.02, extension of the applicability of GMSC Address in ProvideRoamingNumber, and clarification of the limit on the length of O-CSI in MAP_RESUME_CALL-HANDLING.
The document is organized from basic network model and signalling rules through service definitions and protocol syntax to detailed procedures and ASN.1 material.
| Annex | What it covers |
|---|---|
| B | Fully expanded ASN.1 source for MAP-Protocol/TCAPMessages and MAP-DialogueInformation |
| C | Deletions and changes to operations, errors, data types, parameters, results and errors |
Clauses 1 to 5 set the scope, define the network entities and interfaces, discuss overload and compatibility, describe the use of SCCP and TC, and define common MAP services and parameters. Clauses 6 to 10 group the MAP services by function: mobility, operation and maintenance, call handling, supplementary services and short message service. Clauses 12 to 14 cover procedures, TC mapping, abstract syntax, application contexts, operation packages, error codes and data types. Clauses 15 to 21 give user procedure guidance, detailed mobility and service procedures, macros, and the ASN.1 modules and examples that support implementation.
What are the key requirements of SIST ETS 300 974 E10:2003?
The core requirement of SIST ETS 300 974 E10:2003 is that MAP implementations use the same service model, dialogue control and data definitions when exchanging GSM signalling between network entities. In practice, that means a node must encode, route and interpret MAP operations and parameters in the way the document defines, or the transaction will not interwork correctly.
1) Follow the GSM network and interface model in clause 2
SIST ETS 300 974 E10:2003 describes the main GSM entities and the interfaces between them, including HLR, VLR, MSC, BSS, GMSC, SMS Gateway MSC, SMS Interworking MSC, EIR, gsmSCF and GCR. This matters because MAP services are tied to those roles: an implementer has to know which node originates a request, which one answers it and which interface carries it.
2) Handle overload and Application Context version selection in clause 3
Clause 3 covers overload control and compatibility, including a strategy for selecting the Application Context (AC) version and managing a version look-up table. In practice, this lets different release levels of GSM equipment exchange MAP traffic more safely, because each side must agree on the same AC version before service dialogue continues.
3) Use SCCP and TC in the prescribed way in clause 4
Clause 4 sets requirements for SCCP class, Sub-System Number (SSN) and SCCP addressing for nodes such as MSC, HLR, VLR, IWMSC and EIR, and it also addresses use of TC. This is the routing and transport basis for MAP: if the SCCP address or class is wrong, the MAP service may reach the wrong node or fail before the service logic starts.
4) Use the common MAP service model and parameter set in clause 5
Clause 5 defines the common MAP services MAP-OPEN, MAP-CLOSE, MAP-DELIMITER, MAP-U-ABORT, MAP-P-ABORT and MAP-NOTICE, plus sequencing rules and the mapping of those services onto TC. It also defines the shared parameters, including identification, numbering, subscriber management, supplementary service, call, radio, authentication, short message, access and signalling system, and system operation parameters.
For readers, this means the document is not just a list of operations. It also defines the common message pieces, such as IMSI, TMSI, IMEI, MS ISDN, roaming number, GMSC Address, VMSC Address, O-CSI, USSD String and trace-related parameters, so different MAP services can use the same coded data consistently.
5) Implement the service families in clauses 6 to 10
The document groups MAP into functional service families:
- mobility services for location management, paging, access management, handover, authentication, security, IMEI handling, subscriber management, identity management, fault recovery and subscriber information
- operation and maintenance services for tracing and IMSI handling
- call handling services for routing information, roaming number handling and call resumption
- supplementary services related services for registration, erasure, activation, deactivation, interrogation, invocation, password handling and USSD
- short message service management services for routing, forwarding, alerting and delivery status
This matters because implementers usually support only some MAP service groups. The clause structure tells you exactly which functional area each operation belongs to.
6) Map MAP procedures to TC dialogue and component handling in clauses 12 and 13
Clauses 12 and 13 describe dialogue establishment, continuation and termination, abort handling, parameter checks and load control, then map MAP onto TC services and component primitives. In practice, this is the interworking rule set: the MAP user and the MAP provider must handle requests, responses, rejects, errors and notices in the correct TC dialogue state.
7) Use the abstract syntax, operation packages and application contexts in clause 14
Clause 14 defines the abstract syntax of MAP, including encoding rules, application contexts, operation packages, operation and error codes, operation and error types, constants and data types. This is the implementation reference for interoperability: it tells you how to encode a MAP message and how to know which operations belong to which package or context.
8) Apply the detailed procedures and macros in clauses 16 to 21
Clauses 16 to 21 provide the detailed procedures for mobility, handover, fault recovery, tracing, subscriber data management, subscriber identity, call handling, supplementary services and short message services, plus the supporting macros. In practice, these clauses are what developers and test teams use to validate state transitions, procedure sequencing and the behaviour of the MSC, VLR, HLR and related nodes.
What terms does SIST ETS 300 974 E10:2003 define?
- Mobile Application Part (MAP) - The GSM signalling application defined by this standard for network procedures such as mobility, call handling, short messages and supplementary services.
- Mobile-services Switching Centre (MSC) - The switching node that handles mobile service control, signalling and procedures such as handover, paging and subscriber tracing.
- Home Location Register (HLR) - The subscriber database that supports location management, service information and many MAP procedures.
- Visitor Location Register (VLR) - The temporary subscriber database used when a subscriber is served in a visited area.
- Gateway MSC (GMSC) - The gateway switching node that obtains routing information and roaming numbers before a call is delivered.
- Signalling Connection Control Part (SCCP) - The signalling transport layer used to address and route MAP messages in the SS7 environment.
- International Mobile Subscriber Identity (IMSI) - The subscriber identity used in location, authentication and identity-related MAP procedures.
Who uses SIST ETS 300 974 E10:2003?
SIST ETS 300 974 E10:2003 is used by GSM core network vendors, system integrators, protocol developers, test labs and network operators. It is especially relevant to teams working on MSC, HLR, VLR, GMSC, BSS, EIR, gsmSCF and SMS-related nodes.
In practice, these users apply it to implement MAP signalling, verify interoperability, configure addressing and application contexts, test mobility and call-control procedures, and check supplementary service and short message flows.
What changed in SIST ETS 300 974 E10:2003 from the previous edition?
Annex C lists the changes carried in this edition. It records deletions of some operations and errors, including operations such as DeregisterMobileSubscriber, RegisterChargingInfo and ForwardSS-Notification, and operations used only on the B-interface, together with the deletion of the error InsufficientBearerCapabilities.
Annex C also records changes to data type definitions such as CUG-Feature, CUG-Info, IMSI, ISDN-AddressString, Password, RequestParameter, SentParameter, SS-Data, SS-Info, SS-SubscriptionOption and SubscriberData, plus changes to parameters and results for operations including InsertSubscriberData, RegisterSS, SendParameters and SendRoutingInfoForSM. It also lists changes to errors for operations such as ActivateSS, DeactivateSS, EraseSS, RegisterSS and SendRoutingInfo.
Which standards are used with SIST ETS 300 974 E10:2003?
The ASN.1 modules in this standard import material from several companion specifications and from ITU-T Recommendation Q.773:
- TCAPMessages from ITU-T Recommendation Q.773 - provides the OPERATION and ERROR framework used by MAP
- MAP-CommonDataTypes - provides shared identities, addresses, service codes and network identifiers
- MAP-ExtensionDataTypes - provides ExtensionContainer and extension mechanisms
- MAP-MS-DataTypes - provides mobility and subscriber data types
- MAP-OM-DataTypes - provides operation and maintenance data types
- MAP-CH-DataTypes - provides call handling data types
- MAP-SS-DataTypes - provides supplementary service data types
- MAP-SM-DataTypes - provides short message service data types
- MAP-ER-DataTypes - provides error parameter data types
- MAP-SS-Code, MAP-BS-Code and MAP-TS-Code - provide supplementary service, bearer service and teleservice code values
- MobileDomainDefinitions - provides object identifiers and module references used by the MAP ASN.1 modules
What does the SIST ETS 300 974 E10:2003 document contain?
SIST ETS 300 974 E10:2003 contains the service model, parameter catalog, ASN.1 definitions, operation packages, application contexts, error definitions and procedure descriptions needed to implement MAP. It also includes SDL descriptions, detailed state-machine style procedures, and macros that support repeated tasks such as open/close handling, access requests, authentication, IMEI handling, subscriber data insertion and tracing.
The later clauses are practical implementation material: they show how to run location updating, handover, fault recovery, call routing, supplementary service handling and short message service procedures across MSC, VLR, HLR and GMSC roles. Annex B supplies fully expanded ASN.1 source, and Annex C records the technical deltas that were applied to the specification.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 974 E10:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital cellular telecommunications system (Phase 2+) (GSM); Mobile Application Part (MAP) specification (GSM 09.02 version 5.14.1 Release 1996)". This standard covers: SUBJECT Removal of redundant information from GSM 09.02 Extending the applicability of GMSC Address in ProvideRoamingNumber Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING
SUBJECT Removal of redundant information from GSM 09.02 Extending the applicability of GMSC Address in ProvideRoamingNumber Clarification of limit on length of O-CSI in MAP_RESUME_CALL-HANDLING
SIST ETS 300 974 E10:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.50 - Global System for Mobile Communication (GSM). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 974 E10:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ±6SHFLILNDFLMDGHOD]DPRELOQH
DSOLNDFLMH 0$3 *60 UD]OLþLFDL]GDMD
Digital cellular telecommunications system (Phase 2+) (GSM); Mobile Application Part
(MAP) specification (GSM 09.02 version 5.14.1 Release 1996)
Ta slovenski standard je istoveten z: ETS 300 974 Edition 10
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 974
TELECOMMUNICATION April 2000
STANDARD Tenth Edition
Source: SMG Reference: RE/SMG-030902QR9
ICS: 33.020
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2+);
Mobile Application Part (MAP) specification
(GSM 09.02 version 5.14.1 Release 1996)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.:+33492944200- Fax:+33493654716
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 2000. All rights reserved.
Page 2
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
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 Standards Making Support Dept." at the address shown on the title page.
Page 3
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
Contents
Intellectual Property Rights.19
Foreword.19
1 Scope .21
1.1 Normative references .21
1.2 Abbreviations .27
2 Configuration of the mobile network.27
2.1 The entities of the mobile system .27
2.1.1 The Home Location Register (HLR).27
2.1.2 The Visitor Location Register (VLR).27
2.1.3 The Mobile-services Switching Centre (MSC).28
2.1.4 The Base Station System (BSS) .28
2.1.5 The Gateway MSC (GMSC).28
2.1.6 The SMS Gateway MSC .28
2.1.7 The SMS Interworking MSC.28
2.1.8 The VBS/VGCS Anchor MSC .29
2.1.9 The Equipment Identity Register (EIR).29
2.1.10 The GSM Service Control Function (gsmSCF) .29
2.1.11 The Group Call Register (GCR) .29
2.2 Configuration of a Public Land Mobile Network (PLMN).29
2.3 Interconnection between PLMNs .29
2.4 The interfaces within the mobile service.29
2.4.1 Interface between the HLR and the VLR (D-interface).29
2.4.2 Interface between the HLR and the gsmSCF (J-interface) .30
2.4.3 Interface between the VLR and its associated MSC(s) (B-interface).30
2.4.4 Interface between VLRs (G-interface).30
2.4.5 Interface between the HLR and the MSC (C-interface).30
2.4.6 Interface between MSCs (E-interface) .30
2.4.7 Interface between the MSC and Base Station Systems (A-interface).30
2.4.8 Interface between MSC and EIR (F-interface) .30
2.4.9 Interface between VBS/VGCS Anchor MSC and GCR (I-interface).30
2.5 Splitting of the data storage .31
3 Overload and compatibility overview.32
3.1 Overload control.32
3.1.1 Overload control for MSC (outside MAP) .32
3.1.2 Overload control for MAP entities.32
3.1.3 Congestion control for Signalling System No. 7 .35
3.2 Compatibility.35
3.2.1 General.35
3.2.2 Strategy for selecting the Application Context (AC) version.35
3.2.2.1 Proposed method .35
3.2.2.2 Managing the version look-up table.36
3.2.2.3 Optimizing the method.37
4 Requirements concerning the use of SCCP and TC.38
4.1 Use of SCCP.38
4.1.1 SCCP Class.38
4.1.2 Sub-System Number (SSN) .38
4.1.3 SCCP addressing.38
4.1.3.1 Introduction .38
4.1.3.2 The Mobile-services Switching Centre (MSC).39
4.1.3.2.1 MSC interaction during handover .39
4.1.3.2.2 MSC for short message routing.39
4.1.3.3 The Home Location Register (HLR) .39
Page 4
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
4.1.3.3.1 During call set-up . 39
4.1.3.3.2 Before location updating completion . 40
4.1.3.3.3 After location updating completion . 40
4.1.3.3.4 VLR restoration . 40
4.1.3.4 The Visitor Location Register (VLR). 41
4.1.3.4.1 Inter-VLR information retrieval . 41
4.1.3.4.2 HLR request . 41
4.1.3.5 The Interworking MSC (IWMSC) for Short Message
Service . 41
4.1.3.6 The Equipment Identity Register (EIR) . 41
4.1.3.7 Summary table. 41
4.2 Use of TC . 42
5 General on MAP services . 44
5.1 Terminology and definitions . 44
5.2 Modelling principles. 44
5.3 Common MAP services. 44
5.3.1 MAP-OPEN service . 45
5.3.2 MAP-CLOSE service . 47
5.3.3 MAP-DELIMITER service . 48
5.3.4 MAP-U-ABORT service . 48
5.3.5 MAP-P-ABORT service . 49
5.3.6 MAP-NOTICE service. 50
5.4 Sequencing of services . 50
5.5 General rules for mapping of services onto TC. 52
5.5.1 Mapping of common services. 52
5.5.2 Mapping of user specific services. 53
5.6 Definition of parameters . 54
5.6.1 Common parameters. 56
5.6.1.1 Invoke Id. 56
5.6.1.2 Linked Id. 56
5.6.1.3 Provider error . 56
5.6.1.4 User error. 56
5.6.2 Numbering and identification parameter. 58
5.6.2.1 IMSI. 58
5.6.2.2 TMSI. 58
5.6.2.3 IMEI. 58
5.6.2.4 Previous location area Id. 58
5.6.2.5 Stored location area Id . 59
5.6.2.6 Current location area Id. 59
5.6.2.7 Target location area Id . 59
5.6.2.8 Target cell Id . 59
5.6.2.9 [Spare]. 59
5.6.2.10 Originating entity number . 59
5.6.2.11 MSC number. 59
5.6.2.12 Target MSC number . 59
5.6.2.13 HLR number. 59
5.6.2.14 VLR number. 59
5.6.2.15 HLR Id . 59
5.6.2.16 LMSI. 59
5.6.2.17 MS ISDN . 59
5.6.2.18 OMC Id. 59
5.6.2.19 Roaming number . 59
5.6.2.20 [Spare]. 60
5.6.2.21 Handover number . 60
5.6.2.22 Forwarded-to number. 60
5.6.2.23 Forwarded-to subaddress . 60
5.6.2.24 Called number. 60
5.6.2.25 Calling number. 60
5.6.2.26 Originally dialled number. 60
5.6.2.27 Service centre address . 60
5.6.2.28 Zone Code . 60
5.6.2.29 MSIsdn-Alert . 60
Page 5
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
5.6.2.30 Location Information .60
5.6.2.31 GMSC Address.60
5.6.2.32 VMSC Address .60
5.6.2.33 Group Id.60
5.6.3 Subscriber management parameters.61
5.6.3.1 Category .61
5.6.3.2 Equipment status.61
5.6.3.3 Extensible Bearer service.61
5.6.3.4 Extensible Teleservice.61
5.6.3.5 Extensible Basic Service Group .61
5.6.3.6 GSM bearer capability .61
5.6.3.7 Subscriber Status .61
5.6.3.8 CUG Outgoing Access indicator.61
5.6.3.9 Operator Determined Barring General Data.61
5.6.3.10 ODB HPLMN Specific Data .62
5.6.3.11 Regional Subscription Data .62
5.6.3.12 Regional Subscription Response.62
5.6.3.13 Roaming Restriction Due To Unsupported Feature .62
5.6.3.14 Extensible SS-Info .62
5.6.3.15 Extensible Forwarding information .62
5.6.3.16 Extensible Forwarding feature.62
5.6.3.17 Extensible SS-Status .63
5.6.3.18 Extensible Forwarding Options.63
5.6.3.19 Extensible No reply condition timer .63
5.6.3.20 Extensible Call barring information.63
5.6.3.21 Extensible Call barring feature.63
5.6.3.22 CUG info.63
5.6.3.23 CUG subscription.63
5.6.3.24 CUG interlock .63
5.6.3.25 CUG index .63
5.6.3.26 CUG feature.64
5.6.3.27 Inter CUG options .64
5.6.3.28 Intra CUG restrictions .64
5.6.3.29 Extensible SS-Data.64
5.6.3.30 Subscriber State .64
5.6.3.31 Requested Info .64
5.6.3.32 Suppression of Announcement .64
5.6.3.33 Suppress T-CSI .65
5.6.3.34 GMSC CAMEL Subscription Info.65
5.6.3.35 VLR CAMEL Subscription Info.65
5.6.3.36 Supported CAMEL Phases.65
5.6.3.37 CUG Subscription Flag.65
5.6.3.38 CAMEL Subscription Info Withdraw .65
5.6.3.39 Voice Group Call Service (VGCS) Data .65
5.6.3.40 Voice Broadcast Service (VBS) Data .65
5.6.4 Supplementary services parameters.65
5.6.4.1 SS-Code .65
5.6.4.2 SS-Status.65
5.6.4.3 SS-Data .66
5.6.4.4 Override Category.66
5.6.4.5 CLI Restriction Option.66
5.6.4.6 Forwarding Options .66
5.6.4.7 No reply condition timer .66
5.6.4.8 - 5.6.4.14 [Spare].66
5.6.4.15 Forwarding information.66
5.6.4.16 Forwarding feature.66
5.6.4.17 [Spare] .67
5.6.4.18 Call barring information.67
5.6.4.19 Call barring feature .67
5.6.4.20 New password .67
5.6.4.21 Current password .67
5.6.4.22 Guidance information.67
5.6.4.23 [Spare] .67
Page 6
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
5.6.4.24 SS-Info . 67
5.6.4.25 - 5.6.4.35 [Spare] . 68
5.6.4.36 USSD Data Coding Scheme. 68
5.6.4.37 USSD String. 68
5.6.4.38 Bearer service. 68
5.6.4.39 Teleservice. 68
5.6.4.40 Basic Service Group . 68
5.6.4.41 eMLPP information. 68
5.6.5 Call parameters . 68
5.6.5.1 Call reference number . 68
5.6.5.2 Interrogation type . 68
5.6.5.3 OR interrogation. 69
5.6.5.4 OR capability. 69
5.6.5.5 Forwarding reason . 69
5.6.5.6 Forwarding interrogation required . 69
5.6.5.7 O-CSI . 69
5.6.6 Radio parameters . 69
5.6.6.1 - 5.6.6.6[Spare]. 69
5.6.6.7 HO-Number Not Required . 69
5.6.7 Authentication parameters. 69
5.6.7.1 Authentication set list . 69
5.6.7.2 Rand. 69
5.6.7.3 Sres. 69
5.6.7.4 Kc . 69
5.6.7.5 [Spare]. 70
5.6.7.6 Cksn. 70
5.6.7.7 Ciphering mode. 70
5.6.8 Short message parameters . 70
5.6.8.1 SM-RP-DA . 70
5.6.8.2 SM-RP-OA . 70
5.6.8.3 MWD status . 70
5.6.8.4 SM-RP-UI. 70
5.6.8.5 SM-RP-PRI . 70
5.6.8.6 SM Delivery Outcome . 70
5.6.8.7 More Messages To Send. 71
5.6.8.8 Alert Reason . 71
5.6.8.9 Absent Subscriber Diagnostic SM. 71
5.6.9 Access and signalling system related parameters. 71
5.6.9.1 BSS-apdu. 71
5.6.9.2 CM service type. 71
5.6.9.3 Access connection status . 71
5.6.9.4 External Signal Information. 71
5.6.9.5 Access signalling information. 71
5.6.9.6 Location update type. 71
5.6.9.7 Protocol ID . 72
5.6.9.8 Network signal information. 72
5.6.10 System operations parameters. 72
5.6.10.1 Network resources . 72
5.6.10.2 Trace reference. 73
5.6.10.3 Trace type . 73
5.7 Representation of a list of a basic parameter in service-primitives. 73
6 Mobility services. 74
6.1 Location management services . 74
6.1.1 MAP_UPDATE_LOCATION_AREA service. 74
6.1.1.1 Definition . 74
6.1.1.2 Service primitives . 74
6.1.1.3 parameter definitions and use. 74
6.1.2 MAP_UPDATE_LOCATION service. 75
6.1.2.1 Definition . 75
6.1.2.2 Service primitives . 75
6.1.2.3 Parameter definitions and use . 75
6.1.3 MAP_CANCEL_LOCATION service. 76
Page 7
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
6.1.3.1 Definition.76
6.1.3.2 Service primitives.76
6.1.3.3 Parameter definitions and use.77
6.1.4 MAP_SEND_IDENTIFICATION service.77
6.1.4.1 Definition.77
6.1.4.2 Service primitives.77
6.1.4.3 Parameter definitions and use.77
6.1.5 MAP_DETACH_IMSI service .78
6.1.5.1 Definition.78
6.1.5.2 Service primitives.78
6.1.5.3 Parameter definitions and use.78
6.1.6 MAP_PURGE_MS service .79
6.1.6.1 Definition.79
6.1.6.2 Service primitives.79
6.1.6.3 Parameter definitions and use.79
6.2 Paging and search .79
6.2.1 MAP_PAGE service .79
6.2.1.1 Definition.79
6.2.1.2 Service primitives.80
6.2.1.3 Parameter definitions and use.80
6.2.2 MAP_SEARCH_FOR_MS service .80
6.2.2.1 Definition.80
6.2.2.2 Service primitives.81
6.2.2.3 Parameter definitions and use.81
6.3 Access management services.81
6.3.1 MAP_PROCESS_ACCESS_REQUEST service .81
6.3.1.1 Definition.81
6.3.1.2 Service primitives.82
6.3.1.3 Parameter definitions and use.82
6.4 Handover services .83
6.4.1 MAP_PREPARE_HANDOVER service.83
6.4.1.1 Definition.83
6.4.1.2 Service primitives.83
6.4.1.3 Parameter use .83
6.4.2 MAP_SEND_END_SIGNAL service.84
6.4.2.1 Definition.84
6.4.2.2 Service primitives.84
6.4.2.3 Parameter use .84
6.4.3 MAP_PROCESS_ACCESS_SIGNALLING service .85
6.4.3.1 Definition.85
6.4.3.2 Service primitives.85
6.4.3.3 Parameter use .85
6.4.4 MAP_FORWARD_ACCESS_SIGNALLING service .85
6.4.4.1 Definition.85
6.4.4.2 Service primitives.85
6.4.4.3 Parameter use .86
6.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service.86
6.4.5.1 Definition.86
6.4.5.2 Service primitives.86
6.4.5.3 Parameter use .86
6.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service .87
6.4.6.1 Definition.87
6.4.6.2 Service primitives.87
6.4.6.3 Parameter use .87
6.4.7 MAP_SEND_HANDOVER_REPORT service.87
6.4.7.1 Definition.87
6.4.7.2 Service primitives.87
6.4.7.3 Parameter use .88
6.5 Authentication management services.88
6.5.1 MAP_AUTHENTICATE service.88
6.5.1.1 Definition.88
6.5.1.2 Service primitives.88
6.5.1.3 Parameter use .88
Page 8
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
6.5.2 MAP_SEND_AUTHENTICATION_INFO service . 89
6.5.2.1 Definition . 89
6.5.2.2 Service primitives . 89
6.5.2.3 Parameter use. 89
6.6 Security management services . 90
6.6.1 MAP_SET_CIPHERING_MODE service. 90
6.6.1.1 Definitions . 90
6.6.1.2 Service primitives . 90
6.6.1.3 Parameter use. 90
6.7 International mobile equipment identities management services. 90
6.7.1 MAP_CHECK_IMEI service. 90
6.7.1.1 Definition . 90
6.7.1.2 Service primitives . 90
6.7.1.3 Parameter use. 91
6.7.2 MAP_OBTAIN_IMEI service. 91
6.7.2.1 Definition . 91
6.7.2.2 Service primitives . 92
6.7.2.3 Parameter use. 92
6.8 Subscriber management services. 92
6.8.1 MAP-INSERT-SUBSCRIBER-DATA service. 92
6.8.1.1 Definition . 92
6.8.1.2 Service primitives . 93
6.8.1.3 Parameter use. 93
Supported CAMEL Phases . 98
6.8.1.4 Basic service information related to supplementary
services . 99
6.8.2 MAP-DELETE-SUBSCRIBER-DATA service. 99
6.8.2.1 Definition . 99
6.8.2.2 Service primitives . 100
6.8.2.3 Parameter use. 100
6.9 Identity management services. 101
6.9.1 MAP-PROVIDE-IMSI service. 101
6.9.1.1 Definition . 101
6.9.1.2 Service primitives . 102
6.9.1.3 Parameter use. 102
6.9.2 MAP-FORWARD-NEW-TMSI service. 102
6.9.2.1 Definition . 102
6.9.2.2 Service primitives . 102
6.9.2.3 Parameter use. 102
6.10 Fault recovery services . 102
6.10.1 MAP_RESET service. 102
6.10.1.1 Definition . 102
6.10.1.2 Service primitives . 103
6.10.1.3 Parameter definition and use . 103
6.10.2 MAP_FORWARD_CHECK_SS_INDICATION service. 103
6.10.2.1 Definition . 103
6.10.2.2 Service primitives . 103
6.10.2.3 Parameter definition and use . 103
6.10.3 MAP_RESTORE_DATA service. 103
6.10.3.1 Definition . 103
6.10.3.2 Service primitives . 104
6.10.3.3 Parameter definitions and use . 104
6.11 Subscriber Information services. 105
6.11.1 MAP-ANY-TIME-INTERROGATION service. 105
6.11.1.1 Definition . 105
6.11.1.2 Service primitives . 105
6.11.1.3 Parameter definition and use . 105
6.11.2 MAP-PROVIDE-SUBSCRIBER-Info service . 106
6.11.2.1 Definition . 106
6.11.2.2 Service primitives . 106
6.11.2.3 Parameter definition and use . 106
7 Operation and maintenance services . 107
Page 9
ETS 300 974 (GSM 09.02 version 5.14.1 Release 1996): April 2000
7.1 Subscriber tracing services.107
7.1.1 MAP-ACTIVATE-TRACE-MODE service.107
7.1.1.1 Definition.107
7.1.1.2 Service primitives.107
7.1.1.3 Parameter use .107
7.1.2 MAP-DEACTIVATE-TRACE-MODE service.108
7.1.2.1 Definition.108
7.1.2.2 Service primitives.108
7.1.2.3 Parameter use .108
7.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service.108
7.1.3.1 Definition.108
7.1.3.2 Service primitives.109
7.1.3.3 Parameter use .109
7.2 Other operation and maintenance services .109
7.2.1 MAP-SEND-IMSI service.109
7.2.1.1 Definition.109
7.2.1.2 Service primitives.109
7.2.1.3 Parameter use .110
8 Call handling services.110
8.1 MAP_SEND_ROUTING_INFORMATION service.110
8.1.1 Definition.110
8.1.2 Service primitives .110
8.1.3 Parameter use.111
8.2 MAP_PROVIDE_ROAMING_NUMBER service.114
8.2.1 Definition.114
8.2.2 Service primitives .114
8.2.3 Parameter use.114
8.3 MAP_RESUME_CALL_HANDLING service.116
8.3.1 Definition.116
8.3.2 Service primitives .116
8.3.3 Parameter use.116
9 Supplementary services related services.117
9.1 MAP_REGISTER_SS service.117
9.1.1 Definition.117
9.1.2 Service primitives .117
9.1.3 Parameter use.117
9.2 MAP_ERASE_SS service.118
9.2.1 Definition.118
9.2.2 Service primitives .119
9.2.3 Parameter use.119
9.3 MAP_ACTIVATE_SS service .120
9.3.1 Definition.120
9.3.2 Service primitives .120
9.3.3 Parameter use.120
9.4 MAP_DEACTIVATE_SS service .121
9.4.1 Definitions.121
9.4.2 Service primitives .122
9.4.3 Parameter use.122
9.5 MAP_INTERROGATE_SS service.123
9.5.1 Definitions.123
9.5.2 Service primitives .123
9.5.3 Parameter use.123
9.6 MAP_INVOKE_SS service .126
9.6.1 Definitions.126
...