You are on page 1of 1118

3GPP TS 09.02 V7.15.

0 (2004-03)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification (Release 1998)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.

1 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

2 3 4

Keywords
GSM, MAP, SS7

3GPP Postal address 3GPP support office address


650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

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.
2004, 3GPP Organizational Partners (ARIB, CCSA, ETSI, T1, TTA, TTC). All rights reserved.

3GPP

3 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

Contents

7 Contents....................................................................................................................................................3 8 Foreword.................................................................................................................................................24 9 1 Scope....................................................................................................................................................25 10 2 References............................................................................................................................................25 11 3 Abbreviations.......................................................................................................................................31 12 4 Configuration of the mobile network...................................................................................................31


13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

4.1 The entities of the mobile system.........................................................................................................................31 4.1.1 The Home Location Register (HLR).................................................................................................................31 4.1.2 The Visitor Location Register (VLR)...............................................................................................................31 4.1.3 The Mobile-services Switching Centre (MSC).................................................................................................32 4.1.4 The Base Station System (BSS)........................................................................................................................32 4.1.5 The Gateway MSC (GMSC).............................................................................................................................32 4.1.6 The SMS Gateway MSC...................................................................................................................................32 4.1.7 The SMS Interworking MSC............................................................................................................................32 4.1.8 The VBS/VGCS Anchor MSC..........................................................................................................................32 4.1.9 The Equipment Identity Register (EIR)............................................................................................................33 4.1.10 The GSM Service Control Function (gsmSCF)..............................................................................................33 4.1.11 The VBS/VGCS Relay MSC..........................................................................................................................33 4.1.12 The Group Call Register (GCR).....................................................................................................................33 4.1.13 The Shared InterWorking Function Server (SIWFS)......................................................................................33 4.1.14 The Serving GPRS Support Node (SGSN).....................................................................................................33 4.1.15 The Gateway GPRS Support Node (GGSN)..................................................................................................33 4.1.16 The Number Portability Location Register (NPLR).......................................................................................34 4.1.17 The Serving Mobile Location Center (SMLC)...............................................................................................34 4.1.18 The Gateway Mobile Location Center (GMLC).............................................................................................34 4.1.19 The Location Measurement Unit (LMU)........................................................................................................34 4.2 Void 36 4.3 Interconnection between PLMNs.........................................................................................................................36 4.4 The interfaces within the mobile service.............................................................................................................36 4.4.1 Interface between the HLR and the VLR (D-interface)....................................................................................36 4.4.2 Interface between the HLR and the gsmSCF (J-interface)...............................................................................36 4.4.3 Interface between the VLR and its associated MSC(s) (B-interface)...............................................................36 4.4.4 Interface between VLRs (G-interface)..............................................................................................................36 4.4.5 Interface between the HLR and the MSC (C-interface)....................................................................................36 4.4.6 Interface between the MSC and the gsmSCF (L-interface)..............................................................................37 4.4.7 Interface between MSCs (E-interface)..............................................................................................................37 4.4.8 Interface between the MSC and Base Station Systems (A-interface)...............................................................37 4.4.9 Interface between MSC and EIR (F-interface).................................................................................................37 4.4.10 Interface between VBS/VGCS Anchor MSC and GCR (I-interface).............................................................37 4.4.11 Interface between the MSC and the SIWF server (K-interface).....................................................................37 4.4.12 Interface between SGSN and HLR (Gr-interface)..........................................................................................37 4.4.13 Interface between SGSN and SMS-GMSC or SMS-IWMSC (Gd-interface)................................................37 4.4.14 Interface between GGSN and HLR (Gc-interface).........................................................................................38 4.4.15 Interface between SGSN and EIR (Gf-interface)............................................................................................38 4.4.16 Interface between SGSN and BSC (Gb-interface)..........................................................................................38 4.4.17 Interface between SGSN and MSC/VLR (Gs-interface)................................................................................38 4.4.17A Interface between SMLC and BSC (Lb interface).......................................................................................38 4.4.18 Interface between SMLC and MSC (Ls interface).........................................................................................38 4.4.18A Interface between SMLC and SMLC (Lp interface)....................................................................................38 4.4.19 Void 38 4.4.20 Interface between GMLC and HLR (Lh interface).........................................................................................38 4.4.21 Interface between GMLC and MSC (Lg interface)........................................................................................38 4.4.22 Interface between LCS Client and GMLC (Le interface)...............................................................................38 4.5 Splitting of the data storage..................................................................................................................................39

3GPP

5 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

61 5 Overload and compatibility overview..................................................................................................39


62 63 64 65 66 67 68 69 70 71 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 108 109 110 111 112 113 114 115 116 117 118 119 120

5.1 Overload control...................................................................................................................................................39 5.1.1 Overload control for MSC (outside MAP)........................................................................................................39 5.1.2 Overload control for MAP entities....................................................................................................................39 5.1.3 Congestion control for Signalling System No. 7..............................................................................................42 5.2 Compatibility........................................................................................................................................................42 5.2.1 General 42 5.2.2 Strategy for selecting the Application Context (AC) version...........................................................................43 5.2.2.1 Proposed method............................................................................................................................................43 5.2.2.2 Managing the version look-up table...............................................................................................................43 5.2.2.3 Optimizing the method...................................................................................................................................44 6.1 Use of SCCP........................................................................................................................................................45 6.1.1 SCCP Class.......................................................................................................................................................45 6.1.2 Sub-System Number (SSN)..............................................................................................................................45 6.1.3 SCCP addressing...............................................................................................................................................45 6.1.3.1 Introduction....................................................................................................................................................45 6.1.3.2 The Mobile-services Switching Centre (MSC)..............................................................................................47 6.1.3.2.1 MSC interaction during handover...............................................................................................................47 6.1.3.2.2 MSC for short message routing...................................................................................................................47 6.1.3.2.3 MSC for location request routing................................................................................................................47 6.1.3.2.4 MSC for LMU Control................................................................................................................................48 6.1.3.3 The Home Location Register (HLR)..............................................................................................................48 6.1.3.3.1 During call set-up........................................................................................................................................48 6.1.3.3.2 Before location updating completion..........................................................................................................48 6.1.3.3.3 After location updating completion............................................................................................................49 6.1.3.3.4 VLR restoration...........................................................................................................................................49 6.1.3.3.5 During Network-Requested PDP Context Activation.................................................................................49 6.1.3.3.6 Before GPRS location updating completion...............................................................................................49 6.1.3.3.7 After GPRS location updating completion.................................................................................................50 6.1.3.3.8 Query for a Location Request ....................................................................................................................50 6.1.3.4 The Visitor Location Register (VLR)............................................................................................................50 6.1.3.4.1 Inter-VLR information retrieval..................................................................................................................50 6.1.3.4.2 HLR request................................................................................................................................................50 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service......................................................................51 6.1.3.6 The Equipment Identity Register (EIR).........................................................................................................51 6.1.3.7 The Shared Inter Working Function (SIWF).................................................................................................51 6.1.3.8 The Serving GPRS Support Node (SGSN)....................................................................................................51 6.1.3.9 The Gateway GPRS Support Node (GGSN).................................................................................................51 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service.............................................................................51 6.1.3.10A Void 52 6.1.3.10A.1 Void 52 6.1.3.10A.2 Void 52 6.1.3.10B The Gateway Mobile Location Center (GMLC) ......................................................................................52 6.1.3.11 Summary table.............................................................................................................................................52 6.2 Use of TC.............................................................................................................................................................54 7.1 Terminology and definitions................................................................................................................................55 7.2 Modelling principles............................................................................................................................................55 7.3 Common MAP services.......................................................................................................................................56 7.3.1 MAP-OPEN service..........................................................................................................................................57 7.3.2 MAP-CLOSE service........................................................................................................................................60 7.3.3 MAP-DELIMITER service...............................................................................................................................60 7.3.4 MAP-U-ABORT service...................................................................................................................................60 7.3.5 MAP-P-ABORT service...................................................................................................................................61 7.3.6 MAP-NOTICE service......................................................................................................................................62 7.4 Sequencing of services.........................................................................................................................................63 7.5 General rules for mapping of services onto TC...................................................................................................64 7.5.1 Mapping of common services...........................................................................................................................64 7.5.2 Mapping of user specific services.....................................................................................................................65

72 6 Requirements concerning the use of SCCP and TC.............................................................................45

107 7 General on MAP services.....................................................................................................................55

3GPP

7 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181

7.6 Definition of parameters......................................................................................................................................66 7.6.1 Common parameters.........................................................................................................................................69 7.6.1.1 Invoke Id 69 7.6.1.2 Linked Id 69 7.6.1.3 Provider error.................................................................................................................................................69 7.6.1.4 User error70 7.6.2 Numbering and identification parameter..........................................................................................................73 7.6.2.1 IMSI 73 7.6.2.2 TMSI 73 7.6.2.3 IMEI 73 7.6.2.4 Previous location area Id................................................................................................................................73 7.6.2.5 Stored location area Id...................................................................................................................................73 7.6.2.6 Current location area Id..................................................................................................................................73 7.6.2.7 Target location area Id...................................................................................................................................73 7.6.2.8 Target cell Id..................................................................................................................................................73 7.6.2.9 Void 73 7.6.2.10 Originating entity number............................................................................................................................73 7.6.2.11 MSC number................................................................................................................................................73 7.6.2.12 Target MSC number.....................................................................................................................................74 7.6.2.13 HLR number.................................................................................................................................................74 7.6.2.14 VLR number.................................................................................................................................................74 7.6.2.15 HLR Id 74 7.6.2.16 LMSI 74 7.6.2.17 MS ISDN......................................................................................................................................................74 7.6.2.18 OMC Id 74 7.6.2.19 Roaming number..........................................................................................................................................74 7.6.2.20 Void 74 7.6.2.21 Handover number.........................................................................................................................................74 7.6.2.22 Forwarded-to number...................................................................................................................................74 7.6.2.23 Forwarded-to subaddress.............................................................................................................................74 7.6.2.24 Called number..............................................................................................................................................74 7.6.2.25 Calling number.............................................................................................................................................74 7.6.2.26 Originally dialled number............................................................................................................................75 7.6.2.27 Service centre address..................................................................................................................................75 7.6.2.28 Zone Code....................................................................................................................................................75 7.6.2.29 MSIsdn-Alert................................................................................................................................................75 7.6.2.30 Location Information...................................................................................................................................75 7.6.2.31 GMSC Address............................................................................................................................................75 7.6.2.32 VMSC Address............................................................................................................................................75 7.6.2.33 Group Id.......................................................................................................................................................75 7.6.2.34 North American Equal Access preferred Carrier Id.....................................................................................75 7.6.2.35 SIWFS Number............................................................................................................................................75 7.6.2.36 B-subscriber address....................................................................................................................................75 7.6.2.37 Serving cell Id..............................................................................................................................................75 7.6.2.38 SGSN number..............................................................................................................................................76 7.6.2.39 SGSN address...............................................................................................................................................76 7.6.2.40 GGSN address..............................................................................................................................................76 7.6.2.41 GGSN number..............................................................................................................................................76 7.6.2.42 APN 76 7.6.2.43 Network Node number.................................................................................................................................76 7.6.2.44 PDP-Type.....................................................................................................................................................76 7.6.2.45 PDP-Address................................................................................................................................................76 7.6.2.46 Additional number.......................................................................................................................................76 7.6.2.47 P-TMSI 76 7.6.2.48 B-subscriber number....................................................................................................................................76 7.6.2.49 B-subscriber subaddress...............................................................................................................................76 7.6.2.50 LMU Number ..............................................................................................................................................77 7.6.2.51 MLC Number ..............................................................................................................................................77 7.6.3 Subscriber management parameters..................................................................................................................77 7.6.3.1 Category 77 7.6.3.2 Equipment status............................................................................................................................................77

3GPP

9 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242

7.6.3.3 Extensible Bearer service...............................................................................................................................77 7.6.3.4 Extensible Teleservice...................................................................................................................................77 7.6.3.5 Extensible Basic Service Group.....................................................................................................................77 7.6.3.6 GSM bearer capability...................................................................................................................................77 7.6.3.7 Subscriber Status............................................................................................................................................77 7.6.3.8 CUG Outgoing Access indicator....................................................................................................................77 7.6.3.9 Operator Determined Barring General Data..................................................................................................77 7.6.3.10 ODB HPLMN Specific Data........................................................................................................................78 7.6.3.11 Regional Subscription Data..........................................................................................................................78 7.6.3.12 Regional Subscription Response..................................................................................................................78 7.6.3.13 Roaming Restriction Due To Unsupported Feature.....................................................................................78 7.6.3.14 Extensible SS-Info.......................................................................................................................................78 7.6.3.15 Extensible Forwarding information.............................................................................................................79 7.6.3.16 Extensible Forwarding feature.....................................................................................................................79 7.6.3.17 Extensible SS-Status....................................................................................................................................79 7.6.3.18 Extensible Forwarding Options....................................................................................................................79 7.6.3.19 Extensible No reply condition timer............................................................................................................79 7.6.3.20 Extensible Call barring information.............................................................................................................79 7.6.3.21 Extensible Call barring feature.....................................................................................................................80 7.6.3.22 CUG info......................................................................................................................................................80 7.6.3.23 CUG subscription.........................................................................................................................................80 7.6.3.24 CUG interlock..............................................................................................................................................80 7.6.3.25 CUG index...................................................................................................................................................80 7.6.3.26 CUG feature.................................................................................................................................................80 7.6.3.27 Inter CUG options........................................................................................................................................81 7.6.3.28 Intra CUG restrictions..................................................................................................................................81 7.6.3.29 Extensible SS-Data.......................................................................................................................................81 7.6.3.30 Subscriber State............................................................................................................................................81 7.6.3.31 Requested Info.............................................................................................................................................81 7.6.3.32 Suppression of Announcement....................................................................................................................81 7.6.3.33 Suppress T-CSI............................................................................................................................................81 7.6.3.34 GMSC CAMEL Subscription Info...............................................................................................................81 7.6.3.35 VLR CAMEL Subscription Info..................................................................................................................81 7.6.3.36 Supported CAMEL Phases..........................................................................................................................82 7.6.3.37 CUG Subscription Flag................................................................................................................................82 7.6.3.38 CAMEL Subscription Info Withdraw..........................................................................................................82 7.6.3.39 Voice Group Call Service (VGCS) Data.....................................................................................................82 7.6.3.40 Voice Broadcast Service (VBS) Data..........................................................................................................82 7.6.3.41 ISDN bearer capability.................................................................................................................................82 7.6.3.42 Lower layer Compatibility...........................................................................................................................82 7.6.3.43 High Layer Compatibility............................................................................................................................82 7.6.3.44 Alerting Pattern............................................................................................................................................82 7.6.3.45 GPRS Subscription Data Withdraw.............................................................................................................82 7.6.3.46 GPRS Subscription Data..............................................................................................................................82 7.6.3.47 QoS-Subscribed............................................................................................................................................82 7.6.3.48 VPLMN address allowed.............................................................................................................................82 7.6.3.49 Roaming Restricted In SGSN Due To Unsupported Feature.......................................................................83 7.6.3.50 Network Access Mode.................................................................................................................................83 7.6.3.51 Mobile Not Reachable Reason.....................................................................................................................83 7.6.3.52 Cancellation Type........................................................................................................................................83 7.6.3.53 All GPRS Data.............................................................................................................................................83 7.6.3.54 Complete Data List Included.......................................................................................................................83 7.6.3.55 PDP Context Identifier.................................................................................................................................83 7.6.3.56 LSA Information..........................................................................................................................................83 7.6.3.57 SoLSA support indicator..............................................................................................................................83 7.6.3.58 LSA Information Withdraw.........................................................................................................................83 7.6.3.59 LMU Indicator.............................................................................................................................................83 7.6.3.60 LCS Information..........................................................................................................................................83 7.6.3.61 GMLC List..................................................................................................................................................84 7.6.3.62 LCS Privacy Exception List ........................................................................................................................84 7.6.3.63 LCS Privacy Exception Parameters.............................................................................................................84

10

3GPP

11 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303

7.6.3.64 External Client List......................................................................................................................................84 7.6.3.65 Internal Client List ......................................................................................................................................84 7.6.3.66 MO-LR List..................................................................................................................................................84 7.6.3.67 Privacy Notification to MS User..................................................................................................................84 7.6.3.68 GMLC List Withdraw .................................................................................................................................84 7.6.4 Supplementary services parameters..................................................................................................................85 7.6.4.1 SS-Code 85 7.6.4.2 SS-Status 85 7.6.4.3 SS-Data 85 7.6.4.4 Override Category..........................................................................................................................................86 7.6.4.5 CLI Restriction Option...................................................................................................................................86 7.6.4.6 Forwarding Options.......................................................................................................................................86 7.6.4.7 No reply condition timer................................................................................................................................86 7.6.4.8 - 7.6.4.14 Void...............................................................................................................................................86 7.6.4.15 Forwarding information...............................................................................................................................86 7.6.4.16 Forwarding feature.......................................................................................................................................86 7.6.4.17 Void 87 7.6.4.18 Call barring information...............................................................................................................................87 7.6.4.19 Call barring feature......................................................................................................................................87 7.6.4.20 New password..............................................................................................................................................87 7.6.4.21 Current password.........................................................................................................................................87 7.6.4.22 Guidance information...................................................................................................................................87 7.6.4.23 Void 88 7.6.4.24 SS-Info 88 7.6.4.25-7.6.4.35 Void...............................................................................................................................................88 7.6.4.36 USSD Data Coding Scheme.........................................................................................................................88 7.6.4.37 USSD String.................................................................................................................................................88 7.6.4.38 Bearer service...............................................................................................................................................88 7.6.4.39 Teleservice...................................................................................................................................................88 7.6.4.40 Basic Service Group.....................................................................................................................................88 7.6.4.41 eMLPP information .....................................................................................................................................88 7.6.4.42 SS-event.......................................................................................................................................................89 7.6.4.43 SS-event data................................................................................................................................................89 7.6.4.44 LCS Privacy Exceptions .............................................................................................................................89 7.6.4.45 Mobile Originating Location Request (MO-LR).........................................................................................89 7.6.5 Call parameters..................................................................................................................................................89 7.6.5.1 Call reference number....................................................................................................................................89 7.6.5.2 Interrogation type...........................................................................................................................................89 7.6.5.3 OR interrogation.............................................................................................................................................89 7.6.5.4 OR capability.................................................................................................................................................90 7.6.5.5 Forwarding reason..........................................................................................................................................90 7.6.5.6 Forwarding interrogation required.................................................................................................................90 7.6.5.7 O-CSI 90 7.6.5.8 Call Direction.................................................................................................................................................90 7.6.5.9 Channel Type.................................................................................................................................................90 7.6.5.10 Chosen Channel...........................................................................................................................................90 7.6.5.11 CCBS Feature...............................................................................................................................................90 7.6.5.12 UU Data90 7.6.5.14 Number Portability Status...........................................................................................................................91 7.6.6 Radio parameters...............................................................................................................................................91 7.6.6.1-7.6.6.6 Void...................................................................................................................................................91 7.6.6.7 HO-Number Not Required.............................................................................................................................91 7.6.7 Authentication parameters................................................................................................................................91 7.6.7.1 Authentication set list.....................................................................................................................................91 7.6.7.2 Rand 91 7.6.7.3 Sres 91 7.6.7.4 Kc 91 7.6.7.5 Void 91 7.6.7.6 Cksn 91 7.6.7.7 Ciphering mode..............................................................................................................................................91 7.6.8 Short message parameters.................................................................................................................................92

12

3GPP

13 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 358 359 360 361 362 363 364

7.6.8.1 SM-RP-DA.....................................................................................................................................................92 7.6.8.2 SM-RP-OA.....................................................................................................................................................92 7.6.8.3 MWD status...................................................................................................................................................92 7.6.8.4 SM-RP-UI......................................................................................................................................................92 7.6.8.5 SM-RP-PRI....................................................................................................................................................92 7.6.8.6 SM Delivery Outcome...................................................................................................................................92 7.6.8.7 More Messages To Send................................................................................................................................92 7.6.8.8 Alert Reason...................................................................................................................................................93 7.6.8.9 Absent Subscriber Diagnostic SM.................................................................................................................93 7.6.8.10 Alert Reason Indicator.................................................................................................................................93 7.6.8.11 Additional SM Delivery Outcome...............................................................................................................93 7.6.8.12 Additional Absent Subscriber Diagnostic SM.............................................................................................93 7.6.8.13 Delivery Outcome Indicator.........................................................................................................................93 7.6.8.14 GPRS Node Indicator...................................................................................................................................93 7.6.8.15 GPRS Support Indicator...............................................................................................................................93 7.6.8.16 SM-RP-MTI.................................................................................................................................................93 7.6.8.17 SM-RP-SMEA.............................................................................................................................................93 7.6.9 Access and signalling system related parameters.............................................................................................93 7.6.9.1 BSS-apdu93 7.6.9.2 CM service type.............................................................................................................................................94 7.6.9.3 Access connection status................................................................................................................................94 7.6.9.4 External Signal Information...........................................................................................................................94 7.6.9.5 Access signalling information........................................................................................................................94 7.6.9.6 Location update type......................................................................................................................................94 7.6.9.7 Protocol ID.....................................................................................................................................................94 7.6.9.8 Network signal information...........................................................................................................................94 7.6.9.9 Call Info 95 7.6.9.10 Additional signal info...................................................................................................................................95 7.6.10 System operations parameters.........................................................................................................................96 7.6.10.1 Network resources........................................................................................................................................96 7.6.10.2 Trace reference.............................................................................................................................................96 7.6.10.3 Trace type.....................................................................................................................................................96 7.6.11 Location Service Parameters...........................................................................................................................96 7.6.11.1 Age of Location Estimate.............................................................................................................................96 7.6.11.2 Void 96 7.6.11.3 Void 96 7.6.11.4 LCS Client ID..............................................................................................................................................96 7.6.11.5 LCS Event....................................................................................................................................................96 7.6.11.6 LCS MLC Data ...........................................................................................................................................97 7.6.11.7 LCS Priority.................................................................................................................................................97 7.6.11.8 LCS QoS......................................................................................................................................................97 7.6.11.9 Void 97 7.6.11.10 Void 97 7.6.11.11 Location Estimate ......................................................................................................................................97 7.6.11.12 Location Type ...........................................................................................................................................97 7.6.11.13 NA-ESRD .................................................................................................................................................98 7.6.11.14 NA-ESRK..................................................................................................................................................98 7.6.11.15 Void 98 7.6.11.16 Privacy Override........................................................................................................................................98 7.6.11.17 Void 98 7.6.11.18 Void 98 7.6.11.19 Void 98 7.7 Representation of a list of a basic parameter in service-primitives.....................................................................98 8.1 Location management services............................................................................................................................98 8.1.1 MAP_UPDATE_LOCATION_AREA service.................................................................................................98 8.1.1.1 Definition.......................................................................................................................................................98 8.1.1.2 Service primitives...........................................................................................................................................99 8.1.1.3 parameter definitions and use.........................................................................................................................99 8.1.2 MAP_UPDATE_LOCATION service............................................................................................................100 8.1.2.1 Definition.....................................................................................................................................................100

357 8 Mobility services..................................................................................................................................98

14

3GPP

15 Release 1998

3GPP TS 09.02 V7.15.0 (2004-03)

365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425

8.1.2.2 Service primitives.........................................................................................................................................100 8.1.2.3 Parameter definitions and use......................................................................................................................100 8.1.3 MAP_CANCEL_LOCATION service...........................................................................................................101 8.1.3.1 Definition.....................................................................................................................................................101 8.1.3.2 Service primitives.........................................................................................................................................102 8.1.3.3 Parameter definitions and use......................................................................................................................102 8.1.4 MAP_SEND_IDENTIFICATION service.....................................................................................................102 8.1.4.1 Definition.....................................................................................................................................................102 8.1.4.2 Service primitives.........................................................................................................................................103 8.1.4.3 Parameter definitions and use......................................................................................................................103 8.1.5 MAP_DETACH_IMSI service.......................................................................................................................103 8.1.5.1 Definition.....................................................................................................................................................103 8.1.5.2 Service primitives.........................................................................................................................................103 8.1.5.3 Parameter definitions and use......................................................................................................................104 8.1.6 MAP_PURGE_MS service.............................................................................................................................104 8.1.6.1 Definition.....................................................................................................................................................104 8.1.6.2 Service primitives.........................................................................................................................................104 8.1.6.3 Parameter definitions and use......................................................................................................................104 8.1.7 MAP_UPDATE_GPRS_LOCATION service................................................................................................105 8.1.7.1 Definition.....................................................................................................................................................105 8.1.7.2 Service primitives.........................................................................................................................................105 8.1.7.3 Parameter definitions and use......................................................................................................................105 8.2 Paging and search...............................................................................................................................................106 8.2.1 MAP_PAGE service.......................................................................................................................................106 8.2.1.1 Definition.....................................................................................................................................................106 8.2.1.2 Service primitives.........................................................................................................................................107 8.2.1.3 Parameter definitions and use......................................................................................................................107 8.2.2 MAP_SEARCH_FOR_MS service................................................................................................................107 8.2.2.1 Definition.....................................................................................................................................................107 8.2.2.2 Service primitives.........................................................................................................................................108 8.2.2.3 Parameter definitions and use......................................................................................................................108 8.3 Access management services.............................................................................................................................108 8.3.1 MAP_PROCESS_ACCESS_REQUEST service...........................................................................................108 8.3.1.1 Definition.....................................................................................................................................................108 8.3.1.2 Service primitives.........................................................................................................................................109 8.3.1.3 Parameter definitions and use......................................................................................................................109 8.4 Handover services..............................................................................................................................................110 8.4.1 MAP_PREPARE_HANDOVER service........................................................................................................110 8.4.1.1 Definition.....................................................................................................................................................110 8.4.1.2 Service primitives.........................................................................................................................................110 8.4.1.3 Parameter use...............................................................................................................................................111 8.4.2 MAP_SEND_END_SIGNAL service............................................................................................................111 8.4.2.1 Definition.....................................................................................................................................................111 8.4.2.2 Service primitives.........................................................................................................................................111 8.4.2.3 Parameter use...............................................................................................................................................112 8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service.....................................................................................112 8.4.3.1 Definition.....................................................................................................................................................112 8.4.3.2 Service primitives.........................................................................................................................................112 8.4.3.3 Parameter use...............................................................................................................................................112 8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service..................................................................................112 8.4.4.1 Definition.....................................................................................................................................................112 8.4.4.2 Service primitives.........................................................................................................................................112 8.4.4.3 Parameter use...............................................................................................................................................113 8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service............................................................................113 8.4.5.1 Definition.....................................................................................................................................................113 8.4.5.2 Service primitives.........................................................................................................................................113 8.4.5.3 Parameter use...............................................................................................................................................113 8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service.................................................................................114 8.4.6.1 Definition.....................................................................................................................................................114 8.4.6.2 Service primitives.........................................................................................................................................114 8.4.6.3 Parameter use...............................................................................................................................................114

16

3GPP

17 Release 1998

10

3GPP TS 09.02 V7.15.0 (2004-03)

426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486

8.4.7 MAP_SEND_HANDOVER_REPORT service..............................................................................................114 8.4.7.1 Definition.....................................................................................................................................................114 8.4.7.2 Service primitives.........................................................................................................................................114 8.4.7.3 Parameter use...............................................................................................................................................115 8.5 Authentication management services.................................................................................................................115 8.5.1 MAP_AUTHENTICATE service...................................................................................................................115 8.5.1.1 Definition.....................................................................................................................................................115 8.5.1.2 Service primitives.........................................................................................................................................115 8.5.1.3 Parameter use...............................................................................................................................................115 8.5.2 MAP_SEND_AUTHENTICATION_INFO service.......................................................................................116 8.5.2.1 Definition.....................................................................................................................................................116 8.5.2.2 Service primitives.........................................................................................................................................116 8.5.2.3 Parameter use...............................................................................................................................................116 8.6 Security management services...........................................................................................................................117 8.6.1 MAP_SET_CIPHERING_MODE service......................................................................................................117 8.6.1.1 Definitions....................................................................................................................................................117 8.6.1.2 Service primitives.........................................................................................................................................117 8.6.1.3 Parameter use...............................................................................................................................................117 8.7 International mobile equipment identities management services......................................................................117 8.7.1 MAP_CHECK_IMEI service..........................................................................................................................117 8.7.1.1 Definition.....................................................................................................................................................117 8.7.1.2 Service primitives.........................................................................................................................................118 8.7.1.3 Parameter use...............................................................................................................................................118 8.7.2 MAP_OBTAIN_IMEI service........................................................................................................................118 8.7.2.1 Definition.....................................................................................................................................................118 8.7.2.2 Service primitives.........................................................................................................................................118 8.7.2.3 Parameter use...............................................................................................................................................119 8.8 Subscriber management services.......................................................................................................................119 8.8.1 MAP-INSERT-SUBSCRIBER-DATA service..............................................................................................119 8.8.1.1 Definition.....................................................................................................................................................119 8.8.1.2 Service primitives.........................................................................................................................................120 8.8.1.3 Parameter use...............................................................................................................................................120 8.8.1.4 Basic service information related to supplementary services......................................................................127 8.8.2 MAP-DELETE-SUBSCRIBER-DATA service.............................................................................................128 8.8.2.1 Definition.....................................................................................................................................................128 8.8.2.2 Service primitives.........................................................................................................................................128 8.8.2.3 Parameter use...............................................................................................................................................128 8.9 Identity management services............................................................................................................................130 8.9.1 MAP-PROVIDE-IMSI service.......................................................................................................................130 8.9.1.1 Definition.....................................................................................................................................................130 8.9.1.2 Service primitives.........................................................................................................................................131 8.9.1.3 Parameter use...............................................................................................................................................131 8.9.2 MAP-FORWARD-NEW-TMSI service.........................................................................................................131 8.9.2.1 Definition.....................................................................................................................................................131 8.9.2.2 Service primitives.........................................................................................................................................131 8.9.2.3 Parameter use...............................................................................................................................................131 8.10 Fault recovery services.....................................................................................................................................131 8.10.1 MAP_RESET service....................................................................................................................................131 8.10.1.1 Definition...................................................................................................................................................131 8.10.1.2 Service primitives.......................................................................................................................................132 8.10.1.3 Parameter definition and use......................................................................................................................132 8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service............................................................................132 8.10.2.1 Definition...................................................................................................................................................132 8.10.2.2 Service primitives.......................................................................................................................................132 8.10.2.3 Parameter definition and use......................................................................................................................132 8.10.3 MAP_RESTORE_DATA service.................................................................................................................132 8.10.3.1 Definition...................................................................................................................................................132 8.10.3.2 Service primitives.......................................................................................................................................133 8.10.3.3 Parameter definitions and use....................................................................................................................133 8.11 Subscriber Information services.......................................................................................................................134 8.11.1 MAP-ANY-TIME-INTERROGATION service...........................................................................................134

18

3GPP

19 Release 1998

11

3GPP TS 09.02 V7.15.0 (2004-03)

487 488 489 490 491 492 493 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546

8.11.1.1 Definition...................................................................................................................................................134 8.11.1.2 Service primitives.......................................................................................................................................134 8.11.1.3 Parameter definition and use......................................................................................................................134 8.11.2 MAP-PROVIDE-SUBSCRIBER-Info service.............................................................................................135 8.11.2.1 Definition...................................................................................................................................................135 8.11.2.2 Service primitives.......................................................................................................................................135 8.11.2.3 Parameter definition and use......................................................................................................................135 9.1 Subscriber tracing services.................................................................................................................................135 9.1.1 MAP-ACTIVATE-TRACE-MODE service...................................................................................................135 9.1.1.1 Definition.....................................................................................................................................................135 9.1.1.2 Service primitives.........................................................................................................................................136 9.1.1.3 Parameter use...............................................................................................................................................136 9.1.2 MAP-DEACTIVATE-TRACE-MODE service..............................................................................................136 9.1.2.1 Definition.....................................................................................................................................................136 9.1.2.2 Service primitives.........................................................................................................................................137 9.1.2.3 Parameter use...............................................................................................................................................137 9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service.......................................................................................137 9.1.3.1 Definition.....................................................................................................................................................137 9.1.3.2 Service primitives.........................................................................................................................................137 9.1.3.3 Parameter use...............................................................................................................................................138 9.2 Other operation and maintenance services.........................................................................................................138 9.2.1 MAP-SEND-IMSI service..............................................................................................................................138 9.2.1.1 Definition.....................................................................................................................................................138 9.2.1.2 Service primitives.........................................................................................................................................138 9.2.1.3 Parameter use...............................................................................................................................................138 10.1 MAP_SEND_ROUTING_INFORMATION service......................................................................................139 10.1.1 Definition......................................................................................................................................................139 10.1.2 Service primitives..........................................................................................................................................139 10.1.3 Parameter use................................................................................................................................................140 10.2 MAP_PROVIDE_ROAMING_NUMBER service.........................................................................................143 10.2.1 Definition......................................................................................................................................................143 10.2.2 Service primitives..........................................................................................................................................144 10.2.3 Parameter use................................................................................................................................................144 10.3 MAP_RESUME_CALL_HANDLING service...............................................................................................146 10.3.1 Definition......................................................................................................................................................146 10.3.2 Service primitives..........................................................................................................................................146 10.3.3 Parameter use................................................................................................................................................146 10.4 MAP_PREPARE_GROUP_CALL service.....................................................................................................147 10.4.1 Definition......................................................................................................................................................147 10.4.2 Service primitives..........................................................................................................................................148 10.4.3 Parameter definitions and use.......................................................................................................................148 10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service............................................................................149 10.5.1 Definitions.....................................................................................................................................................149 10.5.2 Service primitives..........................................................................................................................................149 10.5.3 Parameter definitions and use.......................................................................................................................149 10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service.........................................................................150 10.6.1 Definitions.....................................................................................................................................................150 10.6.2 Service primitives..........................................................................................................................................150 10.6.3 Parameter definitions and use.......................................................................................................................150 10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service.................................................................................151 10.7.1 Definitions.....................................................................................................................................................151 10.7.2 Service primitives..........................................................................................................................................151 10.7.3 Parameter definitions and use.......................................................................................................................151 10.8 MAP_Provide_SIWFS_Number......................................................................................................................151 10.8.1 Definition......................................................................................................................................................151 10.8.2 Service primitive...........................................................................................................................................152 10.8.3 Parameter use................................................................................................................................................152 10.9 MAP_SIWFS_Signalling_Modify...................................................................................................................153

494 9 Operation and maintenance services..................................................................................................135

513 10 Call handling services......................................................................................................................139

20

3GPP

21 Release 1998

12

3GPP TS 09.02 V7.15.0 (2004-03)

547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607

10.9.1 Definition......................................................................................................................................................153 10.9.2 Service primitive...........................................................................................................................................153 10.9.3 Parameter use................................................................................................................................................153 10.10 MAP_SET_REPORTING_STATE service...................................................................................................154 10.10.1 Definition....................................................................................................................................................154 10.10.2 Service primitives........................................................................................................................................154 10.10.3 Parameter use..............................................................................................................................................154 10.11 MAP_STATUS_REPORT service................................................................................................................155 10.11.1 Definition....................................................................................................................................................155 10.11.2 Service primitives........................................................................................................................................155 10.11.3 Parameter use..............................................................................................................................................155 10.12 MAP_REMOTE_USER_FREE service........................................................................................................156 10.12.1 Definition....................................................................................................................................................156 10.12.2 Service primitives........................................................................................................................................156 10.12.3 Parameter use..............................................................................................................................................156 11.1 MAP_REGISTER_SS service.........................................................................................................................157 11.1.1 Definition......................................................................................................................................................157 11.1.2 Service primitives..........................................................................................................................................157 11.1.3 Parameter use................................................................................................................................................158 11.2 MAP_ERASE_SS service................................................................................................................................159 11.2.1 Definition......................................................................................................................................................159 11.2.2 Service primitives..........................................................................................................................................159 11.2.3 Parameter use................................................................................................................................................159 11.3 MAP_ACTIVATE_SS service........................................................................................................................160 11.3.1 Definition......................................................................................................................................................160 11.3.2 Service primitives..........................................................................................................................................160 11.3.3 Parameter use................................................................................................................................................160 11.4 MAP_DEACTIVATE_SS service...................................................................................................................161 11.4.1 Definitions.....................................................................................................................................................161 11.4.2 Service primitives..........................................................................................................................................161 11.4.3 Parameter use................................................................................................................................................162 11.5 MAP_INTERROGATE_SS service................................................................................................................163 11.5.1 Definitions.....................................................................................................................................................163 11.5.2 Service primitives..........................................................................................................................................163 11.5.3 Parameter use................................................................................................................................................163 11.6 MAP_INVOKE_SS service.............................................................................................................................164 11.6.1 Definitions.....................................................................................................................................................164 11.6.2 Service primitives..........................................................................................................................................165 11.6.3 Parameter use................................................................................................................................................165 11.7 MAP_REGISTER_PASSWORD service........................................................................................................165 11.7.1 Definitions.....................................................................................................................................................165 11.7.2 Service primitives..........................................................................................................................................166 11.7.3 Parameter use................................................................................................................................................166 11.8 MAP_GET_PASSWORD service...................................................................................................................166 11.8.1 Definitions.....................................................................................................................................................166 11.8.2 Service primitives..........................................................................................................................................167 11.8.3 Parameter use................................................................................................................................................167 11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service.....................................................................167 11.9.1 Definitions.....................................................................................................................................................167 11.9.2 Service primitives..........................................................................................................................................167 11.9.3 Parameter use................................................................................................................................................168 11.10 MAP_UNSTRUCTURED_SS_REQUEST service......................................................................................168 11.10.1 Definitions...................................................................................................................................................168 11.10.2 Service primitives........................................................................................................................................169 11.10.3 Parameter use..............................................................................................................................................169 11.11 MAP_UNSTRUCTURED_SS_NOTIFY service..........................................................................................170 11.11.1 Definitions...................................................................................................................................................170 11.11.2 Service primitives........................................................................................................................................170 11.11.3 Parameter use..............................................................................................................................................170 11.12 MAP_SS_INVOCATION_NOTIFY.............................................................................................................171

562 11 Supplementary services related services..........................................................................................157

22

3GPP

23 Release 1998

13

3GPP TS 09.02 V7.15.0 (2004-03)

608 609 610 611 612 613 614 615 616 617 618 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 657 658 659 660 661 662 663 664 665 666 667

11.12.1 Definition....................................................................................................................................................171 11.12.2 Service primitives........................................................................................................................................171 11.12.3 Parameter use..............................................................................................................................................171 11.13 MAP_REGISTER_CC_ENTRY service.......................................................................................................171 11.13.1 Definition....................................................................................................................................................171 11.13.2 Service primitives........................................................................................................................................172 11.13.3 Parameter use..............................................................................................................................................172 11.14 MAP_ERASE_CC_ENTRY service.............................................................................................................173 11.14.1 Definition....................................................................................................................................................173 11.14.2 Service primitives........................................................................................................................................173 11.14.3 Parameter use..............................................................................................................................................173 12.1 MAP-SEND-ROUTING-INFO-FOR-SM service...........................................................................................174 12.1.1 Definition......................................................................................................................................................174 12.1.2 Service primitives..........................................................................................................................................174 12.1.3 Parameter use................................................................................................................................................175 12.2 MAP-MO-FORWARD-SHORT-MESSAGE service.....................................................................................176 12.2.1 Definition......................................................................................................................................................176 12.2.2 Service primitives..........................................................................................................................................176 12.2.3 Parameter use................................................................................................................................................176 12.3 MAP-REPORT-SM-DELIVERY-STATUS service.......................................................................................177 12.3.1 Definition......................................................................................................................................................177 12.3.2 Service primitives..........................................................................................................................................177 12.3.3 Parameter use................................................................................................................................................178 12.4 MAP-READY-FOR-SM service.....................................................................................................................179 12.4.1 Definition......................................................................................................................................................179 12.4.2 Service primitives..........................................................................................................................................179 12.4.3 Parameter use................................................................................................................................................179 12.5 MAP-ALERT-SERVICE-CENTRE service....................................................................................................180 12.5.1 Definition......................................................................................................................................................180 12.5.2 Service primitives..........................................................................................................................................180 12.5.3 Parameter use................................................................................................................................................180 12.6 MAP-INFORM-SERVICE-CENTRE service.................................................................................................181 12.6.1 Definition......................................................................................................................................................181 12.6.2 Service primitives..........................................................................................................................................181 12.6.3 Parameter use................................................................................................................................................181 12.7 MAP-SEND-INFO-FOR-MT-SMS service.....................................................................................................182 12.7.1 Definition......................................................................................................................................................182 12.7.2 Service primitives..........................................................................................................................................182 12.7.3 Parameter use................................................................................................................................................182 12.8 MAP-SEND-INFO-FOR-MO-SMS service....................................................................................................183 12.8.1 Definition......................................................................................................................................................183 12.8.2 Service primitives..........................................................................................................................................183 12.8.3 Parameter use................................................................................................................................................183 12.9 MAP-MT-FORWARD-SHORT-MESSAGE service......................................................................................183 12.9.1 Definition......................................................................................................................................................183 12.9.2 Service primitives..........................................................................................................................................184 12.9.3 Parameter use................................................................................................................................................184 13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service...................................................................................185 13.1.1 Definition......................................................................................................................................................185 13.1.2 Service primitives..........................................................................................................................................185 13.1.3 Parameter definition and use.........................................................................................................................185 13.2 MAP_FAILURE_REPORT service.................................................................................................................186 13.2.1 Definition......................................................................................................................................................186 13.2.2 Service primitives..........................................................................................................................................186 13.2.3 Parameter definition and use.........................................................................................................................186 13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service.......................................................................................187 13.3.1 Definition......................................................................................................................................................187 13.3.2 Service primitives..........................................................................................................................................187

619 12 Short message service management services....................................................................................174

656 13 Network-Requested PDP Context Activation services.....................................................................185

24

3GPP

25 Release 1998

14

3GPP TS 09.02 V7.15.0 (2004-03)

668 13.3.3 Parameter definition and use.........................................................................................................................187

669 13A Location Service Management Services........................................................................................188


670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 695 696 697 698 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727

13A.1 MAP-SEND-ROUTING-INFO-FOR-LCS Service......................................................................................188 13A.1.1 Definition...................................................................................................................................................188 13A.1.2 Service Primitives......................................................................................................................................188 13A.1.3 Parameter Use............................................................................................................................................189 13A.2 MAP-PROVIDE-SUBSCRIBER-LOCATION Service...............................................................................190 13A.2.1 Definition...................................................................................................................................................190 13A.2.2 Service Primitives......................................................................................................................................190 13A.2.3 Parameter Definition and Use....................................................................................................................190 13A.3 MAP-SUBSCRIBER-LOCATION-REPORT Service.................................................................................191 13A.3.1 Definition...................................................................................................................................................191 13A.3.2 Service Primitives......................................................................................................................................191 13A.3.3 Parameter Definition and Use....................................................................................................................192 13A.4 Void...............................................................................................................................................................193 13A.4.1 - 13A.4.3 Void............................................................................................................................................193 13A.5 Void...............................................................................................................................................................193 13A.5.1 - 13A.5.3 Void............................................................................................................................................193 13A.6 Void...............................................................................................................................................................194 13A.6.1 - 13A.6.3 Void............................................................................................................................................194 13A.7 Void...............................................................................................................................................................194 13A.7.1 - 13A.7.3 Void............................................................................................................................................194 13A.8 Void 194 13A.8.1 - 13A.8.3 Void............................................................................................................................................194 13A.9 Void...............................................................................................................................................................194 13A.9.1 - 13A.9.3 Void............................................................................................................................................194 14.1 Overview..........................................................................................................................................................194 14.2 Underlying services..........................................................................................................................................194 14.3 Model...............................................................................................................................................................194 14.4 Conventions......................................................................................................................................................195 15.1 Dialogue establishment....................................................................................................................................195 15.1.1 Handling of unknown operations..................................................................................................................195 15.1.2 Receipt of a MAP-OPEN request primitive..................................................................................................196 15.1.3 Receipt of a TC-BEGIN indication...............................................................................................................196 15.1.4 Receipt of a MAP-OPEN response...............................................................................................................199 15.1.5 Receipt of the first TC-CONTINUE ind.......................................................................................................199 15.1.6 Receipt of a TC-END ind..............................................................................................................................199 15.1.7 Receipt of a TC-U-ABORT ind....................................................................................................................199 15.1.8 Receipt of a TC-P-ABORT ind.....................................................................................................................200 15.2 Dialogue continuation......................................................................................................................................200 15.2.1 Sending entity................................................................................................................................................200 15.2.2 Receiving entity............................................................................................................................................200 15.3 Dialogue termination........................................................................................................................................200 15.3.1 Receipt of a MAP-CLOSE request...............................................................................................................200 15.3.2 Receipt of a TC-END indication...................................................................................................................200 15.4 User Abort........................................................................................................................................................201 15.4.1 MAP-U-ABORT request..............................................................................................................................201 15.4.2 TC-U-ABORT ind........................................................................................................................................201 15.5 Provider Abort..................................................................................................................................................201 15.5.1 MAP PM error situation................................................................................................................................201 15.5.2 TC-P-ABORT ind.........................................................................................................................................201 15.5.3 TC-U-ABORT ind........................................................................................................................................201 15.6 Procedures for MAP specific services.............................................................................................................202 15.6.1 Service invocation.........................................................................................................................................202 15.6.2 Service invocation receipt.............................................................................................................................202 15.6.3 Service response............................................................................................................................................203 15.6.4 Receipt of a response....................................................................................................................................203 15.6.4.1 Receipt of a TC-RESULT-NL indication..................................................................................................204

694 14 General.............................................................................................................................................194

699 15 Elements of procedure......................................................................................................................195

26

3GPP

27 Release 1998

15

3GPP TS 09.02 V7.15.0 (2004-03)

728 729 730 731 732 733 734 735 736 737 738 739 740 741 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787

15.6.4.2 Receipt of a TC-RESULT-L indication.....................................................................................................204 15.6.4.3 Receipt of a TC-U-ERROR indication......................................................................................................204 15.6.4.4 Receipt of a TC-INVOKE indication.........................................................................................................205 15.6.4.5 Receipt of a TC-U-REJECT indication......................................................................................................205 15.6.4.6 Receipt of a TC-L-REJECT indication......................................................................................................205 15.6.4.7 Receipt of a TC-L-CANCEL indication....................................................................................................205 15.6.4.8 Receipt of a TC-NOTICE indication.........................................................................................................206 15.6.5 Other events..................................................................................................................................................206 15.6.5.1 Receipt of a TC-U-REJECT.......................................................................................................................206 15.6.5.2 Receipt of a TC-R-REJECT indication......................................................................................................206 15.6.5.3 Receipt of a TC-L-REJECT indication......................................................................................................206 15.6.6 Parameter checks...........................................................................................................................................206 15.6.7 Returning state machines to idle...................................................................................................................207 15.6.8 Load control..................................................................................................................................................207 16.1 Dialogue control...............................................................................................................................................207 16.1.1 Directly mapped parameters.........................................................................................................................207 16.1.2 Use of other parameters of dialogue handling primitives.............................................................................208 16.1.2.1 Dialogue Id.................................................................................................................................................208 16.1.2.2 Application-context-name..........................................................................................................................208 16.1.2.3 User information........................................................................................................................................208 16.1.2.4 Component present.....................................................................................................................................208 16.1.2.5 Termination................................................................................................................................................208 16.1.2.6 P-Abort-Cause............................................................................................................................................208 16.1.2.7 Quality of service.......................................................................................................................................208 16.2 Service specific procedures..............................................................................................................................209 16.2.1 Directly mapped parameters.........................................................................................................................209 16.2.2 Use of other parameters of component handling primitives.........................................................................209 16.2.2.1 Dialogue Id.................................................................................................................................................209 16.2.2.2 Class 209 16.2.2.3 Linked Id....................................................................................................................................................209 16.2.2.4 Operation....................................................................................................................................................209 16.2.2.5 Error 211 16.2.2.6 Parameters..................................................................................................................................................211 16.2.2.7 Time out.....................................................................................................................................................211 16.2.2.8 Last component..........................................................................................................................................211 16.2.2.9 Problem code..............................................................................................................................................211 16.2.2.9.1 Mapping to MAP User Error...................................................................................................................211 16.2.2.9.2 Mapping to MAP Provider Error parameter...........................................................................................211 16.2.2.9.3 Mapping to diagnostic parameter............................................................................................................212 16.3 SDL descriptions..............................................................................................................................................212 17.1 General.............................................................................................................................................................239 17.1.1 Encoding rules...............................................................................................................................................239 17.1.2 Use of TC......................................................................................................................................................239 17.1.2.1 Use of Global Operation and Error codes defined outside MAP...............................................................240 17.1.3 Use of information elements defined outside MAP......................................................................................240 17.1.4 Compatibility considerations........................................................................................................................241 17.1.5 Structure of the Abstract Syntax of MAP.....................................................................................................241 17.1.6 Application Contexts.....................................................................................................................................243 17.2 Operation packages..........................................................................................................................................244 17.2.1 General aspects..............................................................................................................................................244 17.2.2 Packages specifications.................................................................................................................................245 17.2.2.1 Location updating.......................................................................................................................................245 17.2.2.2 Location cancellation.................................................................................................................................245 17.2.2.3 Roaming number enquiry...........................................................................................................................245 17.2.2.4 Information retrieval..................................................................................................................................246 17.2.2.5 Inter-VLR information retrieval.................................................................................................................246 17.2.2.6 IMSI retrieval.............................................................................................................................................246 17.2.2.7 Call control transfer....................................................................................................................................246

742 16 Mapping on to TC services..............................................................................................................207

769 17 Abstract syntax of the MAP protocol...............................................................................................239

28

3GPP

29 Release 1998

16

3GPP TS 09.02 V7.15.0 (2004-03)

788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848

17.2.2.8 - 17.2.2.9 Void...........................................................................................................................................246 17.2.2.10 Interrogation.............................................................................................................................................246 17.2.2.11 Void 247 17.2.2.12 Handover Control.....................................................................................................................................247 17.2.2.13 Subscriber Data management stand alone................................................................................................247 17.2.2.14 Equipment management...........................................................................................................................247 17.2.2.15 Subscriber data management....................................................................................................................247 17.2.2.16 Location register restart............................................................................................................................248 17.2.2.17 Tracing stand-alone..................................................................................................................................248 17.2.2.18 Functional SS handling............................................................................................................................248 17.2.2.19 Tracing.....................................................................................................................................................248 17.2.2.20 Binding.....................................................................................................................................................248 17.2.2.21 Unstructured SS handling........................................................................................................................249 17.2.2.22 MO Short message relay services............................................................................................................249 17.2.2.23 Short message gateway services..............................................................................................................249 17.2.2.24 MT Short message relay services.............................................................................................................250 17.2.2.25 Void 250 17.2.2.26 Message waiting data management..........................................................................................................250 17.2.2.27 Alerting....................................................................................................................................................250 17.2.2.28 Data restoration........................................................................................................................................250 17.2.2.29 Purging.....................................................................................................................................................251 17.2.2.30 Subscriber information enquiry................................................................................................................251 17.2.2.31 Any time information enquiry..................................................................................................................251 17.2.2.32 Group Call Control...................................................................................................................................251 17.2.2.33 Provide SIWFS number...........................................................................................................................251 17.2.2.34 SIWFS Signalling Modify........................................................................................................................252 17.2.2.35 Gprs location updating.............................................................................................................................252 17.2.2.36 Gprs Interrogation....................................................................................................................................252 17.2.2.37 Failure reporting.......................................................................................................................................252 17.2.2.38 GPRS notifying........................................................................................................................................252 17.2.2.39 Supplementary Service invocation notification.......................................................................................253 17.2.2.40 Set Reporting State...................................................................................................................................253 17.2.2.41 Status Report............................................................................................................................................253 17.2.2.42 Remote User Free.....................................................................................................................................253 17.2.2.43 Call Completion.......................................................................................................................................253 17.2.2.44 Location service gateway services...........................................................................................................253 17.2.2.45 Location service enquiry..........................................................................................................................254 17.2.2.45A Location service reporting.....................................................................................................................254 17.2.2.46 Void 254 17.2.2.47 Void 254 17.2.2.48 Void 254 17.3 Application contexts.........................................................................................................................................254 17.3.1 General aspects..............................................................................................................................................254 17.3.2 Application context definitions.....................................................................................................................255 17.3.2.1 Void 255 17.3.2.2 Location Updating......................................................................................................................................255 17.3.2.3 Location Cancellation................................................................................................................................256 17.3.2.4 Roaming number enquiry...........................................................................................................................256 17.3.2.5 Void 256 17.3.2.6 Location Information Retrieval..................................................................................................................256 17.3.2.7 Call control transfer....................................................................................................................................257 17.3.2.8 - 17.3.2.10 Void.........................................................................................................................................257 17.3.2.11 Location registers restart..........................................................................................................................257 17.3.2.12 Handover control......................................................................................................................................257 17.3.2.13 IMSI Retrieval..........................................................................................................................................257 17.3.2.14 Equipment Management..........................................................................................................................257 17.3.2.15 Information retrieval................................................................................................................................258 17.3.2.16 Inter-VLR information retrieval...............................................................................................................258 17.3.2.17 Stand Alone Subscriber Data Management.............................................................................................258 17.3.2.18 Tracing.....................................................................................................................................................258 17.3.2.19 Network functional SS handling..............................................................................................................259

30

3GPP

31 Release 1998

17

3GPP TS 09.02 V7.15.0 (2004-03)

849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 900 901 902 903 904 905 906 907 908 909

17.3.2.20 Network unstructured SS handling..........................................................................................................259 17.3.2.21 Short Message Gateway...........................................................................................................................259 17.3.2.22 Mobile originating Short Message Relay.................................................................................................260 17.3.2.23 Void 260 17.3.2.24 Short message alert..................................................................................................................................260 17.3.2.25 Short message waiting data management................................................................................................260 17.3.2.26 Mobile terminating Short Message Relay................................................................................................261 17.3.2.27 MS purging...............................................................................................................................................261 17.3.2.28 Subscriber information enquiry................................................................................................................261 17.3.2.29 Any time information enquiry..................................................................................................................261 17.3.2.30 Group Call Control...................................................................................................................................262 17.3.2.31 Provide SIWFS Number..........................................................................................................................262 17.3.2.32 Gprs Location Updating...........................................................................................................................262 17.3.2.33 Gprs Location Information Retreival.......................................................................................................262 17.3.2.34 Failure Reporting.....................................................................................................................................262 17.3.2.35 GPRS Notifying.......................................................................................................................................263 17.3.2.36 Supplementary Service invocation notification.......................................................................................263 17.3.2.37 Reporting..................................................................................................................................................263 17.3.2.38 Call Completion.......................................................................................................................................263 17.3.2.39 Location Service Gateway.......................................................................................................................263 17.3.2.40 Location Service Enquiry.........................................................................................................................264 17.3.2.41 Void 264 17.3.2.42 Void 264 17.3.2.43 Void 264 17.3.3 ASN.1 Module for application-context-names.............................................................................................264 17.4 MAP Dialogue Information.............................................................................................................................266 17.5 MAP operation and error codes.......................................................................................................................268 17.6 MAP operation and error types........................................................................................................................273 17.6.1 Mobile Service Operations............................................................................................................................273 17.6.2 Operation and Maintenance Operations........................................................................................................278 17.6.3 Call Handling Operations..............................................................................................................................279 17.6.4 Supplementary service operations.................................................................................................................282 17.6.5 Short message service operations..................................................................................................................286 17.6.6 Errors 288 17.6.7 Group Call operations...................................................................................................................................293 17.6.8 Location service operations...........................................................................................................................294 17.7 MAP constants and data types.........................................................................................................................296 17.7.1 Mobile Service data types.............................................................................................................................296 17.7.2 Operation and maintenance data types..........................................................................................................310 17.7.3 Call handling data types................................................................................................................................311 17.7.4 Supplementary service data types.................................................................................................................317 17.7.5 Supplementary service codes........................................................................................................................321 17.7.6 Short message data types..............................................................................................................................324 17.7.7 Error data types.............................................................................................................................................327 17.7.8 Common data types.......................................................................................................................................331 17.7.9 Teleservice Codes.........................................................................................................................................337 17.7.10 Bearer Service Codes..................................................................................................................................338 17.7.11 Extension data types....................................................................................................................................340 17.7.12 Group Call data types..................................................................................................................................341 17.7.13 Location service data types.........................................................................................................................342 18.1 Introduction......................................................................................................................................................347 18.2 Common aspects of user procedure descriptions.............................................................................................347 18.2.1 General conventions......................................................................................................................................347 18.2.2 Naming conventions......................................................................................................................................347 18.2.3 Convention on primitives parameters...........................................................................................................349 18.2.3.1 Open service...............................................................................................................................................349 18.2.3.2 Close service..............................................................................................................................................349 18.2.4 Version handling at dialogue establishment.................................................................................................350 18.2.4.1 Behaviour at the initiating side..................................................................................................................350 18.2.4.2 Behaviour at the responding side...............................................................................................................350

899 18 General on MAP user procedures.....................................................................................................347

32

3GPP

33 Release 1998

18

3GPP TS 09.02 V7.15.0 (2004-03)

910 18.2.5 Abort Handling..............................................................................................................................................350 911 18.2.6 SDL conventions...........................................................................................................................................350 912 18.3 Interaction between MAP Provider and MAP Users.......................................................................................351

913 19 Mobility procedures.........................................................................................................................351


914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 966 967 968 969

19.1 Location management Procedures...................................................................................................................351 19.1.1 Location updating..........................................................................................................................................357 19.1.1.1 General 357 19.1.1.2 Detailed procedure in the MSC..................................................................................................................364 19.1.1.3 Detailed procedure in the VLR..................................................................................................................368 19.1.1.4 Detailed procedure in the HLR..................................................................................................................387 19.1.1.5 Send Identification.....................................................................................................................................393 19.1.1.5.1 General 393 19.1.1.5.2 Detailed procedure in the VLR...............................................................................................................393 19.1.1.5.3 Detailed procedure in the PVLR.............................................................................................................393 19.1.1.6 The Process Update Location VLR............................................................................................................395 19.1.1.7 The Process Subscriber Present HLR........................................................................................................397 19.1.1.8 Detailed procedure in the SGSN................................................................................................................399 19.1.2 Location Cancellation...................................................................................................................................402 19.1.2.1 General 402 19.1.2.2 Detailed procedure in the HLR..................................................................................................................403 19.1.2.3 Detailed procedure in the VLR..................................................................................................................403 19.1.2.4 Detailed procedure in the SGSN................................................................................................................407 19.1.3 Detach IMSI..................................................................................................................................................410 19.1.3.1 General 410 19.1.3.2 Detailed procedure in the MSC..................................................................................................................410 19.1.3.3 Detailed procedure in the VLR..................................................................................................................410 19.1.4 Purge MS.......................................................................................................................................................413 19.1.4.1 General 413 19.1.4.2 Detailed procedure in the VLR..................................................................................................................413 19.1.4.3 Detailed procedure in the HLR..................................................................................................................414 19.1.4.4 Detailed procedure in the SGSN................................................................................................................414 19.2 Handover procedure.........................................................................................................................................419 19.2.1 General..........................................................................................................................................................419 19.2.2 Handover procedure in MSC-A....................................................................................................................422 19.2.2.1 Basic handover...........................................................................................................................................422 19.2.2.2 Handling of access signalling.....................................................................................................................422 19.2.2.3 Other procedures in stable handover situation...........................................................................................422 19.2.2.4 Subsequent handover.................................................................................................................................422 19.2.2.5 SDL Diagrams............................................................................................................................................423 19.2.3 Handover procedure in MSC-B....................................................................................................................436 19.2.3.1 Basic handover...........................................................................................................................................436 19.2.3.2 Allocation of handover number.................................................................................................................436 19.2.3.3 Handling of access signalling.....................................................................................................................436 19.2.3.4 Other procedures in stable handover situation...........................................................................................436 19.2.3.5 Subsequent handover.................................................................................................................................436 19.2.3.6 SDL Diagrams............................................................................................................................................436 19.2.4 Handover error handling macro....................................................................................................................449 19.2.5 Handover procedure in VLR.........................................................................................................................451 19.2.5.1 Allocation of handover number.................................................................................................................451 19.2.5.2 SDL Diagrams............................................................................................................................................451 19.3 Fault recovery procedures................................................................................................................................454 19.3.1 VLR fault recovery procedures.....................................................................................................................454 19.3.2 HLR fault recovery procedures.....................................................................................................................456 19.3.3 VLR restoration: the restore data procedure in the HLR..............................................................................464 19.4 Macro Insert_Subs_Data_Framed_HLR..........................................................................................................466 20.1 General.............................................................................................................................................................469 20.1.1 Tracing Co-ordinator for the VLR................................................................................................................469 20.1.2 Subscriber Data Management Co-ordinator for the VLR.............................................................................471 20.1.3 Tracing Co-ordinator for the SGSN..............................................................................................................473

965 20 Operation and maintenance procedures............................................................................................469

34

3GPP

35 Release 1998

19

3GPP TS 09.02 V7.15.0 (2004-03)

970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030

20.1.4 Subscriber Data Management Co-ordinator for the SGSN...........................................................................475 20.2 Tracing procedures...........................................................................................................................................477 20.2.1 Procedures in the HLR..................................................................................................................................479 20.2.1.1 Subscriber tracing activation procedure.....................................................................................................479 20.2.1.2 Subscriber tracing deactivation procedure.................................................................................................484 20.2.2 Procedures in the VLR..................................................................................................................................489 20.2.2.1 Subscriber tracing activation procedure.....................................................................................................489 20.2.2.2 Subscriber tracing deactivation procedure.................................................................................................491 20.2.2.3 Subscriber tracing procedure......................................................................................................................493 20.2.3 Procedures in the MSC..................................................................................................................................493 20.2.3.1 Subscriber tracing procedure......................................................................................................................493 20.2.4 Procedures in the SGSN................................................................................................................................493 20.2.4.1 Subscriber tracing activation procedure.....................................................................................................493 20.2.4.2 Subscriber tracing deactivation procedure in SGSN..................................................................................493 20.3 Subscriber data management procedures.........................................................................................................496 20.3.1 Procedures in the HLR..................................................................................................................................497 20.3.1.1 Subscriber deletion procedure....................................................................................................................497 20.3.1.2 Subscriber data modification procedure.....................................................................................................499 20.3.2 Procedures in the VLR..................................................................................................................................504 20.3.2.1 Subscriber deletion procedure....................................................................................................................504 20.3.2.2 Subscriber data modification procedure.....................................................................................................504 20.3.3 Procedures in the SGSN................................................................................................................................507 20.3.3.1 Subscriber deletion procedure....................................................................................................................507 20.3.3.2 Subscriber data modification procedure.....................................................................................................507 20.4 Subscriber Identity procedure..........................................................................................................................510 20.4.1 Subscriber identity procedure in the HLR....................................................................................................510 20.4.2 Subscriber identity procedure in the VLR....................................................................................................512 21.1 General.............................................................................................................................................................514 21.2 Retrieval of routing information......................................................................................................................515 21.2.1 General..........................................................................................................................................................515 21.2.2 Process in the GMSC....................................................................................................................................516 21.2.3 Procedures in the HLR..................................................................................................................................520 21.2.4 Process in the VLR to provide a roaming number........................................................................................526 21.2.5 Process in the VLR to restore subscriber data..............................................................................................528 21.2.6 Process in the VLR to provide subscriber information.................................................................................530 21.2.7 Process in the HLR for Any Time Interrogation...........................................................................................532 21.2.7.1 Process in the gsmSCF...............................................................................................................................532 21.2.3 Process in the HLR........................................................................................................................................532 21.3 Transfer of call handling..................................................................................................................................536 21.3.1 General..........................................................................................................................................................536 21.3.2 Process in the VMSC....................................................................................................................................536 21.3.3 Process in the GMSC....................................................................................................................................539 21.4 Inter MSC Group Call Procedures...................................................................................................................540 21.4.1 General..........................................................................................................................................................540 21.4.2 Process in the Anchor MSC..........................................................................................................................541 21.4.3 Process in the Relay MSC.............................................................................................................................547 21.5 Allocation and modifications of resources in an SIWFS.................................................................................552 21.5.1 General..........................................................................................................................................................552 21.5.2 Process in the VMSC....................................................................................................................................556 21.5.2.1 Allocation of SIWFS resources..................................................................................................................556 21.5.2.2 Modification of SIWFS resources initiated by the user.............................................................................557 21.5.2.3 Modification of SIWFS resources initiated by the SIWFS........................................................................557 21.5.3 Process in the SIWFS....................................................................................................................................565 21.5.3.1 Procedures for allocation of SIWFS resources..........................................................................................565 21.5.3.2 Process for modification of SIWFS resources initiated by the user...........................................................566 21.5.3.3 Process for modification of SIWFS resources initiated by the SIWFS.....................................................566 21.6 Setting of Reporting State................................................................................................................................572 21.6.1 General..........................................................................................................................................................572 21.6.2 Process in the HLR for Set Reporting State stand-alone..............................................................................572 21.6.3 Reporting co-ordinator process in the VLR..................................................................................................575

997 21 Call handling procedures..................................................................................................................514

36

3GPP

37 Release 1998

20

3GPP TS 09.02 V7.15.0 (2004-03)

1031 1032 1033 1034 1035 1036 1037 1038 1039 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091

21.6.4 Process in the VLR to set the reporting state................................................................................................577 21.7 Status Reporting...............................................................................................................................................580 21.7.1 General..........................................................................................................................................................580 21.7.2 Process in the VLR for Status Reporting......................................................................................................580 21.7.3 Process in the HLR for Status Reporting......................................................................................................584 21.8 Remote User Free.............................................................................................................................................589 21.8.1 General..........................................................................................................................................................589 21.8.2 Process in the HLR for Remote User Free....................................................................................................589 21.8.3 Process in the VLR for Remote User Free....................................................................................................592 22.1 Functional supplementary service processes...................................................................................................595 22.1.1 Functional supplementary service process co-ordinator for MSC................................................................595 22.1.2 Functional supplementary service process co-ordinator for VLR................................................................597 22.1.3 Functional supplementary service process co-ordinator for HLR................................................................600 22.1.4 Call completion supplementary service process co-ordinator for HLR........................................................603 22.2 Registration procedure.....................................................................................................................................605 22.2.1 General..........................................................................................................................................................605 22.2.2 Procedures in the MSC..................................................................................................................................605 22.2.3 Procedures in the VLR..................................................................................................................................608 22.2.4 Procedures in the HLR..................................................................................................................................611 22.3 Erasure procedure.............................................................................................................................................614 22.3.1 General..........................................................................................................................................................614 22.3.2 Procedures in the MSC..................................................................................................................................614 22.3.3 Procedures in the VLR..................................................................................................................................615 22.3.4 Procedures in the HLR..................................................................................................................................615 22.4 Activation procedure........................................................................................................................................615 22.4.1 General..........................................................................................................................................................615 22.4.2 Procedures in the MSC..................................................................................................................................616 22.4.3 Procedures in the VLR..................................................................................................................................618 22.4.4 Procedures in the HLR..................................................................................................................................621 22.5 Deactivation procedure....................................................................................................................................624 22.5.1 General..........................................................................................................................................................624 22.5.2 Procedures in the MSC..................................................................................................................................625 22.5.3 Procedures in the VLR..................................................................................................................................625 22.5.4 Procedures in the HLR..................................................................................................................................625 22.6 Interrogation procedure....................................................................................................................................625 22.6.1 General..........................................................................................................................................................625 22.6.2 Procedures in the MSC..................................................................................................................................626 22.6.3 Procedures in the VLR..................................................................................................................................626 22.6.4 Procedures in the HLR..................................................................................................................................630 22.7 Invocation procedure........................................................................................................................................632 22.7.1 General..........................................................................................................................................................632 22.7.2 Procedures in the MSC..................................................................................................................................632 22.7.3 Procedures in the VLR..................................................................................................................................636 22.8 Password registration procedure......................................................................................................................638 22.8.1 General..........................................................................................................................................................638 22.8.2 Procedures in the MSC..................................................................................................................................639 22.8.3 Procedures in the VLR..................................................................................................................................639 22.8.4 Procedures in the HLR..................................................................................................................................639 22.9 Mobile Initiated USSD procedure....................................................................................................................642 22.9.1 General..........................................................................................................................................................642 22.9.2 Procedures in the MSC..................................................................................................................................642 22.9.3 Procedures in the VLR..................................................................................................................................646 22.9.4 Procedures in the HLR..................................................................................................................................651 22.9.5 655 Procedures in the gsmSCF ......................................................................................................................................656 22.10 Network initiated USSD procedure...............................................................................................................658 22.10.1 General........................................................................................................................................................658 22.10.2 Procedure in the MSC.................................................................................................................................658 22.10.3 Procedure in the VLR..................................................................................................................................663 22.10.4 Procedure in the HLR..................................................................................................................................670

1040 22 Supplementary services procedures..................................................................................................595

38

3GPP

39 Release 1998

21

3GPP TS 09.02 V7.15.0 (2004-03)

1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1139 1140 1141 1142 1143 1144 1145 1147 1148 1149 1150 1151

22.11 Common macros for clause 22.......................................................................................................................676 22.11.1 SS Password handling macros....................................................................................................................677 22.11.2 SS Error handling macros...........................................................................................................................680 22.12 Supplementary Service Invocation Notification procedure...........................................................................686 22.12.1 General........................................................................................................................................................686 22.12.2 Procedures in the MSC................................................................................................................................686 22.12.3 Procedures in the gsmSCF..........................................................................................................................688 22.13 Activation of a CCBS request........................................................................................................................690 22.13.1 General........................................................................................................................................................690 22.13.2 Procedure in the VLR..................................................................................................................................690 22.13.3 Procedure in the HLR..................................................................................................................................693 22.14 Deactivation of a CCBS request....................................................................................................................695 22.14.1 General........................................................................................................................................................695 22.14.2 Procedure in the VLR..................................................................................................................................695 22.14.3 Procedure in the HLR..................................................................................................................................698 23.1 General.............................................................................................................................................................700 23.1.1 Mobile originated short message service Co-ordinator for the MSC...........................................................700 23.1.2 Short message Gateway Co-ordinator for the HLR......................................................................................702 23.1.3 Mobile originated short message service Co-ordinator for the SGSN..........................................................704 23.2 The mobile originated short message transfer procedure................................................................................706 23.2.1 Procedure in the servicing MSC...................................................................................................................707 23.2.2 Procedure in the VLR....................................................................................................................................711 23.2.3 Procedure in the interworking MSC.............................................................................................................713 23.2.4 Procedure in the servicing SGSN..................................................................................................................715 23.3 The mobile terminated short message transfer procedure................................................................................719 23.3.1 Procedure in the Servicing MSC...................................................................................................................721 23.3.2 Procedures in the VLR..................................................................................................................................730 23.3.3 Procedures in the HLR..................................................................................................................................734 23.3.4 Procedures in the gateway MSC...................................................................................................................743 23.3.5 Procedure in the Servicing SGSN.................................................................................................................753 23.4 The Short Message Alert procedure.................................................................................................................761 23.4.1 Procedures in the Servicing MSC.................................................................................................................763 23.4.2 Procedures in the VLR..................................................................................................................................765 23.4.2.1 The Mobile Subscriber is present...............................................................................................................765 23.4.2.2 The Mobile Equipment has memory available..........................................................................................765 23.4.3 Procedures in the HLR..................................................................................................................................767 23.4.4 Procedures in the Interworking MSC............................................................................................................770 23.4.5 Procedures in the Servicing SGSN...............................................................................................................772 23.4.5.1 The Mobile Subscriber is present...............................................................................................................772 23.4.5.2 The Mobile Equipment has memory available..........................................................................................772 23.5 The SM delivery status report procedure.........................................................................................................774 23.5.1 Procedures in the HLR..................................................................................................................................774 23.5.2 Procedures in the gateway MSC...................................................................................................................776 23.6 Common procedures for the short message clause..........................................................................................778 23.6.1 The macro Report_SM_Delivery_Stat_HLR................................................................................................778 24.1 General.............................................................................................................................................................780 24.1.1 Process in the HLR for Send Routing Information for GPRS......................................................................780 24.1.2 Process in the GGSN for Send Routing Information for GPRS...................................................................782 24.2.1 Process in the HLR for Failure Report..........................................................................................................784 24.2.2 Process in the GGSN for Failure Report.......................................................................................................786 24.3.1 Process in the GGSN for Note Ms Present For Gprs....................................................................................788 24.3.2 Process in the HLR for Note Ms Present For Gprs.......................................................................................790 25.1 MAP open macros............................................................................................................................................792 25.1.1 Macro Receive_Open_Ind............................................................................................................................792 25.1.2 Macro Receive_Open_Cnf............................................................................................................................792 25.2 Macros to check the content of indication and confirmation primitives..........................................................797 25.2.1 Macro Check_Indication...............................................................................................................................797

1107 23 Short message service procedures....................................................................................................700

1138 24 GPRS process description................................................................................................................780

1146 25 General macro description................................................................................................................792

40

3GPP

41 Release 1998

22

3GPP TS 09.02 V7.15.0 (2004-03)

1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194

25.2.2 Macro Check_Confirmation..........................................................................................................................797 25.3 The page and search macros............................................................................................................................800 25.3.1 Macro PAGE_MSC......................................................................................................................................800 25.3.2 Macro Search_For_MS_MSC.......................................................................................................................801 25.4 Macros for handling an Access Request..........................................................................................................804 25.4.1 Macro Process_Access_Request_MSC........................................................................................................804 25.4.2 Macro Process_Access_Request_VLR.........................................................................................................809 25.4.3 Macro Identification Procedure.....................................................................................................................811 25.5 Authentication macros and processes..............................................................................................................816 25.5.1 Macro Authenticate_MSC............................................................................................................................816 25.5.2 Macro Authenticate_VLR.............................................................................................................................816 25.5.3 Process Obtain_Authentication_Sets_VLR..................................................................................................816 25.5.4 Macro Obtain_Authent_Para_VLR..............................................................................................................816 25.5.5 Process Obtain_Auth_Sets_HLR..................................................................................................................817 25.5.6 Process Obtain_Authent_Para_SGSN..........................................................................................................824 25.6 IMEI Handling Macros....................................................................................................................................828 25.6.1 Macro Check_IMEI_MSC............................................................................................................................828 25.6.2 Macro Check_IMEI_VLR............................................................................................................................828 25.6.3 Process Check_IMEI_EIR............................................................................................................................829 25.6.4 Macro Obtain_IMEI_MSC...........................................................................................................................829 25.6.5 Macro Obtain_IMEI_VLR............................................................................................................................829 25.6.6 Process Check_IMEI_SGSN........................................................................................................................836 25.7 Insert Subscriber Data Macros.........................................................................................................................839 25.7.1 Macro Insert_Subs_Data_VLR.....................................................................................................................839 25.7.2 Process Insert_Subs_Data_Stand_Alone_HLR............................................................................................841 25.7.3 Macro Wait_for_Insert_Subs_Data_Cnf......................................................................................................847 25.7.4 Process Send_Insert_Subs_Data...................................................................................................................849 25.7.5 Macro Insert_Subs_Data_SGSN...................................................................................................................851 25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf..........................................................................................853 25.8 Request IMSI Macros......................................................................................................................................855 25.8.1 Macro Obtain_IMSI_MSC............................................................................................................................855 25.8.2 Macro Obtain_IMSI_VLR............................................................................................................................857 25.9 Tracing macros.................................................................................................................................................859 25.9.1 Macro Trace_Subscriber_Activity_MSC......................................................................................................859 25.9.2 Macro Trace_Subscriber_Activity_VLR......................................................................................................861 25.9.3 Macro Activate_Tracing_VLR.....................................................................................................................863 25.9.4 Macro Control_Tracing_HLR.......................................................................................................................865 25.9.5 Macro Trace_Subscriber_Activity_SGSN....................................................................................................868 25.9.6 Macro Activate_Tracing_SGSN...................................................................................................................870 25.10 Short Message Alert procedures....................................................................................................................872 25.10.1 Subscriber_Present_VLR process...............................................................................................................872 25.10.2 Macro Alert_Service_Centre_HLR............................................................................................................874 25.10.3 The Mobile Subscriber is present................................................................................................................877

1195 Annex A (informative): 1196 1197 Annex B (informative): 1198

Cross-reference for abstract syntaxes of MAP.................................879 Fully expanded ASN.1 sources for abstract syntaxes of MAP.......1046

1199 B.1 Fully Expanded ASN.1 Source of MAP-Protocol/TCAPMessages..............................................1046 1200 B.2 Fully Expanded ASN.1 Source of MAP-DialogueInformation.....................................................1109 1201 Annex C: 1202
Void...........................................................................................................................1113 Clause mapping table........................................................................1114

1203 Annex D (informative): 1204

1205 D.1 Mapping of Clause numbers.........................................................................................................1114

42

3GPP

43 Release 1998

23

3GPP TS 09.02 V7.15.0 (2004-03)

1206 Annex E (informative): 1207 1208

Change History..................................................................................1115

44

3GPP

45 Release 1998

24

3GPP TS 09.02 V7.15.0 (2004-03)

1209

Foreword

1210 This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). 1211 The contents of the present document are subject to continuing work within the TSG and may change following formal 1212 TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an 1213 identifying change of release date and an increase in version number as follows: 1214 1215 1216 1217 1218 1219 1220 1221 1222

Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

46

3GPP

47 Release 1998

25

3GPP TS 09.02 V7.15.0 (2004-03)

1223

1 Scope

1224 It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN 1225 in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified 1226 by CCITT is used to transfer this information. 1227 This Technical Specification (TS) describes the requirements for the signalling system and the procedures needed at the 1228 application level in order to fulfil these signalling needs. 1229 Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols 1230 required by MAP. 1231 MAP consists of a set of MAP services which are provided to MAP service-users by a MAP service-provider.

M A P s e r v ic e - u s e r S e r v ic e In te r f a c e M A P S e r v ic e - p r o v id e r

M A P s e r v ic e - u s e r

1232
1233

Figure 1.1/1: Modelling principles

1234 Clauses 7 to 12 of the present document describe the MAP services. 1235 Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be 1236 used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.). 1237 Clauses 18 to 25 describe the MAP user procedures which make use of MAP services.

1238

2 References
References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] [2] [3] [4] [5] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)". GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) Supported by a GSM Public Land Mobile Network (PLMN)". GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices Supported by a GSM Public Land Mobile Network (PLMN)". GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services".

1239 The following documents contain provisions which, through reference in this text, constitute provisions of the present 1240 document.

1241
1242

1243 1244
1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256

48

3GPP

49 Release 1998

26

3GPP TS 09.02 V7.15.0 (2004-03)

1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299

[6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [26a] [27]

GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects". GSM 02.16: "Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)". GSM 02.41: "Digital cellular telecommunications system (Phase 2+); Operator determined barring". GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1". GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". GSM 02.83 : "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". GSM 02.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 1". GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 1". GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC) supplementary services - Stage 1". GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1". GSM 02.90: "Digital cellular telecommunication system (Phase 2+); Unstructured supplementary services operation - Stage 1". GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". GSM 03.04: "Digital cellular telecommunications system (Phase 2+); Signalling requirements relating to routeing of calls to mobile subscribers". GSM 03.07: "Digital cellular telecommunications system (Phase 2+); Restoration procedures". GSM 03.08: "Digital cellular telecommunications system (Phase 2+); Organisation of subscriber data". GSM 03.09: "Digital cellular telecommunications system (Phase 2+; Handover procedures". GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". GSM 03.12: "Digital cellular telecommunications system (Phase 2+); Location registration procedures". GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network functions". GSM 03.38: "Digital cellular telecommunications system (Phase 2+); Alphabets and language specific information for GSM". GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)". GSM 03.71: Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Functional Description; Stage 2. GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2".

50

3GPP

51 Release 1998

27

3GPP TS 09.02 V7.15.0 (2004-03)

1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344

[28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [37a] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48]

GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2". GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2". GSM 03.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 2". GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2". GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2". GSM 03.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2". GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification General aspects". GSM 04.11: "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". GSM 04.71: Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 location services specification. GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". GSM 04.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 3". GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". GSM 04.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 3". GSM 08.02: "Digital cellular telecommunications system (Phase 2+); Base Station System Mobile-services Switching Centre (BSS - MSC) interface Interface principles". GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS MSC) interface".

52

3GPP

53 Release 1998

28

3GPP TS 09.02 V7.15.0 (2004-03)

1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390

[49] [49a]

GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre Base Station System (MSC - BSS) interface Layer 3 specification". GSM 08.31: Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Serving Mobile Location Center (SMLC) Serving Mobile Location Center (SMLC); SMLC Peer Protocol (SMLCPP). GSM 08.71: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC - BSS) interface Layer 3 specification". GSM 09.01: "Digital cellular telecommunications system (Phase 2+); General network interworking scenarios". GSM 09.02: "Digital cellular telecommunications system (Phase 1); Mobile Application Part (MAP) specification". GSM 09.03: "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)". GSM 09.04: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)". GSM 09.05: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly facility (PAD) access". GSM 09.06: "Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services". GSM 09.07: "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)". GSM 09.08: "Digital cellular telecommunications system (Phase 2+); Application of the Base Station System Application Part (BSSAP) on the E-interface". GSM 09.10: "Digital cellular telecommunications system (Phase 2+); Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". GSM 09.11: "Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services". GSM 09.31: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE). GSM 09.90: "Digital cellular telecommunications system (Phase 2+); Interworking between Phase 1 infrastructure and Phase 2 Mobile Stations (MS)". GSM 12.08: "Digital cellular telecommunications system (Phase 2); Subscriber and Equipment Trace". ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control". ETS 300 136 (1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service description". ETS 300 138 (1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service Digital Subscriber Signalling System No.one (DSS1) protocol".

[49b]

[50] [51] [52]

[53] [54]

[55]

[56]

[57] [58]

[59] [59a] [60] [61] [62] [63] [64]

54

3GPP

55 Release 1998

29

3GPP TS 09.02 V7.15.0 (2004-03)

1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432

[65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87]

ETS 300 287: "Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities (TC) version 2". ETR 060: "Signalling Protocols and Switching (SPS); Guide-lines for using Abstract Syntax Notation One (ASN.1) in telecommunication application protocols". CCITT Recommendation E.164: "Numbering plan for the ISDN era". CCITT Recommendation E.212: "Identification plan for land mobile stations". CCITT Recommendation E.213: "Telephone and ISDN numbering plan for land mobile stations". CCITT Recommendation E.214: "Structuring of the land mobile global title for the signalling connection control part". CCITT Recommendation Q.669: "Interworking between the Digital Subscriber Signalling System Layer 3 protocol and the Signalling System No.7 ISDN User part". CCITT Recommendation Q.711: "Specifications of Signalling System No.7; Functional description of the signalling connection control part". CCITT Recommendation Q.712: "Definition and function of SCCP messages". CCITT Recommendation Q.713: "Specifications of Signalling System No.7; SCCP formats and codes". CCITT Recommendation Q.714: "Specifications of Signalling System No.7; Signalling connection control part procedures". CCITT Recommendation Q.716: "Specifications of Signalling System No.7; Signalling connection control part (SCCP) performances". CCITT Recommendation Q.721 (1988): "Specifications of Signalling System No.7; Functional description of the Signalling System No.7 Telephone user part". CCITT Recommendation Q.722 (1988): "Specifications of Signalling System No.7; General function of Telephone messages and signals". CCITT Recommendation Q.723 (1988): "Specifications of Signalling System No.7; Formats and codes". CCITT Recommendation Q.724 (1988): "Specifications of Signalling System No.7; Signalling procedures". CCITT Recommendation Q.725 (1988): "Specifications of Signalling System No.7; Signalling performance in the telephone application". CCITT Recommendation Q.761 (1988): "Specifications of Signalling System No.7; Functional description of the ISDN user part of Signalling System No.7". CCITT Recommendation Q.762 (1988): "Specifications of Signalling System No.7; General function of messages and signals". CCITT Recommendation Q.763 (1988): "Specifications of Signalling System No.7; Formats and codes". CCITT Recommendation Q.764 (1988): "Specifications of Signalling System No.7; Signalling procedures". CCITT Recommendation Q.767: "Specifications of Signalling System No.7; Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections". CCITT Recommendation Q.771: "Specifications of Signalling System No.7; Functional description of transaction capabilities".

56

3GPP

57 Release 1998

30

3GPP TS 09.02 V7.15.0 (2004-03)

1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473

[88] [89] [90] [91] [92] [93] [94] [95] [96] [97] [98] [99] [100] [101] [102] [103] [104] [105] [106]

CCITT Recommendation Q.772: "Specifications of Signalling System No.7; Transaction capabilities information element definitions". CCITT Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding". CCITT Recommendation Q.774: "Specifications of Signalling System No.7; Transaction capabilities procedures". CCITT Recommendation Q.775: "Specifications of Signalling System No.7; Guide-lines for using transaction capabilities". CCITT Recommendation X.200: "Reference Model of Open systems interconnection for CCITT Applications". CCITT Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One (ASN.1)". CCITT Recommendation X.209 (1988): "Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)". CCITT Recommendation X.210: "Open systems interconnection layer service definition conventions". GSM 09.02: "Digital cellular telecommunications system (Phase 2); Mobile Application Part (MAP) specification. GSM 03.18: "Digital cellular telecommunications system (Phase 2+); Basic Call Handling". GSM 03.78: "Digital cellular telecommunications system (Phase 2+); Customised Applications for Mobile network Enhanced Logic (CAMEL) - Stage 2. GSM 03.79: "Digital cellular telecommunications system (Phase 2+); Support of Optimal Routeing (SOR) - Stage 2. GSM 03.68: "Digital cellular telecommunications system (Phase 2+); - Stage 2". GSM 03.69: "Digital cellular telecommunications system (Phase 2+); - Stage 2". ANSI T1.113: "Signaling System No. 7 (SS7) - ISDN User Part". GSM 03.54 "Digital cellular telecommunications system (Phase 2+); Stage 2 Description for the use of a Shared Inter Working Function (SIWF) in a GSM PLMN". GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS) Description; Stage 2". GSM 09.60: "Digital cellular telecommunications system (Phase 2+), General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". GSM 09.18: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification". GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". GSM 03.66: "Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); Technical Realisation Stage 2". ANSI T1.112 (1996 ): "Telecommunication Signaling No. 7 Signaling Connection Control Part (SCCP)".

[107] [108] [109]

58

3GPP

59 Release 1998

31

3GPP TS 09.02 V7.15.0 (2004-03)

1474

3 Abbreviations

1475 Abbreviations used in the present document are listed in GSM 01.04.

1476 1477

4 Configuration of the mobile network


4.1 The entities of the mobile system

1478 To provide the mobile service as it is defined, it is necessary to introduce some specific functions. These functional 1479 entities can be implemented in different equipments or integrated. In any case, exchanges of data occur between these 1480 entities.

1481
1482 1483 1484 1485 1486

4.1.1 The Home Location Register (HLR)


This functional entity is a data base in charge of the management of mobile subscribers. A PLMN may contain one or several HLRs; it depends on the number of mobile subscribers, on the capacity of the equipment and on the organization of the network. All subscription data are stored there. The main information stored there concerns the location of each MS in order to be able to route calls to the mobile subscribers managed by each HLR. All management interventions occur on this data base. The HLRs have no direct control of MSCs.

1487 Two numbers attached to each mobile subscription are stored in the HLR: 1488 1489

IMSI; MSISDN.

1490 The data base contains other information such as: 1491 1492 1493 1494 1495

location information (VLR number); basic telecommunication services subscription information; service restrictions (e.g. roaming limitation); supplementary services; the tables contain the parameters attached to these services; GPRS subscription data and routeing information.

1496 The organization of the subscriber data is detailed in GSM 03.08.

1497
1498 1499 1500 1501

4.1.2 The Visitor Location Register (VLR)


An MS roaming in an MSC area is controlled by the Visitor Location Register in charge of this area. When an MS appears in a location area it starts a location updating procedure. The MSC in charge of that area notices this registration and transfers to the Visitor Location Register the identity of the location area where the MS is situated. A VLR may be in charge of one or several MSC areas.

1502 The VLR also contains the information needed to handle the calls set up or received by the MSs registered in its data 1503 base (in some cases the VLR may have to obtain additional information from the HLR); the following elements can be 1504 found in its tables: 1505 1506 1507 1508 1509

the IMSI; the MSISDN; the TMSI, if applicable; the location area where the MS has been registered. This will be used to call the station; supplementary service parameters.

60

3GPP

61 Release 1998

32

3GPP TS 09.02 V7.15.0 (2004-03)

1510 The information is passed between VLR and HLR by the procedures described in GSM 03.12. 1511 The organization of the subscriber data is detailed in GSM 03.08.

1512
1513 1514 1515 1516 1517 1518

4.1.3 The Mobile-services Switching Centre (MSC)


The Mobile-services Switching Centre is an exchange which performs all the switching functions for MSs located in a geographical area designated as the MSC area. The main difference between an MSC and an exchange in a fixed network is that the MSC has to take into account the impact of the allocation of radio resources and the mobile nature of the subscribers and has to perform, for example, the following procedures: procedures required for the location registration (see GSM 03.12); procedures required for hand-over (see GSM 03.09).

1519

4.1.4 The Base Station System (BSS)


by the MSC through an interface (A-interface) with the functionality described in GSM 08.02; by the SGSN through an interface (Gb-interface) with the functionality described in GSM 03.60.

1520 The BSS is the sub-system of Base Station equipment (transceivers, controllers, etc...) which is viewed 1521 1522

1523

4.1.5 The Gateway MSC (GMSC)

1524 In the case of incoming calls to the PLMN, if the fixed network is unable to interrogate the HLR, the call is routed to an 1525 MSC. This MSC will interrogate the appropriate HLR and then route the call to the MSC where the MS is located. The 1526 MSC which then performs the routing function to the actual location of the mobile is called the Gateway MSC. 1527 The choice of which MSCs can act as Gateway MSCs is a network operator matter (e.g. all MSCs or some designated 1528 MSCs). 1529 If the call is a voice group/broadcast call it is routed directly from the GMSC to the VBS/VGCS Anchor MSC, based on 1530 information (VBS/VGCS call reference) contained in the dialled number. See also GTSs 03.68 and 03.69. 1531 See also GSM 03.04.

1532

4.1.6 The SMS Gateway MSC

1533 The SMS GMSC is the interface between the Mobile Network and the network which provides access to the Short 1534 Message Service Centre, for short messages to be delivered to MSs. 1535 The choice of which MSCs can act as SMS Gateway MSCs is a network operator matter (e.g. all MSCs or some 1536 designated MSCs).

1537

4.1.7 The SMS Interworking MSC

1538 The SMS IWMSC is the interface between the Mobile Network and the network which provides access to the Short 1539 Message Service Centre, for short messages submitted by MSs. 1540 The choice of which MSCs can act as SMS Interworking MSCs is a network operator matter (e.g. all MSCs or some 1541 designated MSCs).

1542

4.1.8 The VBS/VGCS Anchor MSC

1543 The voice broadcast/group call anchor MSC obtains from the associated GCR all relevant attributes and controls in turn 1544 all cells in its area, VBS/VGCS Relay-MSCs and dispatchers belonging to a given group call.

62

3GPP

63 Release 1998

33

3GPP TS 09.02 V7.15.0 (2004-03)

1545

4.1.9 The Equipment Identity Register (EIR)

1546 This functional unit is a data base in charge of the management of the equipment identities of the MSs; see also 1547 GSM 02.16.

1548

4.1.10 The GSM Service Control Function (gsmSCF)

1549 This functional entity contains the CAMEL service logic to implement OSS. It interfaces with the gsmSSF and the 1550 HLR; see also TS GSM 03.78.

1551

4.1.11 The VBS/VGCS Relay MSC

1552 The voice broadcast/group call relay MSC obtains from the associated anchor MSC all relevant attributes and controls 1553 in turn all cells in its area belonging to a given group call.

1554

4.1.12 The Group Call Register (GCR)

1555 This functional unit is a data base in charge of the management of attributes related to the establishment of Voice 1556 Broadcast Calls and Voice Group Calls

1557
1558 1559 1560 1561

4.1.13 The Shared InterWorking Function Server (SIWFS)


A Shared Inter Working Function is a network function that may be used by any MSC in the same PLMN to provide interworking for a data/fax call. Whereas an IWF can only be used by its MSC, the SIWF can be used by several other network nodes e.g. any MSC within the same PLMN (the concept is not limited to a certain number of MSCs). SIWF is applied to data services in GSM Phase 2 and GSM Phase 2+ (as defined in GSM 02.02, GSM 02.03 and GSM 02.34).

1562 The usage of an SIWF requires no additional manipulation at the MS. 1563 An IWF provides specific functions associated with the visited MSC for the interworking with other networks. It 1564 comprises signalling and traffic channel related functions. The traffic channel related functions are provided by an Inter 1565 Working Unit (IWU). 1566 The SIWF concept is that it provides specific functions for the interworking with other networks. It comprises 1567 signalling and traffic channel related functions. Whereas the signalling related functions are associated with the visited 1568 MSC, the IWU providing the traffic channel related functions has another physical location. 1569 The entity that contains all additional functions needed in the visited MSC to provide the SIWF is called SIWF 1570 Controller (SIWFC). The entity where the IWU is located is called SIWF Server (SIWFS). The Interface between a 1571 visited MSC and a SIWFS is called the K Interface. 1572 SIWFS can be provided by a MSC (MSC/SIWFS) or by another network entity (stand alone SIWFS).

1573

4.1.14 The Serving GPRS Support Node (SGSN)

1574 This functional unit keeps track of the individual MSs' location and performs security functions and access control; see 1575 also GSM 03.60.

1576

4.1.15 The Gateway GPRS Support Node (GGSN)

1577 This functional unit provides interworking with external packet-switched networks, network screens and routing of the 1578 Network Requested PDP-context activation;see also GSM 03.60.4.2 "Configuration of a Public Land Mobile Network 1579 (PLMN)". 1580 1581 1582 1583 1584

The basic configuration of a Public Land Mobile Network is presented in figure 4.2/1. In this figure the most general solution is described in order to define all the possible interfaces which can be found in any PLMN. The specific implementation in each network may be different: some particular functions may be implemented in the same equipment and then some interfaces may become internal interfaces. In any case the configuration of a PLMN must have no impact on the relationship with the other PLMNs.

64

3GPP

65 Release 1998

34

3GPP TS 09.02 V7.15.0 (2004-03)

1585 In this configuration, all the functions are considered implemented in different equipments. Therefore, all the interfaces 1586 are external and need the support of the Mobile Application Part of the Signalling System No. 7 to exchange the data 1587 necessary to support the mobile service. From this configuration, all the possible PLMN organizations can be deduced.

1588

4.1.16 The Number Portability Location Register (NPLR)

1589 This functional unit provides routing information necessary in some Mobile Number Portability environments in order 1590 to route calls for ported mobile subscribers. For details see also GSM 03.66 [108].

1591
1592 1593 1594 1595 1596 1597 1598 1599 1600

4.1.17 The Serving Mobile Location Center (SMLC)


An SMLC is a database and processing entity that manages the procedures for obtaining the geographic location of a target MS in the coverage area served by the SMLC. In managing the location procedures, the SMLC chooses the positioning method and provides data and instructions to the LMUs or target MS that perform the actual location measurements associated with the chosen method. The SMLC also verifies any location estimate computed by the target MS or computes a location itself from measurements provided to it by the target MS or LMUs. An SMLC also manages a set of LMUs in its coverage area whose purpose is to provide location measurements and location assistance data to the SMLC to compute, or assist in computing, location estimates for target MSs. Management functions performed by an SMLC on behalf of its LMUs include maintaining the status and current serving MSC of each LMU and supporting O&M procedures,

1601 The database in an SMLC contains data necessary for choosing an appropriate position method and any parameters 1602 associated with this method for a target MS in any serving cell, for computing or verifying location estimates and for 1603 managing its LMUs. 1604 An SMLC may be either NSS based or BSS based. An NSS based SMLC supports positioning and management of its 1605 LMUs via interaction with one or more MSCs using the Ls interface. A BSS based SMLC supports positioning and 1606 management of its LMUs via interaction with one or more BSCs using the Lb interface.

1607
1608 1609 1610 1611 1612 1613

4.1.18 The Gateway Mobile Location Center (GMLC)


The GMLC provides access to location services (LCS) for LCS clients external to a PLMN. A GMLC may also support access to location services from LCS clients internal to its own PLMN. The GMLC allows an LCS client to issue location requests for certain target MSs; it then conveys these requests to the VMSC currently serving each target MS and passes back the location results to the LCSclient. Any target MS whose location is requested may belong to either the GMLCs own PLMN or another PLMN and may currently be served by either the GMLCs own PLMN or another PLMN.

1614
1615 1616 1617 1618

4.1.19 The Location Measurement Unit (LMU)


The LMU is the logical network entity that performs location measurements in the VPLMN in order to either position a target MS or provide assistance data to be used in conjunction with other location measurements. An LMU is controlled by an SMLC in the VPLMN from which location commands can be received and to which any location measurements are returned.

66

3GPP

67 Release 1998

35

3GPP TS 09.02 V7.15.0 (2004-03)

AuC VLR HLR

VLR

EIR GSM SCF GCR

Database level SP SP J D SP C SP Signalling level ISDN or PSTN Switched Network SP SP B SP E SP I G SP

SP

X
GMCS

MSC Area

S M S G M CS

IWMSC

MSC

MSC Area
BSC

Cell
BTS BTS

LE

MSC

Cell

A
PLMN

BSC

BTS

Cell

Network level

Abis

User level

Mobile station (MS)

1619
1620

Figure 4.2/1: Configuration of a PLMN

68

3GPP

69 Release 1998

36

3GPP TS 09.02 V7.15.0 (2004-03)

1621 1622

4.2 Void 4.3 Interconnection between PLMNs

1623 Since the configuration of a PLMN does not have any impact on other PLMNs, the signalling interfaces specified can 1624 be implemented both between the entities within a PLMN and between different PLMNs.

1625 1626
1627 1628 1629 1630 1631 1632

4.4 The interfaces within the mobile service


4.4.1 Interface between the HLR and the VLR (D-interface)
This interface is used to exchange the data related to the location of the MS and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to set up or to receive calls within the whole service area. To support that purpose the location registers have to exchange data. The VLR informs the HLR on the registration of a MS managed by the latter and provides it with the relevant location information. The HLR sends to the VLR all the data needed to support the service to the MS. The HLR then calls the previous VLR to inform it that it can cancel the location registration of this station because of the roaming of the mobile.

1633 Exchanges of data may also occur when the mobile subscriber requires a particular service, when he wants to change 1634 some data attached to his subscription or when some parameters of the subscription are modified by administrative 1635 means.

1636
1637 1638 1639 1640

4.4.2 Interface between the HLR and the gsmSCF (J-interface)


This interface is used by the gsmSCF to request information from the HLR (via the Any-time Interrogation function) or to allow call independent related network- or user-initiated interaction between an MS and the gsmSCF (via the USSD function). Support of the gsmSCF-HLR interface is a network operator option. As a network operator option, the HLR may refuse to provide the information requested by the gsmSCF.

1641 1642
1643 1644 1645 1646 1647 1648

4.4.3 Interface between the VLR and its associated MSC(s) (Binterface)
The VLR is the location and management data base for the MSs roaming in the area controlled by the associated MSC(s). Whenever the MSC needs data related to a given MS currently located in its area, it interrogates the VLR. When a MS initiates a location updating procedure with an MSC, the MSC informs its VLR which stores the relevant information in its tables. This procedure occurs whenever a mobile roams to another location area. Also, for instance when a subscriber activates a specific supplementary service or modifies some data attached to a service, the MSC transfers (via the VLR) the request to the HLR, which stores these modifications and updates the VLR if required.

1649 However, this interface is not fully operational specified. It is strongly recommended not to implement the B-interface 1650 as an external interface.

1651

4.4.4 Interface between VLRs (G-interface)

1652 When an MS initiates a location updating using TMSI, the VLR can fetch the IMSI and authentication set from the 1653 previous VLR.

1654

4.4.5 Interface between the HLR and the MSC (C-interface)

1655 When the fixed network is not able to perform the interrogation procedure needed to set up a call to a mobile subscriber, 1656 the Gateway MSC has to interrogate the HLR of the called subscriber to obtain the roaming number of the called MS 1657 (see GSM 03.04). 1658 To forward a short message to a mobile subscriber, the SMS Gateway MSC has to interrogate the HLR to obtain the 1659 MSC number where the MS is located.

70

3GPP

71 Release 1998

37

3GPP TS 09.02 V7.15.0 (2004-03)

1660

4.4.6 Interface between the MSC and the gsmSCF (L-interface)

1661 When one of the following Supplementary Services, CD, ECT or MPTY, is invoked in the MSC a notification shall be 1662 sent towards the gsmSCF.

1663

4.4.7 Interface between MSCs (E-interface)

1664 When a MS moves from one MSC area to another during a call, a handover procedure has to be performed in order to 1665 continue the communication. For that purpose the MSCs involved have to exchange data to initiate and then to realize 1666 the operation. 1667 This interface is also used to forward short messages, to perform location for a target MS for which handover has 1668 occurred on an established call and to transfer LCS messages to and from an LMU for which handover of a signalling 1669 channel has occurred. 1670 This interface is also used to transfer information for inter-MSC VBS/VGCS calls .

1671 1672

4.4.8 Interface between the MSC and Base Station Systems (Ainterface)

1673 The description of this interface is contained in the GSM 08-series of MSs. 1674 The BSS-MSC interface carries information concerning: 1675 1676 1677

BSS management; call handling; location management.

1678

4.4.9 Interface between MSC and EIR (F-interface)

1679 This interface is used when an MSC wants to check an IMEI.

1680 1681

4.4.10 Interface between VBS/VGCS Anchor MSC and GCR (Iinterface)

1682 This is an internal interface.

1683 1684

4.4.11 Interface between the MSC and the SIWF server (Kinterface)

1685 When a MSC detects that it can not provide the requested IW function, resources from an SIWF server can be used. 1686 This interface is used to allocate resources in that SIWF server and establish required physical connections to that 1687 server.

1688

4.4.12 Interface between SGSN and HLR (Gr-interface)

1689 The description of this interface is contained in the GSM 03.60.

1690 1691

4.4.13 Interface between SGSN and SMS-GMSC or SMS-IWMSC (Gd-interface)

1692 The description of this interface is contained in the GSM 03.60.

72

3GPP

73 Release 1998

38

3GPP TS 09.02 V7.15.0 (2004-03)

1693

4.4.14 Interface between GGSN and HLR (Gc-interface)

1694 The description of this interface is contained in the GSM 03.60.

1695

4.4.15 Interface between SGSN and EIR (Gf-interface)

1696 The description of this interface is contained in the GSM 03.60.

1697

4.4.16 Interface between SGSN and BSC (Gb-interface)

1698 The description of this interface is contained in the GSM 03.60.

1699

4.4.17 Interface between SGSN and MSC/VLR (Gs-interface)

1700 The description of this interface is contained in the GSM 09.18.

1701
1702 1703 1704 1705

4.4.17A Interface between SMLC and BSC (Lb interface)


This interface is used by a BSC when an SMLC is BSS based to request either the initiation of location procedures or the retrieval of location assistance data for a particular target MS in the coverage area served by the SMLC. The interface is also used to transfer LCS measurement and O&M information between an SMLC and LMU via the BSC. A description of this interface is contained in GSM 03.71 and GSM 09.31.

1706
1707 1708 1709 1710

4.4.18 Interface between SMLC and MSC (Ls interface)


This interface is used by the MSC when an SMLC is NSS based to request either the initiation of location procedures or the retrieval of location assistance data for a particular target MS in the coverage area served by the SMLC. The interface is also used to transfer LCS measurement and O&M information between an SMLC and LMU or BSC via the MSC. A description of this interface is contained in GSM 03.71 and GSM 09.31.

1711

4.4.18A Interface between SMLC and SMLC (Lp interface)

1712 This interface is used by an SMLC to obtain LCS measurement information from an LMU controlled by another 1713 SMLC. A description of this interface is contained in GSM 03.71 and GSM 08.31.

1714 1715

4.4.19 Void 4.4.20 Interface between GMLC and HLR (Lh interface)

1716 This interface is used by the GMLC to request the address of the visited MSC for a particular target MS whose location 1717 has been requested.

1718

4.4.21 Interface between GMLC and MSC (Lg interface)

1719 This interface is used by the GMLC to convey a location request to the MSC currently serving a particular target MS 1720 whose location was requested. The interface is used by the MSC to return location results to the GMLC.

1721

4.4.22 Interface between LCS Client and GMLC (Le interface)

1722 This interface is used by a client of the Location Services (LCS) to request location information from a GMLC for 1723 certain target MSs. The interface is used by the GMLC to provide location information to an LCS client. This interface 1724 is external to a PLMN and is not defined within GSM.

74

3GPP

75 Release 1998

39

3GPP TS 09.02 V7.15.0 (2004-03)

1725

4.5 Splitting of the data storage

1726 The data attached to each MS management, operation and location are stored in the Location Registers. Some data are 1727 duplicated in the HLR and in the VLR, but others may be stored only in one place. 1728 The data associated with any client that uses a particular GMLC to access location services is stored in the GMLC. 1729 A detailed description of the data organization can be found in GSM 03.08.

1730 1731

5 Overload and compatibility overview


5.1 Overload control

1732 There is a requirement for an overload/congestion control for all entities of the Public Land Mobile Network and the 1733 underlying Signalling System No. 7.

1734

5.1.1 Overload control for MSC (outside MAP)


ISDN CCITT Recommendation Q.764 (Automatic Congestion Control), applicable to reduce the mobile terminating traffic; BSSAP GSM 08.08 (A-interface Flow Control), applicable to reduce the mobile originating traffic.

1735 For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load: 1736 1737 1738 1739 1740

1741

5.1.2 Overload control for MAP entities

1742 For all MAP entities, especially the HLR, the following overload control method is applied: 1743 If overload of a MAP entity is detected, requests for certain MAP operations (see tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4) 1744 may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP 1745 service provider and is based upon the priority of the application context. 1746 Since most of the affected MAP operations are supervised in the originating entity by TC timers (medium) an additional 1747 delay effect is achieved for the incoming traffic. 1748 If overload levels are applicable in the Location Registers the MAP operations should be discarded taking into account 1749 the priority of their application context (see table 5.1/1 for HLR, table 5.1/2 for MSC/VLR, table 5.1/3 for the SGSN 1750 and table 5.1/4 for the SMLC; the lowest priority is discarded first). 1751 The ranking of priorities given in the tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4 is not normative. The tables can only be seen as 1752 a proposal which might be changed due to network operator/implementation matters.

76

3GPP

77 Release 1998

40

3GPP TS 09.02 V7.15.0 (2004-03)

1753
1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787

Table 5.1/1: Priorities of Application Contexts for HLR as Responder


Responder = HLR Priority high Mobility Management networkLocUp (updateLocation), (restoreData/v2), (sendParameters/v1) gprsLocationUpdate (updateGPRSLocation/v3), infoRetrieval (sendAuthenticationInfo/v2), (sendParameters/v1) msPurging VLR (purgeMS/v2/v3) msPurging SGSN (purgeMS/v3) Short Message Service shortMsgGateway (sendRoutingInfoforSM), (reportSM-DeliveryStatus) mwdMngt VLR/SGSN (readyForSM/v2/v3), (noteSubscriberPresent/v1) Mobile Terminating Traffic locInfoRetrieval (sendRoutingInfo) anyTimeEnquiry (anyTimeInterrogation) reporting (statusReport) GMSC VLR Initiating Entity

SGSN VLR/SGSN

GMSC gsmSCF VLR

1788 1789 1790 1791


1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815

Location Services locationSvcGateway (sendRoutingInfoforLCS/v3)


Subscriber Controlled Inputs (Supplementary Services) networkFunctionalSs (registerSS), (eraseSS), (activateSS), (deactivateSS), (interrogateSS), (registerPassword), (processUnstructuredSS-Data/v1), (beginSubscriberActivity/v1) callCompletion (registerCCEntry), (eraseCCEntry) networkUnstructuredSs (processUnstructuredSS-Request/v2) imsiRetrieval (sendIMSI/v2) gprsLocationInfoRetrieval (sendRoutingInfoForGprs/v3) failureReport (failureReport/v3) Priority low

GMLC

VLR

VLR VLR VLR GGSN/SGSN GGSN/SGSN

1816 1817

NOTE:

The application context name is the last component but one of the object identifier. Operation names are given in brackets for information with "/vn" appended to vn only operations.

78

3GPP

79 Release 1998 1818

41

3GPP TS 09.02 V7.15.0 (2004-03)

1819

Table 5.1/2: Priorities of Application Contexts for MSC/VLR as Responder


Responder = MSC/VLR Priority high Handover handoverControl (prepareHandover/v2), (performHandover/v1) Initiating Entity MSC

Group call and Broadcast call groupCallControl (prepareGroupCall/v3)


Mobility and Location Register Management locationCancel (cancelLocation) reset (reset) interVlrInfoRetrieval (sendIdentification/v2), (sendParameters/v1) subscriberDataMngt (insertSubscriberData), (deleteSubscriberData) tracing (activateTraceMode), (deactivateTraceMode) Short Message Service shortMsgMO-Relay (MO-ForwardSM v3) (forwardSM v1/v2) shortMsgMT-Relay (MT-ForwardSM v3) (forwardSM v1/v2) shortMsgAlert (alertServiceCentre/v2), (alertServiceCentreWithoutResult/v1) Mobile Terminating Traffic roamingNbEnquiry (provideRoamingNumber) callControlTransfer (resumeCallHandling) subscriberInfoEnquiry (provideSubscriberInformation) HLR (remoteUserFree) (SetReportingState)

MSC
HLR HLR VLR HLR HLR

MSC/SGSN MSC HLR

HLR MSC HLR reporting

Location Services locationSvcEnquiry (provideSubscriberLocation v3)


Network-Initiated USSD networkUnstructuredSs (unstructuredSS-Request/v2), (unstructuredSS-Notify/v2) Priority low

GMLC

HLR

1820 1821

NOTE:

The application context name is the last component but one of the object identifier. Operation names are given in brackets for information with "/vn" appended to vn only operations.

80

3GPP

81 Release 1998 1822

42

3GPP TS 09.02 V7.15.0 (2004-03)

1823
1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847

Table 5.1/3: Priorities of Application Contexts for SGSN as Responder


Responder = SGSN Priority high Mobility and Location Register Management locationCancel (cancelLocation v3) reset (reset) subscriberDataMngt (insertSubscriberData v3), (deleteSubscriberData v3) tracing (activateTraceMode), (deactivateTraceMode) Short Message Service shortMsgMT-Relay (MT-ForwardSM v3) (forwardSM v1/v2) Network-Requested PDP context activation gprsNotify HLR (noteMsPresentForGprs v3), Priority low Initiating Entity HLR HLR HLR HLR

MSC

1848 1849

NOTE:

The application context name is the last component but one of the object identifier. Operation names are given in brackets for information with "/vn" appended to vn.

1850

5.1.3 Congestion control for Signalling System No. 7

1851 The requirements of SS7 Congestion control have to be taken into account as far as possible. 1852 Means which could be applied to achieve the required traffic reductions are described in subclauses 5.1.1 and 5.1.2.

1853 1854

5.2 Compatibility
5.2.1 General

1855 The present document of the Mobile Application Part is designed in such a way that an implementation which conforms 1856 to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR 1857 interface. 1858 A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol 1859 version used between two entities for supporting a MAP-user signalling procedure. 1860 1861 1862 1863

When starting a signalling procedure, the MAP-user supplies an application-context-name to the MAP-provider. This name refers to the set of application layer communication capabilities required for this dialogue. This refers to the required TC facilities (e.g. version 1 or 2) and the list of operation packages (i.e. set of operations) from which operations can be invoked during the dialogue.

1864 A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of 1865 version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP 1866 operational version 1). 1867 1868 1869 1870

If the proposed application-context-name can be supported by the responding entity the dialogue continues on this basis otherwise the dialogue is refused and the initiating user needs to start a new dialogue, which involves another application-context-name which requires less communication capabilities but provides similar functionalities (if possible).

82

3GPP

83 Release 1998

43

3GPP TS 09.02 V7.15.0 (2004-03)

1871 1872 1873 1874

When a signalling procedure can be supported by several application contexts which differ by their version number, the MAP-User needs to select a name. It can either select the name which corresponds to the highest version it supports or follow a more specific strategy so that the number of protocol fallbacks due to version compatibility problems be minimized.

1875

5.2.2 Strategy for selecting the Application Context (AC) version

1876 A method should be used to minimize the number of protocol fall-backs which would occur sometimes if the highest 1877 supported AC-Name were always the one selected by GSM entities when initiating a dialogue. The following method is 1878 an example which can be used mainly at transitory phase stage when the network is one of mixed phase entities.

1879 5.2.2.1
1880 1881 1882 1883 1884 1885 1886

Proposed method

A table (table 1) may be set up by administrative action to define the highest application context (AC) version supported by each destination; a destination may be another node within the same or a different PLMN, or another PLMN considered as a single entity. The destination may be defined by an E.164 number or an E.214 number derived from an IMSI or in North America (World Zone 1) by an E.164 number or an IMSI (E.212 number). The table also includes the date when each destination is expected to be able to handle at least one AC of the latest version of the MAP protocol. When this date is reached, the application context supported by the node is marked as "unknown", which will trigger the use of table 2.

1887 A second table (table 2) contains an entry for each destination which has an entry in table 1. For a given entity, the entry 1888 in table 2 may be a single application context version or a vector of different versions applying to different application 1889 contexts for that entity. Table 2 is managed as described in subclause 5.2.2.2. 1890 The data for each destination will go through the following states: 1891 1892 1893 1894 1895 1896

a) the version shown in table 1 is "version n-1", where 'n' is the highest version existing in this specification; table 2 is not used; b) the version shown in table 1 is "unknown"; table 2 is used, and maintained as described in subclause 5.2.2.2; c) when the PLMN operator declares that an entity (single node or entire PLMN) has been upgraded to support all the MAP version n ACs defined for the relevant interface, the version shown in table 1 is set to "version n" by administrative action; table 2 is no longer used, and the storage space may be recovered.

1897 5.2.2.2

Managing the version look-up table

1898 WHEN it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the 1899 originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the 1900 IMSI or the MSISDN. 1901 IF the entity number is known 1902 1903 1904 1905

THEN It updates (if required) the associated list of highest supported ACs ELSE It creates an entry for this entity and includes the received AC-name in the list of highest supported ACs.

1906 WHEN starting a procedure, the originating MAP-user looks up its version control table. 1907 IF the destination address is known and not timed-out 1908 1909 1910 1911

THEN It retrieves the appropriate AC-name and uses it IF the dialogue is accepted by the peer THEN

84

3GPP

85 Release 1998

44

3GPP TS 09.02 V7.15.0 (2004-03)

1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931

It does not modify the version control table ELSE (this should never occur) It starts a new dialogue with the common highest version supported (based on information implicitly or explicitly provided by the peer). It replace the old AC-name by the new one in the list of associated highest AC supported. ELSE It uses the AC-name which corresponds to the highest version it supports. IF the dialogue is accepted by the peer THEN It adds the destination node in its version control table and includes the AC-Name in the list of associated highest AC supported. ELSE It starts a new dialogue with the common highest version supported (based on information implicitly or explicitly provided by the peer). IF the destination node was not known THEN It adds the destination node in its version control table and includes the new AC-Name in the list of associated highest AC supported. ELSE It replaces the old AC-name by the new one in the list of highest supported AC and reset the timer.

1932 5.2.2.3

Optimizing the method

1933 A table look-up may be avoided in some cases if both the HLR and the VLR or both the HLR and the SGSN store for 1934 each subscriber the version of the AC-name used at location updating. Then: 1935 1936 1937 1938 1939 1940 1941 1942 1943

for procedures which make use of the same application-context, the same AC-name (thus the same version) can be selected (without any table look-up) when the procedure is triggered; for procedures which make use of a different application-context but which includes one of the packages used by the location updating AC, the same version can be selected (without any table look-up) when the procedure is triggered; for HLR: Subscriber data modification (stand alone);

for VLR: Data Restoration.

86

3GPP

87 Release 1998

45

3GPP TS 09.02 V7.15.0 (2004-03)

1944 1945
1946 1947 1948 1949 1950

6 Requirements concerning the use of SCCP and TC


6.1 Use of SCCP
The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full specification of SCCP. In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. Interworking between a PLMN in North America and a PLMN outside North America will involve an STP to translate between ANSI SCCP and ITU-T/CCITT SCCP.

1951

6.1.1 SCCP Class

1952 MAP will only make use of the connectionless classes (0 or 1) of the SCCP.

1953

6.1.2 Sub-System Number (SSN)

1954 The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are 1955 addressed by sub-system numbers (SSNs). The SSN for MAP are specified in GSM 03.03 [17]. 1956 When the SGSN emulates MSC behavior for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, 1957 MAP_CHECK_IMEI) towards entities which do not support interworking to SGSNs, it shall use the MSC SSN in the 1958 calling party address instead of the SGSN SSN.

1959 1960 6.1.3.1

6.1.3 SCCP addressing


Introduction

1961 Within the GSM System there will be a need to communicate between entities within the same PLMN and in different 1962 PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) 1963 and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. 1964 Only the entities which should be addressed are described below. If the CCITT or ITU-T SCCP is used , the format and 1965 coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 1966 with the following restrictions: 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981

1) Intra-PLMN addressing For communication between entities within the same PLMN, a MAP SSN shall always be included in the called and calling party addresses. All other aspects of SCCP addressing are network specific. 2) Inter-PLMN addressing a) Called Party Address SSN indicator = 1 (MAP SSN always included); Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); the translation type field will be coded "00000000" (Not used). For call related messages for non-optimal routed calls (as described in GSM 03.66) directed to another PLMN the translation type field may be coded "10000000" (CRMNP); Routing indicator = 0 (Routing on global title);

b) Calling Party Address SSN indicator = 1 (MAP SSNs always included); Point code indicator = 0;

88

3GPP

89 Release 1998

46

3GPP TS 09.02 V7.15.0 (2004-03)

1982 1983 1984 1985 1986 1987 1988

Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); Numbering Plan = 0001 (ISDN Numbering Plan, E.164; In Case of Inter-PLMN Signalling, the dialogue initiating entity and dialogue responding entity shall always include its own E.164 Global Title as Calling Party Address); the translation type field will be coded "00000000" (Not used); Routing indicator = 0 (Routing on Global Title).

1989 If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall 1990 comply with ANSI specification T1.112 with the following restrictions: 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012

1) Intra-PLMN addressing For communication between entities within the same PLMN, a MAP SSN shall always be included in the called and calling party addresses. All other aspects of SCCP addressing are network specific. 2) Inter-PLMN addressing a) Called Party Address SSN indicator = 1 (MAP SSN always included); Global title indicator = 0010 (Global title includes translation type); the Translation Type (TT) field will be coded as follows: TT = 9, if IMSI is included, TT = 14, if MSISDN is included, Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked.) - Routing indicator = 0 (Routing on global title); b) Calling Party Address SSN indicator = 1 (MAP SSNs always included); Point code indicator = 0; Global title indicator = 0010 (Global title includes translation type); TT = 9, if IMSI is included, TT = 14, if MSISDN is included, Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked.) Routing indicator = 0 (Routing on Global Title).

2013 If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and 2014 E.214 is applicable. 2015 2016 2017 2018 2019 2020 2021

E.212 numbering plan When CCITT or ITU-T SCCP is used, an E.212 number must not be included as Global Title in an SCCP UNITDATA message. The translation of an E.212 number into a Mobile Global Title is applicable in a dialogue initiating VLR, SGSN or GGSN if the routeing information towards the HLR is derived from the subscriber's IMSI. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR. When an MS moves from one VLR service area to another, the new VLR may derive the address of the previous VLR from the Location Area Identification provided by the MS in the location registration request.

90

3GPP

91 Release 1998

47

3GPP TS 09.02 V7.15.0 (2004-03)

2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034

The PLMN where the previous VLR is located is identified by the E.212 numbering plan elements of the Location Area Identification, ie the Mobile Country Code (MCC) and the Mobile Network Code (MNC). E.214 and E.164 numbering plans When CCITT or ITU-T SCCP is used, , only address information belonging to either E.214 or E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR. If the Calling Party Address associated with the dialogue initiating message contains a Global Title, the sending network entity shall include its E.164 entity number. When receiving an SCCP UNITDATA message, SCCP shall accept either of the valid numbering plans in the Called Party Address and in the Calling Party Address. When CCITT or ITU-T SCCP is used and an N-UNITDATA-REQUEST primitive from TC is received, SCCP shall accept an E.164 number or an E.214 number in the Called Address and in the Calling Address. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used instead of E.214 number.

2035 The following subclauses describe the method of SCCP addressing appropriate for each entity both for the simple intra2036 PLMN case and where an inter-PLMN communication is required. The following entities are considered: 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046

the Mobile-services Switching Centre (MSC); the Home location Register (HLR); the Visitor Location Register (VLR); the Gateway Mobile-services Switching Centre (GMSC); the GSM Service Control Function (gsmSCF); the Interworking Mobile-services Switching Centre (IWMSC); the Shared Inter Working Function (SIWF); the Serving GPRS Support Node (SGSN); the Gateway GPRS Support Node (GGSN); the Gateway Mobile Location Center (GMLC).

2047 6.1.3.2

The Mobile-services Switching Centre (MSC)

2048 There are several cases where it is necessary to address the MSC.

2049 6.1.3.2.1

MSC interaction during handover

2050 The address is derived from the target Cellid.

2051 6.1.3.2.2

MSC for short message routing

2052 When a short message has to be routed to a MS, the GMSC addresses the VMSC by an MSC identity received from the 2053 HLR which complies with E.164 rules. 2054 For MS originating short message, the IWMSC address is derived from the Service Centre address.

2055 6.1.3.2.3

MSC for location request routing

2056 When a location request for a particular MS needs to be sent to the MSs VMSC, the GMLC addresses the VMSC using 2057 an E.164 address received from the MSs HLR.

92

3GPP

93 Release 1998

48

3GPP TS 09.02 V7.15.0 (2004-03)

2058 6.1.3.2.4

MSC for LMU Control

2059 When a control message has to be routed to an LMU from an SMLC, the SMLC addresses the serving MSC for the 2060 LMU using an E.164 address.

2061 6.1.3.3

The Home Location Register (HLR)

2062 There are several cases where the HLR has to be addressed:

2063 6.1.3.3.1
2064 2065 2066 2067

During call set-up

When a call is initiated the HLR of the called mobile subscriber will be interrogated to discover the whereabouts of the MS. The addressing required by the SCCP will be derived from the MSISDN dialled by the calling subscriber. The dialled number will be translated into either an SPC, in the case of communications within a PLMN, or a Global Title if other networks are involved (i.e. if the communication is across a PLMN boundary).

2068 If the calling subscriber is a fixed network subscriber, the interrogation can be initiated from the Gateway MSC of the 2069 home PLMN in the general case. If the topology of the network allows it, the interrogation could be initiated from any 2070 Signalling Point which has MAP capabilities, e.g. local exchange, outgoing International Switching Centre (ISC), etc.

2071 6.1.3.3.2
2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082

Before location updating completion

When a MS registers for the first time in a VLR, the VLR has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the VLR has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing the established update location dialogue (as with any other dialogue), the VLR must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. This means that the VLR must be able to address the HLR based: on an E.214 Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is used), or an E.212 number originally derived from IMSI (when ANSI SCCP is used, an IMSI); or on an E.164 HLR address; or in the case of intra-PLMN signalling, on an SPC.

2083 When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of 2084 the SCCP message containing the first responding CONTINUE message. 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096

If the HLR is in the same PLMN as the VLR, local translation tables may exist to derive an SPC. For authentication information retrieval and location updating via the international PSTN/ISDN signalling network that requires the use of CCITT or ITU-T SCCP, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. In World Zone 1 where the ANSI SCCP is used, IMSI (E.212 number) is used as Global Title. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: E.212 Mobile Country Code translates to E.164 Country Code; E.212 Mobile Network Code translates to E.164 National Destination Code; E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits ). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.

2097 This translation will be done either at the application or at SCCP level in the VLR. The Mobile Global Title thus 2098 derived will be used to address the HLR. 2099 If location updating is triggered by an MS that roams from one MSC Area into a different MSC Area served by the 2100 same VLR, the VLR shall address the HLR in the same way as if the MS registers for the first time in the VLR.

94

3GPP

95 Release 1998

49

3GPP TS 09.02 V7.15.0 (2004-03)

2101 6.1.3.3.3
2102 2103 2104 2105 2106 2107

After location updating completion

In this case, the subscriber's basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing information towards the HLR. This may apply in particular if the dialogue with the HLR is triggered by subscriber controlled input.

2108 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the 2109 E.164 MSISDN or the E.164 number allocated to the HLR or either the E.214 Mobile Global Title derived from the 2110 IMSI if CCITT or ITU-T SCCP is used, or the IMSI if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).

2111 6.1.3.3.4
2112 2113 2114 2115 2116 2117 2118 2119 2120

VLR restoration

If a roaming number is requested by the HLR for an IMSI that has no data record in the interrogated VLR, the VLR provides the roaming number in the dialogue terminating message. Subsequently the VLR must retrieve the authentication data from the MS's HLR, if required, and must then trigger the restore data procedure. For this purpose, the VLR has to initiate in succession two independent dialogues with the MS's HLR. The MTP and SCCP address information needed for routeing towards the HLR can be derived from the IMSI received as a parameter of the MAP message requesting the roaming number. In this case, the IMSI received from the HLR in the roaming number request shall be processed in the same way as the IMSI that is received from an MS that registers for the first time within a VLR. Alternatively to the IMSI, the Calling Party Address associated with the roaming number request may be used to obtain the routeing information towards the HLR.

2121 6.1.3.3.5
2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138

During Network-Requested PDP Context Activation

When receiving a PDP PDU the GGSN may interrogate the HLR of the MS for information retrieval. When initiating such a dialogue, the only data for addressing the HLR that the GGSN has available is contained in the IMSI, and addressing information must be derived from it. The IMSI is obtained from the IP address or the X.25 address in the incoming IP message by means of a translation table. This means that the GGSN shall be able to address the HLR based on an E.214, (if CCITT or ITU-T SCCP is used), or E.212 (if ANSI SCCP is used), Mobile Global Title originally derived by the GGSN from the IMSI in the case of inter-PLMN signalling. In the case of intra-PLMN signalling, an SPC may also be used. If the HLR is in the same PLMN as the GGSN, local translation tables may exist to derive an SPC. For information retrieval via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: E.212 Mobile Country Code translates to E.164 Country Code; E.212 Mobile Network Code translates to E.164 National Destination Code; E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.

2139 This translation will be done either at the application or at SCCP level in the GGSN. The Mobile Global Title thus 2140 derived will be used to address the HLR.

2141 6.1.3.3.6
2142 2143 2144 2145 2146 2147 2148

Before GPRS location updating completion

When a MS registers for the first time in a SGSN, the SGSN has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the SGSN has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing the established update location dialogue (as with any other dialogue), the SGSN must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. This means that the SGSN must be able to address the HLR based:

96

3GPP

97 Release 1998

50

3GPP TS 09.02 V7.15.0 (2004-03)

2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162

on an E.214 (if CCITT or ITU-T SCCP is used) or E.212 (if ANSI SCCP is used) Mobile Global Title originally derived by the SGSN from the IMSI; or on an E.164 HLR address; or in the case of intra-PLMN signalling, on an SPC.

If the HLR is in the same PLMN as the SGSN, local translation tables may exist to derive an SPC. For authentication information retrieval and location updating via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: E.212 Mobile Country Code translates to E.164 Country Code; E.212 Mobile Network Code translates to E.164 National Destination Code; E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits ). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.

2163 This translation will be done either at the application or at SCCP level in the SGSN. The Mobile Global Title thus 2164 derived will be used to address the HLR.

2165 6.1.3.3.7
2166 2167 2168 2169 2170

After GPRS location updating completion

In this case, the subscriber's Basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing information towards the HLR.

2171 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the 2172 E.164 MSISDN or the E.164 number allocated to the HLR or the E.214 Mobile Global Title derived from the IMSI.

2173 6.1.3.3.8
2174 2175 2176 2177

Query for a Location Request

For a location request from an external client, the GMLC needs to address the home HLR of the target MS to obtain the address of the target MSs serving MSC. The GMLC uses either the international E.164 MSISDN, the international E.214 number (if CCITT or ITU-T SCCP is used) or the international E.212 number (if ANSI SCCP is used) of the MS as means to route a query to the HLR.

2178 6.1.3.4

The Visitor Location Register (VLR)

2179 There are several cases when the VLR needs to be addressed.

2180 6.1.3.4.1

Inter-VLR information retrieval

2181 When an MS moves from one VLR service area to another, the new VLR may request the IMSI and authentication sets 2182 from the previous VLR. The new VLR derives the address of the previous VLR from the Location Area Identification 2183 provided by the MS in the location registration request.

2184 6.1.3.4.2

HLR request

2185 The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR's service area. 2186 This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has 2187 indicated successful completion of the update location procedure to the VLR. 2188 When initiating dialogues towards the VLR after successful completion of location updating, the routeing information 2189 used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the 2190 update location dialogue. If the VLR is in the same PLMN as the HLR, the VLR may be addressed directly by an SPC

98

3GPP

99 Release 1998

51

3GPP TS 09.02 V7.15.0 (2004-03)

2191 derived from the E.164 VLR number. For dialogues via the international PSTN/ISDN signalling network, presence of 2192 the E.164 VLR number in the Called Party Address is required.

2193 6.1.3.5

The Interworking MSC (IWMSC) for Short Message Service

2194 The IWMSC is the interface between the mobile network and the network to access to the Short Message Service 2195 Centre. This exchange has an E.164 address known in the SGSN or in the MSC.

2196 6.1.3.6

The Equipment Identity Register (EIR)

2197 The EIR address is either unique or could be derived from the IMEI. The type of address is not defined.

2198 6.1.3.7

The Shared Inter Working Function (SIWF)

2199 When the Visited MSC detects a data or fax call and the IWF in the V-MSC can not handle the required service an 2200 SIWF can be invoked. The SIWF is addressed with an E.164 number.

2201 6.1.3.8
2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214

The Serving GPRS Support Node (SGSN)

The HLR will initiate dialogues towards the SGSN if it is aware that one of its subscribers is in the SGSN's serving area. This means that a GPRS location updating has been successfully completed, i.e, the HLR has indicated successful completion of the GPRS location update to the SGSN. The routeing information used by the HLR is derived form the E.164 SGSN number received as parameter of the MAP message initiating the GPRS update location procedure. If the SGSN is in the same PLMN as the HLR, the SGSN may be addressed directly by an SPC derived from the E.164 SGSN number. For dialogues via the international PSTN/ISDN signalling network, the presence of the E.164 SGSN number in the Called Party Address is required. When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See GSM 03.03) shall be included in the called party address. The routeing information used by the GMSC is derived from the E.164 SGSN number received as a parameter of the MAP message initiating the forward short message procedure. If the GMSC does not support the GPRS functionality the MSC (MAP) SSN value shall be included in the called party address. NOTE: Every VMSC and SGSN shall have uniquely identifiable application using E.164 numbers, for the purpose of SMS over GPRS when the GMSC does not support the GPRS functionality.

2215 6.1.3.9
2216 2217 2218 2219

The Gateway GPRS Support Node (GGSN)

The GGSN provides interworking with external packet-switched networks, network screens and routing of the Network-Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the HLR will alert the GGSN when the subscriber becomes reachable. The HLR will use the E.164 GGSN number received as parameter of the MAP message reporting the failure.

2220 6.1.3.10

The Gateway MSC (GMSC) for Short Message Service

2221 The GMSC provides interworking with the network to access the Short Message Service Centre, the mobile network 2222 and routing of Send Routing Info For SM. The GMSC has on E.164 address known in the HLR, SGSN or MSC.

100

3GPP

101 Release 1998

52

3GPP TS 09.02 V7.15.0 (2004-03)

2223 6.1.3.10A 2224 6.1.3.10A.1 2225 6.1.3.10A.2 2226 6.1.3.10B

Void
Void Void

The Gateway Mobile Location Center (GMLC)

2227 The GMLC initiates location requests on behalf of external clients. The E.164 address of the GMLC is provided to an 2228 HLR when the GMLC requests a serving MSC address from the HLR for a target MS. The E.164 address of the GMLC 2229 is also provided to a serving MSC when the GMLC requests the location of a target MS served by this MSC.

2230 6.1.3.11

Summary table

2231 The following tables summarize the SCCP address used for invoke operations. As a principle, within a PLMN either an 2232 SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT 2233 must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. 2234 For a response, the originating address passed in the invoke is used as SCCP Called Party Adress. For extra-PLMN 2235 addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC 2236 derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP. 2237
to from fixed network home location register visitor location register fixed net work
-----

Table 6.1/1
HLR
E:GT T:MSISDN ---

VLR
--I:SPC/GT E:GT T:VLR NUMBER I:SPC/GT E:GT T:VLR NUMBER

MSC
-----

EIR
-----

gsmSCF
--I:SPC/GT E:GT T:gsmSCF NUMBER ---

SIWF
-----

SGSN
--I:SPC/GT E:GT T:SGSN NUMBER ---

GGSN
--I:SPC/GT E:GT T:GGSN NUMBER ---

---

mobileservices switching centre gsm Service Control Function Shared Inter Working Function Serving GPRS Support Node Gateway GPRS Support Node Gateway

---

I:SPC/GT E:GT T:MGT (outside World Zone 1)/MSISDN (World Zone 1/)HLR NUMBER (note) I:SPC/GT E:GT T:MSISDN I:SPC/GT E:GT T:MSISDN ---

---

---

---

I:SPC/GT E:GT T:VLR NUMBER ---

I:SPC/GT E:GT T:MSC NUMBER ---

I:SPC/GT E:GT T:EIR NUMBER ---

I:SPC/GT E:GT T:gsmSCF NUMBER ---

I:SPC/GT E:GT T:SIWF NUMBER ---

I:SPC/GT E:GT T:SGSN NUMBER ---

---

---

---

---

---

I:SPC/GT E:GT T:MSC NUMBER I:SPC/GT E:GT T:MSC NUMBER ---

---

---

---

---

---

---

I:SPC/GT E:GT T:MGT/ MSISDN/HL R NUMBER I:SPC/GT E:GT T:MGT I:SPC/GT

---

I:SPC/GT E:GT T:EIR NUMBER ---

---

---

---

---

---

---

---

---

---

---

---

---

I:SPC/GT

---

---

---

---

---

102

3GPP

103 Release 1998

53 E:GT
T:MSISDN, MGT (outside World Zone 1) or IMSI (World Zone 1) (note)

3GPP TS 09.02 V7.15.0 (2004-03)

Mobile Location Center

E:GT
T:MSC NUMBER

I: Intra-PLMN E: Extra(Inter)-PLMN T: Address Type T: Global Title MGT: E.214 Mobile Global Title SPC: Signalling Point Code NOTE: For initiating the location updating procedure and an authentication information retrieval from the HLR preceding it, the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).. When continuing the established update location dialogue (as with any other dialogue) the VLR must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. For transactions invoked by the VLR after update location completion, the VLR may derive the information for addressing the HLR from addresses received in the course of the update location procedure (MSISDN or HLR number) or from the IMSI. When invoking the Restore Data procedure and an authentication information retrieval from the HLR preceding it, the VLR must derive the information for addressing the HLR from the address information received in association with the roaming number request. This may be either the IMSI received as a parameter of the MAP message requesting the Roaming Number or the Calling Party Address associated with the MAP message requesting the Roaming Number. The gsmSCF shall be addressed using more than one Global Title number. The first Global Title number is used to address a gsmSCF for MAP. The second Global Title number is used to address a gsmSCF for CAP. For querying the HLR to obtain the VMSC address to support location services, the GMLC has to derive the HLR address from either the MSISDN or IMSI of the target MS. When using the IMSI, the result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).

2239

2238

104

3GPP

105 Release 1998

54

3GPP TS 09.02 V7.15.0 (2004-03)

2240

Table 6.1/2
to from fixed network home location register visitor location register mobile-services switching centre gsm Service Control Function Shared Inter Working Function Serving GPRS Support Node Gateway GPRS Support Node Gateway Mobile Location Center I: Intra-PLMN E: Extra(Inter)-PLMN T: Address Type T: Global Title MGT: E.214 Mobile Global Title SPC: Signalling Point Code GMLC
-------------

---

---

2241

2242

6.2 Use of TC

2243 The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of signalling 2244 system No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be 2245 consulted for the full specification of TC. 2246 The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility. 2247 From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is 2248 for further study. 2249 Transaction Capabilities refers to a protocol structure above the network layer interface (i.e, the SCCP service interface) 2250 up to the application layer including common application service elements but not the specific application service 2251 elements using them. 2252 TC is structured as a Component sub-layer above a Transaction sub-layer. 2253 The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues 2254 and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives 2255 and TC-Component handling primitives respectively. 2256 Services for dialogue control include the ability to exchange information related to application-context negotiation as 2257 well as initialization data. 2258 2259 2260 2261 2262 2263

Services for Remote Operation handling provide for the exchange of protocol data units invoking tasks (operations), and reporting their outcomes (results or errors) plus any non-application-specific protocol errors detected by the component sub-layer. The reporting of application-specific protocol errors by the TC user, as distinct from application process errors, is also provided. The Transaction sub-layer provides a simple end-to-end connection association service over which several related protocol data units (i.e. built by the Component Sub-Layer) can be exchanged. A Transaction termination can be prearranged (no indication provided to the TC user) or basic (indication provided).

106

3GPP

107 Release 1998

55

3GPP TS 09.02 V7.15.0 (2004-03)

2264
2265

Figure 6.2/1: Facilities for supporting the Mobile Application Part in Signalling System No.7

2266 2267

7 General on MAP services


7.1 Terminology and definitions

2268 The term service is used in clauses 7 to 12 as defined in CCITT Recommendation X.200. The service definition 2269 conventions of CCITT Recommendation X.210 are also used.

2270

7.2 Modelling principles

2271 MAP provides its users with a specified set of services and can be viewed by its users as a "black box" or abstract 2272 machine representing the MAP service-provider. The service interface can then be depicted as shown in figure 7.2/1.

2273
2274

Figure 7.2/1: Modelling principles

108

3GPP

109 Release 1998

56

3GPP TS 09.02 V7.15.0 (2004-03)

2275 The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the 2276 service interface. 2277 A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such 2278 cases the overall procedure is synchronised by the service-user. 2279 The MAP service-primitives are named using the following notation: 2280

MAP-ServicePrimitiveName type

2281 where type can be any of: request (req), indication (ind), response (rsp) or confirm (cnf) (In the user arrow diagrams 2282 type is not indicated in the case of req/ind and indicated as "ack" in the case of rsp/cnf). 2283 The services are further classified as unconfirmed-service, confirmed-service and provider-initiated-service where the 2284 first two categories refer to whether or not the service is confirmed by the service-provider. The confirmation may or 2285 may not correspond to a response provided by the other service-user. 2286 MAP services are also classified as common MAP services which are available to all MAP service-users, and MAP 2287 service-user specific services which are services available to one or several, but not all, MAP service-users. 2288 A MAP dialogue is defined as an exchange of information between two MAP users in order to perform a common task. 2289 A MAP dialogue will consist of one or several MAP services.

2290

7.3 Common MAP services


for establishing and clearing MAP dialogues between peer MAP service-users; for accessing functions supported by layers below the applications layer; for reporting abnormal situations; for handling of different MAP versions; for testing whether or not a persistent MAP dialogue is still active at each side.

2291 All MAP service-users require access to services for performing basic application layer functions: 2292 2293 2294 2295 2296

2297 For these purposes the following common services are defined: 2298 2299 2300 2301 2302 2303

MAP-OPEN service; MAP-CLOSE service; MAP-DELIMITER service; MAP-U-ABORT service; MAP-P-ABORT service; MAP-NOTICE service.

2304 In defining the service-primitives the following convention is used for categorising parameters: 2305 2306 2307 2308 2309 2310

M O U

the inclusion of the parameter is mandatory. The M category can be used for any primitive type and specifies that the corresponding parameter must be present in the indicated primitive type; the inclusion of the parameter is a service-provider option. The O category can be used in indication and confirm type primitives and is used for parameters that may optionally be included by the service-provider; the inclusion of the parameter is a service-user option. The U category can be used in request and response type primitives. The inclusion of the corresponding parameter is the choice of the service-user;

110

3GPP

111 Release 1998

57

3GPP TS 09.02 V7.15.0 (2004-03)

2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323

C -

the inclusion of the parameter is conditional. The C category can be used for the following purposes: to indicate that if the parameter is received from another entity it must be included for the service being considered; to indicate that the service user must decide whether to include the parameter, based on the context on which the service is used; to indicate that one of a number of mutually exclusive parameters must be included (e.g. parameters indicating a positive result versus parameters indicating a negative result); to indicate that a service user optional parameter (marked "U") or a conditional parameter (marked "C") presented by the service user in a request or response type primitive is to be presented to the service user in the corresponding indication or confirm type primitive; when appended to one of the above, this symbol means that the parameter takes the same value as the parameter appearing immediately to its left;

(=)

blank the parameter is not present.

2324 A primitive type may also be without parameters, i.e. no parameter is required with the primitive type; in this case the 2325 corresponding column of the table is empty.

2326

7.3.1 MAP-OPEN service

2327 This service is used for establishing a MAP dialogue between two MAP service-users. The service is a confirmed 2328 service with service primitives as shown in table 7.3/1. 2329
Parameters Application context name Destination address Destination reference Originating address Originating reference Specific information Responding address Result Refuse-reason Provider error

Table 7.3/1: Service-primitives for the MAP-OPEN service


Request M M U U U U Indication M(=) M(=) C(=) O C(=) C(=) Response U Confirm C(=)

U U M C

C(=) C(=) M(=) C(=) O

2330 2331 Application context name: 2332 This parameter identifies the type of application context being established. If the dialogue is accepted the received 2333 application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version 2334 supported. 2335 Destination address: 2336 A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this 2337 parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is 2338 issued. 2339 Destination-reference: 2340 This parameter is a reference which refines the identification of the called process. It may be identical to Destination 2341 address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only 2342 these services are allowed to use it.

112

3GPP

113 Release 1998

58

3GPP TS 09.02 V7.15.0 (2004-03)

2343

Table 7.3/2: Use of the destination reference MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTURED-SS-NOTIFY MAP-FORWARD-SHORT-MESSAGE MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY Reference type IMSI IMSI IMSI IMSI IMSI IMSI IMSI IMSI IMSI IMSI (note) IMSI IMSI Use of the parameter Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity

2344 2345 2346

NOTE:

Only when the IMSI and the LMSI are received together from the HLR in the mobile terminated short message transfer.

2347 Originating address: 2348 A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, 2349 this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is 2350 issued. 2351 Originating-reference: 2352 2353 2354 2355

This parameter is a reference which refines the identification of the calling process. It may be identical to the Originating address but its value is to be carried at MAP level. Table 7.3/3 describes the MAP services using the parameter. Only these services are allowed to use it. Processing of the Originating-reference shall be performed according to the supplementary service descriptions and other service descriptions, e.g. operator determined barring.

114

3GPP

115 Release 1998

59

3GPP TS 09.02 V7.15.0 (2004-03)

2356

Table 7.3/3: Use of the originating reference MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY Reference type ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String Use of the parameter Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address

2357 2358 Specific information: 2359 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2360 information is not specified by GSM and shall be performed according to operator specific requirements. 2361 Responding address: 2362 An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is 2363 different from the destination address). 2364 Result: 2365 This parameter indicates whether the dialogue is accepted by the peer. 2366 Refuse reason: 2367 This parameter is only present if the Result parameter indicates that the dialogue is refused. It takes one of the following 2368 values: 2369 2370 2371 2372 2373 2374

Application-context-not-supported; Invalid-destination-reference; Invalid-originating-reference; No-reason-given; Remote node not reachable; Potential version incompatibility.

116

3GPP

117 Release 1998

60

3GPP TS 09.02 V7.15.0 (2004-03)

2375

7.3.2 MAP-CLOSE service

2376 This service is used for releasing a previously established MAP dialogue. The service may be invoked by either MAP 2377 service-user depending on rules defined within the service-user. The service is an unconfirmed service with parameters 2378 as shown in table 7.3/4. 2379

Table 7.3/4: Service-primitives for the MAP-CLOSE service


Parameters

Release method Specific Information


2380 2381 Release method: 2382 This parameter can take the following two values: 2383 2384 2385

Request M U

Indication C(=)

normal release; in this case the primitive is mapped onto the protocol and sent to the peer; prearranged end; in this case the primitive is not mapped onto the protocol. Prearranged end is managed independently by the two users, i.e. only the request type primitive is required in this case.

2386 Specific information: 2387 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2388 information is not specified by GSM GSM and shall be performed according to operator specific requirements.

2389

7.3.3 MAP-DELIMITER service

2390 This service is used to explicitly request the transfer of the MAP protocol data units to the peer entities. 2391 See also subclause 7.4 and 7.5 for the detailed use of the MAP-DELIMITER service. 2392 The service is an unconfirmed service with service-primitives as shown in table 7.3/5. 2393

Table 7.3/5: Service-primitives for the MAP-DELIMITER service


Parameters Request Indication

2394

2395

7.3.4 MAP-U-ABORT service

2396 This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service 2397 with service-primitives as shown in table 7.3/6. 2398

Table 7.3/6: Service-primitives for the MAP-U-ABORT service


Parameters

User reason Diagnostic information Specific information


2399 2400 User reason: 2401 This parameter can take the following values: 2402 2403

Request M U U

Indication M(=) C(=) C(=)

resource limitation (congestion); the requested user resource is unavailable due to congestion;

118

3GPP

119 Release 1998

61

3GPP TS 09.02 V7.15.0 (2004-03)

2404 2405 2406 2407 2408 2409

resource unavailable; the requested user resource is unavailable for reasons other than congestion;

application procedure cancellation; the procedure is cancelled for reason detailed in the diagnostic information parameter;

procedure error; processing of the procedure is terminated for procedural reasons.

2410 Diagnostic information: 2411 This parameter may be used to give additional information for some of the values of the user-reason parameter: 2412

Table 7.3/7: User reason and diagnostic information


User reason Resource limitation (congestion) Resource unavailable Application procedure cancellation Diagnostic information Short term/long term problem Handover cancellation/ Radio Channel release/ Network path release/ Call release/ Associated procedure failure/ Tandem dialogue released/ Remote operations failure -

Procedure error

2413 2414 Specific information: 2415 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2416 information is not specified by GSM and shall be performed according to operator specific requirements.

2417

7.3.5 MAP-P-ABORT service

2418 This service enables the MAP service-provider to abort a MAP dialogue. The service is a provider-initiated service with 2419 service-primitive as shown in table 7.3/8. 2420

Table 7.3/8: Service-primitive for the MAP-P-ABORT service


Parameters Provider reason Source Indication M M

2421 2422 Provider reason: 2423 This parameter indicates the reason for aborting the MAP dialogue: 2424 2425 2426 2427 2428 2429

provider malfunction; supporting dialogue/transaction released; resource limitation; maintenance activity; version incompatibility; abnormal MAP dialogue.

120

3GPP

121 Release 1998

62

3GPP TS 09.02 V7.15.0 (2004-03)

2430 Source: 2431 This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take 2432 the following values: 2433 2434 2435

MAP problem; TC problem; network service problem.

2436 Table 7.3/9: Values of provider reason and source parameters and examples of corresponding events
Provider reason Provider malfunction Source MAP TC Corresponding event Malfunction at MAP level at peer entity "Unrecognised message type" or "Badly formatted transaction portion" or "Incorrect transaction portion" received in TC-P-ABORT "Abnormal dialogue" Malfunction at network service level at peer entity

Network service Supporting dialogue/ transaction released Resource limitation Maintenance activity Abnormal MAP dialogue Version incompatibility TC MAP TC MAP Network service MAP TC

"Unrecognised transaction ID" received in TC-ABORT Congestion towards MAP peer service-user "Resource limitation" received in TC-P-ABORT Maintenance at MAP peer service-user Maintenance at network peer service level MAP dialogue is not in accordance with specified application context A Provider Abort indicating "No common dialogue portion" is received in the dialogue initiated state

2437

2438

7.3.6 MAP-NOTICE service

2439 This service is used to notify the MAP service-user about protocol problems related to a MAP dialogue not affecting the 2440 state of the protocol machines. 2441 The service is a provider-initiated service with service-primitive as shown in table 7.3/10. 2442

Table 7.3/10: Service-primitive for the MAP-NOTICE service


Parameters Problem diagnostic Indication M

2443 2444 Problem diagnostic: 2445 This parameter can take one of the following values: 2446 2447 2448 2449

abnormal event detected by the peer; response rejected by the peer; abnormal event received from the peer message cannot be delivered to the peer.

122

3GPP

123 Release 1998

63

3GPP TS 09.02 V7.15.0 (2004-03)

2450

7.4 Sequencing of services


Opening: The MAP-OPEN service is invoked before any user specific service-primitive is accepted. The sequence may contain none, one or several user specific service-primitives. If no user specific service-primitive is contained between the MAP-OPEN and the MAP-DELIMITER primitives, then this will correspond to sending an empty Begin message in TC. If more than one user specific service-primitive is included, all are to be sent in the same Begin message. The sequence ends with a MAP-DELIMITER primitive. Continuing: This sequence may not be present in some MAP dialogues. If it is present, it ends with a MAP-DELIMITER primitive. If more than one user specific service-primitive is included, all are to be included in the same Continue message. Closing: The sequence can only appear after an opening sequence or a continuing sequence. The sequence may contain none, one or several user specific service-primitives if the MAP-CLOSE primitive specifies normal release. If no user specific service-primitive is included, then this will correspond to sending an empty End message in TC. If more than one user specific service-primitive is included, all are to be sent in the same End message. If prearranged end is specified, the sequence cannot contain any user specific service-primitive. The MAP-CLOSE primitive must be sent after all user specific service-primitives have been delivered to the MAP service-provider. Aborting: A MAP service-user can issue a MAP-U-ABORT primitive at any time after the MAP dialogue has been opened or as a response to an attempt to open a MAP dialogue.

2451 The sequencing of services is shown in figure 7.4/1 and is as follows: 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472

2473 The MAP service-provider may issue at any time a MAP-P-ABORT primitive towards a MAP service-user for which a 2474 MAP dialogue exists. 2475 MAP-U-ABORT primitives and MAP-P-ABORT primitives terminate the MAP dialogue.

124

3GPP

125 Release 1998

64

3GPP TS 09.02 V7.15.0 (2004-03)

2476
2477

Figure 7.4/1: Sequencing of services

2478 If the reason "resource unavailable (short term problem)" is indicated in the MAP-U-ABORT indication primitive, the 2479 MAP service-user may decide to attempt a new MAP dialogue establishment immediately. 2480 Sequencing of user specific service-primitives is done by the MAP service-user and based on rules applicable for each 2481 MAP service-user instance. 2482 A MAP-NOTICE indication primitive may be received at any time during the active period of a MAP dialogue.

2483 2484

7.5 General rules for mapping of services onto TC


7.5.1 Mapping of common services

2485 Table 7.5/1 gives an overview of the mapping rules for mapping of common services onto TC-services. Table 7.5/2 2486 gives the mapping rules for mapping of TC-services onto common services. 2487 Protocol machine description is given in clauses 14 to 17.

126

3GPP

127 Release 1998

65

3GPP TS 09.02 V7.15.0 (2004-03)

2488

Table 7.5/1: Mapping of common services on to TC services


MAP service-primitive MAP-OPEN request (+ any user specific service primitives) + MAP-DELIMITER request MAP-OPEN response (+ any user specific service primitives) + MAP-DELIMITER request (any user specific service primitives) + MAP-DELIMITER request (any user specific service primitives) + MAP-CLOSE request TC service-primitive TC-BEGIN request (+ component handling primitives) TC-CONTINUE request (note) (+ component handling primitives) TC-CONTINUE request (+ component handling primitives) TC-END request (+ component handling primitives)

MAP-U-ABORT request TC-U-ABORT request NOTE: or TC-END if the MAP-CLOSE request has been received before the MAP-DELIMITER request.

2489 2490

Table 7.5/2: Mapping of TC services on to common service


TC service-primitive TC-BEGIN indication (+ component handling primitives) TC-CONTINUE indication (+ component handling primitives) MAP service-primitive MAP-OPEN indication (+ user specific service primitives) + MAP-DELIMITER indication (note 1) First time: MAP-OPEN confirm (+ user specific service primitives) + MAP-DELIMITER indication (note 1) Subsequent times: (user specific service primitives) + MAP-DELIMITER indication (note 1) TC-END indication (+ component handling primitives) TC-U-ABORT indication MAP-OPEN confirm (note 6) (user specific service primitives) + MAP-CLOSE indication MAP-U-ABORT indication or MAP-P-ABORT indication (note 2) MAP-OPEN confirmation (note 3)

TC-P-ABORT indication NOTE 1: NOTE 2: NOTE 3: NOTE 4: NOTE 5: NOTE 6:

MAP-P-ABORT indication (note 4) MAP-OPEN confirmation (note 5) It may not be necessary to present this primitive to the user for MAP version 2 applications. The mapping depends on whether the TC-U-ABORT indication primitive contains a MAP-abort-PDU from the remote MAP service-provider or a MAP-user-abort-PDU from the remote MAP service-user. Only if the opening sequence is pending and if the "Abort Reason" in the TC-U-ABORT indication is set to "Application Context Not Supported". If the "Abort Reason" in the TC-P-ABORT indication is set to a value different from "Incorrect Transaction Portion". Only if the opening sequence is pending and if the "Abort Reason" in the TC-P-ABORT indication is set to "Incorrect Transaction Portion". Only if opening sequence is pending.

2491

2492

7.5.2 Mapping of user specific services

2493 Table 7.5/3 gives the general mapping rules which apply to mapping of MAP user specific services onto TC services 2494 and table 7.5/4 gives the similar rules for mapping of TC services onto MAP user specific services. Detailed mapping is 2495 given in clauses 14 to 17.

128

3GPP

129 Release 1998

66

3GPP TS 09.02 V7.15.0 (2004-03)

2496

Table 7.5/3: Mapping of MAP user specific services onto TC services


MAP service-primitive MAP-xx request MAP-xx response (note 1) TC-service-primitive TC-INVOKE request TC-RESULT-L request TC-U-ERROR request TC-U-REJECT request TC-INVOKE request (note 2)

2497 2498

Table 7.5/4: Mapping of TC services onto MAP user specific services


TC-service-primitive TC-INVOKE indication TC-RESULT-L indication (note 4) TC-U-ERROR indication TC-INVOKE indication (note 2) TC-L-CANCEL indication TC-U-REJECT indication TC-L-REJECT indication TC-R-REJECT indication MAP service-primitive MAP-xx indication MAP-xx confirm

MAP-xx confirm or MAP-NOTICE indication (note 3)

2499 Notes to tables 7.5/3 and 7.5/4: 2500 2501 2502 2503 2504

NOTE 1: The mapping is determined by parameters contained in the MAP-xx response primitive. NOTE 2: This applies only to TC class 4 operations where the operation is used to pass a result of another class 2 or class 4 operation. NOTE 3: The detailed mapping rules are given in clause 16. NOTE 4: If RESULT-NL components are present they are mapped on to the same MAP-xx confirm.

2505
2506

7.6 Definition of parameters


Following is an alphabetic list of parameters used in the common MAP-services in subclause 7.3:
Application context name Destination address Destination reference Diagnostic information Originating address Originating reference Problem diagnostic Provider reason 7.3.1 7.3.1 7.3.1 7.3.4 7.3.1 7.3.1 7.3.6 7.3.5 Refuse reason Release method Responding address Result Source Specific information User reason 7.3.1 7.3.2 7.3.1 7.3.1 7.3.5 7.3.1/7.3.2/7.3.4 7.3.4

2507

130

3GPP

131 Release 1998

67

3GPP TS 09.02 V7.15.0 (2004-03)

2508

Following is an alphabetic list of parameters contained in this clause:

132

3GPP

133 Release 1998

68 7.6.8.9 7.6.9.3 7.6.9.5 7.6.8.12 7.6.2.46 7.6.9.10 7.6.8.11 7.6.8.8 7.6.8.10 7.6.3.44 7.6.3.53 7.6.1.5 7.6.2.42 7.6.7.1 7.6.2.36 7.6.2.48 7.6.2.49 7.6.4.40 7.6.4.38 7.6.9.1 7.6.4.19 7.6.4.18 7.6.5.8 7.6.9.9 7.6.5.1 7.6.2.24 7.6.2.25 7.6.3.38 7.6.3.52 7.6.3.1 7.6.5.8 7.6.5.9 7.6.5.10 7.6.7.7 7.6.7.5 7.6.4.5 7.6.9.2 7.6.3.54 7.6.3.26 7.6.3.25 7.6.3.22 7.6.3.24 7.6.3.8 7.6.3.23 7.6.3.37 7.6.2.6 7.6.4.21 7.6.4.41 7.6.3.2 7.6.3.5 7.6.3.3 7.6.3.21 7.6.3.20 7.6.3.16 7.6.3.15 7.6.3.18 7.6.3.19 7.6.3.29 7.6.3.14 7.6.3.17 7.6.3.4 7.6.9.4 Invoke Id ISDN Bearer Capability Kc Linked Id LMSI Location Information

3GPP TS 09.02 V7.15.0 (2004-03) 7.6.1.1 7.6.3.41 7.6.7.4 7.6.1.2 7.6.2.16 7.6.2.30 7.6.9.6 7.6.3.42 7.6.3.56 7.6.3.58 7.6.3.51 7.6.8.7 7.6.2.17 7.6.2.11 7.6.2.29 7.6.8.3 7.6.3.50 7.6.2.43 7.6.10.1 7.6.9.8 7.6.4.20 7.6.4.7 7.6.2.34 7.6.5.14 7.6.3.9 7.6.3.10 7.6.2.18 7.6.2.26 7.6.2.10 7.6.4.4 7.6.2.47 7.6.2.45 7.6.3.55 7.6.2.44 7.6.2.4 7.6.9.7 7.6.1.3 7.6.3.47 7.6.7.2 7.6.3.11 7.6.3.12 7.6.3.31 7.6.2.19 7.6.3.49 7.6.3.13 7.6.2.27 7.6.2.37 7.6.2.39 7.6.2.38 7.6.2.35 7.6.3.57 7.6.8.6 7.6.8.1 7.6.8.16 7.6.8.2 7.6.8.5 7.6.8.17 7.6.8.4 7.6.7.3 7.6.4.1 7.6.4.3 7.6.4.42

Absent Subscriber Diagnostic SM Access connection status Access signalling information Additional Absent Subscriber Diagnostic SM Additional number Additional signal info Additional SM Delivery Outcome Alert Reason Alert Reason Indicator Alerting Pattern All GPRS Data All Information Sent APN Authentication set list B-subscriber Address B subscriber Number B subscriber subaddress Basic Service Group Bearer service BSS-apdu Call barring feature Call barring information Call Direction Call Info Call reference Called number Calling number CAMEL Subscription Info Withdraw Cancellation Type Category CCBS Feature Channel Type Chosen Channel Ciphering mode Cksn CLI Restriction CM service type Complete Data List Included CUG feature CUG index CUG info CUG interlock CUG Outgoing Access indicator CUG subscription CUG Subscription Flag Current location area Id Current password eMLPP Information Equipment status Extensible Basic Service Group Extensible Bearer service Extensible Call barring feature Extensible Call barring information Extensible Forwarding feature Extensible Forwarding info Extensible Forwarding Options Extensible No reply condition timer Extensible SS-Data Extensible SS-Info Extensible SS-Status Extensible Teleservice External Signal Information

Location update type Lower Layer Compatibility LSA Information LSA Information Withdraw Mobile Not Reachable Reason More Messages To Send MS ISDN MSC number MSIsdn-Alert MWD status Network Access Mode Network node number Network resources Network signal information New password No reply condition timer North American Equal Access preferred Carrier Id Number Portability Status ODB General Data ODB HPLMN Specific Data OMC Id Originally dialled number Originating entity number Override Category P-TMSI PDP-Address PDP-Context identifier PDP-Type Previous location area Id Protocol Id Provider error QoS-Subscribed Rand Regional Subscription Data Regional Subscription Response Requested Info Roaming number Roaming Restricted In SGSN Due To Unsupported Feature Roaming Restriction Due To Unsupported Feature Service centre address Serving Cell Id SGSN address SGSN number SIWF Number SoLSA Support Indicator SM Delivery Outcome SM-RP-DA SM-RP-MTI SM-RP-OA SM-RP-PRI SM-RP-SMEA SM-RP-UI Sres SS-Code SS-Data SS-Event

134

3GPP

135 Release 1998

69 7.6.2.22 7.6.2.23 7.6.4.16 7.6.4.15 7.6.4.6 7.6.2.40 7.6.2.41 7.6.3.34 7.6.8.14 7.6.3.46 7.6.3.45 7.6.8.15 7.6.2.33 7.6.3.6 7.6.4.22 7.6.2.21 7.6.3.43 7.6.2.15 7.6.2.13 7.6.6.7 7.6.2.3 7.6.2.1 7.6.3.27 7.6.3.28

3GPP TS 09.02 V7.15.0 (2004-03) 7.6.4.43 7.6.4.24 7.6.4.2 7.6.2.5 7.6.3.30 7.6.3.7 7.6.3.36 7.6.3.33 7.6.3.32 7.6.2.8 7.6.2.7 7.6.2.12 7.6.4.39 7.6.2.2 7.6.10.2 7.6.10.3 7.6.1.4 7.6.4.36 7.6.4.37 7.6.5.12 7.6.5.13 7.6.3.40 7.6.3.39 7.6.3.35 7.6.2.14 7.6.3.48 7.6.2.28

Forwarded-to number Forwarded-to subaddress Forwarding feature Forwarding information Forwarding Options GGSN address GGSN number GMSC CAMEL Subscription Info GPRS Node Indicator GPRS Subscription Data GPRS Subscription Data Withdraw GPRS Support Indicator Group Id GSM bearer capability Guidance information Handover number High Layer Compatibility HLR Id HLR number HO-Number Not Required IMEI IMSI Inter CUG options Intra CUG restrictions

SS-Event-Data SS-Info SS-Status Stored location area Id Subscriber State Subscriber Status Supported CAMEL Phases Suppress T-CSI Suppression of Announcement Target cell Id Target location area Id Target MSC number Teleservice TMSI Trace reference Trace type User error USSD Data Coding Scheme USSD String UU Data UUS CF Interaction VBS Data VGCS Data VLR CAMEL Subscription Info VLR number VPLMN address allowed Zone Code

2509

2510

7.6.1 Common parameters

2511 The following set of parameters are used in several MAP service-primitives:

2512 7.6.1.1

Invoke Id

2513 This parameter identifies corresponding service primitives. The parameter is supplied by the MAP service-user and 2514 must be unique over each service-user/service-provider interface.

2515 7.6.1.2

Linked Id

2516 This parameter us used for linked services and it takes the value of the invoke Id of the service linked to.

2517 7.6.1.3
-

Provider error

2518 This parameter is used to indicate a protocol related type of error: 2519 2520 2521 2522 2523 2524 2525 2526 2527

duplicated invoke Id; not supported service; mistyped parameter; resource limitation; initiating release, i.e. the peer has already initiated release of the dialogue and the service has to be released; unexpected response from the peer; service completion failure; no response from the peer; invalid response received.

136

3GPP

137 Release 1998

70

3GPP TS 09.02 V7.15.0 (2004-03)

2528 7.6.1.4
NOTE:

User error

2529 This parameter can take values as follows: 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560

The values are grouped in order to improve readability; the grouping has no other significance.

a) Generic error: system failure, i.e. a task cannot be performed because of a problem in another entity. The type of entity or network resource may be indicated by use of the network resource parameter; data missing, i.e. an optional parameter required by the context is missing; unexpected data value, i.e. the data type is formally correct but its value or presence is unexpected in the current context; resource limitation; initiating release, i.e. the receiving entity has started the release procedure; facility not supported, i.e. the requested facility is not supported by the PLMN; incompatible terminal, i.e. the requested facility is not supported by the terminal.

b) Identification or numbering problem: unknown subscriber, i.e. no such subscription exists; number changed, i.e. the subscription does not exist for that number any more; unknown MSC; unidentified subscriber, i.e. if the subscriber is not contained in the database and it has not or cannot be established whether or not a subscription exists; unallocated roaming number; unknown equipment; unknown location area.

c) Subscription problem: roaming not allowed, i.e. a location updating attempt is made in an area not covered by the subscription; illegal subscriber, i.e. illegality of the access has been established by use of authentication procedure; bearer service not provisioned; teleservice not provisioned; illegal equipment, i.e. the IMEI check procedure has shown that the IMEI is blacklisted or not whitelisted.

d) Handover problem: no handover number available; subsequent handover failure, i.e. handover to a third MSC failed for some reason.

e) Operation and maintenance problem: tracing buffer full, i.e. tracing cannot be performed because the tracing capacity is exceeded.

138

3GPP

139 Release 1998

71

3GPP TS 09.02 V7.15.0 (2004-03)

2561 2562 2563

f) Call set-up problem: no roaming number available, i.e. a roaming number cannot be allocated because all available numbers are in use; absent subscriber, i.e. the subscriber has activated the detach service or the system detects the absence condition. This error may be qualified to indicate whether the subscriber was IMSI detached, in a restricted area or did not respond to paging; busy subscriber. This error may be qualified to indicate that the subscriber was busy due to CCBS and that CCBS is possible; no subscriber reply; forwarding violation, i.e. the call has already been forwarded the maximum number of times that is allowed; CUG reject, i.e. the call does not pass a CUG check; additional information may also be given in order to indicate rejection due to e.g. incoming call barred or non-CUG membership. call barred. Optionally, additional information may be included for indicating either that the call meets a barring condition set by the subscriber or that the call is barred for operator reasons. In case of barring of Mobil Terminating Short Message, the additional information may indicate a barring condition due to unauthorised Message Originator. optimal routeing not allowed, i.e. the entity which sends the error does not support optimal routeing, or the HLR will not accept an optimal routeing interrogation from the GMSC, or the call cannot be optimally routed because it would contravene optimal routeing constraints. forwarding failed, i.e. the GMSC interrogated the HLR for forwarding information but the HLR returned an error.

2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592

g) Supplementary services problem: call barred; illegal SS operation; SS error status; SS not available; SS subscription violation; SS incompatibility; negative password check; password registration failure; Number of Password Attempts; USSD Busy; Unknown Alphabet. short term denial; long term denial.

2593 For definition of these errors see GSM 04.80.

140

3GPP

141 Release 1998

72

3GPP TS 09.02 V7.15.0 (2004-03)

2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616

h) Short message problem: SM delivery failure with detailed reason as follows: memory capacity exceeded; MS protocol error; MS not equipped; unknown service centre (SC); SC congestion; invalid SME address; subscriber is not an SC subscriber; and possibly detailed diagnostic information, coded as specified in TS GSM 03.40, under SMS-SUBMITREPORT and SMS-DELIVERY-REPORT. If the SM entity which returns the SM Delivery Failure error includes detailed diagnostic information, it shall be forwarded in the MAP_MO_FORWARD_SHORT_MESSAGE and in the MAP_MT_FORWARD_SHORT_MESSAGE response.

message waiting list full, i.e. no further SC address can be added to the message waiting list; Subscriber busy for MT SMS, i.e. the mobile terminated short message transfer cannot be completed because: another mobile terminated short message transfer is going on and the delivery node does not support message buffering; or another mobile terminated short message transfer is going on and it is not possible to buffer the message for later delivery; or the message was buffered but it is not possible to deliver the message before the expiry of the buffering time defined in GSM 03.40;

Absent Subscriber SM, i.e. the mobile terminated short message transfer cannot be completed because the network cannot contact the subscriber. Diagnostic information regarding the reason for the subscriber's absence may be included with this error.

2617

i) Location services problem: Unauthorized Requesting Network Unauthorized LCS Client with detailed reason as follows Unauthorzied Privacy Class Unauthoized Call Unrelated External Client Unauthorized Call Related External Client Privacy override not applicable Position method failure with detailed reason as follows: Congestion Insufficient resources Insufficient Measurement Data Inconsistent Measurement Data Location procedure not completed

2618 2619 2620 2621 2622 2623


2624

2625 2626 2627 2628 2629

142

3GPP

143 Release 1998

73

3GPP TS 09.02 V7.15.0 (2004-03)

2630 2631 2632 2633 2634 2635 7.6.1.5

Location procedure not supported by target MS QoS not attainable Position Method Not Available in Network Position Method Not Available in Location Area

-Unknown or unreachable LCS Client

All Information Sent

2636 This parameter indicates to the receiving entity when the sending entity has sent all necessary information.

2637 2638 7.6.2.1

7.6.2 Numbering and identification parameter


IMSI

2639 This parameter is the International Mobile Subscriber Identity defined in GSM 03.03.

2640 7.6.2.2

TMSI

2641 This parameter is the Temporary Mobile Subscriber Identity defined in GSM 03.03.

2642 7.6.2.3

IMEI

2643 This parameter is the International Mobile Equipment Identity defined in GSM 03.03.

2644 7.6.2.4

Previous location area Id

2645 This parameter refers to the identity of the location area from which the subscriber has roamed.

2646 7.6.2.5

Stored location area Id

2647 This parameter refers to the location area where the subscriber is assumed to be located.

2648 7.6.2.6

Current location area Id

2649 This parameter is used to indicate the location area in which the subscriber is currently located.

2650 7.6.2.7

Target location area Id

2651 This parameter refers to the location area into which the subscriber intends to roam.

2652 7.6.2.8

Target cell Id

2653 This parameter refers to the identity of the cell to which a call has to be handed over.

2654 7.6.2.9 2655 7.6.2.10

Void Originating entity number

2656 This parameter refers to an application layer identification of a system component in terms of its associated ISDN 2657 number.

2658 7.6.2.11

MSC number

2659 This parameter refers to the ISDN number of an MSC.

144

3GPP

145 Release 1998

74

3GPP TS 09.02 V7.15.0 (2004-03)

2660 7.6.2.12

Target MSC number

2661 This parameter refers to the ISDN number of an MSC to which a call has to be handed over.

2662 7.6.2.13

HLR number

2663 This parameter refers to the ISDN number of an HLR.

2664 7.6.2.14

VLR number

2665 This parameter refers to the ISDN number of a VLR.

2666 7.6.2.15

HLR Id

2667 This parameter refers to the identity of an HLR derived from the IMSI defined in CCITT Recommendation E.212.

2668 7.6.2.16

LMSI

2669 This parameter refers to a local identity allocated by the VLR to a given subscriber for internal management of data in 2670 the VLR. LMSI shall not be sent to the SGSN.

2671 7.6.2.17

MS ISDN

2672 This parameter refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with CCITT 2673 Recommendation E.213.

2674 7.6.2.18

OMC Id

2675 This parameter refers to the identity of an operation and maintenance centre.

2676 7.6.2.19

Roaming number

2677 This parameter refers to the roaming number as defined in CCITT Recommendation E.213.

2678 7.6.2.20 2679 7.6.2.21

Void Handover number

2680 This parameter refers to the number used for routing a call between MSCs during handover.

2681 7.6.2.22

Forwarded-to number

2682 This parameter refers to the address to which a call is to be forwarded. This may include a subaddress. For subscribers 2683 having an originating CAMEL Phase 2 subscription this address need not be in non-E.164 international format.

2684 7.6.2.23

Forwarded-to subaddress

2685 This parameter refers to the sub-address attached to the address to which a call is to be forwarded.

2686 7.6.2.24

Called number

2687 This parameter refers to a called party number as defined in CCITT Recommendation Q.767.

2688 7.6.2.25

Calling number

2689 This parameter refers to a calling party number as defined in CCITT Recommendation Q.767.

146

3GPP

147 Release 1998

75

3GPP TS 09.02 V7.15.0 (2004-03)

2690 7.6.2.26

Originally dialled number

2691 This parameter refers to the number dialled by the calling party in order to reach a mobile subscriber.

2692 7.6.2.27

Service centre address

2693 This parameter represents the address of a Short Message Service Centre.

2694 7.6.2.28

Zone Code

2695 This parameter is used to define location areas into which the subscriber is allowed or not allowed to roam (regional 2696 subscription). With a complete list of Zone Codes the VLR or the SGSN is able to determine for all its location areas 2697 whether roaming is allowed or not.

2698 7.6.2.29

MSIsdn-Alert

2699 This parameter refers to the MSISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service 2700 Centre when the MS is again attainable.

2701 7.6.2.30

Location Information

2702 This parameter indicates the location of the served subscriber as defined in GSM 03.18.

2703 7.6.2.31

GMSC Address

2704 This parameter refers to the E.164 address of a GMSC.

2705 7.6.2.32

VMSC Address

2706 This parameter refers to the E.164 address of a VMSC.

2707 7.6.2.33

Group Id

2708 This parameter is used to describe groups a subscriber can be member of. A subscriber can partake in all group calls 2709 (VBS/VGCS) where he subscribed to the respective groups.

2710 7.6.2.34

North American Equal Access preferred Carrier Id

2711 This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an interexchange 2712 carrier. This identity is used at: 2713 2714 2715

outgoing calls: when the subscriber does not specify at call setup a carrier identity; forwarded calls: when a call is forwarded by the subscriber; incoming calls: applicable to the roaming leg of the call.

2716 7.6.2.35

SIWFS Number

2717 This parameter refers to the number used for routing a call between the MSC and the SIWFS (used by ISUP).

2718 7.6.2.36

B-subscriber address

2719 This parameter refers to the address used by the SIWFS to route the outgoing call from the SIWFS to either the B2720 subscriber in case the non-loop method or back to the VMSC in case of the loop method.

2721 7.6.2.37

Serving cell Id

2722 This parameter indicates the cell currently being used by the served subscriber.

148

3GPP

149 Release 1998

76

3GPP TS 09.02 V7.15.0 (2004-03)

2723 7.6.2.38

SGSN number

2724 This parameter refers to the ISDN number of a SGSN.

2725 7.6.2.39

SGSN address

2726 This parameter refers to the IP-address of a SGSN. This parameter is defined in GSM 03.03.

2727 7.6.2.40

GGSN address

2728 This parameter refers to the IP-address of a GGSN. This parameter is defined in GSM 03.03.

2729 7.6.2.41

GGSN number

2730 This parameter refers to the ISDN number of a GGSN or the ISDN number of the protocol-converter if a protocol2731 converting GSN is used between the GGSN and the HLR..

2732 7.6.2.42

APN

2733 This parameter refers to the DNS name of a GGSN. This parameter is defined in GSM 03.60.

2734 7.6.2.43

Network Node number

2735 This parameter refers either to the ISDN number of SGSN or to the ISDN number of MSC.

2736 7.6.2.44

PDP-Type

2737 This parameter indicates which type of protocol is used by the MS as defined in GSM 03.60.

2738 7.6.2.45

PDP-Address

2739 This parameter indicates the address of the data protocol as defined in GSM 03.60.

2740 7.6.2.46

Additional number

2741 This parameter can refer either to the SGSN number or to the MSC number.

2742 7.6.2.47

P-TMSI

2743 This parameter is the Packet Temporary Mobile Subscriber Identity defined in GSM 03.03.

2744 7.6.2.48

B-subscriber number

2745 This parameter refers to the number of the destination B dialled by the A user. This may include a subaddress.

2746 7.6.2.49

B-subscriber subaddress

2747 This parameter refers to the sub-address attached to the destination B dialled by the A user.

150

3GPP

151 Release 1998

77

3GPP TS 09.02 V7.15.0 (2004-03)

2748 7.6.2.50

LMU Number

2749 This parameter refers to a local number assigned to an LMU by an SMLC.

2750 7.6.2.51

MLC Number

2751 This parameter refers to the ISDN (E.164) number of an MLC.

2752 2753 7.6.3.1

7.6.3 Subscriber management parameters


Category

2754 This parameter refers to the calling party category as defined in CCITT Recommendation Q.767.

2755 7.6.3.2

Equipment status

2756 This parameter refers to the status of the mobile equipment as defined in GSM 02.16.

2757 7.6.3.3

Extensible Bearer service

2758 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in TS 2759 GSM 02.02. This parameter is used only for subscriber profile management. Extensible Bearer service values include 2760 all values defined for a Bearer service parameter (7.6.4.38).

2761 7.6.3.4

Extensible Teleservice

2762 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in TS GSM 02.03. 2763 This parameter is used only for subscriber profile management. Extensible Teleservice values include all values defined 2764 for a Teleservice parameter (7.6.4.39).

2765 7.6.3.5
2766 2767 2768 2769

Extensible Basic Service Group

This parameter refers to the Basic Service Group either as an extensible bearer service (see subclause 7.6.3.3) or an extensible teleservice (see subclause 7.6.3.4). This parameter is used only for subscriber profile management. The null value (i.e. neither extensible bearer service nor extensible teleservice) is used to denote the group containing all extensible bearer services and all extensible teleservices.

2770 7.6.3.6

GSM bearer capability

2771 This parameter refers to the GSM bearer capability information element defined in GSM 04.08.

2772 7.6.3.7
-

Subscriber Status

2773 This parameter refers to the barring status of the subscriber: 2774 2775

service granted; Operator Determined Barring.

2776 7.6.3.8

CUG Outgoing Access indicator

2777 This parameter represents the Outgoing Access as defined in ETS 300 136.

2778 7.6.3.9

Operator Determined Barring General Data

2779 This parameter refers to the set of subscribers features that the network operator or the service provider can regulate. 2780 This set only includes those limitations that can be controlled in the VLR or in the SGSN: 2781

All outgoing calls barred; (*)

152

3GPP

153 Release 1998

78

3GPP TS 09.02 V7.15.0 (2004-03)

2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794

International outgoing calls barred; (*) International outgoing calls except those to the home PLMN country barred; (*) Interzonal outgoing calls barred; (*) Interzonal outgoing calls except those to the home PLMN country barred; (*) Interzonal outgoing calls AND intenational outgoing calls except those directed to the home PLMN country barred; (*) Premium rate (information) outgoing calls barred; Premium rate (entertainment) outgoing calls barred; Supplementary service access barred; Invocation of call transfer barred; Invocation of chargeable call transfer barred; Invocation of internationally chargeable call transfer barred; Invocation of interzonally chargeable call transfer barred; -Invocation of call transfer where both legs are chargeable barred; -Invocation of call transfer if there is already an ongoing transferred call for the served subscriber in the serving MSC/VLR barred.

2795 2796
2797 2798

(*) Only these ODBs are supported by the SGSN. The SGSN applies them only for short message transfer.

2799 7.6.3.10

ODB HPLMN Specific Data

2800 This parameter refers to the set of subscribers features that the network operator or the service provider can regulate 2801 only when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in 2802 the VLR or in the SGSN: 2803 2804 2805 2806

Operator Determined Barring Type 1; Operator Determined Barring Type 2; Operator Determined Barring Type 3; Operator Determined Barring Type 4.

2807 7.6.3.11

Regional Subscription Data

2808 This parameter defines the regional subscription area in which the subscriber is allowed to roam. It consists of a list of 2809 Zone Codes (see subclause 7.6.2.28).

2810 7.6.3.12

Regional Subscription Response

2811 This parameter indicates either that the regional subscription data cannot be handled or that the current MSC or SGSN 2812 area is entirely restricted because of regional subscription.

2813 7.6.3.13

Roaming Restriction Due To Unsupported Feature

2814 This parameter defines that a subscriber is not allowed to roam in the current MSC area. It may be used by the HLR if a 2815 feature or service is indicated as unsupported by the VLR.

2816 7.6.3.14

Extensible SS-Info

2817 This parameter refers to all the information related to a supplementary service and is a choice between:

154

3GPP

155 Release 1998

79

3GPP TS 09.02 V7.15.0 (2004-03)

2818 2819 2820 2821

extensible forwarding information (see subclause 7.6.3.15); extensible call barring information (see subclause 7.6.3.20); CUG info extensible SS-Data (see subclause 7.6.3.22); (see subclause 7.6.3.29).

2822 7.6.3.15
-

Extensible Forwarding information

2823 This parameter represents the information related to each call forwarding service: 2824 2825 2826

the SS-Code of the relevant call forwarding service if required, a list of extensible forwarding feature parameters The list may contain one item per Basic Service Group.

(see subclause 7.6.4.1); (see subclause 7.6.3.16).

2827 7.6.3.16

Extensible Forwarding feature

2828 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 2829 following information, as required: 2830 2831 2832 2833 2834 2835

extensible Basic Service Group extensible SS-Status forwarded-to number forwarded-to subaddress extensible forwarding options extensible no reply condition timer

(see subclause 7.6.3.5); (see subclause 7.6.3.17); (see subclause 7.6.2.22); (see subclause 7.6.2.23); (see subclause 7.6.3.18); (see subclause 7.6.4.19).

2836 7.6.3.17

Extensible SS-Status

2837 This parameter refers to the state information of individual supplementary services as defined in TS GSM 03.11.

2838 7.6.3.18

Extensible Forwarding Options

2839 This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following 2840 informations: 2841 2842 2843 2844 2845

notification to forwarding party redirection notification to the forwarded-to party notification to calling party redirecting presentation Forwarding reason

(see TS GSM 02.82 for the meaning of this parameter); (see TS GSM 02.82 for the meaning of this parameter); (see TS GSM 02.82 for the meaning of this parameter); (see TS GSM 02.82 for the meaning of this parameter); (see TS GSM 02.82 for the meaning of this parameter).

2846 7.6.3.19

Extensible No reply condition timer

2847 This parameter refers to the extensible no reply condition timer for call forwarding on no reply.

2848 7.6.3.20
SS-Code

Extensible Call barring information


(see subclause 7.6.4.1);

2849 This parameter contains for each call barring service: 2850

156

3GPP

157 Release 1998

80

3GPP TS 09.02 V7.15.0 (2004-03)

2851 2852

a list of extensible call barring feature parameters The list may contain one item per Basic Service Group.

(see subclause 7.6.3.21).

2853 7.6.3.21

Extensible Call barring feature

2854 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 2855 contains the following information: 2856 2857

Extensible Basic Service Group provisioned SS-Status

(see subclause 7.6.3.5); (see subclause 7.6.3.17).

2858 7.6.3.22
-

CUG info

2859 This parameter refers to the overall information required for operation for each CUG: 2860 2861

CUG subscriptionList; CUG featureList.

2862 7.6.3.23

CUG subscription

2863 This parameter refers to the set of basic information for each CUG defined in that subscription. The following 2864 information is stored: 2865 2866 2867 2868

CUG index; CUG interlock; Intra CUG restrictions; Basic Service Group List.

2869 7.6.3.24

CUG interlock

2870 This parameter represents the CUG interlock code defined in ETS 300 138.

2871 7.6.3.25

CUG index

2872 This parameter represents the CUG index defined in ETS 300 138.

2873 7.6.3.26

CUG feature

2874 This parameter contains two parameters which are associated with the Basic Service Group. If the Basic Service Group 2875 Code is not present the feature applies to all Basic Services. The following parameters are included: 2876 2877 2878 2879 2880 2881

Preferential CUG indicator: indicates which CUG index is to be used at outgoing call set-up using the associated Basic Service Group;

Inter CUG Option: describes whether it for the associated Basic Service Group is allowed to make calls outside the CUG and whether incoming calls are allowed;

Basic Service Group.

2882 See TS GSM 02.85 for meaning of this parameter.

158

3GPP

159 Release 1998

81

3GPP TS 09.02 V7.15.0 (2004-03)

2883 7.6.3.27

Inter CUG options

2884 This parameter indicates the subscribers ability to make and receive calls outside a specific closed user group. It takes 2885 any of the following values: 2886 2887 2888 2889

CUG only facility (only calls within CUG are allowed); CUG with outgoing access (calls outside CUG allowed); CUG with incoming access (calls from outside CUG into CUG allowed); CUG with both incoming and outgoing access (all calls allowed).

2890 7.6.3.28

Intra CUG restrictions

2891 This parameter describes whether or not the subscriber is allowed to originate calls to or to receive calls from within the 2892 CUG. It can take any of the following values: 2893 2894 2895

no CUG restrictions; CUG incoming calls barred; CUG outgoing calls barred.

2896 7.6.3.29
SS-Code

Extensible SS-Data
(see subclause 7.6.4.1); (see subclause 7.6.3.17); (see subclause 7.6.3.30); (see subclause 7.6.3.31); (see subclause 7.6.3.5).

2897 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 2898 2899 2900 2901 2902

Extensible SS-Status (if applicable) Extensible Override subscription option (if applicable) Extensible CLI Restriction (if applicable) Extensible Basic Service Group Code

2903 7.6.3.30

Subscriber State

2904 This parameter indicates the state of the MS as defined in GSM 03.18.

2905 7.6.3.31

Requested Info

2906 This parameter indicates the subscriber information being requested as defined in GSM 03.18.

2907 7.6.3.32

Suppression of Announcement

2908 This parameter indicates if the announcement or tones shall be suppressed as defined in GSM 03.78.

2909 7.6.3.33

Suppress T-CSI

2910 This parameter is used to suppress the invocation of terminating CAMEL services.

2911 7.6.3.34

GMSC CAMEL Subscription Info

2912 This parameter contains CAMEL subscription information, i.e.O-CSI and/or T-CSI, which indicates to the GMSC that 2913 originating and/or terminating CAMEL services shall be invoked for the incoming call.

2914 7.6.3.35

VLR CAMEL Subscription Info

2915 This parameter identifies the subscriber as having CAMEL services which are invoked in the MSC.

160

3GPP

161 Release 1998

82

3GPP TS 09.02 V7.15.0 (2004-03)

2916 7.6.3.36

Supported CAMEL Phases

2917 This parameter indicates which phases of CAMEL are supported.

2918 7.6.3.37

CUG Subscription Flag

2919 This parameter indicates a that a subscriber with a T-CSI also has a CUG subscription. It is defined in TS GSM 03.78.

2920 7.6.3.38

CAMEL Subscription Info Withdraw

2921 This parameter indicates that CAMEL Subscription Info shall be deleted from the VLR.

2922 7.6.3.39

Voice Group Call Service (VGCS) Data

2923 This parameter refers to one or more groups a subscriber may be member of for voice group calls.

2924 7.6.3.40

Voice Broadcast Service (VBS) Data

2925 This parameter refers to one or more groups a subscriber may be member of for the voice broadcast service. Per group it 2926 is further indicated whether the subscriber is only allowed to listen to respective group calls or whether he is in addition 2927 entitled to initiate respective voice broadcast calls.

2928 7.6.3.41

ISDN bearer capability

2929 This parameter refers to the ISDN bearer capability information element defined in GSM 09.07.

2930 7.6.3.42

Lower layer Compatibility

2931 This parameter refers to the lower layer compatibility information element defined in GSM 04.08.

2932 7.6.3.43

High Layer Compatibility

2933 This parameter refers to the high layer compatibility information element defined in GSM 04.08.

2934 7.6.3.44

Alerting Pattern

2935 This parameter is an indication that can be used by the MS to alert the user in a specific manner in case of mobile 2936 terminating traffic (switched call or USSD). That indication can be an alerting level or an alerting category.

2937 7.6.3.45

GPRS Subscription Data Withdraw

2938 This parameter indicates that GPRS Subscription Data shall be deleted from the SGSN.

2939 7.6.3.46

GPRS Subscription Data

2940 This parameter refers to the list of PDP-Contexts that subscriber has subscribed to.

2941 7.6.3.47

QoS-Subscribed

2942 This parameter indicates the quality of service subscribed for a certain service. It is defined in GSM 03.60.

2943 7.6.3.48

VPLMN address allowed

2944 This parameter specifies whether the MS is allowed to used a dynamic address allocated in the VPLMN. It is defined in 2945 GSM 03.60.

162

3GPP

163 Release 1998

83

3GPP TS 09.02 V7.15.0 (2004-03)

2946 7.6.3.49

Roaming Restricted In SGSN Due To Unsupported Feature

2947 This parameter defines that a subscriber is not allowed to roam in the current SGSN area. It may be used by the HLR if 2948 a feature or service is indicated as unsupported by the SGSN.

2949 7.6.3.50

Network Access Mode

2950 This parameter is defined in GSM 03.08.

2951 7.6.3.51

Mobile Not Reachable Reason

2952 This parameter stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at 2953 the MSC, SGSN or both. It is defined in TS GSM 03.40.

2954 7.6.3.52

Cancellation Type

2955 This parameter indicates the reason of location cancellation. It is defined in TS GSM 03.60.

2956 7.6.3.53

All GPRS Data

2957 This parameter indicates to the SGSN that all GPRS Subscription Data shall be deleted for the subscriber.

2958 7.6.3.54

Complete Data List Included

2959 This parameter indicates to the SGSN that the complete GPRS Subscription Data stored for the Subscriber shall be 2960 replaced with the GPRS Subscription Data received.

2961 7.6.3.55

PDP Context Identifier

2962 This parameter is used to identify a PDP context for the subscriber.

2963 7.6.3.56

LSA Information

2964 This parameter refers to one or more localised service areas a subscriber may be a member of, together with the priority, 2965 the preferential access indicator, the active mode support indicator and active mode indication of each localised service 2966 area. The access right outside these localised service areas is also indicated.

2967 7.6.3.57

SoLSA support indicator

2968 This parameter indicates that the VLR or the SGSN supports SoLSA subscription.

2969 7.6.3.58

LSA Information Withdraw

2970 This parameter indicates that LSA information shall be deleted from the VLR or the SGSN.

2971 7.6.3.59

LMU Indicator

2972 This parameter indicates the presence of an LMU.

2973 7.6.3.60
-

LCS Information

2974 This parameter defines the LCS related information for an MS subscriber and contains the following components: 2975 2976 2977

GMLC List LCS Privacy Exception List MO-LR List

(see subclause 7.6.3.61) (see subclause 7.6.3.62) (see subclause 7.6.3.65A)

164

3GPP

165 Release 1998

84

3GPP TS 09.02 V7.15.0 (2004-03)

2978 7.6.3.61

GMLC List

2979 This parameter contains the addresses of all GMLCs that are permitted to issue a non-call related MT-LR location 2980 request for this MS. Usage of this parameter is defined in GSM 03.71.

2981 7.6.3.62

LCS Privacy Exception List

2982 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 2983 information is provided: 2984 2985

SS-Code a list of LCS privacy exception parameters

(see subclause 7.6.4.1); (see subclause 7.6.3.63).

2986 7.6.3.63

LCS Privacy Exception Parameters

2987 This parameter gives the status of each LCS privacy exception class and any additional parameters relevant to this class. 2988 The parameter contains the following information: 2989 2990 2991 2992

provisioned SS-Status privacy notification to MS user external client List internal client List

(see subclause 7.6.3.17); (see subclause 7.6.3.65B); (see subclause 7.6.3.64); (see subclause 7.6.3.65).

2993 7.6.3.64
2994 2995 2996 2997 2998

External Client List

This parameter is only applicable to the non-call related privacy class and gives the identities of the external clients that are allowed to locate a target MS for a non-call related MT-LR. Each identity is an international (e.g.E.164) address. For each identified external client, GMLC restrictions may be defined. It may also be indicated if the MS shall be notified of a non-restricted MT-LR from each identified LCS client.and, if so, whether notification only or notification with privacy verification shall apply. Usage of this parameter is defined in GSM 03.71.

2999 7.6.3.65

Internal Client List

3000 This parameter is only applicable to the PLMN operator privacy class and gives the identities of the internal PLMN 3001 operator clients that are allowed to locate a target MS for an NI-LR or MT-LR. Usage of this parameter is defined in 3002 GSM 03.71.

3003 7.6.3.66

MO-LR List

3004 This parameter defines the classes of MO-LR for which a subscription exists for a particular MS. For each class, the 3005 following information is provided: 3006

SS-Code

(see subclause 7.6.4.1).

3007 7.6.3.67
3008 3009 3010 3011 3012

Privacy Notification to MS User

This parameter is applicable to the non-call related privacy class and call related privacy class. For non- call related privacy class it indicates whether the MS user shall be notified for a non-call related MT-LR from any value added LCS client when the MT-LR is restricted and be enabled to accept or override the restriction. For call related privacy class it indicates whether the MS shall be notified of a call related MT-LR and, if so, whether notification only or notification with privacy verification shall apply. Usage of this parameter is defined in GSM 03.71.

3013 7.6.3.68

GMLC List Withdraw

3014 This parameter indicates whether the subscribers LCS GMLC list shall be deleted from the VLR. The parameter does 3015 not apply to, and shall be ignored if received by, an SGSN.

166

3GPP

167 Release 1998

85

3GPP TS 09.02 V7.15.0 (2004-03)

3016 3017 7.6.4.1

7.6.4 Supplementary services parameters


SS-Code

3018 This parameter may refer to one supplementary service or a set of supplementary services as defined in TS GSM 02.04. 3019 For MAP Release '98 this includes: 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037

Calling Line Identification Presentation service (CLIP); Calling Line Identification Restriction service (CLIR); Connected Line Identification Presentation service (COLP); Connected Line Identification Restriction service (COLR); Calling Name Presentation (CNAP) All Call Forwarding services; Call Waiting (CW); Call Hold (HOLD); Multi-Party service (MPTY); Closed User Group (CUG); All Charging services; All Call Restriction services; Explicit Call Transfer service (ECT); enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Completion of Calls to Busy Subscriber, originating side (CCBS-A); Completion of Calls to Busy Subscriber, destination side (CCBS-B); All LCS privacy exceptions Mobile Originating Location Request (MO-LR) (see subclause 7.6.4.44); (see subclause 7.6.4.45).

3038 7.6.4.2

SS-Status

3039 This parameter refers to the state information of individual supplementary services as defined in GSM 03.11.

3040 7.6.4.3
SS-Code

SS-Data
(see subclause 7.6.4.1); (see subclause 7.6.4.2); (see subclause 7.6.4.4); (see subclause 7.6.4.5); (see subclause 7.6.4.40).

3041 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 3042 3043 3044 3045 3046

SS-Status (if applicable) Override subscription option CLI Restriction Basic Service Group Code

168

3GPP

169 Release 1998

86

3GPP TS 09.02 V7.15.0 (2004-03)

3047 7.6.4.4

Override Category

3048 This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the 3049 following two values: 3050 3051

Enabled; Disabled.

3052 7.6.4.5

CLI Restriction Option

3053 This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can 3054 take the following three values: 3055 3056 3057

Permanent; Temporary (Default Restricted); Temporary (Default Allowed).

3058 7.6.4.6

Forwarding Options

3059 This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following 3060 values: 3061 3062 3063 3064

notification to forwarding party notification to calling party redirecting presentation Forwarding reason

(see GSM 02.82 for the meaning of this parameter); (see GSM 02.82 for the meaning of this parameter); (see GSM 02.82 for the meaning of this parameter); (see GSM 02.82 for the meaning of this parameter).

3065 7.6.4.7

No reply condition timer

3066 This parameter refers to the no reply condition timer for call forwarding on no reply.

3067 7.6.4.8 - 7.6.4.14 Void 3068 7.6.4.15


-

Forwarding information

3069 This parameter represents the information related to each call forwarding service: 3070 3071 3072

the SS-Code of the relevant call forwarding service if required, a list of forwarding feature parameters The list may contain one item per Basic Service Group.

(see subclause 7.6.4.1); (see subclause 7.6.4.16).

3073 7.6.4.16

Forwarding feature

3074 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 3075 following information, as required: 3076 3077 3078 3079 3080

Basic Service Group SS-Status forwarded-to number forwarded-to subaddress forwarding options

(see subclause 7.6.4.40); (see subclause 7.6.4.2); (see subclause 7.6.2.22); (see subclause 7.6.2.23); (see subclause 7.6.4.6);

170

3GPP

171 Release 1998

87

3GPP TS 09.02 V7.15.0 (2004-03)

3081

no reply condition timer

(see subclause 7.6.4.7).

3082 7.6.4.17 3083 7.6.4.18


SS-Code

Void Call barring information


(see subclause 7.6.4.1); (see subclause 7.6.4.19).

3084 This parameter contains for each call barring service: 3085 3086 3087

a list of call barring feature parameters The list may contain one item per Basic Service Group.

3088 7.6.4.19

Call barring feature

3089 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 3090 contains the following information: 3091 3092

Basic Service Group SS-Status

(see subclause 7.6.4.40); (see subclause 7.6.4.2).

3093 7.6.4.20

New password

3094 This parameter refers to the password which the subscriber just registered in the network. 3095 This parameter refers to a password used by the subscriber for supplementary service control.

3096 7.6.4.21

Current password

3097 This parameter refers to a password used by the subscriber for supplementary service control.

3098 7.6.4.22

Guidance information

3099 This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the 3100 following information may be given: 3101 3102 3103 3104 3105 3106

"enter password"; This information is used for checking of the old password.

"enter new password"; This information is used during password registration for the request of the first new password.

"enter new password again"; This information is used during password registration for the request of the new password again for verification.

172

3GPP

173 Release 1998

88

3GPP TS 09.02 V7.15.0 (2004-03)

3107 7.6.4.23 3108 7.6.4.24


-

Void SS-Info

3109 This parameter refers to all the information related to a supplementary service and is a choice between: 3110 3111 3112 3113 3114

forwarding information call barring information CUG info SS-Data eMLPP information

(see subclause 7.6.4.15); (see subclause 7.6.4.18); (see subclause 7.6.4.8); (see subclause 7.6.4.3). (see subclause 7.6.4.41).

3115 7.6.4.25-7.6.4.35 Void 3116 7.6.4.36 USSD Data Coding Scheme

3117 This parameter contains the information of the alphabet and the language used for the unstructured information in an 3118 Unstructured Supplementary Service Data operation. The coding of this parameter is according to the Cell Broadcast 3119 Data Coding Scheme as specified in GSM 03.38.

3120 7.6.4.37

USSD String

3121 This parameter contains a string of unstructured information in an Unstructured Supplementary Service Data operation. 3122 The string is sent either by the mobile user or the network. The contents of a string sent by the MS are interpreted by the 3123 network as specified in GSM 02.90.

3124 7.6.4.38

Bearer service

3125 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in TS 3126 GSM 02.02. This parameter is used only for supplementary service management.

3127 7.6.4.39

Teleservice

3128 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in TS GSM 02.03. 3129 This parameter is used only for supplementary service management.

3130 7.6.4.40

Basic Service Group

3131 This parameter refers to the Basic Service Group either as a bearer service (see subclause 7.6.4.38) or a teleservice (see 3132 subclause 7.6.4.39). This parameter is used only for supplementary service management. The null value (i.e. neither 3133 bearer service nor teleservice) is used to denote the group containing all bearer services and all teleservices.

3134 7.6.4.41

eMLPP information

3135 This parameter contains two parameters which are associated with the eMLPP service. The following two parameters 3136 are included: 3137 3138 3139 3140

maximum entitled priority: indicates the highest priority level the subscriber is allowed to apply for an outgoing call set-up;

default priority: defines the priority level which shall be assigned to a call if no explicit priority is indicated during call set-up.

174

3GPP

175 Release 1998

89

3GPP TS 09.02 V7.15.0 (2004-03)

3141 7.6.4.42

SS-event

3142 This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It 3143 can indicate one of the following services: 3144 3145 3146

Explicit Call Transfer (ECT) Call Deflection (CD) Multi-Party call (MPTY).

3147 7.6.4.43

SS-event data

3148 This parameter contains additional information related to Supplementary Service invocation. Depending on the service 3149 invoked it can contain the following information: 3150 3151

ECT A list with all Called Party Numbers involved. CDThe called Party number involved.

3152 7.6.4.44 3154


3155

LCS Privacy Exceptions

3153 Distinct SS codes are assigned to the following classes of LCS client in a target MS subscribers privacy exception list.

-Universal Class Call related value added class -Non-Call related value added class -PLMN operator class

3156 3157

3158 7.6.4.45 3160 3161 3162 3163 3164 7.6.5.1

Mobile Originating Location Request (MO-LR)

3159 Distinct SS codes are assigned to the following classes of MO-LR:

Basic Self Location Autonomous Self Location Transfer to Third Party.

7.6.5 Call parameters


Call reference number

3165 This parameter refers to a call reference number allocated by a call control MSC.

3166 7.6.5.2

Interrogation type

3167 This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can 3168 take either of two values: 3169 3170 3171

basic call (for information to route a call before the call has been extended to the VMSC of the called party); forwarding (for information to route the call to the forwarded-to destination after the VMSC of the forwarding party has requested the GMSC to resume handling of the call.

3172 7.6.5.3

OR interrogation

3173 This parameter indicates that the GMSC which interrogated the HLR for routeing information is not in the same PLMN 3174 as the HLR, and therefore that the call will potentially be optimally routed.

176

3GPP

177 Release 1998

90

3GPP TS 09.02 V7.15.0 (2004-03)

3175 7.6.5.4

OR capability

3176 This parameter indicates the phase of OR which the GMSC supports.

3177 7.6.5.5
-

Forwarding reason

3178 This parameter indicates the reason for which the call is to be forwarded. It can take one of three values: 3179 3180 3181

busy subscriber; mobile subscriber not reachable; no subscriber reply.

3182 7.6.5.6

Forwarding interrogation required

3183 This parameter indicates that if the VMSC of the forwarding subscriber requests the GMSC to resume handling of the 3184 call the GMSC shall interrogate the HLR for forwarding information.

3185 7.6.5.7

O-CSI

3186 This parameter identifies the subscriber as having originating CAMEL services as defined in TS GSM 03.78

3187 7.6.5.8

Call Direction

3188 This parameter is used to indicate the direction of the call.

3189 7.6.5.9

Channel Type

3190 This parameter is the result of a Channel Mode Modification for TS61/62. It contains the changed Air Interface User 3191 Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is 3192 defined in GSM 08.08.

3193 7.6.5.10

Chosen Channel

3194 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 3195 parameter is defined in GSM 08.08.

3196 7.6.5.11

CCBS Feature

3197 This parameter corresponds to the 'CCBS Description' parameter in GSM 03.93. It refers to the necessary set of 3198 information required in order to characterise a certain CCBS request. The parameter may contain the following 3199 information: 3200 3201 3202 3203

CCBS Index (see GSM 03.93 for the use of this parameter); B-subscriber number (see subclause 7.6.2.48); B-subscriber subaddress (see subclause 7.6.2.49); Basic Service Group Code (see subclause 7.6.4.40).

3204 7.6.5.12

UU Data

3205 This parameter includes User-To-User Data. It is defined in GSM 03.87.

3206 7.6.5.13

UUS CF Interaction

3207 This parameter indicates if the call forwarding or call deflection has been activated after UUS1 request has been 3208 accepted . It is defined in GSM 03.87.

178

3GPP

179 Release 1998

91

3GPP TS 09.02 V7.15.0 (2004-03)

3209 7.6.5.14

Number Portability Status

3210 This parameter indicates the number portability status of subscriber. See GSM 03.66.

3211

7.6.6 Radio parameters

3212 7.6.6.1-7.6.6.6 Void 3213 7.6.6.7 HO-Number Not Required

3214 This parameter indicates that no handover number allocation is necessary.

3215 3216 7.6.7.1


Rand; Sres; Kc.

7.6.7 Authentication parameters


Authentication set list

3217 This parameter represents a list of sets of authentication parameters for a given subscriber: 3218 3219 3220

3221 7.6.7.2

Rand

3222 This parameter represents a random number used for authentication.

3223 7.6.7.3

Sres

3224 This parameter represents the response to an authentication request.

3225 7.6.7.4

Kc

3226 This parameter refers to a key used for ciphering purposes.

3227 7.6.7.5 3228 7.6.7.6

Void Cksn

3229 This parameter refers to a ciphering key sequence number.

3230 7.6.7.7
-

Ciphering mode

3231 This parameter refers to the ciphering mode which is associated with a radio channel. It may take values as follows: 3232 3233

no encryption; identification of specific ciphering algorithm.

180

3GPP

181 Release 1998

92

3GPP TS 09.02 V7.15.0 (2004-03)

3234 3235 7.6.8.1

7.6.8 Short message parameters


SM-RP-DA

3236 This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be 3237 either of the following: 3238 3239 3240 3241 3242

IMSI LMSI MS-ISDN roaming number service centre address

(see subclause 7.6.2.1); (see subclause 7.6.2.16); (see subclause 7.6.2.17); (see subclause 7.6.2.19); (see subclause 7.6.2.27).

3243 7.6.8.2

SM-RP-OA

3244 This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be 3245 either of the following: 3246 3247

MS-ISDN service centre address

(see subclause 7.6.2.17); (see subclause 7.6.2.27).

3248 7.6.8.3
3249 3250 3251 3252

MWD status

This parameter indicates whether or not the address of the originator service centre is already contained in the Message Waiting Data file. In addition, it contains the status of the Memory Capacity Exceeded Flag (MCEF), the status of the Mobile subscriber Not Reachable Flag (MNRF) and the status of the Mobile station Not Reachable for GPRS flag (MNRG).

3253 7.6.8.4

SM-RP-UI

3254 This parameter represents the user data field carried by the short message service relay sub-layer protocol.

3255 7.6.8.5

SM-RP-PRI

3256 This parameter is used to indicate whether or not delivery of the short message shall be attempted when a service centre 3257 address is already contained in the Message Waiting Data file.

3258 7.6.8.6
-

SM Delivery Outcome

3259 This parameter indicates the cause for setting the message waiting data. It can take one of the following values: 3260 3261 3262

Absent subscriber; MS memory capacity exceeded; Successful transfer.

3263 7.6.8.7

More Messages To Send

3264 This parameter is used to indicate whether or not the service centre has more short messages to send.

182

3GPP

183 Release 1998

93

3GPP TS 09.02 V7.15.0 (2004-03)

3265 7.6.8.8
-

Alert Reason

3266 This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values: 3267 3268

MS present; Memory Available.

3269 7.6.8.9

Absent Subscriber Diagnostic SM

3270 This parameter is used to indicate the reason why the subscriber is absent. For the values for this parameter see TS 3271 GSM 03.40.

3272 7.6.8.10

Alert Reason Indicator

3273 This parameter indicates that the alert reason is sent to the HLR due to GPRS activity.

3274 7.6.8.11

Additional SM Delivery Outcome

3275 This parameter is used to indicate the GPRS delivery outcome in case a combination between delivery outcome for 3276 GPRS and non-GPRS are sent to the HLR.

3277 7.6.8.12

Additional Absent Subscriber Diagnostic SM

3278 This parameter indicates the reason of the additional SM Delivery Outcome.

3279 7.6.8.13

Delivery Outcome Indicator

3280 This parameter indicates that the delivery outcome sent to the HLR is for GPRS.

3281 7.6.8.14

GPRS Node Indicator

3282 This parameter indicates that the Network Node Number sent by the HLR is the SGSN number.

3283 7.6.8.15

GPRS Support Indicator

3284 This parameter indicates that the SMS-GMSC supports GPRS specific procedure of combine delivery of Short Message 3285 via MSC and/or via the SGSN.

3286 7.6.8.16

SM-RP-MTI

3287 This parameter represents the RP-Message Type Indicator of the Short Message. It is used to distinguish a SM sent to 3288 the mobile station in order to acknowledge an MO-SM initiated by the mobile from a normal MT-SM. This parameter is 3289 formatted according to the formatting rules of address fields as described in GSM 03.40.

3290 7.6.8.17

SM-RP-SMEA

3291 This parameter represents the RP-Originating SME-address of the Short Message Entity that has originated the SM. 3292 This parameter is used by the short message service relay sub-layer protocol and is formatted according to the 3293 formatting rules of address fields as described in GSM 03.40.

3294 3295 7.6.9.1

7.6.9 Access and signalling system related parameters


BSS-apdu

3296 This parameter includes one or two concatenated complete 08.06 messages, as described in GSM 03.09 and 3297 GSM 09.10. The Protocol ID indicates that the message or messages are according to GSM 08.06. For the coding of the 3298 messages see GSM 08.06 and GSM 08.08.

184

3GPP

185 Release 1998

94

3GPP TS 09.02 V7.15.0 (2004-03)

3299 7.6.9.2
-

CM service type

3300 This parameter identifies the service category being requested by the subscriber: 3301 3302 3303 3304 3305 3306 3307 3308

mobile originating call; emergency call establishment; short message service; mobile originating call re-establishment; mobile terminating call; SS request; Voice group call setup; Voice broadcast setup.

3309 7.6.9.3
-

Access connection status

3310 This parameter represents the following access connection status information: 3311 3312 3313

RR-connection status (established/not established); ciphering mode (on/off); authentication status (authenticated/not authenticated).

3314 7.6.9.4

External Signal Information

3315 This parameter contains concatenated information elements (including tag and length) which are defined by a common 3316 protocol version, preceded by the associated protocol ID. It is used to transport information of the indicated protocol via 3317 MAP interfaces.

3318 7.6.9.5

Access signalling information

3319 This parameter refers to any set of information elements imported from GSM 04.08.

3320 7.6.9.6

Location update type

3321 This parameter refers to the location update type (normal, periodic or IMSI attach) contained in the GSM 04.08 3322 LOCATION REGISTRATION REQUEST message.

3323 7.6.9.7

Protocol ID

3324 This parameter refers to the protocol to which the coding of the content of the associated External Signal Information 3325 conforms. 3326 The following values are defined: 3327 3328 3329 3330

04.08; 08.06; ETS 300 102-1. This value indicates the protocol defined by ETS 300 102-1 (EDSS1).

3331 7.6.9.8

Network signal information

3332 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1".

186

3GPP

187 Release 1998

95

3GPP TS 09.02 V7.15.0 (2004-03)

3333 The network signal information may include the following information elements as defined in GSM 09.07: 3334 3335 3336 3337 3338 3339

ISDN BC; the tag and length are defined by ETS 300 102-1. For the content, see GSM 09.07.

HLC; the tag and length are defined by ETS 300 102-1. For the content, see GSM 09.07.

LLC; the tag and length are defined by ETS 300 102-1. For the content, see GSM 09.07.

3340 They are contained in the Signal Information parameter according to figure 7.6/1 (irrespective of the order):

3341
3342

Figure 7.6/1: Network signal information parameter

3343 7.6.9.9

Call Info

3344 This parameter is transported as external signal information. The protocol ID shall be set to "GSM 04.08". 3345 The Call Info includes the set of information elements from the original SETUP message and is imported from 3346 GSM 04.08.

3347 7.6.9.10

Additional signal info

3348 This parameter is transported as ext-external signal information. The protocol ID shall be set to "ETS 300 356". 3349 The additional signal information may include the following information elements: 3350 3351

Calling Party Number as defined by ETS 300 356. Generic Number as defined by ETS 300 356.

3352 They are contained in the Signal Information parameter according to figure 7.6/2 (irrespective of the order):

188

3GPP

189 Release 1998

96

3GPP TS 09.02 V7.15.0 (2004-03)

3353
3354

Figure 7.6/2: Additional signal information parameter

3355 3356 7.6.10.1


-

7.6.10 System operations parameters


Network resources

3357 This parameter refers to a class or type of network resource: 3358 3359 3360 3361 3362 3363

PLMN; HLR; VLR (current or previous); MSC (controlling or current); EIR; radio sub-system.

3364 7.6.10.2

Trace reference

3365 This parameter represents a reference associated with a tracing request. The parameter is managed by OMC.

3366 7.6.10.3

Trace type

3367 This parameter identifies the type of trace. Trace types are fully defined in GSM 12.08.

3368 3369 7.6.11.1

7.6.11 Location Service Parameters


Age of Location Estimate

3370 This parameter indicates how long ago the location estimate was obtained.

3371 7.6.11.2 3372 7.6.11.3 3373 7.6.11.4

Void Void LCS Client ID

3374 This parameter provides information related to the identity of an LCS client.

3375 7.6.11.5

LCS Event

3376 This parameter identifies an event associated with the triggering of a location estimate.

190

3GPP

191 Release 1998

97

3GPP TS 09.02 V7.15.0 (2004-03)

3377 7.6.11.6

LCS MLC Data

3378 This parameter provides the identities of any authorized GMLCs for a target MS. Only these GMLCs are allowed to 3379 send a location request for an external client when location requests are restricted to these GMLCs.

3380 7.6.11.7

LCS Priority

3381 This parameter gives the priority of the location request.

3382 7.6.11.8
1)

LCS QoS
Response Time Indicates the category of response time low delay or delay tolerant.

3383 This parameter defines the Quality of Service (QoS) for any location request. It is composed of the following elements. 3384 3385 3386 3387 3388 3389 3390 3391

2)

Horizontal Accuracy Indicates the required horizontal accuracy of the location estimate.

3)

Vertical Coordinate Indicates if a vertical coordinate is required (in addition to horizontal coordinates).

4)

Vertical Accuracy Indicates the required vertical accuracy of the location estimate (inclusion is optional).

3392 7.6.11.9 3393 7.6.11.10 3394 7.6.11.11

Void Void Location Estimate

3395 This parameter gives an estimate of the location of an MS in universal coordinates and the accuracy of the estimate.

3396 7.6.11.12

Location Type

3397 This parameter indicates the type of location estimate required by the LCS client. Possible location estimate types 3398 include:

3399 3400 3401

current location current or last known location initial location for an emergency services call.

192

3GPP

193 Release 1998

98

3GPP TS 09.02 V7.15.0 (2004-03)

3402 7.6.11.13

NA-ESRD

3403 This parameter only applies to location for an emergency services call in North America and gives the North American 3404 Emergency Services Routing Digits.

3405 7.6.11.14

NA-ESRK

3406 This parameter only applies to location for an emergency services call in North America and gives the North American 3407 Emergency Services Routing Key.

3408 7.6.11.15 3409 7.6.11.16

Void Privacy Override

3410 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC for an MR-LR are 3411 in the same country.

3412 7.6.11.17 3413 7.6.11.18 3414 7.6.11.19 3415 3416

Void Void Void

7.7 Representation of a list of a basic parameter in serviceprimitives

3417 In some service-primitives several instances of a basic parameter of subclause 7.6 are required. In the service 3418 descriptions such cases will be represented as 3419

ParameterNameLIST

3420 in the tables where ParameterName refers to one of the parameters defined in subclause 7.6. This corresponds to the 3421 following construction rule:

3422
3423

Figure 7.7/1: Construction of Lists

3424 3425 3426

8 Mobility services
8.1 Location management services
8.1.1 MAP_UPDATE_LOCATION_AREA service
Definition

3427 8.1.1.1

3428 This service is used between MSC and VLR to update location information in the network. It is initiated by an MS 3429 when changing the location area or at first registration. The detailed conditions are given in GSM 03.12. 3430 The MAP_UPDATE_LOCATION_AREA service is a confirmed service using the primitives from table 8.1/1.

194

3GPP

195 Release 1998

99

3GPP TS 09.02 V7.15.0 (2004-03)

3431 8.1.1.2
3432

Service primitives
Table 8.1/1: MAP_UPDATE_LOCATION_AREA
Parameter name Invoke Id Target location area Id Serving cell Id Location update type IMSI TMSI Previous location area Id CKSN User error Provider error Request M M M M C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=) O

3433

3434 8.1.1.3
3435 Invoke Id

parameter definitions and use

3436 See definition in subclause 7.6.1. 3437 Target location area Id 3438 See definition in subclause 7.6.2. 3439 Serving cell Id 3440 See definition in subclause 7.6.2. 3441 Location update type 3442 See definition in subclause 7.6.9. 3443 IMSI 3444 See definition in subclause 7.6.2. It is up to the MS to provide either IMSI or TMSI, but one shall be present. 3445 TMSI 3446 See definition in subclause 7.6.2. It is up to the MS to provide either IMSI or TMSI, but one shall be present. 3447 Previous location area Id 3448 See definition in subclause 7.6.2. This parameter is provided if the updating is not a first registration. 3449 CKSN 3450 See definition in subclause 7.6.7. The CKSN is given if TMSI is used. 3451 User error 3452 One of the following error causes defined in subclause 7.6.1 is sent by the user in case of location area updating 3453 failures, depending on the failure reason: 3454 3455 3456 3457 3458

unknown subscriber; This cause is used if the subscriber is not known in the VLR and even a correlated request to the subscriber's HLR gives a negative result (i.e. the IMSI is not allocated to a subscriber).

unknown location area; This cause is used if the target location area identity given is not known in the VLR.

196

3GPP

197 Release 1998

100

3GPP TS 09.02 V7.15.0 (2004-03)

3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469

roaming not allowed; This cause is used if the MS is not allowed to roam into the target location area indicated in the MAP_UPDATE_LOCATION_AREA Req. The cause will be qualified according to the roaming restriction reason, i.e. one of "National Roaming Not Allowed", "PLMN Not Allowed", "Location Area Not Allowed", or "Operator Determined Barring".

illegal subscriber; This error is sent if a correlated authentication procedure has not authenticated the subscriber.

illegal equipment; This error is sent if an IMEI check failed, i.e. the IMEI is blacklisted or not white-listed.

system failure; unexpected data value.

3470 Provider error 3471 For definition of provider errors see subclause 7.6.1.

3472 3473 8.1.2.1

8.1.2 MAP_UPDATE_LOCATION service


Definition

3474 This service is used by the VLR to update the location information stored in the HLR. 3475 The MAP_UPDATE_LOCATION service is a confirmed service using the service primitives given in table 6.1/2.

3476 8.1.2.2
3477

Service primitives
Table 8.1/2: MAP_UPDATE_LOCATION
Parameter name Invoke Id IMSI MSC Address VLR number LMSI Supported CAMEL Phases SoLSA Support Indicator HLR number User error Provider error Request M M M M U C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

3478

3479 8.1.2.3
3480 Invoke Id

Parameter definitions and use

3481 See definition in subclause 5.6.1. 3482 IMSI 3483 See definition in subclause 5.6.2. 3484 MSC Address 3485 See definition in subclause 5.6.2. The MSC address is used for short message delivery only and for each incoming call 3486 set-up attempt the MSRN will be requested from the VLR.

198

3GPP

199 Release 1998

101

3GPP TS 09.02 V7.15.0 (2004-03)

3487 VLR number 3488 See definition in subclause 5.6.2. 3489 LMSI 3490 See definition in subclause 5.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the 3491 HLR to support the LMSI handling procedures. 3492 Supported CAMEL Phases 3493 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 3494 phase 1 is supported. Otherwise may be absent. 3495 HLR number 3496 See definition in subclause 5.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3497 SoLSA Support Indicator 3498 3499 3500 3501

This parameter is used by the VLR to indicate to the HLR in the Update Location indication that SoLSA is supported. If this parameter is not included in the Update Location indication and the Subscriber is marked as only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the VLR that roaming is not allowed to that Subscriber in the VLR.

3502 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 3503 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 3504 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 3505 User error 3506 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3507 subclause 5.6.1 may be used, depending on the nature of the fault: 3508 3509 3510 3511 3512 3513 3514

unknown subscriber; roaming not allowed; This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the VLR number. The cause is qualified by the roaming restriction reason "PLMN Not Allowed" or "Operator Determined Barring". If no qualification is received (HLR with MAP Version 1), "PLMN Not Allowed" is taken as default.

system failure; unexpected data value.

3515 Provider error 3516 For definition of provider errors see subclause 5.6.1.

3517 3518 8.1.3.1

8.1.3 MAP_CANCEL_LOCATION service


Definition

3519 This service is used between HLR and VLR to delete a subscriber record from the VLR. It may be invoked 3520 automatically when an MS moves from one VLR area to another, to remove the subscriber record from the old VLR, or 3521 by the HLR operator to enforce a location updating from the VLR to the HLR, e.g. on withdrawal of a subscription. 3522 Also this service is used between HLR and SGSN to delete a subscriber record from the SGSN. It may be invoked 3523 automatically when an MS moves from one SGSN area to another, to remove the subscriber record from the old SGSN, 3524 or by the HLR operator to enforce a location updating from the SGSN to the HLR. 3525 The MAP_CANCEL_LOCATION service is a confirmed service using the primitives defined in table 8.1/3.

200

3GPP

201 Release 1998

102

3GPP TS 09.02 V7.15.0 (2004-03)

3526 8.1.3.2
3527

Service primitives
Table 8.1/3: MAP_CANCEL_LOCATION
Parameter name Invoke Id IMSI LMSI Cancellation Type User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C(=) O

3528

3529 8.1.3.3
3530 Invoke Id

Parameter definitions and use

3531 See definition in subclause 7.6.1. 3532 IMSI 3533 See definition in subclause 7.6.2. 3534 LMSI 3535 See definition in subclause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable 3536 between SGSN and HLR. 3537 Value 0000 0000 can be used to indicate that the LMSI is not in use. 3538 Cancellation Type 3539 See definition in subclause 5.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the 3540 SGSN. If the VLR receives this parameter and do not understand it the VLR shall ignore it. 3541 User error 3542 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. The one of the following error 3543 causes defined in subclause 5.6.1 shall be used: 3544 3545

unexpected data value; data missing.

3546 Provider error 3547 For definition of provider errors see subclause 7.6.1.

3548 3549 8.1.4.1

8.1.4 MAP_SEND_IDENTIFICATION service


Definition

3550 The MAP_SEND_IDENTIFICATION service is used between a VLR and a previous VLR to retrieve IMSI and 3551 authentication sets for a subscriber registering afresh in that VLR. 3552 The MAP_SEND_IDENTIFICATION service is a confirmed service using the service primitives defined in table 8.1/4.

202

3GPP

203 Release 1998

103

3GPP TS 09.02 V7.15.0 (2004-03)

3553 8.1.4.2
3554

Service primitives
Table 8.1/4: MAP_SEND_IDENTIFICATION
Parameter name Invoke Id TMSI IMSI Authentication set User error Provider error Request M M Indication M(=) M(=) Response M(=) C U C Confirm M(=) C(=) C(=) C(=) O

3555

3556 8.1.4.3
3557 Invoke Id

Parameter definitions and use

3558 See definition in subclause 7.6.1. 3559 TMSI 3560 See definition in subclause 7.6.2. 3561 IMSI 3562 See definition in subclause 7.6.2. The IMSI is to be returned if the service succeeds. 3563 Authentication set 3564 See definition in subclause 7.6.7. If the service succeeds a list of up to five authentication sets is returned, if there are 3565 any available. 3566 User error 3567 This parameter is mandatory if the service fails. The following error cause defined in subclause 7.6.1 may be used, 3568 depending on the nature of the fault: 3569

unidentified subscriber.

3570 Provider error 3571 For definition of provider errors see subclause 7.6.1.

3572 3573 8.1.5.1

8.1.5 MAP_DETACH_IMSI service


Definition

3574 The MAP_DETACH_IMSI service is used by the MSC to indicate to the VLR that an MS is no longer reachable. The 3575 network needs this information e.g. to reject an incoming call without initiating paging on the radio path. 3576 The MAP_DETACH_IMSI service is a non-confirmed service using the service primitives defined in table 8.1/5.

3577 8.1.5.2
3578

Service primitives
Table 8.1/5: MAP_DETACH_IMSI
Parameter name Invoke Id Serving cell id IMSI TMSI Request M M C C Indication M(=) M(=) C(=) C(=)

3579

204

3GPP

205 Release 1998

104

3GPP TS 09.02 V7.15.0 (2004-03)

3580 8.1.5.3
3581 Invoke Id

Parameter definitions and use

3582 See definition in subclause 7.6.1. 3583 Serving cell id 3584 See definition in subclause 7.6.2. 3585 IMSI 3586 See definition in subclause 7.6.2. It is up to the MS to provide either IMSI or TMSI as subscriber identity, but one shall 3587 be present. 3588 TMSI 3589 See definition in subclause 7.6.2. It is up to the MS to provide either IMSI or TMSI as subscriber identity, but one shall 3590 be present.

3591 3592 8.1.6.1


3593 3594 3595 3596 3597 3598 3599 3600

8.1.6 MAP_PURGE_MS service


Definition

This service is used between the VLR and the HLR to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated call or a mobile terminated short message will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the VLR, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. Also this service is used between the SGSN and the HLR to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated short message or a network requested PDP-context activation will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the SGSN, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days.

3601 The MAP_PURGE_MS service is a confirmed service using the primitives defined in table 8.1/6.

3602 8.1.6.2
3603

Service primitives
Table 8.1/6: MAP_PURGE_MS
Parameter name Invoke Id IMSI VLR number Freeze TMSI Freeze P-TMSI SGSN number User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) C C(=) O Response M(=) C C Confirm M(=) C(=) C(=)

3604

3605 8.1.6.3
3606 Invoke ID

Parameter definitions and use

3607 See definition in subclause 7.6.1. 3608 IMSI 3609 See definition in subclause 7.6.2. 3610 VLR number 3611 Shall be present if the sender is VLR. See definition in subclause 7.6.2.

206

3GPP

207 Release 1998

105

3GPP TS 09.02 V7.15.0 (2004-03)

3612 SGSN number 3613 Shall be present if the sender is SGSN. See definition in subclause 7.6.2 3614 Freeze TMSI 3615 This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR 3616 number matches the stored VLR number. 3617 Freeze P-TMSI 3618 This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received 3619 SGSN number matches the stored SGSN number. 3620 User error 3621 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 3622 3623 3624

Data Missing; Unexpected Data Value; UnknownSubscriber.

3625 Provider error 3626 See definition of provider errors in subclause 7.6.1.

3627 3628 8.1.7.1

8.1.7 MAP_UPDATE_GPRS_LOCATION service


Definition

3629 This service is used by the SGSN to update the location information stored in the HLR. 3630 The MAP_UPDATE_GPRS_LOCATION service is a confirmed service using the service primitives given in 3631 table 8.1/7.

3632 8.1.7.2
3633

Service primitives
Table 8.1/7: MAP_UPDATE_GPRS_LOCATION
Parameter name Invoke Id IMSI SGSN number SGSN address SoLSA Support Indicator HLR number User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

3634

3635 8.1.7.3
3636 Invoke Id

Parameter definitions and use

3637 See definition in subclause 7.6.1. 3638 IMSI 3639 See definition in subclause 7.6.2. 3640 SGSN number 3641 See definition in subclause 7.6.2.

208

3GPP

209 Release 1998

106

3GPP TS 09.02 V7.15.0 (2004-03)

3642 SGSN address 3643 See definition in subclause 7.6.2. 3644 SoLSA Support Indicator 3645 3646 3647 3648

This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that SoLSA is supported. If this parameter is not included in the Update GPRS Location indication and the Subscriber is marked as only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the SGSN that roaming is not allowed to that Subscriber in the SGSN.

3649 This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a 3650 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support 3651 indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted. 3652 HLR number 3653 See definition in subclause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3654 User error 3655 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3656 subclause 7.6.1 may be used, depending on the nature of the fault: 3657 3658 3659 3660 3661 3662 3663

unknown subscriber; roaming not allowed; This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the SGSN number. The cause is qualified by the roaming restriction reason "PLMN Not Allowed" or "Operator Determined Barring".

system failure; unexpected data value.

The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown.

3664 Provider error 3665 For definition of provider errors see subclause 7.6.1.

3666 3667 3668 8.2.1.1

8.2 Paging and search


8.2.1 MAP_PAGE service
Definition

3669 This service is used between VLR and MSC to initiate paging of an MS for mobile terminated call set-up, mobile 3670 terminated short message or unstructured SS notification. 3671 The MAP_PAGE service is a confirmed service using the primitives from table 8.2/1.

210

3GPP

211 Release 1998

107

3GPP TS 09.02 V7.15.0 (2004-03)

3672 8.2.1.2
3673

Service primitives
Table 8.2/1: MAP_PAGE
Parameter name Invoke Id IMSI Stored location area Id TMSI User error Provider error Request M M M U Indication M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

C(=) O

3674

3675 8.2.1.3
3676 Invoke Id

Parameter definitions and use

3677 See definition in subclause 7.6.1. 3678 IMSI 3679 See definition in subclause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging 3680 on the radio path uses the IMSI as an identifier. 3681 Stored location area Id 3682 See definition in subclause 7.6.2. 3683 TMSI 3684 See definition in subclause 7.6.2. The TMSI is included if paging on the radio channel is to use the TMSI as an 3685 identifier. 3686 User error 3687 The following error causes defined in subclause 7.6.1 may be sent by the user in case of a paging error, depending on 3688 the failure reason: 3689 3690 3691 3692 3693 3694 3695

absent subscriber; unknown location area; busy subscriber; system failure; This corresponds to the case where there is no call associated with the MAP_PAGE service, i.e. if the call has been released but the dialogue to the VLR has not been aborted.

unexpected data value.

3696 Provider error 3697 See definition in subclause 7.6.1.

3698 3699 8.2.2.1

8.2.2 MAP_SEARCH_FOR_MS service


Definition

3700 This service is used between VLR and MSC to initiate paging of an MS in all location areas of that VLR. It is used if 3701 the VLR does not hold location area information confirmed by radio contact. 3702 The MAP_SEARCH_FOR_MS service is a confirmed service using the primitives from table 8.2/2.

212

3GPP

213 Release 1998

108

3GPP TS 09.02 V7.15.0 (2004-03)

3703 8.2.2.2
3704

Service primitives
Table 8.2/2: MAP_SEARCH_FOR_MS
Parameter name Invoke Id IMSI Current location area Id User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

3705

3706 8.2.2.3
3707 Invoke Id

Parameter definitions and use

3708 See definition in subclause 7.6.1. 3709 IMSI 3710 See definition in subclause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path. 3711 Current location area Id 3712 See definition in subclause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the 3713 Location Area Id of the area in which the MS responded is given in the response. 3714 User error 3715 The following error causes defined in subclause 7.6.1 shall be sent by the user if the search procedure fails, depending 3716 on the failure reason: 3717 3718 3719 3720 3721 3722 3723

absent subscriber; This error cause is returned by the MSC if the MS does not respond to the paging request.

system failure; This corresponds to the case where there is no call associated with the MAP_SEARCH_FOR_MS service, i.e. if the call has been released but the dialogue to the VLR has not been aborted.

busy subscriber; unexpected data value.

3724 Provider error 3725 See definition in subclause 7.6.1.

3726 3727 3728 8.3.1.1

8.3 Access management services


8.3.1 MAP_PROCESS_ACCESS_REQUEST service
Definition

3729 This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. in case of mobile 3730 originated call set-up or after being paged by the network. 3731 The MAP_PROCESS_ACCESS_REQUEST service is a confirmed service using the primitives from table 8.3/1.

214

3GPP

215 Release 1998

109

3GPP TS 09.02 V7.15.0 (2004-03)

3732 8.3.1.2
3733

Service primitives
Table 8.3/1: MAP_PROCESS_ACCESS_REQUEST
Parameter name Invoke Id CM service type Access connection status Current Location Area Id Serving cell id TMSI Cksn IMSI IMEI MSISDN User error Provider error Request M M M M M C C C C Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C U C

C(=) C(=) C(=) C(=) O

3734

3735 8.3.1.3
3736 Invoke Id

Parameter definitions and use

3737 See definition in subclause 7.6.1. 3738 CM service type 3739 See definition in subclause 7.6.9. 3740 Access connection status 3741 See definition in subclause 7.6.9. 3742 Current Location Area Id 3743 See definition in subclause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure. 3744 Serving cell id 3745 See definition in subclause 7.6.2. 3746 TMSI 3747 See definition in subclause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, 3748 but one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace 3749 IMSI/TMSI. 3750 Cksn 3751 See definition in subclause 7.6.7. In case of access with TMSI, the Cksn shall be present. 3752 IMSI 3753 See definition in subclause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, 3754 but one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace 3755 IMSI/TMSI. 3756 In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM 3757 Service Type "Emergency Call Establishment", IMEI may replace IMSI. 3758 IMEI 3759 See definition in subclause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the 3760 Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment".

216

3GPP

217 Release 1998

110

3GPP TS 09.02 V7.15.0 (2004-03)

3761 MSISDN 3762 See definition in subclause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator 3763 option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding. 3764 User error 3765 One of the following error causes defined in subclause 7.6.1 shall be sent by the user if the access request fails, 3766 depending on the failure reason: 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778

unidentified subscriber; illegal subscriber; This error is sent if a correlated authentication procedure has not authenticated the subscriber.

illegal equipment; This error is sent if an IMEI check failed, i.e. the IMEI is blacklisted or not white-listed.

roaming not allowed; This cause is used after VLR restart if the subscriber has no subscription for the current location area, e.g. due to regional subscription. The cause will be qualified by "location area not allowed" or "national roaming not allowed", respectively.

unknown location area; system failure; unexpected data value.

3779 Provider error 3780 For definition of provider errors see subclause 7.6.1.

3781 3782 3783 8.4.1.1

8.4 Handover services


8.4.1 MAP_PREPARE_HANDOVER service
Definition

3784 This service is used between MSC-A and MSC-B (E-interface) when a call is to be handed over from MSC-A to 3785 MSC-B. 3786 The MAP_PREPARE_HANDOVER service is a confirmed service using the primitives from table 8.4/1.

3787 8.4.1.2
3788

Service primitives
Table 8.4/1: MAP_PREPARE_HANDOVER
Parameter name Invoke Id Target Cell Id HO-NumberNotRequired BSS-APDU Handover Number User error Provider error Request M C C C Indication M(=) C(=) C(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O

3789

218

3GPP

219 Release 1998

111

3GPP TS 09.02 V7.15.0 (2004-03)

3790 8.4.1.3
3791 Invoke Id

Parameter use

3792 For definition of this parameter see subclause 7.6.1. 3793 Target Cell Id 3794 For definition of this parameter see subclause 7.6.2. This parameter is only included if the service is not in an ongoing 3795 transaction. 3796 HO-Number Not Required 3797 For definition of this parameter see subclause 7.6.6. 3798 BSS-APDU 3799 For definition of this parameter see subclause 7.6.9. 3800 Handover Number 3801 For definition of this parameter see subclause 7.6.2. This parameter shall be returned, unless the parameter HO3802 NumberNotRequired is sent. 3803 User error 3804 For definition of this parameter see subclause 7.6.1. The following errors defined in subclause 7.6.1 may be used, 3805 depending on the nature of the fault: 3806 3807 3808 3809

No handover number available; System failure; Unexpected data value; DataMissing.

3810 Provider error 3811 See definition of provider errors in subclause 7.6.1.

3812 3813 8.4.2.1

8.4.2 MAP_SEND_END_SIGNAL service


Definition

3814 This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by 3815 MSC-B to the MS. MSC-A retains then the main control of the call until it clears. 3816 The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either 3817 because the call has been released in MSC-A or because the call has been successfully handed over from MSC-B to 3818 another MSC. 3819 The MAP_SEND_END_SIGNAL service is a confirmed service using the primitives from table 8.4/2.

3820 8.4.2.2
3821

Service primitives
Table 8.4/2: MAP_SEND_END_SIGNAL
Parameter name Invoke Id BSS-APDU Provider error Request M M Indication M(=) M(=) Response M(=) Confirm M(=) O

3822

220

3GPP

221 Release 1998

112

3GPP TS 09.02 V7.15.0 (2004-03)

3823 8.4.2.3
3824 Invoke Id

Parameter use

3825 For definition of this parameter see subclause 7.6.1. 3826 BSS-APDU 3827 For definition of this parameter see subclause 7.6.9. 3828 Provider error 3829 For definition of this parameter see subclause 7.6.1.

3830 3831 8.4.3.1

8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service


Definition

3832 This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A-interface in 3833 MSC-B to MSC-A. 3834 The MAP_PROCESS_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 3835 table 8.4/3.

3836 8.4.3.2
3837

Service primitives
Table 8.4/3: MAP_PROCESS_ACCESS_SIGNALLING
Parameter name Invoke Id BSS-APDU Request M M Indication M(=) M(=)

3838

3839 8.4.3.3
3840 Invoke Id

Parameter use

3841 For definition of this parameter see subclause 7.6.1. 3842 BSS-APDU 3843 For definition of this parameter see subclause 7.6.9.

3844 3845 8.4.4.1

8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service


Definition

3846 This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface 3847 of MSC-B. 3848 The MAP_FORWARD_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 3849 table 8.4/4.

3850 8.4.4.2
3851

Service primitives
Table 8.4/4: MAP_FORWARD_ACCESS_SIGNALLING
Parameter name Invoke Id BSS-APDU Request M M Indication M(=) M(=)

3852

222

3GPP

223 Release 1998

113

3GPP TS 09.02 V7.15.0 (2004-03)

3853 8.4.4.3
3855 Invoke Id

Parameter use

3854 For the definition and use of all parameters and errors, see subclause 7.6.1

3856 For definition of this parameter see subclause 7.6.1. 3857 BSS-APDU 3858 For definition of this parameter see subclause 7.6.9.

3859 3860 8.4.5.1

8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service


Definition

3861 This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a 3862 handover to either MSC-A or a third MSC (MSC-B') is required. 3863 The MAP_PREPARE_SUBSEQUENT_HANDOVER service is a confirmed service using the primitives from 3864 table 8.4/5.

3865 8.4.5.2
3866

Service primitives
Table 8.4/5: MAP_PREPARE_SUBSEQUENT_HANDOVER
Parameter name Invoke Id Target Cell Id Target MSC Number BSS-APDU User error Provider error Request M M M M Indication M(=) M(=) M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

3867

3868 8.4.5.3
3869 Invoke Id

Parameter use

3870 For definition of this parameter see subclause 7.6.1. 3871 Target Cell Id 3872 For definition of this parameter see subclause 7.6.2. 3873 Target MSC Number 3874 For definition of this parameter see subclause 7.6.2. 3875 BSS-APDU 3876 For definition of this parameter see subclause 7.6.9. 3877 User error 3878 For definition of this parameter see subclause 7.6.1. The following error causes defined in subclause 7.6.1 may be used, 3879 depending on the nature of the fault: 3880 3881 3882

Unknown MSC; Subsequent handover failure; Unexpected data value;

224

3GPP

225 Release 1998

114

3GPP TS 09.02 V7.15.0 (2004-03)

3883

Data Missing.

3884 Provider error 3885 For definition of this parameter see subclause 7.6.1.

3886 3887 8.4.6.1

8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service


Definition

3888 This service is used between MSC and VLR (B-interface) to request a handover number. 3889 The MAP_ALLOCATE_HANDOVER_NUMBER service is a confirmed service using the primitives from table 8.4/6.

3890 8.4.6.2
3891

Service primitives
Table 8.4/6: MAP_ALLOCATE_HANDOVER_NUMBER

Parameter name Invoke Id User error Provider error

Request M

Indication M(=)

Response M(=) C

Confirm M(=) C(=) O

3892

3893 8.4.6.3
3894 Invoke Id

Parameter use

3895 For definition of this parameter see subclause 7.6.1. 3896 User error 3897 For definition of this parameter see subclause 7.6.1. The following errors defined in subclause 7.6.1 may be used, 3898 depending on the nature of the fault: 3899

No handover number available.

3900 Provider error 3901 For definition of this parameter see subclause 7.6.1.

3902 3903 8.4.7.1

8.4.7 MAP_SEND_HANDOVER_REPORT service


Definition

3904 This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and 3905 used by MSC-A. 3906 The MAP_SEND_HANDOVER_REPORT service is a confirmed service using the primitives from table 8.4/7.

3907 8.4.7.2
3908

Service primitives
Table 8.4/7: MAP_SEND_HANDOVER_REPORT

Parameter name Invoke Id Handover Number M

Request M M M(=)

Indication M(=) M(=) O

Response M(=) Provider error

Confirm M(=) Linked Id

3909

226

3GPP

227 Release 1998

115

3GPP TS 09.02 V7.15.0 (2004-03)

3910 8.4.7.3
3911 Invoke Id

Parameter use

3912 For definition of this parameter see subclause 7.6.1. 3913 Handover Number 3914 For definition of this parameter see subclause 7.6.2. 3915 Linked Id 3916 For definition of this parameter see subclause 7.6.1. This service is linked with 3917 MAP_ALLOCATE_HANDOVER_NUMBER. 3918 Provider error 3919 For definition of this parameter see subclause 7.6.1.

3920 3921 3922 8.5.1.1

8.5 Authentication management services


8.5.1 MAP_AUTHENTICATE service
Definition

3923 This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC 3924 concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to 3925 initiate authentication. 3926 The service is a confirmed service and consists of four service primitives.

3927 8.5.1.2

Service primitives

3928 The service primitives are shown in table 8.5/1 3929


Parameter name Invoke id RAND CKSN SRES Provider error

Table 8.5/1: MAP_AUTHENTICATE parameters


Request M M M Indication M(=) M(=) M(=) Response M(=) M Confirm M(=) M(=) O

3930

3931 8.5.1.3
3932 Invoke id

Parameter use

3933 See subclause 7.6.1 for the use of this parameter. 3934 RAND 3935 See subclause 7.6.7 for the use of this parameter. 3936 CKSN 3937 See subclause 7.6.7 for the use of this parameter. 3938 SRES 3939 See subclause 7.6.7 for the use of this parameter.

228

3GPP

229 Release 1998

116

3GPP TS 09.02 V7.15.0 (2004-03)

3940 Provider error 3941 See subclause 7.6.1 for the use of this parameter.

3942 3943 8.5.2.1

8.5.2 MAP_SEND_AUTHENTICATION_INFO service


Definition

3944 This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. 3945 The VLR requests some sets of RAND/SRES/Kc vectors. 3946 Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information from the 3947 HLR. The SGSN requests some sets of RAND/SRES/Kc vectors. 3948 If the HLR cannot provide the VLR or the SGSN with triplets, an empty response is returned. The VLR or the SGSN 3949 may then re-use old authentication triplets, except where this is forbidden under the conditions specified in GSM 03.20 3950 [24]. 3951 If the VLR or SGSN receives a MAP-Send_AUTHENTICATION_INFO response containing a User Error parameter as 3952 part of the handling of an authentication procedure, the authentication procedure in the VLR or SGSN shall fail. 3953 Security related network functions are further described in GSM 03.20. 3954 The service is a confirmed service and consists of four service primitives.

3955 8.5.2.2

Service primitives

3956 The service primitives are shown in table 8.5/2. 3957

Table 8.5/2: MAP_SEND_AUTHENTICATION_PARAMETERS parameters


Parameter name Invoke id IMSI AuthenticationSetList User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

3958

3959 8.5.2.3
3960 Invoke id

Parameter use

3961 See subclause 7.6.1 for the use of this parameter. 3962 IMSI 3963 See subclause 7.6.2 for the use of this parameter. 3964 AuthenticationSetList 3965 A set of one to five authentication vectors are transferred from the HLR to the VLR or from the HLR to the SGSN, if 3966 the outcome of the service was successful. 3967 User error 3968 One of the following error causes defined in subclause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 3969 the service, depending on the respective failure reason: 3970 3971 3972

unknown subscriber; unexpected data value; system failure;

230

3GPP

231 Release 1998

117

3GPP TS 09.02 V7.15.0 (2004-03)

3973

data missing.

3974 Provider error 3975 See subclause 7.6.1 for the use of this parameter.

3976 3977 3978 8.6.1.1

8.6 Security management services


8.6.1 MAP_SET_CIPHERING_MODE service
Definitions

3979 This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is 3980 called when another service requires that information is to be sent on the radio path in encrypted form. 3981 The service is a non-confirmed service and consists of two service primitives.

3982 8.6.1.2

Service primitives

3983 The service primitives are shown in table 8.6/1 3984

Table 8.6/1: MAP_SET_CIPHERING_MODE parameters


Parameter name Invoke id Ciphering mode Kc Request M M C Indication M(=) M(=) C(=)

3985

3986 8.6.1.3
3987 Invoke id

Parameter use

3988 See subclause 7.6.1 for the use of this parameter. 3989 Ciphering mode 3990 See subclause 7.6.7 for the use of this parameter. 3991 Kc 3992 The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed.

3993 3994 3995 3996 8.7.1.1

8.7 International mobile equipment identities management services


8.7.1 MAP_CHECK_IMEI service
Definition

3997 This service is used between the VLR and the MSC and between the MSC and the EIR and between the SGSN and EIR 3998 to request check of IMEI. If the IMEI is not available in the MSC or in the SGSN, it is requested from the MS and 3999 transferred to the EIR in the service request. 4000 The service is a confirmed service and consists of four service primitives.

232

3GPP

233 Release 1998

118

3GPP TS 09.02 V7.15.0 (2004-03)

4001 8.7.1.2

Service primitives

4002 The service primitives are shown in table 8.7/1. 4003


Parameter name Invoke id IMEI Equipment status User error Provider error

Table 8.7/1: MAP_CHECK_IMEI parameters


Request M C Indication M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O

4004

4005 8.7.1.3
4006 Invoke id

Parameter use

4007 See subclause 7.6.1 for the use of this parameter. 4008 IMEI 4009 4010 4011 4012

See subclause 7.6.2 for the use of this parameter. The parameter shall not be included in the service request between the VLR and the MSC, but is mandatory in the service request from the MSC to the EIR and from the SGSN to the EIR. It is not included in the service response from the EIR to the MSC or to the SGSN, but is mandatory in the service response from the MSC to the VLR on successful outcome.

4013 Equipment status 4014 See subclause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome 4015 of the service. 4016 User error 4017 One of the following error causes defined in subclause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4018 the service, depending on the respective failure reason: 4019 4020 4021 4022

unknown equipment; This error is returned by the responder when the IMEI is not known in the EIR.

system failure; unexpected data value.

4023 Provider error 4024 See subclause 7.6.1 for the use of this parameter.

4025 4026 8.7.2.1

8.7.2 MAP_OBTAIN_IMEI service


Definition

4027 This service is used between the VLR and the MSC to request the IMEI. If the IMEI is not available in the MSC, it is 4028 requested from the MS. 4029 The service is a confirmed service and consists of four service primitives.

4030 8.7.2.2

Service primitives

4031 The service primitives are shown in table 8.7/2.

234

3GPP

235 Release 1998

119

3GPP TS 09.02 V7.15.0 (2004-03)

4032
Parameter name Invoke id IMEI User error Provider error

Table 8.7/2: MAP_OBTAIN_IMEI parameters


Request M Indication M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

4033

4034 8.7.2.3
4035 Invoke id

Parameter use

4036 See subclause 7.6.1 for the use of this parameter. 4037 IMEI 4038 See subclause 7.6.2 for the use of this parameter. The parameter IS included in the service response from the MSC to 4039 the VLR on successful outcome of the service. 4040 User error 4041 If the service fails, the VLR sends the user error System Failure (see subclause 7.6.1) to the MSC. 4042 Provider error 4043 See subclause 7.6.1 for the use of this parameter.

4044 4045 4046 8.8.1.1


-

8.8 Subscriber management services


8.8.1 MAP-INSERT-SUBSCRIBER-DATA service
Definition

4047 This service is used by an HLR to update a VLR with certain subscriber data in the following occasions: 4048 4049 4050 4051 4052 4053 4054 4055

the operator has changed the subscription of one or more supplementary services, basic services or data of a subscriber. Note that in case of withdrawal of a Basic or Supplementary service this primitive shall not be used; the operator has applied, changed or removed Operator Determined Barring; the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; the HLR provides the VLR with subscriber parameters at location updating of a subscriber or at restoration. In this case, this service is used to indicate explicitly that a supplementary service is not provisioned, if the supplementary service specification requires it. The only supplementary services which have this requirement are the CLIR and COLR services. Network access mode is provided only in restoration.

4056 Also this service is used by an HLR to update a SGSN with certain subscriber data in the following occasions: 4057 4058 4059 4060

if the GPRS subscription has changed; if the network access mode is changed; the operator has applied, changed or removed Operator Determined Barring; the HLR provides the SGSN with subscriber parameters at GPRS location updating of a subscriber.

4061 It is a confirmed service and consists of the primitives shown in table 6.8/1.

236

3GPP

237 Release 1998

120

3GPP TS 09.02 V7.15.0 (2004-03)

4062 8.8.1.2
4063

Service primitives
Table 8.8/1: MAP-INSERT-SUBSCRIBER-DATA

Parameter name Invoke Id IMSI MSISDN Category Subscriber Status Bearer service List Teleservice List Forwarding information List Call barring information List CUG information List SS-Data List eMLPP Subscription Data Operator Determined Barring General data Operator Determined Barring HPLMN data Roaming Restriction Due To Unsupported Feature Regional Subscription Data VLR CAMEL Subscription Info Voice Broadcast Data Voice Group Call Data Network access mode GPRS Subscription Data Roaming Restricted In SGSN Due To Unsupported Feature North American Equal Access preferred Carrier Id List LSA Information SS-Code List LMU Identifier LCS Information Regional Subscription Response Supported CAMEL Phases User error Provider error

Request M C C C C C C C C C C C C C C C C C C C C C U C C C

Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

Response M(=)

Confirm M(=)

C C

C(=) C(=)

C(=)

C C(=) C(=) C C U

C(=) C(=) C (=) C(=) O

4064

4065 8.8.1.3

Parameter use

4066 Network access mode 4067 4068 4069 4070

This parameter defines if the subscriber has access to MSC/VLR and/or to SGSN. This parameter is used by SGSN and MSC/VLR. In VLR, the parameter is used only as part of Restore Data Procedure and the parameter is not stored in the VLR. This parameter shall always be sent to the SGSN as part of the subscriber data at GPRS location updating. It shall be sent to the SGSN or VLR as appropriate if it is to be changed as a result of administrative action.

4071 All parameters are described in subclause 7.6. The following clarifications are applicable: 4072 IMSI 4073 It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by 4074 the VLR and the SGSN. 4075 MSISDN 4076 It is included either at location updating or when it is changed. The MSISDN sent shall be the basic MSISDN. This 4077 parameter is used by the VLR and the SGSN. 4078 Category

238

3GPP

239 Release 1998

121

3GPP TS 09.02 V7.15.0 (2004-03)

4079 It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN 4080 receives this parameter it shall ignore it. 4081 Subscriber Status 4082 It is included either at location updating or when it is changed. 4083 4084 4085 4086

To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator Determined Barring. In this case ODB General Data shall also be present. If the Operator Determined Barring applies and the subscriber is registered in the HPLMN and HPLMN specific Operator Determined Barring applies then ODB HPLMN Specific Data shall also be present.

4087 To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This 4088 parameter is used by the VLR and the SGSN. 4089 Bearer service List 4090 A list of Extensible Bearer service parameters (Extensible Bearer service is defined in subclause 7.6). An Extensible 4091 Bearer service parameter must be the code for an individual Bearer service, except in the cases described below. 4092 4093 4094 4095

The codes for the Bearer service groups "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" shall, if applicable, be sent from the HLR to the VLR as a pair. The codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" shall, if applicable, be sent from the HLR to the VLR as a pair.

4096 If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location 4097 updating or at restoration) or only the ones added (at subscriber data modification). 4098 If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not 4099 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no 4100 error is sent back), except in the cases described below. 4101 4102 4103 4104 4105 4106 4107 4108

If the VLR receives the codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" and supports one or more of the circuit-switched synchronous or asynchronous data rates specified for simple data bearer services, it shall accept the bearer service codes, and not return them in the response to the HLR. If the VLR does not support any of the circuit-switched synchronous or asynchronous data rates specified for simple data bearer services, and receives the pair of codes for "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" or the pair of codes for "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS", it shall reject the pair of codes by returning them in the response to the HLR. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.

4109 Teleservice List 4110 A list of Extensible Teleservice parameters (Extensible Teleservice is defined in subclause 7.6). An Extensible 4111 Teleservice parameter must be the code for an individual Teleservice. 4112 If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating 4113 or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant 4114 to the node at which the message is received should be included in the Teleservice List. 4115 If the VLR or the SGSN receives an Indication containing any Extensible Teleservice parameters which it does not 4116 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Teleservices (no 4117 error is sent back). This parameter is used by the VLR and the SGSN. 4118 Forwarding information List 4119 4120 4121 4122

A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in subclause 7.6). It includes Call Forwarding services either at location updating or at restoration or when they are changed. Each Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive.

4123 The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary 4124 service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible 4125 Forwarding Feature is defined in subclause 7.6).

240

3GPP

241 Release 1998

122

3GPP TS 09.02 V7.15.0 (2004-03)

4126 The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according 4127 to the rules in subclause 8.8.1.4. 4128 The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter. 4129 4130 4131 4132 4133 4134

If the Extensible SS-Status indicates that call forwarding is registered then (except for call forwarding unconditional) the Extensible Forwarding Feature shall contain a forwarded-to number and, if available, the forwarded-to subaddress. In other states the forwarded-to number and, if applicable, the forwarded-to subaddress shall not be included. For call forwarding unconditional the forwarded-to number and, if applicable, the forwarded-to subaddress shall not be included. If the VLR does not receive a forwarded-to subaddress then it shall assume that a forwarded-to subaddress has not been registered.

4135 The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding 4136 unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding 4137 options shall be ignored by the VLR, and may be set to any value by the HLR. 4138 For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the 4139 Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply 4140 condition timer shall not be included. 4141 For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not 4142 contain a no reply condition timer. 4143 If the VLR receives an Indication containing any Call Forwarding service codes which it does not support/allocate it 4144 returns them to the HLR in the parameter SS-Code List and discards the unsupported Call Forwarding service codes (no 4145 error is sent back). This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it. 4146 Call barring information List 4147 4148 4149 4150

A list of Extensible Call barring information parameters (Extensible Call barring information is defined in subclause 7.6). It includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible Call barring information parameter shall be treated independently of all other parameters in the primitive.

4151 The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. 4152 The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call 4153 Barring Feature is defined in subclause 7.6). 4154 The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted 4155 according to the rules in subclause 8.8.1.4. 4156 The Extensible Call Barring Feature shall contain an extensible SS-Status parameter. 4157 4158 4159 4160

If the VLR receives an Indication containing any Extensible Call Barring service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Extensible Call Barring service codes (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.

4161 CUG information List 4162 A list of CUG information list parameters (CUG information is defined in subclause 7.6). It includes CUG information 4163 either at location updating or at restoration or when it is changed. 4164 At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete CUG4165 SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If there 4166 are not options per extensible basic service group the CUG-FeatureList shall not be included. 4167 In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty 4168 CUG-SubscriptionList. 4169 When the VLR receives CUG data it shall replace the stored CUG data with the received data set. 4170 If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible 4171 basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no 4172 preferential CUG exists.

242

3GPP

243 Release 1998

123

3GPP TS 09.02 V7.15.0 (2004-03)

4173 If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies. 4174 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4175 Unexpected Data Value. 4176 Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR. 4177 If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards 4178 the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this 4179 parameter it shall ignore it. 4180 SS-Data List 4181 4182 4183 4184

A list of Extensible SS-Data parameters (Extensible SS-Data is defined in subclause 7.6). It is sent for any other supplementary service than Call Forwarding, Call Barring, CUG and eMLPP either at location updating or at restoration or when they are changed. Each SS-Data parameter shall be treated independently of all other parameters in the primitive.

4185 The Extensible SS-Data shall include the SS-Code for an individual supplementary service. 4186 The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are 4187 applicable to the service defined by the SS-Code. 4188 The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in 4189 subclause 8.8.1.4. 4190 4191 4192 4193

If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.

4194 Operator Determined Barring General data 4195 4196 4197 4198 4199 4200 4201 4202

If it is included in a Request/Indication, it includes all the Operator Determined Barring categories that may be applied to a subscriber registered in any PLMN. This parameter is only included in a Request/Indication when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all General Operator Determined Barring Categories shall be set to their actual status. If the VLR or the SGSN receives an Indication containing Operator Determined Barring General Data which shows that the subscriber is subject to barring not supported / not allocated by the VLR or by the SGSN, it returns Operator Determined Barring General Data in the response to the HLR to show the barring categories which are not supported / not allocated by the VLR or by the SGSN. This parameter is used by the VLR and the SGSN.

4203 Operator Determined Barring HPLMN data 4204 4205 4206 4207

It includes all the Operator Determined Barring categories that may be applied only to a subscriber registered in the HPLMN. Therefore, it shall only be transferred to the VLR or to the SGSN when the subscriber is roaming into the HPLMN and when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all HPLMN Operator Determined Barring Categories shall be set to their actual status.

4208 If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data 4209 is present then the VLR or the SGSN shall not apply any HPLMN specific ODB services to the subscriber. This 4210 parameter is used by the VLR and the SGSN. 4211 eMLPP Subscription Data 4212 If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a 4213 call (as defined in subclause 7.6). It contains both subparameters of eMLPP. 4214 If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and 4215 therefore discards the received information (no error is sent back). 4216 4217 4218 4219

eMLPP subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced by the new eMLPP subscription data received in a MAP_INSERT_SUBSCRIBER_DATA during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.

244

3GPP

245 Release 1998

124

3GPP TS 09.02 V7.15.0 (2004-03)

4220 Roaming Restriction Due To Unsupported Feature 4221 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 4222 supported by the MSC/VLR (e.g. Advice of Charge Charging Level). 4223 If this parameter is sent to the VLR the MSC area is restricted by the HLR and the VLR. This parameter is used only by 4224 the VLR and if the SGSN receives this parameter it shall ignore it. 4225 Regional Subscription Data 4226 4227 4228 4229 4230 4231

If included in the Insert Subscriber Data request this parameter defines the subscriber's subscription area for the addressed VLR or for the addressed SGSN (as defined in subclause 7.6). It contains the complete list of up to 10 Zone Codes that apply to a subscriber in the currently visited PLMN. The HLR shall send only those Zone Codes which are stored against the CC and NDC of the VLR or the CC and NDC of the SGSN to be updated. NOTE: Support of this parameter is a network operator option and it will not be sent to networks which do not support Regional Subscription.

4232 Regional subscription data that have been stored previously in a subscriber data record in the VLR or in the SGSN are 4233 completely replaced by the regional subscription data received in an Insert Subscriber Data indication during either an 4234 Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. 4235 After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are 4236 allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional 4237 Subscription Response. 4238 The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has 4239 been detected in one of the following cases: 4240 4241 4242 4243

Too Many Zone Codes: more than 10 Zone Codes are to be stored in the VLR or in the SGSN; Regional Subscription Not Supported by the VLR or the SGSN; Zone Codes Conflict: the VLR or the SGSN detects that the zone codes indicate conflicting service permission for a location area.

4244 Zone codes which have no mapping to location areas shall be ignored. 4245 If a sequence of MAP_INSERT_SUBSCRIBER_DATA services is used during a dialogue, Regional Subscription Data 4246 shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with 4247 the error Unexpected Data Value. 4248 If Regional Subscription Data are not included in any MAP_INSERT_SUBSCRIBER_DATA service, there is no 4249 restriction of roaming due to Regional Subscription. This parameter is used by the VLR and the SGSN. 4250 Voice Broadcast Data 4251 This parameter contains a list of group id's a user might have subscribed to; (VBS-Data is defined in subclause 7.6). It 4252 includes VBS information either at location updating or at restoration or when it is changed. 4253 At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data. 4254 When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All 4255 subsequent VBS-dta received within this dialogue shall be interpreted as add-on data. 4256 If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data. 4257 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4258 Unexpected Data Value. . This parameter is used only by the VLR and if the SGSN receives this parameter it shall 4259 ignore it. 4260 Voice Group Call Data 4261 This parameter contains a list of group id's a user might have subscribed to; see subclause 7.6.

246

3GPP

247 Release 1998

125

3GPP TS 09.02 V7.15.0 (2004-03)

4262 At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete VGCS4263 Data. 4264 When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. 4265 All VGCS-Data received within this dialogue shall be interpreted as add-on data. 4266 If VBCS-Data is omitted in the Insert Subsciber Data operation the VLR shall keep the previously stored VGCS-Data. 4267 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4268 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4269 it. 4270 North American Equal Access preferred Carrier Id List 4271 A list of the preferred carrier identity codes that are subscribed to. 4272 4273 4274 4275

When the VLR receives this parameter from the HLR, it shall replace the previously stored preferred carrier identity codes with the received ones. It is not possible to delete all the preferred carrier identity codes from the VLR using this service. To delete all the preferred carrier identity codes from the VLR, the HLR shall use the MAP_CANCEL_LOCATION service.

4276 LSA Information 4277 4278 4279 4280 4281 4282 4283

If included in the ISD request, this parameter contains a list of localised service area identities a user might have subscribed to together with the priority, the preferential access indicator, the active mode support indicator and active mode indication of each localised service area; see subclause 7.6. The access right outside these localised service areas is also indicated. In all cases mentioned below, the LSA information shall only include LSA Data applicable to the VPLMN where the Subscriber is located. The VLR number, received in the MAP-UPDATE_LOCATION primitive, or the SGSN number, received in the MAP_UPDATE_GPRS_LOCATION primitive, can be used, alongside data stored in the HLR, to determine the LSA Data applicable to the VPLMN.

4284 At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA 4285 Information. 4286 When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data. 4287 When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access 4288 indicator. 4289 4290 4291 4292

When the SGSN or the VLR receives LSA information within a dialogue it shall check if the received data has to be considered as the entire LSA information. If so, it shall replace the stored LSA information with the received data set, otherwise it shall replace the data only for the modified LSA data (if any) and/or access right, and add the new LSA data (if any) to the stored LSA Information.

4293 If the entire LSA information is received, it shall always include the LSA only access indicator value together with the 4294 LSA data applicable for the PLMN (if any). 4295 If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously 4296 stored LSA Information. 4297 If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the 4298 error Unexpected Data Value. This parameter is used by the VLR and the SGSN. 4299 LMU Identifier 4300 This parameter indicates the presence of an LMU This parameter is used only by the VLR and shall be ignored if 4301 received by an SGSN. 4302 LCS Information 4303 This parameter provides the following LCS related information for an MS subscriber:

4304 4305

-list of GMLCs in the HPLMN -privacy exception list

248

3GPP

249 Release 1998

126

3GPP TS 09.02 V7.15.0 (2004-03)

4306

-MO-LR list

4307 At restoration and location updating, the HLR shall include the complete LCS data of the subscriber. 4308 When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS 4309 data that is not modified need not be included. 4310 The VLR shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data operation. 4311 If the VLR detects that there is overlapping in the LCS information received within a dialogue, it shall send the error 4312 Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the SS-Data 4313 List, then the VLR shall not interpret this as overlapping data. 4314 This parameter is used only by the VLR and shall be ignored if received by an SGSN. 4315 SS-Code List 4316 4317 4318 4319 4320

The list of SS-Code parameters for the services that are provided to a subscriber but are not supported/allocated by the VLR (SS-Code is defined in subclause 7.6). The list can only include individual SS-Codes that were sent in the service request and SS-Codes for the eMLPP and/or CUG services if the above mentioned conditions, as described in eMLPP Subscription Data and/or CUG information List, are met (that is, eMLPP Subscription Data and/or CUG information List are received). This parameter is used only by the VLR.

4321 Regional Subscription Response 4322 If included in the response this parameter indicates one of: 4323 4324 4325 4326 4327

MSC Area Restricted entirely because of regional subscription; SGSN Area Restricted entirely because of regional subscription; Too Many Zone Codes to be inserted; Zone Codes Conflict; Regional Subscription not Supported by the VLR or by the SGSN.

4328 If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR 4329 shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted 4330 is not sent. The HLR shall check whether the current MSC area is no longer restricted. 4331 4332 4333 4334

If the SGSN determines after insertion of Regional Subscription Data that the entire SGSN area is restricted, the SGSN shall respond with a Regional Subscription Response indicating SGSN Area Restricted. Otherwise SGSN Area Restricted is not sent. The HLR shall check whether the current SGSN area is no longer restricted. This parameter is used by the VLR and by the SGSN.

4335 VLR CAMEL Subscription Info 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345

This parameter is sent for subscribers who have CAMEL services which are invoked in the MSC. In CAMEL phase 1 this parameter contains only the O-CSI. If an O-CSI is contained, TDP-Criteria may also be present in CAMEL Phase 2. In CAMEL Phase 2 this parameter contains the SS-CSI and/or the O-CSI. The VLR CAMEL Subscription Info is sent at location updating or when any information in the applicable CAMEL Subscription Info in the HLR has been changed. The entire set of CAMEL Subscription Info is sent within one dialogue. If a set of CAMEL Subscription Info is already stored in the VLR, i.e received within a previous dialogue, it is replaced by the received data. If the VLR CAMEL Subscription Info is ommitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VLR CAMEL Subscription Info. Within one dialogue subsequent received data are interpreted as add-on data. If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.

4346 The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag). See GSM 03.72 for the 4347 use of this parameter and the conditions for its presence. 4348 Supported CAMEL Phases 4349 The use of this parameter and the requirements for its presence are specified in GSM 03.78. This parameter is used only 4350 by the VLR.

250

3GPP

251 Release 1998

127

3GPP TS 09.02 V7.15.0 (2004-03)

4351 A VLR not supporting any CAMEL-Phase may omit this parameter. 4352 GPRS Subscription Data 4353 This parameter contains a list of PDP-contexts a user has subscribed to; see subclause 7.6. 4354 At GPRS location updating the HLR shall include the complete GPRS Subscription Data. 4355 When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts. 4356 4357 4358 4359

When the SGSN receives GPRS Subscription Data within a dialogue it shall check if the received data has to be considered as the entire GPRS subscription data. If so, it shall replace the stored GPRS Subscription Data with the received data set, otherwise it shall replace the data only for the modified PDP contexts (if any) and add the new PDP contexts (if any) to the stored GPRS Subscription Data.

4360 If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored 4361 GPRS Subscription Data. 4362 If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error 4363 Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 4364 it. 4365 Roaming Restricted In SGSN Due To Unsupported Feature 4366 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 4367 supported by the SGSN. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 4368 it. 4369 User error 4370 Only one of the following values is applicable: 4371 4372 4373

Unidentified subscriber; Data missing; Unexpected data value.

4374 8.8.1.4
4375 4376 4377 4378

Basic service information related to supplementary services

A number of parameters that relate to supplementary services can be qualified by a Basic Service Group (or a Basic Service Group List). This subclause explains how this information is to be interpreted. Supplementary service parameters to which this subclause is applicable only apply to the basic service groups described in this subclause, and only those basic service groups shall be overwritten at the VLR.

4379 The Basic Service Group (or Basic Service Group List) is optional. 4380 If present the Basic Service Group (or the elements of the Basic Service Group List) shall be one of: 4381 4382 4383 4384 4385 4386 4387 4388

an Elementary Basic Service Group for which the supplementary service is applicable to at least one basic service in the group; and to which the subscriber has a subscription to at least one basic service in the group; the group "All Teleservices" provided that the service is applicable to at least one teleservice and that the subscriber has a subscription to at least one teleservice that is in the same Elementary Basic Service Group as a teleservice to which the service is applicable; the group "All Bearer Services" provided that the service is applicable to at least one bearer service and that the subscriber has a subscription to at least one bearer service that is in the same Elementary Basic Service Group as a basic service to which the service is applicable.

4389 If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic 4390 Service Groups. 4391 If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as 4392 applying individually to all the Elementary Basic Service Groups for which:

252

3GPP

253 Release 1998

128

3GPP TS 09.02 V7.15.0 (2004-03)

4393 4394

the supplementary service is applicable to at least one basic service in the Basic Service Group; and the subscriber has a subscription to at least one basic service in the Basic Service Group.

4395 The VLR is not required to store supplementary services data for Basic Service Groups that are not supported at the 4396 VLR.

4397 4398 8.8.2.1

8.8.2 MAP-DELETE-SUBSCRIBER-DATA service


Definition

4399 This service is used by an HLR to remove certain subscriber data from a VLR if the subscription of one or more 4400 supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or 4401 deactivation of supplementary services. 4402 Also this service is used by an HLR to remove GPRS subscription data from a SGSN. 4403 It is a confirmed service and consists of the primitives shown in table 8.8/2.

4404 8.8.2.2
4405

Service primitives
Table 8.8/2: MAP-DELETE-SUBSCRIBER-DATA
Parameter name Invoke Id IMSI Basic service List SS-Code List Roaming Restriction Due To Unsupported Feature Camel Subscription Info Withdraw Regional Subscription Data VBS Group Indication VGCS Group Indication GPRS Subscription Data Withdraw Roaming Restricted In SGSN Due To Unsupported Feature LSA Information Withdraw Regional Subscription Response GMLC List Withdraw User error Provider error Request M M C C C C C C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C(=) C C(=) O C(=) Response M(=) Confirm M(=)

4406

4407 8.8.2.3

Parameter use

4408 All parameters are described in subclause 7.6. The following clarifications are applicable: 4409 Basic service List 4410 4411 4412 4413

A list of Extensible Basic service parameters (Extensible Basic service is defined in subclause 7.6). It is used when one, several or all basic services are to be withdrawn from the subscriber. If the VLR or the SGSN receives a value for an Extensible Basic Service which it does not support, it shall ignore that value. This parameter is used by the VLR and by the SGSN.

4414 SS-Code List 4415 A list of SS-Code parameters (SS-Code is defined in subclause 7.6). It is used when several or all supplementary 4416 services are to be withdrawn from the subscriber.

254

3GPP

255 Release 1998

129

3GPP TS 09.02 V7.15.0 (2004-03)

4417 There are three possible options: 4418 4419 4420 4421 4422 4423

deletion of basic service(s); The parameter Basic service List is only included.

deletion of supplementary service(s); The parameter SS-Code List is only included.

deletion of basic and supplementary services; Both Basic service List and SS-Code List are included.

4424 This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it. 4425 Roaming Restriction Due To Unsupported Feature 4426 This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This 4427 may occur if unsupported features or services are removed from the subscriber data in the HLR. 4428 If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is 4429 used only by the VLR and if the SGSN receives this parameter it shall ignore it. 4430 CAMEL Subscription Info Withdraw 4431 This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR. All CAMEL 4432 Subscription Info for the subscriber shall be deleted. This parameter is used only by the VLR and if the SGSN receives 4433 this parameter it shall ignore it. 4434 Regional Subscription Identifier 4435 4436 4437 4438 4439

Contains one single Zone Code (as defined subclause 7.6) and is used if all Zone Codes shall be deleted from the subscriber data. When all the Zone Codes are deleted, the VLR or the SGSN shall check for its location areas whether they are allowed or not. If the whole MSC area is restricted, VLR will report it to HLR by returning the Regional Subscription Response "MSC Area Restricted". If the whole SGSN area is restricted, SGSN will report it to HLR by returning the Regional Subscription Response "SGSN Area Restricted".

4440 The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the 4441 VLR or by the SGSN. 4442 Note that support of this parameter is a network operator option and it shall not be sent to networks which do not 4443 support Regional Subscription. 4444 If Regional Subscription is not supported by the VLR or by the SGSN, the request for deletion of Zone Codes is refused 4445 by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR. 4446 If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information 4447 shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR and by 4448 the SGSN. 4449 VBS Group Indication 4450 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice 4451 Broadcast teleservice. 4452 If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request 4453 for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN receives this 4454 parameter it shall ignore it. 4455 VGCS Group Indication 4456 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice 4457 Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4458 it.

256

3GPP

257 Release 1998

130

3GPP TS 09.02 V7.15.0 (2004-03)

4459 If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the 4460 request for deletion of all Group Ids shall be ignored. 4461 GPRS Subscription Data Withdraw 4462 4463 4464 4465

This parameter is used to indicate whether all GPRS Subscription Data for the subscriber shall be deleted or if only a subset of the stored GPRS Subscription Data for the subscriber shall be deleted. In the latter case only those PDP context whose identifiers are included in the subsequent identifier list will be deleted. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it.

4466 Roaming Restricted In SGSN Due To Unsupported Feature 4467 This parameter is used if Roaming Restricted In SGSN Due To Unsupported Feature is deleted from the GPRS 4468 subscriber data. This may occur if unsupported features or services are removed from the GPRS subscriber data in the 4469 HLR. 4470 If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is 4471 used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4472 LSA Information Withdraw 4473 4474 4475 4476

This parameter is used to indicate whether all LSA Information for the subscriber shall be deleted or if only a subset of the stored LSA Information for the subscriber shall be deleted. In the latter case only the LSA data whose LSA identities are included in the subsequent LSA data list will be deleted. This parameter is used by the VLR and the SGSN.

4477 Regional Subscription Response 4478 If included in the Delete Subscriber Data response this parameter indicates one of: 4479 4480 4481

MSC Area Restricted SGSN Area Restricted; Regional Subscription Not Supported.

4482 This parameter is used by the VLR and by the SGSN. 4483 GMLC List Withdraw 4484 This parameter indicates that the subscriber's LCS GMLC List shall be deleted from the VLR. 4485 This parameter is used only by the VLR and shall be ignored if received by an SGSN. 4486 User error 4487 Only one of the following values is applicable: 4488 4489 4490

Unidentified subscriber; Data missing; Unexpected data value.

4491 4492 4493 8.9.1.1

8.9 Identity management services


8.9.1 MAP-PROVIDE-IMSI service
Definition

4494 This service is used by a VLR in order to get, via the MSC, the IMSI of a subscriber (e.g. when a subscriber has 4495 identified itself with a TMSI not allocated to any subscriber in the VLR). 4496 It is a confirmed service and consists of the primitives shown in table 8.9/1.

258

3GPP

259 Release 1998

131

3GPP TS 09.02 V7.15.0 (2004-03)

4497 8.9.1.2
4498

Service primitives
Table 8.9/1: MAP-PROVIDE-IMSI
Parameter name Invoke Id IMSI User error Provider error Request M Indication M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

4499

4500 8.9.1.3
4502 IMSI

Parameter use

4501 All parameters are described in subclause 7.6. The following clarifications are applicable:

4503 This parameter is received when the request is successfully carried out. It contains the requested IMSI. 4504 User error 4505 Only one of the following values is applicable: 4506

Absent subscriber.

4507 4508 8.9.2.1

8.9.2 MAP-FORWARD-NEW-TMSI service


Definition

4509 This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call 4510 set-up, location updating or supplementary services operation). 4511 It is a confirmed service and consists of the primitives shown in table 8.9/2.

4512 8.9.2.2
4513

Service primitives
Table 8.9/2: MAP-FORWARD-NEW-TMSI
Parameter name Invoke Id TMSI Request M M Indication M(=) M(=) O Response M(=) Provider error Confirm M(=)

4514

4515 8.9.2.3

Parameter use

4516 The parameter TMSI is described in subclause 7.6.

4517 4518 4519 8.10.1.1

8.10 Fault recovery services


8.10.1 MAP_RESET service
Definition

4520 This service is used by the HLR, after a restart, to indicate to a list of VLRs or SGSNs that a failure occurred. 4521 The MAP_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1

260

3GPP

261 Release 1998

132

3GPP TS 09.02 V7.15.0 (2004-03)

4522 8.10.1.2
4523

Service primitives
Table 8.10/1: MAP_RESET
Parameter name Invoke Id HLR number HLR Id LIST Request M M U Indication M(=) M(=) C(=)

4524

4525 8.10.1.3
4526 Invoke Id

Parameter definition and use

4527 See definition in subclause 7.6.1. 4528 HLR number 4529 See definition in subclause 7.6.2. 4530 HLR Id LIST 4531 4532 4533 4534

The HLR Id List is a list of HLR Id. If the parameter is present in the indication, the VLR or SGSN may base the retrieval of subscribers to be restored on their IMSI: the subscribers affected by the reset are those whose IMSI leading digits are equal to one of these numbers. If the parameter is absent, subscribers to be restored are those for which the OriginatingEntityNumber received at location updating time matches the equivalent parameter of the Reset Indication.

4535 4536 8.10.2.1


4537 4538 4539 4540 4541

8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service


Definition

This service may be used by an HLR as an implementation option, to indicate to a mobile subscriber that supplementary services parameters may have been altered, e.g. due to a restart. If received from the HLR, the VLR shall forward this indication to the MSC, which in turn forwards it to the MS. The HLR only sends this indication after successful completion of the subscriber data retrieval from HLR to VLR that ran embedded in a MAP_UPDATE_LOCATION procedure.

4542 The MAP_FORWARD_CHECK_SS_INDICATION service is a non-confirmed service using the service primitives 4543 defined in table 8.10/2.

4544 8.10.2.2
4545

Service primitives
Table 8.10/2: MAP_FORWARD_CHECK_SS_INDICATION
Parameter name Invoke Id Request M Indication M(=)

4546

4547 8.10.2.3
4548 Invoke Id

Parameter definition and use

4549 See definition in subclause 7.6.1.

4550 4551 8.10.3.1

8.10.3 MAP_RESTORE_DATA service


Definition

4552 This service is invoked by the VLR on receipt of a MAP_PROVIDE_ROAMING_NUMBER indication for an 4553 unknown IMSI, or for a known IMSI with the indicator "Confirmed by HLR" set to "Not confirmed". The service is

262

3GPP

263 Release 1998

133

3GPP TS 09.02 V7.15.0 (2004-03)

4554 used to update the LMSI in the HLR, if provided, and to request the HLR to send all data to the VLR that are to be 4555 stored in the subscriber's IMSI record. 4556 The MAP_RESTORE_DATA service is a confirmed service using the service primitives defined in table 6.10/3.

4557 8.10.3.2
4558

Service primitives
Table 8.10/3: MAP_RESTORE_DATA
Parameter name Invoke Id IMSI LMSI Supported CAMEL phases SoLSA support indicator HLR number MS Not Reachable Flag User error Provider error Request M M U C C Indication M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C C

C(=) C(=) C(=) O

4559

4560 8.10.3.3
4561 Invoke Id

Parameter definitions and use

4562 See definition in subclause 5.6.1. 4563 IMSI 4564 See definition in subclause 5.6.2. 4565 LMSI 4566 See definition in subclause 5.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the 4567 HLR to support the LMSI handling procedures. 4568 Supported CAMEL Phases 4569 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 4570 phase 1 is supported. Otherwise may be absent. 4571 SoLSA Support Indicator 4572 4573 4574 4575 4576

This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling. This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted.

4577 HLR number 4578 See definition in subclause 5.6.2. The presence of this parameter is mandatory in case of successful outcome of the 4579 service. 4580 MS Not Reachable Flag 4581 See definition in subclause 5.6.8. This parameter shall be present in case of successful outcome of the service, if the 4582 "MS Not Reachable flag" was set in the HLR. 4583 User error 4584 In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes 4585 defined in subclause 5.6.1 may be used, depending on the nature of the fault:

264

3GPP

265 Release 1998

134

3GPP TS 09.02 V7.15.0 (2004-03)

4586 4587 4588 4589

unknown subscriber; system failure; unexpected data value; data missing.

4590 Provider error 4591 For definition of provider errors see subclause 5.6.1.

4592 4593 4594 8.11.1.1

8.11 Subscriber Information services


8.11.1 MAP-ANY-TIME-INTERROGATION service
Definition

4595 This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR at any 4596 time.

4597 8.11.1.2
4598

Service primitives
Table 8.11/1: Any_Time_Interrogation
Parameter name Invoke id Requested Info gsmSCF-Address IMSI MSISDN Location Information Subscriber State User error Provider error Request M M M C C Indication M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C C C

C(=) C(=) C(=) O

4599

4600 8.11.1.3

Parameter definition and use

4601 All parameters are described in subclause 7.6. 4602 The HLR may be able to use the value of the parameter gsmSCF-address to screen an MAP_Any_Time_Interrogation 4603 indication. 4604 The use of the parameters and the requirements for their presence are specified in GSM 03.78. 4605 User error 4606 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4607 4608 4609 4610 4611

System Failure; Any Time Interrogation Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber.

4612 Provider error 4613 These are defined in subclause 7.6.1.

266

3GPP

267 Release 1998

135

3GPP TS 09.02 V7.15.0 (2004-03)

4614 4615 8.11.2.1

8.11.2 MAP-PROVIDE-SUBSCRIBER-Info service


Definition

4616 This service is used to request information (e.g. subscriber state and location) from the VLR at any time.

4617 8.11.2.2
4618

Service primitives
Table 8.11/2: Provide_Subscriber_Information
Parameter name Invoke id Requested Info IMSI LMSI Location Information Subscriber State User error Provider error Request M M M U Indication M(=) M(=) M(=) O Response M(=) Confirm M(=)

C C C

C(=) C(=) C(=) O

4619

4620 8.11.2.3

Parameter definition and use

4621 All parameters are defined in section 7.6. The use of these parameters and the requirements for their presence are 4622 specified in GSM 03.18 4623 User error 4624 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4625 4626

Data Missing; Unexpected Data Value.

4627 Provider error 4628 These are defined in subclause 7.6.1.

4629 4630 4631

9 Operation and maintenance services


9.1 Subscriber tracing services
9.1.1 MAP-ACTIVATE-TRACE-MODE service
Definition

4632 9.1.1.1

4633 This service is used between the HLR and the VLR to activate subscriber tracing in the VLR. 4634 Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN. 4635 The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1.

268

3GPP

269 Release 1998

136

3GPP TS 09.02 V7.15.0 (2004-03)

4636 9.1.1.2
4637

Service primitives
Table 9.1/1: MAP-ACTIVATE-TRACE-MODE
Parameter name Invoke id IMSI Trace reference Trace type OMC Id User error Provider error Request M C M M U Indication M(=) C(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

C(=) O

4638

4639 9.1.1.3
4640 Invoke id

Parameter use

4641 See definition in subclause 7.6.1. 4642 IMSI 4643 See definition in subclause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 4644 Trace reference 4645 See definition in subclause 7.6.10. 4646 Trace type 4647 See definition in subclause 7.6.10. 4648 OMC Id 4649 See definition in subclause 7.6.2. The use of this parameter is an operator option. 4650 User error 4651 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 4652 4653 4654 4655 4656 4657

Unidentified Subscriber; Facility Not Supported; Tracing Buffer Full; System Failure; Unexpected Data Value; Data missing.

4658 Provider error 4659 For definition of provider errors see subclause 7.6.1.

4660 4661 9.1.2.1

9.1.2 MAP-DEACTIVATE-TRACE-MODE service


Definition

4662 This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR. 4663 Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN. 4664 The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2.

270

3GPP

271 Release 1998

137

3GPP TS 09.02 V7.15.0 (2004-03)

4665 9.1.2.2
4666

Service primitives
Table 9.1/2: MAP-DEACTIVATE-TRACE-MODE
Parameter name Invoke id IMSI Trace reference User error Provider error Request M C M Indication M(=) C(=) M(=) Response M(=) C Confirm M(=) C(=) O

4667

4668 9.1.2.3
4669 Invoke id

Parameter use

4670 See definition in subclause 7.6.1. 4671 IMSI 4672 See definition in subclause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 4673 Trace reference 4674 See definition in subclause 7.6.10. 4675 User error 4676 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 4677 4678 4679 4680 4681

Unidentified Subscriber; Facility Not Supported; System Failure; Unexpected Data Value; Data missing.

4682 Provider error 4683 For definition of provider errors see subclause 7.6.1.

4684 4685 9.1.3.1

9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service


Definition

4686 This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC. 4687 The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3.

4688 9.1.3.2
4689

Service primitives
Table 9.1/3: MAP-TRACE-SUBSCRIBER-ACTIVITY
Parameter name Invoke id IMSI Trace reference Trace type OMC Id Request M C M M U Indication M(=) C(=) M(=) M(=) C(=)

4690

272

3GPP

273 Release 1998

138

3GPP TS 09.02 V7.15.0 (2004-03)

4691 9.1.3.3
4692 Invoke id

Parameter use

4693 See definition in subclause 7.6.1. 4694 IMSI 4695 See definition in subclause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC. 4696 Trace reference 4697 See definition in subclause 7.6.10. 4698 Trace type 4699 See definition in subclause 7.6.10. 4700 OMC Id 4701 See definition in subclause 7.6.2. The use of this parameter is an operator option.

4702 4703 4704 9.2.1.1

9.2 Other operation and maintenance services


9.2.1 MAP-SEND-IMSI service
Definition

4705 This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance 4706 procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber's identity known. 4707 It is a confirmed service and consists of the primitive shown in figure 9.2/1.

4708 9.2.1.2
4709

Service primitives
Table 9.2/1: MAP-SEND-IMSI
Parameter name Invoke Id MSISDN IMSI User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

4710

4711 9.2.1.3
4713 User error

Parameter use

4712 All parameters are described in subclause 7.6. The following clarifications are applicable:

4714 Only one of the following values is applicable: 4715 4716 4717

Unknown subscriber; Unexpected data value; Data missing.

274

3GPP

275 Release 1998

139

3GPP TS 09.02 V7.15.0 (2004-03)

4718 4719 4720

10

Call handling services


10.1 MAP_SEND_ROUTING_INFORMATION service
10.1.1 Definition

4721 This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform 4722 the interrogation of the HLR in order to route a call towards the called MS. 4723 This is a confirmed service using the primitives listed in table 10.1/1. 4724 This service is also used between the GMSC and the NPLR.

4725
4726

10.1.2 Service primitives


Table 10.1/1: MAP_SEND_ROUTING_INFORMATION parameters
Parameter name Invoke Id Interrogation Type GMSC Address MSISDN OR Interrogation OR Capability CUG Interlock CUG Outgoing Access Number of Forwarding Network Signal Info Supported CAMEL Phases Suppress T-CSI Suppression of Announcement Call Reference Number Forwarding Reason Basic Service Group Alerting Pattern CCBS Call Supported CCBS Phase Additional Signal Info IMSI MSRN Forwarding Data Forwarding Interrogation Required VMSC address GMSC Camel Subscription Info Location Information Subscriber State Basic Service Code CUG Subscription Flag North American Equal Access preferred Carrier Id User error SS-List CCBS Target Keep CCBS Call Indicator Number Portability Status Provider error Request M M M M C C C C C C C C C C C C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=)

C C C C C C C C C C U C U C C U

C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O

4727

276

3GPP

277 Release 1998

140

3GPP TS 09.02 V7.15.0 (2004-03)

4728

10.1.3 Parameter use


a conditional parameter whose use is defined only in GSM 03.78 shall be absent if the sending entity does not support CAMEL; a conditional parameter whose use is defined only in GSM 03.79 shall be absent if the sending entity does not support optimal routeing; a conditional parameter whose use is defined only in GSM 03.78 & GSM 03.79 shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

4729 See subclause 7.6 for a definition of the parameters used in addition to the following. Note that: 4730 4731 4732 4733 4734 4735

4736 Interrogation Type 4737 See GSM 03.79 [99] for the use of this parameter. 4738 GMSC address 4739 The E.164 address of the GMSC. 4740 MSISDN 4741 This is the Mobile Subscriber ISDN number assigned to the called subscriber. In the Request & Indication it is the 4742 number received by the GMSC in the IAM. If the call is to be forwarded and the HLR supports determination of the 4743 redirecting number, the HLR inserts the basic MSISDN in the Response. 4744 See GSM 03.66 [108] for the use of this parameter and the conditions for its presence in the response. 4745 OR Interrogation 4746 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4747 OR Capability 4748 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4749 CUG Interlock 4750 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4751 CUG Outgoing Access 4752 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4753 Number of Forwarding 4754 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4755 Network Signal Info 4756 See GSM 03.18 [97] for the conditions for the presence of the components of this parameter. 4757 Supported CAMEL Phases 4758 The use of this parameter and the requirements for its presence are specified in GSM 03.78 4759 T-CSI Suppression 4760 The use of this parameter and the requirements for its presence are specified in GSM 03.78 4761 Suppression Of Announcement 4762 The use of this parameter and the requirements for its presence are specified in GSM 03.78 4763 Call Reference Number 4764 The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98] and GSM 03.79 [99].

278

3GPP

279 Release 1998

141

3GPP TS 09.02 V7.15.0 (2004-03)

4765 Forwarding Reason 4766 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4767 Basic Service Group 4768 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4769 Alerting Pattern 4770 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4771 CCBS Call 4772 See GSM 03.93 [107] for the use of this parameter and the conditions for its presence. 4773 Supported CCBS Phase 4774 This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported. 4775 Additional Signal Info 4776 See GSM 03.81 [27] for the conditions for the presence of the components of this parameter. 4777 IMSI 4778 See GSM 03.18 [97] and GSM 03.66 [108] for the use of this parameter and the conditions for its presence. 4779 MSRN 4780 See GSM 03.18 [97], GSM 03.66 [108] and GSM 03.79 [99] for the use of this parameter and the conditions for its 4781 presence. If the NPLR returns only the MSISDN-number without Routeing Number to the GMSC, the MSISDN4782 number shall be returned as MSRN. 4783 Forwarding Data 4784 This parameter includes the forwarded-to number, the forwarding reason and the forwarding options Notification to 4785 calling party and Redirecting presentation , and can include the forwarded-to subaddress. See GSM 03.18 [97] and 4786 GSM 03.79 [99] for the conditions for the presence of its components. 4787 Forwarding Interrogation Required 4788 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4789 VMSC address 4790 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4791 GMSC CAMEL Subscription Info 4792 The use of this parameter and the requirements for its presence are specified in GSM 03.78 4793 Location Information 4794 The use of this parameter and the requirements for its presence are specified in GSM 03.78 4795 Subscriber State 4796 The use of this parameter and the requirements for its presence are specified in GSM 03.78 4797 CUG Subscription Flag 4798 The use of this parameter and the requirements for its presence are specified in GSM 03.78. 4799 North American Equal Access preferred Carrier Id 4800 This parameter is returned to indicate the preferred carrier identity to be used to setup the call (i.e. forwarding the call or 4801 establishing the roaming leg).

280

3GPP

281 Release 1998

142

3GPP TS 09.02 V7.15.0 (2004-03)

4802 SS-List 4803 4804 4805 4806

This parameter includes SS-codes and will be returned as an operator option. The HLR shall not send PLMN-specific SS-codes across PLMN boundaries. However if the GMSC receives PLMN-specific SS-codes from a foreign PLMN's HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN specific SS codes, this may lead to unpredictable behaviour but the GMSC shall continue call processing.

4807 Basic Service Code 4808 The use of this parameter and the requirements for its presence are specified in GSM 03.78. 4809 4810 4811 4812 4813

If the CAMEL service is not involved, this parameter includes the basic service code and will be returned as an operator option. The HLR shall not send a PLMN-specific Basic Service Code across PLMN boundaries. However if the GMSC receives a PLMN-specific Basic Service Code from a foreign PLMN's HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN specific Basic Service codes, this may lead to unpredictable behaviour but the GMSC shall continue call processing.

4814 CCBS Target 4815 See GSM 03.93 for the use of this parameter and the conditions for its presence. 4816 Keep CCBS Call Indicator 4817 See GSM 03.93 for the use of this parameter and the conditions for its presence. 4818 Number Portability Status 4819 4820

This parameter indicates the number portability status of the subscriber. This parameter may be present if the sender of SRIack is NPLR.

4821 User error 4822 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840

Unknown Subscriber; Number changed; Call Barred; This error will indicate that either incoming calls are barred for this MS or that calls are barred due to Operator Determined Barring (see GSM 02.41 for a definition of this network feature).

CUG Reject; The value of this error cause will indicate the reason for CUG Reject.

Bearer Service Not Provisioned; Teleservice Not Provisioned; A subscription check has been performed and the call has not passed the check due to incompatibility with regard to the requested service. Depending on the nature of the incompatibility, either of these messages will be returned.

Facility Not Supported; Absent Subscriber; This indicates that the location of the MS is not known (either the station is not registered and there is no location information available or the Provide Roaming Number procedure fails due to IMSI detached flag being set), or the GMSC requested forwarding information with a forwarding reason of not reachable, and the call forwarding on MS not reachable service is not active.

282

3GPP

283 Release 1998

143

3GPP TS 09.02 V7.15.0 (2004-03)

4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855

Busy Subscriber; This indicates that Call Forwarding on Busy was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of busy. The error may also indicate that the subscriber is busy due to an outstanding CCBS recall. In the error data it may then be specified that CCBS is possible for the busy encountered call.

No Subscriber Reply; This indicates that Call Forwarding on No Reply was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of no reply.

OR Not Allowed; This indicates that the HLR is not prepared to accept an OR interrogation from the GMSC, or that calls to the specified subscriber are not allowed to be optimally routed.

Forwarding Violation; System Failure; Data Missing; Unexpected Data Value.

4856 See subclause 7.6 for a definition of these errors. 4857 Provider error 4858 These are defined in subclause 7.6.

4859 4860

10.2 MAP_PROVIDE_ROAMING_NUMBER service


10.2.1 Definition

4861 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a 4862 roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. 4863 This is a confirmed service which uses the Primitives described in table 10.2/1.

284

3GPP

285 Release 1998

144

3GPP TS 09.02 V7.15.0 (2004-03)

4864
4865

10.2.2 Service primitives


Table 10.2/1: MAP_PROVIDE_ROAMING_NUMBER parameters
Parameter name Invoke Id IMSI MSC Number MSISDN LMSI GSM Bearer Capability Network Signal Info Suppression Of Announcement Call Reference Number GMSC Address OR Interrogation OR Not Supported in GMSC Alerting Pattern CCBS Call Supported CAMEL Phases in GMSC Additional Signal Info Roaming Number User error Provider error Request M M M U C C C C C C C C C C C C Indication M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C C(=) C(=) O Response M(=) Confirm M(=)

4866

4867

10.2.3 Parameter use


a conditional parameter whose use is defined only in GSM 03.78 shall be absent if the sending entity does not support CAMEL; a conditional parameter whose use is defined only in GSM 03.79 shall be absent if the sending entity does not support optimal routeing; a conditional parameter whose use is defined only in GSM 03.78 & GSM 03.79 shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

4868 See subclause 7.6 for a definition of the parameters used, in addition to the following. Note that: 4869 4870 4871 4872 4873 4874

4875 IMSI 4876 This is the IMSI of the called Subscriber. 4877 MSC Number 4878 This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the 4879 HLR as provided at location updating. 4880 MSISDN 4881 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4882 LMSI 4883 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4884 GSM Bearer Capability 4885 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4886 This information is passed according to the rules specified in TS GSM 09.07. 4887 There may be two GSM Bearer Capabilities supplied.

286

3GPP

287 Release 1998

145

3GPP TS 09.02 V7.15.0 (2004-03)

4888 Network Signal Info 4889 See GSM 03.18 [97] for the conditions for the presence of the components of this parameter. 4890 Suppression Of Announcement 4891 The use of this parameter and the requirements for its presence are specified in GSM 03.78. 4892 Call Reference Number 4893 The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98] and GSM 03.79 [99]. 4894 GMSC Address 4895 The use of this parameter and the conditions for its presence are specified in GSM 03.78 [98] and GSM 03.79 [99]. 4896 OR Interrogation 4897 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4898 Supported CAMEL Phases in GMSC 4899 See GSM 03.78 [98] for the use of this parameter and the conditions for its presence. 4900 OR Not Supported in GMSC 4901 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4902 Alerting Pattern 4903 See GSM 03.78 [98] for the use of this parameter and the conditions for its presence. 4904 CCBS Call 4905 See GSM 03.93 [xx] for the use of this parameter and the conditions for its presence. 4906 Additional Signal Info 4907 See GSM 03.81 [xx] for the conditions for the presence of the components of this parameter. 4908 Roaming Number 4909 See GSM 03.18 [97] for the use of this parameter and the conditions for its presence. 4910 User error 4911 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921

Absent Subscriber; This error will be returned if the IMSI detach flag is set.

No Roaming Number Available; OR Not Allowed; This indicates that the MAP_PROVIDE_ROAMING_NUMBER indication included the OR interrogation indicator, but the VLR does not support optimal routeing.

Facility Not Supported; System Failure; Data Missing; Unexpected Data Value.

4922 See subclause 7.6 for a definition of these reasons.

288

3GPP

289 Release 1998

146

3GPP TS 09.02 V7.15.0 (2004-03)

4923 Provider error 4924 These are defined in subclause 7.6.

4925 4926

10.3 MAP_RESUME_CALL_HANDLING service


10.3.1 Definition

4927 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC 4928 to request the GMSC to resume handling the call and forward it to the specified destination. 4929 This is a confirmed service which uses the Primitives listed in table 10.3/1.

4930
4931

10.3.2 Service primitives


Table 10.3/1: MAP_RESUME_CALL_HANDLING parameters
Parameter name Invoke Id Call Reference Number Basic Service Group IMSI Forwarding Data CUG Interlock CUG Outgoing Access O-CSI CCBS Target UU Data UUS CF Interaction All Information Sent MSISDN User error Provider error Request M C C C C C C C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=) O

4932

4933

10.3.3 Parameter use

4934 Information received in subsequent segment of a segmented dialogue shall not overwrite information received in an 4935 earlier segment. 4936 See subclause 7.6 for a definition of the parameters used, in addition to the following. 4937 Call Reference Number 4938 See GSM 03.79 [99] for the use of this parameter. This parameter shall be present in a first segment of the dialogue. 4939 Basic Service Group 4940 See GSM 03.79 [99] for the use of this parameter. This parameter shall be present in a first segment of the dialogue. 4941 IMSI 4942 This is the IMSI of the forwarding Subscriber. This parameter shall be present in a first segment of the dialogue. 4943 Forwarding Data 4944 This parameter includes the forwarded-to number, the forwarding reason and the forwarding options Notification to 4945 calling party and Redirecting presentation, and can include the forwarded-to subaddress. See GSM 03.79 [99] for the 4946 conditions for the presence of its components. This parameter shall be present in a first segment of the dialogue.

290

3GPP

291 Release 1998

147

3GPP TS 09.02 V7.15.0 (2004-03)

4947 CUG Interlock 4948 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4949 CUG Outgoing Access 4950 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4951 O-CSI 4952 See GSM 03.79 [99] for the use of this parameter and the conditions for its presence. 4953 For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data. 4954 CCBS Target 4955 See GSM 03.93 [107] for the use of this parameter and the conditions for its presence. 4956 UU Data 4957 See GSM 03.87 for the use of this parameter and the conditions for its presence. 4958 UUS CF Interaction 4959 See GSM 03.87 for the use of this parameter and the conditions for its presence. 4960 All Information Sent 4961 This parameter is set when the VMSC has sent all information to GMSC. 4962 MSISDN 4963 This parameter is the basic MSISDN of the forwarding subscriber. It shall be present if the VMSC supports 4964 determination of the redirecting number. 4965 User error 4966 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4967 4968 4969 4970

Optimal Routeing not allowed; Forwarding failed; Unexpected Data Value; Data Missing.

4971 Provider error 4972 These are defined in subclause 7.6.

4973 4974

10.4 MAP_PREPARE_GROUP_CALL service


10.4.1 Definition

4975 This service is used by the Anchor_MSC to inform the Relay_MSC about a group call setup. 4976 The MAP_PREPARE_GROUP_CALL service is a confirmed service using the service primitives given in table 10.4

292

3GPP

293 Release 1998

148

3GPP TS 09.02 V7.15.0 (2004-03)

4977
4978

10.4.2 Service primitives


Table 10.4/1: MAP_PREPARE_GROUP_CALL service
Parameter name Invoke Id Teleservice ASCI Call Reference Ciphering Algorithm Group Key Number Group Key Priority CODEC-Information Uplink Free Indicator Group Call Number User Error Provider Error Request M M M M C C C M M Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) M(=) M(=) Response M(=) Confirm M(=)

M C

M(=) C(=) O

4979

4980
4981 Invoke Id

10.4.3 Parameter definitions and use

4982 See definition in section 7.6.1 4983 Teleservice 4984 Voice Broadcast Service or Voice Group Call Service. 4985 ASCI Call Reference 4986 Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the 4987 Relay_MSC. 4988 Ciphering Algorithm 4989 The ciphering algorithm to be used for the group call. 4990 Group Key Number 4991 This number has to be broadcasted and is used by the mobile station to select the chosen group key. 4992 Shall be present if the ciphering applies. 4993 Group Key 4994 This key is used for ciphering on the radio interface. 4995 Shall be present if the ciphering applies. 4996 Priority 4997 Default priority level related to the call if eMLPP applies. 4998 CODEC-Information 4999 Information on the codecs allowed for this call. 5000 Uplink Free Indicator 5001 A flag indicating whether the call is initiated from a dispatcher. 5002 Group Call Number 5003 This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC. 5004 User Error

294

3GPP

295 Release 1998

149

3GPP TS 09.02 V7.15.0 (2004-03)

5005 For definition of this parameter see section 7.6.1 The following errors defined in section 7.6.1 may be used, depending 5006 on the nature of the fault: 5007 5008 5009

No Group Call Number available; System Failure; Unexpected Data Value.

5010 Provider Error 5011 See definition of provider error in section 7.6.1.

5012 5013 5014

10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service


10.5.1 Definitions

5015 This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications. 5016 The MAP_PROCESS_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives 5017 given in table 10.5

5018
5019

10.5.2 Service primitives


Table 10.5/1: MAP_PROCESS_GROUP_CALL_SIGNALLING service
Parameter name Invoke Id Uplink Request Uplink Release Indication Release Group Call Request M C C C Indication M(=) C(=) C(=) C(=)

5020

5021
5022 Invoke Id

10.5.3 Parameter definitions and use

5023 See definition in section 7.6.1 5024 Uplink Request 5025 This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests 5026 access to the uplink. 5027 Uplink Release Indication 5028 This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free. 5029 Release Group Call 5030 This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who 5031 has initiated the call and who currently has access to the uplink terminates the call.

296

3GPP

297 Release 1998

150

3GPP TS 09.02 V7.15.0 (2004-03)

5032 5033 5034

10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service


10.6.1 Definitions

5035 This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications. 5036 The MAP_FORWARD_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service 5037 primitives given in table 10.6

5038
5039

10.6.2 Service primitives


Table 10.6: MAP_FORWARD_GROUP_CALL_SIGNALLING service
Parameter name Invoke Id IMSI Uplink Request Acknowledgement Uplink Release Indication Uplink Reject Command Uplink Seized Command Uplink Release Command Request M C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=)

5040

5041
5042 IMSI

10.6.3 Parameter definitions and use

5043 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 5044 Invoke Id 5045 See definition in section 7.6.1 5046 Uplink Request Acknowledgement 5047 This information element is used for positive acknowledgement of an uplink request 5048 Uplink Release Indication 5049 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free. 5050 Uplink Reject Command 5051 This information element is used for negative acknowledgement of an uplink request 5052 Uplink Seized Command 5053 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free. 5054 Uplink Release Command 5055 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted 5056 to a MS in the relay MSC area shall be released.

298

3GPP

299 Release 1998

151

3GPP TS 09.02 V7.15.0 (2004-03)

5057 5058

10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service


10.7.1 Definitions

5059 This service is used between the Relay MSC and the Anchor MSC indicating that VGCS / VBS channels have been 5060 established in the Relay MSC area. The response is used by the Anchor MSC to inform Relay MSC that all resources 5061 for the call can be released in Relay MSC because the call has been released in the Anchor MSC. 5062 The MAP_SEND_GROUP_CALL_END_SIGNAL service is a confirmed service using the service primitives given in 5063 table 10.7

5064
5065

10.7.2 Service primitives


Table 10.7: MAP_SEND_GROUP_CALL_END_SIGNAL service
Parameter name Invoke Id IMSI Provider Error Request M C Indication M(=) C(=) Response M(=) Confirm M(=) O

5066

5067
5068 IMSI

10.7.3 Parameter definitions and use

5069 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 5070 Shall be present if the call was established by a service subscriber roaming in the relay MSC area. 5071 Invoke Id 5072 See definition in section 7.6.1 5073 Provider Error 5074 See definition of provider error in section 7.6.1.

5075 5076

10.8 MAP_Provide_SIWFS_Number
10.8.1 Definition

5077 This service is used between an MSC and SIWFS. It is invoked by an MSC receiving an incoming call (call to or from 5078 MS) to request the SIWFS to allocate IWU resources. The service is defined in GSM 03.54. 5079 This is a confirmed service using the primitives described in table 10.8.

300

3GPP

301 Release 1998

152

3GPP TS 09.02 V7.15.0 (2004-03)

5080
5081

10.8.2 Service primitive


Table 10.8: MAP_Provide_SIWFS_Number service
Parameter name Invoke ID GSM Bearer Capability ISDN Bearer Capability Call Direction B-subscriber address Chosen Channel Lower Layer Compatibility High Layer Compatibility SIWFS number User error Provider error Request M M M M M M C C Indication M(=) M(=) M(=) M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

5082

5083

10.8.3 Parameter use

5084 See subclause 7.6 for a definition of the parameter used, in addition to the following. 5085 GSM Bearer Capability 5086 This information is the result from the negotiation with the mobile station. The information is sent from the MSC to the 5087 SIWFS to allocate the correct IWU. 5088 ISDN Bearer Capability 5089 This parameter refers to the ISDN Bearer Capability information element. For the MTC this parameter is received in the 5090 ISUP User Service Information parameter. For the MOC call this parameter is mapped from the GSM BC parameter 5091 according to GSM 09.07. The parameter is used by the SIWFS to route the call and to allocate the outgoing circuit. 5092 Call Direction 5093 This parameter indicates the direction of the call (mobile originated or mobile terminated) at call set-up. 5094 B-subscriber address 5095 5096 5097 5098

This parameter is sent from the MSC to the SIWFS to inform the SIWFS where to route the call i.e. where to send the IAM. If the loop method is used this parameter will indicate the address to the VMSC. This address is allocated by the VMSC in the same way as a MSRN and is used to correlate the incoming IAM to the corresponding MAP dialogue. If the non-loop method is used this parameter will indicate the address to the B-subscriber.

5099 Chosen Channel 5100 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 5101 parameter is defined in GSM 08.08. 5102 Lower Layer Compatibility 5103 This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This 5104 parameter is handled as specified in GSM 09.07. This parameter is defined in GSM 04.08. 5105 High Layer Compatibility 5106 This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This 5107 parameter is handled as specified in GSM 09.07. This parameter is defined in GSM 04.08. 5108 SIWFS number 5109 5110 5111 5112

This parameter is sent from the SIWFS to the MSC. This address is used by the visited MSC to route the call, i.e. the IAM to the SIWFS (similar to MSRN) and will be used by the SIWFS to correlate the incoming IAM to the corresponding MAP message. This parameter must always be sent from the SIWFS when a successful allocation of SIWFS resources has been made.

302

3GPP

303 Release 1998

153

3GPP TS 09.02 V7.15.0 (2004-03)

5113 User error 5114 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5115 5116 5117 5118

Resource limitation; Facility Not Supported; Unexpected Data Value; System Failure.

5119 See subclause 7.6 for a definition of these reasons. 5120 Provider error 5121 These are defined in subclause 7.6.

5122 5123

10.9 MAP_SIWFS_Signalling_Modify
10.9.1 Definition

5124 This service is used to transport signalling information between an MSC and an SIWFS in the case of a request to 5125 modify the configuration (e.g. HSCSD). It is invoked either by an MSC or by the SIWFS. The service is defined in 5126 GSM 03.54. 5127 This is a confirmed service using the primitives described in table 10.9.

5128
5129

10.9.2 Service primitive


Table 10.9: MAP_SIWFS_Signalling_Modify service
Parameter name Invoke ID Channel Type Chosen Channel User error Provider error Request M C C Indication M(=) C(=) C(=) Response M(=) C(=) C Confirm M(=) C(=) C(=) O

5130

5131

10.9.3 Parameter use

5132 See subclause 7.6 for a definition of the parameter used, in addition to the following. 5133 Channel Type 5134 This parameter is the result of a Channel Mode Modification for TS61/62. It contains the changed Air Interface User 5135 Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is 5136 defined in GSM 08.08. 5137 Chosen Channel 5138 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 5139 parameter is defined in GSM 08.08. 5140 User error 5141 This parameter is sent by the responder when an error is detected and if present , takes one of the following values: 5142 5143

Resource limitation; Facility Not Supported;

304

3GPP

305 Release 1998

154

3GPP TS 09.02 V7.15.0 (2004-03)

5144 5145 5146

Data Missing; Unexpected Data Value; System Failure.

5147 See subclause 7.6 for a definition of these reasons. 5148 Provider error 5149 These are defined in subclause 7.6.

5150 5151

10.10 MAP_SET_REPORTING_STATE service


10.10.1 Definition

5152 This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed 5153 service using the service primitives shown in table 10.10/1.

5154

10.10.2 Service primitives


Table 10.10/1: MAP_SET_REPORTING_STATE parameters
Parameter name Invoke id IMSI LMSI CCBS Monitoring CCBS Subscriber Status User error Provider error Request M C C C Indication M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

5155 The service primitives are shown in table 10.10/1. 5156

C C

C(=) C(=) O

5157

5158

10.10.3 Parameter use

5159 See subclause 7.6 for a definition of the parameters used, in addition to the following. 5160 IMSI 5161 The IMSI is a mandatory parameter if the service is used as the only one in a dialogue. 5162 CCBS Monitoring 5163 This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall 5164 be started this service corresponds to the message 'Start Reporting' in GSM 03.93; if it indicates that monitoring shall be 5165 stopped this service corresponds to the message 'Stop Reporting' in GSM 03.93. 5166 CCBS Subscriber Status 5167 See GSM 03.93 for the use of this parameter and the conditions for its presence. 5168 User error 5169 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5170 values defined in subclause 7.6.1: 5171 5172

System Failure; Unidentified Subscriber;

306

3GPP

307 Release 1998

155

3GPP TS 09.02 V7.15.0 (2004-03)

5173 5174 5175 5176 5177

Unexpected Data Value; Data Missing; Resource Limitation; Facility Not Supported. This error is reserved for future use.

NOTE:

5178 Provider error 5179 These are defined in subclause 7.6.

5180 5181

10.11 MAP_STATUS_REPORT service


10.11.1 Definition

5182 This service is used by the VLR to report an event or call outcome to the HLR.It is a confirmed service using the 5183 service primitives shown in table 10.11/1.

5184

10.11.2 Service primitives


Table 10.11/1: MAP_STATUS_REPORT parameters
Parameter name Invoke id IMSI CCBS Subscriber Status Monitoring Mode Call Outcome User error Provider error Request M M C C C Indication M(=) M(=) C(=) C(=) C(=) C C(=) O Response M(=) Confirm M(=)

5185 The service primitives are shown in table 10.11/1. 5186

5187

5188

10.11.3 Parameter use

5189 See subclause 7.6 for a definition of the parameters used, in addition to the following. 5190 CCBS Subscriber Status 5191 If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message 'Event 5192 Report' in GSM 03.93 [107]. See GSM 03.93 [107] for the use of this parameter and the conditions for its presence. 5193 Monitoring Mode 5194 If this parameter is present with CCBS Call Outcome this service corresponds to the message 'CCBS Call Report' in 5195 GSM 03.93. See GSM 03.93 for the use of this parameter and the conditions for its presence. 5196 Call Outcome 5197 See GSM 03.93 for the use of this parameter and the conditions for its presence. 5198 User error 5199 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5200 values defined in subclause 7.6.1: 5201

Unknown Subscriber ;

308

3GPP

309 Release 1998

156

3GPP TS 09.02 V7.15.0 (2004-03)

5202 5203 5204

System Failure; Unexpected Data Value; Data Missing.

5205 Provider error 5206 These are defined in subclause 7.6.

5207 5208

10.12 MAP_REMOTE_USER_FREE service


10.12.1 Definition

5209 This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber 5210 can be notified. It is a confirmed service using the service primitives shown in table 10.12/1.

5211

10.12.2 Service primitives


Table 10.12/1: MAP_REMOTE_USER_FREE parameters
Parameter name Invoke id IMSI Call Info CCBS Feature Translated B Number Replace B Number Alerting Pattern RUF Outcome User error Provider error Request M M M M M C C Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

5212 The service primitives are shown in table 10.12/1. 5213

C C

C(=) C(=) O

5214

5215

10.12.3 Parameter use

5216 See subclause 7.6 for a definition of the parameters used, in addition to the following. 5217 Call Info 5218 See GSM 03.93 for the use of this parameter. 5219 CCBS Feature 5220 See GSM 03.93 for the conditions for the presence of the parameters included in the CCBS feature. 5221 Translated B Number 5222 See GSM 03.93 for the use of this parameter. 5223 Replace B Number 5224 See GSM 03.93 for the use of this parameter and the conditions for its presence. 5225 Alerting Pattern 5226 See GSM 03.93 for the use of this parameter and the conditions for its presence. 5227 RUF Outcome 5228 See GSM 03.93 for the use of this parameter and the conditions for its presence.

310

3GPP

311 Release 1998

157

3GPP TS 09.02 V7.15.0 (2004-03)

5229 User error 5230 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5231 values defined in subclause 7.6.1: 5232 5233 5234 5235 5236 5237 5238 5239

Unexpected Data Value; Data Missing; Incompatible Terminal; This error is returned by the responder when the terminal used for CCBS activation is not compatible with the terminal used for the CCBS recall. For details refer to GSM 04.08.

Absent Subscriber (IMSI Detach; Restricted Area; No Page Response); System Failure; Busy Subscriber (CCBS Busy).

5240 Provider error 5241 These are defined in subclause 7.6.

5242 5243 5244

11

Supplementary services related services


11.1 MAP_REGISTER_SS service
11.1.1 Definition

5245 This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a 5246 supplementary service. The VLR will relay the message to the HLR. 5247 The service is a confirmed service and consists of four service primitives.

5248

11.1.2 Service primitives


Table 11.1/1: MAP_REGISTER_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarded-to number with subaddress No reply condition time EMLPP default priority Forwarding information User error Provider error Request M M C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C C C C(=) C(=) C(=) O Response M(=) Confirm M(=)

5249 The service primitives are shown in table 11.1/1. 5250

5251

312

3GPP

313 Release 1998

158

3GPP TS 09.02 V7.15.0 (2004-03)

5252
5253 Invoke id

11.1.3 Parameter use

5254 See subclause 7.6.1 for the use of this parameter. 5255 SS-Code 5256 This parameter indicates the supplementary service which the mobile subscriber wants to register. 5257 Basic service 5258 This parameter indicates for which basic service group the supplementary service is to be registered. If it is not 5259 included, the registration request applies to all basic services. 5260 Forwarded-to number with subaddress 5261 This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can 5262 optionally include a sub-address. 5263 No reply condition time 5264 This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a 5265 superset of this service) and the mobile subscriber supplies a value for this time. 5266 EMLPP default priority 5267 This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at 5268 successful outcome of the service. 5269 Forwarding information 5270 This parameter is returned by the responder at successful outcome of the service, if the registration request concerned 5271 one or a group of Call Forwarding supplementary services. 5272 User error 5273 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5274 values defined in subclause 7.6.1: 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285

System failure; Data missing; Unexpected data value; Call Barred; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to.

Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to.

Illegal SS operation; SS error status; SS incompatibility.

5286 Provider error 5287 See subclause 7.6.1 for the use of this parameter.

314

3GPP

315 Release 1998

159

3GPP TS 09.02 V7.15.0 (2004-03)

5288 5289

11.2 MAP_ERASE_SS service


11.2.1 Definition

5290 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a 5291 supplementary service. The VLR will relay the message to the HLR. 5292 The service is a confirmed service and consists of four service primitives.

5293

11.2.2 Service primitives


Table 11.2/1: MAP_ERASE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O

5294 The service primitives are shown in table 11.2/1. 5295

5296

5297
5298 Invoke id

11.2.3 Parameter use

5299 See subclause 7.6.1 for the use of this parameter. 5300 SS-Code 5301 This parameter indicates the supplementary service which the mobile subscriber wants to erase. 5302 Basic service 5303 This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, 5304 the erasure request applies to all basic services. 5305 Forwarding information 5306 This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or 5307 a group of Call Forwarding supplementary services. 5308 User error 5309 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5310 values, defined in subclause 7.6.1: 5311 5312 5313 5314 5315 5316 5317 5318

System failure; Data Missing; Unexpected data value; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to.

Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to.

Call Barred;

316

3GPP

317 Release 1998

160

3GPP TS 09.02 V7.15.0 (2004-03)

5319 5320

Illegal SS operation; SS error status.

5321 Provider error 5322 See subclause 7.6.1 for the use of this parameter.

5323 5324

11.3 MAP_ACTIVATE_SS service


11.3.1 Definition

5325 This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary 5326 service. The VLR will relay the message to the HLR. 5327 The service is a confirmed service and consists of four service primitives.

5328

11.3.2 Service primitives


Table 11.3/1: MAP_ACTIVATE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) Confirm M(=)

5329 The service primitives are shown in table 11.3/1. 5330

C C C C

C(=) C(=) C(=) C(=) O

5331

5332
5333 Invoke id

11.3.3 Parameter use

5334 See subclause 7.6.1 for the use of this parameter. 5335 SS-Code 5336 This parameter indicates the supplementary service which the mobile subscriber wants to activate. 5337 Basic service 5338 This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it 5339 is not included, the activation request applies to all basic services. 5340 Forwarding information 5341 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 5342 Call Forwarding. 5343 Call barring information 5344 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 5345 Call Barring. 5346 SS-Data 5347 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for 5348 example Call Waiting.

318

3GPP

319 Release 1998

161

3GPP TS 09.02 V7.15.0 (2004-03)

5349 User error 5350 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5351 values, defined in subclause 7.6.1: 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365

System failure; Data Missing; Unexpected data value; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to.

Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to.

Call Barred; Illegal SS operation; SS error status; SS subscription violation; SS incompatibility; Negative PW check; Number Of PW Attempts Violation.

5366 Provider error 5367 See subclause 7.6.1 for the use of this parameter.

5368 5369

11.4 MAP_DEACTIVATE_SS service


11.4.1 Definitions

5370 This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary 5371 service. The VLR will relay the message to the HLR. 5372 The service is a confirmed service and consists of four service primitives.

5373

11.4.2 Service primitives


Table 11.4/1: MAP_DEACTIVATE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C C C C O Confirm M(=) C(=) C(=) C(=) C(=)

5374 The service primitives are shown in table 11.4/1. 5375

5376

320

3GPP

321 Release 1998

162

3GPP TS 09.02 V7.15.0 (2004-03)

5377
5378 Invoke id

11.4.3 Parameter use

5379 See subclause 7.6.1 for the use of this parameter. 5380 SS-Code 5381 This parameter indicates the supplementary service which the mobile subscriber wants to deactivate. 5382 Basic service 5383 This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If 5384 it is not included the deactivation request applies to all basic services. 5385 Forwarding information 5386 This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned 5387 one or a group of Call Forwarding supplementary services. 5388 Call barring information 5389 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one 5390 or a group of Call Barring supplementary services. 5391 SS-Data 5392 This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request 5393 concerned the Call Waiting supplementary service. 5394 User error 5395 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5396 values, defined in subclause 7.6.1: 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409

System failure; Data Missing; Unexpected data value; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to.

Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to.

Call Barred; Illegal SS operation; SS error status; SS subscription violation; Negative PW check; Number Of PW Attempts Violation.

5410 Provider error 5411 See subclause 7.6.1 for the use of this parameter.

322

3GPP

323 Release 1998

163

3GPP TS 09.02 V7.15.0 (2004-03)

5412 5413

11.5 MAP_INTERROGATE_SS service


11.5.1 Definitions

5414 This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related 5415 to a supplementary service. The VLR will relay the message to the HLR if necessary. 5416 The service is a confirmed service and consists of four service primitives.

5417

11.5.2 Service primitives


Table 11.5/1: MAP_INTERROGATE_SS parameters
Parameter name Invoke id SS-Code Basic service SS-Status Basic service Group LIST Forwarding feature LIST CLI restriction Info EMLPP Info CCBS Feature LIST User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C C C C C C C Confirm M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O

5418 The service primitives are shown in table 11.5/1. 5419

5420

5421

11.5.3 Parameter use

5422 For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications. 5423 Invoke id 5424 See subclause 7.6.1 for the use of this parameter. 5425 SS-Code 5426 The mobile subscriber can only interrogate a single supplementary service per service request. 5427 Basic service 5428 This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not 5429 included, the interrogation request applies to all basic services. 5430 SS-Status 5431 This parameter is included by the responder if: 5432 5433 5434 5435 5436

the interrogated supplementary service can only be subscribed for all applicable basic services simultaneously; or the interrogated supplementary service is not active for any of the interrogated basic services, or the interrogation was for the CCBS supplementary service and no CCBS request is active or the service is not provisioned.

5437 Basic service group LIST 5438 This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary 5439 service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) 5440 basic service groups, the SS-Status parameter is returned.

324

3GPP

325 Release 1998

164

3GPP TS 09.02 V7.15.0 (2004-03)

5441 Forwarding feature LIST 5442 The forwarding feature parameter is described in subclause 7.6.4. A list of one or more forwarding features is returned 5443 by the responder when the interrogation request applied to Call Forwarding supplementary service. 5444 If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all 5445 provisioned basic services. 5446 CLI restriction Info 5447 The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR 5448 supplementary service. 5449 EMLPP Info 5450 The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation 5451 request applies to the eMLPP supplementary service. 5452 CCBS Feature LIST 5453 The CCBS feature parameter is described in subclause 7.6. A list of one or more CCBS features is returned by the 5454 responder when the interrogation request applied to the CCBS supplementary service. See GSM 03.93 [107] for the 5455 conditions for the presence of the parameters included in the CCBS feature. 5456 User error 5457 This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the 5458 following values, defined in subclause 7.6.1: 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468

System failure; Data Missing; Unexpected data value; Bearer Service not provisioned; This error is returned only if not even a subset of the interrogated bearer services are provided.

Teleservice not provisioned; This error is returned only if not even a subset of the interrogated teleservices are provided.

Call Barred; Illegal SS operation; SS not available.

5469 Provider error 5470 See subclause 7.6.1 for the use of this parameter.

5471 5472

11.6 MAP_INVOKE_SS service


11.6.1 Definitions

5473 This service is used between the MSC and the VLR to check the subscriber's subscription to a given supplementary 5474 service in the VLR, in connection with in-call invocation of that supplementary service, i.e. after the call set-up phase is 5475 finished. For supplementary service invocation during call set-up phase, please refer to the call handling descriptions. 5476 The service is a confirmed service and consists of four service primitives.

326

3GPP

327 Release 1998

165

3GPP TS 09.02 V7.15.0 (2004-03)

5477

11.6.2 Service primitives


Table 11.6/1: MAP_INVOKE_SS parameters
Parameter name Invoke id SS-Code Basic service User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C Confirm M(=) C(=) O

5478 The service primitives are shown in table 11.6/1. 5479

5480

5481
5482 Invoke id

11.6.3 Parameter use

5483 See subclause 7.6.1 for the use of this parameter. 5484 SS-Code 5485 This SS-Code can only refer to a single supplementary service, e.g. the Call Hold or Multi Party supplementary 5486 services. 5487 Basic service 5488 This parameter indicates for which basic service the supplementary service invocation is required. 5489 User error 5490 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5491 values: 5492 5493 5494 5495 5496 5497 5498

System Failure; Data Missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS not available.

5499 Provider error 5500 See subclause 7.6.1 for the use of this parameter.

5501 5502

11.7 MAP_REGISTER_PASSWORD service


11.7.1 Definitions

5503 This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber 5504 requests to register a new password. The VLR will relay the message to the HLR. 5505 The service is a confirmed service and consists of four service primitives.

328

3GPP

329 Release 1998

166

3GPP TS 09.02 V7.15.0 (2004-03)

5506

11.7.2 Service primitives


Table 11.7/1: MAP_REGISTER_PASSWORD parameters
Parameter name Invoke id SS-Code New password User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

5507 The service primitives are shown in table 11.7/1. 5508

5509

5510
5511 Invoke id

11.7.3 Parameter use

5512 See subclause 7.6.1 for the use of this parameter. 5513 SS-Code 5514 This parameter indicates for which supplementary service(s) the password should be registered. 5515 New Password 5516 See subclause 7.6.4 for the use of this parameter. 5517 User error 5518 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5519 values, defined in subclause 7.6.1: 5520 5521 5522 5523 5524 5525 5526 5527

System failure; Data Missing; Unexpected data value; Call Barred; SS subscription violation; Password registration failure; Negative PW check; Number Of PW Attempts Violation.

5528 Provider error 5529 See subclause 7.6.1 for the use of this parameter.

5530 5531

11.8 MAP_GET_PASSWORD service


11.8.1 Definitions

5532 This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a 5533 request from the mobile subscriber for an operation on a supplementary service which requires a password from the 5534 subscriber. The VLR will relay the message to the MSC. 5535 The service is a confirmed service and consists of four service primitives.

330

3GPP

331 Release 1998

167

3GPP TS 09.02 V7.15.0 (2004-03)

5536

11.8.2 Service primitives


Table 11.8/1: MAP_GET_PASSWORD parameters
Parameter name Invoke id Linked id Guidance info Current password Provider error Request M C M Indication M(=) C(=) M(=) Response M(=) M Confirm M(=) M(=) O

5537 The service primitives are shown in table 11.8/1. 5538

5539

5540
5541 Invoke id

11.8.3 Parameter use

5542 See subclause 7.6.1 for the use of this parameter. 5543 Linked Id 5544 See subclause 7.6.1 for the use of this parameter. If the MAP GET PASSWORD service is used in conjunction with the 5545 MAP REGISTER PASSWORD service, this parameter must be present; otherwise it must be absent. 5546 Guidance info 5547 See subclause 7.6.4 for the use of this parameter. 5548 Current password 5549 See subclause 7.6.4 for the use of this parameter. 5550 Provider error 5551 See subclause 7.6.1 for the use of this parameter.

5552 5553 5554

11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service


11.9.1 Definitions

5555 This service is used between the MSC and the VLR, between the VLR and the HLR and between the HLR and gsmSCF 5556 to relay information in order to allow unstructured supplementary service operation. 5557 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from 5558 table 11.9/1.

5559
5560

11.9.2 Service primitives


Table 11.9/1: MAP_PROCESS_UNSTRUCTURED_SS_REQUEST parameters
Parameter name Invoke id USSD Data Coding Scheme USSD String MSISDN User error Provider error Request M M M U Indication M(=) M(=) M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O

5561

332

3GPP

333 Release 1998

168

3GPP TS 09.02 V7.15.0 (2004-03)

5562
5563 Invoke id

11.9.3 Parameter use

5564 See subclause 7.6.1 for the use of this parameter. 5565 USSD Data Coding Scheme: 5566 See subclause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the 5567 unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be 5568 present. 5569 USSD String: 5570 See subclause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the 5571 unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme 5572 parameter has to be present. 5573 MSISDN: 5574 The subscribers basic MSISDN. 5575 See definition in subclause 7.6.2. The MSISDN is included as an operator option, e.g. to allow addressing the 5576 subscribers data in the gsmSCF with the MSISDN. 5577 User error 5578 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5579 values defined in subclause 7.6.1: 5580 5581 5582 5583 5584 5585

System failure; Data missing; Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string.

Call Barred; Unknown Alphabet.

5586 Provider error 5587 See subclause 7.6.1 for the use of this parameter.

5588 5589

11.10 MAP_UNSTRUCTURED_SS_REQUEST service


11.10.1 Definitions

5590 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 5591 when the invoking entity requires information from the mobile user, in connection with unstructured supplementary 5592 service handling. 5593 The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.10/1.

334

3GPP

335 Release 1998

169

3GPP TS 09.02 V7.15.0 (2004-03)

5594

11.10.2 Service primitives


Table 11.10/1: MAP_UNSTRUCTURED_SS_REQUEST parameters
Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error Request M M M C Indication M(=) M(=) M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O

5595 The service primitives are shown in table 11.10/1. 5596

5597

5598
5599 Invoke id

11.10.3 Parameter use

5600 See subclause 7.6.1 for the use of this parameter. 5601 USSD Data Coding Scheme: 5602 See subclause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the 5603 mobile user's MMI input. If this parameter is present, then the USSD String parameter has to be present. 5604 USSD String: 5605 See subclause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the 5606 mobile user's MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. 5607 Alerting Pattern 5608 See subclause 7.6.3 for the use of this parameter. 5609 User error 5610 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5611 values defined in subclause 7.6.1: 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622

System failure; Data missing; Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string.

Absent Subscriber; Illegal Subscriber; This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication.

Illegal Equipment; USSD Busy; Unknown Alphabet.

5623 Provider error 5624 See subclause 7.6.1 for the use of this parameter.

336

3GPP

337 Release 1998

170

3GPP TS 09.02 V7.15.0 (2004-03)

5625 5626

11.11 MAP_UNSTRUCTURED_SS_NOTIFY service


11.11.1 Definitions

5627 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 5628 when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured 5629 supplementary services handling. 5630 The MAP_UNSTRUCTURED_SS_NOTIFY service is a confirmed service using the primitives from table 11.11/1.

5631

11.11.2 Service primitives


Table 11.11/1: MAP_UNSTRUCTURED_SS_NOTIFY parameters
Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error Request M M M C Indication M(=) M(=) M(=) C(=) C C(=) O Response M(=) Confirm M(=)

5632 The service primitives are shown in table 11.11/1. 5633

5634

5635
5636 Invoke id

11.11.3 Parameter use

5637 See subclause 7.6.1 for the use of this parameter. 5638 USSD Data Coding Scheme: 5639 See subclause 7.6.4 for the use of this parameter. 5640 USSD String: 5641 See subclause 7.6.1 for the use of this parameter. 5642 Alerting Pattern 5643 See subclause 7.6.3 for the use of this parameter. 5644 User error 5645 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5646 values defined in subclause 7.6.1: 5647 5648 5649 5650 5651 5652 5653 5654

System failure; Data missing; Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string.

Absent Subscriber; Illegal Subscriber; This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication.

338

3GPP

339 Release 1998

171

3GPP TS 09.02 V7.15.0 (2004-03)

5655 5656 5657

Illegal Equipment; USSD Busy; Unknown Alphabet.

5658 Provider error 5659 See subclause 7.6.1 for the use of this parameter.

5660 5661

11.12 MAP_SS_INVOCATION_NOTIFY
11.12.1 Definition

5662 This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following 5663 supplementary services; CD, ECT or MPTY.

5664

11.12.2 Service primitives


Table 11.12/1: SS_INVOCATION_NOTIFY parameters
Parameter name Invoke id MSISDN IMSI SS- event SS- event data User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

5665 The service primitives are shown in table 11.12/1. 5666

C(=) O

5667

5668

11.12.3 Parameter use

5669 All parameters are described in subclause 7.6. The use of these parameters and the requirements for their presence are 5670 specified in GSM 03.78. 5671 User error 5672 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5673 5674 5675

Data Missing; Unexpected Data Value; Unknown Subscriber.

5676 Provider error 5677 This is defined in subclause 7.6.1.

5678 5679

11.13 MAP_REGISTER_CC_ENTRY service


11.13.1 Definition

5680 This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested 5681 call completion supplementary service. The VLR will relay the message to the HLR. 5682 The service is a confirmed service and uses the service primitives shown in table 11.13/1.

340

3GPP

341 Release 1998

172

3GPP TS 09.02 V7.15.0 (2004-03)

5683

11.13.2 Service primitives


Table 11.13/1: MAP_REGISTER_CC_ENTRY parameters
Parameter name Invoke id SS Code CCBS Feature Translated B number Service Indicator Call Info Network Signal Info User error Provider error Request M M C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) Response M(=) C Confirm M(=) C(=)

5684 The service primitives are shown in table 11.13/1. 5685

C(=) O

5686

5687

11.13.3 Parameter use

5688 See subclause 7.6 for a definition of the parameters used, in addition to the following. 5689 SS-Code 5690 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an 5691 entry. 5692 CCBS Feature 5693 See GSM 03.93 for the conditions for the presence of the parameters included in the CCBS feature. 5694 Translated B Number 5695 See GSM 03.93 for the use of this parameter and the conditions for its presence. 5696 Service Indicator 5697 This parameter corresponds to the parameters 'Presentation Indicator' and 'CAMEL Invoked' in GSM 03.93 [107]. It 5698 indicates which services have been invoked for the original call (e.g. CLIR, Camel). See GSM 03.93 [107] for the use 5699 of this parameter and the conditions for its presence. 5700 Call Info 5701 See GSM 03.93 [107] for the use of this parameter and the conditions for its presence. 5702 Network Signal Info 5703 See GSM 03.93 [107] for the use of this parameter and the conditions for its presence. 5704 User error 5705 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5706 values, defined in subclause 7.6.1: 5707 5708 5709 5710 5711 5712

System failure; Data missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status;

342

3GPP

343 Release 1998

173

3GPP TS 09.02 V7.15.0 (2004-03)

5713 5714 5715 5716 5717 5718

SS incompatibility. Short Term Denial; Long Term Denial; Facility Not Supported; This error is reserved for future use.

NOTE:

Private Extensions shall not be sent with these user errors for this operation.

5719 Provider error 5720 See subclause 7.6.1 for the use of this parameter.

5721 5722

11.14 MAP_ERASE_CC_ENTRY service


11.14.1 Definition

5723 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call 5724 completion supplementary service. The VLR will relay the message to the HLR. 5725 The service is a confirmed service and uses the service primitives shown in table 11.14/1.

5726

11.14.2 Service primitives


Table 11.14/1: MAP_ERASE_CC_ENTRY parameters
Parameter name Invoke id SS-Code CCBS Index SS-Status User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C(=) C C Confirm M(=) C(=) C(=) C(=) O

5727 The service primitives are shown in table 11.14/1. 5728

5729

5730

11.14.3 Parameter use

5731 See subclause 7.6 for a definition of the parameters used, in addition to the following. 5732 SS-Code 5733 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an 5734 entry/entries. 5735 CCBS Index 5736 See GSM 03.93 for the use of this parameter and the condition for its presence. 5737 SS-Status 5738 Depending on the outcome of the service request this parameter may indicate either provisioned and active or not 5739 provisioned.

344

3GPP

345 Release 1998

174

3GPP TS 09.02 V7.15.0 (2004-03)

5740 User error 5741 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5742 values, defined in subclause 7.6.1: 5743 5744 5745 5746 5747 5748

System failure; Data Missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status.

5749 Private Extensions shall not be sent with these user errors for this operation. 5750 Provider error 5751 See subclause 7.6.1 for the use of this parameter.

5752 5753 5754

12

Short message service management services


12.1 MAP-SEND-ROUTING-INFO-FOR-SM service
12.1.1 Definition

5755 This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the 5756 short message to the servicing MSC. 5757 The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1.

5758

12.1.2 Service primitives


Table 12.1/1: MAP-SEND-ROUTING-INFO-FOR-SM
Parameter name Invoke Id MSISDN SM-RP-PRI Service Centre Address SM-RP-MTI SM-RP-SMEA GPRS Support Indicator IMSI Network Node Number LMSI GPRS Node Indicator Additional Number User error Provider error Request M M M M C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

5759 The service primitives are shown in table 12.1/1. 5760

C C C C C C

C(=) C(=) C(=) C(=) C(=) C(=) O

5761

346

3GPP

347 Release 1998

175

3GPP TS 09.02 V7.15.0 (2004-03)

5762
5763 Invoke id:

12.1.3 Parameter use

5764 See definition in subclause 7.6.1. 5765 MSISDN: 5766 See definition in subclause 7.6.2. 5767 SM-RP-PRI: 5768 See definition in subclause 7.6.8. 5769 Service Centre Address: 5770 See definition in subclause 7.6.2. 5771 SM-RP-MTI: 5772 See definition in subclause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 5773 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub5774 layer protocol. 5775 SM-RP-SMEA: 5776 See definition in subclause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 5777 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub5778 layer protocol. 5779 GPRS Support Indicator: 5780 See definition in subclause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of 5781 the two numbers from the HLR. 5782 IMSI: 5783 See definition in subclause 7.6.2. The presence of this parameter is mandatory in a successful case. 5784 Network Node Number: 5785 See definition in subclause 7.6.2. This parameter is provided in a successful response. 5786 LMSI: 5787 See definition in subclause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for 5788 the HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 5789 GPRS Node Indicator: 5790 See definition in subclause 7.6.8. The presence of this parameter is mandatory if only the SGSN number is sent in the 5791 Network Node Number. 5792 Additional Number: 5793 See definition in subclause 7.6.2. This parameter is provided in a successful response. 5794 User error: 5795 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 5796 5797 5798 5799

Unknown subscriber; Call Barred; Teleservice Not Provisioned; Absent Subscriber_SM;

348

3GPP

349 Release 1998

176

3GPP TS 09.02 V7.15.0 (2004-03)

5800 5801 5802 5803

Facility Not Supported; System failure; Unexpected Data Value; Data missing.

5804 Provider error: 5805 For definition of provider errors see subclause 7.6.1.

5806 5807

12.2 MAP-MO-FORWARD-SHORT-MESSAGE service


12.2.1 Definition

5808 This service is used between the serving MSC or the SGSN and the SMS Interworking MSC to forward mobile 5809 originated short messages. 5810 The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 5811 table 12.2/1.

5812

12.2.2 Service primitives


Table 12.2/1: MAP-MO-FORWARD-SHORT-MESSAGE
Parameter name Invoke Id SM RP DA SM RP OA SM RP UI IMSI User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O

5813 The service primitives are shown in table 12.2/1. 5814

5815

5816
5817 Invoke id:

12.2.3 Parameter use

5818 See definition in subclause 7.6.1. 5819 SM RP DA: 5820 See definition in subclause 7.6.8. 5821 In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile 5822 station. 5823 SM RP OA: 5824 See definition in subclause 7.6.8. 5825 The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM 5826 transfer. 5827 SM RP UI: 5828 See definition in subclause 7.6.8. The short message transfer protocol data unit received from the Service Centre is 5829 inserted in this parameter.

350

3GPP

351 Release 1998

177

3GPP TS 09.02 V7.15.0 (2004-03)

5830 IMSI: 5831 See definition in subclause 7.6.2.1. The IMSI of the originating subscriber is inserted in this parameter in the mobile 5832 originated SM transfer. 5833 This parameter shall be included if the sending entity, whether MSC or SGSN, supports mobile number portability. 5834 User error: 5835 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845

Facility Not Supported; System Failure; SM Delivery Failure; The reason of the SM Delivery Failure can be one of the following in the mobile originated SM: unknown Service Centre address; Service Centre congestion; invalid Short Message Entity address; subscriber not Service Centre subscriber; protocol error.

Unexpected Data Value

5846 Provider error: 5847 For definition of provider errors see subclause 7.6.1.

5848 5849

12.3 MAP-REPORT-SM-DELIVERY-STATUS service


12.3.1 Definition

5850 This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is 5851 used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This 5852 service is invoked by the gateway MSC. 5853 The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in 5854 table 12.3/1.

5855

12.3.2 Service primitives

5856 The service primitives are shown in table 12.3/1.

352

3GPP

353 Release 1998

178

3GPP TS 09.02 V7.15.0 (2004-03)

5857

Table 12.3/1: MAP-REPORT-SM-DELIVERY-STATUS


Parameter name Invoke Id MSISDN Service Centre Address SM Delivery Outcome Absent Subscriber Diagnostic SM GPRS Support Indicator Delivery Outcome Indicator Additional SM Delivery Outcome Additional Absent Subscriber Diagnostic SM MSIsdn-Alert User error Provider error Request M M M M C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C C C(=) C(=) O Response M(=) Confirm M(=)

5858

5859
5860 Invoke id:

12.3.3 Parameter use

5861 See definition in subclause 7.6.1. 5862 MSISDN: 5863 See definition in subclause 7.6.2. 5864 Service Centre Address: 5865 See definition in subclause 7.6.2. 5866 SM Delivery Outcome: 5867 See definition in subclause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. 5868 Absent Subscriber Diagnostic SM: 5869 See definition in subclause 7.6.8. 5870 GPRS Support Indicator: 5871 See definition in subclause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of 5872 two delivery outcomes. 5873 Delivery Outcome Indicator: 5874 See definition in subclause 7.6.8. 5875 Additional SM Delivery Outcome: 5876 See definition in subclause 7.6.8. 5877 Additional Absent Subscriber Diagnostic SM: 5878 See definition in subclause 7.6.8. 5879 MSIsdn-Alert: 5880 See definition in subclause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN 5881 received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned 5882 to the gateway MSC.

354

3GPP

355 Release 1998

179

3GPP TS 09.02 V7.15.0 (2004-03)

5883 User error: 5884 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 5885 5886 5887 5888

Unknown Subscriber; Message Waiting List Full; Unexpected Data Value; Data missing.

5889 Provider error: 5890 For definition of provider errors see subclause 7.6.1.

5891 5892

12.4 MAP-READY-FOR-SM service


12.4.1 Definition

5893 This service is used between the MSC and VLR and as well between the VLR and the HLR. The MSC initiates this 5894 service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. 5895 The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the 5896 MSC. 5897 Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates 5898 memory available situation. The SGSN uses the service to indicate this to the HLR. 5899 The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in 5900 the GPRS. 5901 The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1.

5902

12.4.2 Service primitives


Table 12.4/1: MAP-READY-FOR-SM
Parameter name Invoke Id IMSI TMSI Alert Reason Alert Reason Indicator User error Provider error Request M C C M C Indication M(=) C(=) C(=) M(=) C(=) Response M(=) Confirm M(=)

5903 The service primitives are shown in table 12.4/1. 5904

C(=) O

5905

5906
5907 Invoke id:

12.4.3 Parameter use

5908 See definition in subclause 7.6.1. 5909 See definition in subclause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and 5910 the HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI. 5911 TMSI: 5912 See definition in subclause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR.

356

3GPP

357 Release 1998

180

3GPP TS 09.02 V7.15.0 (2004-03)

5913 Alert Reason: 5914 See definition in subclause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory 5915 available. 5916 Alert Reason Indicator: 5917 See definition in subclause 7.6.8. 5918 User error: 5919 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 5920 5921 5922 5923 5924

Unknown Subscriber; Facility Not Supported: System Failure; Unexpected Data Value; Data missing;

5925 Provider error: 5926 For definition of provider errors see subclause 7.6.1.

5927 5928

12.5 MAP-ALERT-SERVICE-CENTRE service


12.5.1 Definition

5929 This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects 5930 that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available. 5931 The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1.

5932

12.5.2 Service primitives


Table 12.5/1: MAP-ALERT-SERVICE-CENTRE
Parameter name Invoke Id MSIsdn-Alert Service Centre Address User error Provider error Request M M M Indication M(=) M(=) M(=) Response M(=) C Confirm M(=) C(=) O

5933 The service primitives are shown in table 12.5/1. 5934

5935

5936
5937 Invoke id:

12.5.3 Parameter use

5938 See definition in subclause 7.6.1. 5939 MSIsdn-Alert: 5940 See definition in subclause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data 5941 file.

358

3GPP

359 Release 1998

181

3GPP TS 09.02 V7.15.0 (2004-03)

5942 Service Centre Address: 5943 See definition in subclause 7.6.2. 5944 User error: 5945 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 5946 5947 5948

System Failure; Unexpected Data Value; Data missing.

5949 Provider error: 5950 For definition of provider errors see subclause 7.6.1.

5951 5952
5953 5954 5955 5956

12.6 MAP-INFORM-SERVICE-CENTRE service


12.6.1 Definition
This service is used between the HLR and the gateway MSC to inform the Service Centre which MSISDN number is stored in the Message Waiting Data file. If the stored MSISDN number is not the same than the one received from the gateway MSC in the MAP-SEND-ROUTING-INFO-FOR-SM service primitive the stored MSISDN number is included in the message.

5957 Additionally the status of MCEF, MNRF and MNRG flags and the inclusion of the particular Service Centre address in 5958 the Message Waiting Data list is informed to the gateway MSC when appropriate. 5959 The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1.

5960

12.6.2 Service primitives


Table 12.6/1: MAP-INFORM-SERVICE-CENTRE
Parameter name Invoke Id MSIsdn-Alert MWD Status Request M C C Indication M(=) C(=) C(=)

5961 The service primitives are shown in table 12.6/1. 5962

5963

5964
5965 Invoke id:

12.6.3 Parameter use

5966 See definition in subclause 7.6.1. 5967 MSIsdn-Alert: 5968 See definition in subclause 7.6.2 This parameter refers to the MSISDN stored in a Message Waiting Data file in the 5969 HLR. 5970 MWD Status: 5971 See definition in subclause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the 5972 status of the particular SC address presence in the Message Waiting Data list.

360

3GPP

361 Release 1998

182

3GPP TS 09.02 V7.15.0 (2004-03)

5973 5974

12.7 MAP-SEND-INFO-FOR-MT-SMS service


12.7.1 Definition

5975 This service is used between the MSC and the VLR. The service is invoked by the MSC receiving an mobile terminated 5976 short message to request subscriber related information from the VLR. 5977 The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1.

5978

12.7.2 Service primitives


Table 12.7/1: MAP-SEND-INFO-FOR-MT-SMS
Parameter name Invoke Id SM RP DA MSISDN User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

5979 The service primitives are shown in table 12.7/1. 5980

5981

5982
5983 Invoke id:

12.7.3 Parameter use

5984 See definition in subclause 7.6.1. 5985 SM RP DA: 5986 See definition in subclause 7.6.8. This parameter shall contain either an IMSI or a LMSI. 5987 MSISDN: 5988 See definition in subclause 7.6.2. 5989 User error: 5990 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 5991 5992 5993 5994 5995 5996 5997 5998 5999

Unknown subscriber; Unidentified Subscriber; Absent subscriber; Unexpected Data Value; Data Missing; Illegal subscriber; Illegal equipment; Subscriber busy for MT SMS; System Failure.

6000 Provider error: 6001 For definition of provider errors see subclause 7.6.1.

362

3GPP

363 Release 1998

183

3GPP TS 09.02 V7.15.0 (2004-03)

6002 6003

12.8 MAP-SEND-INFO-FOR-MO-SMS service


12.8.1 Definition

6004 This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile 6005 originated short message request to request the subscriber related information from the VLR. 6006 The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1.

6007

12.8.2 Service primitives


Table 12.8/1: MAP-SEND-INFO-FOR-MO-SMS
Parameter name Invoke Id Service Centre Address MSISDN User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

6008 The service primitives are shown in table 12.8/1. 6009

6010

6011
6012 Invoke id:

12.8.3 Parameter use

6013 See definition in subclause 7.6.1. 6014 Service Centre Address: 6015 See definition in subclause 7.6.2. 6016 MSISDN: 6017 See definition in subclause 7.6.2. 6018 User error: 6019 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 6020 6021 6022 6023

Teleservice Not Provisioned; Call Barred; Unexpected Data Value; Data Missing.

6024 Provider error: 6025 For definition of provider errors see subclause 7.6.1.

6026 6027

12.9 MAP-MT-FORWARD-SHORT-MESSAGE service


12.9.1 Definition

6028 This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile terminated short 6029 messages. 6030 The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 6031 table 12.9/1.

364

3GPP

365 Release 1998

184

3GPP TS 09.02 V7.15.0 (2004-03)

6032

12.9.2 Service primitives


Table 12.9/1: MAP-MT-FORWARD-SHORT-MESSAGE
Parameter name Invoke Id SM RP DA SM RP OA SM RP UI More Messages To Send User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O

6033 The service primitives are shown in table 12.9/1. 6034

6035

6036
6037 Invoke id:

12.9.3 Parameter use

6038 See definition in subclause 7.6.1. 6039 SM RP DA: 6040 See definition in subclause 7.6.8. This parameter can contain either an IMSI or a LMSI. The use of the LMSI is an 6041 operator option. The LMSI can be provided if it is received from the HLR. The IMSI is used if the use of the LMSI is 6042 not available. 6043 This parameter is omitted in the mobile terminated subsequent SM transfers. 6044 SM RP OA: 6045 See definition in subclause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in 6046 this parameter . 6047 This parameter is omitted in the mobile terminated subsequent SM transfers. 6048 SM RP UI: 6049 See definition in subclause 7.6.8. The short message transfer protocol data unit received from the Service Centre is 6050 inserted in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the 6051 message delivery acknowledgement from the MSC or from the SGSN to the Service Centre. 6052 More Messages To Send: 6053 See definition in subclause 7.6.8. The information from the MMS indication received from the Service Centre is 6054 inserted in this parameter. 6055 User error: 6056 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 6057 6058 6059 6060 6061 6062 6063 6064

Unidentified subscriber; Absent Subscriber_SM; Subscriber busy for MT SMS; Facility Not Supported; Illegal Subscriber indicates that delivery of the mobile terminated short message failed because the mobile station failed authentication; Illegal equipment indicates that delivery of the mobile terminated short message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed;

366

3GPP

367 Release 1998

185

3GPP TS 09.02 V7.15.0 (2004-03)

6065 6066 6067 6068 6069 6070 6071 6072

System Failure; SM Delivery Failure; The reason of the SM Delivery Failure can be one of the following in the mobile terminated SM: memory capacity exceeded in the mobile equipment; protocol error; mobile equipment does not support the mobile terminated short message service.

Unexpected Data Value; Data Missing.

6073 Provider error: 6074 For definition of provider errors see subclause 7.6.1.

6075 6076 6077

13

Network-Requested PDP Context Activation services


13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service
13.1.1 Definition

6078 This service is used by the GGSN to request GPRS routing information from the HLR.

6079
6080

13.1.2 Service primitives


Table 13.1/1: MAP_SEND_ROUTING_INFO_FOR_GPRS
Parameter name Invoke id IMSI GGSN address GGSN number SGSN address Mobile Not Reachable Reason User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=) O

6081

6082
6083 Invoke Id

13.1.3 Parameter definition and use

6084 See definition in subclause 7.6.1. 6085 IMSI 6086 See definition in subclause 7.6.2. 6087 GGSN address 6088 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6089 GGSN number 6090 See definition in subclause 7.6.2.

368

3GPP

369 Release 1998

186

3GPP TS 09.02 V7.15.0 (2004-03)

6091 SGSN address 6092 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 6093 process in the HLR is positive. 6094 Mobile Not Reachable Reason 6095 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 6096 process in the HLR is positive and the MNRG flag in the HLR is set. See definition in subclause 7.6.3.51. 6097 User error 6098 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6099 6100 6101 6102 6103

Absent Subscriber; System Failure; Data Missing; Unexpected Data Value; UnknownSubscriber.

6104 The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown. 6105 Provider error 6106 These are defined in subclause 7.6.1.

6107 6108

13.2 MAP_FAILURE_REPORT service


13.2.1 Definition

6109 This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed.

6110
6111

13.2.2 Service primitives


Table 13.2/1: MAP_FAILURE_REPORT
Parameter name Invoke id IMSI GGSN address GGSN number User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

6112

6113
6114 Invoke Id

13.2.3 Parameter definition and use

6115 See definition in subclause 7.6.1. 6116 IMSI 6117 See definition in subclause 7.6.2. 6118 GGSN address 6119 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR.

370

3GPP

371 Release 1998

187

3GPP TS 09.02 V7.15.0 (2004-03)

6120 GGSN number 6121 See definition in subclause 7.6.2. 6122 User error 6123 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6124 6125 6126 6127

System Failure; Data Missing; Unexpected Data Value; UnknownSubscriber.

6128 Provider error 6129 These are defined in subclause 7.6.1.

6130 6131

13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service


13.3.1 Definition

6132 This service is used by the HLR to inform the GGSN that the MS is present for GPRS again.

6133
6134

13.3.2 Service primitives


Table 13.3/1: MAP_NOTE_MS_PRESENT_FOR_GPRS
Parameter name Invoke id IMSI GGSN address SGSN address User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) Confirm M(=)

C(=) O

6135

6136
6137 Invoke Id

13.3.3 Parameter definition and use

6138 See definition in subclause 7.6.1. 6139 IMSI 6140 See definition in subclause 7.6.2. 6141 GGSN address 6142 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6143 SGSN address 6144 See definition in subclause 7.6.2. 6145 User error 6146 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6147 6148

System Failure; Data Missing;

372

3GPP

373 Release 1998

188

3GPP TS 09.02 V7.15.0 (2004-03)

6149 6150

Unexpected Data Value; UnknownSubscriber.

6151 Provider error 6152 These are defined in subclause 7.6.1.

6153 6154 6155

13A

Location Service Management Services


13A.1MAP-SEND-ROUTING-INFO-FOR-LCS Service
13A.1.1 Definition

6156 This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location 6157 service request to the servicing VMSC. The MAP-SEND-ROUTING-INFO-FOR-LCS is a confirmed service using the 6158 primitives from table A.1/1.

6159

13A.1.2 Service Primitives


Table 13A.1/1: MAP-SEND-ROUTING-INFO-FOR-LCS
Parameter name Invoke Id MLC Number MSISDN IMSI LMSI MSC Number User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) C C C C C Confirm M(=) C(=) C(=) C(=) C(=) C(=) O

6160 The service primitives are shown in table 13A.1/1. 6161

6162

374

3GPP

375 Release 1998

189

3GPP TS 09.02 V7.15.0 (2004-03)

6163
6164 Invoke id:

13A.1.3 Parameter Use

6165 See definition in subclause 7.6.1. 6166 MLC Number: 6167 See definition in subclause 7.6.2. 6168 MSISDN: 6169 See definition in subclause 7.6.2. The request shall carry either the IMSI or MSISDN. The response shall carry 6170 whichever of these was not included in the request (see GSM 03.71 for details). 6171 IMSI: 6172 See definition in subclause 7.6.2. 6173 LMSI: 6174 See definition in subclause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for 6175 the HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6176 MSC Number: 6177 See definition in subclause 7.6.2. This parameter is provided in a successful response. 6178 User error: 6179 The following errors defined in subclause 7.6.1 may be used, depending on the nature of the fault: 6180 6181 6182 6183 6184 6185 6186

Unknown subscriber; Absent Subscriber; Facility Not Supported; System failure; Unexpected Data Value; Data missing; Unauthorized requesting network

376

3GPP

377 Release 1998

190

3GPP TS 09.02 V7.15.0 (2004-03)

6187 Provider error: 6188 For definition of provider errors see subclause 7.6.1.

6189 6190

13A.2MAP-PROVIDE-SUBSCRIBER-LOCATION Service
13A.2.1 Definition

6191 This service is used by a GMLC to request the location of a target MS from the visited MSC at any time. This is a 6192 confirmed service using the primitives from table 13A.2/1.

6193
6194

13A.2.2 Service Primitives


Table 13A.2/1: Provide_Subscriber_Location
Parameter name Invoke id Location Type MLC Number LCS Client ID Privacy Override IMSI MSISDN LMSI LCS Priority LCS QoS IMEI Location Estimate Age of Location Estimate User error Provider error Request M M M M U C C C C C U Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

M C C

M(=) C(=) C(=) O

6195

6196

13A.2.3 Parameter Definition and Use

6197 All parameters are defined in section 7.6. The use of these parameters and the requirements for their presence are 6198 specified in GSM 03.71. 6199 Location Type 6200 This parameter identifies the type of location information requested 6201 MLC Number 6202 This is the E.164 number of the requesting GMLC. 6203 LCS Client ID 6204 This parameter provides information related to the identity of an LCS client. 6205 Privacy Override 6206 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC for an MR-LR are 6207 in the same country. 6208 IMSI 6209 The IMSI is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 6210 MSISDN 6211 The MSISDN is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory.

378

3GPP

379 Release 1998

191

3GPP TS 09.02 V7.15.0 (2004-03)

6212 LMSI 6213 The LMSI shall be provided if previously supplied by the HLR 6214 LCS Priority 6215 This parameter indicates the priority of the location request. 6216 LCS QoS 6217 This parameter indicates the required quality of service in terms of response time and accuracy. 6218 IMEI 6219 Inclusion of the IMEI is optional. 6220 Location Estimate 6221 This parameter provides the location estimate. 6222 Age of Location Estimate 6223 This parameter indicates how long ago the location estimate was obtained. 6224 User error 6225 This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one 6226 of the following values defined in section 7.6.1: 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237

System Failure; Data Missing; Unexpected Data Value; Facility Not Supported; Unidentified Subscriber; Illegal Subscriber; Illegal Equipment; Absent Subscriber (diagnostic information may also be provided); Unauthorized requesting network; Unauthorized LCS Client with detailed reason; Position method failure with detailed reason.

6238 Provider error 6239 These are defined in subclause 7.6.1.

6240 6241

13A.3MAP-SUBSCRIBER-LOCATION-REPORT Service
13A.3.1 Definition

6242 This service is used by a VMSC to provide the location of a target MS to a GMLC when a request for location is either 6243 implicitly administered or made at some earlier time. This is a confirmed service using the primitives from 6244 table 13A.3/1.

6245

13A.3.2 Service Primitives

380

3GPP

381 Release 1998

192

3GPP TS 09.02 V7.15.0 (2004-03)

6246

Table 13A.3/1: Subscriber_Location_Report


Parameter name Invoke id LCS Event LCS Client ID MSC Number IMSI MSISDN NA-ESRD NA-ESRK IMEI Location Estimate Age of Location Estimate LMSI User error Provider error Request M M M M C C C C U C C U Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C(=) O Response M(=) Confirm M(=)

6247

6248

13A.3.3 Parameter Definition and Use

6249 All parameters are defined in section 7.6. The use of these parameters and the requirements for their presence are 6250 specified in GSM 03.71. 6251 LCS Event 6252 This parameter indicates the event that triggered the Subscriber Location Report. 6253 LCS Client ID 6254 This parameter provides information related to the identity of the recipient LCS client. 6255 MSC Number 6256 See definition in subclause 7.6.2. This parameter provides the address of the visited MSC for target MS. 6257 IMSI 6258 The IMSI shall be provided if available to the VMSC 6259 MSISDN 6260 The MSISDN shall be provided if available to the VMSC 6261 NA-ESRD 6262 If the target MS has originated an emergency service call in North America, the NA-ESRD shall be provided by the 6263 VMSC if available. 6264 NA-ESRK 6265 If the target MS has originated an emergency service call in North America, the NA-ESRK shally be provided by the 6266 VMSC if assigned. 6267 IMEI 6268 Inclusion of the IMEI is optional. 6269 Location Estimate 6270 This parameter provides the location estimate. The absence of this parameter implies that a location estimate was not 6271 available or could not be successfully obtained.

382

3GPP

383 Release 1998

193

3GPP TS 09.02 V7.15.0 (2004-03)

6272 Age of Location Estimate 6273 This parameter indicates how long ago the location estimate was obtained. 6274 LMSI 6275 The LMSI may be provided if assigned by the VLR. 6276 User error 6277 This parameter is sent by the responder when the received message contains an error, cannot be forwarded or stored for 6278 an LCS client or cannot be accepted for some other reason and if present, takes one of the following values defined in 6279 section 7.6.1. 6280 6281 6282 6283 6284 6285 6286 6287

System Failure; Data Missing; Unexpected Data Value; Resource Limitation; Unknown Subscriber; Unauthorized requesting network; Unknown or unreachable LCS Client; Provider error

6288 These are defined in subclause 7.6.1.

6289 6290 6291 6292

13A.4Void
13A.4.1 - 13A.4.3 Void

13A.5Void
13A.5.1 - 13A.5.3 Void

384

3GPP

385 Release 1998

194

3GPP TS 09.02 V7.15.0 (2004-03)

6293 6294 6295 6296 6297 6298 6299 6300

13A.6Void
13A.6.1 - 13A.6.3 Void

13A.7Void
13A.7.1 - 13A.7.3 Void 13A.8 Void 13A.8.1 - 13A.8.3 Void

13A.9Void
13A.9.1 - 13A.9.3 Void

6301 6302

14

General
14.1 Overview

6303 Clauses 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. 6304 Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping on to TC service 6305 primitives. Clause 17 specifies the application contexts, operation packages and abstract syntaxes for the MAP protocol 6306 as well as the encoding rules to be applied.

6307

14.2 Underlying services

6308 The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of signalling system number 7, 6309 as referenced in clause 6.

6310
6311 6312 6313 6314

14.3 Model
The MAP Protocol Machine (MAP PM) can be modelled as a collection of service state machines (SSMs) - one per MAP specific service invoked - coordinated by a MAP dialogue control function with its one state machine: MAP dialogue state machine (DSM). There are two types of Service State Machines: Requesting Service State Machines (RSM) and Performing Service State Machines (PSM).

6315 A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a TC-BEGIN 6316 indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific service invoked 6317 during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is created at the performer's side. 6318 This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not intended to 6319 suggest any implementation. SDL descriptions are organized according to this model. 6320 How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local 6321 implementation matter. 6322 How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter.

386

3GPP

387 Release 1998

195

3GPP TS 09.02 V7.15.0 (2004-03)

6323

14.4 Conventions

6324 The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major 6325 difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do 6326 not belong to the so-called "version one context set". 6327 The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1 implementation 6328 according to the latest phase 1 version of GSM 09.02. This set is defined in clause 15. 6329 The procedures described in clause 15 are used when the application-context-name does not refer to a dialogue between 6330 an MSC and its VLR. When the application-context-name refers to a dialogue between an MSC and its VLR the MAP 6331 PM procedures are a local implementation matter.

6332 6333

15

Elements of procedure
15.1 Dialogue establishment

6334 The establishment of a MAP dialogue involves two MAP-service-users, one that is the dialogue-initiator and one that is 6335 the dialogue-responder. 6336 This procedure is driven by the following signals: 6337 6338 6339 6340

a MAP-OPEN request primitive from the dialogue-initiator; a TC-BEGIN indication primitive occurring at the responding side; a MAP-OPEN response primitive from the dialogue-responder; the first TC-CONTINUE indication primitive occurring at the initiating side;

6341 and under specific conditions: 6342 6343 6344

a TC-END indication primitive occurring at the initiating side; a TC-U-ABORT indication primitive occurring at the initiating side; a TC-P-ABORT indication primitive occurring at the initiating side.

6345
6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358

15.1.1 Handling of unknown operations


Unknown operations (i.e. a standard operation introduced in a later version of GSM 09.02 or a private operation) can be introduced in MAP in a backwards compatible way. This means, that the receiver of an unknown operation shall, if the dialogue state allows it, send a TC-REJECT component to the sender of the operation indicating 'unrecognised operation' and continue with the processing of further components or messages exchanged within the dialogue as if the unknown operation had not been received. The standardised structure of a MAP dialogue shall not be affected by the invocation of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is acknowledged by a TC-END message, a TC-CONTINUE message shall not be used to invoke an unknown operation. However the standardised structure of a MAP dialogue may be affected by the rejection of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is acknowledged by a TC-END message, a TC-CONTINUE message followed by a TC-END message may be used to carry the rejection of an unknown operation and the response to the standardised operation. The entity which initiated a dialogue whose standardised structure is a TC-BEGIN message which is acknowledged by a TC-END message shall not send any messages in that dialogue after the TC-BEGIN.

6359 Note that if the dialogue structure is affected as described in this paragraph the TC-CONTINUE shall include the 6360 dialogue portion required to confirm the acceptance of the dialogue.

388

3GPP

389 Release 1998

196

3GPP TS 09.02 V7.15.0 (2004-03)

6361 Unknown operations can be invoked in the following types of messages (there is no restriction as to how many 6362 unknown operations can be invoked in a message): 6363 6364 6365 6366 6367 6368 6369

TC-BEGIN the component to invoke the unknown operation shall follow the component of the standard operation that is included in this message. TC-CONTINUE: the component to invoke the unknown operation may be transported as the only component in a stand-alone message or can be grouped with existing operations. In the latter case a specific sequencing of components is not required. TC-END: if the component to invoke the unknown operation is grouped with an existing operation a specific sequencing of components is not required.

6370 The TC-REJECT component may be sent in the following messages: 6371 6372 6373 6374 6375 6376 6377 6378 6379

TC-CONTINUE or TC-END: either as the only component of the message or grouped with an existing component. The choice is up to the MAP-Service User. If the received message contains only unknown operations the MAP-Service User shall send the TC-REJECT components in a TC-CONTINUE message to the peer entity, if the dialogue state allows it. If the received message contains unknown operations and standard operations and the standardised structure of the dialogue requires the response to the standard operation to be sent within a TC-END message, then the MAP-Service User may send the response to the standard operations and the TC-REJECT components for the unknown operations in a TC-CONTINUE message followed by a TC-END message. A specific distribution of the components to the TC messages or a specific sequencing of components is not required.

6380 Note that SDLs of chapters 19 - 25 do not show the report to the MAP-Service User about the reception of the unknown 6381 operation. This has been done for the sake of simplicity of description; the MAP PM may inform the MAP-Service 6382 User. 6383 The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown 6384 operation.

6385

15.1.2 Receipt of a MAP-OPEN request primitive

6386 On receipt of a MAP-OPEN request primitive the behaviour of the MAP PM shall be as follows: 6387 The MAP PM shall accept zero, one or several user request primitives until a MAP-DELIMITER request primitive is 6388 received. 6389 For each user request primitive, the MAP PM shall request the invocation of the associated operation using the TC6390 INVOKE service. See subclause 15.6 for a description of the associated SSMs. 6391 On receipt of the MAP-DELIMITER request primitive the MAP PM shall issue a TC-BEGIN request primitive. The 6392 application-context-name as well as the user information parameter (if any) shall be mapped to the corresponding TC6393 BEGIN parameters. 6394 The requesting MAP PM waits for a TC indication primitive and does not accept any other primitive from its user, 6395 except a MAP-U-ABORT request or a MAP-CLOSE request.

6396

15.1.3 Receipt of a TC-BEGIN indication


if no application-context-name is included in the primitive and if the "Components present" indicator indicates "no components", issue a TC-U-ABORT request primitive (note 2). The local MAP-User is not informed. if no application-context-name is included in the primitive and if presence of components is indicated, wait for the first TC-INVOKE primitive, and derive a version 1 application-context-name from the operation code according to table 15.1/1 (note 1).

6397 On receipt of a TC-BEGIN indication primitive, the MAP PM shall: 6398 6399 6400 6401 6402 6403

NOTE 1: In some cases, it may be necessary to analyse the operation argument.

390

3GPP

391 Release 1998

197

3GPP TS 09.02 V7.15.0 (2004-03)

6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451

Then: a) if no application-context-name can be derived (i.e. the operation code does not exist in MAP V1 specifications), the MAP PM shall issue a TC-U-ABORT request primitive (note 2). The local MAP-User is not informed. b) if an application-context-name can be derived and if it is acceptable from a load control point of view, the MAP PM shall: i) if this primitive requests the beginSubscriberActivity operation, the MAP PM shall check whether more components have been received associated with this operation. If more components are present, the MAP PM shall issue a MAP-OPEN indication primitive with the version 1 application-context-name "networkFunctionalSsContext-v1". The Destination-reference shall include the IMSI taken from the argument of the beginSubscriberActivity operation; the Originating-reference shall cover the originatingEntityNumber. A beginSubscriberActivity operation that is not associated with any other Component shall be rejected by the MAP PM by issuing a TC-U-ABORT request primitive (note 2). The local MAP-User shall not be informed. ii) otherwise, the MAP PM shall issue a MAP-OPEN indication primitive with the version 1 applicationcontext-name set according to table 15.1/1. DestinationReference and OriginatingReference must not be included in the MAP-OPEN indication primitive. Then the MAP PM shall function in a way that the dialogue responding MAP behaves as specified in the GSM phase 1 protocol (latest version of TS GSM 09.02 phase 1). NOTE 2: If no AARQ apdu was included in the BEGIN message, TC (Component Sub-layer) will not include an AARE apdu or an ABRT apdu in a TR-U-ABORT request primitive that is to be issued on receipt of a TC-U-ABORT request primitive from the local MAP service provider. c) if an application-context-name can be derived but if it is not acceptable from a load control point of view, the MAP PM shall ignore this dialogue request and not inform the MAP-user; if a version 1 application-context-name is included, the MAP PM shall issue a TC-U-ABORT request primitive with abort-reason "User-specific" and user-information "MAP-ProviderAbortInfo" indicating "abnormalDialogue". The local MAP-user shall not be informed. if an application-context-name different from version 1 is included in the primitive and if User-information is present, the User-information must constitute a syntactically correct MAP-OPEN dialogue PDU. Otherwise a TC-U-ABORT request primitive with abort-reason "User-specific" and user-information "MAPProviderAbortInfo" indicating "abnormalDialogue" shall be issued and the local MAP-user shall not be informed. if no User-information is present it is checked whether presence of User Information in the TC-BEGIN indication primitive is required for the received application-context-name. If User Information is required but not present, a TC-U-ABORT request primitive with abort-reason "User-specific" and user-information "MAP-ProviderAbortInfo" indicating "abnormalDialogue" shall be issued. The local MAP-user shall not be informed.

if an application-context-name different from version 1 is received in a syntactically correct TC-BEGIN indication primitive but is not acceptable from a load control point of view, the MAP PM shall ignore this dialogue request. The MAP-user is not informed. if an application-context-name different from version 1 is received in a syntactically correct TC-BEGIN indication primitive and if it is acceptable from a load control point of view, the MAP PM shall check whether the application-context-name is supported.

NOTE 3: Unknown application-context-names are treated like unsupported ones. If it is, the MAP PM shall issue a MAP-OPEN indication primitive with all parameters (application-contextname included) set according to the value of the corresponding parameter of the TC-BEGIN indication primitive.

392

3GPP

393 Release 1998

198

3GPP TS 09.02 V7.15.0 (2004-03)

6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472

The MAP PM shall then process any other indication primitives received from TC as described in subclause 15.6. Once all the received components have been processed, the MAP PM shall inform the local MAP service user by a MAP-DELIMITER indication primitive. If the TC-BEGIN indication primitive is not associated with any component, the MAP PM shall inform the MAP User by a MAP-DELIMITER indication primitive. Once all the received primitives have been processed, the MAP PM does not accept any primitive from the provider and waits for a MAP-OPEN response primitive from its user. if an application-context-name different from version 1 is received in a syntactically correct TC-BEGIN indication primitive and if it is acceptable from a load control point of view but the application-context-name is not supported, the MAP PM shall issue a TC-U-ABORT request primitive with abort-reason indicating "application-context-not-supported". If an alternative application-context-name cannot be offered, the received application-context-name shall be returned in the TC-U-ABORT Req primitive.

In the following cases an alternative application-context can be offered and its name included in the TC-UABORT Req primitive: a) if an application-context of version 2 or higher is requested, but only version 1 application-context supported, then the v1 application context shall be returned; b) if an application-context of version 3 or higher is requested, but only version 2 application-context supported, then the v2 application context shall be returned. c) if an application-context of version 4 or higher is requested, but only version 3 application-context supported, then the v3 application context shall be returned. Table 15.1/1: Mapping of V1 operation codes on to application-context-names
Operation updateLocation cancelLocation provideRoamingNumber insertSubscriberData deleteSubscriberData sendParameters Application-context-name (note 1) networkLocUpContext-v1 locationCancellationContext-v1 roamingNumberEnquiryContext-v1 subscriberDataMngtContext-v1 subscriberDataMngtContext-v1 infoRetrievalContext-v1 networkLocUpContext-v1 (note 2) beginSubscriberActivity networkFunctionalSsContext-v1 sendRoutingInfo locationInfoRetrievalContext-v1 performHandover handoverControlContext-v1 reset resetContext-v1 activateTraceMode tracingContext-v1 deactivateTraceMode tracingContext-v1 sendRoutingInfoForSM shortMsgGatewayContext-v1 forwardSM shortMsgRelayContext-v1 reportSM-deliveryStatus shortMsgGatewayContext-v1 noteSubscriberPresent mwdMngtContext-v1 alertServiceCentreWithoutResult shortMsgAlertContext-v1 checkIMEI EquipmentMngtContext-v1 NOTE 1: These symbolic names refer to the object identifier value defined in clause 17 and allocated to each application-context used for the MAP. NOTE 2: The choice between the application contexts is based on the parameters received in the operation.

6473

394

3GPP

395 Release 1998

199

3GPP TS 09.02 V7.15.0 (2004-03)

6474
6475 6476 6477 6478 6479 6480 6481

15.1.4 Receipt of a MAP-OPEN response


On receipt of a MAP-OPEN response primitive indicating that the dialogue is accepted, the MAP PM shall build a MAP-Accept PDU if the user-information parameter is included in the response primitive and accept any MAP specific service request or service response until a MAP-DELIMITER request or a MAP-CLOSE request is received from the MAP user. The MAP PM shall process the MAP specific primitives as described in subclause 15.6. The MAP PM shall then issue a TC-CONTINUE request primitive after it receives the MAP-DELIMITER request primitive if no MAPCLOSE request primitive has been received, otherwise it shall issue a TC-END request primitive. In both cases the MAP-Accept PDU (if any) is included in the user-information parameter of the TC primitive.

6482 If the dialogue is not associated with a version 1 application context, the MAP PM shall include the application-context6483 name in the TC primitive. 6484 If no MAP-CLOSE request has been received, the MAP PM waits for a request primitive from its user or an indication 6485 primitive from TC. 6486 On receipt of a MAP-OPEN response primitive indicating that the dialogue is not accepted, the MAP PM shall build a 6487 MAP-Refuse PDU and request its transfer using the TC-U-ABORT req primitive (abort reason = user specific).

6488
6489 6490 6491 6492 6493 6494 6495

15.1.5 Receipt of the first TC-CONTINUE ind


On receipt of the first TC-CONTINUE indication primitive for a dialogue, the MAP PM shall check the value of the application-context-name parameter. If this value matches the one used in the MAP-OPEN request primitive, the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter indicating "accepted", then process the following TC component handling indication primitives as described in subclause 15.6, and then waits for a request primitive from its user or an indication primitive from TC, otherwise it shall issue a TC-U-ABORT request primitive with a MAP-providerAbort PDU indicating "abnormal dialogue" and a MAP-P-ABORT indication primitive with the "provider-reason" parameter indicating "abnormal dialogue".

6496
6497 6498 6499 6500

15.1.6 Receipt of a TC-END ind


On receipt of a TC-END indication primitive in the dialogue initiated state, the MAP PM shall check the value of the application-context-name parameter. If this value does not match the one used in the MAP-OPEN request primitive, the MAP PM shall discard any following component handling primitive and shall issue a MAP-P-ABORT indication primitive with the "provider-reason" parameter indicating "abnormal dialogue".

6501 Otherwise it shall issue a MAP-OPEN confirm primitive with the result parameter set to "accepted" and process the 6502 following TC component handling indication primitives as described in subclause 15.6; then it shall issue a MAP6503 CLOSE indication primitive and return to idle all state machines associated with the dialogue.

6504
6505 6506 6507 6508 6509 6510 6511 6512

15.1.7 Receipt of a TC-U-ABORT ind


On receipt of a TC-U-ABORT indication primitive in the "Dialogue Initiated" state with an abort-reason parameter indicating "ApplicationContextNotSupported", the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter indicating "Dialogue Refused" and the refuse-reason parameter indicating "ApplicationContextNotSupported". On receipt of a TC-U-ABORT indication primitive in the "Dialogue Initiated" state with an abort-reason parameter indicating "User Specific" and without user information, the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter indicating "Dialogue Refused" and the refuse-reason parameter indicating "Potential Version Incompatibility".

6513 On receipt of a TC-U-ABORT indication primitive in the "Dialogue Initiated" state with an abort-reason parameter 6514 indicating "User Specific" and a MAP-Refuse PDU included as user information, the MAP PM shall issue a MAP6515 OPEN confirm primitive with the result set to refused and the refuse reason set as received in the MAP Refuse PDU. 6516 Receipt of a TC-U-ABORT indication primitive with abort-reason "User Specific" and with user information is 6517 described as part of abnormal termination (see subclause 15.4.2).

396

3GPP

397 Release 1998

200

3GPP TS 09.02 V7.15.0 (2004-03)

6518

15.1.8 Receipt of a TC-P-ABORT ind

6519 On receipt of a TC-P-ABORT indication primitive in the "Dialogue Initiated" state with a P-abort parameter indicating 6520 "Incorrect Transaction Portion", the MAP PM shall issue a MAP-OPEN confirm primitive with the result parameter 6521 indicating "Dialogue Refused" and the refuse reason parameter indicating "Potential Version Incompatibility". 6522 On receipt of a TC-P-ABORT indication primitive in the "Dialogue Initiated" state with a P-abort parameter indicating 6523 "No Common Dialogue Portion", the MAP PM shall issue a MAP-P-ABORT indication primitive with the provider 6524 reason parameter indicating "Version Incompatibility". 6525 Receipt of a TC-P-ABORT indication primitive with another P-abort parameter value is described as part of abnormal 6526 termination (see subclause 15.5.2).

6527

15.2 Dialogue continuation

6528 Once established the dialogue is said to be in a continuation phase. 6529 Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue.

6530

15.2.1 Sending entity

6531 The MAP PM shall accept any MAP specific service request or response primitives and process them as described in 6532 subclause 15.6. 6533 On receipt of a MAP-DELIMITER request primitive, the MAP PM shall issue a TC-CONTINUE request primitive.

6534

15.2.2 Receiving entity

6535 On receipt of a TC-CONTINUE indication primitive the MAP PM shall accept zero, one or several TC component 6536 handling indication primitives and process them as described in subclause 15.6.

6537

15.3 Dialogue termination

6538 Both the dialogue-initiator and the dialogue-responder have the ability to request the termination of a dialogue after it 6539 has been established. 6540 The dialogue termination procedure is driven by the following events: 6541 6542

a MAP-CLOSE request primitive; a TC-END indication primitive.

6543
6544 6545 6546 6547

15.3.1 Receipt of a MAP-CLOSE request


On receipt of a MAP-CLOSE request primitive, the MAP PM shall issue a TC-END request primitive and, if applicable, return to idle the associated active SSMs. Note that if the release method parameter of the MAP-CLOSE request indicates "normal" the TC-END request primitive will trigger the transmission of components associated with any user specific request or response primitives which may have been issued after the last MAP-DELIMITER request.

6548

15.3.2 Receipt of a TC-END indication

6549 On receipt of a TC-END indication primitive, the MAP shall accept any component handling indication primitives and 6550 process them as described in subclause 15.6. 6551 Once all the received primitives have been processed, the MAP PM shall return to idle the associated SSMs and issue a 6552 MAP-CLOSE indication primitive.

398

3GPP

399 Release 1998

201

3GPP TS 09.02 V7.15.0 (2004-03)

6553

15.4 User Abort

6554 Both the dialogue-initiator and the dialogue-responder have the ability to abort a dialogue at any time. 6555 The user abort procedure is driven by one of the following events: 6556 6557

a MAP-U-ABORT request primitive; a TC-U-ABORT indication primitive carrying a MAP-user-abort PDU.

6558

15.4.1 MAP-U-ABORT request

6559 On receipt of a MAP-U-ABORT request the MAP PM shall construct a MAP-user-abort PDU from the user-reason and 6560 diagnostic parameters and issue a TC-U-ABORT request primitive. All state machines associated with the dialogue are 6561 returned to idle.

6562

15.4.2 TC-U-ABORT ind

6563 On receipt of a TC-U-ABORT indication carrying a MAP-user-abort PDU, the MAP PM shall issue a MAP-U-ABORT 6564 indication primitive. The user-reason and diagnostic information elements are mapped to the corresponding parameters 6565 of the MAP-U-ABORT indication primitive. 6566 All state machines associated with the dialogue are returned to idle.

6567

15.5 Provider Abort

6568 The MAP has the ability to abort a dialogue at both the dialogue-initiator side and the dialogue-responder side. 6569 The provider abort procedure is driven by one of the following events: 6570 6571 6572

a MAP PM error situation; a TC-P-ABORT indication primitive; a TC-U-ABORT indication primitive carrying a MAP-abort PDU.

6573

15.5.1 MAP PM error situation


issue a MAP-P-ABORT indication primitive with the appropriate value of the provider-reason parameter; construct a MAP-abort PDU from the value of these parameters and request its transfer using a TC-U-ABORT request primitive.

6574 In the case of an abnormal situation detected at the MAP level during an established dialogue, the MAP PM shall: 6575 6576 6577

6578

15.5.2 TC-P-ABORT ind

6579 On receipt of a TC-P-ABORT indication, the MAP PM shall issue a MAP-P-ABORT indication primitive. 6580 All state machines associated with the dialogue are returned to idle.

6581

15.5.3 TC-U-ABORT ind

6582 On receipt of a TC-U-ABORT indication carrying a MAP-abort PDU, the MAP PM shall issue a MAP-P-ABORT 6583 indication primitive, with the appropriate value of the provider-reason parameter. The source parameter shall indicate 6584 "MAP-provider". 6585 All state machines associated with the dialogue are returned to idle.

400

3GPP

401 Release 1998

202

3GPP TS 09.02 V7.15.0 (2004-03)

6586

15.6 Procedures for MAP specific services

6587 This subclause describes the MAP procedures for MAP specific services. 6588 These procedures are driven by the following types of events: 6589 6590

a MAP specific request or a MAP specific MAP response primitive; a component handling primitive from TC.

6591 A Service State Machine is activated on receipt of one of the following signals: 6592 6593

a MAP request primitive, which activates a requesting SSM; a TC-INVOKE indication primitive without linked identifier, which activates a responding SSM.

6594 For component handling primitives there are two types of events: 6595 6596 6597 6598

events which activate a Service State Machine or which can be related to an existing one; The procedure elements driven by these events are described in subclauses 15.6.1 to 15.6.4.

events which cannot be related to a Service State Machine. The procedure elements driven by these events are described in subclause 15.6.5.

6599

15.6.1 Service invocation


On receipt of a MAP request primitive, the MAP PM shall build an operation argument from the parameters received in the request primitive and request the invocation of the associated operation using the TC-INVOKE procedure. If a linked ID parameter is inserted in the primitive this indicates a child service and implies that the operation on which the service is mapped is linked to the operation on which the parent service is mapped.

6600 The MAP specific procedures are initiated by the MAP request primitives. 6601 6602 6603 6604

6605 The mapping of MAP specific services on to remote operations is given in table 16.2/1.

6606

15.6.2 Service invocation receipt


if the invoke ID is already in use by an active service, request the transfer of a reject component using the TC-UREJECT request primitive with the appropriate problem code (duplicated invokeID) and issue a MAP-NOTICE indication primitive with a diagnostic parameter set to "abnormal event received from the peer"; if the operation code does not correspond to an operation supported by the application-context, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized operation), and -if the dialogue version is lower than 3- issue a MAP-NOTICE indication primitive with a diagnostic parameter set to abnormal event received from the peer; if a linked ID is included, perform the following checks: If the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to a permitted linked operation, issue a TCU-REJECT request primitive with the appropriate problem code (linked response unexpected or unexpected linked operation); if the type of the argument is not the one defined for the operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter), and issue a MAP-NOTICE indication primitive with a diagnostic parameter set to "abnormal event from the peer"; if the type of the argument is correct but the values of the information elements it contains do not permit the type of MAP service being invoked to be determined, request the transfer of an error component using the TC-UERROR request primitive with an error code set to "unexpected data value" and issue a MAP-NOTICE indication primitive with a diagnostic parameter set to "abnormal event from the peer";

6607 On receipt of a TC-INVOKE indication primitive, the MAP PM shall: 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625

402

3GPP

403 Release 1998

203

3GPP TS 09.02 V7.15.0 (2004-03)

6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641

NOTE 1: These checks are only relevant when there is not a one-to-one mapping between a service and an operation. if the type of the argument is correct but information elements required for the service being invoked are missing, request the transfer of an error component using the TC-U-ERROR request primitive with an error code set to "data missing" and issue a MAP-NOTICE indication primitive with a diagnostic parameter set to "abnormal event from the peer";

NOTE 2: These checks are only relevant when there is not a one-to-one mapping between a service and an operation. if the type of the argument is correct but contains information elements which are not relevant for the type of MAP service being invoked, request the transfer of an error component using the TC-U-ERROR request primitive with an error code set to "unexpected data value" and issue a MAP-NOTICE indication primitive with a diagnostic parameter set to "abnormal event from the peer";

NOTE 3: These checks are only relevant when there is not a one-to-one mapping between a service and an operation. Otherwise, issue the relevant MAP indication primitive to the MAP-service-user. If the service is to be user confirmed, the MAP PM waits for the corresponding response primitive.

6642

15.6.3 Service response


if no error indication is included in the primitive and the service maps on to a class 1 or 3 operation, construct a result information element from the parameters received and request its transfer using the TC-RESULT-L service and optionally the TC-RESULT-NL service.

6643 For user confirmed services, the MAP PM shall accept a MAP response primitive and shall: 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666

The TC-RESULT-NL services shall be used when the user specific parameters of the response primitives cannot be transferred in a single signalling frame and no segmenting mechanism is available from the underlying layers. The MAP PM shall issue one or several TC-RESULT-NL request primitives followed by a TC-RESULT-L primitive. The user parameters shall be split so that each portion contains sufficient information to construct a value compatible with the type defined for the result of the associated operation. if no error indication is included in the primitive and the service response maps on to a class 4 linked operation, construct an operation argument from the parameters received and request its transfer using the TC-INVOKE service for this class 4 linked operation. The operation to be invoked is deduced from the value of the result parameter of the service primitive; if an error indication is included in the primitive and the service maps on to a class 1 or 2 operation, either issue a TC-U-REJECT request primitive if the user error parameter indicates "resource limitation" or "initiating release", or construct an error parameter from the parameters received and request its transfer using the TC-UERROR request primitive. The error code should be the one associated with the value of the user error parameter of the response primitive. The only user errors that a MAP user can generate in addition to the list of errors attached to the operation which is associated with the service are: resource limitation and initiating release. Any other abnormal situation is detected either by the TC entity or by the MAP entity.

NOTE:

if an error indication is received and the operation maps on to a class 3 operation, or if no error indication is received but the service maps on to a class 2 operation which has no class 4 linked operation, return the local service state machine to idle without requesting any service from TC.

6667
6668 6669 6670 6671 6672

15.6.4 Receipt of a response


A component handling indication primitive is considered as driving a response for a confirmed service if the invoke ID parameter value matches the one stored for the service, or if the linked ID parameter value matches the one stored for the service and the operation invoked is a class 4 operation. On receipt of a response (except a TC-L-CANCEL indication) for an unconfirmed service the MAP PM shall issue a MAP-NOTICE indication primitive with the appropriate provider error (return result unexpected or return error unexpected).

404

3GPP

405 Release 1998

204

3GPP TS 09.02 V7.15.0 (2004-03)

6673 15.6.4.1
6674 6675 6676 6677 6678

Receipt of a TC-RESULT-NL indication

If the type of the partial result parameter is not compatible with the one defined for the complete result of this operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter) and issue a confirm primitive with the provider error parameter set to "invalid response received". The MAP PM shall also issue a TC-U-CANCEL request primitive so that all subsequent result components for this operation are discarded by TC.

6679 Otherwise, store the value of the partial result parameter and wait for subsequent TC-RESULT-NL indication primitives 6680 until a TC-RESULT-L indication primitive is received.

6681 15.6.4.2

Receipt of a TC-RESULT-L indication

6682 If the type of the result parameter is not the one defined for the result of this operation, request the transfer of a reject 6683 component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter), and 6684 issue a confirm primitive with the provider error parameter set to "invalid response received". 6685 If the type of the result parameter is correct but does not contain all the information elements required by the service 6686 associated with the invocation, issue a confirm primitive with the provider error parameter set to "invalid response 6687 received". 6688 6689

NOTE 1: These checks are only relevant when there is not a one-to-one mapping between a service and an operation.

6690 If the type of the result parameter is correct but contains information elements which are not relevant for the service 6691 associated with the invocation are missing, issue a confirm primitive with the provider error parameter set to "invalid 6692 response received". 6693 6694

NOTE 2: These checks are only relevant when there is not a one-to-one mapping between a service and an operation.

6695 Otherwise, issue a MAP confirm primitive to the MAP-service-user mapping the result parameter of the TC-RESULT6696 L primitive on to the MAP specific parameters. 6697 If partial results have been previously received, the value of the partial result parameters shall also be taken into account 6698 before performing the three previous checks.

6699 15.6.4.3
6700 6701 6702 6703

Receipt of a TC-U-ERROR indication

If the error code is not defined for the MAP or is not one associated with the operation referred to by the invoke identifier, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized error or unexpected error), and issue a confirm primitive with the provider error parameter set to "invalid response received".

6704 If the type of the error parameter is not the one defined for this error, request the transfer of a reject component using 6705 the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter), and issue a confirm 6706 primitive with the provider error parameter set to "invalid response received". 6707 If the type of the error parameter is correct but does not contain all the information elements required by the service 6708 associated with the invocation, issue a confirm primitive with the provider error parameter set to "invalid response 6709 received". 6710

NOTE 1: In some cases, it may be necessary to analyse the operation argument.

6711 If the type of the error parameter is correct but its value includes information elements which are not relevant for the 6712 service associated with the invocation, issue a confirm primitive with the provider error parameter set to "invalid 6713 response received". 6714

NOTE 2: In some cases, it may be necessary to analyse the operation argument.

6715 Otherwise, issue a MAP confirm primitive to the MAP-service-user with the user error parameter set according to the 6716 received error code. If applicable the error parameter is mapped to the diagnostic parameter.

406

3GPP

407 Release 1998

205

3GPP TS 09.02 V7.15.0 (2004-03)

6717 15.6.4.4
6718 6719 6720 6721

Receipt of a TC-INVOKE indication

A TC-INVOKE indication primitive is considered as carrying a possible response to a specific service if the linked ID refers to an active specific service and the associated operation is a class 4 operation. Note that the presence of a linked ID parameter in a TC-INVOKE primitive requesting a non class 4 operation indicates a child service whose procedures are the same as the procedures for the parent service.

6722 On receipt of a TC-INVOKE indication confirming an active service, the MAP PM shall: 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733

if the operation code is not defined for MAP and the dialogue version is at least 3, issue a TC-U-REJECT request primitive with the appropriate problem code (unrecognized operation). if the operation code is not defined for MAP and the dialogue version is lower than 3, or if the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to an allowed linked operation, issue a TC-U-REJECT request primitive with the appropriate problem code (unrecognized operation, linked response unexpected or unexpected linked operation). If the service is confirmed, the MAP shall also issue a Confirm primitive with provider error indication "unexpected response from the peer", otherwise it may issue a MAP-NOTICE indication primitive with an appropriate diagnostic "abnormal event received from the peer". otherwise issue a confirm primitive mapping the operation argument parameter to the user specific parameters and setting the result parameter according to the operation code of the linked operation.

6734 15.6.4.5

Receipt of a TC-U-REJECT indication

6735 On receipt of a TC-U-REJECT indication primitive which affects a pending service, the MAP PM shall issue a MAP 6736 confirm primitive to the MAP-service-user with the appropriate value of the provider error or user error parameter. 6737 The mapping of TC invoke problem codes on to MAP Provider Error and MAP User Error parameter values is 6738 described in clause 16.

6739 15.6.4.6

Receipt of a TC-L-REJECT indication

6740 This event occurs when the local TC detects a protocol error in an incoming component which affects an active specific 6741 service. 6742 On receipt of a TC-L-REJECT indicating "return result problem, unexpected return result", the MAP shall issue a 6743 confirm primitive with the parameter provider error indicating "unexpected response from the peer". 6744 On receipt of a TC-L-REJECT indicating "return error problem, unexpected error result", the MAP shall issue a confirm 6745 primitive with the parameter provider error indicating "unexpected response from the peer". 6746 Note that when the problem code indicates a general problem, it is considered that the event cannot be related to an 6747 existing SSM even if the invoke Id is provided by TC. This is because whether the invoke Id refers to a local or remote 6748 invocation is ambiguous. The behaviour of the MAP PM in such a case is described in subclause 15.6.5.3.

6749 15.6.4.7
-

Receipt of a TC-L-CANCEL indication

6750 On receipt of a TC-L-CANCEL indication, the MAP PM shall: 6751 6752 6753 6754 6755 6756 6757 6758

if the associated operation is a class 1 operation, issue a confirm primitive with the provider error cause indicating "no response from the peer"; if the associated operation is a class 2 operation and no linked operations are defined for this operation, issue a confirm primitive without parameter (i.e. indicating implicitly the successful completion of the service); if the associated operation is a class 2 operation and has linked operations but none of them has been invoked, issue a confirm primitive with the provider error parameter indicating "service completion failure"; if the associated operation is a class 2 operation and a linked operation invocation has already been received in response to this operation, ignore the primitive;

408

3GPP

409 Release 1998

206

3GPP TS 09.02 V7.15.0 (2004-03)

6759 6760 6761 6762 6763 6764 6765 6766

if the associated operation is a class 3 operation, issue a confirm primitive with the provider error cause indicating "service completion failure"; if the associated operation is a class 4 operation, ignore the primitive. When a TC-L-CANCEL ind primitive is received before the dialogue has been confirmed (i.e. no backward message is received by the dialogue initiator node), the MAP PM shall first issue a MAPOPEN Cnf primitive with the result parameter indicating "accepted" (which means that the dialogue is considered as being implicitly accepted). Then, as indicated above, the TC-L-CANCEL Indication is interpreted according to the class of the operation to which it refers.

NOTE:

6767 15.6.4.8

Receipt of a TC-NOTICE indication

6768 If a TC-NOTICE indication primitive is received before the dialogue has been confirmed (i.e. no backward message is 6769 received by the dialogue initiator node), the MAP PM shall issue a MAP-OPEN Cnf primitive with the result parameter 6770 indicating Refused and a refuse reason Remote node not reachable. 6771 If a TC-NOTICE indication primitive is received after the dialogue has been confirmed, the MAP PM shall issue a 6772 MAP-NOTICE indication to the user, with a problem diagnostic indicating "message cannot be delivered to the peer".

6773
6774 6775 6776 6777

15.6.5 Other events


This subclause describes the behaviour of the MAP PM on receipt of a component handling indication primitive which cannot be related to any service or which does not affect a pending one. The MAP user is only informed that an abnormal event occurred during the associated dialogue. It is up to the MAP user to abort, continue or terminate the dialogue.

6778 15.6.5.1

Receipt of a TC-U-REJECT

6779 On receipt of a TC-U-REJECT indication primitive which does not affect an active SSM (i.e. indicating a return result 6780 or return error problem), the MAP PM shall issue a MAP-NOTICE indication primitive with the diagnostic parameter 6781 set to "response rejected by the peer". 6782 This is also applicable for invoke problems related to a class 4 linked operation.

6783 15.6.5.2

Receipt of a TC-R-REJECT indication

6784 On receipt of a TC-R-REJECT indication (i.e. when a protocol error has been detected by the peer TC entity) which 6785 does not affect an active SSM, the MAP PM shall either discard this indication or issue a MAP-NOTICE indication 6786 primitive with the provider error indicating "abnormal event detected by the peer". 6787 In case of notification, it is up to the MAP user to continue, abort or terminate the dialogue. Note also that for MAP V1 6788 the reject component is received in an END message and therefore the dialogue is terminated anyway.

6789 15.6.5.3

Receipt of a TC-L-REJECT indication

6790 On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) 6791 which cannot be related to an active SSM, the MAP PM shall either discard this indication or issue a MAP-NOTICE 6792 indication primitive with the provider error indicating "abnormal event received from the peer". 6793 In case of notification, it is up to the MAP user to continue, or to terminate the dialogue and implicitly trigger the 6794 transmission of the reject component or to abort the dialogue.

6795

15.6.6 Parameter checks

6796 As described in the previous subclauses, the MAP PM performs a set of checks to ensure the correctness of the 6797 information elements received; these are: 6798

check if the syntax and encoding (note) of the operation argument, result or error parameter are correct.

410

3GPP

411 Release 1998

207

3GPP TS 09.02 V7.15.0 (2004-03)

6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810

NOTE:

Depending on the implementation, encoding problems on the TC user portion may be detected at TC level or by the MAP user. In the second case the problem is reported in a similar manner to a syntactical problem.

The syntax shall be considered incorrect if a mandatory information element is missing in any constructed element or if the value of an information element is out of the range defined for the type it is supposed to belong to; if there is not a one-to-one mapping between a service and an operation: i) check if the value of the information elements (generally a single one) permits the MAP PM to determine the service associated with the operation invocation; ii) check that there are no information elements which are irrelevant for the indication or a confirm primitive to be issued; check if all the information elements required to built an indication or a confirm primitive are available.

6811 However some additional checks may have to be performed by the MAP user (see clause 18).

6812

15.6.7 Returning state machines to idle

6813 Unlike TC invocation state machines, service state machines exist at both requestor and performer side. 6814 A service state machine at the requestor side is returned to idle when the MAP-specific confirm primitive is issued or 6815 when the dialogue terminates. 6816 A service state machine at the performer side is returned to idle on receipt of a MAP-specific response primitive from 6817 the MAP user, when the dialogue terminates or at expiry of an implementation dependent watch-dog timer which is 6818 started when the state machine is created.

6819

15.6.8 Load control

6820 As stated in the previous subclauses, before issuing a MAP-OPEN indication primitive the MAP PM performs a check 6821 to verify if there are sufficient resources to open the dialogue taking into account possible overload conditions. 6822 The decision is based on the priority allocated to the application-context whose name is explicitly included in the TC6823 BEGIN indication primitive or implied by the first operation invocation when V1 contexts are in use. How a V1 6824 application-context-name is derived from an operation code is described in table 15.1/1. 6825 The priority level allocated to each application-context is described in clause 3 tables 5.1/1 and 5.1/2.

6826 6827

16

Mapping on to TC services
16.1 Dialogue control

6828 Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP 6829 PM.

6830

16.1.1 Directly mapped parameters

6831 The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the 6832 corresponding parameters of the TC-BEGIN primitives: 6833 6834

destination address; originating address.

412

3GPP

413 Release 1998

208

3GPP TS 09.02 V7.15.0 (2004-03)

6835 6836 16.1.2.1

16.1.2 Use of other parameters of dialogue handling primitives


Dialogue Id

6837 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

6838 16.1.2.2

Application-context-name

6839 The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of 6840 TC dialogue handling primitives according to the rules described in subclause 15.1.

6841 16.1.2.3

User information

6842 The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs.

6843 16.1.2.4

Component present

6844 This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP 6845 user.

6846 16.1.2.5

Termination

6847 The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method 6848 parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE 6849 INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end".

6850 16.1.2.6
6851 6852 6853 6854 6855

P-Abort-Cause

Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the MAP-PABORT indication primitive according to table 16.1/1, except in the dialogue initiated phase for the "incorrectTransactionPortion" and "noCommonDialoguePortion" values which are mapped to the "potential incompatibility problem" value of the refuse-reason parameter of the MAP-OPEN cnf primitive. The source parameter in the MAP-P-ABORT ind takes the value "TC problem".

6856 16.1.2.7
-

Quality of service

6857 The quality of service of TC request primitives is set by the MAP as shown below. 6858 6859 6860 6861 6862 6863

Return option: "Return message on error" or "Discard message on error" as required by the network operator; Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the network operator; "Sequence guaranteed" shall be used when a segmented result is to be transferred (e.g. subscriber data in response to SendParameters). It may also be appropriate to use Sequence guaranteed when a series of InsertSubscriberData, ProcessAccessSignalling or ForwardAccessSignalling operations is used.

6864 It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue 6865 initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue 6866 responder shall ensure that this requirement is met by: 6867 6868 6869 6870

Sending the dialogue acceptance message in a TC-END, if the dialogue structure requires it; or Using "Sequence guaranteed", if the dialogue acceptance message is sent in a TC-CONTINUE; or Waiting until the dialogue acceptance message has been acknowledged by the dialogue initiator before sending a subsequent message, if the dialogue acceptance message is sent in a TC-CONTINUE.

414

3GPP

415 Release 1998

209

3GPP TS 09.02 V7.15.0 (2004-03)

6871 6872

Table 16.1/1: Mapping of P-Abort cause in TC-P-ABORT indication on to provider-reason in MAP-P-ABORT indication
TC P-Abort cause MAP provider-reason unrecognized message type provider malfunction unrecognized transaction Id supporting dialogue released badlyFormattedTransactionPortion provider malfunction incorrectTransactionPortion provider malfunction (note) resourceLimitation resource limitation abnormalDialogue provider malfunction noCommonDialoguePortion version incompatibility NOTE: Or version incompatibility in the dialogue initiated phase.

6873

6874

16.2 Service specific procedures


16.2.1 Directly mapped parameters

6875 Specific services are mapped to TC component handling services.

6876

6877 The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter 6878 of the component handling primitives.

6879 6880 16.2.2.1

16.2.2 Use of other parameters of component handling primitives


Dialogue Id

6881 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

6882 16.2.2.2

Class

6883 The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.

6884 16.2.2.3
6885 6886 6887 6888

Linked Id

When a service response is mapped to a class 4 operation, the value of this parameter is set by the MAP PM and corresponds to the value assigned by the user to the initial service request (i.e. the value of the invoke ID parameter of the request primitive). Otherwise if such a parameter is included in MAP request/indication primitives it is directly mapped to the linked ID parameter of the associated TC-INVOKE request/indication primitives.

6889 16.2.2.4

Operation

6890 When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code 6891 according to the mapping described in table 16.2/1. 6892 When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the 6893 TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time.

416

3GPP

417 Release 1998

210

3GPP TS 09.02 V7.15.0 (2004-03)

6894

Table 16.2/1: Mapping of MAP specific services on to MAP operations


MAP-SERVICE MAP-ACTIVATE-SS MAP-ACTIVATE-TRACE-MODE MAP-ALERT-SERVICE-CENTRE MAP-ANY-TIME-INTERROGATION MAP-CANCEL-LOCATION MAP-CHECK-IMEI MAP-DEACTIVATE-SS MAP-DEACTIVATE-TRACE-MODE MAP-DELETE-SUBSCRIBER-DATA MAP-ERASE-CC-ENTRY MAP-ERASE-SS MAP-FAILURE-REPORT MAP-FORWARD-ACCESS-SIGNALLING MAP-FORWARD-CHECK-SS-INDICATION MAP-FORWARD-GROUP-CALL-SIGNALLING MAP-MT-FORWARD-SHORT-MESSAGE MAP-MO-FORWARD-SHORT-MESSAGE MAP-GET-PASSWORD MAP-INFORM-SERVICE-CENTRE MAP-INSERT-SUBSCRIBER-DATA MAP-INTERROGATE-SS MAP-NOTE-MS-PRESENT-FOR-GPRS MAP-PREPARE-GROUP-CALL MAP-PREPARE-HANDOVER MAP-PREPARE-SUBSEQUENT-HANDOVER MAP-PROCESS-ACCESS-SIGNALLING MAP-PROCESS-GROUP-CALL-SIGNALLING MAP-PROCESS-UNSTRUCTURED-SS-REQUEST MAP-PROVIDE-ROAMING-NUMBER MAP-PROVIDE-SIWFS-NUMBER MAP-PROVIDE-SUBSCRIBER-LOCATION MAP-PROVIDE-SUBSCRIBER-INFO MAP-PURGE-MS MAP-READY-FOR-SM MAP-REGISTER-CC-ENTRY MAP-REGISTER-PASSWORD MAP-REGISTER-SS MAP-REMOTE-USER-FREE MAP-REPORT-SM-DELIVERY-STATUS MAP-RESET MAP-RESTORE-DATA MAP-SEND_GROUP-CALL_END_SIGNAL MAP-SEND-END-SIGNAL MAP-SEND-AUTHENTICATION-INFO MAP-SEND-IMSI MAP-SEND-IDENTIFICATION MAP-SEND-ROUTING-INFO-FOR-SM MAP-SEND-ROUTING-INFO-FOR-GPRS MAP-SEND-ROUTING-INFO-FOR-LCS MAP-SEND-ROUTING-INFORMATION MAP-SET-REPORTING-STATE MAP-SIWFS-SIGNALLING-MODIFY MAP-STATUS-REPORT MAP-SUBSCRIBER-LOCATION-REPORT MAP-SUPPLEMENTARY-SERVICE-INVOCATIONNOTIFICATION MAP-UNSTRUCTURED-SS-NOTIFY MAP-UNSTRUCTURED-SS-REQUEST MAP-UPDATE-GPRS-LOCATION MAP-UPDATE-LOCATION operation activateSS activateTraceMode alertServiceCentre anyTimeInterrogaton cancelLocation checkIMEI deactivateSS deactivateTraceMode deleteSubscriberData eraseCC-Entry eraseSS failureReport forwardAccessSignalling forwardCheckSsIndication forwardGroupCallSignalling mt-forwardSM mo-forwardSM getPassword informServiceCentre insertSubscriberData interrogateSs noteMsPresentForGprs prepareGroupCall prepareHandover prepareSubsequentHandover processAccessSignalling processGroupCallSignalling processUnstructuredSS-Request provideRoamingNumber provideSIWFSNumber provideSubscriberLocation provideSubscriberInfo purgeMS readyForSM registerCC-Entry registerPassword registerSS remoteUserFree reportSmDeliveryStatus reset restoreData sendGroupCallEndSignal sendEndSignal sendAuthenticationInfo sendIMSI sendIdentification sendRoutingInfoForSM sendRoutingInfoForGprs sendRoutingInfoForLCS sendRoutingInfo setReportingState SIWFSSignallingModify statusReport subscriberLocationReport ss-Invocation-Notification unstructuredSS-Notify unstructuredSS-Request updateGprsLocation updateLocation

6895

418

3GPP

419 Release 1998

211

3GPP TS 09.02 V7.15.0 (2004-03)

6896 16.2.2.5

Error

6897 The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm 6898 primitive of the service associated with the operation to which the error is attached. 6899 The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request 6900 primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of 6901 the TC-U-REJECT request primitive.

6902 16.2.2.6

Parameters

6903 The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC6904 INVOKE primitives. 6905 The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L 6906 primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on 6907 linked class 4 operations is used.

6908 16.2.2.7

Time out

6909 The value of this parameter is set by the MAP PM according to the type of operation invoked.

6910 16.2.2.8

Last component

6911 This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP 6912 user.

6913 16.2.2.9 6914 16.2.2.9.1

Problem code
Mapping to MAP User Error

6915 The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. 6916 These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the 6917 MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive. 6918 6919

Table 16.2/2: Mapping of MAP User Error parameter on to TC problem code in TC-U-REJECT primitives
MAP User Error resource limitation initiating release TC problem code resource limitation initiating release

6920

6921 16.2.2.9.2

Mapping to MAP Provider Error parameter

6922 The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as 6923 follows to values of the MAP Provider Error parameter of the MAP confirm primitive. 6924 6925

Table 16.2/3: Mapping of TC problem code in TC-U-REJECT on to MAP Provider Error parameter
TC problem code duplicated invoke Id unrecognized operation mistyped parameter MAP Provider Error duplicated invoke id service not supported mistyped parameter

6926 6927 The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the 6928 provider error parameter of the MAP confirm primitive as follows:

420

3GPP

421 Release 1998

212

3GPP TS 09.02 V7.15.0 (2004-03)

6929 6930

Table 16.2/4: Mapping of TC problem code in TC-L-REJECT on to MAP Provider Error parameter
TC problem code return result unexpected return error unexpected MAP Provider Error unexpected response from the peer unexpected response from the peer

6931

6932 16.2.2.9.3

Mapping to diagnostic parameter

6933 The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to 6934 values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: 6935 6936

Table 16.2/5: Mapping of TC problem code of TC-R-REJECT and TC-U-REJECT on to diagnostic parameter
TC problem code General problem abnormal event detected by the peer Invoke problem - unrecognized linked ID - linked response unexpected - unexpected linked operation Return result problem - unrecognized invoke ID - return result unexpected - mistyped parameter Return error problem - unrecognized invoke ID - return error unexpected - unrecognized error - unexpected error - mistyped parameter MAP diagnostic

- abnormal event detected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer

6937 6938 The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the 6939 diagnostic parameter of the MAP-NOTICE indication primitive as follows: 6940

Table 16.2/6: Mapping of TC problem code of TC-L-REJECT on to diagnostic parameter


TC problem code General problems: Invoke problem: - unrecognized linked ID Return result problem: - unrecognized invoke ID Return error problem: - unrecognized invoke ID MAP diagnostic - abnormal event received from the peer - abnormal event received from the peer - abnormal event received from the peer - abnormal event received from the peer

6941

6942

16.3 SDL descriptions

6943 The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. 6944 Such a system resides in each network component supporting MAP and communicates with its peers via the lower 6945 layers of the signalling network which are part of the environment. 6946 Only the MAP-provider is fully described in this subclause. The various type of processes which form the MAP-User 6947 block and the TC block are described respectively in clauses 18 to 25 of the present document and in CCITT 6948 Recommendation Q.774. 6949 The MAP-Provider block communicates with the MAP_USER via two channels U1 and U2. Via U1 the MAP-provider 6950 receives the MAP request and response primitives. Via U2 it sends the MAP indication and confirm primitives.

422

3GPP

423 Release 1998

213

3GPP TS 09.02 V7.15.0 (2004-03)

6951 The MAP-Provider block communicates with TC via two channels P1 and P2. Via P1 the MAP-Provider sends all the 6952 TC request primitives. Via P2 it receives all the TC indication primitives. 6953 The MAP-Provider block is composed of the four following types of processes: 6954 6955 6956 6957 6958 6959 6960 6961

a) MAP_DSM: This type of process handles a dialogue. There exists one process instance per MAP dialogue. b) LOAD_CTRL: This type of process is in charge of load control. There is only one instance of this process in each system. c) PERFORMING_MAP_SSM: This type of process handle a MAP service performed during a dialogue. An instance of this process is created by the instance of the MAP_DSM process for each MAP-service to be performed. d) REQUESTING_MAP_SSM: This type of process handle a MAP service requested during a dialogue. An instance of this process is created by the instance of the MAP_DSM process for each requested MAP-service.

6962 A process MAP_DSM exchanges external signals with other blocks as well as internal signals with the other processes 6963 of the MAP-Provider block. The external signals are either MAP service primitives or TC service primitives. 6964 The signal routes used by the various processes are organized as follows: 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980

a) A process MAP_DSM receives and sends events from/to the MAP_user via signal route User1/User2. These routes uses respectively channel U1 and U2. b) A process MAP_DSM receives and sends events from/to the TC via signal route Tc1/Tc2. These routes uses respectively channel P1 and P2. c) A process MAP_DSM receives and sends events from/to the LOAD_CTRL process via signal route Load1/Load2. These routes are internal. d) A process MAP_DSM sends events to the PERFORMING_MAP_SSM processes via signal route Intern1. This route is internal. e) A process MAP_DSM sends events to the REQUESTING_MAP_SSM processes via signal route Intern2. This route is internal. f) A process MAP_PERFORMING_SSM sends events to the MAP_USER via signal route User4. This route uses channel U2. g) A process MAP_PERFORMING_SSM sends events to TC via signal route Tc3. This route uses channel P1. h) A process MAP_REQUESTING_SSM sends events to the MAP_USER via signal route User5. This route uses channel U2. j) A process MAP_REQUESTING_SSM sends events to TC via signal route Tc4. This route uses channel P1.

424

3GPP

425 Release 1998

214

3GPP TS 09.02 V7.15.0 (2004-03)

0 9 .0 2 ve rs io n 6 .6 .0

System MAP_STACK
F ig u re 1 6. 2 /1 :

16.2_1(1)

M AP_USER
U2

(MAP_R EQ _SM) MAP_IN D_SP


U1

MAP_ PRO VIDER TC _REQ _SP

P2

TC_IND _SP
P1

TC AP

6981
6982

Figure 16.2/1: System MAP_STACK

426

3GPP

427 Release 1998

215

3GPP TS 09.02 V7.15.0 (2004-03)

B lo c k M A P P R O V ID E R
F i g u r e 1 6 .1 /2 :

1 6 .2_ 2 (1 )

TC 2 TC 1 U S ER 1 LO AD 2 L O AD 1 LOA D_C T RL M A P_ D SM

US E R2

IN T E R N 2

IN T E R N 1 P ER F O R M IN G _M AP _ SS M

T C3 US E R4

U S ER 5

T C4 R E Q U ES T IN G _M AP _ SS M

6983
6984

Figure 16.2/2: Block MAPPROVIDER

428

3GPP

429 Release 1998

216

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2 _3.1(11 )

C o m m en t ' MA P D ialo g es S ta te Ma s c hin e': DC L CO M P O N E N T S _ P R E S E N T , IN V O K E ID _ A C T IV E , LA S T _C O MP O N E N T , O P _ E X IS T B O O LE A N , O P _C O D E IN T E G E R ;

ID L E

ID L E

M AP_OPEN _ RE Q

S to re _ A C _ a nd _ u se r_d a ta

W A IT _F O R _ U SE R _ R E Q U E S T S

6985
6986

Figure 16.2/3 (sheet 1 of 11): Process MAP_DSM

430

3GPP

431 Release 1998

217

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2 _3.2(11 )

W A IT _F O R _ IN IT _D A T A

W A IT _ L O A D_ CH E C K _ RE S U L T2

T C _ IN V O K E _ IN D (O P _ C O D E )

T C _L _ R E J E C T A N Y _O T H ER _ IN D IN D

LOAD _OK

OVER LOAD

op e ra tio n _ exist s y es D e rive_ V 1_ A C

no

o pe ratio n _ c od e

ELSE

be g in_ su b s c rib er _ac tiv ity C H E C K _L O A D _ V IA _ LO A D 1 T C _U _ A B OR T _ RE Q _ V IA _ T C 1 las t_ c om p o n en t yes no

W A IT _ LO A D _ CH ECK_ R E S U L T2

'B u ild _ M A P -O P E N _ In d _p rim it ive '

T C -U -A B O R T _ R E Q _V IA _ TC 1

M A P -O P E N _IN D _V IA _ US E R 2

P erfo rm_ v ers io n _1 _ p ro to c o l

6987
6988

Figure 16.2/3 (sheet 2 of 11): Process MAP_DSM

432

3GPP

433 Release 1998

218

3GPP TS 09.02 V7.15.0 (2004-03)

Pro ce ss MA P_D SM
ID L E F ig u re 1 6. 2 /3 : T C _ B E G IN _ In d

W A IT _F O R _ L O A D _C H E C K _ R E S U LT 1

16.2 _3.3(11 )

LO AD_OK AC _ in c lu de d ye s A C of ve rs io n _1 ye s E xtra c t us er in form at io n AC_ s up p o rted ye s A C _n am e := R e c eiv e d_ A C _ n am e no

OVER LOAD

no U se r_ in fo rm atio n in c lu d ed no y es

no

no

A lte rn a tive _ na m e_ ex is ts y es

M A P -O P E N dia lo g ue P D U ye s no

no

inv alid _ p aram ete r ye s

S et_ u se r_d a ta

A C _ n am e := R e c eiv ed _ A C _ na m e

S et_ A C _ na m e := A lte rn a tiv e_ na m e

CH E C K _ L O A D _V IA _ L O A D 1

M A P _ O P E N _ IN D _ V IA _ U S E R 2

W A IT _F O R _ LO A D _ C H E C K _ R ES U L T 1 U se r_inf o _ req u ired _ fo r_A C no ye s

C om p o n en ts _ p res en t ye s M A P -P ro v ide r_ Ab o rtR ea so n := ab no rm alD ia lo gu e Se t U s er_ in fo := M A P -P ro vide r _A b o rtIn fo S et A b o rt_ re as o n := U s er_ sp e c ific no C om p o n en ts _ p res en t ye s PR OC ESS_ C O MP O NE N TS

no

A b o rt _rea s on := A C _ n ot_ s up p p orte d

MAP_ MAP_ D E LIM IT E R _ D E LIM IT E R _ IN D _ V IA _ U S E R 2IN D _ V IA _U S E R 2

TC _ U_ A B O RT _ R E Q _V IA _ T C 1

C HE C K _ L O A D _V IA _ L O A D 1

T C _U _ A B O R T _ R E Q _ V IA _ T C 1

W A IT _F O R _ LO A D _C H E C K _ R E SULT1

W A IT _F O R _ IN IT _ D A T A

D IA L O G U E _ P E N D IN G

6989
6990

Figure 16.2/3 (sheet 3 of 11): Process MAP_DSM

434

3GPP

435 Release 1998

219

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2 _3.4(11 )

W A IT _ F O R _ US E R _ R E Q UE S T S

an y M A P s pe c ific req ue st p rim itiv

M A P _ RE Q

M AP_ D E LI MIT E R _ REQ

M A P_ U_ A B OR T_ RE Q

RE Q U E S T IN G _M A P _ SSM

S et_ A b o rt_ re as o n = us er_ sp e c ific

S e t_ us e r_ in fo = m ap _ us e r_ A b o rt_ P D U

S E R V IC E _ IN V O K E D _ V IA IN T E R N 2

T C _ B E G IN _ R E Q V IA _ T C 1

TC _ U_ A B O R T_ R E Q _ V IA _T C I

T E R M IN A T E D _ V IA _ IN T E R N 2

to all R S M s

W A IT _ F O R _ US E R _ R E Q UE S T S

D IA L O G U E _ IN IT IA T E D

6991
6992

Figure 16.2/3 (sheet 4 of 11): Process MAP_DSM

436

3GPP

437 Release 1998

220

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 : D IA L O G U E _ IN IT IA T E D

16.2 _3.5(11 )

T C _E N D _ IN D

A C n am e u n c h an g ed ? y es R e su lt := D ialo gu e_ A c c e p ted

no

P ro v id er_re as o n : = A b no rm al_ M A P _ D ialog u e

M A P _O PE N_ CN F_ V IA _U S E R 2

M A P _ P _ A B O R T_ IN D _ V IA _ U S E R 2

C o m po n en ts _ n o p res e nt y es P R O CE S S _ CO M P O N E NT S

M A P _C L O S E _ IN D _ V IA _U S E R 2

T E R MI N A T E D _ all ac tive P S M V IA _ IN T E R N 1

T E R MI N A T E D _ all ac tiv e R S M V IA _ IN T E R N 2

6993
6994

Figure 16.2/3 (sheet 5 of 11): Process MAP_DSM

438

3GPP

439 Release 1998

221

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2 _3.6(11 )

D IA LO G U E _ IN IT IA T ED

TC _ C O N T IN U E _ t h e firs t on e IN D

AC name un c h an g ed ye s S e t_ R e su lt := D ialog u e_ A c c e p ted

no

M A P -P ro vid e r_ A b o rtRe as o n := a bn o rm a lD ialo gu e

M A P _ O P E N_ C N F _ V IA _U S E R 2

ind ic a tin g ' d ialog u e a c c ep ted '

MAP_P_ A B O R T _ IN D _ V IA _ U S E R 2

n C O MP O N E N T S _ o P RE S E NT ye s

A b o rt_R e as o n := U s er_ S pe c ific

P ROC E S S _ CO M P O N E NT S

M A P -P rov id er _ U s er_ In f orm atio n := A b ortR ea s on := M A P _ P rov id er _ ab n orm alD ialo g u e A b o rt_In fo

M A P_ D E L IM IT E R _ In d

T C_U _ A B OR T_ R E Q _ VI A_ T C 1

D IA L O G U E _ E S T A B L IS H E D

6995
6996

Figure 16.2/3 (sheet 6 of 11): Process MAP_DSM

440

3GPP

441 Release 1998

222

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2_3.7(1 1)

D IA L O G U E _ IN IT IA T E D

TC _ U_ A B O R T_ Ind

T C_ P _ A B O R T _ Ind

M A P _U _ A B O R T _ re q

U s er_ S p ec ific A b ort_ R eas o n A C _ N o t_ S u p po rte d S et_ R es ul t := D ia lo g ue_ R e fu se d D ia lo g ue _ R e fu se d

In c o rrec t_ T ra n sa c tio n 'P -ab o rt _ P o rtio n p aram e ter'

E ls e

S et _A b o rt _ R e as on := U s er_ S p ec ific

N o_ U s er_ U s er_ Info rm at ion In fo P ro vid e r_ A b o rt_ U se r_ PD U A b o rt_ PD U

No _ C o m m on _ D ia lo g ue _ P ort ion

S et _U s er_ Info := M A P _ U se r_ A b ort _In fo

S et_ R efu s e_ R ea so n := A C _ N ot _S u p po rted

S et _R es u lt := S e t_P ro v ide r_ D ialo g ue _ R ea so n := V e rs ion R efu s ed _ Inc om p at ibilit y

3 S e t_ R e fu se _ R ea s on := P ot en tia l_ V ers io n _ In c om p at ibilit y M AP_OPEN _ C nf via U S E R 2

in d ic at e 'D ialo g ue _ R efu se d '

M A P _U _ A B O R T _ In d vi a U S E R 2

in d ic a te 'D ia lo gu e_ R efu s ed '

L o c al

M A P _P _ A B O R T _ Ind v ia U S E R 2

M A P_ O P E N _ C n f v ia U S E R 2

M A P _ P _A B O R T _ Ind via U S E R 2

T C _U _ A B O R T _R eq v ia T C 1

6997
6998

Figure 16.2/3 (sheet 7 of 11): Process MAP_DSM

442

3GPP

443 Release 1998

223

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2 _3.8(11 )

D IA L O G U E _ IN IT IA T E D

TC _ N O T IC E _ IN D

MAP_ C LOSE_ REQ

T C_ L _ C A NC E L _ IN D

S et _R es u lt= D ia lo g u e_ R e fu se d

T C _E N D _ REQ_ V IA _ T C 1

p re-a rra ng ed

M AP_OPEN _ C NF _ V IA _U S E R 2

A c c ep t ed . T he dialo g u e is c on s id ere d im plic itly a c c ep te d w h en s o m et hin g is re c eiv ed

S et_ R efu s e_ R ea so n = N od e _N o t_R e ac h ab le

IN V O K E ID _ A C T IV E TRU E

F ALSE

M AP_OPEN _ C NF_ V IA _U S E R 2

T IM E R _ E X P IR Y_ V IA _ IN T E R N 2

S et _R e su lt := D ialo g u e_ R efu s ed in va lid _d e st ina tion _ MAP_ re fere nc e R e fus e_P D U e rro r in va lid _ orig inat io n_ refe re n c e

D IA L O G U E _ IN IT IA T E D

no _ rea so n _ given S et _R efu s e_ R ea so nS:= t_ R e fu se _ R e as o n := S e t_R e fus e _R e as o n := e in va lid _d e st ina tion _ n o _ rea so n _ in v alid_ o rig ina tio n _ re fere nc e g iven refe ren c e

6999
7000

Figure 16.2/3 (sheet 8 of 11): Process MAP_DSM

444

3GPP

445 Release 1998

224

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2 _3.9(11 )

D IA L O G U E _ P E N D IN G

M AP_OPEN _ RS P

M A P _U _ A B O R T_ RE Q

re fu se d R es ult a c c ep te d U s er_ in fo_ in c lu de d y es B uild _M A P _ A CC E P T_ P D U B u ild _ M A P _ R e fus e _P D U U se r_info := M A P -U se rA b o rtIn fo no A b o rt_ re as o n := U s er_ S p ec ific A b or t_ rea so n := U se r_s p ec ific

T C_ U _ A B O R T _ R EQ _V IA _ T C 1

D IA L O G U E _ A C CE P TE D

7001
7002

Figure 16.2/3 (sheet 9 of 11): Process MAP_DSM

446

3GPP

447 Release 1998

225

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 : D IA LO G U E _ A CC E P T E D

16.2_3.10(11)

M A P _ RE Q

MA P _ R S P

MAP_ C LO S E _ REQ

MAP_ D E L IM E T E R _ RE Q

M A P -U A B OR T_ RE Q A b o rt-res o n := U s er-s p ec ific

R E Q U E S T IN G _ MAP_SSM

an y MA P s pe c ific re q ue st p rimitiv

S E R V IC E _ IN V O K E D _V IA _ IN T E RN 2 D IA L O G U E _ A C C EP T E D

RE S P O N S E _ IS SU E D _V IA _ IN T E R N 1 D IA LO G U E _ A CC E P T E D

TC _ E N D_ R E Q V IA _ T C 1

TC _ C O N T IN U E _ R E Q _ V IA _T C 1

U se r- inf o := MAPU se rA b o rtIn fo T C -U A B O RT _ RE Q _V IA _ T C 1

D IA L O G U E _ E S T A B LIS H E D

a n y M A P sp e c ific re sp o n s e p rim itiv D IA L O G U E _ E S T A B L IS H E D

TC _ C O N T IN U E _ IN D

T C _E N D _ IN D

T C _U _ A B O RT _ IN D

TC _ P _ A BO R T_ IN D

C o m po n en ts _ p re se n t y es

no

no CO M P O NE N TS _ P RE S E NT ye s PR OC ESS_ C O MP O NE NTS

u s er_ ab o rt_P D U U s er_ in fo pro v ide r_ ab o rt _P D U

P RO CE S S _ C O M P O N E NT S

MAP_ D E LIM IT E R _ IN D _ V IA _U S E R 2

M A P _ C LO S E _IN D _ V IA _ US E R 2

MAP_P_ A B O R T _ IN D _ V IA _U S E R 2

M A P _U _ A B O R T _ IN D _ V IA _U S E R 2

M AP _ P _ A B O R T _ IN D _ V IA _U S E R 2

D IA L O G U E _ E S T A B L IS H E D

7003
7004

Figure 16.2/3 (sheet 10 of 11): Process MAP_DSM

448

3GPP

449 Release 1998

226

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess MA P_D SM


F ig u re 1 6. 2 /3 :

16.2_3.11(11)

D IA L O G U E _ E S T A B L IS H E D

MA P _ R E Q

MA P _ R S P

MAP_ C LO S E _ R EQ

MAP_ D E LIM IT E R _ RE Q

M A P -U A B OR T_ RE Q ' A bo rt- res o n := U s er-sp e c ific '

an y M AP s pe c ific re q ue st p rim itiv e

a ny M A P s p ec ific res p o n se p rim itiv e

R E Q U E S T IN G _ MAP_SSM

'U se r-in fo := MAPU s e rA b o rtIn fo ' RE S P O N S E _ IS SU E D _V IA _ IN T E R N 1 D IA L O G U E E ST A B LIS H E D T C_ E N D_ R EQ_ V IA _ T C 1 TC _ C O N T IN U E _ R E Q _ VI A_ T C 1 D IA L O G U E E S T A B L IS H E D T C -U A BO R T_ R E Q _ V IA _T C 1

S E R V IC E _ IN V O K E D _V IA _ IN T E RN 2 D IA L O G U E E S T A B LIS H E D

D IA L O G U E _ E ST A B LIS H E D

T C _L _ C A N CE L _ IN D IN V O K E _ no ID _A C T IV E ye s

TC _ N O T IC E _ IN D

an d S S M ac tive

T IM E R _ E X P IR Y_ VI A_ IN T E R N 2

MAP_ N O T IC E _ IN D _ V IA _ U S E R _ 2

D IA LO G U E E S T A B LIS H E D

7005
7006

Figure 16.2/3 (sheet 11 of 11): Process MAP_DSM

450

3GPP

451 Release 1998

227

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cedure PRO C ES S_C OMPO NENTS


F ig u re 1 6. 2 /4 :

16.2 _4.1(4)

C om m e nts : C o m p on e nts f rom T C A P : DC L O P _C O D E IN T E R G E R , O P _ E X IS T , L A S T _C O M P O N E N T , IN V O K E ID _A S S , L IN K E D ID _ P R E S , L IN K E D ID _ A S S B O O LE A N ;

W A IT _ F O R _ C O MP O NE NTS

7007
7008

Figure 16.2/4 (sheet 1 of 4): Procedure PROCESS_COMPONENTS

452

3GPP

453 Release 1998

228

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cedure PRO C ES S_C OMPO NENTS


F ig u re 1 6. 2 /4 :

16.2 _4.2(4)

W A IT _F O R _ C O M P O N E NT S

T C _ IN V O K E _ IN D (O P _ C O D E ) IN V O K E ID _ ASS T RU E 2 F ALSE LIN K E D ID _ P RE S TR U E LIN K E D ID _ A SS M A P _N O T IC E _ IN D _ V IA _U S E R 2 TR U E 2 TC _ U_ R E JE C T_ R E Q _V IA _ T C 1 O pe rat io n C las s 1 ,2 ,3 LIN K E D _S E R V IC E _ IN V O K E D _ V IA _ IN T E R N 2 L IN K E D _ R E Q U E S T _ R F O R M IN G _ PE R E C E IV E D _ V IA MAP_SSM IN T E R N 2 S E R V IC E _ IN V O C AT IO N _ R E C E IV E D _V IA _ IN T E R N 1 4 'S et_ p rob le m _ c o de = un rec o g niz ed o pe ration ' TC _ U_ R E J EC T _ R E Q _ V IA _ T C 1 F AL S E F AL S E an d S S M a c tiv e O P _ E X IS T T RU E fo r th is A C

4 F AL S E

v3 D IA LO G U E o r h igh e r f als e T ru e M A P _ N O T IC E IN D _ V IA _U S E R 2 3 L A S T_ CO M P O N E NT T RU E 1 F A L SE 3

7009
7010

Figure 16.2/4 (sheet 2 of 4): Procedure PROCESS_COMPONENTS

454

3GPP

455 Release 1998

229

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cedure PRO C ES S_C OMPO NENTS


F ig u re 1 6. 2 /4 : W A IT _ F O R _ C O M PO N E N T S

16.2 _4.3(4)

TC _ R E SU L T _ L _ IN D

T C_ R E S U LT _ N L _ IN D

T C_ U_ E R RO R _ IN D

IN V O K E ID _ ASS TR U E

FA L S E

IN V O K E ID _ ASS T RU E

FA L S E

IN V O K E ID _ ASS T RU E

FAL S E

R E S UL T_ R E C E IV E D _V IA _ IN T E R N 2

P A R T IA L _ R E S U L T_ R E C E IV E D _ V IA _ IN T E R N 2

N E G A T IV E _ R E S UL T_ R E C E IV E D _V IA _ IN T E R N 2

W A IT _F O R _ C O M P O N E NT S

T C _ U_ R E JE CT_ IN D

T C_R _ R E JE C T_ IN D

P rob lem Typ e =

rr_ p b, re -p b

P ro b lem T yp e =

rr-p b , re_ p b , ge n eral_p b

inv o k e_ pb

in vo k e_ p b

IN V O K E ID _ ASS T RU E

F ALSE

MAP_ N O T IC E _ IN D _ V IA _ U SE R 2

IN V O K E ID _ ASS TR UE

FA L S E

M A P_ N O T IC E _ IN D _ V IA _U S E R 2

U S E R_ R E JE C T_ R E C E IV E D _V IA _ IN T E R N 2

MA P _ N O T IC E _ IN D _ V IA _U S E R 2

P R E V IO U S _ R ES UL T _ R E C EI VE D _ V IA _ IN T E R N 2

MAP_ N O T IC E _IN D _ V IA _U S E R 2

7011
7012

Figure 16.2/4 (sheet 3 of 4): Procedure PROCESS_COMPONENTS

456

3GPP

457 Release 1998

230

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cedure PRO C ES S_C OMPO NENTS


F ig u re 1 6. 2 /4 :

16.2 _4.4(4)

W A IT _ F O R _ CO M P O N E NT S

T C _L _ RE JE C T_ IN D

IN V O K E ID _ n o in c lu de d ye s P ro b le m T y pe = rr_ p b, re _p b , g e ne ral_ p b

in v ok e _p b IN V O K E ID _ ASS TR U E F A LS E

P R O V ID E R _ RE JE C T_ R E C E IV E D _V IA _ IN T E R N 2

M AP_ N O T IC E _ IN D _ V IA _ US E R 2

MAP_ N O T IC E _ IN D _ V IA _ U S E R 2

MAP_ N O T IC E _IN D _ V IA _U S E R 2

7013
7014

Figure 16.2/4 (sheet 4 of 4): Procedure PROCESS_COMPONENTS

458

3GPP

459 Release 1998

231

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess LOA D _C TRL


F ig u re 1 6.2 /5 :

16.2_5(1)

C o m m en t 'L O A D C O N T R O L ' : DC L C O N G E S T IO N , D IA L O G U E _ A C C E P T A B LE B O O L E A N ;

ID L E

ID L E

C H E CK _ LOAD

(F A LS E ) C O N G E S T IO N (T R U E ) ' C o m p are _A C _ p rio rity _w ith _ loa d' LO A D _ O K _ V IA _ LO A D2

D IA L O G U E _ (F A L S E ) A C C E P TA B L E (T R U E ) LOAD _OK_ V IA _ L O A D 2 O V ER L O A D _ V IA _ L O A D 2

ID L E

7015
7016

Figure 16.2/5: Process LOAD_CTRL

460

3GPP

461 Release 1998

232

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess PER FOR MIN G _M AP_SS M


F ig u re 1 6. 2 /6 :

16.2 _6.1(3)

C o m m en t 'M A P S e rv ic e S tat e M a c hin e': DC L A R G U M E N T _ C O R R E C T , U S E R _E R R O R _ P R E S E N T , S P E C IF I C _ E R R O R _ L IN K E D _R E Q U E S T , C N F B O O L E A N , O P _ C L A S S IN T E G E R , T IM E R G U A R D _T IM E R C O MM E N T 'ex pire s if M A P us er d oes no t res po n d' ;

ID L E

7017
7018

Figure 16.2/6 (sheet 1 of 3): Process PERFORMING_MAP_SSM

462

3GPP

463 Release 1998

233

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess PER FOR MIN G _M AP_SS M


ID L E F ig u re 1 6. 2 /6 : S E R V IC E _ IN V O C A T IO N _ R E C E IV E D

16.2 _6.2(3)

( TRU E )

A R G U M E NT _ CO R RE C T (F A LS E ) ( F A LS E )

is th e sy n tax c o rre c t ?

Se rvic e _ c an _ be _ id en tified (T R U E ) S ervic e p aram e te rs av ailab le ? (T R U E )

'S et_ p rob le m _ c o de = M is ty pe d P aram ete r' 'D is c ard _ in vo c a tio n ' T C _U _ R E J E C T _ R E Q _V IA _ T C 3

( F A LS E )

' D isc a rd_ inv o c at ion ' OP_C LASS o p erat io n c la ss a s so c ia ted w it h th e s ervic e ( 3 ,4 ) 4 ( 1,2 ) (3 ,4 )

o pe ra tion c las s as s o c iat ed w ith th e s e rvic e

M AP _ N O T IC E _ IN D _ V IA _U S E R 4

O P _ CL A S S ( 1 ,2 ) 'S et _e rr or= da ta m iss ing '

3 U n exp e c ted _ da ta (T R U E ) (F A L S E ) M A P _I N D _ V IA _U S E R 4

'S et _e rror= u ne xp ec ted da ta va lue '

T C_ U _ E R R O R_ R E Q _ V IA _ T C 3 M A P _ N O T IC E _ IN D _ V IA _U S E R 4

C NF req uire d (T R U E )

(F A L S E )

'D is c a rd _ in v ok a tion '

'S e t_ (G U A R D _ T IM E R )' W A IT _F O R _ R ESPON SE

O P _C L A S S

o p erat ion c las s a ss o c ia ted w it h the s ervic e (3, 4)

( 1 ,2 ) 4

7019
7020

Figure 16.2/6 (sheet 2 of 3): Process PERFORMING_MAP_SSM

464

3GPP

465 Release 1998

234

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess PER FOR MIN G _M AP_SS M


F ig u re 1 6. 2 /6 :

16.2 _6.3(3)

W A IT _F O R _ R ESPON SE

R E SP O N S E _ IS S U ED

by th e M A P u se r

G UA R D_ T IM E R

T E R M INA T E D

U S E R_ E R R OR_ PRESENT (F A L S E ) L IN K E D _ R E Q UE S T (F A L S E ) LE N G T H _ O .K .

(T R U E ) S P EC IF IC _ E RR OR

(T R U E ) 'S e t_ o pera tio n _ c od e_ a nd _ T C A P _ p ar a' (F A LS E ) 'S P L IT _ IN F O ' TC _ IN V O K E _ R E Q _ V IA _ T C 3

(T R U E ) 'S e t_ error_ c od e '

(F A LS E ) 'S et_ p rob le m _ c od e '

(T R U E ) 8

T C_ U_ TC _ U_ E R R O R _ R E Q _ R E J EC T _ R E Q _ V IA _ T C 3 V IA _ T C 3

TC _ RE S U L T_ L _ RE Q _ V IA _ T C 3

T C _ R E S U LT _ N L _ R E Q _V IA _ T C 3

m o re _ da ta (T R U E )

(F A L S E )

7021
7022

Figure 16.2/6 (sheet 3 of 3): Process PERFORMING_MAP_SSM

466

3GPP

467 Release 1998

235

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess REQ UESTING _MAP_SSM


F ig u re 1 6. 2 /7 :

16.2 _7.1(4)

C om m e nt 'M A P S e rvic e S tat e M a sc h ine ': DC L A R G U M E N T _ C O R R E C T , E R R O R _C O D E _ C O R RE C T , LIN K E D _R E Q _ D E F , S Y N T A X _ C O R R E C T , M A P _ IN IT IA T E D , C N F , L IN K ED _ O P E R A T IO N _ A L LO W E D B O O L E A N , O P _ C L A S S IN T E G E R ;

ID L E

ID L E

S E R V IC E _ IN V O K E D

a s ervic e h as b ee n in vo k ed b y t h e M A P u s er

'S e t_ O p era tio n_ _ c o d e_ an d _ T C AP _ pa ram et ers '

T C _ IN VO K E _ R E Q _V IA _ T C 4

W ait_ fo r_ co n f ?

(F A L S E )

(T R U E )

W A IT _ F O R _ C O N F IR M

7023
7024

Figure 16.2/7 (sheet 1 of 4): Process REQUESTING_MAP_SSM

468

3GPP

469 Release 1998

236

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess REQ UESTING _MAP_SSM


F ig u re 1 6. 2 /7 :

16.2 _7.2(4)

W A IT _F O R _ C O N F IR M

RE S U L T_ R E C E IV E D 4 S YN T A X _ CO RR E C T ( TRU E ) P A R T IA L_ R ES U L T _ CO RR E C T ( TRU E ) 'A P P E ND _ P A R T IA L _ IN F O ' 'S e t_ p ro v id er_ e rro r= in va lid _ res p on s e_ rec e ive d (F A L S E )

P A R T IA L _ R E SU L T _ R E C E IV E D

S YN T A X _ CO RR E C T

(F A L S E )

( TR UE ) (F A L S E ) 'S T O R E _ PA R T IA L _ IN F O ' T C _U _ CA N CE L _ RE Q

W A IT _F O R _ C O N F IR M

S ervic e_ p aram e ter_ av ailable? ( TRU E ) U n exp e c ted _ d a ta (F A L S E )

(F A L S E )

M A P _ CN F_ V IA _ U S E R 5

(T R U E )

' S et _p rov id er_ e rro r= inv alid _ re sp o ns e _re c eiv ed

'S e t_ p ro b lem _ c o d e= m is ty p ed_ p ar am eter'

'S et _p ro vid er_ error= inv alid_ re s po n se _ re c eived

T C _ U _R E J E C T _ R E Q _ V IA _ T C 4

M A P _C N F _ V IA _U S E R 5

7025
7026

Figure 16.2/7 (sheet 2 of 4): Process REQUESTING_MAP_SSM

470

3GPP

471 Release 1998

237

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess REQ UESTING _MAP_SSM


F ig u re 1 6. 2 /7 : W A IT _ F O R _ C O N F IR M

16.2 _7.3(4)

N E G A T IV E _ RE S U L T_ R E C E IV E D

E RR O R _ CO DE _ CO RR E C T (T R U E ) S YN T A X _ CO RR E C T (T R U E ) S e rvic e _ p aram ete rs _ a va ila ble ? (T R U E ) U ne xp e c ted _ d a ta_ va lu e ? (F A L S E ) (T R U E )

(F A L S E )

(F A L S E )

4 (F A L S E )

'S e t_ pro v ide r_ e rro r= in va lid _ res p on s e_ rec e ive d

'S et_ u s er_ erro r'

' S et _p rov id er_ e rro r= inv alid _ re sp o ns e _re c eiv ed

M A P_ C N F _ V IA _U S E R 5

7027
7028

Figure 16.2/7 (sheet 3 of 4): Process REQUESTING_MAP_SSM

472

3GPP

473 Release 1998

238

3GPP TS 09.02 V7.15.0 (2004-03)

Pro cess REQ UESTING _MAP_SSM


F ig u re 1 6. 2 /7 : W A IT _ F O R _ C O N F IR M

16.2 _7.4(4)

L IN K E D _ R EQ U E S T _ R EC E IV E D ' F in d _p a re n t_ O pe rat ion _ c od e' L IN K E D _ O P E R A T IO N _ A L LO W E D ( F A LS E ) (T R U E ) 4 A R G UM E N T_ C O R R E CT (T R U E ) ' S ervic e_ p ara m ete rs_ a va ila b le ? ' (T R U E ) ( F A LS E ) ( F A LS E ) 'S e t_ p rob le m _ c o de ' T C _U _ R E JE C T_ R E Q _ V IA _ T C 4

L IN K E D _ S E R V IC E_ IN VO K E D 'S E T _ IM P L IC IT _ CO NF = TR UE '

U S ER_ R E JE CT _ R E CE IV E D MA P _ IN IT IA T E D (T R U E ) (F A L S E)

W A IT _F O R _ C O N F IR M

'S e t_ pro v ide r_ erro r'

'S et_ u s er_ erro r'

M A P _ CN F_ V IA _U S E R 5

'S et _p r o vid e r_ error= d ata _ m is s ing '

M A P _C N F _ V IA _U S E R 5

W A IT _ F O R _ C O N F IR M

P R O V ID E R _ RE JE C T_ R E C E IV E D

T IM E R _ E X P IR Y

'O pe ration c las s a s so c ia ted w ith th e s ervic e ' (2 ) (4 )

T E R M IN A T E D

O P _C L A S S (1 ,3 ) 'S et _p ro vid e r_ erro r' ' S et _p rov id er_ e rro r' L IN K E D _ R EQ _ DE F (T R U E ) (F A L SE ) IM P L IC IT _ C ON F (TR U E ) M A P _C N F _ V IA _U S E R 5 M A P _ C NF _ V IA _ U S ER 5 M A P _ CN F_ V IA _ U S E R 5 'A link ed o pe ratio n sh o uld ha ve b een inv o k ed ' (F A L S E )

7029
7030

Figure 16.2/7 (sheet 4 of 4): Process REQUESTING_MAP_SSM

474

3GPP

475 Release 1998

239

3GPP TS 09.02 V7.15.0 (2004-03)

7031 7032
7033 7034 7035 7036

17

Abstract syntax of the MAP protocol


17.1 General

This subclause specifies the Abstract Syntaxes for the Mobile Application Part as well as the associated set of Operations and Errors, using the Abstract Syntax Notation One (ASN.1), defined in CCITT Recommendation X.208 (1988) or X.680 (1994) with additions as defined in subclause 17.1.4 on Compatibility Considerations and the OPERATION and ERROR external MACROs, defined in CCITT Recommendation Q.773.

7037 The Abstract Syntax is defined for all interfaces specified in subclause 4.4 except for the A- and B-interfaces. 7038 The Mobile Application Part protocol is defined by two Abstract Syntaxes: 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050

one Abstract Syntax which encompass all Operations; and Errors identified by the various MAP subsystem numbers.

This Abstract Syntax represents the set of values each of which is a value of the ASN.1 type TCAPMessages. MessageType as defined in CCITT Recommendation Q.773 with the ANY DEFINED BY sections resolved by the operation and error codes included in the ASN.1 module MAP-Protocol. However, only the subset of this abstract syntax which is required by the procedures defined for an entity needs to be supported: one Abstract Syntax identified by the OBJECT IDENTIFIER value MAP-DialogueInformation.mapDialogueAS.

This Abstract Syntax represents the set of values each of which is a value of the ASN.1 type MAPDialogueInformation.MAP-DialoguePDU. Such a value of the ASN.1 single-ASN.1-type element is contained within the user-information element of the TCAPMessages.DialoguePortion ASN.1 type. This Abstract Syntax name is to be used as a direct reference.

7051

17.1.1 Encoding rules

7052 The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract 7053 Syntax Notation One, defined in CCITT Recommendation X.690 with the same exceptions as in CCITT 7054 Recommendation Q.773 section 4 Message Representation. 7055 When the definite form is used for length encoding, a data value of length less than 128 octets must have the length 7056 encoded in the short form. 7057 When the long form is employed to code a length, the minimum number of octets shall be used to code the length field. 7058 OCTET STRING values and BIT STRING values must be encoded in a primitive form. 7059 There is no restriction to the use of empty constructors (e.g. an empty SEQUENCE type). That is, the encoding of the 7060 content of any data value shall consist of zero, one ore more octets.

7061

17.1.2 Use of TC

7062 The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on 7063 CCITT Recommendation Q.773 (1992). 7064 7065 7066 7067 7068 7069

NOTE 1: The class of an operation is not stated explicitly but is specified as well in the ASN.1 operation type definition. Class 1: RESULT and ERROR appear in ASN.1 operation type definition. Class 2: only ERROR appears in ASN.1 operation type definition. Class 3: only RESULT appears in ASN.1 operation type definition. Class 4: both RESULT and ERROR do not appear in ASN.1 operation type definition.

476

3GPP

477 Release 1998

240

3GPP TS 09.02 V7.15.0 (2004-03)

7070 7071 7072 7073

The ASN.1 data type which follows the keywords "ARGUMENT", "PARAMETER" or "RESULT" (for OPERATION and ERROR) is always optional from a syntactic point of view. However, except when specifically mentioned with the ASN.1 comment -- optional , the parameter part of a component has to be considered as mandatory from a semantic point of view.

7074 When an optional element is missing in an invoke component or in an inner data structure while it is required by the 7075 context, an error component is returned if specified in the operation type; the associated type of error is DataMissing. 7076 This holds also when the entire parameter of an invoke component is missing while it is required by the context. 7077 7078

NOTE 2: When a mandatory element is missing in the parameter or inner data structure of any component, a reject component is returned (if the dialogue still exists). The problem code to be used is "Mistyped parameter".

7079 The Timer Values used in the operation type definitions are indicated as ASN.1 comment. The Timer Value Ranges are: 7080 7081 7082 7083

= from 3 seconds to 10 seconds;

m = from 15 seconds to 30 seconds; ml = from 1 minute to 10 minutes; l = from 28 hours to 38 hours.

7084 17.1.2.1
7085 7086 7087 7088 7089 7090 7091 7092 7093

Use of Global Operation and Error codes defined outside MAP

An entity supporting an application context greater than 2 shall be capable of receiving an operation or error code, within an application context defined in GSM 09.02, encoded as either an Object Identifier (as defined in CCITT Recommendation X.690 (1994)) or an integer value (as defined in section 17.5). Related restrictions regarding the use of Object Identiers are as follows: The length of the Object Identifier shall not exceed 16 octets and the number of components of the Object Identifier shall not exceed 16. Object Identifiers shall be used only for operations or errors defined outside of GSM 09.02. Global error codes may be sent only in response to a global operation. If a standard operation is received then a global error code shall not be sent in response.

7094 Handling of an unknown operation codes by the receiving entity is defined in section 15.1.1

7095

17.1.3 Use of information elements defined outside MAP

7096 An information element or a set of information elements (messages) transparently carried in the Mobile Application 7097 Part but defined in other recommendation/technical specifications are handled in one of the following ways: 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107

i) The contents of each information element (without the octets encoding the identifier and the length in the recommendation/technical specification where it is defined unless explicitly stated otherwise) is carried as the value of an ASN.1 NamedType derived from the OCTET STRING data type. Additionally, the internal structure may be explained by means of comments. In case of misalignment the referred to recommendation/technical specification takes precedence. ii) The complete information element (including the octets encoding the identifier and the length in the recommendation/technical specification where it is defined) or set of information elements and the identity of the associated protocol are carried as the value of the ExternalSignalInfo data type defined in the present document. Where more than one information element is carried, the information elements are sent contiguously with no filler octets between them.

478

3GPP

479 Release 1998

241

3GPP TS 09.02 V7.15.0 (2004-03)

7108

17.1.4 Compatibility considerations

7109 The following ASN.1 modules conform to CCITT Recommendation X.208 (1988) or X.680 (1994) (the only module 7110 which makes use of X.680 is MAP-ExtensionDataTypes), but in addition Ellipsis Notation ("..." - notation) is used as 7111 described in ITU-T Recommendation X.680 Amendment 1 (1995) wherever future protocol extensions are foreseen. 7112 7113 7114 7115

The "..." construct applies only to SEQUENCE and ENUMERATED data types. An entity supporting a version greater than 1 shall not reject an unsupported extension following "..." of that SEQUENCE or ENUMERATED data type. The Encoding Rules from subclause 17.1.1 apply to every element of the whole Transfer Syntax especially to the ASN.1 type EXTERNAL.

7116 Private extensions shall: 7117 7118 7119 7120 7121 7122

1) if included in operations of an AC of V2, follow the extension marker and be tagged using PRIVATE tags up to and including 29. NOTE: This type of extension is in most cases used only within a PLMN. 2) if included in operations of an AC of V3 or higher: be included only in the Private Extension Container that is defined in the specification. NOTE: This type of extension can be used between PLMNs.

7123 Private extensions shall not be included in v2 supplementary service operations. 7124 Private extensions shall not be included within user error for RegisterCCEntry and EraseCCEntry operations. 7125 PCS extensions shall be included in the PCS Extension Container that is defined in this specification. 7126 7127 7128 7129

In order to improve extensibility, a few error parameters have been defined as a CHOICE between the version 2 description and a SEQUENCE including the version 2 description and an extension container. Operations used in a v2application-context must consider only the first alternative while operations used in a vn-application-context (n>2) must consider only the second alternative.

7130
7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147

17.1.5 Structure of the Abstract Syntax of MAP


For each MAP parameter which has to be transferred by a MAP Protocol Data Unit (MAP message), there is a PDU field (an ASN.1 NamedType) whose ASN.1 identifier has the same name as the corresponding parameter, except for the differences required by the ASN.1 notation (blanks between words are removed or replaced by hyphen, the first letter of the first word is lower-case and the first letter of the following words are capitalized, e.g. "no reply condition time" is mapped to "noReplyConditionTime"). Additionally some words may be abbreviated as follows: bs ch cug ho ic id info lcs ms oc om pw basic service call handling closed user group handover incoming call identity information location services mobile service outgoing call operation & maintenance Password

480

3GPP

481 Release 1998

242

3GPP TS 09.02 V7.15.0 (2004-03)

7148 7149 7150 7151 7152 7153 7154 7155

sm ss

short message service supplementary service

The MAP protocol is composed of several ASN.1 modules dealing with either operations, errors, data types, and, if applicable, split into those dealing with mobile services, call handling services, supplementary services and short message services. For operations and errors no values are assigned, but only the operation and error types in order to allow use of the defined types also by other protocols (e.g. GSM 04.80). The values (operation codes and error codes) are defined in a separate module. The ASN.1 source lines are preceded by line-numbers at the left margin in order to enable the usage of the cross-reference in annex A.

7156 The module containing the definition of the operation packages for MAP is: 7157

1. MAP-OperationPackages.

7158 The module containing the definition of the application contexts for MAP is: 7159

2. MAP-ApplicationContexts.

7160 The module containing the data types for the Abstract Syntax to be used for TCAPMessages.DialoguePortion for MAP 7161 is: 7162

3. MAP-DialogueInformation.

7163 The module containing the operation codes and error codes for MAP is: 7164

4. MAP-Protocol.

7165 The modules containing all operation type definitions for MAP are: 7166 7167 7168 7169 7170 7171 7172

5. MAP-MobileServiceOperations; 6. MAP-OperationAndMaintenanceOperations; 7. MAP-CallHandlingOperations; 8. MAP-SupplementaryServiceOperations; 9. MAP-ShortMessageServiceOperations; 10. MAP-Group-Call-Operations. 11. MAP-LocationServiceOperations

7173 The module containing all error type definitions for MAP is: 7174

12. MAP-Errors.

7175 Modules containing all data type definitions for MAP are: 7176 7177 7178 7179 7180 7181 7182 7183 7184

13. MAP-MS-DataTypes; 14. MAP-OM-DataTypes; 15. MAP-CH-DataTypes; 16. MAP-SS-DataTypes; 17. MAP-SS-Code; 18. MAP-SM-DataTypes; 19. MAP-ER-DataTypes; 20. MAP-CommonDataTypes; 21. MAP-TS-Code;

482

3GPP

483 Release 1998

243

3GPP TS 09.02 V7.15.0 (2004-03)

7185 7186 7187 7188

22. MAP-BS-Code; 23. MAP-ExtensionDataTypes; 24. MAP-GR-DataTypes; 25. MAP-LCS-DataTypes.

7189 References are made also to modules defined outside of the present document. They are defined in the technical 7190 specification Mobile Services Domain and technical specification Transaction Capability respectively: 7191 7192 7193

MobileDomainDefinitions; TCAPMessages; DialoguePDUs.

7194

17.1.6 Application Contexts

7195 The following informative table lists the latest versions of the Application Contexts used in this specification, with the 7196 operations used by them and, where applicable, whether or not the operation description is exactly the same as for 7197 previous versions. Information in sections 17.6 & 17.7 relates only to the ACs in this table. 7198
AC Name locationCancellationContext equipmentMngtContext imsiRetrievalContext infoRetrievalContext interVlrInfoRetrievalContext handoverControlContext AC Version v3 v2 v2 v2 v2 v2 Operations Used cancelLocation checkIMEI sendIMSI sendAuthenticationInfo sendIdentification prepareHandover forwardAccessSignalling sendEndSignal processAccessSignalling prepareSubsequentHandover readyForSM purgeMS alertServiceCentre reset processUnstructuredSSRequest unstructuredSS-Request unstructuredSS-Notify activateTraceMode deactivateTraceMode registerSS eraseSS activateSS deactivateSS registerPassword interrogateSS getPassword mo-forwardSM mt-forwardSM sendRoutingInfoForSM reportSM-DeliveryStatus InformServiceCentre updateLocation forwardCheckSs-Indication restoreData insertSubscriberData Comments *

mwdMngtContext msPurgingContext shortMsgAlertContext resetContext networkUnstructuredSsContext

v3 v3 v2 v2 v2

tracingContext networkFunctionalSsContext

v3 v2

shortMsgMO-RelayContext shortMsgMT-RelayContext shortMsgGatewayContext

v3 v3 v3

the syntax of this operation has been extended in comparison with release 96 version the syntax is the same in v1 & v2

networkLocUpContext

v3

484

3GPP

485 Release 1998

244 activateTraceMode updateGprsLocation insertSubscriberData activateTraceMode insertSubscriberData deleteSubscriberData provideRoamingNumber sendRoutingInfo noteMsPresentForGprs sendRoutingInfoForGprs failureReport resumeCallHandling provideSubscriberInfo anyTimeInterrogation ss-InvocationNotification provideSIWFSNumber sIWFSSignallingModify prepareGroupCall processGroupCallSignalling forwardGroupCallSignalling sendGroupCallEndSignal setReportingState statusReport remoteUserFree registerCC-Entry eraseCC-Entry provideSubscriberLocation subscriberLocationReport

3GPP TS 09.02 V7.15.0 (2004-03)

gprsLocationUpdateContext subscriberDataMngtContext roamingNumberEnquiryContext locationInfoRetrievalContext gprsNotifyContext gprsLocationInfoRetrievalContext failureReportContext callControlTransferContext subscriberInfoEnquiryContext anyTimeEnquiryContext ss-InvocationNotificationContext sIWFSAllocationContext groupCallControlContext

v3 v3 v3 v3 v3 v3 v3 v4 v3 v3 v3 v3 v3

reportingContext callCompletionContext locationSvcEnquiryContext

v3 v3 v3

locationSvcGatewayContext

v3

sendRoutingInfoForLCS

7199 7200

NOTE (*):

The syntax of the operations is not the same as in previous versions unless explicitly stated

7234 7235

17.2 Operation packages


17.2.1 General aspects

7236 This subclause describes the operation-packages which are used to build the application-contexts defined in 7237 subclause 17.3. 7238 Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), 7239 in term of operations which they can invoke of each other. 7240 The grouping of operations into one or several packages does not necessarily imply any grouping in term of Application 7241 Service Elements. 7242 The following ASN.1 MACRO is used to describe operation-packages in this subclause:
7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258

OPERATION-PACKAGE MACRO ::= BEGIN TYPE NOTATION ::= Symmetric | ConsumerInvokes SupplierInvokes | empty VALUE NOTATION ::= value(VALUE OBJECT IDENTIFIER) Symmetric ::= "OPERATIONS" "{" OperationList "}" ConsumerInvokes ::= "CONSUMER INVOKES" "{" OperationList "}" SupplierInvokes ::= "SUPPLIER INVOKES" "{" OperationList "}" | empty OperationList ::= Operation | OperationList "," Operation Operation ::= value(OPERATION) END

486

3GPP

487 Release 1998

245

3GPP TS 09.02 V7.15.0 (2004-03)

7259 Since the application-context definitions provided in subclause 17.3 use only an informal description technique, only 7260 the type notation is used in the following subclauses to define operation-packages. 7261 The following definitions are used throughout this subclause (n>=2): 7262 7263 7264 7265 7266 7267 7268 7269

v1-only operation: An operation which shall be used only in v1 application-contexts; vn-only operation: An operation which shall be used only in vn application-contexts; v(n-1)-operation: An operation whose specification has not been modified since the MAP v(n-1) specifications or if the modifications are considered as not affecting v(n-1) implementations; v(n-1)-equivalent operation: The version of an operation which excludes all the information elements and errors which have been added since the MAP v(n-1) specification; vn-only package: An operation package which contains only vn-only operations; v(n-1)-package: An operation package which contains only v(n-1)- operations.

7270 The names of vn-packages are suffixed by "-vn" where n>=2. 7271 For each operation package which is not vn-only (n>=2) and which does not include only v(n-1)-operations, there is a 7272 v(n-1)-equivalent package. Except when a definition is explicitly provided in the following subclauses, the v(n-1)7273 equivalent package includes the v(n-1)-equivalent operations of the operations which belong to this package.

7274 7275 17.2.2.1

17.2.2 Packages specifications


Location updating

7276 This operation package includes the operations required for location management procedures between HLR and VLR.
7277 7278 7279 7280 7281 7282 7283

LocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { updateLocation} SUPPLIER INVOKES { forwardCheckSs-Indication}

7284 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

7285 17.2.2.2

Location cancellation

7286 This operation package includes the operations required for location cancellation and MS purging procedures between 7287 HLR and VLR and between HLR and SGSN.
7288 7289 7290 7291 7292

LocationCancellationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { cancelLocation}

7293 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

7294 17.2.2.3

Roaming number enquiry

7295 This operation package includes the operations required for roaming number enquiry procedures between HLR and 7296 VLR.
7297 7298 7299 7300 7301

RoamingNumberEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideRoamingNumber}

7302 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

488

3GPP

489 Release 1998

246

3GPP TS 09.02 V7.15.0 (2004-03)

7303 17.2.2.4

Information retrieval

7304 This operation package includes the operation required for the authentication information retrieval procedure between 7305 HLR and VLR and between HLR and SGSN.
7306 7307 7308 7309 7310 7311

InfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo}

7312 The v1-equivalent package is defined as follows:


7313 7314 7315 7316 7317 7318

InfoRetrievalPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR or VLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendParameters}

7319 17.2.2.5

Inter-VLR information retrieval

7320 This operation package includes the operations required for inter VLR information retrieval procedures.
7321 7322 7323 7324 7325

InterVlrInfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification}

7326 The v1-equivalent package is : InfoRetrievalPackage-v1.

7327 17.2.2.6

IMSI retrieval

7328 This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR.
7329 7330 7331 7332 7333

IMSIRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { sendIMSI}

7334 This package is v2 only.

7335 17.2.2.7

Call control transfer

7336 This operation package includes the operation required for the call control transfer procedure between VMSC and 7337 GMSC.
7338 7339 7340 7341 7342

CallControlTransferPackage-v4 ::= OPERATION-PACKAGE -- Supplier is GMSC if Consumer is VMSC CONSUMER INVOKES { resumeCallHandling}

7343 The v3-equivalent package can be determined according to the rules described in subclause 17.2.1.

7344 17.2.2.8 - 17.2.2.9 Void 7345 17.2.2.10 Interrogation

7346 This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR.
7347 7348 7349 7350 7351

InterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR or NPLR if Consumer is MSC CONSUMER INVOKES { sendRoutingInfo}

7352 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

490

3GPP

491 Release 1998

247

3GPP TS 09.02 V7.15.0 (2004-03)

7353 17.2.2.11 7354 17.2.2.12

Void Handover Control

7355 This operation package includes the operations required for handover procedures between MSCs.
7356 7357 7358 7359 7360 7361 7362 7363 7364 7365

HandoverControlPackage-v2 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { prepareHandover, forwardAccessSignalling} SUPPLIER INVOKES { sendEndSignal, processAccessSignalling, prepareSubsequentHandover}

7366 The v1-equivalent package is defined as follows.


7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378

HandoverControlPackage-v1 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { performHandover, forwardAccessSignalling, traceSubscriberActivity} SUPPLIER INVOKES { sendEndSignal, noteInternalHandover, processAccessSignalling, performSubsequentHandover}

7379 17.2.2.13

Subscriber Data management stand alone

7380 This operation package includes the operations required for stand alone subscriber data management procedures 7381 between HLR and VLR or between HLR and SGSN.
7382 7383 7384 7385 7386 7387

SubscriberDataMngtStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData, deleteSubscriberData}

7388 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

7389 17.2.2.14

Equipment management

7390 This operation package includes the operations required for equipment management procedures between EIR and MSC 7391 or between EIR and SGSN.
7392 7393 7394 7395 7396 7397

EquipmentMngtPackage-v2 ::= OPERATION-PACKAGE -- Supplier is EIR if Consumer is MSC -- Supplier is EIR if Consumer is SGSN CONSUMER INVOKES { checkIMEI}

7398 The v1-equivalent package can be determined according to the rules described in subclause 17.2.1.

7399 17.2.2.15

Subscriber data management

7400 This operation package includes the operations required for subscriber data management procedures between HLR and 7401 VLR or between HLR and SGSN.
7402 7403 7404 7405 7406

SubscriberDataMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData}

7407 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

492

3GPP

493 Release 1998

248

3GPP TS 09.02 V7.15.0 (2004-03)

7408 17.2.2.16

Location register restart

7409 This operation package includes the operations required for location register restart procedures between HLR and VLR 7410 or between HLR and SGSN.
7411 7412 7413 7414 7415

ResetPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { reset}

7416 The v1-equivalent package can be determined according to the rules described in subclause 17.2.1.

7417 17.2.2.17

Tracing stand-alone

7418 This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or 7419 between HLR and SGSN.
7420 7421 7422 7423 7424 7425

TracingStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode, deactivateTraceMode}

7426 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

7427 17.2.2.18

Functional SS handling

7428 This operation package includes the operations required for functional supplementary services procedures between VLR 7429 and HLR.
7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441

FunctionalSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerSS, eraseSS, activateSS, deactivateSS, registerPassword, interrogateSS} SUPPLIER INVOKES { getPassword}

7442 The v1-equivalent package can be determined according to the rules described in subclause 17.2.1.

7443 17.2.2.19

Tracing

7444 This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR 7445 and SGSN.
7446 7447 7448 7449 7450

TracingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode}

7451 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in subclause 17.2.1.

7452 17.2.2.20

Binding

7453 This operation package includes the operation required to initialize a supplementary service procedure between VLR 7454 and HLR or between gsmSCF and HLR.
7455 7456 7457 7458 7459 7460

BindingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { beginSubscriberActivity}

7461 This package is v1 only.

494

3GPP

495 Release 1998

249

3GPP TS 09.02 V7.15.0 (2004-03)

7462 17.2.2.21

Unstructured SS handling

7463 This operation package includes the operations required for unstructured supplementary services procedures between 7464 VLR and HLR, and between the HLR and the gsmSCF.
7465 7466 7467 7468 7469 7470 7471 7472 7473

UnstructuredSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Request} SUPPLIER INVOKES { unstructuredSS-Request, unstructuredSS-Notify}

7474 The v1-equivalent package is defined as follows:


7475 7476 7477 7478 7479 7480

UnstructuredSsPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Data}

7481 17.2.2.22

MO Short message relay services

7482 This operation package includes the operations required for short message relay service procedures between IWMSC 7483 and VMSC or between GMSC and MSC or between SGSN and IWMSC.
7484 7485 7486 7487 7488 7489

MOShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is MSC -- Supplier is IWMSC if Consumer is SGSN CONSUMER INVOKES { MO-forwardSM}

7490 The v2-equivalent package is defined as follows:


7491 7492 7493 7494 7495 7496 7497

ShortMsgRelayPackage-v2 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is MSC -- Supplier is MSC or SGSN if Consumer is GMSC -- Supplier is IWMSC if Consumer is SGSN CONSUMER INVOKES { forwardSM}

7498 The v1-equivalent package can be determined according to the rules described in subclause 17.2.1.

7499 17.2.2.23

Short message gateway services

7500 This operation package includes the operations required for short message service gateway procedures between MSC 7501 and HLR.
7502 7503 7504 7505 7506 7507 7508 7509 7510

ShortMsgGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM, reportSM-DeliveryStatus} SUPPLIER INVOKES { informServiceCentre}

The v2-equivalent package can be determined according to the rules described in subclause 17.2.1

7511 The v1-equivalent package is defined as follows:


7512 7513 7514 7515 7516 7517

ShortMsgGatewayPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM reportSMDeliveryStatus}

496

3GPP

497 Release 1998

250

3GPP TS 09.02 V7.15.0 (2004-03)

7518 17.2.2.24

MT Short message relay services

7519 This operation package includes the operations required for short message relay service procedures between GMSC and 7520 MSC or between GMSC and SGSN.
7521 7522 7523 7524 7525

MTShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSC or SGSN if Consumer is GMSC CONSUMER INVOKES { MT-forwardSM}

7526 The v2-equivalent package is: ShortMsgRelayPackage-v2

7527 17.2.2.25 7528 17.2.2.26

Void Message waiting data management

7529 This operation package includes the operations required for short message waiting data procedures between HLR and 7530 VLR, between HLR and SGSN.
7531 7532 7533 7534 7535 7536

MwdMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { readyForSM}

7537 The v2-equivalent package can be determined according to the rules described in subclause 17.2.1.
7538

7539 The v1-equivalent package is defined as follows:


7540 7541 7542 7543 7544

MwdMngtPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { noteSubscriberPresent}

7545 17.2.2.27

Alerting

7546 This operation package includes the operations required for alerting between HLR and IWMSC.
7547 7548 7549 7550 7551

AlertingPackage-v2 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentre}

7552 The v1-equivalent package is defined as follows.


7553 7554 7555 7556 7557

AlertingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentreWithoutResult}

7558 17.2.2.28

Data restoration

7559 This operation package includes the operations required for VLR data restoration between HLR and VLR.
7560 7561 7562 7563 7564

DataRestorationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { restoreData}

7565 The v2-equivalent package can be determined according to the rules described in subclause 17.2.1. 7566 The v1-equivalent package is: InfoRetrievalPackage-v1

498

3GPP

499 Release 1998

251

3GPP TS 09.02 V7.15.0 (2004-03)

7567 17.2.2.29

Purging

7568 This operation package includes the operations required for purging between HLR and VLR or between HLR and 7569 SGSN.
7570 7571 7572 7573 7574 7575

PurgingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { purgeMS}

7576 The v2-equivalent package can be determined according to the rules described in subclause 17.2.1.

7577 17.2.2.30

Subscriber information enquiry

7578 This operation package includes the operations required for subscriber information enquiry procedures between HLR 7579 and VLR.
7580 7581 7582 7583 7584

SubscriberInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideSubscriberInfo}

7585 This package is v3 only.

7586 17.2.2.31

Any time information enquiry

7587 This operation package includes the operations required for any time information enquiry procedures between gsmSCF 7588 and HLR.
7589 7590 7591 7592 7593

AnyTimeInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeInterrogation}

7594 This package is v3 only.

7595 17.2.2.32

Group Call Control

7596 This operation package includes the operations required for group call and broadcast call procedures between MSCs.
7597 7598 7599 7600 7601 7602 7603 7604 7605

GroupCallControlPackage-v3 ::= OPERATION-PACKAGE -- Supplier is relay MSC if Consumer is anchor MSC CONSUMER INVOKES { prepareGroupCall, forwardGroupCallSignalling} SUPPLIER INVOKES { sendGroupCallEndSignal, processGroupCallSignalling}

7606 This package is v3 only.

7607 17.2.2.33

Provide SIWFS number

7608 This operation package includes the operations required between VMSC and SIWF for requesting resources from an 7609 SIWF.
7610 7611 7612 7613 7614

ProvideSIWFSNumberPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { provideSIWFSNumber}

7615 This package is v3 only.

500

3GPP

501 Release 1998

252

3GPP TS 09.02 V7.15.0 (2004-03)

7616 17.2.2.34

SIWFS Signalling Modify

7617 This operation package includes the operations required for the modification of the resourses in an SIWF between the 7618 VMSC and SIWF.
7619 7620 7621 7622 7623

SIWFSSignallingModifyPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { sIWFSSignallingModify}

7624 This package is v3 only.

7625 17.2.2.35

Gprs location updating

7626 This operation package includes the operations required for the gprs location management procedures between HLR 7627 and SGSN.
7628 7629 7630 7631

GprsLocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { updateGprsLocation}

7632 7633 This package is v3 only.

7634 17.2.2.36

Gprs Interrogation

7635 This operation package includes the operations required for interrogation procedures between HLR and GGSN.
7636 7637 7638 7639

GprsInterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs}

7640 7641 This package is v3 only.

7642 17.2.2.37

Failure reporting

7643 This operation package includes the operations required for failure reporting between HLR and GGSN.
7644 7645 7646 7647

FailureReportingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { failureReport}

7648 7649 This package is v3 only.

7650 17.2.2.38

GPRS notifying

7651 This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and 7652 GGSN.
7653 7654 7655 7656

GprsNotifyingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is GGSN if Consumer is HLR CONSUMER INVOKES { noteMsPresentForGprs}

7657 7658 This package is v3 only.

502

3GPP

503 Release 1998

253

3GPP TS 09.02 V7.15.0 (2004-03)

7659 17.2.2.39

Supplementary Service invocation notification

7660 This operation package includes the operations required for Supplementary Service invocation notification procedures 7661 between MSC and gsmSCF.
7662 7663 7664 7665 7666

SS-InvocationNotificationPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is gsmSCF if Consumer is MSC CONSUMER INVOKES { ss-InvocationNotification}

7667 This package is v3 only.

7668 17.2.2.40

Set Reporting State

7669 This operation package includes the operation required for procedures between HLR and VLR to set the reporting state.
7670 7671 7672 7673 7674

SetReportingStatePackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { setReportingState}

7675 This package is v3 only.

7676 17.2.2.41

Status Report

7677 This operation package includes the operation required for procedures between VLR and HLR to report call results and 7678 events.
7679 7680 7681 7682 7683

StatusReportPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { statusReport}

7684 This package is v3 only.

7685 17.2.2.42

Remote User Free

7686 This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free.
7687 7688 7689 7690 7691

RemoteUserFreePackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { remoteUserFree}

7692 This package is v3 only.

7693 17.2.2.43

Call Completion

7694 This operation package includes the operations required for procedures between VLR and HLR for subscriber control of 7695 call completion services.
7696 7697 7698 7699 7700 7701

CallCompletionPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerCC-Entry, eraseCC-Entry}

7702 This package is v3 only.

7703 17.2.2.44

Location service gateway services

7704 This operation package includes the operations required for location service gateway procedures between GMLC and 7705 HLR.

504

3GPP

505 Release 1998


7706 7707 7708 7709 7710 7711

254

3GPP TS 09.02 V7.15.0 (2004-03)

LocationSvcGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMLC CONSUMER INVOKES { sendRoutingInfoForLCS}

This package is v3 only.

7712 17.2.2.45

Location service enquiry

7713 This operation package includes the operations required for the location service enquiry procedures between GMLC and 7714 MSC.
7715 7716 7717 7718 7719

LocationSvcEnquiryPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is MSC if Consumer is GMLC CONSUMER INVOKES { provideSubscriberLocation}

7720 This package is v3 only.

7721 17.2.2.45A

Location service reporting

7722 This operation package includes the operations required for the location service enquiry procedures between MSC and 7723 GMLC.
7724 7725 7726 7727

LocationSvcReportingPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is GMLC if Consumer is MSC CONSUMER INVOKES { subscriberLocationReport}

7728

7729 17.2.2.46 7730 17.2.2.47 7731 17.2.2.48 7732 7733

Void Void Void

17.3 Application contexts


17.3.1 General aspects

7734 An application-context is assigned for each dialogue established by a MAP-user. In the present document each 7735 application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and 7736 transmitted to the peer under certain circumstances.

506

3GPP

507 Release 1998

255

3GPP TS 09.02 V7.15.0 (2004-03)

7737 The following ASN.1 MACRO is used to describe the main aspects of application-contexts in the following subclauses:
7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760

APPLICATION-CONTEXT MACRO ::= BEGIN TYPE NOTATION ::= Symmetric | InitiatorConsumerOf ResponderConsumerOf | empty VALUE NOTATION ::= value(VALUE OBJECT IDENTIFIER) Symmetric ::= "OPERATIONS OF" "{" PackageList "}" InitiatorConsumerOf ::= "INITIATOR CONSUMER OF" "{" PackageList "}" ResponderConsumerOf ::= "RESPONDER CONSUMER OF" "{" PackageList "}" | empty PackageList ::= Package | PackageList "," Package Package ::= value(OPERATION-PACKAGE) | type -- shall reference a package type END

7761 The following definitions are used throughout this subclause: 7762 7763 7764

v1-application-context: An application-context which contains only v1-packages and uses only TC v1 facilities; v1 context set: the set of v1-application-contexts defined in the present document. vn-application-context (n>=2): An application-context which contains only vn-packages;

7765 The names of v1-application-contexts are suffixed by "-v1" while other names are suffixed by "-vn" where n>=2. 7766 Application-contexts which do not belong to the v1 context set use v2 TC facilities. 7767 The last component of each application-context-name (i.e. the last component of the object identifier value) assigned to 7768 an application-context which belongs to the v1 context set indicates explicitly "version1". 7769 For each application-context which does not belong to the "v1 context set" there is a v1-equivalent application context. 7770 This is a v1-application-context which includes the v1-equivalents of the packages included in the original context. 7771 Each application-context uses the abstract-syntax associated with the operation-packages it includes and uses the 7772 transfer-syntax derived from it by applying the encoding rules defined in subclause 17.1.1. 7773 ACs which do not belong to the v1 context set require the support of the abstract-syntax identified by the object 7774 identifier value: MAP-DialogueInformation.map-Dialogue-AS defined in subclause 17.4.

7775 7776 17.3.2.1 7777 17.3.2.2

17.3.2 Application context definitions


Void Location Updating

7778 This application context is used between HLR and VLR for location updating procedures.
7779 7780 7781 7782 7783 7784 7785 7786 7787 7788

networkLocUpContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { LocationUpdatingPackage-v3, DataRestorationPackage-v3} RESPONDER CONSUMER OF { SubscriberDataMngtPackage-v3 TracingPackage-v3} ::= {map-ac networkLocUp(1) version3(3)}

7789 The following application-context-name is assigned to the v2-equivalent application-context:


7790

{map-ac networkLocUp(1) version2(2)}

508

3GPP

509 Release 1998


7791

256

3GPP TS 09.02 V7.15.0 (2004-03)

7792 The following application-context-name is assigned to the v1-equivalent application-context:


7793 7794

{map-ac networkLocUp(1) version1(1)}

7795 17.3.2.3

Location Cancellation

7796 This application context is used between HLR and VLR or between HLR and SGSN for location cancellation 7797 procedures. For the HLR - SGSN interface only version 3 of this application context is applicable.
7798 7799 7800 7801 7802 7803

locationCancellationContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { LocationCancellationPackage-v3} ::= {map-ac locationCancel(2) version3(3)}

7804 The following application-context-name is assigned to the v2-equivalent application-context:


7805

map-ac locationCancel(2) version2(2)

7806 7807 The following application-context-name is assigned to the v1-equivalent application-context:


7808 7809

map-ac locationCancel(2) version1(1)

7810 17.3.2.4

Roaming number enquiry

7811 This application context is used between HLR and VLR for roaming number enquiry procedures.
7812 7813 7814 7815 7816 7817

roamingNumberEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { RoamingNumberEnquiryPackage-v3} ::= {map-ac roamingNbEnquiry(3) version3(3)}

7818 The following application-context-name is assigned to the v2-equivalent application-context:


7819 7820

{map-ac roamingNbEnquiry(3) version2(2)}

7821 The following application-context-name is assigned to the v1-equivalent application-context:


7822 7823

{map-ac roamingNbEnquiry(3) version1(1)}

7824 17.3.2.5 7825 17.3.2.6

Void Location Information Retrieval

7826 This application-context is used between GMSC and HLR or between GMSC and NPLR when retrieving location 7827 information. For the GMSC - NPLR interface version 1, version 2 and version 3 of this application context are 7828 applicable.
7829 7830 7831 7832 7833 7834

locationInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR or NPLR if Initiator is GMSC INITIATOR CONSUMER OF { InterrogationPackage-v3} ::= {map-ac locInfoRetrieval(5) version3(3)}

7835 The following application-context-name is assigned to the v2-equivalent application-context:


7836 7837 7838

{map-ac locInfoRetrieval(5) version2(2)}

7839 The following application-context-name is assigned to the v1-equivalent application-context:


7840 7841

{map-ac locInfoRetrieval(5) version1(1)}

510

3GPP

511 Release 1998

257

3GPP TS 09.02 V7.15.0 (2004-03)

7842 17.3.2.7

Call control transfer

7843 This application context is used for the call control transfer procedure between the VMSC and the GMSC.
7844 7845 7846 7847 7848 7849

callControlTransferContext-v4 APPLICATION-CONTEXT -- Responder is GMSC if Initiator is VMSC INITIATOR CONSUMER OF { CallControlTransferPackage-v4} ::= {map-ac callControlTransfer(6) version4(4)}

7850 The following application-context-name is assigned to the v3-equivalent application-context:


7851

{map-ac callControlTransfer(6) version3(3)}

7852 17.3.2.8 - 17.3.2.10 Void 7853 17.3.2.11 Location registers restart

7854 This application context is used between HLR and VLR or between HLR and SGSN for location register restart 7855 procedures. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable.
7856 7857 7858 7859 7860 7861

resetContext-v2 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { ResetPackage-v2} ::= {map-ac reset(10) version2(2)}

7862 The following application-context-name is assigned to the v1-equivalent application-context:


7863 7864

{map-ac reset(10) version1(1)}

7865 17.3.2.12

Handover control

7866 This application context is used for handover procedures between MSCs.
7867 7868 7869 7870 7871 7872

handoverControlContext-v2 APPLICATION-CONTEXT -- Responder is MSCB if Initiator is MSCA INITIATOR CONSUMER OF { HandoverControlPackage-v2} ::= {map-ac handoverControl(11) version2(2)}

7873 The following application-context-name is assigned to the v1-equivalent application-context:


7874 7875

{map-ac handoverControl(11) version1(1)}

7876 17.3.2.13

IMSI Retrieval

7877 This application context is used for IMSI retrieval between HLR and VLR.
7878 7879 7880 7881 7882 7883

imsiRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { IMSIRetrievalPackage-v2} ::= {map-ac imsiRetrieval(26) version2(2)}

7884 This application-context is v2 only.

7885 17.3.2.14

Equipment Management

7886 This application context is used for equipment checking between MSC and EIR or between SGSN and EIR. For the 7887 SGSN - EIR interface version 1 and version 2 of this application context are applicable:
7888 7889 7890 7891 7892 7893 7894

equipmentMngtContext-v2 APPLICATION-CONTEXT -- Responder is EIR if Initiator is MSC -- Responder is EIR if Initiator is SGSN INITIATOR CONSUMER OF { EquipmentMngtPackage-v2} ::= {map-ac equipmentMngt(13) version2(2)}

512

3GPP

513 Release 1998

258

3GPP TS 09.02 V7.15.0 (2004-03)

7895 The following application-context-name is assigned to the v1-equivalent application-context:


7896 7897

{map-ac equipmentMngt(13) version1(1)}

7898 17.3.2.15

Information retrieval

7899 This application context is used for authentication information retrieval between HLR and VLR or between HLR and 7900 SGSN. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable.
7901 7902 7903 7904 7905 7906 7907

infoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { InfoRetrievalPackage-v2} ::= {map-ac infoRetrieval(14) version2(2)}

7908 The following application-context-name is assigned to the v1-equivalent application-context:


7909 7910 7911

-- Responder is HLR if Initiator is VLR {map-ac infoRetrieval(14) version1(1)}

7912 17.3.2.16

Inter-VLR information retrieval

7913 This application context is used for information retrieval between VLRs.
7914 7915 7916 7917 7918 7919

interVlrInfoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { InterVlrInfoRetrievalPackage-v2} ::= {map-ac interVlrInfoRetrieval(15) version2(2)}

7920 The v1-equivalent application-context is:


7921 7922 7923

-- Responder is VLR if Initiator is VLR {map-ac infoRetrieval(14) version1(1)}

7924 17.3.2.17

Stand Alone Subscriber Data Management

7925 This application context is used for stand alone subscriber data management between HLR and VLR or between HLR 7926 and SGSN. For the HLR - SGSN interface only version 3 of this application context is applicable:
7927 7928 7929 7930 7931 7932

subscriberDataMngtContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { SubscriberDataMngtStandAlonePackage-v3} ::= {map-ac subscriberDataMngt(16) version3(3)}

7933 The following application-context-name is assigned to the v2-equivalent application-context:


7934 7935

{map-ac subscriberDataMngt(16) version2(2)}

7936 The following application-context-name is assigned to the v1-equivalent application-context:


7937 7938

{map-ac subscriberDataMngt(16) version1(1)}

7939 17.3.2.18

Tracing

7940 This application context is used between HLR and VLR or between HLR and SGSN for stand alone tracing control 7941 procedures: For the HLR - SGSN interface version 1, version 2 and version 3 of this application context are applicable.
7942 7943 7944 7945 7946

tracingContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { TracingStandAlonePackage-v3} ::= {map-ac tracing(17) version3(3)}

7947

514

3GPP

515 Release 1998

259

3GPP TS 09.02 V7.15.0 (2004-03)

7948 The following application-context-name is assigned to the v2-equivalent application-context:


7949 7950

{map-ac tracing(17) version2(2)}

7951 The following application-context-name is assigned to the v1-equivalent application-context:


7952 7953

{map-ac tracing(17) version1(1)}

7954 17.3.2.19

Network functional SS handling

7955 This application context is used for functional-like SS handling procedures between VLR and HLR.
7956 7957 7958 7959 7960 7961

networkFunctionalSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { FunctionalSsPackage-v2} ::= {map-ac networkFunctionalSs(18) version2(2)}

7962 The v1-equivalent application-context is defined as follows:


7963 7964 7965 7966 7967 7968 7969 7970

networkFunctionalSsContext-v1 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { FunctionalSsPackage-v1, UnstructuredSsPackage-v1, BindingPackage-v1} ::= {map-ac networkFunctionalSs(18) version1(1)}

7971 17.3.2.20

Network unstructured SS handling

7972 This application context is used for handling stimuli-like procedures between HLR and VLR, and between the HLR and 7973 gsmSCF.
7974 7975 7976 7977 7978 7979 7980 7981 7982

networkUnstructuredSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR -- Responder is VLR, Initiator is HLR -- Responder is gsmSCF, Initiator is HLR -- Responder is HLR, Initiator is gsmSCF OPERATIONS OF { UnstructuredSsPackage-v2} ::= {map-ac networkUnstructuredSs(19) version2(2)}

7983 The following application-context-name is assigned to the v1-equivalent application-context:


7984 7985

{map-ac networkFunctionalSs(18) version1(1)}

7986 17.3.2.21

Short Message Gateway

7987 This application context is used for short message gateway procedures.
7988 7989 7990 7991 7992 7993

shortMsgGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { ShortMsgGatewayPackage-v3} ::= {map-ac shortMsgGateway(20) version3(3)}

7994 The following application-context-name is assigned to the v2-equivalent application-context:


7995 7996

{map-ac shortMsgGateway(20) version2(2)}

7997 The following application-context-name is assigned to the v1-equivalent application-context:


7998 7999

{map-ac shortMsgGateway(20) version1(1)}

516

3GPP

517 Release 1998

260

3GPP TS 09.02 V7.15.0 (2004-03)

8000 17.3.2.22

Mobile originating Short Message Relay

8001 This application context is used between MSC and IWMSC or between SGSN and IWMSC for mobile originating short 8002 message relay procedures. For the SGSN - IWMSC interface version 1, version 2 and version 3 of this application 8003 context are applicable.
8004 8005 8006 8007 8008 8009 8010

shortMsgMO-RelayContext-v3 APPLICATION-CONTEXT -- Responder is IWMSC if Initiator is MSC -- Responder is IWMSC if Initiator is SGSN INITIATOR CONSUMER OF { MOShortMsgRelayPackage-v3} ::= {map-ac shortMsgMO-Relay(21) version3(3)}

8011 The following application-context-name is assigned to the v2-equivalent application-context:


8012 8013

{map-ac shortMsgMO-Relay(21) version2(2)}

8014 The following application-context-name is assigned to the v1-equivalent application-context:


8015 8016

{map-ac shortMsg-Relay(21) version1(1)}

8017 17.3.2.23 8018 17.3.2.24

Void Short message alert

8019 This application context is used for short message alerting procedures.
8020 8021 8022 8023 8024 8025

shortMsgAlertContext-v2 APPLICATION-CONTEXT -- Responder is IWMSC if Initiator is HLR INITIATOR CONSUMER OF { AlertingPackage-v2} ::= {map-ac shortMsgAlert(23) version2(2)}

8026 The following application-context-name is symbolically assigned to the v1-equivalent application-context:


8027 8028

{map-ac shortMsgAlert(23) version1(1)}

8029 17.3.2.25

Short message waiting data management

8030 This application context is used between VLR and HLR or between SGSN and HLR for short message waiting data 8031 management procedures. For the SGSN - HLR interface only version 3 of this application context is applicable.
8032 8033 8034 8035 8036 8037

mwdMngtContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is SGSN -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { MwdMngtPackage-v3} ::= {map-ac mwdMngt(24) version3(3)}

8038 8039 The following application-context-name is assigned to the v2-equivalent application-context:


8040

{map-ac mwdMngt(24) version2(2)}

8041 8042 The following application-context-name is assigned to the v1-equivalent application-context:


8043 8044

{map-ac mwdMngt(24) version1(1)}

518

3GPP

519 Release 1998

261

3GPP TS 09.02 V7.15.0 (2004-03)

8045 17.3.2.26

Mobile terminating Short Message Relay

8046 This application context is used between GMSC and MSC or between GMSC and SGSN for mobile terminating short 8047 message relay procedures. For the GMSC - SGSN interface version 2and version 3 of this application context and the 8048 equivalent version 1 application context are applicable.
8049 8050 8051 8052 8053 8054

shortMsgMT-RelayContext-v3 APPLICATION-CONTEXT -- Responder is MSC or SGSN if Initiator is GMSC INITIATOR CONSUMER OF { MTShortMsgRelayPackage-v3} ::= {map-ac shortMsgMT-Relay(25) version3(3)}

8055 The following application-context-name is assigned to the v2-equivalent application-context:


8056 8057

{map-ac shortMsgMT-Relay(25) version2(2)}

8058 The following application-context-name is assigned to the v1-equivalent application-context:


8059 8060

{map-ac shortMsgMO-Relay(21) version1(1)}

8061 17.3.2.27

MS purging

8062 This application context is used between HLR and VLR or between HLR and SGSN for MS purging procedures. For 8063 the SGSN - HLR interface only version 3 of this application context is applicable.
8064 8065 8066 8067 8068 8069 8070

msPurgingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { purgingPackage-v3} ::= {map-ac msPurging(27) version3(3)}

8071 The following application-context-name is assigned to the v2-equivalent application-context:


8072 8073

{map-ac msPurging(27) version2(2)}

8074 17.3.2.28

Subscriber information enquiry

8075 This application context is used between HLR and VLR for subscriber information enquiry procedures.
8076 8077 8078 8079 8080 8081

subscriberInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { SubscriberInformationEnquiryPackage-v3} ::= {map-ac subscriberInfoEnquiry(28) version3(3)}

8082 This application-context is v3 only.

8083 17.3.2.29

Any time information enquiry

8084 This application context is used between gsmSCF and HLR for any time information enquiry procedures.
8085 8086 8087 8088 8089 8090

anyTimeInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is gsmSCF INITIATOR CONSUMER OF { AnyTimeInformationEnquiryPackage-v3} ::= {map-ac anyTimeInfoEnquiry(29) version3(3)}

8091 This application-context is v3 only.

520

3GPP

521 Release 1998

262

3GPP TS 09.02 V7.15.0 (2004-03)

8092 17.3.2.30

Group Call Control

8093 This application context is used between anchor MSC and relay MSC for group call and broadcast call procedures.
8094 8095 8096 8097 8098 8099

groupCallControlContext-v3 APPLICATION-CONTEXT -- Responder is relay MSC if Initiator is anchor MSC INITIATOR CONSUMER OF { GroupCallControlPackage-v3} ::= {map-ac groupCallControl(31) version3(3)}

8100 This application-context is v3 only.

8101 17.3.2.31

Provide SIWFS Number

8102 This application context is used for activation or modification of SIWF resources.
8103 8104 8105 8106 8107 8108 8109

sIWFSAllocationContext-v3 APPLICATION-CONTEXT

-- Responder is SIWF if Initiater is VMSC INITIATOR CONSUMER OF { ProvideSIWFSNumberPackage-v3, SIWFSSignallingModifyPackage-v3} ::= {map-ac sIWFSAllocation (12) version3(3)}

8110 This application-context is v3 only.

8111 17.3.2.32

Gprs Location Updating

8112 This application context is used between HLR and SGSN for gprs location updating procedures.
8113 8114 8115 8116 8117 8118 8119 8120 8121

gprsLocationUpdateContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { GprsLocationUpdatingPackage-v3} RESPONDER CONSUMER OF { SubscriberDataMngtPackage-v3 TracingPackage-v3} ::= {map-ac gprsLocationUpdate(32) version3(3)}

8122 This application-context is v3 only.

8123 17.3.2.33

Gprs Location Information Retreival

8124 This application context is used between HLR and GGSN when retrieving gprs location information.
8125 8126 8127 8128 8129 8130

gprsLocationInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { GprsInterrogationPackage-v3} ::= {map-ac gprsLocationInfoRetrieval(33) version3(3)}

8131 This application-context is v3 only.

8132 17.3.2.34

Failure Reporting

8133 This application context is used between HLR and GGSN to inform that network requested PDP-context activation has 8134 failed.
8135 8136 8137 8138 8139 8140

failureReportContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { FailureReportingPackage-v3} ::= {map-ac failureReport(34) version3(3)}

8141 This application-context is v3 only.

522

3GPP

523 Release 1998

263

3GPP TS 09.02 V7.15.0 (2004-03)

8142 17.3.2.35

GPRS Notifying

8143 This application context is used between HLR and GGSN for notifying that GPRS subscriber is present again.
8144 8145 8146 8147 8148 8149

gprsNotifyContext-v3 APPLICATION-CONTEXT -- Responder is GGSN if Initiator is HLR INITIATOR CONSUMER OF { GprsNotifyingPackage-v3} ::= {map-ac gprsNotify(35) version3(3)}

8150 This application-context is v3 only.

8151 17.3.2.36

Supplementary Service invocation notification

8152 This application context is used between MSC and gsmSCF for Supplementary Service invocation notification 8153 procedures.
8154 8155 8156 8157 8158 8159

ss-InvocationNotificationContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is MSC INITIATOR CONSUMER OF { SS-InvocationNotificationPackage-v3} ::= {map-ac ss-InvocationNotification(36) version3(3)}

8160 This application-context is v3 only.

8161 17.3.2.37

Reporting

8162 This application context is used between HLR and VLR for reporting procedures.
8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174

reportingContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { SetReportingStatePackage-v3, StatusReportPackage-v3, RemoteUserFreePackage-v3} RESPONDER CONSUMER OF { SetReportingStatePackage-v3, StatusReportPackage-v3} ::= {map-ac reporting(7) version3(3)}

8175 This application-context is v3 only.

8176 17.3.2.38

Call Completion

8177 This application context is used between VLR and the HLR for subscriber control of call completion services.
8178 8179 8180 8181 8182 8183

callCompletionContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { CallCompletionPackage-v3} ::= {map-ac callCompletion(8) version3(3)}

8184 This application-context is v3 only.

8185 17.3.2.39

Location Service Gateway

8186 This application context is used for location service gateway procedures.
8187 8188 8189 8190 8191

locationSvcGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMLC INITIATOR CONSUMER OF { locationSvcGatewayPackage-v3} ::= {map-ac locationSvcGateway(37) version3(3)}

8192

524

3GPP

525 Release 1998

264

3GPP TS 09.02 V7.15.0 (2004-03)

8193 17.3.2.40 Location Service Enquiry


8194 This application context is used for location service enquiry procedures.
8195 8196 8197 8198 8199 8200 8201

locationSvcEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is MSC if Initiator is GMLC -- Responder is GMLC if Initiator is MSC INITIATOR CONSUMER OF { locationSvcEnquiryPackage-v3, locationSvcReportingPackage-v3} ::= {map-ac locationSvcEnquiry(38) version3 (3)}

8202

8203 17.3.2.41 8204 17.3.2.42 8205 17.3.2.43

Void Void Void

17.3.3 ASN.1 Module for application-context-names


The following ASN.1 module summarizes the application-context-name assigned to MAP application-contexts.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50

MAP-ApplicationContexts { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ApplicationContexts (2) version5 (5)} DEFINITIONS ::= BEGIN -- EXPORTS everything IMPORTS gsm-NetworkId, ac-Id FROM MobileDomainDefinitions { ccitt (0) identified-organization (4) etsi (0) mobileDomain (0) mobileDomainDefinitions (0) version1 (1)} ; -- application-context-names map-ac OBJECT IDENTIFIER ::= {gsm-NetworkId ac-Id}

networkLocUpContext-v3 OBJECT IDENTIFIER ::= {map-ac networkLocUp(1) version3(3)} locationCancellationContext-v3 OBJECT IDENTIFIER ::= {map-ac locationCancel(2) version3(3)} roamingNumberEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac roamingNbEnquiry(3) version3(3)} locationInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac locInfoRetrieval(5) version3(3)} resetContext-v2 OBJECT IDENTIFIER ::= {map-ac reset(10) version2(2)} handoverControlContext-v2 OBJECT IDENTIFIER ::= {map-ac handoverControl(11) version2(2)} equipmentMngtContext-v2 OBJECT IDENTIFIER ::= {map-ac equipmentMngt(13) version2(2)} infoRetrievalContext-v2 OBJECT IDENTIFIER ::= {map-ac infoRetrieval(14) version2(2)}

526

3GPP

527 Release 1998


51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122

265

3GPP TS 09.02 V7.15.0 (2004-03)

interVlrInfoRetrievalContext-v2 OBJECT IDENTIFIER ::= {map-ac interVlrInfoRetrieval(15) version2(2)} subscriberDataMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberDataMngt(16) version3(3)} tracingContext-v3 OBJECT IDENTIFIER ::= {map-ac tracing(17) version3(3)} networkFunctionalSsContext-v2 OBJECT IDENTIFIER ::= {map-ac networkFunctionalSs(18) version2(2)} networkUnstructuredSsContext-v2 OBJECT IDENTIFIER ::= {map-ac networkUnstructuredSs(19) version2(2)} shortMsgGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgGateway(20) version3(3)} shortMsgMO-RelayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMO-Relay(21) version3(3)} shortMsgAlertContext-v2 OBJECT IDENTIFIER ::= {map-ac shortMsgAlert(23) version2(2)} mwdMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac mwdMngt(24) version3(3)} shortMsgMT-RelayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMT-Relay(25) version3(3)} imsiRetrievalContext-v2 OBJECT IDENTIFIER ::= {map-ac imsiRetrieval(26) version2(2)} msPurgingContext-v3 OBJECT IDENTIFIER ::= {map-ac msPurging(27) version3(3)}

subscriberInfoEnquiryContext-v3 anyTimeInfoEnquiryContext-v3

OBJECT IDENTIFIER ::= {map-ac subscriberInfoEnquiry(28) version3(3)} OBJECT IDENTIFIER ::= {map-ac anyTimeInfoEnquiry(29) version3(3)}

callControlTransferContext-v4 OBJECT IDENTIFIER ::= {map-ac callControlTransfer(6) version4(4)} ss-InvocationNotificationContext-v3 OBJECT IDENTIFIER ::= {map-ac ss-InvocationNotification(36) version3(3)}

sIWFSAllocationContext-v3 OBJECT IDENTIFIER ::= {map-ac sIWFSAllocation(12) version3(3)}


groupCallControlContext-v3 OBJECT IDENTIFIER ::= {map-ac groupCallControl(31) version3(3)} gprsLocationUpdateContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsLocationUpdate(32) version3(3)} gprsLocationInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsLocationInfoRetrieval(33) version3(3)} failureReportContext-v3 OBJECT IDENTIFIER ::= {map-ac failureReport(34) version3(3)} gprsNotifyContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsNotify(35) version3(3)} reportingContext-v3 OBJECT IDENTIFIER ::= {map-ac reporting(7) version3(3)} callCompletionContext-v3 OBJECT IDENTIFIER ::= {map-ac callCompletion(8) version3(3)}

528

3GPP

529 Release 1998


123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163

266

3GPP TS 09.02 V7.15.0 (2004-03)

locationSvcGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcGateway(37) version3(3)} locationSvcEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcEnquiry(38) version3(3)} -- The following Object Identifiers are reserved for application-- contexts existing in previous versions of the protocol

-- AC Name & Version

--- networkLocUpContext-v1 -- networkLocUpContext-v2 -- locationCancellationContext-v1 -- locationCancellationContext-v2 -- roamingNumberEnquiryContext-v1 -- roamingNumberEnquiryContext-v2 -- locationInfoRetrievalContext-v1 -- locationInfoRetrievalContext-v2 -- resetContext-v1 -- handoverControlContext-v1 -- equipmentMngtContext-v1 -- infoRetrievalContext-v1 -- subscriberDataMngtContext-v1 -- subscriberDataMngtContext-v2 -- tracingContext-v1 -- tracingContext-v2 -- networkFunctionalSsContext-v1 -- shortMsgGatewayContext-v1 -- shortMsgGatewayContext-v2 -- shortMsgRelayContext-v1 -- shortMsgAlertContext-v1 -- mwdMngtContext-v1 -- mwdMngtContext-v2 -- shortMsgMT-RelayContext-v2 -- msPurgingContext-v2 -- callControlTransferContext-v3

Object Identifier
map-ac networkLocUp (1) map-ac networkLocUp (1) map-ac locationCancellation (2) map-ac locationCancellation (2) map-ac roamingNumberEnquiry (3) map-ac roamingNumberEnquiry (3) map-ac locationInfoRetrieval (5) map-ac locationInfoRetrieval (5) map-ac reset (10) map-ac handoverControl (11) map-ac equipmentMngt (13) map-ac infoRetrieval (14) map-ac subscriberDataMngt (16) map-ac subscriberDataMngt (16) map-ac tracing (17) map-ac tracing (17) map-ac networkFunctionalSs (18) map-ac shortMsgGateway (20) map-ac shortMsgGateway (20) map-ac shortMsgRelay (21) map-ac shortMsgAlert (23) map-ac mwdMngt (24) map-ac mwdMngt (24) map-ac shortMsgMT-Relay (25) map-ac msPurging (27) map-ac callControlTransferContext (6) version1 (1) version2 (2) version1 (1) version2 (2) version1 (1) version2 (2) version1 (1) version2 (2) version1 (1) version1 (1) version1 (1) version1 (1) version1 (1) version2 (2) version1 (1) version2 (2) version1 (1) version1 (1) version2 (2) version1 (1) version1 (1) version1 (1) version2 (2) version2 (2) version2 (2) version3 (3)

END

164
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

17.4 MAP Dialogue Information


MAP-DialogueInformation { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-DialogueInformation (3) version5 (5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS map-DialogueAS, MAP-DialoguePDU ; IMPORTS gsm-NetworkId, as-Id FROM MobileDomainDefinitions { ccitt (0) identified-organization (4) etsi (0) mobileDomain (0) mobileDomainDefinitions (0) version1 (1)} AddressString FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network(1) modules (3) map-CommonDataTypes (18) version5 (5)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version5 (5)}

530

3GPP

531 Release 1998


34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108

267

3GPP TS 09.02 V7.15.0 (2004-03)

; -- abstract syntax name for MAP-DialoguePDU map-DialogueAS OBJECT IDENTIFIER ::= {gsm-NetworkId as-Id map-DialoguePDU (1) version1 (1)} MAP-DialoguePDU ::= CHOICE { map-open map-accept map-close [2] MAP-CloseInfo, map-refuse map-userAbort map-providerAbort [0] MAP-OpenInfo, [1] MAP-AcceptInfo, [3] MAP-RefuseInfo, [4] MAP-UserAbortInfo, [5] MAP-ProviderAbortInfo} OPTIONAL, OPTIONAL, OPTIONAL

MAP-OpenInfo ::= SEQUENCE { destinationReference [0] AddressString originationReference [1] AddressString ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-AcceptInfo ::= SEQUENCE { ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-CloseInfo ::= SEQUENCE { ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-RefuseInfo ::= SEQUENCE { reason Reason, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } Reason ::= ENUMERATED { noReasonGiven (0), invalidDestinationReference invalidOriginatingReference

OPTIONAL

OPTIONAL

OPTIONAL

(1), (2)}

MAP-UserAbortInfo ::= SEQUENCE { map-UserAbortChoice MAP-UserAbortChoice, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-UserAbortChoice ::= CHOICE { userSpecificReason userResourceLimitation resourceUnavailable applicationProcedureCancellation [0] [1] [2] [3] NULL, NULL, ResourceUnavailableReason, ProcedureCancellationReason}

OPTIONAL

ResourceUnavailableReason ::= ENUMERATED { shortTermResourceLimitation (0), longTermResourceLimitation (1)} ProcedureCancellationReason ::= ENUMERATED { handoverCancellation (0), radioChannelRelease (1), networkPathRelease (2), callRelease (3), associatedProcedureFailure (4), tandemDialogueRelease (5), remoteOperationsFailure (6)}

532

3GPP

533 Release 1998


109 110 111 112 113 114 115 116 117 118 119 120

268

3GPP TS 09.02 V7.15.0 (2004-03)

MAP-ProviderAbortInfo ::= SEQUENCE { map-ProviderAbortReason MAP-ProviderAbortReason, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-ProviderAbortReason ::= ENUMERATED { abnormalDialogue (0), invalidPDU (1)} END

OPTIONAL

121
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

17.5 MAP operation and error codes


MAP-Protocol { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Protocol (4) version5 (5)} DEFINITIONS ::= BEGIN IMPORTS UpdateLocation, CancelLocation, PurgeMS, SendIdentification, UpdateGprsLocation, PrepareHandover, SendEndSignal, ProcessAccessSignalling, ForwardAccessSignalling, PrepareSubsequentHandover, SendAuthenticationInfo, CheckIMEI, InsertSubscriberData, DeleteSubscriberData, Reset, ForwardCheckSS-Indication, RestoreData, ProvideSubscriberInfo, AnyTimeInterrogation, SendRoutingInfoForGprs, FailureReport, NoteMsPresentForGprs FROM MAP-MobileServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version5 (5)} ActivateTraceMode, DeactivateTraceMode, SendIMSI FROM MAP-OperationAndMaintenanceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version5 (5)} SendRoutingInfo, ProvideRoamingNumber, ResumeCallHandling, ProvideSIWFSNumber, SIWFSSignallingModify, SetReportingState, StatusReport, RemoteUserFree FROM MAP-CallHandlingOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version5 (5)} RegisterSS, EraseSS,

534

3GPP

535 Release 1998


64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142

269

3GPP TS 09.02 V7.15.0 (2004-03)

ActivateSS, DeactivateSS, InterrogateSS, ProcessUnstructuredSS-Request, UnstructuredSS-Request, UnstructuredSS-Notify, RegisterPassword, GetPassword, SS-InvocationNotification, RegisterCC-Entry, EraseCC-Entry FROM MAP-SupplementaryServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version5 (5)} SendRoutingInfoForSM, MO-ForwardSM, MT-ForwardSM, ReportSM-DeliveryStatus, AlertServiceCentre, InformServiceCentre, ReadyForSM FROM MAP-ShortMessageServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) version5 (5)} PrepareGroupCall, ProcessGroupCallSignalling, ForwardGroupCallSignalling, SendGroupCallEndSignal FROM MAP-Group-Call-Operations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Group-Call-Operations (22) version5 (5)} ProvideSubscriberLocation, SendRoutingInfoForLCS, SubscriberLocationReport FROM MAP-LocationServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version5 (5)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, RoamingNotAllowed, IllegalSubscriber, IllegalEquipment, BearerServiceNotProvisioned, TeleserviceNotProvisioned, NoHandoverNumberAvailable, SubsequentHandoverFailure, TracingBufferFull, OR-NotAllowed, NoRoamingNumberAvailable, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, ATI-NotAllowed, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy,

536

3GPP

537 Release 1998


143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216

270

3GPP TS 09.02 V7.15.0 (2004-03)

PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM, ResourceLimitation, NoGroupCallNumberAvailable, ShortTermDenial, LongTermDenial, IncompatibleTerminal, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, UnknownOrUnreachableLCSClient FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} ; -- location registration operation codes updateLocation UpdateLocation ::= localValue 2 cancelLocation CancelLocation ::= localValue 3 purgeMS PurgeMS ::= localValue 67 sendIdentification SendIdentification ::= localValue 55 -- handover operation codes prepareHandover PrepareHandover ::= localValue 68 sendEndSignal SendEndSignal ::= localValue 29 processAccessSignalling ProcessAccessSignalling ::= localValue 33 forwardAccessSignalling ForwardAccessSignalling ::= localValue 34 prepareSubsequentHandover PrepareSubsequentHandover ::= localValue 69 -- authentication operation codes sendAuthenticationInfo SendAuthenticationInfo ::= localValue 56

-- IMEI MANAGEMENT operation codes checkIMEI CheckIMEI ::= localValue 43

-- subscriber management operation codes insertSubscriberData deleteSubscriberData InsertSubscriberData ::= localValue 7 DeleteSubscriberData ::= localValue 8

-- fault recovery operation codes


reset Reset ::= localValue 37 forwardCheckSS-Indication ForwardCheckSS-Indication ::= localValue 38 restoreData RestoreData ::= localValue 57 -- operation and maintenance operation codes activateTraceMode ActivateTraceMode ::= localValue 50 deactivateTraceMode DeactivateTraceMode ::= localValue 51 sendIMSI SendIMSI ::= localValue 58 -- call handling operation codes

538

3GPP

539 Release 1998


217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290

271

3GPP TS 09.02 V7.15.0 (2004-03)

sendRoutingInfo SendRoutingInfo ::= localValue 22 provideRoamingNumber ProvideRoamingNumber ::= localValue 4 resumeCallHandling ResumeCallHandling ::= localValue 6 provideSIWFSNumber ProvideSIWFSNumber ::= localValue 31 sIWFSSignallingModify SIWFSSignallingModify ::= localValue 32 setReportingState SetReportingState ::= localValue 73 statusReport StatusReport ::= localValue 74 remoteUserFree RemoteUserFree ::= localValue 75 -- supplementary service handling operation codes registerSS RegisterSS ::= localValue 10 eraseSS EraseSS ::= localValue 11 activateSS ActivateSS ::= localValue 12 deactivateSS DeactivateSS ::= localValue 13 interrogateSS InterrogateSS ::= localValue 14 processUnstructuredSS-Request ProcessUnstructuredSS-Request ::= localValue 59 unstructuredSS-Request UnstructuredSS-Request ::= localValue 60 unstructuredSS-Notify UnstructuredSS-Notify ::= localValue 61 registerPassword RegisterPassword ::= localValue 17 getPassword GetPassword ::= localValue 18 registerCC-Entry RegisterCC-Entry ::= localValue 76 eraseCC-Entry EraseCC-Entry ::= localValue 77 -- short message service operation codes sendRoutingInfoForSM SendRoutingInfoForSM ::= localValue 45 mo-forwardSM MO-ForwardSM ::= localValue 46 mt-forwardSM MT-ForwardSM ::= localValue 44 reportSM-DeliveryStatus ReportSM-DeliveryStatus ::= localValue 47 informServiceCentre InformServiceCentre ::= localValue 63 alertServiceCentre AlertServiceCentre ::= localValue 64 readyForSM ReadyForSM ::= localValue 66 -- provide subscriber info operation codes

provideSubscriberInfo

ProvideSubscriberInfo ::= localValue 70

-- any time interrogation operation codes

anyTimeInterrogation

AnyTimeInterrogation ::= localValue 71

-- supplementary service invocation notification operation codes

ss-InvocationNotification
--Group Call operation codes

SS-InvocationNotification ::= localValue 72

prepareGroupCall PrepareGroupCall ::= localValue 39 sendGroupCallEndSignal SendGroupCallEndSignal ::= localValue 40 processGroupCallSignalling ProcessGroupCallSignalling ::= localValue 41 forwardGroupCallSignalling ForwardGroupCallSignalling ::= localValue 42 -- gprs location updating operation codes

updateGprsLocation

UpdateGprsLocation ::= localValue 23

-- gprs location information retrieval operation codes

sendRoutingInfoForGprs

SendRoutingInfoForGprs ::= localValue 24

-- failure reporting operation codes

failureReport

FailureReport ::= localValue 25

-- GPRS notification operation codes

noteMsPresentForGprs

NoteMsPresentForGprs ::= localValue 26

540

3GPP

541 Release 1998


291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363

272

3GPP TS 09.02 V7.15.0 (2004-03)

-- Location service operation codes provideSubscriberLocation ProvideSubscriberLocation ::= localValue 83 sendRoutingInfoForLCS SendRoutingInfoForLCS ::= localValue 85 subscriberLocationReport SubscriberLocationReport ::= localValue 86 -- generic error codes systemFailure SystemFailure ::= localValue 34 dataMissing DataMissing ::= localValue 35 unexpectedDataValue UnexpectedDataValue ::= localValue 36 facilityNotSupported FacilityNotSupported ::= localValue 21 incompatibleTerminal IncompatibleTerminal ::= localValue 28 resourceLimitation ResourceLimitation ::= localValue 51 -- identification and numbering error codes unknownSubscriber UnknownSubscriber ::= localValue 1 numberChanged NumberChanged ::= localValue 44 unknownMSC UnknownMSC ::= localValue 3 unidentifiedSubscriber UnidentifiedSubscriber ::= localValue 5 unknownEquipment UnknownEquipment ::= localValue 7 -- subscription error codes roamingNotAllowed RoamingNotAllowed ::= localValue 8 illegalSubscriber IllegalSubscriber ::= localValue 9 illegalEquipment IllegalEquipment ::= localValue 12 bearerServiceNotProvisioned BearerServiceNotProvisioned ::= localValue 10 teleserviceNotProvisioned TeleserviceNotProvisioned ::= localValue 11 -- handover error codes noHandoverNumberAvailable localValue 25 subsequentHandoverFailure localValue 26 NoHandoverNumberAvailable ::= SubsequentHandoverFailure ::=

-- operation and maintenance error codes tracingBufferFull TracingBufferFull ::= localValue 40

hn -d a
noRoamingNumberAvailable NoRoamingNumberAvailable ::= localValue 39 absentSubscriber AbsentSubscriber ::= localValue 27 busySubscriber BusySubscriber ::= localValue 45 noSubscriberReply NoSubscriberReply ::= localValue 46 callBarred CallBarred ::= localValue 13 forwardingFailed ForwardingFailed ::= localValue 47 or-NotAllowed OR-NotAllowed ::= localValue 48 forwardingViolation ForwardingViolation ::= localValue 14 cug-Reject CUG-Reject ::= localValue 15 -- any time interrogation error codes ati-NotAllowed ATI-NotAllowed ::= localValue 49 -- Group Call error codes noGroupCallNumberAvailable

NoGroupCallNumberAvailable ::= localValue 50

-- supplementary service error codes

542

3GPP

543 Release 1998


364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419

273

3GPP TS 09.02 V7.15.0 (2004-03)

illegalSS-Operation IllegalSS-Operation ::= localValue 16 ss-ErrorStatus SS-ErrorStatus ::= localValue 17 ss-NotAvailable SS-NotAvailable ::= localValue 18 ss-SubscriptionViolation SS-SubscriptionViolation ::= localValue 19 ss-Incompatibility SS-Incompatibility ::= localValue 20 unknownAlphabet UnknownAlphabet ::= localValue 71 ussd-Busy USSD-Busy ::= localValue 72 pw-RegistrationFailure PW-RegistrationFailure ::= localValue 37 negativePW-Check NegativePW-Check ::= localValue 38 numberOfPW-AttemptsViolation NumberOfPW-AttemptsViolation ::= localValue 43 shortTermDenial ShortTermDenial ::= localValue 29 longTermDenial LongTermDenial ::= localValue 30 -- short message service error codes subscriberBusyForMT-SMS SubscriberBusyForMT-SMS ::= localValue 31 sm-DeliveryFailure SM-DeliveryFailure ::= localValue 32 messageWaitingListFull MessageWaitingListFull ::= localValue 33 absentsubscriberSM AbsentSubscriberSM ::= localValue 6 -- location service error codes unauthorizedRequestingNetwork UnauthorizedRequestingNetwork::= localValue 52 unauthorizedLCSClient UnauthorizedLCSClient ::= localValue 53 positionMethodFailure PositionMethodFailure ::= localValue 54 unknownOrUnreachableLCSClient UnknownOrUnreachableLCSClient ::= localValue 58

-- The following operation codes are reserved for operations -- existing in previous versions of the protocol -- Operation Name --- sendParameters -- processUnstructuredSS-Data -- performHandover -- performSubsequentHandover -- noteInternalHandover -- noteSubscriberPresent -- alertServiceCentreWithoutResult -- traceSubscriberActivity -- beginSubscriberActivity AC used map-ac infoRetrieval (14) version1 (1) map-ac networkFunctionalSs (18) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac mwdMngt (24) version1 (1) map-ac shortMsgAlert (23) version1 (1) map-ac handoverControl (11) version1 (1) map-ac networkFunctionalSs (18) version1 (1) Oper. Code localValue 9 localValue 19 localValue 28 localValue 30 localValue 35 localValue 48 localValue 49 localValue 52 localValue 54

-- The following error codes are reserved for errors -- existing in previous versions of the protocol -- Error Name --- unknownBaseStation -- invalidTargetBaseStation -- noRadioResourceAvailable END AC used map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) Error Code localValue 2 localValue 23 localValue 24

420 421
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

17.6 MAP operation and error types


17.6.1 Mobile Service Operations
MAP-MobileServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS -- location registration operations UpdateLocation,

544

3GPP

545 Release 1998


16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94

274

3GPP TS 09.02 V7.15.0 (2004-03)

CancelLocation, PurgeMS, SendIdentification, -- gprs location registration operations UpdateGprsLocation, -- subscriber information enquiry operations ProvideSubscriberInfo, -- any time information enquiry operations AnyTimeInterrogation, -- handover operations PrepareHandover, SendEndSignal, ProcessAccessSignalling, ForwardAccessSignalling, PrepareSubsequentHandover, -- authentication management operations SendAuthenticationInfo, -- IMEI management operations CheckIMEI, -- subscriber management operations InsertSubscriberData, DeleteSubscriberData, -- fault recovery operations Reset, ForwardCheckSS-Indication, RestoreData, -- gprs location information retrieval operations SendRoutingInfoForGprs, -- failure reporting operations FailureReport, -- gprs notification operations NoteMsPresentForGprs

; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, RoamingNotAllowed, ATI-NotAllowed, NoHandoverNumberAvailable, SubsequentHandoverFailure, AbsentSubscriber FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes,

546

3GPP

547 Release 1998


95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166

275

3GPP TS 09.02 V7.15.0 (2004-03)

PrepareHO-Arg, PrepareHO-Res, PrepareSubsequentHO-Arg, SendAuthenticationInfoArg, SendAuthenticationInfoRes, EquipmentStatus, InsertSubscriberDataArg, InsertSubscriberDataRes, DeleteSubscriberDataArg, DeleteSubscriberDataRes, ResetArg, RestoreDataArg, RestoreDataRes, ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, AnyTimeInterrogationArg, AnyTimeInterrogationRes, SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, FailureReportArg, FailureReportRes, NoteMsPresentForGprsArg, NoteMsPresentForGprsRes FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version5 (5)} ExternalSignalInfo, TMSI, IMEI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} ; -- location registration operations UpdateLocation ::= OPERATION ARGUMENT updateLocationArg RESULT updateLocationRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, RoamingNotAllowed} CancelLocation ::= OPERATION ARGUMENT cancelLocationArg RESULT cancelLocationRes -- optional ERRORS { DataMissing, UnexpectedDataValue} PurgeMS ::= OPERATION ARGUMENT purgeMS-Arg RESULT purgeMS-Res -- optional ERRORS{ DataMissing, UnexpectedDataValue, UnknownSubscriber} --Timer m UpdateLocationArg UpdateLocationRes

--Timer m CancelLocationArg CancelLocationRes

--Timer m PurgeMS-Arg PurgeMS-Res

548

3GPP

549 Release 1998


167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239

276

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer s

SendIdentification ::= OPERATION ARGUMENT tmsi RESULT sendIdentificationRes ERRORS { DataMissing, UnidentifiedSubscriber} -- gprs location registration operations UpdateGprsLocation ::= OPERATION ARGUMENT updateGprsLocationArg RESULT updateGprsLocationRes ERRORS { SystemFailure, UnexpectedDataValue, UnknownSubscriber, RoamingNotAllowed}

TMSI SendIdentificationRes

--Timer m UpdateGprsLocationArg UpdateGprsLocationRes

-- subscriber information enquiry operations

ProvideSubscriberInfo ::= OPERATION


ARGUMENT provideSubscriberInfoArg RESULT provideSubscriberInfoRes ERRORS { DataMissing, UnexpectedDataValue} ProvideSubscriberInfoArg ProvideSubscriberInfoRes

--Timer m

-- any time information enquiry operations

AnyTimeInterrogation ::= OPERATION


ARGUMENT anyTimeInterrogationArg RESULT anyTimeInterrogationRes ERRORS { SystemFailure, ATI-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber} AnyTimeInterrogationArg AnyTimeInterrogationRes

--Timer m

-- handover operations PrepareHandover ::= OPERATION ARGUMENT prepareHO-Arg RESULT prepareHO-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, NoHandoverNumberAvailable} SendEndSignal ::= OPERATION ARGUMENT bss-APDU RESULT ProcessAccessSignalling ::= OPERATION ARGUMENT bss-APDU ForwardAccessSignalling ::= OPERATION ARGUMENT bss-APDU --Timer m PrepareHO-Arg PrepareHO-Res

--Timer l ExternalSignalInfo --Timer s ExternalSignalInfo --Timer s ExternalSignalInfo

550

3GPP

551 Release 1998


240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308

277
--Timer m PrepareSubsequentHO-Arg ExternalSignalInfo

3GPP TS 09.02 V7.15.0 (2004-03)

PrepareSubsequentHandover ::= OPERATION ARGUMENT prepareSubsequentHO-Arg RESULT bss-APDU ERRORS { UnexpectedDataValue, DataMissing, UnknownMSC, SubsequentHandoverFailure} -- authentication management operations SendAuthenticationInfo ::= OPERATION ARGUMENT sendAuthenticationInfoArg RESULT sendAuthenticationInfoRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} -- IMEI management operations CheckIMEI ::= OPERATION ARGUMENT imei RESULT equipmentStatus ERRORS { SystemFailure, DataMissing, UnknownEquipment} -- subscriber management operations InsertSubscriberData ::= OPERATION ARGUMENT insertSubscriberDataArg RESULT insertSubscriberDataRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnidentifiedSubscriber} DeleteSubscriberData ::= OPERATION ARGUMENT deleteSubscriberDataArg RESULT deleteSubscriberDataRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnidentifiedSubscriber} -- fault recovery operations Reset ::= OPERATION ARGUMENT resetArg ForwardCheckSS-Indication ::= OPERATION

--Timer m SendAuthenticationInfoArg SendAuthenticationInfoRes

--Timer m IMEI EquipmentStatus

--Timer m InsertSubscriberDataArg InsertSubscriberDataRes

--Timer m DeleteSubscriberDataArg DeleteSubscriberDataRes

--Timer m ResetArg --Timer s

552

3GPP

553 Release 1998


309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363

278

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer m

RestoreData ::= OPERATION ARGUMENT restoreDataArg RESULT restoreDataRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber}

RestoreDataArg RestoreDataRes

-- gprs location information retrieval operations SendRoutingInfoForGprs ::= OPERATION ARGUMENT sendRoutingInfoForGprsArg RESULT sendRoutingInfoForGprsRes ERRORS { AbsentSubscriber, SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} -- failure reporting operations FailureReport ::= OPERATION ARGUMENT failureReportArg RESULT failureReportRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} -- gprs notification operations NoteMsPresentForGprs ::= OPERATION ARGUMENT noteMsPresentForGprsArg RESULT noteMsPresentForGprsRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} END --Timer m NoteMsPresentForGprsArg NoteMsPresentForGprsRes --Timer m FailureReportArg FailureReportRes --Timer m SendRoutingInfoForGprsArg SendRoutingInfoForGprsRes

364
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

17.6.2 Operation and Maintenance Operations


MAP-OperationAndMaintenanceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS ActivateTraceMode, DeactivateTraceMode, SendIMSI ; IMPORTS OPERATION FROM TCAPMessages {

554

3GPP

555 Release 1998


21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87

279

3GPP TS 09.02 V7.15.0 (2004-03)

ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, UnidentifiedSubscriber, TracingBufferFull FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} ActivateTraceModeArg, ActivateTraceModeRes, DeactivateTraceModeArg, DeactivateTraceModeRes FROM MAP-OM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version5 (5)} ISDN-AddressString, IMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} ; ActivateTraceMode ::= OPERATION ARGUMENT activateTraceModeArg RESULT activateTraceModeRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, TracingBufferFull} DeactivateTraceMode ::= OPERATION ARGUMENT deactivateTraceModeArg RESULT deactivateTraceModeRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber} SendIMSI ::= OPERATION ARGUMENT msisdn RESULT imsi ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber} END --Timer m ActivateTraceModeArg ActivateTraceModeRes

--Timer m DeactivateTraceModeArg DeactivateTraceModeRes

--Timer m ISDN-AddressString IMSI

88
1 2 3 4 5 6 7 8

17.6.3 Call Handling Operations


MAP-CallHandlingOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version5 (5)} DEFINITIONS ::=

556

3GPP

557 Release 1998


9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73

280

3GPP TS 09.02 V7.15.0 (2004-03)

BEGIN EXPORTS SendRoutingInfo, ProvideRoamingNumber, ResumeCallHandling, ProvideSIWFSNumber, SIWFSSignallingModify, SetReportingState, StatusReport, RemoteUserFree ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, UnknownSubscriber, NumberChanged, BearerServiceNotProvisioned, TeleserviceNotProvisioned, NoRoamingNumberAvailable, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, ResourceLimitation, IncompatibleTerminal, UnidentifiedSubscriber FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg, ResumeCallHandlingRes, ProvideSIWFSNumberArg, ProvideSIWFSNumberRes, SIWFSSignallingModifyArg, SIWFSSignallingModifyRes, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes FROM MAP-CH-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CH-DataTypes (13) version5 (5)} ;

558

3GPP

559 Release 1998


74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144

281

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer m

SendRoutingInfo ::= OPERATION ARGUMENT sendRoutingInfoArg RESULT sendRoutingInfoRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, UnknownSubscriber, NumberChanged, BearerServiceNotProvisioned, TeleserviceNotProvisioned, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, CUG-Reject, ForwardingViolation} ProvideRoamingNumber ::= OPERATION ARGUMENT provideRoamingNumberArg RESULT provideRoamingNumberRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, AbsentSubscriber, NoRoamingNumberAvailable} ResumeCallHandling ::= OPERATION ARGUMENT resumeCallHandlingArg RESULT resumeCallHandlingRes -- optional ERRORS { ForwardingFailed, OR-NotAllowed, UnexpectedDataValue, DataMissing } ProvideSIWFSNumber ::= OPERATION ARGUMENT provideSIWFSNumberArg RESULT provideSIWFSNumberRes ERRORS { ResourceLimitation, DataMissing, UnexpectedDataValue, SystemFailure} SIWFSSignallingModify ::= OPERATION ARGUMENT sIWFSSignallingModifyArg RESULT sIWFSSignallingModifyRes -- optional ERRORS { ResourceLimitation, DataMissing, UnexpectedDataValue, SystemFailure}

SendRoutingInfoArg SendRoutingInfoRes

--Timer m ProvideRoamingNumberArg ProvideRoamingNumberRes

--Timer m ResumeCallHandlingArg ResumeCallHandlingRes

--Timer m ProvideSIWFSNumberArg ProvideSIWFSNumberRes

--Timer m SIWFSSignallingModifyArg SIWFSSignallingModifyRes

560

3GPP

561 Release 1998


145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184

282

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer m

SetReportingState ::= OPERATION ARGUMENT setReportingStateArg RESULT setReportingStateRes -- optional ERRORS { SystemFailure, UnidentifiedSubscriber, UnexpectedDataValue, DataMissing, ResourceLimitation, FacilityNotSupported} StatusReport ::= OPERATION ARGUMENT statusReportArg RESULT statusReportRes -- optional ERRORS { UnknownSubscriber, SystemFailure, UnexpectedDataValue, DataMissing} RemoteUserFree ::= OPERATION ARGUMENT remoteUserFreeArg RESULT remoteUserFreeRes ERRORS { UnexpectedDataValue, DataMissing, IncompatibleTerminal, AbsentSubscriber, SystemFailure, BusySubscriber} END

SetReportingStateArg SetReportingStateRes

--Timer m StatusReportArg StatusReportRes

--Timer ml RemoteUserFreeArg RemoteUserFreeRes

185
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35

17.6.4 Supplementary service operations


MAP-SupplementaryServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS RegisterSS, EraseSS, ActivateSS, DeactivateSS, InterrogateSS, ProcessUnstructuredSS-Request, UnstructuredSS-Request, UnstructuredSS-Notify, RegisterPassword, GetPassword, SS-InvocationNotification, RegisterCC-Entry, EraseCC-Entry ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue,

562

3GPP

563 Release 1998


36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103

283

3GPP TS 09.02 V7.15.0 (2004-03)

UnknownSubscriber, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, UnknownAlphabet, USSD-Busy, AbsentSubscriber, IllegalSubscriber, IllegalEquipment, ShortTermDenial, LongTermDenial, FacilityNotSupported FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} RegisterSS-Arg, SS-Info, SS-ForBS-Code, InterrogateSS-Res, USSD-Arg, USSD-Res, Password, GuidanceInfo, SS-InvocationNotificationArg, SS-InvocationNotificationRes, RegisterCC-EntryArg, RegisterCC-EntryRes, EraseCC-EntryArg, EraseCC-EntryRes FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version5 (5)} SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version5 (5)} ; -- supplementary service handling operations RegisterSS ::= OPERATION ARGUMENT registerSS-Arg RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-Incompatibility} --Timer m RegisterSS-Arg SS-Info

564

3GPP

565 Release 1998


104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174

284

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer m

EraseSS ::= OPERATION ARGUMENT ss-ForBS RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus } ActivateSS ::= OPERATION ARGUMENT ss-ForBS RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-SubscriptionViolation, SS-Incompatibility, NegativePW-Check, NumberOfPW-AttemptsViolation} DeactivateSS ::= OPERATION ARGUMENT ss-ForBS RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-SubscriptionViolation, NegativePW-Check, NumberOfPW-AttemptsViolation} InterrogateSS ::= OPERATION ARGUMENT ss-ForBS RESULT interrogateSS-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-NotAvailable}

SS-ForBS-Code SS-Info

--Timer m SS-ForBS-Code SS-Info

--Timer m SS-ForBS-Code SS-Info

--Timer m SS-ForBS-Code InterrogateSS-Res

566

3GPP

567 Release 1998


175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250

285

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer 10 minutes

ProcessUnstructuredSS-Request ::= OPERATION ARGUMENT ussd-Arg USSD-Arg RESULT ussd-Res USSD-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownAlphabet, CallBarred} UnstructuredSS-Request ::= OPERATION ARGUMENT ussd-Arg RESULT ussd-Res -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, AbsentSubscriber, IllegalSubscriber, IllegalEquipment, UnknownAlphabet, USSD-Busy} UnstructuredSS-Notify ::= OPERATION ARGUMENT ussd-Arg RESULT ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, AbsentSubscriber, IllegalSubscriber, IllegalEquipment, UnknownAlphabet, USSD-Busy} RegisterPassword ::= OPERATION ARGUMENT ss-Code RESULT newPassword ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, CallBarred, SS-SubscriptionViolation, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation} LINKED { GetPassword} GetPassword ::= OPERATION ARGUMENT guidanceInfo RESULT currentPassword SS-InvocationNotification ::= OPERATION ARGUMENT ss-InvocationNotificationArg RESULT ss-InvocationNotificationRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber}

--Timer ml USSD-Arg USSD-Res

--Timer ml USSD-Arg

--Timer ml SS-Code Password

--Timer m GuidanceInfo Password --Timer m SS-InvocationNotificationArg SS-InvocationNotificationRes

568

3GPP

569 Release 1998


251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281

286

3GPP TS 09.02 V7.15.0 (2004-03)


--Timer m

RegisterCC-Entry ::= OPERATION ARGUMENT registerCC-EntryArg RESULT registerCC-EntryRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-Incompatibility, ShortTermDenial, LongTermDenial, FacilityNotSupported} EraseCC-Entry ::= OPERATION ARGUMENT eraseCC-EntryArg RESULT eraseCC-EntryRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, CallBarred, IllegalSS-Operation, SS-ErrorStatus} END

RegisterCC-EntryArg RegisterCC-EntryRes

--Timer m EraseCC-EntryArg EraseCC-EntryRes

282
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

17.6.5 Short message service operations


MAP-ShortMessageServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS SendRoutingInfoForSM, MO-ForwardSM, MT-ForwardSM, ReportSM-DeliveryStatus, AlertServiceCentre, InformServiceCentre, ReadyForSM ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, TeleserviceNotProvisioned, AbsentSubscriber, CallBarred, SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)}

570

3GPP

571 Release 1998


45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111

287

3GPP TS 09.02 V7.15.0 (2004-03)

RoutingInfoForSM-Arg, RoutingInfoForSM-Res, MO-ForwardSM-Arg, MO-ForwardSM-Res, MT-ForwardSM-Arg, MT-ForwardSM-Res, ReportSM-DeliveryStatusArg, ReportSM-DeliveryStatusRes, AlertServiceCentreArg, InformServiceCentreArg, ReadyForSM-Arg, ReadyForSM-Res FROM MAP-SM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version5 (5)}

; SendRoutingInfoForSM ::= OPERATION ARGUMENT routingInfoForSM-Arg RESULT routingInfoForSM-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, TeleserviceNotProvisioned, CallBarred, AbsentSubscriberSM} MO-ForwardSM ::= OPERATION ARGUMENT mo-forwardSM-Arg RESULT mo-forwardSM-Res -- optional ERRORS { SystemFailure, UnexpectedDataValue, FacilityNotSupported, SM-DeliveryFailure} MT-ForwardSM ::= OPERATION ARGUMENT mt-forwardSM-Arg RESULT mt-forwardSM-Res -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, SubscriberBusyForMT-SMS, SM-DeliveryFailure, AbsentSubscriberSM} --Timer m RoutingInfoForSM-Arg RoutingInfoForSM-Res

--Timer ml MO-ForwardSM-Arg MO-ForwardSM-Res

--Timer ml MT-ForwardSM-Arg MT-ForwardSM-Res

572

3GPP

573 Release 1998


112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149

288
--Timer s ReportSM-DeliveryStatusArg ReportSM-DeliveryStatusRes

3GPP TS 09.02 V7.15.0 (2004-03)

ReportSM-DeliveryStatus ::= OPERATION ARGUMENT reportSM-DeliveryStatusArg RESULT reportSM-DeliveryStatusRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber, MessageWaitingListFull} AlertServiceCentre ::= OPERATION ARGUMENT alertServiceCentreArg RESULT ERRORS { SystemFailure, DataMissing, UnexpectedDataValue} InformServiceCentre ::= OPERATION ARGUMENT informServiceCentreArg ReadyForSM ::= OPERATION ARGUMENT readyForSM-Arg RESULT readyForSM-Res -- optional ERRORS { DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber} END

--Timer s AlertServiceCentreArg

--Timer s InformServiceCentreArg --Timer m ReadyForSM-Arg ReadyForSM-Res

150
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

17.6.6 Errors
MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS -- generic errors SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, IncompatibleTerminal, ResourceLimitation, -- identification and numbering errors UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, -- subscription errors RoamingNotAllowed, IllegalSubscriber, IllegalEquipment, BearerServiceNotProvisioned, TeleserviceNotProvisioned, -- handover errors NoHandoverNumberAvailable, SubsequentHandoverFailure,

574

3GPP

575 Release 1998


38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116

289

3GPP TS 09.02 V7.15.0 (2004-03)

-- operation and maintenance errors TracingBufferFull, -- call handling errors OR-NotAllowed, NoRoamingNumberAvailable, BusySubscriber, NoSubscriberReply, AbsentSubscriber, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, -- any time interrogation errors ATI-NotAllowed, -- supplementary service errors IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, ShortTermDenial, LongTermDenial, -- short message service errors SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM, -- Group Call errors NoGroupCallNumberAvailable, -- location service errors UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, UnknownOrUnreachableLCSClient ; IMPORTS ERROR FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SS-Status FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version5 (5)} SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, RoamingNotAllowedParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam, TracingBufferFullParam, NoRoamingNbParam, OR-NotAllowedParam, AbsentSubscriberParam, BusySubscriberParam,

576

3GPP

577 Release 1998


117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192

290

3GPP TS 09.02 V7.15.0 (2004-03)

NoSubscriberReplyParam, CallBarredParam, ForwardingViolationParam, ForwardingFailedParam, CUG-RejectParam, ATI-NotAllowedParam, SubBusyForMT-SMS-Param, MessageWaitListFullParam, AbsentSubscriberSM-Param, ResourceLimitationParam, NoGroupCallNbParam, IncompatibleTerminalParam, ShortTermDenialParam, LongTermDenialParam, UnauthorizedRequestingNetwork-Param, UnauthorizedLCSClient-Param, PositionMethodFailure-Param, UnknownOrUnreachableLCSClient-Param FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version5 (5)} ; -- generic errors SystemFailure ::= ERROR PARAMETER systemFailureParam -- optional

SystemFailureParam

DataMissing ::= ERROR PARAMETER dataMissingParam DataMissingParam -- optional -- dataMissingParam must not be used in version <3 UnexpectedDataValue ::= ERROR PARAMETER unexpectedDataParam UnexpectedDataParam -- optional -- unexpectedDataParam must not be used in version <3 FacilityNotSupported ::= ERROR PARAMETER facilityNotSupParam FacilityNotSupParam -- optional -- facilityNotSupParam must not be used in version <3 IncompatibleTerminal ::= ERROR PARAMETER incompatibleTerminalParam -- optional ResourceLimitation ::= ERROR PARAMETER resourceLimitationParam -- optional -- identification and numbering errors UnknownSubscriber ::= ERROR PARAMETER unknownSubscriberParam UnknownSubscriberParam -- optional -- unknownSubscriberParam must not be used in version <3 NumberChanged ::= ERROR PARAMETER numberChangedParam -- optional UnknownMSC ::= ERROR

IncompatibleTerminalParam

ResourceLimitationParam

NumberChangedParam

578

3GPP

579 Release 1998


193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266

291

3GPP TS 09.02 V7.15.0 (2004-03)

UnidentifiedSubscriber ::= ERROR PARAMETER unidentifiedSubParam UnidentifiedSubParam -- optional -- unidentifiedSubParam must not be used in version <3 UnknownEquipment ::= ERROR -- subscription errors RoamingNotAllowed ::= ERROR PARAMETER roamingNotAllowedParam

RoamingNotAllowedParam

IllegalSubscriber ::= ERROR PARAMETER illegalSubscriberParam IllegalSubscriberParam -- optional -- illegalSubscriberParam must not be used in version <3 IllegalEquipment ::= ERROR PARAMETER illegalEquipmentParam IllegalEquipmentParam -- optional -- illegalEquipmentParam must not be used in version <3 BearerServiceNotProvisioned ::= ERROR PARAMETER bearerServNotProvParam BearerServNotProvParam -- optional -- bearerServNotProvParam must not be used in version <3 TeleserviceNotProvisioned ::= ERROR PARAMETER teleservNotProvParam TeleservNotProvParam -- optional -- teleservNotProvParam must not be used in version <3 -- handover errors NoHandoverNumberAvailable ::= ERROR SubsequentHandoverFailure ::= ERROR -- operation and maintenance errors TracingBufferFull ::= ERROR PARAMETER tracingBufferFullParam -- optional -- call handling errors NoRoamingNumberAvailable ::= ERROR PARAMETER noRoamingNbParam -- optional AbsentSubscriber ::= ERROR PARAMETER absentSubscriberParam -- optional

TracingBufferFullParam

NoRoamingNbParam

AbsentSubscriberParam

-- absentSubscriberParam must not be used in version <3 BusySubscriber ::= ERROR PARAMETER busySubscriberParam -- optional

BusySubscriberParam

580

3GPP

581 Release 1998


267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339

292

3GPP TS 09.02 V7.15.0 (2004-03)

NoSubscriberReply ::= ERROR PARAMETER noSubscriberReplyParam -- optional CallBarred ::= ERROR PARAMETER callBarredParam -- optional ForwardingViolation ::= ERROR PARAMETER forwardingViolationParam -- optional ForwardingFailed ::= ERROR PARAMETER forwardingFailedParam -- optional CUG-Reject ::= ERROR PARAMETER cug-RejectParam -- optional OR-NotAllowed ::= ERROR PARAMETER or-NotAllowedParam -- optional -- any time interrogation errors ATI-NotAllowed ::= ERROR PARAMETER ati-NotAllowedParam -- optional -- supplementary service errors IllegalSS-Operation ::= ERROR SS-ErrorStatus ::= ERROR PARAMETER ss-Status -- optional SS-NotAvailable ::= ERROR SS-SubscriptionViolation ::= ERROR SS-Incompatibility ::= ERROR PARAMETER ss-IncompatibilityCause -- optional UnknownAlphabet ::= ERROR USSD-Busy ::= ERROR PW-RegistrationFailure ::= ERROR PARAMETER pw-RegistrationFailureCause NegativePW-Check ::= ERROR NumberOfPW-AttemptsViolation ::= ERROR ShortTermDenial ::= ERROR PARAMETER shortTermDenialParam -- optional

NoSubscriberReplyParam

CallBarredParam

ForwardingViolationParam

ForwardingFailedParam

CUG-RejectParam

OR-NotAllowedParam

ATI-NotAllowedParam

SS-Status

SS-IncompatibilityCause

PW-RegistrationFailureCause

ShortTermDenialParam

582

3GPP

583 Release 1998


340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396

293

3GPP TS 09.02 V7.15.0 (2004-03)

LongTermDenial ::= ERROR PARAMETER longTermDenialParam -- optional -- short message service errors SubscriberBusyForMT-SMS ::= ERROR PARAMETER subBusyForMT-SMS-Param -- optional SM-DeliveryFailure ::= ERROR PARAMETER sm-DeliveryFailureCause MessageWaitingListFull ::= ERROR PARAMETER messageWaitListFullParam -- optional AbsentSubscriberSM ::= ERROR PARAMETER absentSubscriberSM-Param -- optional -- Group Call errors NoGroupCallNumberAvailable ::= ERROR PARAMETER noGroupCallNbParam -- optional -- location service errors

LongTermDenialParam

SubBusyForMT-SMS-Param

SM-DeliveryFailureCause

MessageWaitListFullParam

AbsentSubscriberSM-Param

NoGroupCallNbParam

UnauthorizedRequestingNetwork ::= ERROR PARAMETER unauthorizedRequestingNetwork-Param UnauthorizedRequestingNetwork-Param -- optional UnauthorizedLCSClient ::= ERROR PARAMETER unauthorizedLCSClient-Param -- optional PositionMethodFailure ::= ERROR PARAMETER positionMethodFailure-Param -- optional

UnauthorizedLCSClient-Param

PositionMethodFailure-Param

UnknownOrUnreachableLCSClient ::= ERROR PARAMETER unknownOrUnreachableLCSClient-Param -- optional END

UnknownOrUnreachableLCSClient-Param

397
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

17.6.7 Group Call operations


MAP-Group-Call-Operations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Group-Call-Operations (22) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS PrepareGroupCall, SendGroupCallEndSignal, ForwardGroupCallSignalling, ProcessGroupCallSignalling ;

584

3GPP

585 Release 1998


18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71

294

3GPP TS 09.02 V7.15.0 (2004-03)

IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, UnexpectedDataValue, NoGroupCallNumberAvailable FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} PrepareGroupCallArg, PrepareGroupCallRes, SendGroupCallEndSignalArg, SendGroupCallEndSignalRes, ForwardGroupCallSignallingArg, ProcessGroupCallSignallingArg FROM MAP-GR-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-GR-DataTypes (23) version5 (5)}

; PrepareGroupCall ::= OPERATION ARGUMENT prepareGroupCallArg RESULT prepareGroupCallRes ERRORS { SystemFailure, NoGroupCallNumberAvailable, UnexpectedDataValue} SendGroupCallEndSignal ::= OPERATION ARGUMENT sendGroupCallEndSignalArg RESULT sendGroupCallEndSignalRes --Timer m PrepareGroupCallArg PrepareGroupCallRes

--Timer l SendGroupCallEndSignalArg SendGroupCallEndSignalRes

ProcessGroupCallSignalling ::= OPERATION --Timer s ARGUMENT processGroupCallSignallingArg ProcessGroupCallSignallingArg ForwardGroupCallSignalling ::= OPERATION --Timer s ARGUMENT forwardGroupCallSignallingArg ForwardGroupCallSignallingArg END

17.6.8 Location service operations


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

MAP-LocationServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version5 (5)} DEFINITIONS ::= BEGIN EXPORTS ProvideSubscriberLocation, SendRoutingInfoForLCS, SubscriberLocationReport ;

586

3GPP

587 Release 1998


18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83

295

3GPP TS 09.02 V7.15.0 (2004-03)

IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, AbsentSubscriber, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, ResourceLimitation, UnknownOrUnreachableLCSClient, UnidentifiedSubscriber, IllegalEquipment, IllegalSubscriber FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version5 (5)} RoutingInfoForLCS-Arg, RoutingInfoForLCS-Res, ProvideSubscriberLocation-Arg, ProvideSubscriberLocation-Res, SubscriberLocationReport-Arg, SubscriberLocationReport-Res FROM MAP-LCS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LCS-DataTypes (25) version5 (5)} ; SendRoutingInfoForLCS ::= OPERATION --Timer m ARGUMENT routingInfoForLCS-Arg RoutingInfoForLCS-Arg RESULT routingInfoForLCS-Res RoutingInfoForLCS-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, AbsentSubscriber, UnauthorizedRequestingNetwork }

ProvideSubscriberLocation ::= OPERATION


ARGUMENT provideSubscriberLocation-Arg RESULT provideSubscriberLocation-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, AbsentSubscriber, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure }

--Timer ml

ProvideSubscriberLocation-Arg ProvideSubscriberLocation-Res

588

3GPP

589 Release 1998


84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

296
--Timer m SubscriberLocationReport-Arg SubscriberLocationReport-Res

3GPP TS 09.02 V7.15.0 (2004-03)

SubscriberLocationReport ::= OPERATION ARGUMENT subscriberLocationReport-Arg RESULT subscriberLocationReport-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, ResourceLimitation, UnknownSubscriber, UnauthorizedRequestingNetwork, UnknownOrUnreachableLCSClient} END

100 101
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55

17.7 MAP constants and data types


17.7.1 Mobile Service data types
MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version5 (5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS -- location registration types UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes,

-- handover types PrepareHO-Arg, PrepareHO-Res, PrepareSubsequentHO-Arg, -- authentication management types SendAuthenticationInfoArg, SendAuthenticationInfoRes, -- security management types EquipmentStatus, Kc, -- subscriber management types InsertSubscriberDataArg, InsertSubscriberDataRes, DeleteSubscriberDataArg, DeleteSubscriberDataRes, SubscriberData, ODB-Data, SubscriberStatus, ZoneCodeList, maxNumOfZoneCodes, O-CSI, O-BcsmCamelTDPCriteriaList, SS-CSI, ServiceKey, DefaultCallHandling,

590

3GPP

591 Release 1998


56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134

297

3GPP TS 09.02 V7.15.0 (2004-03)

CamelCapabilityHandling, BasicServiceCriteria, SupportedCamelPhases, maxNumOfCamelTDPData, CUG-Index, CUG-Interlock, InterCUG-Restrictions, IntraCUG-Options, NotificationToMSUser, -- fault recovery types ResetArg, RestoreDataArg, RestoreDataRes, -- subscriber information enquiry types ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, SubscriberInfo, LocationInformation, SubscriberState, -- any time information enquiry types AnyTimeInterrogationArg, AnyTimeInterrogationRes, -- gprs location information retrieval types SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, -- failure reporting types FailureReportArg, FailureReportRes, -- gprs notification types NoteMsPresentForGprsArg, NoteMsPresentForGprsRes ; IMPORTS maxNumOfSS, SS-SubscriptionOption, SS-List FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version5 (5)}

FROM MAP-SS-Code {

SS-Code

ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version5 (5)}

FROM MAP-BS-Code {

Ext-BearerServiceCode ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version5 (5)}

FROM MAP-TS-Code {

Ext-TeleserviceCode ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version5 (5)}

ISDN-AddressString, maxISDN-AddressLength, ISDN-SubaddressString, ExternalSignalInfo, IMSI, HLR-List, LMSI, Identity, GlobalCellId, CellIdOrLAI, Ext-BasicServiceCode, NAEA-PreferredCI, EMLPP-Info, SubscriberIdentity,

592

3GPP

593 Release 1998


135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209

298

3GPP TS 09.02 V7.15.0 (2004-03)

AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, TBCD-STRING

FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version5 (5)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version5 (5)} ; -- location registration types UpdateLocationArg ::= SEQUENCE { imsi msc-Number vlr-Number lmsi extensionContainer ... , vlr-Capability IMSI, [1] ISDN-AddressString, ISDN-AddressString, [10] LMSI OPTIONAL, ExtensionContainer [6] VLR-Capability [0] SupportedCamelPhases ExtensionContainer [2] NULL

OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL, OPTIONAL }

VLR-Capability ::= SEQUENCE{


supportedCamelPhases extensionContainer ... , solsaSupportIndicator

UpdateLocationRes ::= SEQUENCE { hlr-Number extensionContainer ... } CancelLocationArg ::= [3] SEQUENCE { identity cancellationType extensionContainer ...}

ISDN-AddressString, ExtensionContainer OPTIONAL,

Identity, CancellationType ExtensionContainer

OPTIONAL, OPTIONAL,

CancellationType ::= ENUMERATED { updateProcedure (0), subscriptionWithdraw (1), ...} -- The HLR shall not send values other than listed above CancelLocationRes ::= SEQUENCE { extensionContainer ...} PurgeMS-Arg ::= [3] SEQUENCE { imsi vlr-Number sgsn-Number extensionContainer ...}

ExtensionContainer

OPTIONAL,

IMSI, [0] ISDN-AddressString [1] ISDN-AddressString ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

594

3GPP

595 Release 1998


210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286

299

3GPP TS 09.02 V7.15.0 (2004-03)

PurgeMS-Res ::= SEQUENCE { freezeTMSI freezeP-TMSI extensionContainer ...} SendIdentificationRes ::= SEQUENCE { imsi authenticationSetList ...}

[0] NULL [1] NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

IMSI, AuthenticationSetList

OPTIONAL,

AuthenticationSetList ::= SEQUENCE SIZE (1..5) OF AuthenticationSet AuthenticationSet ::= SEQUENCE { rand sres kc ...} RAND ::= OCTET STRING (SIZE (16)) SRES ::= OCTET STRING (SIZE (4)) Kc ::= OCTET STRING (SIZE (8)) -- gprs location registration types UpdateGprsLocationArg ::= SEQUENCE { imsi sgsn-Number sgsn-Address extensionContainer ... , IMSI, ISDN-AddressString, GSN-Address, ExtensionContainer [0] SGSN-Capability NULL [1] ExtensionContainer RAND, SRES, Kc,

OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL,

sgsn-Capability

SGSN-Capability ::= SEQUENCE{


solsaSupportIndicator extensionContainer ... }

GSN-Address ::= OCTET STRING (SIZE (5..17)) -- Octets are coded according to TS GSM 03.03 UpdateGprsLocationRes ::= SEQUENCE { hlr-Number extensionContainer ...} -- handover types PrepareHO-Arg ::= SEQUENCE { targetCellId ho-NumberNotRequired bss-APDU ...} PrepareHO-Res ::= SEQUENCE { handoverNumber bss-APDU ...} PrepareSubsequentHO-Arg ::= SEQUENCE { targetCellId targetMSC-Number bss-APDU ...} -- authentication management types SendAuthenticationInfoArg ::= IMSI SendAuthenticationInfoRes ::= AuthenticationSetList -- security management types GlobalCellId NULL ExternalSignalInfo OPTIONAL, OPTIONAL, OPTIONAL, ISDN-AddressString, ExtensionContainer

OPTIONAL,

ISDN-AddressString ExternalSignalInfo

OPTIONAL, OPTIONAL,

GlobalCellId, ISDN-AddressString, ExternalSignalInfo,

596

3GPP

597 Release 1998


287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325

300

3GPP TS 09.02 V7.15.0 (2004-03)

EquipmentStatus ::= ENUMERATED { whiteListed (0), blackListed (1), greyListed (2)} -- subscriber management types InsertSubscriberDataArg ::= SEQUENCE { imsi [0] IMSI COMPONENTS OF SubscriberData, extensionContainer [14] ExtensionContainer ... , naea-PreferredCI [15] NAEA-PreferredCI -- naea-PreferredCI is included at the discretion of the HLR operator. gprsSubscriptionData [16] GPRSSubscriptionData roamingRestrictedInSgsnDueToUnsupportedFeature [23] OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, NULL OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

networkAccessMode [24] NetworkAccessMode lsaInformation [25] LSAInformation lmu-Indicator [21] NULL lcsInformation [22] LCSInformation } -- If the Network Access Mode parameter is sent, it shall be present only in -- the first sequence if the seqmentation is used LCSInformation ::= SEQUENCE { gmlc-List [0] lcs-PrivacyExceptionList molr-List ...} GMLC-List OPTIONAL, [1] LCS-PrivacyExceptionList [2] MOLR-List

OPTIONAL, OPTIONAL,

GMLC-List ::= SEQUENCE SIZE (1..maxNumOfGMLC) OF

ISDN-AddressString -- if segmentation is used, the complete GMLC-List shall be sent in one segment INTEGER ::= 5

maxNumOfGMLC

326
327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349
350

NetworkAccessMode ::= ENUMERATED {


bothMSCAndSGSN onlyMSC onlySGSN ...} -- if unknown values are received in -- they shall be discarded. (0), (1), (2), NetworkAccessMode

GPRSDataList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF PDP-Context maxNumOfPDP-Contexts INTEGER ::= 50 ContextId, [16] PDP-Type, [17] PDP-Address [18] QoS-Subscribed, [19] NULL OPTIONAL, [20] APN , [21] ExtensionContainer

PDP-Context ::= SEQUENCE { pdp-ContextId pdp-Type pdp-Address qos-Subscribed vplmnAddressAllowed apn extensionContainer ...}

OPTIONAL,

OPTIONAL,

ContextId ::= INTEGER (1..maxNumOfPDP-Contexts) GPRSSubscriptionData ::= SEQUENCE { completeDataListIncluded

351 352 353 354 355 356 357 358

NULL

OPTIONAL,

-- If segmentation is used, completeDataListIncluded may only be present in the -- first segment. gprsDataList [1] GPRSDataList, extensionContainer [2] ExtensionContainer OPTIONAL, ...}

359

598

3GPP

599 Release 1998


360 361 362

301

3GPP TS 09.02 V7.15.0 (2004-03)

APN ::=

OCTET STRING (SIZE (2..63)) -- Octets are coded according to TS GSM 03.03

363
364 365

PDP-Type ::= OCTET STRING (SIZE (2)) -- Octets are coded according to TS GSM 09.60

366
367 368 369 370 371 372 373

PDP-Address ::= OCTET STRING (SIZE (1..16)) -- Octets are coded according to TS GSM 09.60 -- The possible size values -- 1-7 octets X.25 address -- 4 octets IPv4 address -- 16 octets Ipv6 address are: type type type

374
375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432

QoS-Subscribed ::= OCTET STRING (SIZE (3)) -- Octets are coded according to TS GSM 04.08. LSAOnlyAccessIndicator ::= ENUMERATED { accessOutsideLSAsAllowed (0), accessOutsideLSAsRestricted (1)} LSADataList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF LSAData maxNumOfLSAs INTEGER ::= 20 [0] [1] [2] [3] LSAIdentity, LSAAttributes, NULL ExtensionContainer

LSAData ::= SEQUENCE { lsaIdentity lsaAttributes lsaActiveModeIndicator extensionContainer ...} LSAInformation ::= SEQUENCE { completeDataListIncluded

OPTIONAL, OPTIONAL,

NULL

OPTIONAL,

-- If segmentation is used, completeDataListIncluded may only be present in the -- first segment. lsaOnlyAccessIndicator [1] LSAOnlyAccessIndicator OPTIONAL, lsaDataList [2] LSADataList OPTIONAL, extensionContainer [3] ExtensionContainer OPTIONAL, ...} LSAIdentity ::= OCTET STRING (SIZE (3)) -- Octets are coded according to TS GSM 03.03 LSAAttributes ::= OCTET STRING (SIZE (1)) -- Octets are coded according to TS GSM 08.08 SubscriberData ::= SEQUENCE { msisdn [1] ISDN-AddressString category [2] Category subscriberStatus [3] SubscriberStatus bearerServiceList [4] BearerServiceList -- The exception handling for reception of unsupported / not allocated -- bearerServiceCodes is defined in section 6.8.1 teleserviceList [6] TeleserviceList -- The exception handling for reception of unsupported / not allocated -- teleserviceCodes is defined in section 6.8.1 provisionedSS [7] Ext-SS-InfoList odb-Data [8] ODB-Data roamingRestrictionDueToUnsupportedFeature [9] NULL regionalSubscriptionData [10] ZoneCodeList vbsSubscriptionData [11] VBSDataList vgcsSubscriptionData [12] VGCSDataList vlrCamelSubscriptionInfo [13] VlrCamelSubscriptionInfo } Category ::= OCTET STRING (SIZE (1)) -- The internal structure is defined in CCITT Rec Q.763.

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

600

3GPP

601 Release 1998


433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479

302

3GPP TS 09.02 V7.15.0 (2004-03)

SubscriberStatus ::= ENUMERATED { serviceGranted (0), operatorDeterminedBarring (1)} BearerServiceList ::= SEQUENCE SIZE (1..maxNumOfBearerServices) OF Ext-BearerServiceCode maxNumOfBearerServices INTEGER ::= 50

TeleserviceList ::= SEQUENCE SIZE (1..maxNumOfTeleservices) OF Ext-TeleserviceCode maxNumOfTeleservices INTEGER ::= 20 ODB-GeneralData, ODB-HPLMN-Data ExtensionContainer

ODB-Data ::= SEQUENCE { odb-GeneralData odb-HPLMN-Data extensionContainer ...}

OPTIONAL, OPTIONAL,

ODB-GeneralData ::= BIT STRING { allOG-CallsBarred (0), internationalOGCallsBarred (1), internationalOGCallsNotToHPLMN-CountryBarred (2), interzonalOGCallsBarred (6), interzonalOGCallsNotToHPLMN-CountryBarred (7), interzonalOGCallsAndInternationalOGCallsNotToHPLMN-CountryBarred (8), premiumRateInformationOGCallsBarred (3), premiumRateEntertainementOGCallsBarred (4), ss-AccessBarred (5), allECT-Barred (9), chargeableECT-Barred (10), internationalECT-Barred (11), interzonalECT-Barred (12), doublyChargeableECT-Barred (13), multipleECT-Barred (14)} (SIZE (15..32)) -- exception handling: reception of unknown bit assignments in the -- ODB-GeneralData type shall be treated like unsupported ODB-GeneralData ODB-HPLMN-Data ::= BIT STRING { plmn-SpecificBarringType1 (0), plmn-SpecificBarringType2 (1), plmn-SpecificBarringType3 (2), plmn-SpecificBarringType4 (3)} (SIZE (4..32)) -- exception handling: reception of unknown bit assignments in the -- ODB-HPLMN-Data type shall be treated like unsupported ODB-HPLMN-Data

480
481 482

Ext-SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF


Ext-SS-Info

483
484 485 486 487 488 489 490

Ext-SS-Info ::= CHOICE {


forwardingInfo callBarringInfo cug-Info ss-Data emlpp-Info

[0] [1] [2] [3] [4]

Ext-ForwInfo, Ext-CallBarInfo, CUG-Info, Ext-SS-Data, EMLPP-Info}

491
492 493 494 495 496

Ext-ForwInfo ::= SEQUENCE { ss-Code forwardingFeatureList extensionContainer ...}

SS-Code, Ext-ForwFeatureList, [0] ExtensionContainer

OPTIONAL,

497
498 499

Ext-ForwFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF


Ext-ForwFeature

602

3GPP

603 Release 1998


500
501 502 503 504 505 506 507 508 509 510 511 512

303

3GPP TS 09.02 V7.15.0 (2004-03)

Ext-ForwFeature ::= SEQUENCE {

basicService Ext-BasicServiceCode OPTIONAL, ss-Status [4] Ext-SS-Status, forwardedToNumber [5] ISDN-AddressString OPTIONAL, -- When this data type is sent from an HLR which supports CAMEL Phase 2 -- to a VLR that supports CAMEL Phase 2 the VLR shall not check the -- format of the number forwardedToSubaddress [8] ISDN-SubaddressString OPTIONAL, forwardingOptions [6] Ext-ForwOptions OPTIONAL, noReplyConditionTime [7] Ext-NoRepCondTime OPTIONAL, extensionContainer [9] ExtensionContainer OPTIONAL, ...}

513
514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561

Ext-SS-Status ::= OCTET STRING (SIZE (1..5))


-- OCTET 1: --- bits 8765: 0000 (unused) -- bits 4321: Used to convey the "P bit","R bit","A bit" and "Q bit", -representing supplementary service state information -as defined in TS GSM 03.11 -- bit 4: "Q bit" -- bit 3: "P bit" -- bit 2: "R bit" -- bit 1: "A bit" -- OCTETS 2-5: reserved for future use. They shall be discarded if -- received and not understood.

534

Ext-ForwOptions ::= OCTET STRING (SIZE (1..5))


-- OCTET 1: ---------------bit 8: notification to forwarding party 0 no notification 1 notification bit 7: redirecting presentation 0 no presentation 1 presentation bit 6: notification to calling party 0 no notification 1 notification bit 5: 0 (unused) bits 00 01 10 11 43: forwarding reason ms not reachable ms busy no reply unconditional

-- bits 21: 00 (unused) -- OCTETS 2-5: reserved for future use. They shall be discarded if -- received and not understood.

563
564 565 566 567 568 569

562

Ext-NoRepCondTime ::= INTEGER (1..100)


-- Only values 5-30 are used. -- Values in the ranges 1-4 and 31-100 are reserved for future use -- If received: -values 1-4 shall be mapped on to value 5 -values 31-100 shall be mapped on to value 30

570
571 572 573 574 575

Ext-CallBarInfo ::= SEQUENCE {


ss-Code callBarringFeatureList extensionContainer ...}

SS-Code, Ext-CallBarFeatureList, ExtensionContainer

OPTIONAL,

604

3GPP

605 Release 1998


576
577 578

304

3GPP TS 09.02 V7.15.0 (2004-03)

Ext-CallBarFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF


Ext-CallBarringFeature

579
580 581 582 583 584

Ext-CallBarringFeature ::= SEQUENCE {


basicService ss-Status [4] Ext-SS-Status, extensionContainer ...} Ext-BasicServiceCode ExtensionContainer OPTIONAL, OPTIONAL,

585
586 587 588 589 590

CUG-Info ::= SEQUENCE {


cug-SubscriptionList cug-FeatureList extensionContainer ...} CUG-SubscriptionList, CUG-FeatureList [0] ExtensionContainer OPTIONAL, OPTIONAL,

591
592 593

CUG-SubscriptionList ::= SEQUENCE SIZE (0..maxNumOfCUG) OF


CUG-Subscription

594
595 596 597 598 599 600 601

CUG-Subscription ::= SEQUENCE {


cug-Index CUG-Index, cug-Interlock intraCUG-Options basicServiceGroupList extensionContainer ...} CUG-Interlock, IntraCUG-Options, Ext-BasicServiceGroupList [0] ExtensionContainer

OPTIONAL, OPTIONAL,

602
603 604

CUG-Index ::= INTEGER (0..32767)


-- The internal structure is defined in ETS 300 138.

605
606

CUG-Interlock ::= OCTET STRING (SIZE (4)) IntraCUG-Options ::= ENUMERATED {


noCUG-Restrictions (0), cugIC-CallBarred (1), cugOG-CallBarred (2)}

607
608 609 610 611

612
613

maxNumOfCUG

INTEGER ::= 10

614
615 616 617 618 619

CUG-FeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF


CUG-Feature Ext-BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) Ext-BasicServiceCode OF

620
621

maxNumOfExt-BasicServiceGroups CUG-Feature ::= SEQUENCE {


basicService preferentialCUG-Indicator interCUG-Restrictions extensionContainer ...}

INTEGER ::= 32

622
623 624 625 626 627 628

Ext-BasicServiceCode CUG-Index OPTIONAL, InterCUG-Restrictions, ExtensionContainer

OPTIONAL, OPTIONAL,

629
630 631 632 633 634 635 636 637 638 639 640

InterCUG-Restrictions ::= OCTET STRING (SIZE (1))


-- bits 876543: 000000 (unused) -- Exception handling: -- bits 876543 shall be ignored if received and not understood -- bits 21 -00 CUG -01 CUG -10 CUG -11 CUG only with with with facilities outgoing access incoming access both outgoing and incoming access

606

3GPP

607 Release 1998


641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715

305

3GPP TS 09.02 V7.15.0 (2004-03)

Ext-SS-Data ::= SEQUENCE { ss-Code ss-Status [4] Ext-SS-Status, ss-SubscriptionOption basicServiceGroupList extensionContainer ...}

SS-Code, SS-SubscriptionOption Ext-BasicServiceGroupList [5] ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL,

LCS-PrivacyExceptionList ::= SEQUENCE SIZE (1..maxNumOfPrivacyClass) OF LCS-PrivacyClass maxNumOfPrivacyClass INTEGER ::= 4

LCS-PrivacyClass ::= SEQUENCE {

ss-Code SS-Code, ss-Status Ext-SS-Status, notificationToMSUser [0] NotificationToMSUser OPTIONAL, -- notificationToMSUser may be sent only for SS-codes callrelated -- and callunrelated. If not received for SS-codes callrelated and callunrelated, -- the default values according to GSM 03.71 shall be assumed. externalClientList [1] ExternalClientList OPTIONAL, -- externalClientList may be sent only for SS-code callunrelated. plmnClientList [2] PLMNClientList OPTIONAL, -- plmnClientList may be sent only for SS-code plmnoperator. extensionContainer [3] ExtensionContainer OPTIONAL, ...} -- if segmentation is used, the complete LCS-PrivacyClass shall be sent in one segment

ExternalClientList ::= SEQUENCE SIZE (0..maxNumOfExternalClient) OF ExternalClient maxNumOfExternalClient INTEGER ::= 5

PLMNClientList ::= SEQUENCE SIZE (1..maxNumOfPLMNClient) OF LCSClientInternalID maxNumOfPLMNClient INTEGER ::= 5

ExternalClient ::= SEQUENCE { clientIdentity LCSClientExternalID, gmlc-Restriction [0] GMLC-Restriction OPTIONAL, notificationToMSUser [1] NotificationToMSUser OPTIONAL, -- If notificationToMSUser is not received, the default value according to -- GSM 03.71 shall be assumed. extensionContainer [2] ExtensionContainer OPTIONAL, ... } GMLC-Restriction ::= ENUMERATED { gmlc-List (0), home-Country (1), ... } -- exception handling: -- At reception of any other value than the ones listed the receiver shall ignore -- GMLC-Restriction. NotificationToMSUser ::= ENUMERATED { notifyLocationAllowed (0), notifyAndVerify-LocationAllowedIfNoResponse (1), notifyAndVerify-LocationNotAllowedIfNoResponse(2), ... } -- exception handling: -- At reception of any other value than the ones listed the receiver shall ignore -- NotificationToMSUser. MOLR-List ::= SEQUENCE SIZE (1..maxNumOfMOLR-Class) OF MOLR-Class maxNumOfMOLR-Class INTEGER ::= 3 SS-Code, Ext-SS-Status, [0] ExtensionContainer

MOLR-Class ::= SEQUENCE {


ss-Code ss-Status extensionContainer ...}

OPTIONAL,

608

3GPP

609 Release 1998


716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792

306

3GPP TS 09.02 V7.15.0 (2004-03)

ZoneCodeList ::= SEQUENCE SIZE (1..maxNumOfZoneCodes) OF ZoneCode ZoneCode ::= OCTET STRING (SIZE (2)) -- internal structure is defined in TS GSM 03.03 maxNumOfZoneCodes INTEGER ::= 10 TeleserviceList BearerServiceList SS-List ODB-GeneralData OPTIONAL, SupportedCamelPhases ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

InsertSubscriberDataRes ::= SEQUENCE { teleserviceList [1] bearerServiceList [2] ss-List [3] odb-GeneralData [4] regionalSubscriptionResponse [5] RegionalSubscriptionResponse supportedCamelPhases [6] extensionContainer [7] ...} RegionalSubscriptionResponse ::= ENUMERATED { networkNode-AreaRestricted (0), tooManyZoneCodes (1), zoneCodesConflict (2), regionalSubscNotSupported (3)}

DeleteSubscriberDataArg ::= SEQUENCE { imsi [0] IMSI, basicServiceList [1] BasicServiceList -- The exception handling for reception of unsupported/not allocated -- basicServiceCodes is defined in section 6.8.2 ss-List [2] SS-List roamingRestrictionDueToUnsupportedFeature [4] NULL regionalSubscriptionIdentifier [5] ZoneCode vbsGroupIndication [7] NULL vgcsGroupIndication [8] NULL OPTIONAL, camelSubscriptionInfoWithdraw [9] NULL OPTIONAL, extensionContainer [6] ExtensionContainer OPTIONAL, ..., gprsSubscriptionDataWithdraw [10] GPRSSubscriptionDataWithdraw roamingRestrictedInSgsnDueToUnsuppportedFeature [11] NULL lsaInformationWithdraw [12] LSAInformationWithdraw gmlc-ListWithdraw [13] NULL GPRSSubscriptionDataWithdraw ::= CHOICE { allGPRSData NULL, contextIdList ContextIdList} ContextIdList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF ContextId LSAInformationWithdraw ::= CHOICE { allLSAData lsaIdentityList NULL, LSAIdentityList }

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

LSAIdentityList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF LSAIdentity BasicServiceList ::= SEQUENCE SIZE (1..maxNumOfBasicServices) OF Ext-BasicServiceCode maxNumOfBasicServices INTEGER ::= 70 [0] RegionalSubscriptionResponse ExtensionContainer

DeleteSubscriberDataRes ::= SEQUENCE { regionalSubscriptionResponse extensionContainer ...} o-CSI extensionContainer ..., ss-CSI o-BcsmCamelTDP-CriteriaList tif-CSI }

OPTIONAL, OPTIONAL,

VlrCamelSubscriptionInfo ::= SEQUENCE {

[0] O-CSI [1] ExtensionContainer [2] SS-CSI [4] O-BcsmCamelTDPCriteriaList [3] NULL

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

610

3GPP

611 Release 1998


793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869

307

3GPP TS 09.02 V7.15.0 (2004-03)

SS-CSI ::= SEQUENCE {

ss-CamelData extensionContainer ...} ::= SEQUENCE { ss-EventList gsmSCF-Address extensionContainer ... } ------

SS-CamelData, ExtensionContainer

OPTIONAL,

SS-CamelData

SS-EventList, ISDN-AddressString, [0] ExtensionContainer

OPTIONAL,

SS-EventList

::= SEQUENCE SIZE (1..maxNumOfCamelSSEvents) OF SS-Code Actions for the following SS-Code values are defined in CAMEL Phase 2: ect SS-Code ::= '00110001'B multiPTY SS-Code ::= '01010001'B cd SS-Code ::= '00100100'B all other SS codes shall be ignored

maxNumOfCamelSSEvents INTEGER ::= 10 O-CSI ::= SEQUENCE {


o-BcsmCamelTDPDataList extensionContainer ..., camelCapabilityHandling } O-BcsmCamelTDPDataList, ExtensionContainer [0] CamelCapabilityHandling

OPTIONAL, OPTIONAL

O-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF

O-BcsmCamelTDPData --- O-BcsmCamelTDPDataList shall not contain more than one instance of --- O-BcsmCamelTDPData containing the same value for o-BcsmTriggerDetectionPoint. --- For CAMEL Phase 2, this means that only one instance of O-BcsmCamelTDPData is allowed --- with o-BcsmTriggerDetectionPoint being equal to DP2.

maxNumOfCamelTDPData

INTEGER ::= 10 O-BcsmTriggerDetectionPoint, ServiceKey, [0] ISDN-AddressString, [1] DefaultCallHandling, [2] ExtensionContainer

O-BcsmCamelTDPData ::= SEQUENCE {


o-BcsmTriggerDetectionPoint serviceKey gsmSCF-Address defaultCallHandling extensionContainer ... }

OPTIONAL,

ServiceKey ::= INTEGER (0..2147483647) O-BcsmTriggerDetectionPoint ::= ENUMERATED {


-------collectedInfo (2), ... } exception handling: For O-BcsmCamelTDPData sequences containing this parameter with any other value than the ones listed the receiver shall ignore the whole O-BcsmCamelTDPDatasequence. For O-BcsmCamelTDP-Criteria sequences containing this parameter with any other value than the ones listed the receiver shall ignore the whole O-BcsmCamelTDP-Criteria sequence.

O-BcsmCamelTDPCriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF O-BcsmCamelTDP-Criteria O-BcsmCamelTDP-Criteria ::= SEQUENCE {


o-BcsmTriggerDetectionPoint destinationNumberCriteria basicServiceCriteria callTypeCriteria ... } O-BcsmTriggerDetectionPoint, [0] DestinationNumberCriteria [1] BasicServiceCriteria [2] CallTypeCriteria

OPTIONAL, OPTIONAL, OPTIONAL,

DestinationNumberCriteria

::= SEQUENCE { matchType [0] MatchType, destinationNumberList [1] DestinationNumberList OPTIONAL, destinationNumberLengthList [2] DestinationNumberLengthList OPTIONAL, -- one or both of destinationNumberList and destinationNumberLengthList -- shall be present ... }

612

3GPP

613 Release 1998


870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943

308

3GPP TS 09.02 V7.15.0 (2004-03)

DestinationNumberList

::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumbers) OF ISDN-AddressString -- The receiving entity shall not check the format of a number in -- the dialled number list

DestinationNumberLengthList
OF

::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumberLengths) INTEGER(1..maxNumOfISDN-AddressDigits)

BasicServiceCriteria

Ext-BasicServiceCode

::= SEQUENCE SIZE(1..maxNumOfCamelBasicServiceCriteria) OF INTEGER ::= 15 INTEGER ::= 10 INTEGER ::= 3

maxNumOfISDN-AddressDigits

maxNumOfCamelDestinationNumbers

maxNumOfCamelDestinationNumberLengths maxNumOfCamelBasicServiceCriteria

INTEGER ::= 5 (0), (1)} (0), (1)}

CallTypeCriteria
forwarded notForwarded inhibiting enabling

::= ENUMERATED {

MatchType

::= ENUMERATED {

DefaultCallHandling ::= ENUMERATED {

continueCall (0) , releaseCall (1) , ...} -- exception handling: -- reception of values in range 2-31 shall be treated as "continueCall" -- reception of values greater than 31 shall be treated as "releaseCall"

CamelCapabilityHandling ::= INTEGER(1..16)

-- value 1 = CAMEL phase 1, -- value 2 = CAMEL phase 2: -- reception of values greater than 2 shall be treated as CAMEL phase 2

SupportedCamelPhases ::= BIT STRING {

phase1 (0), phase2 (1) } (SIZE (1..16)) -- A node shall mark in the BIT STRING all CAMEL Phases which it supports. -- Other values than those listed above shall be discarded. -- gprs location information retrieval types

SendRoutingInfoForGprsArg ::= SEQUENCE {


imsi ggsn-Address ggsn-Number extensionContainer ...}

[0] IMSI, [1] GSN-Address [2] ISDN-AddressString, [3] ExtensionContainer

OPTIONAL, OPTIONAL,

SendRoutingInfoForGprsRes ::= SEQUENCE {


sgsn-Address ggsn-Address mobileNotReachableReason extensionContainer ...}

[0] GSN-Address, [1] GSN-Address OPTIONAL, [2] AbsentSubscriberDiagnosticSM OPTIONAL, [3] ExtensionContainer OPTIONAL,

-- failure report types

FailureReportArg ::= SEQUENCE {


imsi ggsn-Number ggsn-Address extensionContainer ...}

[0] [1] [2] [3]

IMSI, ISDN-AddressString GSN-Address ExtensionContainer

, OPTIONAL, OPTIONAL,

614

3GPP

615 Release 1998


944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020

309

3GPP TS 09.02 V7.15.0 (2004-03)

FailureReportRes ::= SEQUENCE {


ggsn-Address extensionContainer ...}

[0] GSN-Address [1] ExtensionContainer

OPTIONAL, OPTIONAL,

-- gprs notification types

NoteMsPresentForGprsArg ::= SEQUENCE {


imsi sgsn-Address ggsn-Address extensionContainer ...} extensionContainer ...}

[0] [1] [2] [3]

IMSI, GSN-Address, GSN-Address ExtensionContainer

OPTIONAL, OPTIONAL,

NoteMsPresentForGprsRes ::= SEQUENCE {

[0] ExtensionContainer

OPTIONAL,

-- fault recovery types ResetArg ::= SEQUENCE { hlr-Number hlr-List ...} RestoreDataArg ::= SEQUENCE { imsi lmsi extensionContainer ... , vlr-Capability RestoreDataRes ::= SEQUENCE { hlr-Number msNotReachable extensionContainer ...} ISDN-AddressString, HLR-List

OPTIONAL,

IMSI, LMSI ExtensionContainer [6] VLR-Capability ISDN-AddressString, NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL }

OPTIONAL, OPTIONAL,

-- VBS/VGCS types VBSDataList ::= SEQUENCE SIZE (1..maxNumOfVBSGroupIds) OF VoiceBroadcastData VGCSDataList ::= SEQUENCE SIZE (1..maxNumOfVGCSGroupIds) OF VoiceGroupCallData maxNumOfVBSGroupIds maxNumOfVGCSGroupIds INTEGER ::= 50 INTEGER ::= 50 GroupId, ExtensionContainer

VoiceGroupCallData ::= SEQUENCE { groupId extensionContainer ...} VoiceBroadcastData ::= SEQUENCE { groupid broadcastInitEntitlement extensionContainer ...} GroupId -----

OPTIONAL,

GroupId, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

::= TBCD-STRING (SIZE (3)) When Group-Id is less than six characters in length, the TBCD filler (1111) is used to fill unused half octets. Refers to the Group Identification as specified in GSM TS 03.03 and 03.68/ 03.69

-- provide subscriber info types

ProvideSubscriberInfoArg ::= SEQUENCE {


imsi [0] IMSI, lmsi [1] LMSI requestedInfo extensionContainer ...} OPTIONAL, [2] RequestedInfo, [3] ExtensionContainer

OPTIONAL,

616

3GPP

617 Release 1998


1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087

310

3GPP TS 09.02 V7.15.0 (2004-03)

ProvideSubscriberInfoRes ::= SEQUENCE {


subscriberInfo extensionContainer ...}

SubscriberInfo, ExtensionContainer

OPTIONAL,

SubscriberInfo ::= SEQUENCE {


locationInformation subscriberState extensionContainer ...} locationInformation subscriberState extensionContainer ...}

[0] LocationInformation [1] SubscriberState [2] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

RequestedInfo ::= SEQUENCE {

[0] NULL [1] NULL [2] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

LocationInformation ::= SEQUENCE {


ageOfLocationInformation geographicalInformation vlr-number locationNumber cellIdOrLAI extensionContainer ...}

AgeOfLocationInformation [0] GeographicalInformation [1] ISDN-AddressString [2] LocationNumber [3] CellIdOrLAI [4] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

GeographicalInformation ::= OCTET STRING (SIZE (8))

-- Refers to geographical Information defined in GSM 03.32. -- Only the description of an ellipsoid point with uncertainty circle --as specified in GSM 03.32 is allowed to be used -- The internal structure according to GSM 03.32 is as follows: -Type of shape (ellipsoid point with uncertainty circle) -Degrees of Latitude -Degrees of Longitude -Uncertainty code

1 3 3 1

octet octets octets octet

LocationNumber ::= OCTET STRING (SIZE (2..10)) SubscriberState ::= CHOICE {


assumedIdle camelBusy [1] NULL, netDetNotReachable notProvidedFromVLR

-- the internal structure is defined in CCITT Rec Q.763 [0] NULL, NotReachableReason, [2] NULL}

NotReachableReason ::= ENUMERATED {


msPurged (0), imsiDetached (1), restrictedArea (2), notRegistered (3)}

-- any time interrogation info types

AnyTimeInterrogationArg ::= SEQUENCE {


subscriberIdentity requestedInfo gsmSCF-Address extensionContainer ...} subscriberInfo extensionContainer ...}

[0] [1] [3] [2]

SubscriberIdentity, RequestedInfo, ISDN-AddressString, ExtensionContainer

OPTIONAL,

AnyTimeInterrogationRes ::= SEQUENCE {

SubscriberInfo, ExtensionContainer

OPTIONAL,

END

1088
1 2 3 4 5 6 7

17.7.2 Operation and maintenance data types


MAP-OM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version5 (5)} DEFINITIONS IMPLICIT TAGS

618

3GPP

619 Release 1998


8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

311

3GPP TS 09.02 V7.15.0 (2004-03)

::= BEGIN EXPORTS ActivateTraceModeArg, ActivateTraceModeRes, DeactivateTraceModeArg, DeactivateTraceModeRes ; IMPORTS AddressString, IMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version5 (5)} ; ActivateTraceModeArg ::= SEQUENCE { imsi traceReference traceType [2] TraceType, omc-Id extensionContainer ...}

[0] IMSI [1] TraceReference, [3] AddressString [4] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

TraceReference ::= OCTET STRING (SIZE (1..2)) TraceType ::= INTEGER (0..255) -- Trace types are fully defined in TS GSM 12.08. ActivateTraceModeRes ::= SEQUENCE { extensionContainer ...} DeactivateTraceModeArg ::= SEQUENCE { imsi traceReference extensionContainer ...} DeactivateTraceModeRes ::= SEQUENCE { extensionContainer ...} END [0] ExtensionContainer OPTIONAL,

[0] IMSI [1] TraceReference, [2] ExtensionContainer

OPTIONAL, OPTIONAL,

[0] ExtensionContainer

OPTIONAL,

65
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

17.7.3 Call handling data types


MAP-CH-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CH-DataTypes (13) version5 (5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg,

620

3GPP

621 Release 1998


19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87

312

3GPP TS 09.02 V7.15.0 (2004-03)

ResumeCallHandlingRes, NumberOfForwarding, SuppressionOfAnnouncement, CallReferenceNumber, ProvideSIWFSNumberArg, ProvideSIWFSNumberRes, SIWFSSignallingModifyArg, SIWFSSignallingModifyRes, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes

IMPORTS maxNumOfCamelTDPData, SubscriberInfo, ServiceKey, DefaultCallHandling, SupportedCamelPhases, CamelCapabilityHandling, BasicServiceCriteria, CUG-Interlock, O-CSI, O-BcsmCamelTDPCriteriaList FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version5 (5)} ForwardingOptions, SS-List, CCBS-Feature FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version5 (5)} ISDN-AddressString, ISDN-SubaddressString, ExternalSignalInfo, Ext-ExternalSignalInfo, IMSI, LMSI, Ext-BasicServiceCode, AlertingPattern, NAEA-PreferredCI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version5 (5)} ; CUG-CheckInfo ::= SEQUENCE { cug-Interlock cug-OutgoingAccess extensionContainer ...} NumberOfForwarding ::= INTEGER (1..5)

CUG-Interlock, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

622

3GPP

623 Release 1998


88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160

313

3GPP TS 09.02 V7.15.0 (2004-03)

SendRoutingInfoArg ::= SEQUENCE { msisdn cug-CheckInfo numberOfForwarding interrogationType or-Interrogation or-Capability gmsc-Address callReferenceNumber forwardingReason basicServiceGroup networkSignalInfo camelInfo suppressionOfAnnouncement extensionContainer ..., alertingPattern ccbs-Call supportedCCBS-Phase additionalSignalInfo

[0] ISDN-AddressString, [1] CUG-CheckInfo [2] NumberOfForwarding [3] InterrogationType, [4] NULL [5] OR-Phase [6] ISDN-AddressString, [7] CallReferenceNumber [8] ForwardingReason [9] Ext-BasicServiceCode [10] ExternalSignalInfo [11] CamelInfo [12] SuppressionOfAnnouncement [13] ExtensionContainer [14] AlertingPattern [15] NULL [16] SupportedCCBS-Phase [17] Ext-ExternalSignalInfo

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

SuppressionOfAnnouncement ::= NULL InterrogationType ::= ENUMERATED {


basicCall (0), forwarding (1)}

OR-Phase ::= INTEGER (1..127) CallReferenceNumber ::= OCTET STRING (SIZE (1..8)) ForwardingReason ::= ENUMERATED {
notReachable (0), busy (1), noReply (2)}

SupportedCCBS-Phase ::= INTEGER (1..127) -- exception handling: -- Only value 1 is used. -- Values in the ranges 2-127 are reserved for future use. -- If received values 2-127 shall be mapped on to value 1. SendRoutingInfoRes ::= [3] SEQUENCE { imsi [9] IMSI -- IMSI must be present if SendRoutingInfoRes is not segmented. -- If the TC-Result-NL segmentation option is taken the IMSI must be -- present in one segmented transmission of SendRoutingInfoRes. extendedRoutingInfo ExtendedRoutingInfo cug-CheckInfo [3] CUG-CheckInfo cugSubscriptionFlag [6] NULL subscriberInfo [7] SubscriberInfo ss-List [1] SS-List basicService [5] Ext-BasicServiceCode forwardingInterrogationRequired [4] NULL vmsc-Address [2] ISDN-AddressString extensionContainer [0] ExtensionContainer ... , naea-PreferredCI [10] NAEA-PreferredCI -- naea-PreferredCI is included at the discretion of the HLR operator. ccbs-Indicators [11] CCBS-Indicators msisdn [12] ISDN-AddressString numberPortabilityStatus [13] NumberPortabilityStatus } OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

NumberPortabilityStatus ::= ENUMERATED { notKnownToBePorted (0), ownNumberPortedOut (1), foreignNumberPortedToForeignNetwork (2), ...} -exception handling: -- reception of other values than the ones listed the receiver shall ignore the -- whole NumberPortabilityStatus

624

3GPP

625 Release 1998


161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235

314

3GPP TS 09.02 V7.15.0 (2004-03)

CCBS-Indicators ::= SEQUENCE { ccbs-Possible keepCCBS-CallIndicator extensionContainer ...} RoutingInfo ::= CHOICE { roamingNumber forwardingData

[0] [1] [2]

NULL NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

ISDN-AddressString, ForwardingData} OPTIONAL,

ForwardingData ::= SEQUENCE { forwardedToNumber [5] ISDN-AddressString -- When this datatype is sent from an HLR which supports CAMEL Phase 2 -- to a GMSC which supports CAMEL Phase 2 the GMSC shall not check the -- format of the number forwardedToSubaddress [4] ISDN-SubaddressString forwardingOptions [6] ForwardingOptions extensionContainer [7] ExtensionContainer ...} ProvideRoamingNumberArg ::= SEQUENCE { imsi msc-Number msisdn lmsi gsm-BearerCapability networkSignalInfo suppressionOfAnnouncement gmsc-Address callReferenceNumber or-Interrogation extensionContainer ... , alertingPattern ccbs-Call supportedCamelPhasesInGMSC additionalSignalInfo orNotSupportedInGMSC ProvideRoamingNumberRes ::= SEQUENCE { roamingNumber extensionContainer ...} ResumeCallHandlingArg ::= SEQUENCE { callReferenceNumber basicServiceGroup forwardingData imsi cug-CheckInfo o-CSI extensionContainer ccbs-Possible msisdn uu-Data allInformationSent ...} [0] IMSI, [1] ISDN-AddressString, [2] ISDN-AddressString [4] LMSI [5] ExternalSignalInfo [6] ExternalSignalInfo [7] SuppressionOfAnnouncement [8] ISDN-AddressString [9] CallReferenceNumber [10] NULL [11] ExtensionContainer [12] [13] [15] [14] [16] AlertingPattern NULL SupportedCamelPhases Ext-ExternalSignalInfo NULL

OPTIONAL, OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

ISDN-AddressString, ExtensionContainer

OPTIONAL,

[0] CallReferenceNumber [1] Ext-BasicServiceCode [2] ForwardingData [3] IMSI [4] CUG-CheckInfo [5] O-CSI [7] ExtensionContainer [8] NULL [9] ISDN-AddressString [10] UU-Data [11] NULL

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

UU-Data ::= SEQUENCE {


uuIndicator uui uusCFInteraction extensionContainer ...}

[0] [1] [2] [3]

UUIndicator UUI NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

UUIndicator ::= OCTET STRING (SIZE (1)) -- Octets are coded according to ETS 300 356 UUI ::= OCTET STRING (SIZE (1..131)) -- Octets are coded according to ETS 300 356 ExtensionContainer OPTIONAL,

ResumeCallHandlingRes ::= SEQUENCE { extensionContainer ...}

626

3GPP

627 Release 1998


236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313

315

3GPP TS 09.02 V7.15.0 (2004-03)

CamelInfo ::= SEQUENCE {


supportedCamelPhases suppress-T-CSI extensionContainer ...} routingInfo camelRoutingInfo

SupportedCamelPhases, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

ExtendedRoutingInfo ::= CHOICE {

RoutingInfo, [8] CamelRoutingInfo} ForwardingData [0] GmscCamelSubscriptionInfo, [1] ExtensionContainer OPTIONAL, OPTIONAL,

CamelRoutingInfo ::= SEQUENCE {


forwardingData gmscCamelSubscriptionInfo extensionContainer ...}

GmscCamelSubscriptionInfo ::= SEQUENCE {


t-CSI o-CSI extensionContainer ... , o-BcsmCamelTDP-CriteriaList

[0] T-CSI OPTIONAL, [1] O-CSI OPTIONAL, [2] ExtensionContainer [3] O-BcsmCamelTDPCriteriaList

OPTIONAL, OPTIONAL

T-CSI ::= SEQUENCE {

t-BcsmCamelTDPDataList extensionContainer ..., camelCapabilityHandling }

T-BcsmCamelTDPDataList, ExtensionContainer [0] CamelCapabilityHandling

OPTIONAL, OPTIONAL

T-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF

T-BcsmCamelTDPData --- T-BcsmCamelTDPDataList shall not contain more than one instance of --- T-BcsmCamelTDPData containing the same value for t-BcsmTriggerDetectionPoint. --- For CAMEL Phase 2, this means that only one instance of T-BcsmCamelTDPData is allowed --- with t-BcsmTriggerDetectionPoint being equal to DP12.

T-BcsmCamelTDPData ::= SEQUENCE {


t-BcsmTriggerDetectionPoint serviceKey gsmSCF-Address defaultCallHandling extensionContainer ...}

T-BcsmTriggerDetectionPoint, ServiceKey, [0] ISDN-AddressString, [1] DefaultCallHandling, [2] ExtensionContainer

OPTIONAL,

T-BcsmTriggerDetectionPoint ::= ENUMERATED {


-----

termAttemptAuthorized(12), ...} exception handling: For T-BcsmCamelTDPData sequences containing this parameter with any other value thanthe ones listed the receiver shall ignore the whole T-BcsmCamelTDPData sequence. [0] [1] [2] [3] [4] [5] [6] [7] ExternalSignalInfo, ExternalSignalInfo, CallDirection, ISDN-AddressString, ExternalSignalInfo, ExternalSignalInfo ExternalSignalInfo ExtensionContainer

ProvideSIWFSNumberArg ::= SEQUENCE { gsm-BearerCapability isdn-BearerCapability call-Direction b-Subscriber-Address chosenChannel lowerLayerCompatibility highLayerCompatibility extensionContainer ...} CallDirection ::= OCTET STRING (SIZE (1)) -- OCTET 1 -- bit 1 (direction of call) -- 0 Mobile Originated Call (MOC) -- 1 Mobile Terminated Call (MTC) ProvideSIWFSNumberRes ::= SEQUENCE { sIWFSNumber extensionContainer ...}

OPTIONAL, OPTIONAL, OPTIONAL,

[0] ISDN-AddressString, [1] ExtensionContainer

OPTIONAL,

628

3GPP

629 Release 1998


314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390

316

3GPP TS 09.02 V7.15.0 (2004-03)

SIWFSSignallingModifyArg ::= SEQUENCE { channelType chosenChannel extensionContainer ...} SIWFSSignallingModifyRes ::= SEQUENCE { chosenChannel extensionContainer ...} SetReportingStateArg ::= SEQUENCE { imsi lmsi ccbs-Monitoring extensionContainer ...}

[0] ExternalSignalInfo [1] ExternalSignalInfo [2] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

[0] ExternalSignalInfo [1] ExtensionContainer

OPTIONAL, OPTIONAL,

[0] [1] [2] [3]

IMSI LMSI ReportingState ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

ReportingState ::= ENUMERATED { stopMonitoring (0), startMonitoring (1), ...} -- exception handling: -- reception of values 2-10 shall be mapped to 'stopMonitoring' -- reception of values > 10 shall be mapped to 'startMonitoring' SetReportingStateRes ::= SEQUENCE{ ccbs-SubscriberStatus extensionContainer ...} [0] [1] CCBS-SubscriberStatus ExtensionContainer OPTIONAL, OPTIONAL,

CCBS-SubscriberStatus ::= ENUMERATED { ccbsNotIdle (0), ccbsIdle (1), ccbsNotReachable (2), ...} -- exception handling: -- reception of values 3-10 shall be mapped to 'ccbsNotIdle' -- reception of values 11-20 shall be mapped to 'ccbsIdle' -- reception of values > 20 shall be mapped to 'ccbsNotReachable' StatusReportArg ::= SEQUENCE{ imsi eventReportData callReportdata extensionContainer ...} EventReportData ::= SEQUENCE{ ccbs-SubscriberStatus extensionContainer ...} CallReportData ::= SEQUENCE{ monitoringMode callOutcome extensionContainer ...} [0] [1] [2] [3] IMSI, EventReportData CallReportData ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

[0] [1]

CCBS-SubscriberStatus ExtensionContainer

OPTIONAL, OPTIONAL,

[0] [1] [2]

MonitoringMode CallOutcome ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

MonitoringMode ::= ENUMERATED { a-side (0), b-side (1), ...} -exception handling: -- reception of values 2-10 shall be mapped 'a-side' -- reception of values > 10 shall be mapped to 'b-side' CallOutcome ::= ENUMERATED { success (0), failure (1), busy (2), ...} -exception handling: -- reception of values 3-10 shall be mapped to 'success' -- reception of values 11-20 shall be mapped to 'failure' -- reception of values > 20 shall be mapped to 'busy'

630

3GPP

631 Release 1998


391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426

317

3GPP TS 09.02 V7.15.0 (2004-03)

StatusReportRes ::= SEQUENCE { extensionContainer ...} RemoteUserFreeArg ::= SEQUENCE{ imsi callInfo ccbs-Feature translatedB-Number replaceB-Number alertingPattern extensionContainer ...} RemoteUserFreeRes ::= SEQUENCE{ ruf-Outcome extensionContainer ...}

[0]

ExtensionContainer

OPTIONAL,

[0] [1] [2] [3] [4] [5] [6]

IMSI, ExternalSignalInfo, CCBS-Feature, ISDN-AddressString, NULL AlertingPattern ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

[0] [1]

RUF-Outcome, ExtensionContainer

OPTIONAL,

RUF-Outcome ::= ENUMERATED{ accepted (0), rejected (1), noResponseFromFreeMS (2), -- T4 Expiry noResponseFromBusyMS (3), -- T10 Expiry udubFromFreeMS (4), udubFromBusyMS (5), ...} -- exception handling: -- reception of values 6-20 shall be mapped to 'accepted' -- reception of values 21-30 shall be mapped to 'rejected' -- reception of values 31-40 shall be mapped to 'noResponseFromFreeMS' -- reception of values 41-50 shall be mapped to 'noResponseFromBusyMS' -- reception of values 51-60 shall be mapped to 'udubFromFreeMS' -- reception of values > 60 shall be mapped to 'udubFromBusyMS' END

427
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39

17.7.4 Supplementary service data types


MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version5 (5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RegisterSS-Arg, SS-Info, SS-Status, SS-SubscriptionOption, SS-ForBS-Code, InterrogateSS-Res, USSD-Arg, USSD-Res, USSD-DataCodingScheme, USSD-String, Password, GuidanceInfo, SS-List, SS-InfoList, OverrideCategory, CliRestrictionOption, NoReplyConditionTime, ForwardingOptions, maxNumOfSS, SS-Data, CCBS-Feature, RegisterCC-EntryArg, RegisterCC-EntryRes, EraseCC-EntryArg,

SS-InvocationNotificationArg, SS-InvocationNotificationRes,

632

3GPP

633 Release 1998


40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117

318

3GPP TS 09.02 V7.15.0 (2004-03)

EraseCC-EntryRes

IMPORTS AddressString, ISDN-AddressString, ISDN-SubaddressString, IMSI, BasicServiceCode, AlertingPattern, EMLPP-Priority, ExternalSignalInfo FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version5 (5)} SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version5 (5)} ; RegisterSS-Arg ::= SEQUENCE{ ss-Code basicService forwardedToNumber forwardedToSubaddress noReplyConditionTime ..., defaultPriority NoReplyConditionTime ::= INTEGER (5..30) SS-Info ::= CHOICE { forwardingInfo callBarringInfo ss-Data ForwardingInfo ::= SEQUENCE { ss-Code forwardingFeatureList ...} [0] ForwardingInfo, [1] CallBarringInfo, [3] SS-Data} SS-Code ForwardingFeatureList, OPTIONAL,

SS-Code, BasicServiceCode [4] AddressString [6] ISDN-SubaddressString [5] NoReplyConditionTime [7] EMLPP-Priority

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

ForwardingFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF ForwardingFeature ForwardingFeature ::= SEQUENCE { basicService ss-Status [4] SS-Status forwardedToNumber forwardedToSubaddress forwardingOptions noReplyConditionTime ...} SS-Status ::= OCTET STRING (SIZE (1)) -- bits 8765: 0000 (unused) -- bits 4321: Used to convey the "P bit","R bit","A bit" and "Q bit", -representing supplementary service state information -as defined in TS GSM 03.11 -- bit 4: "Q bit" -- bit 3: "P bit" -- bit 2: "R bit" -- bit 1: "A bit" BasicServiceCode OPTIONAL, [5] ISDN-AddressString [8] ISDN-SubaddressString [6] ForwardingOptions [7] NoReplyConditionTime OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

634

3GPP

635 Release 1998


118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194

319

3GPP TS 09.02 V7.15.0 (2004-03)

ForwardingOptions ::= OCTET STRING (SIZE (1)) -- bit 8: notification to forwarding party -0 no notification -1 notification -- bit 7: redirecting presentation -0 no presentation -1 presentation -- bit 6: notification to calling party -0 no notification -1 notification -- bit 5: 0 (unused) -- bits 43: forwarding reason -00 ms not reachable -01 ms busy -10 no reply -11 unconditional when used in a SRI Result, -or call deflection when used in a RCH Argument -- bits 21: 00 (unused) CallBarringInfo ::= SEQUENCE { ss-Code callBarringFeatureList ...} SS-Code CallBarringFeatureList, OPTIONAL,

CallBarringFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF CallBarringFeature CallBarringFeature ::= SEQUENCE { basicService ss-Status [4] SS-Status ...} SS-Data ::= SEQUENCE { ss-Code ss-Status [4] SS-Status ss-SubscriptionOption basicServiceGroupList ..., defaultPriority } SS-SubscriptionOption ::= CHOICE { cliRestrictionOption overrideCategory CliRestrictionOption ::= ENUMERATED { permanent (0), temporaryDefaultRestricted (1), temporaryDefaultAllowed (2)} OverrideCategory ::= ENUMERATED { overrideEnabled (0), overrideDisabled (1)} SS-ForBS-Code ::= SEQUENCE { ss-Code basicService ...} GenericServiceInfo ::= SEQUENCE { ss-Status SS-Status, cliRestrictionOption ..., maximumEntitledPriority defaultPriority ccbs-FeatureList SS-Code, BasicServiceCode BasicServiceCode OPTIONAL, OPTIONAL,

SS-Code OPTIONAL, SS-SubscriptionOption BasicServiceGroupList EMLPP-Priority

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

[2] CliRestrictionOption, [1] OverrideCategory}

OPTIONAL,

CliRestrictionOption [0] EMLPP-Priority [1] EMLPP-Priority [2] CCBS-FeatureList

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

CCBS-FeatureList ::= SEQUENCE SIZE (1..maxNumOfCCBS-Requests) OF CCBS-Feature maxNumOfCCBS-Requests INTEGER ::= 5

636

3GPP

637 Release 1998


195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269

320

3GPP TS 09.02 V7.15.0 (2004-03)

CCBS-Feature ::= SEQUENCE { ccbs-Index b-subscriberNumber b-subscriberSubaddress basicServiceGroup ...} CCBS-Index

[0] [1] [2] [3]

CCBS-Index ISDN-AddressString ISDN-SubaddressString BasicServiceCode

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

::= INTEGER (1..maxNumOfCCBS-Requests)

InterrogateSS-Res ::= CHOICE { ss-Status [0] SS-Status, basicServiceGroupList forwardingFeatureList genericServiceInfo USSD-Arg ::= SEQUENCE { ussd-DataCodingScheme ussd-String ... , alertingPattern msisdn USSD-Res ::= SEQUENCE { ussd-DataCodingScheme ussd-String ...}

[2] BasicServiceGroupList, [3] ForwardingFeatureList, [4] GenericServiceInfo } USSD-DataCodingScheme, USSD-String, AlertingPattern [0] ISDN-AddressString USSD-DataCodingScheme, USSD-String, OPTIONAL, OPTIONAL }

USSD-DataCodingScheme ::= OCTET STRING (SIZE (1)) -- The structure of the USSD-DataCodingScheme is defined by -- the Cell Broadcast Data Coding Scheme as described in -- TS GSM 03.38 USSD-String ::= OCTET STRING (SIZE (1..maxUSSD-StringLength)) -- The structure of the contents of the USSD-String is dependent -- on the USSD-DataCodingScheme as described in TS GSM 03.38. maxUSSD-StringLength INTEGER ::= 160

Password ::= NumericString (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9")) (SIZE (4)) GuidanceInfo ::= ENUMERATED { enterPW (0), enterNewPW (1), enterNewPW-Again (2)} -- How this information is really delivered to the subscriber -- (display, announcement, ...) is not part of this -- specification. SS-List ::= SEQUENCE SIZE (1..maxNumOfSS) OF SS-Code maxNumOfSS INTEGER ::= 30

SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF SS-Info BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF BasicServiceCode maxNumOfBasicServiceGroups INTEGER ::= 13

SS-InvocationNotificationArg ::= SEQUENCE {

imsi [0] IMSI, msisdn [1] ISDN-AddressString, ss-Event [2] SS-Code, -- The following SS-Code values are allowed : -- ect SS-Code ::= '00110001'B -- multiPTY SS-Code ::= '01010001'B -- cd SS-Code ::= '00100100'B ss-EventSpecification [3] SS-EventSpecification extensionContainer [4] ExtensionContainer ...}

OPTIONAL, OPTIONAL,

638

3GPP

639 Release 1998


270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313

321

3GPP TS 09.02 V7.15.0 (2004-03)

SS-InvocationNotificationRes ::= SEQUENCE {


extensionContainer ... }

ExtensionContainer

OPTIONAL,

SS-EventSpecification ::= SEQUENCE SIZE (1..maxEventSpecification) OF AddressString maxEventSpecification INTEGER ::= 2 [0] SS-Code, CCBS-Data OPTIONAL,

RegisterCC-EntryArg ::= SEQUENCE { ss-Code ccbs-Data [1] ...} CCBS-Data ::= SEQUENCE { ccbs-Feature translatedB-Number serviceIndicator callInfo networkSignalInfo ...}

[0] [1] [2] [3] [4]

CCBS-Feature, ISDN-AddressString, ServiceIndicator ExternalSignalInfo, ExternalSignalInfo,

OPTIONAL,

ServiceIndicator ::= BIT STRING { clir-invoked (0), camel-invoked (1)} (SIZE(2..32)) -- exception handling: -- bits 2 to 31 shall be ignored if received and not understood RegisterCC-EntryRes ::= SEQUENCE { ccbs-Feature ...} EraseCC-EntryArg ::= SEQUENCE { ss-Code ccbs-Index ...} EraseCC-EntryRes ::= SEQUENCE { ss-Code ss-Status [1] SS-Status ...} END [0] CCBS-Feature OPTIONAL,

[0] [1]

SS-Code, CCBS-Index

OPTIONAL,

[0] SS-Code, OPTIONAL,

314
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

17.7.5 Supplementary service codes


MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version5 (5)} DEFINITIONS ::= BEGIN SS-Code --------::= OCTET STRING (SIZE (1)) This type is used to represent the code identifying a single supplementary service, a group of supplementary services, or all supplementary services. The services and abbreviations used are defined in TS GSM 02.04. The internal structure is defined as follows: bits 87654321: group (bits 8765), and specific service (bits 4321)

allSS SS-Code ::= '00000000'B -- reserved for possible future use -- all SS

640

3GPP

641 Release 1998


25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96

322
'00010000'B '00010001'B '00010010'B '00010011'B '00010100'B '00010101'B

3GPP TS 09.02 V7.15.0 (2004-03)

allLineIdentificationSS SS-Code ::= -- reserved for possible future use -- all line identification SS clip SS-Code ::= -- calling line identification presentation clir SS-Code ::= -- calling line identification restriction colp SS-Code ::= -- connected line identification presentation colr SS-Code ::= -- connected line identification restriction mci SS-Code ::= -- reserved for possible future use -- malicious call identification allNameIdentificationSS -- all name identification SS cnap -- calling name presentation

SS-Code ::= '00011000'B SS-Code ::= '00011001'B

-- SS-Codes '00011010'B to '00011111'B are reserved for future -- NameIdentification Supplementary Service use. allForwardingSS SS-Code ::= '00100000'B -- all forwarding SS cfu SS-Code ::= '00100001'B -- call forwarding unconditional allCondForwardingSS SS-Code ::= '00101000'B -- all conditional forwarding SS cfb SS-Code ::= '00101001'B -- call forwarding on mobile subscriber busy cfnry SS-Code ::= '00101010'B -- call forwarding on no reply cfnrc SS-Code ::= '00101011'B -- call forwarding on mobile subscriber not reachable cd SS-Code ::= '00100100'B -- call deflection allCallOfferingSS SS-Code ::= '00110000'B -- reserved for possible future use -- all call offering SS includes also all forwarding SS ect SS-Code ::= '00110001'B -- explicit call transfer mah SS-Code ::= '00110010'B -- reserved for possible future use -- mobile access hunting allCallCompletionSS SS-Code ::= '01000000'B -- reserved for possible future use -- all Call completion SS cw SS-Code ::= '01000001'B -- call waiting hold SS-Code ::= '01000010'B -- call hold ccbs-A SS-Code ::= '01000011'B -- completion of call to busy subscribers, originating side ccbs-B SS-Code ::= '01000100'B -- completion of call to busy subscribers, destination side -- this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData allMultiPartySS SS-Code ::= '01010000'B -- reserved for possible future use -- all multiparty SS multiPTY SS-Code ::= '01010001'B -- multiparty allCommunityOfInterest-SS SS-Code ::= '01100000'B -- reserved for possible future use -- all community of interest SS cug SS-Code ::= '01100001'B -- closed user group

642

3GPP

643 Release 1998


97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169

323

3GPP TS 09.02 V7.15.0 (2004-03)

allChargingSS SS-Code ::= '01110000'B -- reserved for possible future use -- all charging SS aoci SS-Code ::= '01110001'B -- advice of charge information aocc SS-Code ::= '01110010'B -- advice of charge charging allAdditionalInfoTransferSS SS-Code -- reserved for possible future use -- all additional information transfer SS uus1 SS-Code -- UUS1 user-to-user signalling uus2 SS-Code -- UUS2 user-to-user signalling uus3 SS-Code -- UUS3 user-to-user signalling ::= '10000000'B ::= '10000001'B ::= '10000010'B ::= '10000011'B

allBarringSS SS-Code ::= '10010000'B -- all barring SS barringOfOutgoingCalls SS-Code ::= '10010001'B -- barring of outgoing calls baoc SS-Code ::= '10010010'B -- barring of all outgoing calls boic SS-Code ::= '10010011'B -- barring of outgoing international calls boicExHC SS-Code ::= '10010100'B -- barring of outgoing international calls except those directed -- to the home PLMN barringOfIncomingCalls SS-Code ::= '10011001'B -- barring of incoming calls baic SS-Code ::= '10011010'B -- barring of all incoming calls bicRoam SS-Code ::= '10011011'B -- barring of incoming calls when roaming outside home PLMN -- Country allPLMN-specificSS plmn-specificSS-1 plmn-specificSS-2 plmn-specificSS-3 plmn-specificSS-4 plmn-specificSS-5 plmn-specificSS-6 plmn-specificSS-7 plmn-specificSS-8 plmn-specificSS-9 plmn-specificSS-A plmn-specificSS-B plmn-specificSS-C plmn-specificSS-D plmn-specificSS-E plmn-specificSS-F SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= '11110000'B '11110001'B '11110010'B '11110011'B '11110100'B '11110101'B '11110110'B '11110111'B '11111000'B '11111001'B '11111010'B '11111011'B '11111100'B '11111101'B '11111110'B '11111111'B

allCallPrioritySS SS-Code ::= '10100000'B -- reserved for possible future use -- all call priority SS emlpp SS-Code ::= '10100001'B -- enhanced Multilevel Precedence Pre-emption (EMLPP) service allLCSPrivacyException SS-Code ::= '10110000'B -- all LCS Privacy Exception Classes universal SS-Code ::= '10110001'B -- allow location by any LCS client callrelated SS-Code ::= '10110010'B -- allow location by any value added LCS client to which a call -- is established from the target MS callunrelated SS-Code ::= '10110011'B -- allow location by designated external value added LCS clients plmnoperator SS-Code ::= '10110100'B -- allow location by designated PLMN operator LCS clients

644

3GPP

645 Release 1998


170 171 172 173 174 175 176 177 178 179 180

324

3GPP TS 09.02 V7.15.0 (2004-03)

allMOLR-SS SS-Code ::= '11000000'B -- all Mobile Originating Location Request Classes basicSelfLocation SS-Code ::= '11000001'B -- allow an MS to request its own location autonomousSelfLocation SS-Code ::= '11000010'B -- allow an MS to perform self location without interaction -- with the PLMN for a predetermined period of time transferToThirdParty SS-Code ::= '11000011'B -- allow an MS to request transfer of its location to another LCS client END

181
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

17.7.6 Short message data types


MAP-SM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version5 (5)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RoutingInfoForSM-Arg, RoutingInfoForSM-Res, MO-ForwardSM-Arg, MO-ForwardSM-Res, MT-ForwardSM-Arg, MT-ForwardSM-Res, ReportSM-DeliveryStatusArg, ReportSM-DeliveryStatusRes, AlertServiceCentreArg, InformServiceCentreArg, ReadyForSM-Arg, ReadyForSM-Res, SM-DeliveryOutcome, AlertReason ; IMPORTS AddressString, ISDN-AddressString, SignalInfo, IMSI, LMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version5 (5)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version5 (5)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version5 (5)} ; RoutingInfoForSM-Arg ::= SEQUENCE { msisdn [0] ISDN-AddressString, sm-RP-PRI [1] BOOLEAN, serviceCentreAddress [2] AddressString, extensionContainer [6] ExtensionContainer ... , gprsSupportIndicator [7] NULL -- gprsSupportIndicator is set only if the SMS-GMSC supports -- receiving of two numbers from the HLR sm-RP-MTI [8] SM-RP-MTI OPTIONAL, sm-RP-SMEA [9] SM-RP-SMEA

OPTIONAL, OPTIONAL,

OPTIONAL }

646

3GPP

647 Release 1998


64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137

325

3GPP TS 09.02 V7.15.0 (2004-03)

SM-RP-MTI ::= INTEGER (0..10) -- 0 SMS Deliver -- 1 SMS Status Report -- other values are reserved for future use and shall be discarded if -- received SM-RP-SMEA ::= OCTET STRING (SIZE (1..12)) -- this parameter contains an address field which is encoded -- as defined in GSM 03.40. An address field contains 3 elements : -address-length -type-of-address -address-value RoutingInfoForSM-Res ::= SEQUENCE { imsi locationInfoWithLMSI extensionContainer ...} LocationInfoWithLMSI ::= SEQUENCE { networkNode-Number lmsi extensionContainer ..., gprsNodeIndicator -- gprsNodeIndicator is set only if -- Network Node Number additional-Number -- NetworkNode-number can be either }

IMSI, [0] LocationInfoWithLMSI, [4] ExtensionContainer

OPTIONAL,

[1] ISDN-AddressString, LMSI ExtensionContainer [5] NULL the SGSN number is sent as the [6] Additional-Number msc-number or sgsn-number

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

Additional-Number ::= CHOICE { msc-Number [0] ISDN-AddressString, sgsn-Number [1] ISDN-AddressString} -- additional-number can be either msc-number or sgsn-number -- if received networkNode-number is msc-number then the -- additional number is sgsn-number -- if received networkNode-number is sgsn-number then the -- additional number is msc-number MO-ForwardSM-Arg ::= SEQUENCE { sm-RP-DA sm-RP-OA sm-RP-UI extensionContainer ... , imsi MO-ForwardSM-Res ::= SEQUENCE { sm-RP-UI extensionContainer ...} MT-ForwardSM-Arg ::= SEQUENCE { sm-RP-DA sm-RP-OA sm-RP-UI moreMessagesToSend extensionContainer ...} MT-ForwardSM-Res ::= SEQUENCE { sm-RP-UI extensionContainer ...} SM-RP-DA ::= CHOICE { imsi lmsi serviceCentreAddressDA noSM-RP-DA SM-RP-DA, SM-RP-OA, SignalInfo, ExtensionContainer IMSI SignalInfo ExtensionContainer

OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL,

SM-RP-DA, SM-RP-OA, SignalInfo, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

SignalInfo ExtensionContainer

OPTIONAL, OPTIONAL,

[0] [1] [4] [5]

IMSI, LMSI, AddressString, NULL}

648

3GPP

649 Release 1998


138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214

326

3GPP TS 09.02 V7.15.0 (2004-03)

SM-RP-OA ::= CHOICE { msisdn serviceCentreAddressOA noSM-RP-OA

[2] ISDN-AddressString, [4] AddressString, [5] NULL}

ReportSM-DeliveryStatusArg ::= SEQUENCE { msisdn ISDN-AddressString, serviceCentreAddress AddressString, sm-DeliveryOutcome SM-DeliveryOutcome, absentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM

OPTIONAL, extensionContainer [1] ExtensionContainer OPTIONAL, ..., gprsSupportIndicator [2] NULL OPTIONAL, -- gprsSupportIndicator is set only if the SMS-GMSC supports -- handling of two delivery outcomes deliveryOutcomeIndicator [3] NULL OPTIONAL, -- DeliveryOutcomeIndicator is set when the SM-DeliveryOutcome -- is for GPRS additionalSM-DeliveryOutcome [4] SM-DeliveryOutcome OPTIONAL, -- If received, additionalSM-DeliveryOutcome is for GPRS -- If DeliveryOutcomeIndicator is set, then AdditionalSM-DeliveryOutcome shall be absent additionalAbsentSubscriberDiagnosticSM [5] AbsentSubscriberDiagnosticSM OPTIONAL -- If received additionalAbsentSubscriberDiagnosticSM is for GPRS -- If DeliveryOutcomeIndicator is set, then AdditionalAbsentSubscriberDiagnosticSM -- shall be absent }

SM-DeliveryOutcome ::= ENUMERATED { memoryCapacityExceeded (0), absentSubscriber (1), successfulTransfer (2)} ReportSM-DeliveryStatusRes ::= SEQUENCE { storedMSISDN ISDN-AddressString extensionContainer ExtensionContainer ...} AlertServiceCentreArg ::= SEQUENCE { msisdn serviceCentreAddress ...} InformServiceCentreArg ::= SEQUENCE { storedMSISDN mw-Status MW-Status extensionContainer ...} OPTIONAL, OPTIONAL,

ISDN-AddressString, AddressString,

ISDN-AddressString OPTIONAL, ExtensionContainer

OPTIONAL, OPTIONAL,

MW-Status ::= BIT STRING { sc-AddressNotIncluded (0), mnrf-Set (1), mcef-Set (2) , mnrg-Set (3)} (SIZE (6..16)) -- exception handling: -- bits 4 to 15 shall be ignored if received and not understood ReadyForSM-Arg ::= SEQUENCE { imsi [0] IMSI, alertReason AlertReason, alertReasonIndicator NULL -- alertReasonIndicator is set only when the alertReason -- sent to HLR is for GPRS exte