Anda di halaman 1dari 1271

1

3GPP TS 29.002 V4.17.0 (2006-06)


Technical Specification

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

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

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 Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational 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 Organizational Partners' Publications Offices.

2 3 4

3 Release 4 4 5

3GPP TS 29.002 V4.17.0 (2006-06)

Keywords
GSM, UMTS, MAP, SS7, network

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

7 Release 4 8 9

3GPP TS 29.002 V4.17.0 (2006-06)

Contents

7 Contents....................................................................................................................................................3 8 Foreword.................................................................................................................................................25 9 1 Scope....................................................................................................................................................26 10 2 References............................................................................................................................................26 11 3 Abbreviations.......................................................................................................................................31 12 4 Void.....................................................................................................................................................31 13 5 Overload and compatibility overview..................................................................................................31
14 15 16 17 18 19 20 21 22 23 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

5.1 Overload control...................................................................................................................................................31 5.1.1 Overload control for MSC (outside MAP)........................................................................................................31 5.1.2 Overload control for MAP entities....................................................................................................................32 5.1.3 Congestion control for Signalling System No. 7..............................................................................................36 5.2 Compatibility........................................................................................................................................................36 5.2.1 General 36 5.2.2 Strategy for selecting the Application Context (AC) version...........................................................................36 5.2.2.1 Proposed method............................................................................................................................................36 5.2.2.2 Managing the version look-up table...............................................................................................................37 5.2.2.3 Optimising the method...................................................................................................................................38 6.1 Use of SCCP........................................................................................................................................................38 6.1.1 SCCP Class.......................................................................................................................................................38 6.1.2 Sub-System Number (SSN)..............................................................................................................................38 6.1.3 SCCP addressing...............................................................................................................................................39 6.1.3.1 Introduction....................................................................................................................................................39 6.1.3.2 The Mobile-services Switching Centre (MSC)..............................................................................................41 6.1.3.2.1 MSC interaction during handover or relocation..........................................................................................41 6.1.3.2.2 MSC for short message routing...................................................................................................................41 6.1.3.2.3 MSC for location request routing................................................................................................................41 6.1.3.2.4 MSC for LMU Control................................................................................................................................41 6.1.3.3 The Home Location Register (HLR)..............................................................................................................41 6.1.3.3.1 During call set-up........................................................................................................................................41 6.1.3.3.2 Before location updating completion..........................................................................................................42 6.1.3.3.3 After location updating completion............................................................................................................42 6.1.3.3.4 VLR restoration...........................................................................................................................................43 6.1.3.3.5 During Network-Requested PDP Context Activation.................................................................................43 6.1.3.3.6 Before GPRS location updating completion...............................................................................................43 6.1.3.3.7 After GPRS location updating completion.................................................................................................44 6.1.3.3.8 Query for a Location Request.....................................................................................................................44 6.1.3.4 The Visitor Location Register (VLR)............................................................................................................44 6.1.3.4.1 Inter-VLR information retrieval..................................................................................................................44 6.1.3.4.2 HLR request................................................................................................................................................44 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service......................................................................44 6.1.3.6 The Equipment Identity Register (EIR).........................................................................................................44 6.1.3.7 The Shared Inter Working Function (SIWF).................................................................................................45 6.1.3.8 The Serving GPRS Support Node (SGSN)....................................................................................................45 6.1.3.9 The Gateway GPRS Support Node (GGSN).................................................................................................45 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service.............................................................................45 6.1.3.10A Void 45 6.1.3.10A.1 Void 45 6.1.3.10A.2 Void 45 6.1.3.10B The Gateway Mobile Location Centre (GMLC).......................................................................................45 6.1.3.11 Summary table.............................................................................................................................................45 6.2 Use of TC.............................................................................................................................................................49

24 6 Requirements concerning the use of SCCP and TC.............................................................................38

10

59 7 General on MAP services.....................................................................................................................49


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

11 Release 4 12 13

3GPP TS 29.002 V4.17.0 (2006-06)

7.1 Terminology and definitions................................................................................................................................49 7.2 Modelling principles............................................................................................................................................49 7.3 Common MAP services.......................................................................................................................................50 7.3.1 MAP-OPEN service..........................................................................................................................................51 7.3.2 MAP-CLOSE service........................................................................................................................................54 7.3.3 MAP-DELIMITER service...............................................................................................................................54 7.3.4 MAP-U-ABORT service...................................................................................................................................54 7.3.5 MAP-P-ABORT service...................................................................................................................................55 7.3.6 MAP-NOTICE service......................................................................................................................................56 7.3.7 void 57 7.3.8 void 57 7.3.9 void 57 7.3.10 void 57 7.4 Sequencing of services.........................................................................................................................................57 7.5 General rules for mapping of services onto TC...................................................................................................58 7.5.1 Mapping of common services...........................................................................................................................58 7.5.2 Mapping of user specific services.....................................................................................................................59 7.6 Definition of parameters......................................................................................................................................60 7.6.1 Common parameters.........................................................................................................................................62 7.6.1.1 Invoke Id 62 7.6.1.2 Linked Id 62 7.6.1.3 Provider error.................................................................................................................................................62 7.6.1.4 User error63 7.6.2 Numbering and identification parameters.........................................................................................................66 7.6.2.1 IMSI 66 7.6.2.2 TMSI 66 7.6.2.3 IMEI 66 7.6.2.4 Previous location area Id................................................................................................................................66 7.6.2.5 Stored location area Id...................................................................................................................................66 7.6.2.6 Current location area Id..................................................................................................................................66 7.6.2.7 Target location area Id...................................................................................................................................66 7.6.2.8 Target cell Id..................................................................................................................................................66 7.6.2.8A Target RNC Id.............................................................................................................................................67 7.6.2.9 Void 67 7.6.2.10 Originating entity number............................................................................................................................67 7.6.2.11 MSC number................................................................................................................................................67 7.6.2.12 Target MSC number.....................................................................................................................................67 7.6.2.13 HLR number.................................................................................................................................................67 7.6.2.14 VLR number.................................................................................................................................................67 7.6.2.15 HLR Id 67 7.6.2.16 LMSI 67 7.6.2.17 MS ISDN......................................................................................................................................................67 7.6.2.18 OMC Id 67 7.6.2.19 Roaming number..........................................................................................................................................67 7.6.2.19A Relocation Number List............................................................................................................................67 7.6.2.20 Void 67 7.6.2.21 Handover number.........................................................................................................................................67 7.6.2.22 Forwarded-to number...................................................................................................................................68 7.6.2.22A Long forwarded-to number.......................................................................................................................68 7.6.2.22B Long FTN Supported.................................................................................................................................68 7.6.2.23 Forwarded-to subaddress.............................................................................................................................68 7.6.2.24 Called number..............................................................................................................................................68 7.6.2.25 Calling number.............................................................................................................................................68 7.6.2.26 Originally dialled number............................................................................................................................68 7.6.2.27 Service centre address..................................................................................................................................68 7.6.2.28 Zone Code....................................................................................................................................................68 7.6.2.29 MSIsdn-Alert................................................................................................................................................68 7.6.2.30 Location Information...................................................................................................................................68 7.6.2.31 GMSC Address............................................................................................................................................68 7.6.2.32 VMSC Address............................................................................................................................................68

14

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

15 Release 4 16 17

3GPP TS 29.002 V4.17.0 (2006-06)

7.6.2.33 Group Id.......................................................................................................................................................69 7.6.2.34 North American Equal Access preferred Carrier Id.....................................................................................69 7.6.2.35 SIWFS Number............................................................................................................................................69 7.6.2.36 B-subscriber address....................................................................................................................................69 7.6.2.37 Serving cell Id..............................................................................................................................................69 7.6.2.38 SGSN number..............................................................................................................................................69 7.6.2.39 SGSN address...............................................................................................................................................69 7.6.2.40 GGSN address..............................................................................................................................................69 7.6.2.41 GGSN number..............................................................................................................................................69 7.6.2.42 APN 69 7.6.2.43 Network Node number.................................................................................................................................69 7.6.2.44 PDP-Type.....................................................................................................................................................69 7.6.2.45 PDP-Address................................................................................................................................................70 7.6.2.46 Additional number.......................................................................................................................................70 7.6.2.47 P-TMSI 70 7.6.2.48 B-subscriber number....................................................................................................................................70 7.6.2.49 B-subscriber subaddress...............................................................................................................................70 7.6.2.50 LMU Number ..............................................................................................................................................70 7.6.2.51 MLC Number ..............................................................................................................................................70 7.6.2.52 Multicall Bearer Information.......................................................................................................................70 7.6.2.53 Multiple Bearer Requested...........................................................................................................................70 7.6.2.54 Multiple Bearer Not Supported....................................................................................................................70 7.6.2.55 PDP-Charging Characteristics.....................................................................................................................70 7.6.2.56 Selected RAB ID..........................................................................................................................................70 7.6.2.57 RAB ID 70 7.6.3 Subscriber management parameters..................................................................................................................70 7.6.3.1 Category 70 7.6.3.2 Equipment status............................................................................................................................................71 7.6.3.3 Extensible Bearer service...............................................................................................................................71 7.6.3.4 Extensible Teleservice...................................................................................................................................71 7.6.3.5 Extensible Basic Service Group.....................................................................................................................71 7.6.3.6 GSM bearer capability...................................................................................................................................71 7.6.3.7 Subscriber Status............................................................................................................................................71 7.6.3.8 CUG Outgoing Access indicator....................................................................................................................71 7.6.3.9 Operator Determined Barring General Data..................................................................................................71 7.6.3.10 ODB HPLMN Specific Data........................................................................................................................73 7.6.3.11 Regional Subscription Data..........................................................................................................................74 7.6.3.12 Regional Subscription Response..................................................................................................................74 7.6.3.13 Roaming Restriction Due To Unsupported Feature.....................................................................................74 7.6.3.14 Extensible SS-Info.......................................................................................................................................74 7.6.3.15 Extensible forwarding information..............................................................................................................74 7.6.3.16 Extensible forwarding feature......................................................................................................................74 7.6.3.17 Extensible SS-Status....................................................................................................................................75 7.6.3.18 Extensible Forwarding Options....................................................................................................................75 7.6.3.19 Extensible No reply condition timer............................................................................................................75 7.6.3.20 Extensible Call barring information.............................................................................................................75 7.6.3.21 Extensible Call barring feature.....................................................................................................................75 7.6.3.22 CUG info......................................................................................................................................................75 7.6.3.23 CUG subscription.........................................................................................................................................76 7.6.3.24 CUG interlock..............................................................................................................................................76 7.6.3.25 CUG index...................................................................................................................................................76 7.6.3.26 CUG feature.................................................................................................................................................76 7.6.3.27 Inter CUG options........................................................................................................................................76 7.6.3.28 Intra CUG restrictions..................................................................................................................................76 7.6.3.29 Extensible SS-Data.......................................................................................................................................77 7.6.3.30 Subscriber State............................................................................................................................................77 7.6.3.31 Requested Info.............................................................................................................................................77 7.6.3.32 Suppression of Announcement....................................................................................................................77 7.6.3.33 Suppress T-CSI............................................................................................................................................77 7.6.3.34 GMSC CAMEL Subscription Info...............................................................................................................77 7.6.3.35 VLR CAMEL Subscription Info..................................................................................................................77

18

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

19 Release 4 20 21

3GPP TS 29.002 V4.17.0 (2006-06)

7.6.3.36 Supported CAMEL Phases in the VLR.......................................................................................................77 7.6.3.36A Supported CAMEL Phases in the SGSN..................................................................................................77 7.6.3.37 CUG Subscription Flag................................................................................................................................77 7.6.3.38 CAMEL Subscription Info Withdraw..........................................................................................................77 7.6.3.39 Voice Group Call Service (VGCS) Data.....................................................................................................78 7.6.3.40 Voice Broadcast Service (VBS) Data..........................................................................................................78 7.6.3.41 ISDN bearer capability.................................................................................................................................78 7.6.3.42 Lower layer Compatibility...........................................................................................................................78 7.6.3.43 High Layer Compatibility............................................................................................................................78 7.6.3.44 Alerting Pattern............................................................................................................................................78 7.6.3.45 GPRS Subscription Data Withdraw.............................................................................................................78 7.6.3.46 GPRS Subscription Data..............................................................................................................................78 7.6.3.47 QoS-Subscribed............................................................................................................................................78 7.6.3.48 VPLMN address allowed.............................................................................................................................78 7.6.3.49 Roaming Restricted In SGSN Due To Unsupported Feature.......................................................................78 7.6.3.50 Network Access Mode.................................................................................................................................78 7.6.3.51 Mobile Not Reachable Reason.....................................................................................................................78 7.6.3.52 Cancellation Type........................................................................................................................................79 7.6.3.53 All GPRS Data.............................................................................................................................................79 7.6.3.54 Complete Data List Included.......................................................................................................................79 7.6.3.55 PDP Context Identifier.................................................................................................................................79 7.6.3.56 LSA Information..........................................................................................................................................79 7.6.3.57 SoLSA support indicator..............................................................................................................................79 7.6.3.58 LSA Information Withdraw.........................................................................................................................79 7.6.3.59 LMU Indicator.............................................................................................................................................79 7.6.3.60 LCS Information..........................................................................................................................................79 7.6.3.61 GMLC List...................................................................................................................................................79 7.6.3.62 LCS Privacy Exception List.........................................................................................................................79 7.6.3.63 LCS Privacy Exception Parameters.............................................................................................................80 7.6.3.64 External Client List .....................................................................................................................................80 7.6.3.65 Internal Client List ......................................................................................................................................80 7.6.3.65A MO-LR List...............................................................................................................................................80 7.6.3.65B Privacy Notification to MS User...............................................................................................................80 7.6.3.65C GMLC List Withdraw...............................................................................................................................80 7.6.3.66 IST Alert Timer............................................................................................................................................80 7.6.3.67 Call Termination Indicator...........................................................................................................................80 7.6.3.68 IST Information Withdraw...........................................................................................................................80 7.6.3.69 IST Support Indicator...................................................................................................................................81 7.6.3.70 Super-Charger Supported In HLR...............................................................................................................81 7.6.3.71 Super-Charger Supported In Serving Network Entity.................................................................................81 7.6.3.72 Age Indicator................................................................................................................................................81 7.6.3.73 GPRS enhancements support indicator........................................................................................................81 7.6.3.74 Extensible QoS-Subscribed..........................................................................................................................81 7.6.3.75 SGSN Camel Subscription Info...................................................................................................................81 7.6.3.76 SMS-CSI......................................................................................................................................................81 7.6.3.77 GPRS-CSI....................................................................................................................................................81 7.6.3.78 CAMEL subscription info............................................................................................................................81 7.6.3.83 Call Barring Data.........................................................................................................................................82 7.6.3.84 Call Forwarding Data...................................................................................................................................82 7.6.3.85 ODB Data.....................................................................................................................................................82 7.6.3.86 Requested Subscription Info........................................................................................................................82 7.6.3.87 CS Allocation/Retention priority.................................................................................................................82 7.6.3.88 ODB Info......................................................................................................................................................82 7.6.4 Supplementary services parameters..................................................................................................................82 7.6.4.1 SS-Code 82 7.6.4.2 SS-Status 83 7.6.4.3 SS-Data 83 7.6.4.4 Override Category..........................................................................................................................................83 7.6.4.5 CLI Restriction Option...................................................................................................................................84 7.6.4.6 Forwarding Options.......................................................................................................................................84 7.6.4.7 No reply condition timer................................................................................................................................84

22

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

23 Release 4 24 25

3GPP TS 29.002 V4.17.0 (2006-06)

7.6.4.8 - 7.6.4.14 Void...............................................................................................................................................84 7.6.4.15 Forwarding information...............................................................................................................................84 7.6.4.16 Forwarding feature.......................................................................................................................................84 7.6.4.17 Void 85 7.6.4.18 Call barring information...............................................................................................................................85 7.6.4.19 Call barring feature......................................................................................................................................85 7.6.4.20 New password..............................................................................................................................................85 7.6.4.21 Current password.........................................................................................................................................85 7.6.4.22 Guidance information...................................................................................................................................85 7.6.4.23 Void 85 7.6.4.24 SS-Info 85 7.6.4.25 - 7.6.4.35 Void.............................................................................................................................................86 7.6.4.36 USSD Data Coding Scheme.........................................................................................................................86 7.6.4.37 USSD String.................................................................................................................................................86 7.6.4.38 Bearer service...............................................................................................................................................86 7.6.4.39 Teleservice...................................................................................................................................................86 7.6.4.40 Basic Service Group.....................................................................................................................................86 7.6.4.41 eMLPP information......................................................................................................................................86 7.6.4.42 SS-event.......................................................................................................................................................86 7.6.4.43 SS-event data................................................................................................................................................87 7.6.4.44 LCS Privacy Exceptions .............................................................................................................................87 7.6.4.45 Mobile Originating Location Request (MO-LR).........................................................................................87 7.6.4.46 NbrUser 87 7.6.4.47 MC Subscription Data..................................................................................................................................87 7.6.4.48 MC Information...........................................................................................................................................87 7.6.4.49 CCBS Request State.....................................................................................................................................88 7.6.5 Call parameters..................................................................................................................................................88 7.6.5.1 Call reference number....................................................................................................................................88 7.6.5.2 Interrogation type...........................................................................................................................................88 7.6.5.3 OR interrogation.............................................................................................................................................88 7.6.5.4 OR capability.................................................................................................................................................88 7.6.5.5 Forwarding reason..........................................................................................................................................88 7.6.5.6 Forwarding interrogation required.................................................................................................................88 7.6.5.7 O-CSI 88 7.6.5.7A D-CSI 89 7.6.5.7B T-CSI 89 7.6.5.7C VT-CSI 89 7.6.5.8 Call Direction.................................................................................................................................................89 7.6.5.9 Channel Type.................................................................................................................................................89 7.6.5.10 Chosen Channel...........................................................................................................................................89 7.6.5.11 CCBS Feature...............................................................................................................................................89 7.6.5.12 UU Data89 7.6.5.14 Number Portability Status............................................................................................................................89 7.6.5.15 Pre-paging supported...................................................................................................................................89 7.6.6 Radio parameters...............................................................................................................................................90 7.6.6.1 - 7.6.6.4 Void................................................................................................................................................90 7.6.6.5 BSSMAP Service Handover.........................................................................................................................90 7.6.6.5A BSSMAP Service Handover List...............................................................................................................90 7.6.6.6 RANAP Service Handover...........................................................................................................................90 7.6.6.7 HO-Number Not Required.............................................................................................................................90 7.6.6.8 Integrity Protection Information....................................................................................................................90 7.6.6.9 Encryption Information..................................................................................................................................90 7.6.6.10 Radio Resource Information........................................................................................................................90 7.6.6.10A Radio Resource List..................................................................................................................................90 7.6.6.10B Chosen Radio Resource Information.........................................................................................................90 7.6.6.11 Key Status....................................................................................................................................................90 7.6.6.12 Selected UMTS Algorithms.........................................................................................................................90 7.6.6.13 Allowed GSM Algorithms...........................................................................................................................90 7.6.6.14 Allowed UMTS Algorithms.........................................................................................................................91 7.6.6.15 Selected GSM Algorithm.............................................................................................................................91 7.6.7 Authentication parameters................................................................................................................................91

26

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

27 Release 4 28 29

3GPP TS 29.002 V4.17.0 (2006-06)

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 Xres 91 7.6.7.5A Ck 91 7.6.7.5B Ik 91 7.6.7.5C Autn 91 7.6.7.6 Cksn 91 7.6.7.6A Ksi 91 7.6.7.6B Auts 91 7.6.7.7 Ciphering mode..............................................................................................................................................92 7.6.7.8 Current Security Context................................................................................................................................92 7.6.7.9 Failure cause...................................................................................................................................................92 7.6.7.10 Re-attempt....................................................................................................................................................92 7.6.7.11 Access Type.................................................................................................................................................92 7.6.8 Short message parameters.................................................................................................................................92 7.6.8.1 SM-RP-DA.....................................................................................................................................................92 7.6.8.2 SM-RP-OA.....................................................................................................................................................92 7.6.8.3 MWD status...................................................................................................................................................93 7.6.8.4 SM-RP-UI......................................................................................................................................................93 7.6.8.5 SM-RP-PRI....................................................................................................................................................93 7.6.8.6 SM Delivery Outcome...................................................................................................................................93 7.6.8.7 More Messages To Send................................................................................................................................93 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...................................................................................................................................94 7.6.8.15 GPRS Support Indicator...............................................................................................................................94 7.6.8.16 SM-RP-MTI.................................................................................................................................................94 7.6.8.17 SM-RP-SMEA.............................................................................................................................................94 7.6.9 Access and signalling system related parameters.............................................................................................94 7.6.9.1 AN-apdu 94 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........................................................................................................................95 7.6.9.6 Location update type......................................................................................................................................95 7.6.9.7 Protocol ID.....................................................................................................................................................95 7.6.9.8 Network signal information...........................................................................................................................95 7.6.9.9 Call Info 96 7.6.9.10 Additional signal info...................................................................................................................................96 7.6.10 System operations parameters.........................................................................................................................96 7.6.10.1 Network resources........................................................................................................................................96 7.6.10.2 Trace reference.............................................................................................................................................97 7.6.10.3 Trace type.....................................................................................................................................................97 7.6.11 Location Service Parameters ..........................................................................................................................97 7.6.11.1 Age of Location Estimate.............................................................................................................................97 7.6.11.2 Deferred MT-LR Response Indicator .........................................................................................................97 7.6.11.3 Deferred MT-LR Data..................................................................................................................................97 7.6.11.4 LCS Client ID..............................................................................................................................................97 7.6.11.5 LCS Event....................................................................................................................................................97 7.6.11.7 LCS Priority.................................................................................................................................................97 7.6.11.8 LCS QoS......................................................................................................................................................97 7.6.11.9 Void 98 7.6.11.10 Void 98 7.6.11.11 Location Estimate.......................................................................................................................................98 7.6.11.12 Location Type............................................................................................................................................98

30

364 365 366 367 368 369 370 371 372 373 374 375 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

31 Release 4 32 33

3GPP TS 29.002 V4.17.0 (2006-06)

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........................................................................................................................................99 7.6.11.17 Supported LCS Capability Sets..................................................................................................................99 7.6.11.18 Void 99 7.6.11.19 NA-ESRK Request.....................................................................................................................................99 7.6.11.20 Supported GAD Shapes.............................................................................................................................99 7.6.11.21 Additional Location Estimate....................................................................................................................99 7.6.11.22 LCS-Reference Number.............................................................................................................................99 7.6.12 void 99 7.7 Representation of a list of a basic parameter in service-primitives.....................................................................99 8.1 Location management services..........................................................................................................................100 8.1.1 Void 100 8.1.1.1 Void 100 8.1.1.2 Void 100 8.1.1.3 Void 100 8.1.2 MAP_UPDATE_LOCATION service............................................................................................................100 8.1.2.1 Definition.....................................................................................................................................................100 8.1.2.2 Service primitives.........................................................................................................................................100 8.1.2.3 Parameter definitions and use......................................................................................................................100 8.1.3 MAP_CANCEL_LOCATION service...........................................................................................................102 8.1.3.1 Definition.....................................................................................................................................................102 8.1.3.2 Service primitives.........................................................................................................................................102 8.1.3.3 Parameter definitions and use......................................................................................................................103 8.1.4 MAP_SEND_IDENTIFICATION service.....................................................................................................103 8.1.4.1 Definition.....................................................................................................................................................103 8.1.4.2 Service primitives.........................................................................................................................................103 8.1.4.3 Parameter definitions and use......................................................................................................................103 8.1.5 Void 104 8.1.5.1 Void 104 8.1.5.2 Void 104 8.1.5.3 Void 104 8.1.6 MAP_PURGE_MS service.............................................................................................................................104 8.1.6.1 Definition.....................................................................................................................................................104 8.1.6.2 Service primitives.........................................................................................................................................105 8.1.6.3 Parameter definitions and use......................................................................................................................105 8.1.7 MAP_UPDATE_GPRS_LOCATION service................................................................................................106 8.1.7.1 Definition.....................................................................................................................................................106 8.1.7.2 Service primitives.........................................................................................................................................106 8.1.7.3 Parameter definitions and use......................................................................................................................106 8.1.8 MAP-NOTE-MM-EVENT.............................................................................................................................107 8.1.8.1 Definition.....................................................................................................................................................108 8.1.8.2 Service primitives.........................................................................................................................................108 8.1.8.3 Parameter use...............................................................................................................................................108 8.2 Paging and search...............................................................................................................................................109 8.2.1 MAP_PAGE service.......................................................................................................................................109 8.2.1.1 Definition.....................................................................................................................................................109 8.2.1.2 Service primitives.........................................................................................................................................109 8.2.1.3 Parameter definitions and use......................................................................................................................109 8.2.2 MAP_SEARCH_FOR_MS service................................................................................................................110 8.2.2.1 Definition.....................................................................................................................................................110 8.2.2.2 Service primitives.........................................................................................................................................110 8.2.2.3 Parameter definitions and use......................................................................................................................110 8.3 Access management services.............................................................................................................................111 8.3.1 MAP_PROCESS_ACCESS_REQUEST service...........................................................................................111 8.3.1.1 Definition.....................................................................................................................................................111 8.3.1.2 Service primitives.........................................................................................................................................111 8.3.1.3 Parameter definitions and use......................................................................................................................111

376 8 Mobility services................................................................................................................................100

34

424 425 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

35 Release 4 36 37

10

3GPP TS 29.002 V4.17.0 (2006-06)

8.4 Handover services..............................................................................................................................................112 8.4.1 MAP_PREPARE_HANDOVER service........................................................................................................112 8.4.1.1 Definition.....................................................................................................................................................113 8.4.1.2 Service primitives.........................................................................................................................................113 8.4.1.3 Parameter use...............................................................................................................................................113 8.4.2 MAP_SEND_END_SIGNAL service............................................................................................................116 8.4.2.1 Definition.....................................................................................................................................................116 8.4.2.2 Service primitives.........................................................................................................................................116 8.4.2.3 Parameter use...............................................................................................................................................116 8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service.....................................................................................116 8.4.3.1 Definition.....................................................................................................................................................116 8.4.3.2 Service primitives.........................................................................................................................................117 8.4.3.3 Parameter use...............................................................................................................................................117 8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service..................................................................................117 8.4.4.1 Definition.....................................................................................................................................................117 8.4.4.2 Service primitives.........................................................................................................................................117 8.4.4.3 Parameter use...............................................................................................................................................118 8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service............................................................................119 8.4.5.1 Definition.....................................................................................................................................................119 8.4.5.2 Service primitives.........................................................................................................................................119 8.4.5.3 Parameter use...............................................................................................................................................119 8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service.................................................................................120 8.4.6.1 Definition.....................................................................................................................................................120 8.4.6.2 Service primitives.........................................................................................................................................120 8.4.6.3 Parameter use...............................................................................................................................................120 8.4.7 MAP_SEND_HANDOVER_REPORT service..............................................................................................120 8.4.7.1 Definition.....................................................................................................................................................120 8.4.7.2 Service primitives.........................................................................................................................................121 8.4.7.3 Parameter use...............................................................................................................................................121 8.5 Authentication management services.................................................................................................................121 8.5.1 MAP_AUTHENTICATE service...................................................................................................................121 8.5.1.1 Definition.....................................................................................................................................................121 8.5.1.2 Service primitives.........................................................................................................................................121 8.5.1.3 Parameter use...............................................................................................................................................122 8.5.2 MAP_SEND_AUTHENTICATION_INFO service.......................................................................................122 8.5.2.1 Definition.....................................................................................................................................................122 8.5.2.2 Service primitives.........................................................................................................................................122 8.5.2.3 Parameter use...............................................................................................................................................123 8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service..........................................................................124 8.5.3.1 Definition.....................................................................................................................................................124 8.5.3.2 Service primitives.........................................................................................................................................124 8.5.3.3 Parameter use...............................................................................................................................................124 8.6 Security management services...........................................................................................................................125 8.6.1 MAP_SET_CIPHERING_MODE service......................................................................................................125 8.6.1.1 Definitions....................................................................................................................................................125 8.6.1.2 Service primitives.........................................................................................................................................125 8.6.1.3 Parameter use...............................................................................................................................................125 8.7 International mobile equipment identities management services......................................................................126 8.7.1 MAP_CHECK_IMEI service..........................................................................................................................126 8.7.1.1 Definition.....................................................................................................................................................126 8.7.1.2 Service primitives.........................................................................................................................................126 8.7.1.3 Parameter use...............................................................................................................................................126 8.7.2 MAP_OBTAIN_IMEI service........................................................................................................................127 8.7.2.1 Definition.....................................................................................................................................................127 8.7.2.2 Service primitives.........................................................................................................................................127 8.7.2.3 Parameter use...............................................................................................................................................127 8.8 Subscriber management services.......................................................................................................................127 8.8.1 MAP-INSERT-SUBSCRIBER-DATA service..............................................................................................127 8.8.1.1 Definition.....................................................................................................................................................127 8.8.1.2 Service primitives.........................................................................................................................................128 8.8.1.3 Parameter use...............................................................................................................................................129

38

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

39 Release 4 40 41

11

3GPP TS 29.002 V4.17.0 (2006-06)

8.8.1.4 Basic service information related to supplementary services......................................................................137 8.8.2 MAP-DELETE-SUBSCRIBER-DATA service.............................................................................................138 8.8.2.1 Definition.....................................................................................................................................................138 8.8.2.2 Service primitives.........................................................................................................................................138 8.8.2.3 Parameter use...............................................................................................................................................138 8.9 Identity management services............................................................................................................................141 8.9.1 MAP-PROVIDE-IMSI service.......................................................................................................................141 8.9.1.1 Definition.....................................................................................................................................................141 8.9.1.2 Service primitives.........................................................................................................................................141 8.9.1.3 Parameter use...............................................................................................................................................141 8.9.2 MAP-FORWARD-NEW-TMSI service.........................................................................................................141 8.9.2.1 Definition.....................................................................................................................................................142 8.9.2.2 Service primitives.........................................................................................................................................142 8.9.2.3 Parameter use...............................................................................................................................................142 8.10 Fault recovery services.....................................................................................................................................142 8.10.1 MAP_RESET service....................................................................................................................................142 8.10.1.1 Definition...................................................................................................................................................142 8.10.1.2 Service primitives.......................................................................................................................................142 8.10.1.3 Parameter definition and use......................................................................................................................142 8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service............................................................................142 8.10.2.1 Definition...................................................................................................................................................143 8.10.2.2 Service primitives.......................................................................................................................................143 8.10.2.3 Parameter definition and use......................................................................................................................143 8.10.3 MAP_RESTORE_DATA service.................................................................................................................143 8.10.3.1 Definition...................................................................................................................................................143 8.10.3.2 Service primitives.......................................................................................................................................143 8.10.3.3 Parameter definitions and use....................................................................................................................143 8.11 Subscriber Information services.......................................................................................................................145 8.11.1 MAP-ANY-TIME-INTERROGATION service...........................................................................................145 8.11.1.1 Definition...................................................................................................................................................145 8.11.1.2 Service primitives.......................................................................................................................................145 8.11.1.3 Parameter definition and use......................................................................................................................145 8.11.2 MAP-PROVIDE-SUBSCRIBER-Info service.............................................................................................146 8.11.2.1 Definition...................................................................................................................................................146 8.11.2.2 Service primitives.......................................................................................................................................146 8.11.2.3 Parameter definition and use......................................................................................................................146 8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service.............................................................146 8.11.3.1 Definition...................................................................................................................................................146 8.11.3.2 Service primitives.......................................................................................................................................147 8.11.3.3 Parameter definition and use......................................................................................................................147 8.11.4 MAP-ANY-TIME-MODIFICATION service..............................................................................................147 8.11.4.1 Definition...................................................................................................................................................147 8.11.4.2 Service primitives.......................................................................................................................................148 8.11.4.3 Parameter definition and use......................................................................................................................148 8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service...........................................................................148 8.11.5.1 Definition...................................................................................................................................................149 8.11.5.2 Service primitives.......................................................................................................................................149 8.11.5.3 Parameter definition and use......................................................................................................................149 9.1 Subscriber tracing services.................................................................................................................................150 9.1.1 MAP-ACTIVATE-TRACE-MODE service...................................................................................................150 9.1.1.1 Definition.....................................................................................................................................................150 9.1.1.2 Service primitives.........................................................................................................................................150 9.1.1.3 Parameter use...............................................................................................................................................150 9.1.2 MAP-DEACTIVATE-TRACE-MODE service..............................................................................................151 9.1.2.1 Definition.....................................................................................................................................................151 9.1.2.2 Service primitives.........................................................................................................................................151 9.1.2.3 Parameter use...............................................................................................................................................151 9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service.......................................................................................152 9.1.3.1 Definition.....................................................................................................................................................152

533 9 Operation and maintenance services..................................................................................................150

42

545 546 547 548 549 550 551 553 554 555 556 557 558 559 560 561 562 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

43 Release 4 44 45

12

3GPP TS 29.002 V4.17.0 (2006-06)

9.1.3.2 Service primitives.........................................................................................................................................152 9.1.3.3 Parameter use...............................................................................................................................................152 9.2 Other operation and maintenance services.........................................................................................................152 9.2.1 MAP-SEND-IMSI service..............................................................................................................................152 9.2.1.1 Definition.....................................................................................................................................................152 9.2.1.2 Service primitives.........................................................................................................................................153 9.2.1.3 Parameter use...............................................................................................................................................153 10.1 MAP_SEND_ROUTING_INFORMATION service......................................................................................153 10.1.1 Definition......................................................................................................................................................153 10.1.2 Service primitives..........................................................................................................................................153 10.1.3 Parameter use................................................................................................................................................154 10.2 MAP_PROVIDE_ROAMING_NUMBER service.........................................................................................158 10.2.1 Definition......................................................................................................................................................158 10.2.2 Service primitives..........................................................................................................................................158 10.2.3 Parameter use................................................................................................................................................159 10.3 MAP_RESUME_CALL_HANDLING service...............................................................................................161 10.3.1 Definition......................................................................................................................................................161 10.3.2 Service primitives..........................................................................................................................................161 10.3.3 Parameter use................................................................................................................................................161 10.4 MAP_PREPARE_GROUP_CALL service.....................................................................................................162 10.4.1 Definition......................................................................................................................................................162 10.4.2 Service primitives..........................................................................................................................................163 10.4.3 Parameter definitions and use.......................................................................................................................163 10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service............................................................................164 10.5.1 Definitions.....................................................................................................................................................164 10.5.2 Service primitives..........................................................................................................................................164 10.5.3 Parameter definitions and use.......................................................................................................................164 10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service.........................................................................164 10.6.1 Definitions.....................................................................................................................................................165 10.6.2 Service primitives..........................................................................................................................................165 10.6.3 Parameter definitions and use.......................................................................................................................165 10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service.................................................................................165 10.7.1 Definitions.....................................................................................................................................................166 10.7.2 Service primitives..........................................................................................................................................166 10.7.3 Parameter definitions and use.......................................................................................................................166 10.8 MAP_Provide_SIWFS_Number......................................................................................................................166 10.8.1 Definition......................................................................................................................................................166 10.8.2 Service primitive...........................................................................................................................................166 10.8.3 Parameter use................................................................................................................................................167 10.9 MAP_SIWFS_Signalling_Modify...................................................................................................................168 10.9.1 Definition......................................................................................................................................................168 10.9.2 Service primitive...........................................................................................................................................168 10.9.3 Parameter use................................................................................................................................................168 10.10 MAP_SET_REPORTING_STATE service...................................................................................................169 10.10.1 Definition....................................................................................................................................................169 10.10.2 Service primitives........................................................................................................................................169 10.10.3 Parameter use..............................................................................................................................................169 10.11 MAP_STATUS_REPORT service................................................................................................................170 10.11.1 Definition....................................................................................................................................................170 10.11.2 Service primitives........................................................................................................................................170 10.11.3 Parameter use..............................................................................................................................................170 10.12 MAP_REMOTE_USER_FREE service........................................................................................................171 10.12.1 Definition....................................................................................................................................................171 10.12.2 Service primitives........................................................................................................................................171 10.12.3 Parameter use..............................................................................................................................................171 10.13 MAP_IST_ALERT service............................................................................................................................172 10.13.1 Definition....................................................................................................................................................172 10.13.2 Service primitives........................................................................................................................................172 10.13.3 Parameter use..............................................................................................................................................172

552 10 Call handling services......................................................................................................................153

46

605 606 607 608 610 611 612 613 614 615 616 617 618 619 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 656 657 658 659 660 661 662 663 664

47 Release 4 48 49

13

3GPP TS 29.002 V4.17.0 (2006-06)

10.14 MAP_IST_COMMAND service...................................................................................................................173 10.14.1 Definition....................................................................................................................................................173 10.14.2 Service primitives........................................................................................................................................173 10.14.3 Parameter use..............................................................................................................................................173 11.1 MAP_REGISTER_SS service.........................................................................................................................173 11.1.1 Definition......................................................................................................................................................173 11.1.2 Service primitives..........................................................................................................................................174 11.1.3 Parameter use................................................................................................................................................174 11.2 MAP_ERASE_SS service................................................................................................................................175 11.2.1 Definition......................................................................................................................................................175 11.2.2 Service primitives..........................................................................................................................................175 11.2.3 Parameter use................................................................................................................................................175 11.3 MAP_ACTIVATE_SS service........................................................................................................................176 11.3.1 Definition......................................................................................................................................................176 11.3.2 Service primitives..........................................................................................................................................176 11.3.3 Parameter use................................................................................................................................................177 11.4 MAP_DEACTIVATE_SS service...................................................................................................................178 11.4.1 Definitions.....................................................................................................................................................178 11.4.2 Service primitives..........................................................................................................................................178 11.4.3 Parameter use................................................................................................................................................178 11.5 MAP_INTERROGATE_SS service................................................................................................................179 11.5.1 Definitions.....................................................................................................................................................179 11.5.2 Service primitives..........................................................................................................................................179 11.5.3 Parameter use................................................................................................................................................180 11.6 MAP_INVOKE_SS service.............................................................................................................................181 11.6.1 Definitions.....................................................................................................................................................181 11.6.2 Service primitives..........................................................................................................................................181 11.6.3 Parameter use................................................................................................................................................182 11.7 MAP_REGISTER_PASSWORD service........................................................................................................182 11.7.1 Definitions.....................................................................................................................................................182 11.7.2 Service primitives..........................................................................................................................................182 11.7.3 Parameter use................................................................................................................................................183 11.8 MAP_GET_PASSWORD service...................................................................................................................183 11.8.1 Definitions.....................................................................................................................................................183 11.8.2 Service primitives..........................................................................................................................................183 11.8.3 Parameter use................................................................................................................................................184 11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service.....................................................................184 11.9.1 Definitions.....................................................................................................................................................184 11.9.2 Service primitives..........................................................................................................................................184 11.9.3 Parameter use................................................................................................................................................184 11.10 MAP_UNSTRUCTURED_SS_REQUEST service......................................................................................185 11.10.1 Definitions...................................................................................................................................................185 11.10.2 Service primitives........................................................................................................................................185 11.10.3 Parameter use..............................................................................................................................................185 11.11 MAP_UNSTRUCTURED_SS_NOTIFY service..........................................................................................186 11.11.1 Definitions...................................................................................................................................................186 11.11.2 Service primitives........................................................................................................................................187 11.11.3 Parameter use..............................................................................................................................................187 11.12 MAP_SS_INVOCATION_NOTIFY.............................................................................................................188 11.12.1 Definition....................................................................................................................................................188 11.12.2 Service primitives........................................................................................................................................188 11.12.3 Parameter use..............................................................................................................................................188 11.13 MAP_REGISTER_CC_ENTRY service.......................................................................................................188 11.13.1 Definition....................................................................................................................................................188 11.13.2 Service primitives........................................................................................................................................189 11.13.3 Parameter use..............................................................................................................................................189 11.14 MAP_ERASE_CC_ENTRY service.............................................................................................................190 11.14.1 Definition....................................................................................................................................................190 11.14.2 Service primitives........................................................................................................................................190

609 11 Supplementary services related services..........................................................................................173

50

665 11.14.3 Parameter use..............................................................................................................................................190

51 Release 4 52 53

14

3GPP TS 29.002 V4.17.0 (2006-06)

666 12 Short message service management services....................................................................................191


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 704 705 706 707 708 709 710 711 712 713 714 715 717 718 719 720 721 722 723

12.1 MAP-SEND-ROUTING-INFO-FOR-SM service...........................................................................................191 12.1.1 Definition......................................................................................................................................................191 12.1.2 Service primitives..........................................................................................................................................191 12.1.3 Parameter use................................................................................................................................................191 12.2 MAP-MO-FORWARD-SHORT-MESSAGE service.....................................................................................193 12.2.1 Definition......................................................................................................................................................193 12.2.2 Service primitives..........................................................................................................................................193 12.2.3 Parameter use................................................................................................................................................193 12.3 MAP-REPORT-SM-DELIVERY-STATUS service.......................................................................................194 12.3.1 Definition......................................................................................................................................................194 12.3.2 Service primitives..........................................................................................................................................194 12.3.3 Parameter use................................................................................................................................................194 12.4 MAP-READY-FOR-SM service.....................................................................................................................195 12.4.1 Definition......................................................................................................................................................195 12.4.2 Service primitives..........................................................................................................................................196 12.4.3 Parameter use................................................................................................................................................196 12.5 MAP-ALERT-SERVICE-CENTRE service....................................................................................................196 12.5.1 Definition......................................................................................................................................................196 12.5.2 Service primitives..........................................................................................................................................197 12.5.3 Parameter use................................................................................................................................................197 12.6 MAP-INFORM-SERVICE-CENTRE service.................................................................................................197 12.6.1 Definition......................................................................................................................................................197 12.6.2 Service primitives..........................................................................................................................................198 12.6.3 Parameter use................................................................................................................................................198 12.7 MAP-SEND-INFO-FOR-MT-SMS service.....................................................................................................198 12.7.1 Definition......................................................................................................................................................198 12.7.2 Service primitives..........................................................................................................................................198 12.7.3 Parameter use................................................................................................................................................198 12.8 MAP-SEND-INFO-FOR-MO-SMS service....................................................................................................199 12.8.1 Definition......................................................................................................................................................199 12.8.2 Service primitives..........................................................................................................................................199 12.8.3 Parameter use................................................................................................................................................199 12.9 MAP-MT-FORWARD-SHORT-MESSAGE service......................................................................................200 12.9.1 Definition......................................................................................................................................................200 12.9.2 Service primitives..........................................................................................................................................200 12.9.3 Parameter use................................................................................................................................................200 13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service...................................................................................201 13.1.1 Definition......................................................................................................................................................201 13.1.2 Service primitives..........................................................................................................................................202 13.1.3 Parameter definition and use.........................................................................................................................202 13.2 MAP_FAILURE_REPORT service.................................................................................................................203 13.2.1 Definition......................................................................................................................................................203 13.2.2 Service primitives..........................................................................................................................................203 13.2.3 Parameter definition and use.........................................................................................................................203 13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service.......................................................................................203 13.3.1 Definition......................................................................................................................................................203 13.3.2 Service primitives..........................................................................................................................................204 13.3.3 Parameter definition and use.........................................................................................................................204 13A.1 MAP-SEND-ROUTING-INFO-FOR-LCS Service......................................................................................204 13A.1.1 Definition...................................................................................................................................................204 13A.1.2 Service Primitives......................................................................................................................................205 13A.1.3 Parameter Use............................................................................................................................................205 13A.2 MAP-PROVIDE-SUBSCRIBER-LOCATION Service...............................................................................206 13A.2.1 Definition...................................................................................................................................................206 13A.2.2 Service Primitives......................................................................................................................................206

703 13 Network-Requested PDP Context Activation services.....................................................................201

716 13A Location Service Management Services........................................................................................204

54

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 754 755 756 757 759 760 761 762 763 764 765 766 767 768 769 770 771 773 774 775 776 777 778 779 780 781 782

55 Release 4 56 57

15

3GPP TS 29.002 V4.17.0 (2006-06)

13A.2.3 Parameter Definition and Use....................................................................................................................206 13A.3 MAP-SUBSCRIBER-LOCATION-REPORT Service.................................................................................208 13A.3.1 Definition...................................................................................................................................................208 13A.3.2 Service Primitives......................................................................................................................................208 13A.3.3 Parameter Definition and Use....................................................................................................................208 13A.4 Void...............................................................................................................................................................210 13A.4.1 Void 210 13A.4.2 Void 210 13A.4.3 Void 210 13A.5 Void...............................................................................................................................................................210 13A.5.1 Void 210 13A.5.2 Void 210 13A.5.3 Void 210 13A.6 Void...............................................................................................................................................................210 13A.6.1 Void 210 13A.6.2 Void 210 13A.6.3 Void 210 13A.7 Void...............................................................................................................................................................211 13A.7.1 Void 211 13A.7.2 Void 211 13A.7.3 Void 211 13A.8 Void...............................................................................................................................................................211 13A.8.1 Void 211 13A.8.2 Void 211 13A.8.3 Void 211 13A.9 Void...............................................................................................................................................................211 13A.9.1 Void 211 13A.9.2 Void 211 13A.9.3 Void 211 14.1 Overview..........................................................................................................................................................211 14.2 Underlying services..........................................................................................................................................211 14.3 Model...............................................................................................................................................................211 14.4 Conventions......................................................................................................................................................212 15.1 Handling of unknown operations.....................................................................................................................212 15.2 Dialogue establishment....................................................................................................................................213 15.2.1 Behaviour at the initiating side.....................................................................................................................213 15.2.2 Behaviour at the responding side..................................................................................................................214 15.3 Dialogue continuation......................................................................................................................................215 15.4 Load control.....................................................................................................................................................215 15.5 Procedures for MAP specific services.............................................................................................................215 15.5.1 Service invocation ........................................................................................................................................215 15.5.2 void 215 15.5.3 Service invocation receipt ............................................................................................................................215 15.5.4 void 216 15.5.5 Handling of components received from TC..................................................................................................216 15.6 SDL descriptions..............................................................................................................................................216 16.1 Dialogue control...............................................................................................................................................249 16.1.1 Directly mapped parameters.........................................................................................................................249 16.1.2 Use of other parameters of dialogue handling primitives.............................................................................249 16.1.2.1 Dialogue Id.................................................................................................................................................249 16.1.2.2 Application-context-name..........................................................................................................................249 16.1.2.3 User information........................................................................................................................................249 16.1.2.4 Component present.....................................................................................................................................249 16.1.2.5 Termination................................................................................................................................................249 16.1.2.6 P-Abort-Cause............................................................................................................................................249 16.1.2.7 Quality of service.......................................................................................................................................249

753 14 General.............................................................................................................................................211

758 15 Elements of procedure......................................................................................................................212

772 16 Mapping on to TC services..............................................................................................................249

58

783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 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

59 Release 4 60 61

16

3GPP TS 29.002 V4.17.0 (2006-06)

16.2 Service specific procedures..............................................................................................................................250 16.2.1 Directly mapped parameters.........................................................................................................................250 16.2.2 Use of other parameters of component handling primitives.........................................................................250 16.2.2.1 Dialogue Id.................................................................................................................................................250 16.2.2.2 Class 250 16.2.2.3 Linked Id....................................................................................................................................................250 16.2.2.4 Operation....................................................................................................................................................251 16.2.2.5 Error 252 16.2.2.6 Parameters..................................................................................................................................................252 16.2.2.7 Time out.....................................................................................................................................................252 16.2.2.8 Last component..........................................................................................................................................252 16.2.2.9 Problem code..............................................................................................................................................252 16.2.2.9.1 Mapping to MAP User Error...................................................................................................................252 16.2.2.9.2 Mapping to MAP Provider Error parameter...........................................................................................252 16.2.2.9.3 Mapping to diagnostic parameter............................................................................................................253 17.1 General.............................................................................................................................................................254 17.1.1 Encoding rules...............................................................................................................................................254 17.1.2 Use of TC......................................................................................................................................................254 17.1.2.1 Use of Global Operation and Error codes defined outside MAP...............................................................255 17.1.3 Use of information elements defined outside MAP......................................................................................255 17.1.4 Compatibility considerations........................................................................................................................256 17.1.5 Structure of the Abstract Syntax of MAP.....................................................................................................256 17.1.6 Application Contexts.....................................................................................................................................258 17.2 Operation packages..........................................................................................................................................259 17.2.1 General aspects..............................................................................................................................................259 17.2.2 Packages specifications.................................................................................................................................260 17.2.2.1 Location updating.......................................................................................................................................260 17.2.2.2 Location cancellation.................................................................................................................................260 17.2.2.3 Roaming number enquiry...........................................................................................................................261 17.2.2.4 Information retrieval..................................................................................................................................261 17.2.2.5 Inter-VLR information retrieval.................................................................................................................261 17.2.2.6 IMSI retrieval.............................................................................................................................................261 17.2.2.7 Call control transfer....................................................................................................................................262 17.2.2.8 void 262 17.2.2.9 Void 262 17.2.2.10 Interrogation.............................................................................................................................................262 17.2.2.11 Void 262 17.2.2.12 Handover Control.....................................................................................................................................262 17.2.2.13 Subscriber Data management stand alone................................................................................................263 17.2.2.14 Equipment management...........................................................................................................................263 17.2.2.15 Subscriber data management....................................................................................................................263 17.2.2.16 Location register restart............................................................................................................................263 17.2.2.17 Tracing stand-alone..................................................................................................................................263 17.2.2.18 Functional SS handling............................................................................................................................264 17.2.2.19 Tracing.....................................................................................................................................................264 17.2.2.20 Binding.....................................................................................................................................................264 17.2.2.21 Unstructured SS handling........................................................................................................................264 17.2.2.22 MO Short message relay services............................................................................................................265 17.2.2.23 Short message gateway services..............................................................................................................265 17.2.2.24 MT Short message relay services.............................................................................................................265 17.2.2.25 Void 266 17.2.2.26 Message waiting data management..........................................................................................................266 17.2.2.27 Alerting....................................................................................................................................................266 17.2.2.28 Data restoration........................................................................................................................................266 17.2.2.29 Purging.....................................................................................................................................................266 17.2.2.30 Subscriber information enquiry................................................................................................................267 17.2.2.31 Any time information enquiry..................................................................................................................267 17.2.2.32 Group Call Control...................................................................................................................................267 17.2.2.33 Provide SIWFS number...........................................................................................................................267

798 17 Abstract syntax of the MAP protocol...............................................................................................254

62

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 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

63 Release 4 64 65

17

3GPP TS 29.002 V4.17.0 (2006-06)

17.2.2.34 SIWFS Signalling Modify........................................................................................................................267 17.2.2.35 Gprs location updating.............................................................................................................................268 17.2.2.36 Gprs Interrogation....................................................................................................................................268 17.2.2.37 Failure reporting.......................................................................................................................................268 17.2.2.38 GPRS notifying........................................................................................................................................268 17.2.2.39 Supplementary Service invocation notification.......................................................................................269 17.2.2.40 Set Reporting State...................................................................................................................................269 17.2.2.41 Status Report............................................................................................................................................269 17.2.2.42 Remote User Free.....................................................................................................................................269 17.2.2.43 Call Completion.......................................................................................................................................269 17.2.2.44 Location service gateway services...........................................................................................................269 17.2.2.45 Location service enquiry..........................................................................................................................270 17.2.2.45A Location service reporting.....................................................................................................................270 17.2.2.46 Void 270 17.2.2.47 Void 270 17.2.2.48 Void 270 17.2.2.49 IST Alerting.............................................................................................................................................270 17.2.2.50 Service Termination.................................................................................................................................270 17.2.2.51 Mobility Management event notification.................................................................................................271 17.2.2.53 Subscriber Data modification notification...............................................................................................271 17.2.2.54 Authentication Failure Report..................................................................................................................271 17.3 Application contexts.........................................................................................................................................271 17.3.1 General aspects..............................................................................................................................................271 17.3.2 Application context definitions.....................................................................................................................272 17.3.2.1 Void 272 17.3.2.2 Location Updating......................................................................................................................................272 17.3.2.3 Location Cancellation................................................................................................................................273 17.3.2.4 Roaming number enquiry...........................................................................................................................273 17.3.2.5 Void 273 17.3.2.6 Location Information Retrieval..................................................................................................................273 17.3.2.7 Call control transfer....................................................................................................................................274 17.3.2.8 void 274 17.3.2.9 - 17.3.2.10 Void.........................................................................................................................................274 17.3.2.11 Location registers restart..........................................................................................................................274 17.3.2.12 Handover control......................................................................................................................................274 17.3.2.13 IMSI Retrieval..........................................................................................................................................274 17.3.2.14 Equipment Management..........................................................................................................................275 17.3.2.15 Information retrieval................................................................................................................................275 17.3.2.16 Inter-VLR information retrieval...............................................................................................................275 17.3.2.17 Stand Alone Subscriber Data Management.............................................................................................276 17.3.2.18 Tracing.....................................................................................................................................................276 17.3.2.19 Network functional SS handling..............................................................................................................276 17.3.2.20 Network unstructured SS handling..........................................................................................................277 17.3.2.21 Short Message Gateway...........................................................................................................................277 17.3.2.22 Mobile originating Short Message Relay.................................................................................................277 17.3.2.23 Void 278 17.3.2.24 Short message alert..................................................................................................................................278 17.3.2.25 Short message waiting data management................................................................................................278 17.3.2.26 Mobile terminating Short Message Relay................................................................................................278 17.3.2.27 MS purging...............................................................................................................................................279 17.3.2.28 Subscriber information enquiry................................................................................................................279 17.3.2.29 Any time information enquiry..................................................................................................................279 17.3.2.30 Group Call Control...................................................................................................................................279 17.3.2.31 Provide SIWFS Number..........................................................................................................................279 17.3.2.32 Gprs Location Updating...........................................................................................................................280 17.3.2.33 Gprs Location Information Retreival.......................................................................................................280 17.3.2.34 Failure Reporting.....................................................................................................................................280 17.3.2.35 GPRS Notifying.......................................................................................................................................280 17.3.2.36 Supplementary Service invocation notification.......................................................................................280 17.3.2.37 Reporting..................................................................................................................................................281 17.3.2.38 Call Completion.......................................................................................................................................281

66

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 943 944 945 946 947 948 949 950 951 952 953 954 955 957 958 959 960 961 962 963

67 Release 4 68 69

18

3GPP TS 29.002 V4.17.0 (2006-06)

17.3.2.39 Location Service Gateway.......................................................................................................................282 17.3.2.40 Location Service Enquiry.........................................................................................................................282 17.3.2.41 Void 282 17.3.2.42 Void 282 17.3.2.43 Void 282 17.3.2.44 IST Alerting.............................................................................................................................................282 17.3.2.45 Service Termination.................................................................................................................................282 17.3.2.46 Mobility Management event notification.................................................................................................283 17.3.2.48 Subscriber Data modification notification...............................................................................................283 17.3.2.49 Authentication Failure Report..................................................................................................................283 17.3.3 ASN.1 Module for application-context-names.............................................................................................283 17.4 MAP Dialogue Information.............................................................................................................................286 17.5 MAP operation and error codes.......................................................................................................................288 17.6 MAP operation and error types........................................................................................................................294 17.6.1 Mobile Service Operations............................................................................................................................294 17.6.2 Operation and Maintenance Operations........................................................................................................300 17.6.3 Call Handling Operations..............................................................................................................................302 17.6.4 Supplementary service operations.................................................................................................................304 17.6.5 Short message service operations..................................................................................................................308 17.6.6 Errors 310 17.6.7 Group Call operations...................................................................................................................................316 17.6.8 Location service operations...........................................................................................................................317 17.6.9 void 319 17.7 MAP constants and data types.........................................................................................................................319 17.7.1 Mobile Service data types.............................................................................................................................319 17.7.2 Operation and maintenance data types..........................................................................................................346 17.7.3 Call handling data types................................................................................................................................347 17.7.4 Supplementary service data types.................................................................................................................353 17.7.5 Supplementary service codes........................................................................................................................357 17.7.6 Short message data types..............................................................................................................................360 17.7.7 Error data types.............................................................................................................................................363 17.7.8 Common data types.......................................................................................................................................368 17.7.9 Teleservice Codes.........................................................................................................................................375 17.7.10 Bearer Service Codes..................................................................................................................................376 17.7.11 Extension data types....................................................................................................................................378 17.7.12 Group Call data types..................................................................................................................................379 17.7.13 Location service data types.........................................................................................................................381 17.7.14 void 388 18.1 Introduction......................................................................................................................................................388 18.2 Common aspects of user procedure descriptions.............................................................................................388 18.2.1 General conventions......................................................................................................................................388 18.2.2 Naming conventions......................................................................................................................................388 18.2.3 Convention on primitives parameters...........................................................................................................389 18.2.3.1 Open service...............................................................................................................................................389 18.2.3.2 Close service..............................................................................................................................................390 18.2.4 Version handling at dialogue establishment.................................................................................................390 18.2.4.1 Behaviour at the initiating side..................................................................................................................390 18.2.4.2 Behaviour at the responding side...............................................................................................................390 18.2.5 Abort Handling..............................................................................................................................................390 18.2.6 SDL conventions...........................................................................................................................................390 18.3 Interaction between MAP Provider and MAP Users.......................................................................................391 19.1 Location management Procedures...................................................................................................................391 19.1.1 Location updating..........................................................................................................................................394 19.1.1.1 General 394 19.1.1.3 Detailed procedure in the VLR..................................................................................................................399 19.1.1.4 Detailed procedure in the HLR..................................................................................................................408 19.1.1.5 Send Identification.....................................................................................................................................415 19.1.1.5.1 General 415

942 18 General on MAP user procedures.....................................................................................................388

956 19 Mobility procedures.........................................................................................................................391

70

964 965 966 967 968 969 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 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023

71 Release 4 72 73

19

3GPP TS 29.002 V4.17.0 (2006-06)

19.1.1.5.2 Detailed procedure in the VLR...............................................................................................................415 19.1.1.5.3 Detailed procedure in the PVLR.............................................................................................................415 19.1.1.6 Process Update Location VLR...................................................................................................................420 19.1.1.8 Detailed procedure in the SGSN................................................................................................................422 19.1.2 Location Cancellation...................................................................................................................................425 19.1.2.1 General 425 19.1.2.2 Detailed procedure in the HLR..................................................................................................................425 19.1.2.3 Detailed procedure in the VLR..................................................................................................................425 19.1.2.4 Detailed procedure in the SGSN................................................................................................................428 19.1.3 Void 431 19.1.3.1 Void 432 19.1.3.2 Void 432 19.1.3.3 Void 432 19.1.4 Purge MS.......................................................................................................................................................432 19.1.4.1 General 432 19.1.4.2 Void 432 19.1.4.3 Void 432 19.1.4.4 Detailed procedure in the SGSN................................................................................................................432 19.2 Handover procedure.........................................................................................................................................437 19.2.1 General..........................................................................................................................................................438 19.2.2 Handover procedure in MSC-A....................................................................................................................441 19.2.2.1 Basic handover...........................................................................................................................................441 19.2.2.2 Handling of access signalling.....................................................................................................................441 19.2.2.3 Other procedures in stable handover situation...........................................................................................442 19.2.2.4 Subsequent handover.................................................................................................................................442 19.2.2.5 SDL Diagrams............................................................................................................................................442 19.2.3 Handover procedure in MSC-B....................................................................................................................455 19.2.3.1 Basic handover...........................................................................................................................................456 19.2.3.2 Allocation of handover number.................................................................................................................456 19.2.3.3 Handling of access signalling.....................................................................................................................456 19.2.3.4 Other procedures in stable handover situation...........................................................................................456 19.2.3.5 Subsequent handover.................................................................................................................................456 19.2.3.6 SDL Diagrams............................................................................................................................................456 19.2.4 Handover error handling macro....................................................................................................................468 19.2.5 Handover procedure in VLR.........................................................................................................................470 19.2.5.1 Allocation of handover number.................................................................................................................470 19.2.5.2 SDL Diagrams............................................................................................................................................470 19.3 Fault recovery procedures................................................................................................................................473 19.3.1 VLR fault recovery procedures.....................................................................................................................473 19.3.2 HLR fault recovery procedures.....................................................................................................................475 19.3.3 VLR restoration: the restore data procedure in the HLR..............................................................................483 19.4 Macro Insert_Subs_Data_Framed_HLR..........................................................................................................485 19.5 Mobility Management Event notification procedure.......................................................................................488 19.5.1 General..........................................................................................................................................................488 19.5.2 Process in the VLR........................................................................................................................................488 19.5.3 Process in the gsmSCF..................................................................................................................................490 20.1 General.............................................................................................................................................................492 20.1.1 Tracing Co-ordinator for the VLR................................................................................................................492 20.1.2 Subscriber Data Management Co-ordinator for the VLR.............................................................................494 20.1.3 Tracing Co-ordinator for the SGSN..............................................................................................................496 20.1.4 Subscriber Data Management Co-ordinator for the SGSN...........................................................................498 20.2 Tracing procedures...........................................................................................................................................500 20.2.1 Procedures in the HLR..................................................................................................................................502 20.2.1.1 Subscriber tracing activation procedure.....................................................................................................502 20.2.1.2 Subscriber tracing deactivation procedure.................................................................................................507 20.2.2 Procedures in the VLR..................................................................................................................................512 20.2.2.1 Subscriber tracing activation procedure.....................................................................................................512 20.2.2.2 Subscriber tracing deactivation procedure.................................................................................................514 20.2.2.3 Subscriber tracing procedure......................................................................................................................516

1010 20 Operation and maintenance procedures............................................................................................492

74

1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 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

75 Release 4 76 77

20

3GPP TS 29.002 V4.17.0 (2006-06)

20.2.3 Procedures in the MSC..................................................................................................................................516 20.2.3.1 Subscriber tracing procedure......................................................................................................................516 20.2.4 Procedures in the SGSN................................................................................................................................516 20.2.4.1 Subscriber tracing activation procedure.....................................................................................................516 20.2.4.2 Subscriber tracing deactivation procedure in SGSN..................................................................................516 20.3 Subscriber data management procedures.........................................................................................................519 20.3.1 Procedures in the HLR..................................................................................................................................520 20.3.1.1 Subscriber deletion procedure....................................................................................................................520 20.3.1.2 Subscriber data modification procedure.....................................................................................................522 20.3.2 Procedures in the VLR..................................................................................................................................527 20.3.2.1 Subscriber deletion procedure....................................................................................................................527 20.3.2.2 Subscriber data modification procedure.....................................................................................................527 20.3.3 Procedures in the SGSN................................................................................................................................530 20.3.3.1 Subscriber deletion procedure....................................................................................................................530 20.3.3.2 Subscriber data modification procedure.....................................................................................................530 20.4 Subscriber Identity procedure..........................................................................................................................533 20.4.1 Subscriber identity procedure in the HLR....................................................................................................533 20.4.2 Subscriber identity procedure in the VLR....................................................................................................535 21.1 General.............................................................................................................................................................537 21.2 Retrieval of routing information......................................................................................................................537 21.2.1 General..........................................................................................................................................................537 21.2.2 Process in the GMSC....................................................................................................................................539 21.2.3 Procedures in the HLR..................................................................................................................................543 21.2.4 Process in the VLR to provide a roaming number........................................................................................549 21.2.5 Process in the VLR to restore subscriber data..............................................................................................551 21.2.6 Process in the VLR to provide subscriber information.................................................................................553 21.2.7 Process in the HLR for Any Time Interrogation...........................................................................................555 21.2.7.1 Process in the gsmSCF...............................................................................................................................555 21.2.7.2 Process in the HLR.....................................................................................................................................555 21.2.8 Process in the GMLC for Any Time Interrogation.......................................................................................559 21.2.8.1 Process in the gsmSCF...............................................................................................................................559 21.2.8.2 Process in the GMLC.................................................................................................................................559 21.3 Transfer of call handling..................................................................................................................................562 21.3.1 General..........................................................................................................................................................562 21.3.2 Process in the VMSC....................................................................................................................................562 21.3.3 Process in the GMSC....................................................................................................................................565 21.4 Inter MSC Group Call Procedures...................................................................................................................567 21.4.1 General..........................................................................................................................................................567 21.4.2 Process in the Anchor MSC..........................................................................................................................567 21.4.3 Process in the Relay MSC.............................................................................................................................573 21.5 Allocation and modifications of resources in an SIWFS.................................................................................578 21.5.1 General..........................................................................................................................................................578 21.5.2 Process in the VMSC....................................................................................................................................581 21.5.2.1 Allocation of SIWFS resources..................................................................................................................581 21.5.2.2 Modification of SIWFS resources initiated by the user.............................................................................582 21.5.2.3 Modification of SIWFS resources initiated by the SIWFS........................................................................582 21.5.3 Process in the SIWFS....................................................................................................................................590 21.5.3.1 Procedures for allocation of SIWFS resources..........................................................................................590 21.5.3.2 Process for modification of SIWFS resources initiated by the user...........................................................591 21.5.3.3 Process for modification of SIWFS resources initiated by the SIWFS.....................................................591 21.6 Setting of Reporting State................................................................................................................................597 21.6.1 General..........................................................................................................................................................597 21.6.2 Process in the HLR for Set Reporting State stand-alone..............................................................................597 21.6.3 Reporting co-ordinator process in the VLR..................................................................................................600 21.6.4 Process in the VLR to set the reporting state................................................................................................602 21.7 Status Reporting...............................................................................................................................................605 21.7.1 General..........................................................................................................................................................605 21.7.2 Process in the VLR for Status Reporting......................................................................................................605 21.7.3 Process in the HLR for Status Reporting......................................................................................................609

1042 21 Call handling procedures..................................................................................................................537

78

1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 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 1138 1139 1140 1141 1142 1143

79 Release 4 80 81

21

3GPP TS 29.002 V4.17.0 (2006-06)

21.8 Remote User Free.............................................................................................................................................614 21.8.1 General..........................................................................................................................................................614 21.8.2 Process in the HLR for Remote User Free....................................................................................................614 21.8.3 Process in the VLR for Remote User Free....................................................................................................617 21.9 IST Alert...........................................................................................................................................................620 21.9.1 General..........................................................................................................................................................620 21.9.2 Procedure in the MSC...................................................................................................................................620 21.9.3 Procedure in the HLR....................................................................................................................................622 21.10 IST Command................................................................................................................................................624 21.10.1 General........................................................................................................................................................624 21.10.2 Procedure in the HLR..................................................................................................................................624 21.10.3 Procedure in the MSC.................................................................................................................................626 22.1 Functional supplementary service processes...................................................................................................628 22.1.1 Functional supplementary service process co-ordinator for MSC................................................................628 22.1.2 Functional supplementary service process co-ordinator for VLR................................................................630 22.1.3 Functional supplementary service process co-ordinator for HLR................................................................632 22.1.4 Call completion supplementary service process co-ordinator for HLR........................................................634 22.2 Registration procedure.....................................................................................................................................636 22.2.1 General..........................................................................................................................................................636 22.2.2 Procedures in the MSC..................................................................................................................................636 22.2.3 Procedures in the VLR..................................................................................................................................639 22.2.4 Procedures in the HLR..................................................................................................................................641 22.3 Erasure procedure.............................................................................................................................................644 22.3.1 General..........................................................................................................................................................644 22.3.2 Procedures in the MSC..................................................................................................................................644 22.3.3 Procedures in the VLR..................................................................................................................................645 22.3.4 Procedures in the HLR..................................................................................................................................645 22.4 Activation procedure........................................................................................................................................645 22.4.1 General..........................................................................................................................................................645 22.4.2 Procedures in the MSC..................................................................................................................................646 22.4.3 Procedures in the VLR..................................................................................................................................648 22.4.4 Procedures in the HLR..................................................................................................................................651 22.5 Deactivation procedure....................................................................................................................................653 22.5.1 General..........................................................................................................................................................653 22.5.2 Procedures in the MSC..................................................................................................................................654 22.5.3 Procedures in the VLR..................................................................................................................................654 22.5.4 Procedures in the HLR..................................................................................................................................654 22.6 Interrogation procedure....................................................................................................................................654 22.6.1 General..........................................................................................................................................................654 22.6.2 Procedures in the MSC..................................................................................................................................655 22.6.3 Procedures in the VLR..................................................................................................................................655 22.6.4 Procedures in the HLR..................................................................................................................................660 22.7 Invocation procedure........................................................................................................................................662 22.7.1 General..........................................................................................................................................................662 22.7.2 Procedures in the MSC..................................................................................................................................662 22.7.3 Procedures in the VLR..................................................................................................................................666 22.8 Password registration procedure......................................................................................................................668 22.8.1 General..........................................................................................................................................................668 22.8.2 Procedures in the MSC..................................................................................................................................669 22.8.3 Procedures in the VLR..................................................................................................................................669 22.8.4 Procedures in the HLR..................................................................................................................................669 22.9 Mobile Initiated USSD procedure....................................................................................................................672 22.9.1 General..........................................................................................................................................................672 22.9.2 Procedures in the MSC..................................................................................................................................672 22.9.3 Procedures in the VLR..................................................................................................................................676 22.9.4 Procedures in the HLR..................................................................................................................................681 22.9.5 Procedures in the gsmSCF/secondary HLR..................................................................................................685 22.10 Network initiated USSD procedure...............................................................................................................688 22.10.1 General........................................................................................................................................................688

1096 22 Supplementary services procedures..................................................................................................628

82

1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 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 1195 1196 1197 1198 1199 1200 1201

83 Release 4 84 85

22

3GPP TS 29.002 V4.17.0 (2006-06)

22.10.2 Procedure in the MSC.................................................................................................................................688 22.10.3 Procedure in the VLR..................................................................................................................................693 22.10.4 Procedure in the HLR..................................................................................................................................700 22.10.5 Procedure in the gsmSCF and secondary HLR...........................................................................................706 22.11 Common macros for clause 22.......................................................................................................................710 22.11.1 SS Password handling macros....................................................................................................................710 22.11.2 SS Error handling macros...........................................................................................................................713 22.12 Supplementary Service Invocation Notification procedure...........................................................................719 22.12.1 General........................................................................................................................................................719 22.12.2 Procedures in the MSC................................................................................................................................719 22.12.3 Procedures in the gsmSCF..........................................................................................................................721 22.13 Activation of a CCBS request........................................................................................................................723 22.13.1 General........................................................................................................................................................723 22.13.2 Procedure in the VLR..................................................................................................................................723 22.13.3 Procedure in the HLR..................................................................................................................................725 22.14 Deactivation of a CCBS request....................................................................................................................727 22.14.1 General........................................................................................................................................................727 22.14.2 Procedure in the VLR..................................................................................................................................727 22.14.3 Procedure in the HLR..................................................................................................................................729 23.1 General.............................................................................................................................................................731 23.1.1 Mobile originated short message service Co-ordinator for the MSC...........................................................731 23.1.2 Short message Gateway Co-ordinator for the HLR......................................................................................733 23.1.3 Mobile originated short message service Co-ordinator for the SGSN..........................................................735 23.2 The mobile originated short message transfer procedure................................................................................737 23.2.1 Procedure in the servicing MSC...................................................................................................................737 23.2.2 Procedure in the VLR....................................................................................................................................744 23.2.3 Procedure in the interworking MSC.............................................................................................................747 23.2.4 Procedure in the SGSN.................................................................................................................................749 23.3 The mobile terminated short message transfer procedure................................................................................754 23.3.1 Procedure in the Servicing MSC...................................................................................................................756 23.3.2 Procedures in the VLR..................................................................................................................................765 23.3.3 Procedures in the HLR..................................................................................................................................769 23.3.4 Procedures in the gateway MSC...................................................................................................................778 23.3.5 Procedure in the Servicing SGSN.................................................................................................................788 23.4 The Short Message Alert procedure.................................................................................................................796 23.4.1 Procedures in the Servicing MSC.................................................................................................................798 23.4.2 Procedures in the VLR..................................................................................................................................800 23.4.2.1 The Mobile Subscriber is present...............................................................................................................800 23.4.2.2 The Mobile Equipment has memory available..........................................................................................800 23.4.3 Procedures in the HLR..................................................................................................................................802 23.4.4 Procedures in the Interworking MSC............................................................................................................805 23.4.5 Procedures in the Servicing SGSN...............................................................................................................807 23.4.5.1 The Mobile Subscriber is present...............................................................................................................807 23.4.5.2 The Mobile Equipment has memory available..........................................................................................807 23.5 The SM delivery status report procedure.........................................................................................................809 23.5.1 Procedures in the HLR..................................................................................................................................809 23.5.2 Procedures in the gateway MSC...................................................................................................................811 23.6 Common procedures for the short message clause..........................................................................................813 23.6.1 The macro Report_SM_Delivery_Stat_HLR................................................................................................813 24.1 General.............................................................................................................................................................815 24.1.1 Process in the HLR for Send Routing Information for GPRS......................................................................815 24.1.2 Process in the GGSN for Send Routing Information for GPRS...................................................................817 24.2.1 Process in the HLR for Failure Report..........................................................................................................819 24.2.2 Process in the GGSN for Failure Report.......................................................................................................821 24.3.1 Process in the GGSN for Note Ms Present For Gprs....................................................................................823 24.3.2 Process in the HLR for Note Ms Present For Gprs.......................................................................................825

1163 23 Short message service procedures....................................................................................................731

1194 24 GPRS process description................................................................................................................815

86

1202 24A CSE control of subscriber data......................................................................................................827


1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261

87 Release 4 88 89

23

3GPP TS 29.002 V4.17.0 (2006-06)

24A.1 Any Time Subscription Interrogation procedure..........................................................................................827 24A.1.1 General.......................................................................................................................................................827 24A.1.2 Process in the gsmSCF...............................................................................................................................827 24A.1.3 Process in the HLR.....................................................................................................................................827 24A.2 Any Time Modification procedure................................................................................................................830 24A.2.1 General.......................................................................................................................................................830 24A.2.2 Process in the gsmSCF...............................................................................................................................830 24A.2.3 Process in the HLR.....................................................................................................................................830 24A.3 Subscriber Data Modification Notification procedure..................................................................................833 24A.3.1 General.......................................................................................................................................................833 24A.3.2 Processes in the MAP Entities...................................................................................................................833 24A.3.2.1 Process in the HLR..................................................................................................................................833 24A.3.2.2 Process in the gsmSCF............................................................................................................................836 24B.1 Routeing information retrieval procedure for LCS.......................................................................................837 24B.1.1 General.......................................................................................................................................................838 24B.1.2 Process in the GMLC.................................................................................................................................839 24B.1.3 Process in the HLR.....................................................................................................................................840 24B.2 Provide Subscriber Location procedure........................................................................................................841 24B.2.1 General.......................................................................................................................................................841 24B.2.2 Process in the GMLC.................................................................................................................................842 24B.2.3 Process in the MSC....................................................................................................................................843 24B.2.4 Process in the SGSN...................................................................................................................................843 24B.3 Subscriber Location Report procedure..........................................................................................................845 24B.3.1 General.......................................................................................................................................................845 24B.3.2 Process in the GMLC.................................................................................................................................846 24B.3.3 Process in the MSC....................................................................................................................................847 24B.3.4 Process in the SGSN...................................................................................................................................848 25.1 MAP open macros............................................................................................................................................849 25.1.1 Macro Receive_Open_Ind............................................................................................................................849 25.1.2 Macro Receive_Open_Cnf............................................................................................................................849 25.2 Macros to check the content of indication and confirmation primitives..........................................................854 25.2.1 Macro Check_Indication...............................................................................................................................854 25.2.2 Macro Check_Confirmation..........................................................................................................................854 25.3 The page and search macros............................................................................................................................857 25.3.1 Macro PAGE_MSC......................................................................................................................................857 25.3.2 Macro Search_For_MS_MSC.......................................................................................................................858 25.4 Macros for handling an Access Request..........................................................................................................861 25.4.1 Macro Process_Access_Request_MSC........................................................................................................861 25.4.2 Macro Process_Access_Request_VLR.........................................................................................................866 25.4.3 Macro Identification Procedure.....................................................................................................................868 25.5 Authentication macros and processes..............................................................................................................873 25.5.1 Macro Authenticate_MSC............................................................................................................................873 25.5.2 Macro Authenticate_VLR.............................................................................................................................873 25.5.3 Process Obtain_Authentication_Sets_VLR..................................................................................................873 25.5.4 Macro Obtain_Authent_Para_VLR..............................................................................................................873 25.5.5 Process Obtain_Auth_Sets_HLR..................................................................................................................874 25.5.6 Process Obtain_Authent_Para_SGSN..........................................................................................................884 25.5.7 Process Authentication_Failure_Report........................................................................................................889 25.5.7.1 General 889 25.5.7.2 Process in the VLR.....................................................................................................................................889 25.5.7.3 Process in the SGSN..................................................................................................................................891 25.5.7.4 Process in the HLR.....................................................................................................................................892 25.6 IMEI Handling Macros....................................................................................................................................893 25.6.1 Macro Check_IMEI_MSC............................................................................................................................893 25.6.2 Macro Check_IMEI_VLR............................................................................................................................893 25.6.3 Process Check_IMEI_EIR............................................................................................................................894 25.6.4 Macro Obtain_IMEI_MSC...........................................................................................................................894

1216 24B Location Service process description.............................................................................................837

1231 25 General macro description................................................................................................................849

90

1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284

91 Release 4 92 93

24

3GPP TS 29.002 V4.17.0 (2006-06)

25.6.5 Macro Obtain_IMEI_VLR............................................................................................................................894 25.6.6 Process Check_IMEI_SGSN........................................................................................................................901 25.7 Insert Subscriber Data Macros.........................................................................................................................904 25.7.1 Macro Insert_Subs_Data_VLR.....................................................................................................................904 25.7.2 Process Insert_Subs_Data_Stand_Alone_HLR............................................................................................906 25.7.3 Macro Wait_for_Insert_Subs_Data_Cnf......................................................................................................912 25.7.4 Process Send_Insert_Subs_Data...................................................................................................................914 25.7.5 Macro Insert_Subs_Data_SGSN...................................................................................................................914 25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf..........................................................................................916 25.8 Request IMSI Macros......................................................................................................................................918 25.8.1 Macro Obtain_IMSI_MSC............................................................................................................................918 25.8.2 Macro Obtain_IMSI_VLR............................................................................................................................918 25.9 Tracing macros.................................................................................................................................................920 25.9.1 Macro Trace_Subscriber_Activity_MSC......................................................................................................920 25.9.2 Macro Trace_Subscriber_Activity_VLR......................................................................................................920 25.9.3 Macro Activate_Tracing_VLR.....................................................................................................................921 25.9.4 Macro Control_Tracing_HLR.......................................................................................................................923 25.9.5 Macro Trace_Subscriber_Activity_SGSN....................................................................................................926 25.9.6 Macro Activate_Tracing_SGSN...................................................................................................................926 25.10 Short Message Alert procedures....................................................................................................................928 25.10.1 Subscriber_Present_VLR process...............................................................................................................928 25.10.2 Macro Alert_Service_Centre_HLR............................................................................................................930 25.10.3 The Mobile Subscriber is present................................................................................................................932

1285 Annex A (informative): 1286 1287 Annex B (informative): 1288

Cross-reference for abstract syntaxes of MAP.................................934 Fully expanded ASN.1 sources for abstract syntaxes of MAP.......1155

1289 B.1 Fully Expanded ASN.1 Source of MAP-Protocol/TCAPMessages..............................................1155 1290 B.2 Fully Expanded ASN.1 Source of MAP-DialogueInformation.....................................................1258 1291 Annex C : 1292 1293 Annex D (informative): 1294 1296 Annex E (informative): 1297 1298
Void....................................................................................................1262 Clause mapping table........................................................................1263

1295 D.1 Mapping of Clause numbers.........................................................................................................1263


Change History..................................................................................1264

94

95 Release 4 96 97

25

3GPP TS 29.002 V4.17.0 (2006-06)

1299

Foreword

1300 This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). 1301 The present document specifies the Mobile Application Part (MAP), the requirements for the signalling system and 1302 procedures within the 3GPP system at application level. 1303 The contents of the present document are subject to continuing work within the TSG and may change following formal 1304 TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an 1305 identifying change of release date and an increase in version number as follows: 1306 1307 1308 1309 1310 1311 1312 1313 1314

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.

98

99 Release 4 100 101

26

3GPP TS 29.002 V4.17.0 (2006-06)

1330

1 Scope

1331 It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN 1332 in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified 1333 by CCITT is used to transfer this information. 1334 The present document describes the requirements for the signalling system and the procedures needed at the application 1335 level in order to fulfil these signalling needs. 1336 Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols 1337 required by MAP. 1338 MAP consists of a set of MAP services that 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

1339
1340

Figure 1.1/1: Modelling principles

1341 Clauses 7 to 13A of the present document describe the MAP services. 1342 Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be 1343 used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.). 1344 Clauses 18 to 25 describe the MAP user procedures that make use of MAP services.

1345

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] [6] [7] 3GPP TS 21.905: "3G Vocabulary". 3GPP TS 22.001: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a Public Land Mobile Network (PLMN)". 3GPP TS 22.002: "Bearer Services Supported by a Public Land Mobile Network (PLMN)". 3GPP TS 22.003: "Circuit Teleservices Supported by a Public Land Mobile Network (PLMN)". 3GPP TS 22.004: "General on Supplementary Services". 3GPP TS 42.009: "Digital cellular telecommunications system (Phase 2+); Security aspects". 3GPP TS 22.016: "International Mobile station Equipment Identities (IMEI)".

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

1348
1349

1350 1351
1352 1353 1354 1355 1356 1357 1358 1359 1360 1361

102

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 1391 1392 1393 1394 1395 1396 1397

103 Release 4 104 105

27

3GPP TS 29.002 V4.17.0 (2006-06)

[8] [9]

3GPP TS 22.041: "Operator Determined Barring". 3GPP TS 22.081: "Line identification supplementary services - Stage 1". 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". 3GPP TS 22.084: "Multi Party (MPTY) Supplementary Services - Stage 1". 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". 3GPP TS 22.086: "Advice of charge (AoC) Supplementary Services - Stage 1". 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1". 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD); - Stage 1". 3GPP TS 23.003: "Numbering, addressing and identification". GSM 03.04: "Digital cellular telecommunications system (Phase 2+); Signalling requirements relating to routeing of calls to mobile subscribers". 3GPP TS 23.007: "Restoration procedures". 3GPP TS 23.008: "Organisation of subscriber data". 3GPP TS 23.009: "Handover procedures". 3GPP TS 23.011: "Technical realization of Supplementary Services - General Aspects". 3GPP TS 23.012: "Location registration procedures". 3GPP TS 43.020: "Security related network functions". 3GPP TS 23.038: "Alphabets and language". 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". 3GPP TS 23.271: "Functional stage2 description of LCS (Release 4)". 3GPP TS 23.081: "Line Identification Supplementary Services - Stage 2". 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services - Stage 2". 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 2". 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Services - Stage 2". 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Services - Stage 2". 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Services - Stage 2". 3GPP TS 23.088: "Call Barring (CB) Supplementary Services - Stage 2". 3GPP TS 23.090: "Unstructured Supplementary Services Data (USSD) - Stage 2". 3GPP TS 33.200: "3G Security; Network domain security; MAP application layer security". 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary Services specification - General aspects". 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".

[10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [26a] [27] [28] [29] [30] [31] [32] [33] [34] [34a] [35] [36] [37]

106

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 1433 1434 1435 1436 1437 1438 1439

107 Release 4 108 109

28

3GPP TS 29.002 V4.17.0 (2006-06)

[37a] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49]

3GPP TS 44.071: "Location Services (LCS) stage 3". 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification - Formats and coding". 3GPP TS 24.081: "Line identification supplementary services - Stage 3". 3GPP TS 24.082: "Call Forwarding (CF) Supplementary Services - Stage 3". 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". 3GPP TS 24.084: "Multi Party (MPTY) Supplementary Services - Stage 3". 3GPP TS 24.085: "Closed User Group (CUG) Supplementary Services - Stage 3". 3GPP TS 24.086: "Advice of Charge (AoC) Supplementary Services - Stage 3". 3GPP TS 24.088: "Call Barring (CB) Supplementary Services - Stage 3". 3GPP TS 24.090: "Unstructured Supplementary Services Data - Stage 3". 3GPP TS 48.002: " Base Station System - Mobile-services Switching Centre (BSS - MSC) interface principles". 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System Mobile-services Switching Centre (BSS - MSC) interface". 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". 3GPP TS 48.031: "Location Services (LCS); Serving Mobile Location Centre (SMLC) Serving Mobile Location Centre (SMLC); SMLC Peer Protocol (SMLCPP)". 3GPP TS 48.071: "Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC - BSS) interface Layer 3 specification". 3GPP TS 49.001: "General network interworking scenarios". 3GPP TS 29.002: "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". 3GPP TS 29.006: "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". 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". 3GPP TS 29.008: "Application of the Base Station System Application Part (BSSAP) on the Einterface". 3GPP TS 29.010: "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)".

[49a1] [49b] [50] [51] [52]

[53] [54]

[55]

[56]

[57] [58]

110

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 1474 1475 1476 1477 1478 1479 1480 1481 1482

111 Release 4 112 113

29

3GPP TS 29.002 V4.17.0 (2006-06)

[59]

3GPP TS 29.011: "Signalling interworking for Supplementary Services". 3GPP TS 49.031: "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". 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". ITU-T Recommendation E.164: "Numbering plan for the ISDN era". ITU-T Recommendation E.212: "Identification plan for land mobile stations". ITU-T Recommendation E.213: "Telephone and ISDN numbering plan for land mobile stations". ITU-T Recommendation E.214: "Structuring of the land mobile global title for the signalling connection control part". CCITT Recommendation Q.699: "Interworking between the Digital Subscriber Signalling System Layer 3 protocol and the Signalling System No.7 ISDN User part". ITU-T Recommendation Q.711: "Specifications of Signalling System No.7; Functional description of the Signalling Connection Control Part". ITU-T Recommendation Q.712: "Definition and function of SCCP messages". ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; SCCP formats and codes". ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling Connection Control Part procedures". ITU-T Recommendation Q.716: "Specifications of Signalling System No.7; Signalling connection control part (SCCP) performances". ITU-T Recommendation Q.721 (1988): "Specifications of Signalling System No.7; Functional description of the Signalling System No.7 Telephone user part". ITU-T Recommendation Q.722 (1988): "Specifications of Signalling System No.7; General function of Telephone messages and signals". ITU-T Recommendation Q.723 (1988): "Specifications of Signalling System No.7; Formats and codes". ITU-T Recommendation Q.724 (1988): "Specifications of Signalling System No.7; Signalling procedures". ITU-T Recommendation Q.725 (1988): "Specifications of Signalling System No.7; Signalling performance in the telephone application".

[59a] [60] [61] [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81]

114

1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524

115 Release 4 116 117

30

3GPP TS 29.002 V4.17.0 (2006-06)

[82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95] [97] [98] [99]

ITU-T Recommendation Q.761 (1988): "Specifications of Signalling System No.7; Functional description of the ISDN user part of Signalling System No.7". ITU-T Recommendation Q.762 (1988): "Specifications of Signalling System No.7; General function of messages and signals". ITU-T Recommendation Q.763 (1988): "Specifications of Signalling System No.7; Formats and codes". ITU-T Recommendation Q.764 (1988): "Specifications of Signalling System No.7; Signalling procedures". ITU-T 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". ITU-T Recommendation Q.771: "Specifications of Signalling System No.7; Functional description of transaction capabilities". ITU-T Recommendation Q.772: "Specifications of Signalling System No.7; Transaction capabilities information element definitions". ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding". ITU-T Recommendation Q.774: "Specifications of Signalling System No.7; Transaction capabilities procedures". ITU-T Recommendation Q.775: "Specifications of Signalling System No.7; Guide-lines for using transaction capabilities". ITU-T Recommendation X.200: "Reference Model of Open systems interconnection for CCITT Applications". ITU-T Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One (ASN.1)". ITU-T Recommendation X.209 (1988): "Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)". ITU-T Recommendation X.210: "Open systems interconnection layer service definition conventions". 3GPP TS 23.018: "Basic Call Handling". 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2". 3GPP TS 23.079: "Support of Optimal Routeing (SOR) - Stage 2". 3GPP TS 43.068: "Voice Group Call Service (VGCS) - Stage 2". 3GPP TS 43.069: "Voice Broadcast service (VBS) - Stage 2". ANSI T1.113: "Signaling System No. 7 (SS7) - ISDN User Part". GSM 03.54 "Shared Inter Working Function (SIWF) - Stage 2". 3GPP TS 23.060: "General Packet Radio Service (GPRS) Description; Stage 2". 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) Visitors Location Register (VLR); Gs interface layer 3 specification". 3GPP TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2".

[100] [101] [102] [103] [104] [105] [106] [107]

118

1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549

119 Release 4 120 121

31

3GPP TS 29.002 V4.17.0 (2006-06)

[108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122] [123]

3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical Realisation Stage 2". ANSI T1.112 (1996): "Telecommunication Signalling No. 7 - Signaling Connection Control Part (SCCP)". 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2." ITU-T Recommendation Q.711: "Specifications of Signalling System No.7; Signalling System No. 7 Functional Description of the Signalling Connection Control Part". ITU-T Recommendation Q.712: "Specifications of Signalling System No.7; Signalling System No. 7 Definition and Function of SCCP Messages". ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; Signalling System No. 7 SCCP formats and codes". ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling System No. 7 Signalling Connection Control Part Procedures". ITU-T Recommendation Q.716: "Specifications of Signalling System No.7; Signalling System No. 7 Signalling Connection Control Part (SCCP) Performance". ITU-T Q.850, May 1998: "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". 3GPP TS 22.135: "Multicall; Service description; Stage 1". 3GPP TS 23.135: "Multicall supplementary service; Stage 2". 3GPP TS 24.135: "Multicall supplementary service; Stage 3". 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". 3GPP TS 29.202: "SS7 signalling transport in core network" 3GPP TS 23.032: "Universal Geographical Area Description (GAD)" 3GPP TS 32.215: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain".

1550

3 Abbreviations

1551 Abbreviations used in the present document are listed in 3GPP TS 21.905.

1552 1553 1554

4 Void 5 Overload and compatibility overview


5.1 Overload control

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

1557

5.1.1 Overload control for MSC (outside MAP)

1558 For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load:

122

1559 1560 1561 1562 1563

123 Release 4 124 125

32

3GPP TS 29.002 V4.17.0 (2006-06)

ISDN CCITT Recommendation Q.764 (Automatic Congestion Control), applicable to reduce the mobile terminating traffic; BSSAP 3GPP TS 48.008 [49] (A-interface Flow Control), applicable to reduce the mobile originating traffic.

1564

5.1.2 Overload control for MAP entities

1565 For all MAP entities, especially the HLR, the following overload control method is applied. 1566 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) 1567 may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP 1568 service provider and is based upon the priority of the application context. 1569 Since most of the affected MAP operations are supervised in the originating entity by TC timers (medium) an additional 1570 delay effect is achieved for the incoming traffic. 1571 If overload levels are applicable in the Location Registers the MAP operations should be discarded taking into account 1572 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 1573 and table 5.1/4 for the SMLC; the lowest priority is discarded first). 1574 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 1575 a proposal that might be changed due to network operator/implementation matters.

126

1576

127 Release 4 128 129

33

3GPP TS 29.002 V4.17.0 (2006-06)

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


Responder = HLR Mobility Management networkLocUp (updateLocation), (restoreData/v2), (sendParameters/v1) gprsLocationUpdate (updateGPRSLocation/v3), infoRetrieval (sendAuthenticationInfo/v2/v3), (sendParameters/v1) istAlerting (istAlert/v3) (purgeMS/v2/v3) msPurging (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) Initiating Entity VLR

1577 1578 Priority high 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607

SGSN VLR/SGSN MSC msPurging SGSN GMSC

VLR

GMSC gsmSCF VLR

1608 1609 1610


1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 Priority low

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/v4) failureReport (failureReport/v3) authenticationFailureReport (authenticationFailureReport/v3)

GMLC
VLR

VLR VLR VLR GGSN/SGSN GGSN/SGSN VLR/SGSN

1635 1636

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.

130

1637

131 Release 4 132 133

34

3GPP TS 29.002 V4.17.0 (2006-06)

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


Initiating Entity HLR HLR HLR HLR

1638 Responder = SGSN 1639 Priority high 1640 Mobility and Location Register Management 1641 locationCancel 1642 (cancelLocation v3) 1643 reset 1644 (reset) 1645 subscriberDataMngt 1646 (insertSubscriberData v3), 1647 (deleteSubscriberData v3) 1648 tracing 1649 (activateTraceMode), 1650 (deactivateTraceMode) 1651 1652 Short Message Service 1653 shortMsgMT-Relay 1654 (MT-ForwardSM v3) 1655 (forwardSM v1/v2) 1656 1657 Location Services 1658 1659 locationSvcEnquiry 1660 (provideSubscriberLocation v3) 1661 1662 Network-Requested PDP context activation 1663 gprsNotify HLR 1664 (noteMsPresentForGprs v3), 1665 1666 Priority low

MSC

GMLC

1667 1668

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.

134

1669

135 Release 4 136 137

35

3GPP TS 29.002 V4.17.0 (2006-06)

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


Initiating Entity MSC

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

Group call and Broadcast call groupCallControl (prepareGroupCall/v3)


Mobility and Location Register Management locationCancel (cancelLocation) reset (reset) immediateTermination (istCommand/v3) interVlrInfoRetrieval (sendIdentification/v2/v3), (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 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

1671 1672

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.

138

1673

139 Release 4 140 141

36

3GPP TS 29.002 V4.17.0 (2006-06)

5.1.3 Congestion control for Signalling System No. 7

1674 The requirements of SS7 Congestion control have to be taken into account as far as possible. 1675 Means that could be applied to achieve the required traffic reductions are described in clauses 5.1.1 and 5.1.2.

1676 1677

5.2 Compatibility
5.2.1 General

1678 The present document of the Mobile Application Part is designed in such a way that an implementation which conforms 1679 to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR 1680 interface. 1681 A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol 1682 version used between two entities for supporting a MAP-user signalling procedure. 1683 1684 1685 1686

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.

1687 A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of 1688 version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP 1689 operational version 1). 1690 1691 1692 1693 1694 1695 1696 1697

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 functionality (if possible). When a signalling procedure can be supported by several application contexts that differ by their version number, the MAP-User needs to select a name. It can either select the name that 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 is minimised.

1698

5.2.2 Strategy for selecting the Application Context (AC) version

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

1702 5.2.2.1
1703 1704 1705 1706 1707 1708 1709

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.

1710 A second table (table 2) contains an entry for each destination that has an entry in table 1. For a given entity, the entry 1711 in table 2 may be a single application context version or a vector of different versions applying to different application 1712 contexts for that entity. Table 2 is managed as described in clause 5.2.2.2. 1713 The data for each destination will go through the following states: 1714 1715

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;

142

1716 1717 1718 1719

143 Release 4 144 145

37

3GPP TS 29.002 V4.17.0 (2006-06)

b) the version shown in table 1 is "unknown"; table 2 is used, and maintained as described in clause 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.

1720 5.2.2.2

Managing the version look-up table

1721 WHEN it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the 1722 originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the 1723 IMSI or the MSISDN. 1724 IF the entity number is known: 1725 1726 1727 1728

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.

1729 WHEN starting a procedure, the originating MAP-user looks up its version control table. 1730 IF the destination address is known and not timed-out. 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752

THEN It retrieves the appropriate AC-name and uses it IF the dialogue is accepted by the peer THEN 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 replaces the old AC-name by the new one in the list of associated highest AC supported. ELSE It uses the AC-name that 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.

146

1753 1754

147 Release 4 148 149

38

3GPP TS 29.002 V4.17.0 (2006-06)

ELSE It replaces the old AC-name by the new one in the list of highest supported AC and reset the timer.

1755 5.2.2.3

Optimising the method

1756 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 1757 each subscriber the version of the AC-name used at location updating. Then: 1758 1759 1760 1761 1762 1763 1764 1765 1766

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.

1767 1768

6 Requirements concerning the use of SCCP and TC


6.1 Use of SCCP

1769 The Mobile Application Part (MAP) makes use of the services offered by the Signalling Connection Control Part 1770 (SCCP). 1771 MAP supports the following SCCP versions:

1772 1773
1774 1775 1776 1777 1778 1779 1780

Signalling Connection Control Part, Signalling System no. 7 CCITT (Blue Book SCCP); Signalling Connection Control Part, Signalling System no. 7 ITU-T Recommendation (07/96) Q.711 to Q.716 (White Book SCCP). Support of White Book SCCP at the receiving side shall be mandated from 00:01hrs, 1st July 2002(UTC). However, for signalling over the MAP E-interface to support inter-MSC handover/relocation, the support of White Book SCCP shall be mandated with immediate effect. A White Book SCCP message will fail if any signalling point used in the transfer of the message does not support White Book SCCP. Therefore it is recommended that the originator of the White Book SCCP message supports a drop back mechanism or route capability determination mechanism to interwork with signalling points that are beyond the control of GSM/UMTS network operators.

1781 In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. Interworking 1782 between a PLMN in North America and a PLMN outside North America will involve an STP to translate between 1783 ANSI SCCP and ITU-T/CCITT SCCP. 1784 The SCCP is identified as an MTP3-user and the transport of SCCP messages between two entities shall be 1785 accomplished according to the 3GPP TS 29.202 [121].

1786

6.1.1 SCCP Class

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

1788

6.1.2 Sub-System Number (SSN)

1789 The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are 1790 addressed by sub-system numbers (SSNs). The SSNs for MAP are specified in 3GPP TS 23.003 [17].

150

1791 When the SGSN emulates MSC behaviour for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, 1792 MAP_CHECK_IMEI, MAP_SUBSCRIBER_LOCATION_REPORT) towards entities which do not support 1793 interworking to SGSNs, it shall use the MSC SSN in the calling party address instead of the SGSN SSN.

151 Release 4 152 153

39

3GPP TS 29.002 V4.17.0 (2006-06)

1794 1795 6.1.3.1

6.1.3 SCCP addressing


Introduction

1796 Within the GSM System there will be a need to communicate between entities within the same PLMN and in different 1797 PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) 1798 and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. 1799 Only the entities that should be addressed are described below. If the CCITT or ITU-T SCCP is used, the format and 1800 coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 1801 with the following restrictions: 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823

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 3GPP TS 23.066 [108]) 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; 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).

1824 If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall 1825 comply with ANSI specification T1.112 with the following restrictions: 1826 1827 1828 1829 1830

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

154

1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847

155 Release 4 156 157

40

3GPP TS 29.002 V4.17.0 (2006-06)

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).

1848 If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and 1849 E.214 is applicable. 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870

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. The PLMN where the previous VLR is located is identified by the E.212 numbering plan elements of the Location Area Identification, i.e. 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.

1871 The following clauses describe the method of SCCP addressing appropriate for each entity both for the simple 1872 intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered:

158

1873 1874 1875 1876 1877 1878 1879 1880 1881 1882

159 Release 4 160 161

41

3GPP TS 29.002 V4.17.0 (2006-06)

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 Centre (GMLC).

1883 6.1.3.2

The Mobile-services Switching Centre (MSC)

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

1885 6.1.3.2.1

MSC interaction during handover or relocation

1886 The address is derived from the target Cell id or from the target RNC id.

1887 6.1.3.2.2

MSC for short message routing

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

1891 6.1.3.2.3

MSC for location request routing

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

1894 6.1.3.2.4

MSC for LMU Control

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

1897 6.1.3.3

The Home Location Register (HLR)

1898 There are several cases where the HLR has to be addressed.

1899 6.1.3.3.1
1900 1901 1902 1903

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).

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

162

1907 6.1.3.3.2
1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918

163 Release 4 164 165

42

3GPP TS 29.002 V4.17.0 (2006-06)

Before location updating completion

When an 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 an E.164 HLR address; or in the case of intra-PLMN signalling, an SPC.

1919 When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of 1920 the SCCP message containing the first responding CONTINUE message. 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932

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.

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

1937 6.1.3.3.3
1938 1939 1940 1941 1942 1943

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.

1944 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the 1945 E.164 MSISDN or the E.164 number allocated to the HLR or either the E.214 Mobile Global Title derived from the 1946 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).

166

1947 6.1.3.3.4
1948 1949 1950 1951 1952 1953 1954 1955 1956

167 Release 4 168 169

43

3GPP TS 29.002 V4.17.0 (2006-06)

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.

1957 6.1.3.3.5
1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974

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.

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

1977 6.1.3.3.6
1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994

Before GPRS location updating completion

When an MS registers for the first time in an 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 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 an E.164 HLR address; or in the case of intra-PLMN signalling, 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;

170

1995 1996 1997 1998

171 Release 4 172 173

44

3GPP TS 29.002 V4.17.0 (2006-06)

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.

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

2001 6.1.3.3.7
2002 2003 2004 2005 2006

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.

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

2009 6.1.3.3.8
2010 2011 2012 2013

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.

2014 6.1.3.4

The Visitor Location Register (VLR)

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

2016 6.1.3.4.1

Inter-VLR information retrieval

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

2020 6.1.3.4.2

HLR request

2021 The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR service area. 2022 This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has 2023 indicated successful completion of the update location procedure to the VLR. 2024 2025 2026 2027 2028

When initiating dialogues towards the VLR after successful completion of location updating, the routeing information used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the update location dialogue. If the VLR is in the same PLMN as the HLR, the VLR may be addressed directly by an SPC derived from the E.164 VLR number. For dialogues via the international PSTN/ISDN signalling network, presence of the E.164 VLR number in the Called Party Address is required.

2029 6.1.3.5

The Interworking MSC (IWMSC) for Short Message Service

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

2032 6.1.3.6

The Equipment Identity Register (EIR)

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

174

2034 6.1.3.7

175 Release 4 176 177

45

3GPP TS 29.002 V4.17.0 (2006-06)

The Shared Inter Working Function (SIWF)

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

2037 6.1.3.8
2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050

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 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 3GPP TS 23.003 [17]) 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.

2051 6.1.3.9
2052 2053 2054 2055

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.

2056 6.1.3.10

The Gateway MSC (GMSC) for Short Message Service

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

2059 6.1.3.10A 2060 6.1.3.10A.1 2061 6.1.3.10A.2 2062 6.1.3.10B


2063 2064 2065 2066

Void
Void Void

The Gateway Mobile Location Centre (GMLC)

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

2067 6.1.3.11

Summary table

2068 The following tables summarise the SCCP address used for invoke operations. As a principle, within a PLMN either an 2069 SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT 2070 must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. 2071 For a response, the originating address passed in the invoke is used as SCCP Called Party Address. For extra-PLMN 2072 addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC 2073 derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP.

178

2074

179 Release 4 180 181

46

3GPP TS 29.002 V4.17.0 (2006-06)

Table 6.1/1

182

183 Release 4 184 185 to from

47 fixed net work


-----

3GPP TS 29.002 V4.17.0 (2006-06) EIR


-----

HLR
E:GT T:MSISDN ---

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

MSC
-----

gsmSCF
--I:SPC/GT E:GT T:gsmSCF NUMBER 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 ---

fixed network Home Location Register Visitor Location Register

---

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

---

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

---

---

---

I:SPC/GT

---

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

E:GT
T:MSC NUMBER

E:GT
T:SGSN NUMBER

186

187 Release 4 48 3GPP TS 29.002 V4.17.0 (2006-06) 188 189 I: Intra-PLMN. E: Extra (Inter)-PLMN. T: Address Type. GT: 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).

2075 2076
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 Centre I: Intra-PLMN. E: Extra (Inter)-PLMN. T: Address Type. GT: Global Title. MGT: E.214 Mobile Global Title. SPC: Signalling Point Code.

Table 6.1/2
GMLC
------I:SPC/GT E:GT T:MLC Number I:SPC/GT E:GT T:MSISDN ---

I:SPC/GT E:GT T:MLC Number ---

2077

190

191 Release 4 192 193

49

3GPP TS 29.002 V4.17.0 (2006-06)

2078

6.2 Use of TC

2079 The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of Signalling 2080 System No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be 2081 consulted for the full specification of TC. 2082 The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility. 2083 From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is 2084 for further study. 2085 Transaction Capabilities refers to a protocol structure above the network layer interface (i.e., the SCCP service 2086 interface) up to the application layer including common application service elements but not the specific application 2087 service elements using them. 2088 TC is structured as a Component sub-layer above a Transaction sub-layer. 2089 The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues 2090 and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives 2091 and TC-Component handling primitives respectively. 2092 Services for dialogue control include the ability to exchange information related to application-context negotiation as 2093 well as initialisation data. 2094 2095 2096 2097 2098 2099 2100

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).

2101 2102

7 General on MAP services


7.1 Terminology and definitions

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

2105

7.2 Modelling principles

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

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

2108
2109

Figure 7.2/1: Modelling principles

2110 The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the 2111 service interface.

194

2112 A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such 2113 cases the overall procedure is synchronised by the service-user. 2114 The MAP service-primitives are named using the following notation: 2115

195 Release 4 196 197

50

3GPP TS 29.002 V4.17.0 (2006-06)

MAP-ServicePrimitiveName type

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

2125

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.

2126 All MAP service-users require access to services for performing basic application layer functions: 2127 2128 2129 2130 2131

2132 For these purposes the following common services are defined: 2133 2134 2135 2136 2137 2138

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

2139 In defining the service-primitives the following convention is used for categorising parameters: 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150

M O U C -

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; 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;

198

2151 2152 2153 2154 2155 2156 2157 2158

199 Release 4 200 201

51

3GPP TS 29.002 V4.17.0 (2006-06)

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.

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

2161

7.3.1 MAP-OPEN service

2162 This service is used for establishing a MAP dialogue between two MAP service-users. The service is a confirmed 2163 service with service primitives as shown in table 7.3/1. 2164
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

2165 2166 Application context name: 2167 This parameter identifies the type of application context being established. If the dialogue is accepted the received 2168 application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version 2169 supported. 2170 Destination address: 2171 A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this 2172 parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is 2173 issued. 2174 Destination-reference: 2175 This parameter is a reference that refines the identification of the called process. It may be identical to Destination 2176 address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only 2177 these services are allowed to use it.

202

2178

203 Release 4 204 205

52

3GPP TS 29.002 V4.17.0 (2006-06)

Table 7.3/2: Use of the destination reference Reference type IMSI IMSI IMSI IMSI IMSI IMSI IMSI (note 1) IMSI (note 2) IMSI (note 2) IMSI (note 3) 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

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
2179 2180 2181 2182 2183 2185 2186
2184

NOTE 1: On the HLR - HLR interface and on the HLR - gsmSCF interface the Destination reference shall be either IMSI or MSISDN. NOTE 2: On the gsmSCF - HLR interface and on the HLR - HLR interface the Destination reference shall be either IMSI or MSISDN. NOTE 3: Only when the IMSI and the LMSI are received together from the HLR in the mobile terminated short message transfer.

2187 Originating address: 2188 A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, 2189 this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is 2190 issued. 2191 Originating-reference: 2192 2193 2194 2195 2196

This parameter is a reference that 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. Furthermore the receiving entity may be able to use the value of the Originating-reference to screen the service indication.

206

2197

207 Release 4 208 209

53

3GPP TS 29.002 V4.17.0 (2006-06)

Table 7.3/3: Use of the originating reference 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 (note) ISDN-Address-String (note) 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 Originated entity address Originated entity address

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-UNSTRUCTUREDSS-NOTIFY MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY
2198 2199

NOTE:

The Originating reference may be omitted.

2200 Specific information: 2201 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2202 information is not specified by GSM and shall be performed according to operator specific requirements. 2203 Responding address: 2204 An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is 2205 different from the destination address). 2206 Result: 2207 This parameter indicates whether the peer accepts the dialogue. 2208 Refuse reason: 2209 This parameter is present only if the Result parameter indicates that the dialogue is refused. It takes one of the following 2210 values:

2211 2212 2213 2214 2215 2216

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

210

2217

211 Release 4 212 213

54

3GPP TS 29.002 V4.17.0 (2006-06)

7.3.2 MAP-CLOSE service

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

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


Parameters Release method Specific Information Request M U Indication C(=)

2222 2223 Release method: 2224 This parameter can take the following two values: 2225 2226 2227

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.

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

2231

7.3.3 MAP-DELIMITER service

2232 This service is used to explicitly request the transfer of the MAP protocol data units to the peer entities. 2233 See also clause 7.4 and 7.5 for the detailed use of the MAP-DELIMITER service. 2234 The service is an unconfirmed service with service-primitives as shown in table 7.3/5. 2235

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


Parameters Request Indication

2236

2237

7.3.4 MAP-U-ABORT service

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

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


Parameters User reason Diagnostic information Specific information Request M U U Indication M(=) C(=) C(=)

2241 2242 User reason: 2243 This parameter can take the following values: 2244 2245 2246

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

resource unavailable;

214

2247 2248 2249 2250 2251

215 Release 4 216 217

55

3GPP TS 29.002 V4.17.0 (2006-06)

the requested user resource is unavailable for reasons other than congestion; application procedure cancellation; the procedure is cancelled for reasons detailed in the diagnostic information parameter;

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

2252 Diagnostic information: 2253 This parameter may be used to give additional information for some of the values of the user-reason parameter: 2254

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

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

2259

7.3.5 MAP-P-ABORT service

2260 This service enables the MAP service-provider to abort a MAP dialogue. The service is a provider-initiated service with 2261 service-primitives as shown in table 7.3/8. 2262

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


Parameters Provider reason Source Indication M M

2263 2264 Provider reason: 2265 This parameter indicates the reason for aborting the MAP dialogue: 2266 2267 2268 2269 2270 2271

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

2272 Source: 2273 This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take 2274 the following values:

218

2275 2276 2277

219 Release 4 220 221

56

3GPP TS 29.002 V4.17.0 (2006-06)

MAP problem; TC problem; network service problem. 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

2278 2279

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

2280

2281

7.3.6 MAP-NOTICE service

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

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


Parameters Problem diagnostic Indication M

2286 2287 Problem diagnostic: 2288 This parameter can take one of the following values: 2289 2290 2291 2292

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

222

2293 2294 2295 2296 2297

223 Release 4 224 225

57

3GPP TS 29.002 V4.17.0 (2006-06)

7.3.7 void 7.3.8 void 7.3.9 void 7.3.10 void

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.

2298 The sequencing of services is shown in figure 7.4/1 and is as follows: 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319

2320 The MAP service-provider may issue at any time a MAP-P-ABORT primitive towards a MAP service-user for which a 2321 MAP dialogue exists. 2322 MAP-U-ABORT primitives and MAP-P-ABORT primitives terminate the MAP dialogue.
M A P -O P E N M A P -D E L IM IT E R

U s e r s p e c ific s e r v ic e p r im itiv e

2323
2324

a) Opening

226

227 Release 4 228 229

58

3GPP TS 29.002 V4.17.0 (2006-06)

U s e r s p e c ific s e r v ic e p r im itiv e

M A P -D E L IM IT E R

2325
2326

b) Continuing
M A P -C L O S E

U s e r s p e c ific s e rv ic e p r im itiv e

2327
2328

c) Closing
M A P -U -A B O R T M A P -P -A B O R T

2329
2330 2331

d) Aborting Figure 7.4/1: Sequencing of services

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

2337 2338

7.5 General rules for mapping of services onto TC


7.5.1 Mapping of common services

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

Table 7.5/1: Mapping of common services onto 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)

230

231 Release 4 232 233

59

3GPP TS 29.002 V4.17.0 (2006-06)

MAP-U-ABORT request
NOTE:

TC-U-ABORT request

Or TC-END if the MAP-CLOSE request has been received before the MAP-DELIMITER request.

2343 2344

Table 7.5/2: Mapping of TC services onto 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) 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) MAP-P-ABORT indication (note 4) MAP-OPEN confirmation (note 5)

TC-END indication (+ component handling primitives) TC-U-ABORT indication TC-P-ABORT indication

NOTE 1: It may not be necessary to present this primitive to the user for MAP version 2 applications. NOTE 2: 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. NOTE 3: 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". NOTE 4: If the "Abort Reason" in the TC-P-ABORT indication is set to a value different from "Incorrect Transaction Portion". NOTE 5: Only if the opening sequence is pending and if the "Abort Reason" in the TC-P-ABORT indication is set to "Incorrect Transaction Portion". NOTE 6: Only if opening sequence is pending.

2345

2346

7.5.2 Mapping of user specific services

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

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)

2351 2352

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) MAP service-primitive MAP-xx indication MAP-xx confirm

234

235 Release 4 236 237

60 TC-L-CANCEL indication TC-U-REJECT indication TC-L-REJECT indication TC-R-REJECT indication

3GPP TS 29.002 V4.17.0 (2006-06)

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

2353 2354 2355 2356 2357 2358 2359

Notes to tables 7.5/3 and 7.5/4: 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 onto the same MAP-xx confirm.

2360

7.6 Definition of parameters

2361 Following is an alphabetic list of parameters used in the common MAP-services in clause 7.3: 2362
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

2363 2364 Following is an alphabetic list of parameters contained in this clause: 2365
Absent Subscriber Diagnostic SM Access connection status 7.6.8.9 7.6.9.3 Invoke Id ISDN Bearer Capability IST Alert Timer IST Information Withdrawn IST Support Indicator Kc LCS-Reference Number Linked Id LMSI Location Information Location update type Long Forwarded-to Number Long FTN Supported Lower Layer Compatibility LSA Information LSA Information Withdraw MC Information MC Subscription Data Mobile Not Reachable Reason Modification request for CSI Modification request for SS Information More Messages To Send MS ISDN MSC number MSIsdn-Alert Multicall Bearer Information Multiple Bearer Requested Multiple Bearer Not Supported 7.6.1.1 7.6.3.41 7.6.3.66 7.6.3.68 7.6.3.69 7.6.7.4 7.6.11.22 7.6.1.2 7.6.2.16 7.6.2.30 7.6.9.6 7.6.2.22A 7.6.2.22B 7.6.3.42 7.6.3.56 7.6.3.58 7.6.4.48 7.6.4.47 7.6.3.51 7.6.3.81 7.6.3.82 7.6.8.7 7.6.2.17 7.6.2.11 7.6.2.29 7.6.2.52 7.6.2.53 7.6.2.54

Access signalling information Additional Absent Subscriber Diagnostic SM Additional Location Estimate Additional number Additional signal info Additional SM Delivery Outcome Age Indicator Alert Reason Alert Reason Indicator Alerting Pattern All GPRS Data All Information Sent AN-apdu APN Authentication set list B-subscriber Address B subscriber Number B subscriber subaddress Basic Service Group

7.6.9.5 7.6.8.12 7.6.11.21 7.6.2.46 7.6.9.10 7.6.8.11 7.6.3.72 7.6.8.8 7.6.8.10 7.6.3.44 7.6.3.53 7.6.1.5 7.6.9.1 7.6.2.42 7.6.7.1 7.6.2.36 7.6.2.48 7.6.2.49 7.6.4.40

238

239 Release 4 240 241 Bearer service BSSMAP Service Handover BSSMAP Service Handover List Call Barring Data Call barring feature Call barring information Call Direction Call Forwarding Data Call Info Call reference Call Termination Indicator Called number

61 7.6.4.38 7.6.6.5 7.6.6.5A 7.6.3.83 7.6.4.19 7.6.4.18 7.6.5.8 7.6.3.84 7.6.9.9 7.6.5.1 7.6.3.67 7.6.2.24 7.6.2.25 7.6.3.78 7.6.3.38 7.6.3.52 7.6.3.1 7.6.5.8 7.6.4.49 7.6.5.9 7.6.5.10 7.6.6.10B 7.6.7.7 7.6.7.5 7.6.4.5 7.6.9.2 7.6.3.54 7.6.3.87 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.11.3 7.6.11.2 7.6.4.41 7.6.6.9 7.6.3.2 7.6.3.5 7.6.3.3 7.6.3.21 7.6.3.20 7.6.3.79 7.6.3.16 7.6.3.15 7.6.3.80 7.6.3.18 7.6.3.19 7.6.3.74 7.6.3.29 7.6.3.14 7.6.3.17 7.6.3.4 7.6.9.4 7.6.7.9 MWD status

3GPP TS 29.002 V4.17.0 (2006-06) 7.6.8.3 7.6.4.45 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.85 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.5.15 7.6.2.4 7.6.9.7 7.6.1.3 7.6.3.47 7.6.6.10 7.6.6.10A 7.6.6.6 7.6.7.2 7.6.3.11 7.6.3.12 7.6.2.19A 7.6.3.31 7.6.3.86 7.6.2.19 7.6.3.49 7.6.3.13 7.6.7.8 7.6.2.56 7.6.2.27 7.6.2.37 7.6.2.39 7.6.3.75 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 7.6.4.43 7.6.4.24

NbrUser 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 Data 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 Pre-paging supported Previous location area Id Protocol Id Provider error QoS-Subscribed Radio Resource Information Radio Resource List RANAP Service Handover Rand Regional Subscription Data Regional Subscription Response Relocation Number List Requested Info Requested Subscription Info Roaming number Roaming Restricted In SGSN Due To Unsupported Feature Roaming Restriction Due To Unsupported Feature Current Security Context Selected RAB ID Service centre address Serving Cell Id SGSN address SGSN CAMEL Subscription Info 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 SS-Event-Data SS-Info

Calling number CAMEL Subscription Info CAMEL Subscription Info Withdraw Cancellation Type Category CCBS Feature CCBS Request State Channel Type Chosen Channel Chosen Radio Resource Information Ciphering mode Cksn CLI Restriction CM service type Complete Data List Included CS Allocation Retention priority CUG feature CUG index CUG info CUG interlock CUG Outgoing Access indicator CUG subscription CUG Subscription Flag Current location area Id Current password Deferred MT-LR Data Deferred MT-LR Response Indicator eMLPP Information Encryption Information Equipment status Extensible Basic Service Group Extensible Bearer service Extensible Call barring feature Extensible Call barring information Extensible Call barring information for CSE Extensible Forwarding feature Extensible Forwarding info Extensible Forwarding information for CSE Extensible Forwarding Options Extensible No reply condition timer Extensible QoS-Subscribed Extensible SS-Data Extensible SS-Info Extensible SS-Status Extensible Teleservice External Signal Information Failure Cause

242

243 Release 4 244 245 Forwarded-to number Forwarded-to subaddress Forwarding feature Forwarding information Forwarding Options GGSN address

62 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.3.73 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.6.8 7.6.3.27 7.6.3.28

3GPP TS 29.002 V4.17.0 (2006-06) 7.6.4.2 7.6.2.5 7.6.3.30 7.6.3.7 7.6.3.70 7.6.3.71 7.6.3.36 7.6.3.36A 7.6.11.20 7.6.11.17 7.6.3.33 7.6.3.32 7.6.2.8 7.6.2.7 7.6.2.8A 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

GGSN number GMSC CAMEL Subscription Info GPRS enhancements support indicator 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 Integrity Protection Information Inter CUG options Intra CUG restrictions

SS-Status Stored location area Id Subscriber State Subscriber Status Super-Charger Supported in HLR Super-Charger Supported in Serving Network Entity Supported CAMEL Phases in VLR Supported CAMEL Phases in SGSN Supported GAD Shapes Supported LCS Capability Sets Suppress T-CSI Suppression of Announcement Target cell Id Target location area Id Target RNC 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

2366

2367

7.6.1 Common parameters

2368 The following set of parameters is used in several MAP service-primitives.

2369 7.6.1.1

Invoke Id

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

2372 7.6.1.2

Linked Id

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

2374 7.6.1.3
-

Provider error

2375 This parameter is used to indicate a protocol related type of error: 2376 2377 2378 2379

duplicated invoke Id; not supported service; mistyped parameter; resource limitation;

246

2380 2381 2382 2383 2384

247 Release 4 248 249

63

3GPP TS 29.002 V4.17.0 (2006-06)

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.

2385 7.6.1.4
NOTE:

User error

2386 This parameter can take values as follows: 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414

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 with detailed reasons as follows: Shape of location estimate not supported;

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.

250

2415

251 Release 4 252 253

64

3GPP TS 29.002 V4.17.0 (2006-06)

d) Handover problem: -no handover number available, i.e. the VLR cannot allocate a number for handover or cannot allocate the required amount of numbers for relocation; -subsequent handover failure, i.e. handover to a third MSC failed for some reason; -target cell outside group call area. e) Operation and maintenance problem: tracing buffer full, i.e. tracing cannot be performed because the tracing capacity is exceeded.

2416
2417

2418 2419
2420 2421 2422 2423 2424

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 the case of barring of Mobile 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.

2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451

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;

254

2452 2453

255 Release 4 256 257

65

3GPP TS 29.002 V4.17.0 (2006-06)

short term denial; long term denial.

2454 For definition of these errors see 3GPP TS 24.080 [38]. 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477

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 3GPP TS 23.140, under SMSSUBMIT-REPORT and SMS-DELIVERY-REPORT. If the SM entity that 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 3GPP TS 23.140;

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.

2478

i) Location services problem: -Unauthorised Requesting Network -Unauthorised LCS Client with detailed reasons as follows: Unauthorised Privacy Class Unauthorised Call/Session Unrelated External Client Unauthorised Call/Session Related External Client

2479 2480 2481 2482 2483 2484 2485 2486 2487

-Privacy override not applicable -Position method failure with detailed reasons as follows: Congestion Insufficient resources

258

2488 2489 2490 2491 2492 2493


2494 2495 2496 2497 2498 2499

259 Release 4 260 261

66

3GPP TS 29.002 V4.17.0 (2006-06)

Insufficient Measurement Data Inconsistent Measurement Data Location procedure not completed QoS not attainable Position Method Not Available in Network Position Method Not Available in Location Area Unknown or unreachable LCS Client.

j) Problem detected by an application using secure transport: Secure transport error. This error indicates that the application using secure transport returned an error. The parameter of the error indicates: The protected payload, which carries the result of applying the protection function specified in 3GPP TS 33.200 to the encoding of the parameter of the original error.

2500 7.6.1.5

All Information Sent

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

2502 2503 7.6.2.1

7.6.2 Numbering and identification parameters


IMSI

2504 This parameter is the International Mobile Subscriber Identity defined in 3GPP TS 23.003 [17].

2505 7.6.2.2

TMSI

2506 This parameter is the Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003 [17].

2507 7.6.2.3

IMEI

2508 This parameter is the International Mobile Equipment Identity defined in 3GPP TS 23.003 [17].

2509 7.6.2.4

Previous location area Id

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

2511 7.6.2.5

Stored location area Id

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

2513 7.6.2.6

Current location area Id

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

2515 7.6.2.7

Target location area Id

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

2517 7.6.2.8

Target cell Id

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

262

2519 7.6.2.8A

263 Release 4 264 265

67

3GPP TS 29.002 V4.17.0 (2006-06)

Target RNC Id

2520 This parameter refers to the identity of the RNC to which a call has to be relocated.

2521 7.6.2.9 2522 7.6.2.10

Void Originating entity number

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

2525 7.6.2.11

MSC number

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

2527 7.6.2.12

Target MSC number

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

2529 7.6.2.13

HLR number

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

2531 7.6.2.14

VLR number

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

2533 7.6.2.15

HLR Id

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

2535 7.6.2.16

LMSI

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

2538 7.6.2.17

MS ISDN

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

2541 7.6.2.18

OMC Id

2542 This parameter refers to the identity of an Operation and Maintenance Centre.

2543 7.6.2.19

Roaming number

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

2545 7.6.2.19A

Relocation Number List

2546 This parameter refers to the number(s) used for routing one call or several calls between MSCs during relocation.

2547 7.6.2.20 2548 7.6.2.21

Void Handover number

266

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

267 Release 4 268 269

68

3GPP TS 29.002 V4.17.0 (2006-06)

2550 7.6.2.22

Forwarded-to number

2551 This parameter refers to the address to which a call is to be forwarded. A subaddress may be appended. For subscribers 2552 having an originating CAMEL Phase 2 or higher subscription, this address need not be in E.164 international format.

2553 7.6.2.22A

Long forwarded-to number

2554 This parameter refers to the address to which a call is to be forwarded. A subaddress may be appended. For subscribers 2555 having an originating CAMEL Phase 2 or higher subscription this address need not be in international format.

2556 7.6.2.22B

Long FTN Supported

2557 This parameter indicates that the sending entity supports Long Forwarded-to Numbers.

2558 7.6.2.23

Forwarded-to subaddress

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

2560 7.6.2.24

Called number

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

2562 7.6.2.25

Calling number

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

2564 7.6.2.26

Originally dialled number

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

2566 7.6.2.27

Service centre address

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

2568 7.6.2.28

Zone Code

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

2572 7.6.2.29

MSIsdn-Alert

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

2575 7.6.2.30

Location Information

2576 This parameter indicates the location of the served subscriber as defined in 3GPP TS 23.018 [97].

2577 7.6.2.31

GMSC Address

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

2579 7.6.2.32

VMSC Address

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

270

2581 7.6.2.33

271 Release 4 272 273

69

3GPP TS 29.002 V4.17.0 (2006-06)

Group Id

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

2584 7.6.2.34

North American Equal Access preferred Carrier Id

2585 This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an inter-exchange 2586 carrier. This identity is used at: 2587 2588 2589

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

2590 7.6.2.35

SIWFS Number

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

2592 7.6.2.36

B-subscriber address

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

2595 7.6.2.37

Serving cell Id

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

2597 7.6.2.38

SGSN number

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

2599 7.6.2.39

SGSN address

2600 This parameter refers to the IP-address of a SGSN. This parameter is defined in 3GPP TS 23.003 [17].

2601 7.6.2.40

GGSN address

2602 This parameter refers to the IP-address of a GGSN. This parameter is defined in 3GPP TS 23.003 [17].

2603 7.6.2.41

GGSN number

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

2606 7.6.2.42

APN

2607 This parameter refers to the DNS name of a GGSN. This parameter is defined in 3GPP TS 23.060 [104].

2608 7.6.2.43

Network Node number

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

2610 7.6.2.44

PDP-Type

2611 This parameter indicates which type of protocol is used by the MS as defined in 3GPP TS 23.060 [104].

274

2612 7.6.2.45

275 Release 4 276 277

70

3GPP TS 29.002 V4.17.0 (2006-06)

PDP-Address

2613 This parameter indicates the address of the data protocol as defined in 3GPP TS 23.060 [104].

2614 7.6.2.46

Additional number

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

2616 7.6.2.47

P-TMSI

2617 This parameter is the Packet Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003 [17].

2618 7.6.2.48

B-subscriber number

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

2620 7.6.2.49

B-subscriber subaddress

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

2622 7.6.2.50

LMU Number

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

2624 7.6.2.51

MLC Number

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

2626 7.6.2.52

Multicall Bearer Information

2627 This parameter refers to the number of simultaneous bearers supported per user by the serving network.

2628 7.6.2.53

Multiple Bearer Requested

2629 This parameter indicates whether multiple bearers are requested for a relocation.

2630 7.6.2.54

Multiple Bearer Not Supported

2631 This parameter indicates whether multiple bearers are supported.

2632 7.6.2.55

PDP-Charging Characteristics

2633 This parameter indicates the charging characteristics associated with a specific PDP context as defined in 3GPP 2634 TS 32.015.

2635 7.6.2.56

Selected RAB ID

2636 The selected radio access bearer to be kept at subsequent inter-MSC handover from UMTS to GSM.

2637 7.6.2.57

RAB ID

2638 This parameter indicates the radio access bearer identifier as defined in 3GPP TS 25.413. This parameter is used to 2639 relate the radio resources with the radio access bearers.

2640 2641 7.6.3.1

7.6.3 Subscriber management parameters


Category

278

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

279 Release 4 280 281

71

3GPP TS 29.002 V4.17.0 (2006-06)

2643 7.6.3.2

Equipment status

2644 This parameter refers to the status of the mobile equipment as defined in 3GPP TS 22.016 [7].

2645 7.6.3.3

Extensible Bearer service

2646 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in 3GPP 2647 TS 22.002 [3]. This parameter is used only for subscriber profile management. Extensible Bearer service values include 2648 all values defined for a Bearer service parameter (7.6.4.38).

2649 7.6.3.4

Extensible Teleservice

2650 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in 3GPP TS 22.003 2651 [4]. This parameter is used only for subscriber profile management. Extensible Teleservice values include all values 2652 defined for a Teleservice parameter (7.6.4.39).

2653 7.6.3.5
2654 2655 2656 2657

Extensible Basic Service Group

This parameter refers to the Basic Service Group either as an extensible bearer service (see clause 7.6.3.3) or an extensible teleservice (see clause 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.

2658 7.6.3.6

GSM bearer capability

2659 This parameter refers to the GSM bearer capability information element defined in 3GPP TS 24.008 [35].

2660 7.6.3.7
-

Subscriber Status

2661 This parameter refers to the barring status of the subscriber: 2662 2663

service granted; Operator Determined Barring.

2664 7.6.3.8

CUG Outgoing Access indicator

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

2666 7.6.3.9

Operator Determined Barring General Data

2667 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate. 2668 This set only includes those limitations that can be 2669 2670 2671 2672 2673

a) controlled in the VLR, b) controlled in the SGSN, c) controlled in the SGSN applied for short message transfer only, d) interrogated or modified by the gsmSCF:

ODB category

Controlled in the VLR Controlled in the SGSN

Controlled in the Interrogatable and SGSN applied for modifyable by the short message transfer gsmSCF only

282

283 Release 4 284 285

72

3GPP TS 29.002 V4.17.0 (2006-06)

All outgoing calls barred 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 international 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

X X X

X X X

X X X

X X

X X

X X

X X X

X X X

286

287 Release 4 288 289

73

3GPP TS 29.002 V4.17.0 (2006-06)

barred

All packet Oriented Services barred Roamer Access to HPLMN-AP barred Roamer Access to VPLMN-AP barred Outgoing calls when roaming outside the home PLMN country All incoming calls Incoming calls when roaming outside the home PLMN country Incoming calls when roaming outside the zone of the home PLMN country Roaming outside the home PLMN Roaming outside the home PLMN country Registration of any call forwarded-to number Registration of any international call forwarded-to number Registration of any international call forwarded-to number except to a number within the HPLMN country Registration of any inter-zone call forwarded-to number Registration of any inter-zone call forwarded-to number except to a number within the HPLMN country
2674 2675 2676

X X X

X X X X

X X

X X X X

2677 7.6.3.10

ODB HPLMN Specific Data

290

2678 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate only 2679 when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in the 2680 VLR or in the SGSN: 2681 2682 2683 2684

291 Release 4 292 293

74

3GPP TS 29.002 V4.17.0 (2006-06)

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

2685 7.6.3.11

Regional Subscription Data

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

2688 7.6.3.12

Regional Subscription Response

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

2691 7.6.3.13

Roaming Restriction Due To Unsupported Feature

2692 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 2693 feature or service is indicated as unsupported by the VLR.

2694 7.6.3.14
-

Extensible SS-Info

2695 This parameter refers to all the information related to a supplementary service and is a choice between: 2696 2697 2698 2699

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

2700 7.6.3.15
-

Extensible forwarding information


(see clause 7.6.4.1); (see clause 7.6.3.16).

2701 This parameter represents the information related to each call forwarding service: 2702 2703 2704

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.

2705 7.6.3.16

Extensible forwarding feature

2706 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 2707 following information, as required: 2708 2709 2710 2711 2712

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

(see clause 7.6.3.5); (see clause 7.6.3.17); (see clause 7.6.2.22); (see clause 7.6.2.23); (see clause 7.6.3.18);

294

2713 2714 2715 2716 2717 2718 2719

295 Release 4 296 297

75

3GPP TS 29.002 V4.17.0 (2006-06)

extensible no reply condition timer long forwarded-to number

(see clause 7.6.4.19); (see clause 7.6.2.22A).

If a number is required to define the forwarded-to destination then: If the VLR supports Long Forwarded-to Numbers then the long forwarded-to number shall be present and the forwarded-to number shall be absent; If the VLR does not support Long Forwarded-to Numbers then the forwarded-to number shall be present and the long forwarded-to number shall be absent.

2720 7.6.3.17

Extensible SS-Status

2721 This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011 [22].

2722 7.6.3.18

Extensible Forwarding Options

2723 This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following 2724 information: 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734

notification to forwarding party parameter); redirection notification to the forwarded-to party parameter); notification to calling party parameter); redirecting presentation parameter); forwarding reason parameter).

(see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this

2735 7.6.3.19

Extensible No reply condition timer

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

2737 7.6.3.20
SS-Code

Extensible Call barring information

2738 This parameter contains for each call barring service: 2739 2740 2741

(see clause 7.6.4.1); (see clause 7.6.3.21).

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

2742 7.6.3.21

Extensible Call barring feature

2743 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 2744 contains the following information: 2745 2746

Extensible Basic Service Group provisioned SS-Status

(see clause 7.6.3.5); (see clause 7.6.3.17).

2747 7.6.3.22

CUG info

2748 This parameter refers to the overall information required for operation for each CUG:

298

2749 2750

299 Release 4 300 301

76

3GPP TS 29.002 V4.17.0 (2006-06)

CUG subscriptionList; CUG featureList.

2751 7.6.3.23

CUG subscription

2752 This parameter refers to the set of basic information for each CUG defined in that subscription. The following 2753 information is stored: 2754 2755 2756 2757

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

2758 7.6.3.24

CUG interlock

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

2760 7.6.3.25

CUG index

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

2762 7.6.3.26

CUG feature

2763 This parameter contains two parameters that are associated with the Basic Service Group. If the Basic Service Group 2764 Code is not present the feature applies to all Basic Services. The following parameters are included: 2765 2766 2767 2768 2769 2770

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.

2771 See 3GPP TS 22.085 [13] for meaning of this parameter.

2772 7.6.3.27

Inter CUG options

2773 This parameter indicates the subscribers' ability to make and receive calls outside a specific closed user group. It takes 2774 any of the following values: 2775 2776 2777 2778

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).

2779 7.6.3.28

Intra CUG restrictions

2780 This parameter describes whether or not the subscriber is allowed to originate calls to or to receive calls from within the 2781 CUG. It can take any of the following values: 2782

no CUG restrictions;

302

2783 2784

303 Release 4 304 305

77

3GPP TS 29.002 V4.17.0 (2006-06)

CUG incoming calls barred; CUG outgoing calls barred.

2785 7.6.3.29
SS-Code

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

2786 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 2787 2788 2789 2790 2791

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

2792 7.6.3.30

Subscriber State

2793 This parameter indicates the state of the MS as defined in 3GPP TS 23.018 [97].

2794 7.6.3.31

Requested Info

2795 This parameter indicates the subscriber information being requested as defined in 3GPP TS 23.018 [97].

2796 7.6.3.32

Suppression of Announcement

2797 This parameter indicates if the announcement or tones shall be suppressed as defined in 3GPP TS 23.078.

2798 7.6.3.33

Suppress T-CSI

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

2800 7.6.3.34

GMSC CAMEL Subscription Info

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

2803 7.6.3.35

VLR CAMEL Subscription Info

2804 This parameter identifies the subscriber as having CAMEL services that are invoked in the MSC or VLR.

2805 7.6.3.36

Supported CAMEL Phases in the VLR

2806 This parameter indicates which phases of CAMEL are supported in the VLR.

2807 7.6.3.36A

Supported CAMEL Phases in the SGSN

2808 This parameter indicates which phases of CAMEL are supported in the SGSN.

2809 7.6.3.37

CUG Subscription Flag

2810 This parameter indicates a that a subscriber with a T-CSI also has a CUG subscription. It is defined in 3GPP TS 23.078.

2811 7.6.3.38

CAMEL Subscription Info Withdraw

2812 This parameter indicates that CAMEL Subscription Info shall be deleted from the VLR or SGSN.

306

2813 7.6.3.39

307 Release 4 308 309

78

3GPP TS 29.002 V4.17.0 (2006-06)

Voice Group Call Service (VGCS) Data

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

2815 7.6.3.40

Voice Broadcast Service (VBS) Data

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

2819 7.6.3.41

ISDN bearer capability

2820 This parameter refers to the ISDN bearer capability information element defined in 3GPP TS 29.007 [56].

2821 7.6.3.42

Lower layer Compatibility

2822 This parameter refers to the lower layer compatibility information element defined in 3GPP TS 24.008 [35].

2823 7.6.3.43

High Layer Compatibility

2824 This parameter refers to the high layer compatibility information element defined in 3GPP TS 24.008 [35].

2825 7.6.3.44

Alerting Pattern

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

2828 7.6.3.45

GPRS Subscription Data Withdraw

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

2830 7.6.3.46

GPRS Subscription Data

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

2832 7.6.3.47

QoS-Subscribed

2833 This parameter indicates the quality of service subscribed for a certain service. It is defined in 3GPP TS 23.060 [104].

2834 7.6.3.48

VPLMN address allowed

2835 This parameter specifies whether the MS is allowed to use a dynamic address allocated in the VPLMN. It is defined in 2836 3GPP TS 23.060 [104].

2837 7.6.3.49

Roaming Restricted In SGSN Due To Unsupported Feature

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

2840 7.6.3.50

Network Access Mode

2841 This parameter is defined in 3GPP TS 23.108.

2842 7.6.3.51

Mobile Not Reachable Reason

2843 This parameter stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at 2844 the MSC, SGSN or both. It is defined in 3GPP TS 23.140.

310

2845 7.6.3.52

311 Release 4 312 313

79

3GPP TS 29.002 V4.17.0 (2006-06)

Cancellation Type

2846 This parameter indicates the reason of location cancellation. It is defined in 3GPP TS 23.060 [104].

2847 7.6.3.53

All GPRS Data

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

2849 7.6.3.54

Complete Data List Included

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

2852 7.6.3.55

PDP Context Identifier

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

2854 7.6.3.56

LSA Information

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

2858 7.6.3.57

SoLSA support indicator

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

2860 7.6.3.58

LSA Information Withdraw

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

2862 7.6.3.59

LMU Indicator

2863 This parameter indicates the presence of an LMU.

2864 7.6.3.60
-

LCS Information

2865 This parameter defines the LCS related information for an MS subscriber and contains the following components: 2866 2867 2868

GMLC List LCS Privacy Exception List MO-LR List

(see clause 7.6.3.61). (see clause 7.6.3.62). (see clause 7.6.3.65A).

2869 7.6.3.61

GMLC List

2870 This parameter contains the addresses of all GMLCs that are permitted to issue a call/session unrelated or call/session 2871 related MT-LR location request for this MS. Usage of this parameter is defined in 3GPP TS 23.271.

2872 7.6.3.62

LCS Privacy Exception List

2873 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 2874 information is provided: 2875 2876

SS-Code a list of LCS privacy exception parameters

(see clause 7.6.4.1); (see clause 7.6.3.63).

314

2877 7.6.3.63

315 Release 4 316 317

80

3GPP TS 29.002 V4.17.0 (2006-06)

LCS Privacy Exception Parameters

2878 This parameter gives the status of each LCS privacy exception class and any additional parameters relevant to this class. 2879 The parameter contains the following information: 2880 2881 2882 2883

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

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

2884 7.6.3.64
2885 2886 2887 2888 2889 2890

External Client List

This parameter is only applicable to the call/session unrelated privacy class and call/session related privacy class, and gives the identities of the external clients that are allowed to locate a target MS for a 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 3GPP TS 23.271.

2891 7.6.3.65

Internal Client List

2892 This parameter is only applicable to the PLMN operator privacy class and gives the identities of the internal PLMN 2893 operator clients that are allowed to locate a target MS for an NI-LR or MT-LR. Usage of this parameter is defined in 2894 3GPP TS 23.271.

2895 7.6.3.65A

MO-LR List

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

SS-Code

(see clause 7.6.4.1).

2899 7.6.3.65B
2900 2901 2902 2903

Privacy Notification to MS User

This parameter is applicable to the call/session unrelated privacy class and call/session related privacy class. For each privacy class it indicates whether the MS user shall be notified for athat class MT-LR from any value added LCS client when the MT-LR is restricted and be enabled to accept or override the restriction. Usage of this parameter is defined in 3GPP TS 23.271.

2904 7.6.3.65C

GMLC List Withdraw

2905 This parameter indicates whether the subscribers LCS GMLC list shall be deleted from the VLR or SGSN.

2906 7.6.3.66

IST Alert Timer

2907 This parameter indicates the IST Alert Timer value that must be used in the MSC to inform the HLR about the call 2908 activities that the subscriber performs. Units are minutes.

2909 7.6.3.67

Call Termination Indicator

2910 This parameter indicates whether the MSC shall terminate a specific ongoing call, or all the call activities related to a 2911 specified subscriber.

2912 7.6.3.68

IST Information Withdraw

2913 This parameter indicates that IST information shall be deleted from the VMSC.

318

2914 7.6.3.69

319 Release 4 320 321

81

3GPP TS 29.002 V4.17.0 (2006-06)

IST Support Indicator

2915 This parameter indicates the degree of IST functionality supported by the MSC (Visited MSC or Gateway MSC). It can 2916 take one of the following values: 2917 2918 2919

Basic IST functionality; IST command service (in addition to the basic IST functionality and including the ability to terminate all calls being carried for the identified subscriber).

2920 7.6.3.70

Super-Charger Supported In HLR

2921 This parameter is used by the HLR to indicate support of the Super-Charger functionality and an indication of the age of 2922 the subscription data stored in the HLR.

2923 7.6.3.71

Super-Charger Supported In Serving Network Entity

2924 This parameter is used to indicate support of the Super-Charger functionality by the originating entity and to indicate 2925 either that subscription data is required or the date and time of the last know subscriber data modification.

2926 7.6.3.72

Age Indicator

2927 This parameter is used by the HLR to determine the validity of the subscription data retained by the serving network 2928 entity in a Super-Charged network.

2929 7.6.3.73

GPRS enhancements support indicator

2930 This parameter indicates to the HLR that the SGSN supports GPRS enhancements.

2931 7.6.3.74

Extensible QoS-Subscribed

2932 This parameter indicates the enhanced QoS subscribed for a certain service. It is defined in 3GPP TS 23.060. This 2933 parameter is an extension to QoS-Subscribed.

2934 7.6.3.75

SGSN Camel Subscription Info

2935 This parameter identifies the subscriber as having CAMEL services that are invoked in the SGSN.

2936 7.6.3.76

SMS-CSI

2937 This parameter identifies the subscriber as having SMS CAMEL services as defined in 3GPP TS 23.078.

2938 7.6.3.77

GPRS-CSI

2939 This parameter identifies the subscriber as having GPRS CAMEL services as defined in 3GPP TS 23.078.

2940 7.6.3.78

CAMEL subscription info

2941 This parameter indicates the CSI that can be controlled by CSE.

2942 7.6.3.79
SS-Code;

Extensible Call barring information for CSE

2943 This parameter contains for each call barring service for CSE: 2944 2945 2946

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

322

2947 2948 2949

323 Release 4 324 325

82

3GPP TS 29.002 V4.17.0 (2006-06)

password; wrong password attempt counter; notification-to-CSE flag.

2950 7.6.3.80
-

Extensible Forwarding information for CSE

2951 This parameter represents the information for CSE related to each call forwarding service: 2952 2953 2954 2955

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; notification-to-CSE flag.

2956 7.6.3.81

Modification Request for CSI

2957 This parameter indicates the CAMEL subscription information to be modified by CSE.

2958 7.6.3.82

Modification Request for SS Information

2959 This parameter indicates the call forwarding and call barring supplementary service data to be modified by CSE.

2960 7.6.3.83

Call Barring Data

2961 This parameter contains the extensible call barring feature list (see clause 7.6.3.21) and Notification to CSE flag.

2962 7.6.3.84

Call Forwarding Data

2963 This parameter contains the extensible call forwarding feature list (see clause 7.6.3.16) and Notification to CSE flag.

2964 7.6.3.85

ODB Data

2965 This parameter contains the ODB general data, ODB HPLMN specific data .

2966 7.6.3.86

Requested Subscription Info

2967 This parameter indicates the subscription information being requested.

2968 7.6.3.87

CS Allocation/Retention priority

2969 This parameter indicates the allocation/retention priority for Circuit Switched (CS). It corresponds to the 2970 allocation/retention priority that is defined in 3GPP TS 23.107.

2971 7.6.3.88

ODB Info

2972 This parameter contains the ODB data and Notification to CSE flag. 2973

2974 2975 7.6.4.1

7.6.4 Supplementary services parameters


SS-Code

2976 This parameter may refer to one supplementary service or a set of supplementary services as defined in 3GPP TS 2977 22.004. For this includes:

326

2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996

327 Release 4 328 329

83

3GPP TS 29.002 V4.17.0 (2006-06)

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 (see clause 7.6.4.44); (see clause 7.6.4.45);

Mobile Originating Location Request (MO-LR) Multicall (MC).

2997 7.6.4.2

SS-Status

2998 This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011.

2999 7.6.4.3
SS-Code

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

3000 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 3001 3002 3003 3004 3005

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

3006 7.6.4.4

Override Category

3007 This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the 3008 following two values: 3009 3010

Enabled; Disabled.

330

3011 7.6.4.5

331 Release 4 332 333

84

3GPP TS 29.002 V4.17.0 (2006-06)

CLI Restriction Option

3012 This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can 3013 take the following three values: 3014 3015 3016

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

3017 7.6.4.6

Forwarding Options

3018 This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following 3019 values: 3020 3021 3022 3023

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

(see 3GPP TS 22.082 [10] for the meaning of this parameter); (see 3GPP TS 22.082 [10] for the meaning of this parameter); (see 3GPP TS 22.082 [10] for the meaning of this parameter); (see 3GPP TS 22.082 [10] for the meaning of this parameter).

3024 7.6.4.7

No reply condition timer

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

3026 7.6.4.8 - 7.6.4.14 Void 3027 7.6.4.15


-

Forwarding information
(see clause 7.6.4.1); (see clause 7.6.4.16).

3028 This parameter represents the information related to each call forwarding service: 3029 3030 3031

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.

3032 7.6.4.16

Forwarding feature

3033 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 3034 following information, as required: 3035 3036 3037 3038 3039 3040 3041

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

(see clause 7.6.4.40); (see clause 7.6.4.2); (see clause 7.6.2.22); (see clause 7.6.2.23); (see clause 7.6.4.6); (see clause 7.6.4.7); (see clause 7.6.2.22A).

3042 If a number is required to define the forwarded-to destination then: 3043 3044

If the VLR supports Long Forwarded-to Numbers then the long forwarded-to number shall be present and the forwarded-to number shall be absent.

334

3045 3046

335 Release 4 336 337

85

3GPP TS 29.002 V4.17.0 (2006-06)

If the VLR does not support Long Forwarded-to Numbers then the forwarded-to number shall be present and the long forwarded-to number shall be absent.

3047 7.6.4.17 3048 7.6.4.18


SS-Code

Void Call barring information


(see clause 7.6.4.1); (see clause 7.6.4.19).

3049 This parameter contains for each call barring service: 3050 3051 3052

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

3053 7.6.4.19

Call barring feature

3054 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 3055 contains the following information: 3056 3057

Basic Service Group SS-Status

(see clause 7.6.4.40); (see clause 7.6.4.2).

3058 7.6.4.20

New password

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

3061 7.6.4.21

Current password

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

3063 7.6.4.22

Guidance information

3064 This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the 3065 following information may be given: 3066 3067 3068 3069 3070 3071

"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.

3072 7.6.4.23 3073 7.6.4.24


-

Void SS-Info

3074 This parameter refers to all the information related to a supplementary service and is a choice between: 3075 3076 3077

forwarding information call barring information CUG info

(see clause 7.6.4.15); (see clause 7.6.4.18); (see clause 7.6.4.8);

338

3078 3079

339 Release 4 340 341

86

3GPP TS 29.002 V4.17.0 (2006-06)

SS-Data eMLPP information

(see clause 7.6.4.3). (see clause 7.6.4.41).

3080 7.6.4.25 - 7.6.4.35 Void 3081 7.6.4.36 USSD Data Coding Scheme

3082 This parameter contains the information of the alphabet and the language used for the unstructured information in an 3083 Unstructured Supplementary Service Data operation. The coding of this parameter is according to the Cell Broadcast 3084 Data Coding Scheme as specified in 3GPP TS 23.038 [25].

3085 7.6.4.37

USSD String

3086 This parameter contains a string of unstructured information in an Unstructured Supplementary Service Data operation. 3087 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 3088 network as specified in 3GPP TS 22.090 [16].

3089 7.6.4.38

Bearer service

3090 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in 3GPP 3091 TS 22.002 [3]. This parameter is used only for supplementary service management.

3092 7.6.4.39

Teleservice

3093 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in 3GPP TS 22.003 3094 [4]. This parameter is used only for supplementary service management.

3095 7.6.4.40

Basic Service Group

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

3099 7.6.4.41

eMLPP information

3100 This parameter contains two parameters which are associated with the eMLPP service. The following two parameters 3101 are included: 3102 3103 3104 3105

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.

3106 7.6.4.42

SS-event

3107 This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It 3108 can indicate one of the following services: 3109 3110 3111 3112

Explicit Call Transfer (ECT) Call Deflection (CD) Multi-Party call (MPTY) Completion of Calls to Busy Subscriber (CCBS)

342

3113 7.6.4.43

343 Release 4 344 345

87

3GPP TS 29.002 V4.17.0 (2006-06)

SS-event data

3114 This parameter contains additional information related to Supplementary Service invocation. Depending on the service 3115 invoked it can contain the following information: 3116 3117

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

3118 7.6.4.44
-

LCS Privacy Exceptions

3119 Distinct SS codes are assigned to the following classes of LCS client in a target MS subscribers privacy exception list. 3120 3121 3122 3123

Universal Class; Call/session related value added class; Call/session unrelated value added class; PLMN operator class.

3124 7.6.4.45
-

Mobile Originating Location Request (MO-LR)

3125 Distinct SS codes are assigned to the following classes of MO-LR: 3126 3127 3128

Basic Self Location; Autonomous Self Location; Transfer to Third Party.

3129 7.6.4.46

NbrUser

3130 This parameter indicates the maximum number of parallel bearers that may be used as defined by the user at registration 3131 of the MC SS.

3132 7.6.4.47

MC Subscription Data

3133 This parameter contains two parameters which are associated with the MC service. The following two parameters are 3134 included:

3135
3136 3137

NbrUser: indicates the maximum number of parallel bearers that may be used as defined by the user at registration of the MC SS NbrSB: indicates the maximum number of parallel bearers that may be used as defined by the users subscription.

3138
3139

3140 7.6.4.48

MC Information

3141 This parameter contains three parameters which are associated with the MC service. The following parameters are 3142 included: 3143 3144 3145

NbrSB; NbrUser; NbrSN.

3146 Definitions of these parameters are provided in 3GPP TS 23.135.

346

3147 7.6.4.49
request; recall; active;

347 Release 4 348 349

88

3GPP TS 29.002 V4.17.0 (2006-06)

CCBS Request State

3148 This parameter indicates the current state of the CCBS request. It can take one of seven values: 3149 3150 3151 3152 3153 3154 3155

completed; suspended; frozen; deleted.

3156 3157 7.6.5.1

7.6.5 Call parameters


Call reference number

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

3159 7.6.5.2

Interrogation type

3160 This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can 3161 take either of two values: 3162 3163 3164

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.

3165 7.6.5.3

OR interrogation

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

3168 7.6.5.4

OR capability

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

3170 7.6.5.5
-

Forwarding reason

3171 This parameter indicates the reason for which the call is to be forwarded. It can take one of three values: 3172 3173 3174

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

3175 7.6.5.6

Forwarding interrogation required

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

3178 7.6.5.7

O-CSI

3179 This parameter identifies the subscriber as having originating CAMEL services as defined in 3GPP TS 23.078.

350

3180 7.6.5.7A

351 Release 4 352 353

89

3GPP TS 29.002 V4.17.0 (2006-06)

D-CSI

3181 This parameter identifies the subscriber as having originating CAMEL dialled services as defined in 3GPP TS 23.078.

3182 7.6.5.7B

T-CSI

3183 This parameter identifies the subscriber as having terminating CAMEL services in the GMSC, as defined in 3184 TS 3G 23.078.

3185 7.6.5.7C

VT-CSI

3186 This parameter identifies the subscriber as having terminating CAMEL services in the VMSC, as defined in 3GPP 3187 TS 23.078.

3188 7.6.5.8

Call Direction

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

3190 7.6.5.9

Channel Type

3191 This parameter is the result of a Channel Mode Modification for TS 61/62. It contains the changed Air Interface User 3192 Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is 3193 defined in 3GPP TS 48.008 [49].

3194 7.6.5.10

Chosen Channel

3195 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 3196 parameter is defined in 3GPP TS 48.008 [49].

3197 7.6.5.11

CCBS Feature

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

CCBS Index B-subscriber number B-subscriber subaddress Basic Service Group Code

(see 3GPP TS 23.093 for the use of this parameter); (see clause 7.6.2.48); (see clause 7.6.2.49); (see clause 7.6.4.40).

3205 7.6.5.12

UU Data

3206 This parameter includes User-To-User Data. It is defined in 3GPP TS 23.087.

3207 7.6.5.13

UUS CF Interaction

3208 This parameter indicates if the call forwarding or call deflection has been activated after UUS1 request has been 3209 accepted . It is defined in 3GPP TS 23.087.

3210 7.6.5.14

Number Portability Status

3211 This parameter indicates the number portability status of subscriber. See 3GPP TS 23.066 [108].

3212 7.6.5.15

Pre-paging supported

3213 This parameter indicates that the entity which sent it supports pre-paging.

354

3214

355 Release 4 356 357

90

3GPP TS 29.002 V4.17.0 (2006-06)

7.6.6 Radio parameters


Void

3215 7.6.6.1 - 7.6.6.4 3216 7.6.6.5

BSSMAP Service Handover

3217 This parameter refers to the Service Handover information element defined in 3GPP TS 48.008

3218 7.6.6.5A

BSSMAP Service Handover List

3219 This parameter refers to the list of Service Handover information elements defined in 3GPP TS 48.008. This parameter 3220 shall be used when there are multiple bearers and at least one of the bearers has an associated BSSMAP Service 3221 Handover parameter.

3222 7.6.6.6

RANAP Service Handover

3223 This parameter refers to the Service Handover information element defined in 3GPP TS 25.413.

3224 7.6.6.7

HO-Number Not Required

3225 This parameter indicates that no handover or relocation number allocation is necessary.

3226 7.6.6.8

Integrity Protection Information

3227 This parameter refers to the Integrity Protection Information element defined in 3GPP TS 25.413.

3228 7.6.6.9

Encryption Information

3229 This parameter refers to the Encryption Information element defined in 3GPP TS 25.413.

3230 7.6.6.10

Radio Resource Information

3231 This parameter refers to the Channel Type information element defined in 3GPP TS 48.008 [49].

3232 7.6.6.10A

Radio Resource List

3233 This parameter refers to list of RAB-id's and their associated Channel Type information elements defined in 3GPP TS 3234 48.008. This parameter shall be used when there are multiple bearers and at least one of the bearers has an associated 3235 Radio Resource Information parameter.

3236 7.6.6.10B

Chosen Radio Resource Information

3237 This parameter refers to the Chosen Channel and Speech Version information elements defined in 3GPP TS 48.008.

3238 7.6.6.11

Key Status

3239 This parameter refers to the Key Status element defined in 3GPP TS 25.413.

3240 7.6.6.12

Selected UMTS Algorithms

3241 This parameters identifies the UMTS integrity and optionally encryption algorithms selected by MSC-B. Coding of this 3242 parameter is defined in 3GPP TS 25.413.

3243 7.6.6.13

Allowed GSM Algorithms

3244 This parameters identifies the allowed GSM algorithms in MSC-B. Coding of this parameter is defined in 3GPP TS 3245 48.008.

358

3246 7.6.6.14

359 Release 4 360 361

91

3GPP TS 29.002 V4.17.0 (2006-06)

Allowed UMTS Algorithms

3247 This parameters identifies the allowed UMTS algorithms in MSC-B. Coding of this parameter is defined in 3GPP TS 3248 25.413.

3249 7.6.6.15

Selected GSM Algorithm

3250 This parameter identifies the GSM algorithm selected by GSM BSC controlled by MSC-B. Coding of this parameter is 3251 defined in 3GPP TS 48.008.

3252 3253 7.6.7.1

7.6.7 Authentication parameters


Authentication set list

3254 This parameter represents a list of sets of authentication parameters for a given subscriber. 3255 The list either contains Authentication Triplets (Rand, Sres, Kc) or Authentication Quintuplets (Rand, Xres, Ck, Ik, 3256 Autn). If the list contains Authentication Quintuplets, the order of sequence in this list is chronological, the first 3257 quintuplet in the list is the oldest one.

3258 7.6.7.2

Rand

3259 This parameter represents a random number used for authentication.

3260 7.6.7.3

Sres

3261 This parameter represents the response to an authentication request.

3262 7.6.7.4

Kc

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

3264 7.6.7.5

Xres

3265 This parameter represents the response to an UMTS authentication request.

3266 7.6.7.5A

Ck

3267 This parameter refers to a key used for UMTS ciphering purposes.

3268 7.6.7.5B

Ik

3269 This parameter refers to the Integrity Key.

3270 7.6.7.5C

Autn

3271 This parameter refers to the Authentication Token.

3272 7.6.7.6

Cksn

3273 This parameter refers to a ciphering key sequence number.

3274 7.6.7.6A

Ksi

3275 This parameter refers to a key set identifier.

3276 7.6.7.6B

Auts

362

3277 This parameter refers to the resynchronisation token.

363 Release 4 364 365

92

3GPP TS 29.002 V4.17.0 (2006-06)

3278 7.6.7.7
-

Ciphering mode

3279 This parameter refers to the ciphering mode which is associated with a radio channel. It may take values as follows: 3280 3281

no encryption; identification of specific ciphering algorithm.

3282 7.6.7.8

Current Security Context

3283 This parameter represents a list of security context parameters for a given subscriber. 3284 The list either contains GSM Security Context data (Kc, Cksn) or UMTS Security Context Data (Ck, Ik, Ksi).

3285 7.6.7.9
-

Failure cause

3286 This parameter refers to an authentication failure which has occurred. It may take values as follows: 3287 3288

wrong user response; wrong network signature.

3289 7.6.7.10

Re-attempt

3290 It indicates whether the failure ocurred in a normal authentication attempt or in an authentication reattempt (there was a 3291 previous unsuccessful authentication).

3292 7.6.7.11

Access Type

3293 It indicates whether the authentication procedure was initiated due to a call, an emergency call, a location updating, a 3294 supplementary service procedure, a short message transfer, a GPRS attach procedure, a routing area updating, a service 3295 request, a MS initiated Detach in GPRS, a PDP context activation or a PDP context deactivation procedure.

3296 3297 7.6.8.1

7.6.8 Short message parameters


SM-RP-DA

3298 This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be 3299 either of the following: 3300 3301 3302 3303 3304

IMSI LMSI MS-ISDN roaming number service centre address

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

3305 7.6.8.2

SM-RP-OA

3306 This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be 3307 either of the following: 3308 3309

MS-ISDN service centre address

(see clause 7.6.2.17); (see clause 7.6.2.27).

366

3310 7.6.8.3
3311 3312 3313 3314

367 Release 4 368 369

93

3GPP TS 29.002 V4.17.0 (2006-06)

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).

3315 7.6.8.4

SM-RP-UI

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

3317 7.6.8.5

SM-RP-PRI

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

3320 7.6.8.6
-

SM Delivery Outcome

3321 This parameter indicates the cause for setting the message waiting data. It can take one of the following values: 3322 3323 3324

Absent subscriber; MS memory capacity exceeded; Successful transfer.

3325 7.6.8.7

More Messages To Send

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

3327 7.6.8.8
-

Alert Reason

3328 This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values: 3329 3330

MS present; Memory Available.

3331 7.6.8.9

Absent Subscriber Diagnostic SM

3332 This parameter is used to indicate the reason why the subscriber is absent. For the values for this parameter see 3GPP 3333 TS 23.140.

3334 7.6.8.10

Alert Reason Indicator

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

3336 7.6.8.11

Additional SM Delivery Outcome

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

3339 7.6.8.12

Additional Absent Subscriber Diagnostic SM

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

3341 7.6.8.13

Delivery Outcome Indicator

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

370

3343 7.6.8.14

371 Release 4 372 373

94

3GPP TS 29.002 V4.17.0 (2006-06)

GPRS Node Indicator

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

3345 7.6.8.15

GPRS Support Indicator

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

3348 7.6.8.16

SM-RP-MTI

3349 This parameter represents the RP-Message Type Indicator of the Short Message. It is used to distinguish a SM sent to 3350 the mobile station in order to acknowledge an MO-SM initiated by the mobile from a normal MT-SM. This parameter is 3351 formatted according to the formatting rules of address fields as described in 3GPP TS 23.140.

3352 7.6.8.17

SM-RP-SMEA

3353 This parameter represents the RP-Originating SME-address of the Short Message Entity that has originated the SM. 3354 This parameter is used by the short message service relay sub-layer protocol and is formatted according to the 3355 formatting rules of address fields as described in 3GPP TS 23.140.

3356 3357 7.6.9.1


3358 3359 3360 3361

7.6.9 Access and signalling system related parameters


AN-apdu

This parameter includes one or two concatenated complete 3GPP TS 25.413 or 3GPP TS 48.006 [48] messages, as described in 3GPP TS 23.009 and 3GPP TS 29.010. The access network protocol ID indicates that the message or messages are according to either 3GPP TS 48.006 [48] or 3GPP TS 25.413. For the coding of the messages see 3GPP TS 25.413, 3GPP TS 48.006 [48] and 3GPP TS 48.008 [49].

3362 7.6.9.2
-

CM service type

3363 This parameter identifies the service category being requested by the subscriber: 3364 3365 3366 3367 3368 3369 3370 3371

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

3372 7.6.9.3
-

Access connection status

3373 This parameter represents the following access connection status information: 3374 3375 3376

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

3377 7.6.9.4

External Signal Information

374

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

375 Release 4 376 377

95

3GPP TS 29.002 V4.17.0 (2006-06)

3381 7.6.9.5

Access signalling information

3382 This parameter refers to any set of information elements imported from 3GPP TS 24.008 [35].

3383 7.6.9.6

Location update type

3384 This parameter refers to the location update type (normal, periodic or IMSI attach) contained in the 3GPP TS 24.008 3385 [35] LOCATION REGISTRATION REQUEST message.

3386 7.6.9.7

Protocol ID

3387 This parameter refers to the protocol to which the coding of the content of the associated External Signal Information 3388 conforms. 3389 The following values are defined: 3390 3391 3392

04.08; 08.06; ETS 300 102-1.

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

3394 7.6.9.8

Network signal information

3395 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1". 3396 The network signal information may include the following information elements as defined in 3GPP TS 29.007 [56]: 3397 3398 3399 3400 3401 3402

ISDN BC; the tag and length are defined by ETS 300 102-1. For the content, see 3GPP TS 29.007 [56].

HLC; the tag and length are defined by ETS 300 102-1. For the content, see 3GPP TS 29.007 [56].

LLC; the tag and length are defined by ETS 300 102-1. For the content, see 3GPP TS 29.007 [56].

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

378

379 Release 4 380 381

96

3GPP TS 29.002 V4.17.0 (2006-06)

IS D N B C T A G LEN G TH C O N TEN T H LC TAG LEN G TH C O N TEN T LLC TAG LEN G TH C O N TEN T

3404
3405

Figure 7.6/1: Network signal information parameter

3406 7.6.9.9

Call Info

3407 This parameter is transported as external signal information. The protocol ID shall be set to "3GPP TS 24.008 [35]". 3408 The Call Info includes the set of information elements from the original SETUP message and is imported from 3GPP 3409 TS 24.008 [35].

3410 7.6.9.10

Additional signal info

3411 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 356". 3412 The additional signal information may include the following information elements: 3413 3414

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

3415 They are contained in the Signal Information parameter according to figure 7.6/2 (irrespective of the order):
CALLING PARTY NUMBER TAG

LENGTH CONTENT
GENERIC NUMBER TAG

3416
3417

LENGTH CONTENT
Figure 7.6/2: Additional signal information parameter

3418 3419 7.6.10.1


-

7.6.10 System operations parameters


Network resources

3420 This parameter refers to a class or type of network resource: 3421

PLMN;

382

3422 3423 3424 3425 3426

383 Release 4 384 385

97

3GPP TS 29.002 V4.17.0 (2006-06)

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

3427 7.6.10.2

Trace reference

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

3429 7.6.10.3

Trace type

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

3431 3432 7.6.11.1

7.6.11 Location Service Parameters


Age of Location Estimate

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

3434 7.6.11.2

Deferred MT-LR Response Indicator

3435 This parameter shows that this is a response to a deferred mt-lr request.

3436 7.6.11.3
3437 3438 3439 3440 3441 3442 3443 3444

Deferred MT-LR Data

This parameter is used to report the deferred location event type, the location information and reason why the serving node aborted monitoring the event to the GMLC. The termination cause mt-lrRestart shall be used to trigger the GMLC to restart the location procedure in all the cases where the sending node detects that the location procedure cannot be successfully performed anymore by the sending node and that it could be successfully performed by another node (as for example when. Cancel Location or Send Identification has been received). The location information shall be included only if the termination cause is mt-lrRestart. The network node number contained in the location information refers to the node where the MS/UE has moved to and shall be included if available, like in case Send Identification has been received.

3445 7.6.11.4

LCS Client ID

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

3447 7.6.11.5
3449 7.6.11.6

LCS Event

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

Void

3450 7.6.11.7

LCS Priority

3451 This parameter gives the priority of the location request.

3452 7.6.11.8

LCS QoS

3453 This parameter defines the Quality of Service (QoS) for any location request. It is composed of the following elements. 3454 3455

1) Response Time Indicates the category of response time low delay or delay tolerant.

386

3456 3457 3458 3459 3460 3461

387 Release 4 388 389

98

3GPP TS 29.002 V4.17.0 (2006-06)

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).

3462 7.6.11.9 3463 7.6.11.10 3464 7.6.11.11


3465 3466 3467 3468 3469 3470 3471 3472 3473

Void Void Location Estimate

This parameter gives an estimate of the location of an MS in universal coordinates and the accuracy of the estimate. The estimate is expressed in terms of the geographical shapes defined by 3GPP TS 23.032. and is composed of the type of shape plus the encoding of the shape itself. Any type of shape defined in 3GPP TS 23.032 can be filled in in the Location Estimate parameter, but only the encoding of the following shapes shall be carried by Location Estimate: - Ellipsoid point with uncertainty circle - Ellipsoid point with uncertainty ellipse - Ellipsoid point with altitude and uncertainty ellipsoid - Ellipsoid arc - Ellipsoid point

3474 The encoding for the remaining types of shape, defined in the 3GPP TS 23.032, shall be filled in in the Additional 3475 Location Estimate parameter. 3476

3477 7.6.11.12

Location Type

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

3480 3481 3482 3483

current location; current or last known location; initial location for an emergency services call; deferred location event type.

3484 7.6.11.13

NA-ESRD

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

3487 7.6.11.14

NA-ESRK

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

3490 7.6.11.15

Void

390

3491 7.6.11.16

391 Release 4 392 393

99

3GPP TS 29.002 V4.17.0 (2006-06)

Privacy Override

3492 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC/SGSN for an MT3493 LR are in the same country.

3494 7.6.11.17

Supported LCS Capability Sets

3495 This parameter indicates which capability sets of LCS are supported in the VLR or SGSN.

3496 7.6.11.18

Void

3497 7.6.11.19 NA-ESRK Request


3498 This parameter allows the MSC to indicate that it requires the GMLC to allocate a NA-ESRK based on the target MS 3499 location estimate. This parameter only applies to emergency services calls in North America.

3500 3501 7.6.11.20 Supported GAD Shapes

3502 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. If the parameter is not provided 3503 then the receiving node shall assume that the sending entity supports the following shapes: 3504 3505 3506 3507 3508

- Ellipsoid point with uncertainty circle - Ellipsoid point with uncertainty ellipse - Ellipsoid point with altitude and uncertainty ellipsoid - Ellipsoid arc - Ellipsoid point

3509 7.6.11.21

Additional Location Estimate

3510 This parameter gives an estimate of the location of an MS/UE in universal coordinates and the accuracy of the estimate. 3511 This parameter allows the location estimate to be expressed in any of the geographical shapes defined in 3GPP TS 3512 23.032

3513 7.6.11.22

LCS-Reference Number

3514 This parameter represents a reference between a request and a responce of a deferred mt-lr procedure as deccribed in 3515 3GPP TS 23.271 [26a]. 3516

3517
3518

7.6.12 void

3519 3520

7.7 Representation of a list of a basic parameter in serviceprimitives

3521 In some service-primitives several instances of a basic parameter of clause 7.6 are required. In the service descriptions 3522 such cases will be represented as 3523

ParameterNameLIST

394

3524 in the tables where ParameterName refers to one of the parameters defined in clause 7.6. This corresponds to the 3525 following construction rule:

395 Release 4 396 397

100

3GPP TS 29.002 V4.17.0 (2006-06)

3526
3527

P a ra m e te r
Figure 7.7/1: Construction of Lists

3528 3529 3530

8 Mobility services
8.1 Location management services
8.1.1 Void
Void Void Void

3531 8.1.1.1 3532 8.1.1.2 3533 8.1.1.3 3534 3535 8.1.2.1

8.1.2 MAP_UPDATE_LOCATION service


Definition

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

3538 8.1.2.2
3539

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 IST Support Indicator Super-Charger Supported in Serving Network Entity Long FTN Supported Supported LCS Capability Sets Inform Previous Network Entity HLR number User error Provider error

Request M M M M U C C C C C C C

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

Response M(=)

Confirm M(=)

C C

C(=) C(=) O

3540

3541 8.1.2.3
3542 Invoke Id

Parameter definitions and use

398

3543 See definition in clause 7.6.1. 3544 IMSI 3545 See definition in clause 7.6.2. 3546 MSC Address 3547 See definition for MSC number in clause 7.6.2. The MSC address is used for short message delivery only and for each 3548 incoming call set-up attempt the MSRN will be requested from the VLR. 3549 VLR number 3550 See definition in clause 7.6.2. 3551 LMSI 3552 See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR 3553 to support the LMSI handling procedures. 3554 Supported CAMEL Phases 3555 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 3556 phase 1 is supported. Otherwise may be absent. 3557 HLR number 3558 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3559 SoLSA Support Indicator 3560 3561 3562 3563

399 Release 4 400 401

101

3GPP TS 29.002 V4.17.0 (2006-06)

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.

3564 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 3565 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 3566 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 3567 IST Support Indicator 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578

This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Update Location indication and the Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of not having the basic IST mechanism available. This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Update Location indication and the HLR supports the IST Command capability, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of not having the IST Command mechanism available.

3579 Long FTN Supported 3580 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 3581 Super-Charger Supported in Serving Network Entity 3582 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 3583 whether subscription data has been retained by the VLR. If subscription data has been retained by the VLR the age 3584 indicator shall be included. Otherwise the VLR shall indicate that subscriber data is required. 3585 If this parameter is absent then the VLR does not support the Super-Charger functionality.

402

3586 Supported LCS Capability Sets 3587 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 3588 capability set is marked as supported then the VLR does not support LCS at all. 3589 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 3590 version. 3591 Inform Previous Network Entity

403 Release 4 404 405

102

3GPP TS 29.002 V4.17.0 (2006-06)

3592 3593 3594 3595

This parameter is used by the VLR to ask the HLR to inform the previous network entity about the update by sending the previous network entity a Cancel Location message. It is used in case Super-Charger is supported in the network and the serving network entity has not been able to inform the previous network entity that MS has moved, that is if it has not sent Send Identification to the previous serving entity.

3596 User error 3597 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3598 clause 7.6.1 may be used, depending on the nature of the fault: 3599 3600 3601 3602 3603 3604 3605 3606

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.

3607 Provider error 3608 For definition of provider errors see clause 7.6.1.

3609 3610 8.1.3.1

8.1.3 MAP_CANCEL_LOCATION service


Definition

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

3618 8.1.3.2
3619

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

3620

406

3621 8.1.3.3

407 Release 4 408 409

103

3GPP TS 29.002 V4.17.0 (2006-06)

Parameter definitions and use

3622 Invoke Id 3623 See definition in clause 7.6.1. 3624 IMSI 3625 See definition in clause 7.6.2. 3626 LMSI 3627 See definition in clause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable 3628 between SGSN and HLR. 3629 Value 0000 0000 can be used to indicate that the LMSI is not in use. 3630 Cancellation Type 3631 See definition in clause 7.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the 3632 SGSN. If the VLR receives this parameter and do not understand it the VLR shall ignore it. 3633 User error 3634 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. One of the following error causes 3635 defined in clause 7.6.1 shall be used: 3636 3637

unexpected data value; data missing.

3638 Provider error 3639 For definition of provider errors see clause 7.6.1.

3640 3641 8.1.4.1

8.1.4 MAP_SEND_IDENTIFICATION service


Definition

3642 The MAP_SEND_IDENTIFICATION service is used between a VLR and a previous VLR to retrieve IMSI and 3643 authentication data for a subscriber registering afresh in that VLR. 3644 The MAP_SEND_IDENTIFICATION service is a confirmed service using the service primitives defined in table 8.1/4.

3645 8.1.4.2
3646

Service primitives
Table 8.1/4: MAP_SEND_IDENTIFICATION

Parameter name Invoke Id TMSI Number of requested vectors Segmentation prohibited indicator IMSI Authentication set Current Security Context User error Provider error

Request M M M C

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

Response M(=)

Confirm M(=)

C U U C

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

3647

3648 8.1.4.3
3649 Invoke Id

Parameter definitions and use

410

3650 See definition in clause 7.6.1. 3651 TMSI 3652 See definition in clause 7.6.2. 3653 If multiple service requests are present in a dialogue then this parameter shall be present in every service request. 3654 Number of requested vectors 3655 A number indicating how many authentication vectors the new VLR is prepared to receive. The previous VLR shall not 3656 return more vectors than indicated by this parameter. 3657 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 3658 dialogue then this parameter shall not be present in any service request other than the first one 3659 Segmentation prohibited indicator 3660 This parameter indicates if the new VLR or SGSN allows segmentation of the response at MAP user level. 3661 This parameter may be present only in the first request of the dialogue. 3662 IMSI 3663 See definition in clause 7.6.2. The IMSI is to be returned if the service succeeds. 3664 If multiple service requests are present in a dialogue and the service succeeds then this parameter shall not be present in 3665 any service response other than the first one. 3666 Authentication set 3667 See definition in clause 7.6.7. If the service succeeds a list of up to five authentication sets is returned, if there are any 3668 available. 3669 Current Security Context 3670 See definition in clause 7.6.7. If the service succeeds, a list of either GSM or UMTS Security Context parameters can be 3671 returned. 3672 User error 3673 This parameter is mandatory if the service fails. The following error cause defined in clause 7.6.1 may be used, 3674 depending on the nature of the fault: 3675

411 Release 4 412 413

104

3GPP TS 29.002 V4.17.0 (2006-06)

unidentified subscriber.

3676 Provider error 3677 For definition of provider errors see clause 7.6.1.

3678 3679 8.1.5.1 3680 8.1.5.2 3681 8.1.5.3 3682 3683 8.1.6.1

8.1.5 Void
Void Void Void

8.1.6 MAP_PURGE_MS service


Definition

414

3684 3685 3686 3687 3688 3689 3690 3691 3692 3693

415 Release 4 416 417

105

3GPP TS 29.002 V4.17.0 (2006-06)

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. This service shall not be used if both the VLR and HLR support the Super-Charger functionality. 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. This service shall not be used if both the SGSN and HLR support the Super-Charger functionality.

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

3695 8.1.6.2
3696

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(=)

Response M(=) C C C

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

3697

3698 8.1.6.3
3699 Invoke ID

Parameter definitions and use

3700 See definition in clause 7.6.1. 3701 IMSI 3702 See definition in clause 7.6.2. 3703 VLR number 3704 Shall be present if the sender is VLR. See definition in clause 7.6.2. 3705 SGSN number 3706 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 3707 Freeze TMSI 3708 This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR 3709 number matches the stored VLR number. 3710 Freeze P-TMSI 3711 This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received 3712 SGSN number matches the stored SGSN number. 3713 User error 3714 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 3715 3716

Data Missing; Unexpected Data Value;

418

3717

419 Release 4 420 421

106

3GPP TS 29.002 V4.17.0 (2006-06)

Unknown Subscriber.

3718 Provider error 3719 See definition of provider errors in clause 7.6.1.

3720 3721 8.1.7.1

8.1.7 MAP_UPDATE_GPRS_LOCATION service


Definition

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

3725 8.1.7.2
3726

Service primitives
Table 8.1/7: MAP_UPDATE_GPRS_LOCATION

Parameter name Invoke Id IMSI SGSN number SGSN address Supported CAMEL Phases SoLSA Support Indicator Super-Charger Supported in Serving Network Entity GPRS enhancements support indicator Supported LCS Capability Sets Inform Previous Network Entity HLR number User error Provider error

Request M M M M C C C C C C

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

Response M(=)

Confirm M(=)

C C

C(=) C(=) O

3727

3728 8.1.7.3
3729 Invoke Id

Parameter definitions and use

3730 See definition in clause 7.6.1. 3731 IMSI 3732 See definition in clause 7.6.2. 3733 SGSN number 3734 See definition in clause 7.6.2. 3735 SGSN address 3736 See definition in clause 7.6.2. 3737 Supported CAMEL Phases 3738 This parameter indicates which phases of CAMEL are supported. The SGSN can only support CAMEL phase 3 or 3739 greater. 3740 SoLSA Support Indicator 3741 This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that SoLSA is 3742 supported. If this parameter is not included in the Update GPRS Location indication and the Subscriber is marked as

422

3743 only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the SGSN that roaming 3744 is not allowed to that Subscriber in the SGSN. 3745 This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a 3746 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support 3747 indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted. 3748 Super-Charger Supported in Serving Network Entity 3749 This parameter is used by the SGSN to indicate to the HLR that the SGSN supports the Super-Charger functionality and 3750 whether subscription data has been retained by the SGSN. If subscription data has been retained by the SGSN the age 3751 indicator shall be included. Otherwise the SGSN shall indicate that subscriber data is required. 3752 If this parameter is absent then the SGSN does not support the Super-Charger functionality. 3753 GPRS enhancements support indicator 3754 This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that GPRS 3755 enhancements are supported. If this parameter is included in the Update GPRS Location indication the HLR may send 3756 the extensible QoS in the PDP contexts to the SGSN. 3757 HLR number 3758 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3759 Supported LCS Capability Sets 3760 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 3761 capability set is marked as supported then the SGSN does not support LCS at all. 3762 The SGSN is not allowed to indicate support for LCS capability set 1. 3763 If this parameter is absent then the SGSN does not support LCS at all. 3764 Inform Previous Network Entity

423 Release 4 424 425

107

3GPP TS 29.002 V4.17.0 (2006-06)

3765 3766 3767 3768

This parameter is used by the SGSN to ask the HLR to inform the previous network entity about the update by sending the previous network entity a Cancel Location message. It is used in case Super-Charger is supported in the network and the serving network entity has not been able to inform the previous network entity that MS has moved, that is if it has not sent SGSN Context Request to the previous serving entity.

3769 User error 3770 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3771 clause 7.6.1 may be used, depending on the nature of the fault: 3772 3773 3774 3775 3776 3777 3778 3779

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.

3780 Provider error 3781 For definition of provider errors see clause 7.6.1.

3782

8.1.8 MAP-NOTE-MM-EVENT

426

3783 8.1.8.1

427 Release 4 428 429

108

3GPP TS 29.002 V4.17.0 (2006-06)

Definition

3784 This service is used between the VLR and the gsmSCF when for a subscriber a mobility management event has been 3785 processed successfully, that subscriber is provisioned with M-CSI and the relevant mobility management event is 3786 marked for reporting.

3787 8.1.8.2

Service primitives

3788 The service primitives are shown in table 8.1/8. 3789

Table 8.1/8: MAP_NOTE_MM_EVENT parameters


Parameter name Invoke id Event Met Service Key IMSI Basic MSISDN Location Information LSA Identity Supported CAMEL Phases User error Provider error Request M M M M M C C M Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) M(=) Response M(=) Confirm M(=)

C(=) O

3790

3791 8.1.8.3

Parameter use

3792 Event Met 3793 This parameter indicates the mobility management event that has lead to the notification. It shall have one of the 3794 following values: 3795 3796 3797 3798 3799

Location update in the same VLR service area; Location update to another VLR service area; IMSI attach; MS initiated IMSI detach (explicit detach); Network initiated IMSI detach (implicit detach).

3800 Service Key 3801 See clause 7.6.x. 3802 IMSI 3803 See clause 7.6.x. 3804 Basic MSISDN 3805 See clause 7.6.x. 3806 Location Information 3807 See clause 7.6.x. This information shall be sent, if available. 3808 LSA Identity 3809 See clause 7.6.x. This information shall be sent, if available. 3810 Supported CAMEL Phases 3811 See clause 7.6.x. This information shall always be sent.

430

3812 User error

431 Release 4 432 433

109

3GPP TS 29.002 V4.17.0 (2006-06)

3813 This parameter is sent by the receiving entity when an error is detected. It shall have one of the following values: 3814 3815 3816 3817

Data Missing; Unexpected Data Value; Unknown Subscriber; MM-EventNotSupported.

3818 Provider error 3819 This is defined in clause 7.6.1.

3820 3821 3822 8.2.1.1

8.2 Paging and search


8.2.1 MAP_PAGE service
Definition

3823 This service is used between VLR and MSC to initiate paging of an MS for mobile terminated call set-up, mobile 3824 terminated short message or unstructured SS notification. 3825 The MAP_PAGE service is a confirmed service using the primitives from table 8.2/1.

3826 8.2.1.2
3827

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

3828

3829 8.2.1.3
3830 Invoke Id

Parameter definitions and use

3831 See definition in clause 7.6.1. 3832 IMSI 3833 See definition in clause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging on 3834 the radio path uses the IMSI as an identifier. 3835 Stored location area Id 3836 See definition in clause 7.6.2. 3837 TMSI 3838 See definition in clause 7.6.2. The TMSI is included if paging on the radio channel is to use the TMSI as an identifier. 3839 User error 3840 The following error causes defined in clause 7.6.1 may be sent by the user in case of a paging error, depending on the 3841 failure reason:

434

3842 3843 3844 3845 3846 3847 3848

435 Release 4 436 437

110

3GPP TS 29.002 V4.17.0 (2006-06)

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.

3849 Provider error 3850 See definition in clause 7.6.1.

3851 3852 8.2.2.1

8.2.2 MAP_SEARCH_FOR_MS service


Definition

3853 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 3854 the VLR does not hold location area information confirmed by radio contact. 3855 The MAP_SEARCH_FOR_MS service is a confirmed service using the primitives from table 8.2/2.

3856 8.2.2.2
3857

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

3858

3859 8.2.2.3
3860 Invoke Id

Parameter definitions and use

3861 See definition in clause 7.6.1. 3862 IMSI 3863 See definition in clause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path. 3864 Current location area Id 3865 See definition in clause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the 3866 Location Area Id of the area in which the MS responded is given in the response. 3867 User error 3868 The following error causes defined in clause 7.6.1 shall be sent by the user if the search procedure fails, depending on 3869 the failure reason: 3870 3871 3872

absent subscriber; this error cause is returned by the MSC if the MS does not respond to the paging request;

system failure;

438

3873 3874 3875 3876

439 Release 4 440 441

111

3GPP TS 29.002 V4.17.0 (2006-06)

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.

3877 Provider error 3878 See definition in clause 7.6.1.

3879 3880 3881 8.3.1.1

8.3 Access management services


8.3.1 MAP_PROCESS_ACCESS_REQUEST service
Definition

3882 This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. in case of 3883 mobile originated call set-up or after being paged by the network. 3884 The MAP_PROCESS_ACCESS_REQUEST service is a confirmed service using the primitives from table 8.3/1.

3885 8.3.1.2
3886

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

3887

3888 8.3.1.3
3889 Invoke Id

Parameter definitions and use

3890 See definition in clause 7.6.1. 3891 CM service type 3892 See definition in clause 7.6.9. 3893 Access connection status 3894 See definition in clause 7.6.9. 3895 Current Location Area Id 3896 See definition in clause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure. 3897 Serving cell Id 3898 See definition in clause 7.6.2.

442

3899 TMSI

443 Release 4 444 445

112

3GPP TS 29.002 V4.17.0 (2006-06)

3900 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 3901 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 3902 Cksn 3903 See definition in clause 7.6.7. In case of access with TMSI, the Cksn shall be present. 3904 IMSI 3905 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 3906 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 3907 In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM 3908 Service Type "Emergency Call Establishment", IMEI may replace IMSI. 3909 IMEI 3910 See definition in clause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the 3911 Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment". 3912 MSISDN 3913 See definition in clause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator 3914 option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding. 3915 User error 3916 One of the following error causes defined in clause 7.6.1 shall be sent by the user if the access request fails, depending 3917 on the failure reason: 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929

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.

3930 Provider error 3931 For definition of provider errors see clause 7.6.1.

3932

8.4 Handover services

3933 It should be noted that the handover services used on the B-interface have not been updated for Release 99. The B3934 interface is not fully operational specified. It is strongly recommended not to implement the B-interface as an external 3935 interface.

3936

8.4.1 MAP_PREPARE_HANDOVER service

446

3937 8.4.1.1

447 Release 4 448 449

113

3GPP TS 29.002 V4.17.0 (2006-06)

Definition

3938 This service is used between MSC-A and MSC-B (E-interface) when a call is to be handed over or relocated from 3939 MSC-A to MSC-B. 3940 The MAP_PREPARE_HANDOVER service is a confirmed service using the primitives from table 8.4/1.

3941 8.4.1.2
3942

Service primitives
Table 8.4/1: MAP_PREPARE_HANDOVER
Parameter name Invoke Id Target Cell Id Target RNC Id HO-NumberNotRequired IMSI Integrity Protection Information Encryption Information Radio Resource Information AN-APDU Allowed GSM Algorithms Allowed UMTS Algorithms Radio Resource List RAB ID BSSMAP Service Handover BSSMAP Service Handover List RANAP Service Handover ASCI Call Reference Handover Number Relocation Number List Multicall Bearer Information Multiple Bearer Requested Multiple Bearer Not Supported Selected UMTS Algorithms Chosen Radio Resource Information User error Provider error Request M C C C C 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(=) C(=) C(=) C(=) C(=) C C C C C(=) C C C C C(=) C(=) C(=) C(=) O C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=)

3943

3944 8.4.1.3
3945 Invoke Id

Parameter use

3946 For definition of this parameter see clause 7.6.1. 3947 Target Cell Id 3948 For definition of this parameter see clause 7.6.2. This parameter is only included if the service is not in an ongoing 3949 transaction. This parameter shall also be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure 3950 or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009. 3951 Target RNC Id 3952 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter3953 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 3954 23.009. 3955 HO-Number Not Required 3956 For definition of this parameter see clause 7.6.6.

450

3957 IMSI

451 Release 4 452 453

114

3GPP TS 29.002 V4.17.0 (2006-06)

3958 For definition of this parameter see clause 7.6.2. This UMTS parameter shall be included if:

3959 3960 3961

available and if the access network protocol is BSSAP and there is an indication that the MS also supports UMTS.

3962 Integrity Protection Information 3963 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 3964 network protocol is BSSAP. 3965 Encryption Information 3966 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 3967 network protocol is BSSAP. 3968 Radio Resource Information 3969 For definition of this parameter see clause 7.6.6. This GSM parameter shall be included if the access network protocol 3970 is RANAP and there is an indication that the UE also supports GSM. If the parameter Radio Resource List is sent , the 3971 parameter Radio Resource Information shall not be sent. 3972 AN-APDU 3973 For definition of this parameter see clause 7.6.9. 3974 Allowed GSM Algorithms 3975 For definition of this parameter see clause 7.6.6. This parameters includes allowed GSM algorithms. This GSM 3976 parameter shall be included if:

3977 3978 3979

the service is a part of the Inter-MSC SRNS Relocation procedure and Ciphering or Security Mode Setting procedure has been performed.and there is an indication that the UE also supports GSM.

3980 Allowed UMTS Algorithms 3981 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if all of the following 3982 conditions apply:

3983 3984

access network protocol is BSSAP and Integrity Protection Information and Encryption Information are not available and

3985 Ciphering or Security Mode Setting procedure has been performed. 3986 Radio Resource List 3987 3988 3989 3990

For definition of this parameter see clause 7.6.6. This parameter shall be included if the access network protocol is RANAP and there is an indication that the UE also supports GSM. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter Radio Resource Information is sent , the parameter Radio Resource List shall not be sent.

3991 RAB ID 3992 For definition of this parameter see subclause 7.6.2. This parameter shall be included when MSC-A supports multiple 3993 bearers and access network protocol is BSSAP and the RAB ID has a value other than 1. 3994 BSSMAP Service Handover

454

3995 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 3996 RANAP. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not 3997 be sent. 3998 BSSMAP Service Handover List 3999 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4000 RANAP. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter BSSMAP 4001 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4002 RANAP Service Handover 4003 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4004 BSSAP. 4005 ASCI Call Reference 4006 This parameter contains either the broadcast call reference or group call reference. It shall be included if a subscriber is 4007 undergoing handover during a VGCS or VBS call, where MSC-B already has a Bearer established, so that MSC-B can 4008 determine the Group or Broadcast Call to which it shall attach the subscriber, see 3GPP TS 48.008 [49]. 4009 4010 Handover Number 4011 For definition of this parameter see clause 7.6.2. This parameter shall be returned at handover, unless the parameter 4012 HO-NumberNotRequired is sent. If the parameter Handover Number is returned, the parameter Relocation Number List 4013 shall not be returned. 4014 Relocation Number List 4015 For definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation, unless the parameter 4016 HO-NumberNotRequired is sent. If the parameter Relocation Number List is returned, the parameter Handover Number 4017 shall not be returned. 4018 Multicall Bearer Information 4019 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation in the case that MSC-B 4020 supports multiple bearers. 4021 4022 Multiple Bearer Requested 4023 For a definition of this parameter see clause 7.6.2. This parameter shall be sent when MSC-A requests multiple bearers 4024 to MSC-B. 4025 Multiple Bearer Not Supported 4026 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation when MSC-B receives 4027 Multiple Bearer Requested parameter and MSC-B does not support multiple bearers. 4028 Selected UMTS Algorithms 4029 For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally 4030 encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the 4031 service is a part of the inter MSC inter system handover from GSM to UMTS. 4032 Chosen Radio Resource Information 4033 For definition of this parameter see clause 7.6.6. This parameter shall be returned at relocation if the encapsulated PDU 4034 is RANAP RAB Assignment Response and MS is in GSM access.

455 Release 4 456 457

115

3GPP TS 29.002 V4.17.0 (2006-06)

458

4035 User error

459 Release 4 460 461

116

3GPP TS 29.002 V4.17.0 (2006-06)

4036 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4037 on the nature of the fault: 4038 4039 4040 4041 4042

No handover number available. Target cell outside group call area; System failure. Unexpected data value. Data Missing.

4043 Provider error 4044 See definition of provider errors in clause 7.6.1.

4045 4046 8.4.2.1

8.4.2 MAP_SEND_END_SIGNAL service


Definition

4047 This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by 4048 MSC-B to the MS. MSC-A retains then the main control of the call until it clears. 4049 The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either 4050 because the call has been released in MSC-A or because the call has been successfully handed over or relocated from 4051 MSC-B to another MSC. 4052 The MAP_SEND_END_SIGNAL service is a confirmed service using the primitives from table 8.4/2.

4053 8.4.2.2
4054

Service primitives
Table 8.4/2: MAP_SEND_END_SIGNAL
Parameter name Invoke Id AN-APDU Provider error Request M M Indication M(=) M(=) Response M(=) Confirm M(=) O

4055

4056 8.4.2.3
4057 Invoke Id

Parameter use

4058 For definition of this parameter see clause 7.6.1. 4059 AN-APDU 4060 For definition of this parameter see clause 7.6.9. 4061 Provider error 4062 For definition of this parameter see clause 7.6.1.

4063 4064 8.4.3.1

8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service


Definition

4065 This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A-interface or Iu4066 interface in MSC-B to MSC-A.

462

4067 The MAP_PROCESS_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4068 table 8.4/3.

463 Release 4 464 465

117

3GPP TS 29.002 V4.17.0 (2006-06)

4069 8.4.3.2
4070

Service primitives
Table 8.4/3: MAP_PROCESS_ACCESS_SIGNALLING
Parameter name Invoke Id AN-APDU Selected GSM Algorithm Selected UMTS Algorithms Chosen Radio Resource Information Selected RAB id Request M M C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=)

4071

4072 8.4.3.3
4073 Invoke Id

Parameter use

4074 For definition of this parameter see clause 7.6.1. 4075 AN-APDU 4076 For definition of this parameter see clause 7.6.9. 4077 Selected GSM algorithm 4078 For definition of this parameter see clause 7.6.6. This parameter shall be present if the encapsulated PDU is Security 4079 Mode Complete and MS is in GSM access. 4080 Selected UMTS Algorithms 4081 4082 4083 4084

For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the encapsulated PDU is BSSMAP Cipher Mode Complete and the MS is in UMTS, or an interystem handover to UMTS is performed in MSC-B, or in the case of intra MSC-B intra UMTS relocation.

4085 Chosen Radio Resource Information 4086 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4087 Assignment Response and MS is in GSM access. 4088 Selected RAB ID 4089 The selected radio access bearer that was kept at subsequent intra-MSC handover from UMTS to GSM after multiple 4090 bearers were used.

4091 4092 8.4.4.1

8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service


Definition

4093 This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface 4094 or Iu-interface of MSC-B. 4095 The MAP_FORWARD_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4096 table 8.4/4.

4097 8.4.4.2
4098

Service primitives
Table 8.4/4: MAP_FORWARD_ACCESS_SIGNALLING

466

467 Release 4 468 469

118 Parameter name Invoke Id Integrity Protection Information Encryption Information Key Status AN-APDU Allowed GSM Algorithms Allowed UMTS Algorithms Radio Resource Information Radio Resource List BSSMAP Service Handover BSSMAP Service Handover List RANAP Service Handover Request M C C C M C C C C C C C

3GPP TS 29.002 V4.17.0 (2006-06) Indication M(=) C(=) C(=) C(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

4099

4100 8.4.4.3
4102 Invoke Id

Parameter use

4101 For the definition and use of all parameters and errors, see clause 7.6.1.

4103 For definition of this parameter see clause 7.6.1. 4104 Integrity Protection Information 4105 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4106 encapsulated PDU is BSSMAP Cipher Mode Command. 4107 Encryption Information 4108 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4109 encapsulated PDU is BSSMAP Cipher Mode Command. 4110 Key Status 4111 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4112 encapsulated PDU is BSSMAP Cipher Mode Command. 4113 AN-APDU 4114 For definition of this parameter see clause 7.6.9. 4115 Allowed GSM Algorithms 4116 This parameters includes allowed GSM algorithms. This GSM parameter shall be included if the encapsulated PDU is 4117 RANAP Security Mode Command and there is an indication that the UE also supports GSM. 4118 Allowed UMTS Algorithms 4119 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if Integrity Protection 4120 Information and Encryption Information are not available and the encapsulated PDU is BSSMAP Cipher Mode 4121 Command. 4122 Radio Resource Information 4123 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4124 Assignment Request. If the parameter Radio Resource List is sent, the parameter Radio Resource Information shall not 4125 be sent. 4126 Radio Resource List 4127 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4128 Assignment Request and MSC-A requests modification of multiple bearers. If the parameter Radio Resource 4129 Information is sent, the parameter Radio Resource List shall not be sent. 4130 BSSMAP Service Handover

470

4131 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4132 RANAP RAB Assignment Request. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP 4133 Service Handover shall not be sent. 4134 BSSMAP Service Handover List 4135 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4136 RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter BSSMAP 4137 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4138 RANAP Service Handover 4139 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4140 BSSMAP Assignment Request. 4141

471 Release 4 472 473

119

3GPP TS 29.002 V4.17.0 (2006-06)

4142 4143 8.4.5.1

8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service


Definition

4144 This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a 4145 handover or relocation to either MSC-A or a third MSC (MSC-B') is required. 4146 The MAP_PREPARE_SUBSEQUENT_HANDOVER service is a confirmed service using the primitives from 4147 table 8.4/5.

4148 8.4.5.2
4149

Service primitives
Table 8.4/5: MAP_PREPARE_SUBSEQUENT_HANDOVER
Parameter name Invoke Id Target Cell Id Target RNC Id Target MSC Number Selected RAB ID AN-APDU User error Provider error Request M C C M C M Indication M(=) C(=) C(=) M(=) C(=) M(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

4150

4151 8.4.5.3
4152 Invoke Id

Parameter use

4153 For definition of this parameter see clause 7.6.1. 4154 Target Cell Id 4155 For definition of this parameter see clause 7.6.2. This parameter shall be excluded if the service is a part of the Inter4156 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4157 23.009. 4158 Target RNC Id 4159 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter4160 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4161 23.009. 4162 Target MSC Number 4163 For definition of this parameter see clause 7.6.2.

474

4164 Selected RAB ID 4165 For definition of this parameter see clause 7.6.2. 4166 AN-APDU 4167 For definition of this parameter see clause 7.6.9. 4168 User error 4169 For definition of this parameter see clause 7.6.1. The following error causes defined in clause 7.6.1 may be used, 4170 depending on the nature of the fault: 4171 4172 4173 4174

475 Release 4 476 477

120

3GPP TS 29.002 V4.17.0 (2006-06)

Unknown MSC; Subsequent handover failure; Unexpected data value; Data Missing.

4175 Provider error 4176 For definition of this parameter see clause 7.6.1.

4177 4178 8.4.6.1

8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service


Definition

4179 This service is used between MSC and VLR (B-interface) to request a handover number. 4180 The MAP_ALLOCATE_HANDOVER_NUMBER service is a confirmed service using the primitives from table 8.4/6.

4181 8.4.6.2
4182

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

4183

4184 8.4.6.3
4185 Invoke Id

Parameter use

4186 For definition of this parameter see clause 7.6.1. 4187 User error 4188 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4189 on the nature of the fault: 4190

No handover number available.

4191 Provider error 4192 For definition of this parameter see clause 7.6.1.

4193 4194 8.4.7.1

8.4.7 MAP_SEND_HANDOVER_REPORT service


Definition

478

4195 This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and 4196 used by MSC-A. 4197 The MAP_SEND_HANDOVER_REPORT service is a confirmed service using the primitives from table 8.4/7.

479 Release 4 480 481

121

3GPP TS 29.002 V4.17.0 (2006-06)

4198 8.4.7.2
4199

Service primitives
Table 8.4/7: MAP_SEND_HANDOVER_REPORT

Parameter name Invoke Id Handover Number Linked Id Provider error

Request M M M

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

Response M(=)

Confirm M(=) O

4200

4201 8.4.7.3
4202 Invoke Id

Parameter use

4203 For definition of this parameter see clause 7.6.1. 4204 Handover Number 4205 For definition of this parameter see clause 7.6.2. 4206 Linked Id 4207 For definition of this parameter see clause 7.6.1. This service is linked with 4208 MAP_ALLOCATE_HANDOVER_NUMBER. 4209 Provider error 4210 For definition of this parameter see clause 7.6.1.

4211 4212

8.5 Authentication management services


8.5.1 MAP_AUTHENTICATE service

4213 The MAP_AUTHENTICATE service is used on the MAP B interface. This interface is not fully operational specified. 4214 It is strongly recommended not to implement the B-interface as an external interface.

4215 8.5.1.1

Definition

4216 This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC 4217 concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to 4218 initiate authentication. 4219 The service is a confirmed service and consists of four service primitives.

4220 8.5.1.2

Service primitives

4221 The service primitives are shown in table 8.5/1. 4222


Parameter name Invoke id RAND CKSN SRES

Table 8.5/1: MAP_AUTHENTICATE parameters


Request M M M Indication M(=) M(=) M(=) Response M(=) Confirm M(=)

M(=)

482

483 Release 4 484 485 Provider error

122

3GPP TS 29.002 V4.17.0 (2006-06) O

4223

4224 8.5.1.3
4225 Invoke id

Parameter use

4226 See clause 7.6.1 for the use of this parameter. 4227 RAND 4228 See clause 7.6.7 for the use of this parameter. 4229 CKSN 4230 See clause 7.6.7 for the use of this parameter. 4231 SRES 4232 See clause 7.6.7 for the use of this parameter. 4233 Provider error 4234 See clause 7.6.1 for the use of this parameter.

4235 4236 8.5.2.1

8.5.2 MAP_SEND_AUTHENTICATION_INFO service


Definition

4237 This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. 4238 The VLR requests up to five authentication vectors. 4239 Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information from the 4240 HLR. The SGSN requests up to five authentication vectors. 4241 If the user is a UMTS subscriber, the HLR shall return authentication quintuplets. If the user is a GSM subscriber, the 4242 HLR shall return authentication triplets. 4243 If the HLR cannot provide the VLR or the SGSN with triplets, an empty response is returned. The VLR or the SGSN 4244 may then re-use old authentication triplets, except where this is forbidden under the conditions specified in 3GPP TS 4245 43.020 [24]. 4246 If the HLR cannot provide the VLR or the SGSN with quintuplets, an empty response is returned. The VLR or the 4247 SGSN shall not re-use old authentication quintuplets. 4248 If the VLR or SGSN receives a MAP_SEND_AUTHENTICATION_INFO response containing a User Error parameter 4249 as part of the handling of an authentication procedure, the authentication procedure in the VLR or SGSN shall fail. 4250 Security related network functions are further described in 3GPP TS 43.020 [24] and 3GPP TS 33.200. 4251 The service is a confirmed service and consists of four service primitives.

4252 8.5.2.2

Service primitives

4253 The service primitives are shown in table 8.5/2. 4254

Table 8.5/2: MAP_SEND_AUTHENTICATION_INFO parameters


Parameter name Invoke id IMSI Number of requested vectors Requesting node type Re-synchronisation Info Request M C C C C Indication M(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

486

487 Release 4 488 489 Segmentation prohibited indicator Immediate response preferred indicator AuthenticationSetList User error Provider error

123 C U C (=) C (=)

3GPP TS 29.002 V4.17.0 (2006-06)

C C

C(=) C(=) O

4255

4256 8.5.2.3
4257 Invoke id

Parameter use

4258 See clause 7.6.1 for the use of this parameter. 4259 IMSI 4260 See clause 7.6.2 for the use of this parameter. 4261 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4262 dialogue then this parameter shall not be present in any service request other than the first one. 4263 Number of requested vectors 4264 A number indicating how many authentication vectors the VLR or SGSN is prepared to receive. The HLR shall not 4265 return more vectors than indicated by this parameter. 4266 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4267 dialogue then this parameter shall not be present in any service request other than the first one. 4268 Requesting node type 4269 The type of the requesting node (SGSN or VLR). 4270 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4271 dialogue then this parameter shall not be present in any service request other than the first one. 4272 Re-synchronisation Info 4273 For definition and use of this parameter see 3GPP TS 33.200. 4274 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4275 than the first one. 4276 Segmentation prohibited indicator 4277 This parameter indicates if the VLR or SGSN allows segmentation of the response at MAP user level. 4278 This parameter may be present only in the first request of the dialogue. 4279 Immediate response preferred indicator 4280 4281 4282 4283

This parameter indicates that one of the requested authentication vectors is requested for immediate use in the VLR or SGSN. It may be used by the HLR together with the number of requested vectors and the number of vectors stored in the HLR to determine the number of vectors to be obtained from the AuC. It shall be ignored if the number of available vectors is greater than the number of requested vectors.

4284 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4285 than the first one. 4286 AuthenticationSetList 4287 A set of one to five authentication vectors are transferred from the HLR to the VLR or from the HLR to the SGSN, if 4288 the outcome of the service was successful. 4289 User error

490

4290 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4291 the service, depending on the respective failure reason: 4292 4293 4294 4295

491 Release 4 492 493

124

3GPP TS 29.002 V4.17.0 (2006-06)

unknown subscriber; unexpected data value; system failure; data missing.

4296 Provider error 4297 See clause 7.6.1 for the use of this parameter.

4298 4299 8.5.3.1

8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service


Definition

4300 This service is used between the VLR and the HLR or between the SGSN or HLR for reporting of authentication 4301 failures.

4302 8.5.3.2

Service primitives

4303 The service primitives are shown in table 8.5/3. 4304

Table 8.5/3: MAP_AUTHENTICATION_FAILURE_REPORT parameters


Parameter name Invoke id IMSI Failure cause Re-attempt Access Type Rand VLR number SGSN 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(=) O

4305

4306 8.5.3.3
4307 Invoke id

Parameter use

4308 See clause 7.6.1 for the use of this parameter. 4309 IMSI 4310 See clause 7.6.2 for the use of this parameter. 4311 Failure Cause 4312 See clause 7.6.7 for use of this parameter. 4313 4314 Re-attempt 4315 See clause 7.6.7 for use of this parameter. 4316 Access Type 4317 See clause 7.6.7 for use of this parameter.

494

4318 Rand

495 Release 4 496 497

125

3GPP TS 29.002 V4.17.0 (2006-06)

4319 This parameter identifies the specific AV that failed authentication. 4320 See clause 7.6.7 for use of this parameter. 4321 VLR number 4322 Shall be present if the sender is VLR. See definition in clause 7.6.2. 4323 SGSN number 4324 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 4325 User error 4326 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 4327 values defined in clause 7.6.1: 4328 4329 4330

Unknown Subscriber; System Failure; Unexpected Data Value.

4331 Provider error 4332 These are defined in clause 7.6.

4333 4334 4335 8.6.1.1

8.6 Security management services


8.6.1 MAP_SET_CIPHERING_MODE service
Definitions

4336 This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is 4337 called when another service requires that information is to be sent on the radio path in encrypted form. 4338 The service is a non-confirmed service and consists of two service primitives.

4339 8.6.1.2

Service primitives

4340 The service primitives are shown in table 8.6/1. 4341

Table 8.6/1: MAP_SET_CIPHERING_MODE parameters


Parameter name Invoke id Ciphering mode Kc Request M M C Indication M(=) M(=) C(=)

4342

4343 8.6.1.3
4344 Invoke id

Parameter use

4345 See clause 7.6.1 for the use of this parameter. 4346 Ciphering mode 4347 See clause 7.6.7 for the use of this parameter. 4348 Kc

498

4349 The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed.

499 Release 4 500 501

126

3GPP TS 29.002 V4.17.0 (2006-06)

4350 4351 4352 4353 8.7.1.1

8.7 International mobile equipment identities management services


8.7.1 MAP_CHECK_IMEI service
Definition

4354 This service is used between the VLR and the MSC and between the MSC and the EIR and between the SGSN and EIR 4355 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 4356 transferred to the EIR in the service request. 4357 The service is a confirmed service and consists of four service primitives.

4358 8.7.1.2

Service primitives

4359 The service primitives are shown in table 8.7/1. 4360


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

4361

4362 8.7.1.3
4363 Invoke id

Parameter use

4364 See clause 7.6.1 for the use of this parameter. 4365 IMEI 4366 4367 4368 4369

See clause 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.

4370 Equipment status 4371 See clause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of 4372 the service. 4373 User error 4374 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4375 the service, depending on the respective failure reason: 4376 4377 4378 4379

unknown equipment; this error is returned by the responder when the IMEI is not known in the EIR;

system failure; unexpected data value.

4380 Provider error

502

4381 See clause 7.6.1 for the use of this parameter.

503 Release 4 504 505

127

3GPP TS 29.002 V4.17.0 (2006-06)

4382 4383 8.7.2.1

8.7.2 MAP_OBTAIN_IMEI service


Definition

4384 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 4385 requested from the MS. 4386 The service is a confirmed service and consists of four service primitives.

4387 8.7.2.2

Service primitives

4388 The service primitives are shown in table 8.7/2. 4389


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

4390

4391 8.7.2.3
4392 Invoke id

Parameter use

4393 See clause 7.6.1 for the use of this parameter. 4394 IMEI 4395 See clause 7.6.2 for the use of this parameter. The parameter is included in the service response from the MSC to the 4396 VLR on successful outcome of the service. 4397 User error 4398 If the service fails, the VLR sends the user error System Failure (see clause 7.6.1) to the MSC. 4399 Provider error 4400 See clause 7.6.1 for the use of this parameter.

4401 4402 4403 8.8.1.1


-

8.8 Subscriber management services


8.8.1 MAP-INSERT-SUBSCRIBER-DATA service
Definition

4404 This service is used by an HLR to update a VLR with certain subscriber data in the following occasions: 4405 4406 4407 4408 4409 4410 4411

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

506

4412 4413 4414

507 Release 4 508 509

128

3GPP TS 29.002 V4.17.0 (2006-06)

are the CLIR and COLR services. Network access mode is provided only in restoration. If the Super-Charger functionality is supported the HLR may not need to provide the VLR with subscriber parameters at location updating of a subscriber. See TS 23.116.

4415 Also this service is used by an HLR to update an SGSN with certain subscriber data in the following occasions: 4416 4417 4418 4419 4420 4421 4422

if the GPRS subscription has changed; if the network access mode is changed; 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 SGSN with subscriber parameters at GPRS location updating of a subscriber. If the Super-Charger functionality is supported the HLR may not need to provide the SGSN with subscriber parameters. See 3GPP TS 23.116.

4423 It is a confirmed service and consists of the primitives shown in table 8.8/1.

4424 8.8.1.2
4425

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 MC-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 SGSN Camel Subscription Info LSA Information IST Alert Timer SS-Code List LMU Identifier LCS Information CS Allocation/Retention priority Super-Charger Supported In HLR Subscribed Charging Characteristics 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 C U C C C C C 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(=) C(=) C(=) C(=)

Response M(=)

Confirm M(=)

C C

C(=) C(=)

C(=)

C C(=) C(=) C(=) C(=) C(=) C C U

C(=)

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

510

4426

511 Release 4 512 513

129

3GPP TS 29.002 V4.17.0 (2006-06)

4427 8.8.1.3

Parameter use

4428 All parameters are described in clause 7.6. The following clarifications are applicable: 4429 Network access mode 4430 4431 4432 4433

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 GPRS subscriber data at GPRS location updating. It shall be sent to the SGSN if it is changed as a result of administrative action.

4434 IMSI 4435 It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by 4436 the VLR and the SGSN. 4437 MSISDN 4438 It is included either at location updating or when it is changed. The MSISDN sent shall be the basic MSISDN. This 4439 parameter is used by the VLR and the SGSN. 4440 Category 4441 It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN 4442 receives this parameter it shall ignore it. 4443 Subscriber Status 4444 It is included either at location updating or when it is changed. 4445 4446 4447 4448

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.

4449 To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This 4450 parameter is used by the VLR and the SGSN. 4451 Bearer service List 4452 A list of Extensible Bearer service parameters (Extensible Bearer service is defined in clause 7.6). An Extensible Bearer 4453 service parameter must be the code for an individual Bearer service, except in the cases described below. 4454 4455 4456 4457

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.

4458 If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location 4459 updating or at restoration) or only the ones added (at subscriber data modification). 4460 If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not 4461 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no 4462 error is sent back), except in the cases described below. 4463 4464 4465 4466 4467 4468 4469 4470

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.

514

4471 Teleservice List 4472 A list of Extensible Teleservice parameters (Extensible Teleservice is defined in clause 7.6). An Extensible Teleservice 4473 parameter must be the code for an individual Teleservice. 4474 If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating 4475 or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant 4476 to the node at which the message is received should be included in the Teleservice List. 4477 If the VLR or the SGSN receives an Indication containing any Extensible Teleservice parameters which it does not 4478 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Teleservices (no 4479 error is sent back). This parameter is used by the VLR and the SGSN. 4480 Forwarding information List 4481 A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in clause 7.6). It 4482 includes Call Forwarding services either at location updating or at restoration or when they are changed. Each 4483 Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive. 4484 The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary 4485 service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible 4486 Forwarding Feature is defined in clause 7.6). 4487 The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according 4488 to the rules in clause 8.8.1.4. 4489 The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter. 4490 4491 4492 4493 4494 4495

515 Release 4 516 517

130

3GPP TS 29.002 V4.17.0 (2006-06)

If the Extensible SS-Status indicates that call forwarding is registered then (except for call forwarding unconditional) the Extensible Forwarding Feature shall contain a number to define the forwarded-to destination 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.

4496 The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding 4497 unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding 4498 options shall be ignored by the VLR, and may be set to any value by the HLR. 4499 For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the 4500 Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply 4501 condition timer shall not be included. 4502 For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not 4503 contain a no reply condition timer. 4504 4505 4506 4507

If the VLR receives an Indication containing any Call Forwarding service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Call Forwarding 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.

4508 Call barring information List 4509 A list of Extensible Call barring information parameters (Extensible Call barring information is defined in clause 7.6). It 4510 includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible 4511 Call barring information parameter shall be treated independently of all other parameters in the primitive. 4512 The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. 4513 The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call 4514 Barring Feature is defined in clause 7.6). 4515 The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted 4516 according to the rules in clause 8.8.1.4. 4517 The Extensible Call Barring Feature shall contain an extensible SS-Status parameter.

518

4518 4519 4520 4521

519 Release 4 520 521

131

3GPP TS 29.002 V4.17.0 (2006-06)

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.

4522 CUG information List 4523 A list of CUG information list parameters (CUG information is defined in clause 7.6). It includes CUG information 4524 either at location updating or at restoration or when it is changed. 4525 At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete 4526 CUG-SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If 4527 there are not options per extensible basic service group the CUG-FeatureList shall not be included. 4528 In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty 4529 CUG-SubscriptionList. 4530 When the VLR receives CUG data it shall replace the stored CUG data with the received data set. 4531 If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible 4532 basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no 4533 preferential CUG exists. 4534 If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies. 4535 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4536 Unexpected Data Value. 4537 Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR. 4538 If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards 4539 the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this 4540 parameter it shall ignore it. 4541 SS-Data List 4542 4543 4544 4545

A list of Extensible SS-Data parameters (Extensible SS-Data is defined in clause 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.

4546 The Extensible SS-Data shall include the SS-Code for an individual supplementary service. 4547 The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are 4548 applicable to the service defined by the SS-Code. 4549 The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in clause 8.8.1.4. 4550 If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it 4551 returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received 4552 (no error is sent back). 4553 4554 4555 4556

This parameter is used by the SGSN only for LCS. If the SGSN receives an Indication containing any LCS related supplementary service codes which it does not support/allocate then it returns them to the HLR in the parameter SSCode List and therefore discards the unsupported service codes received (no error is sent back). SS-codes not related to the supported LCS capability set shall be discarded.

4557 Operator Determined Barring General data 4558 4559 4560 4561

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.

522

4562 4563 4564 4565

523 Release 4 524 525

132

3GPP TS 29.002 V4.17.0 (2006-06)

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.

4566 Operator Determined Barring HPLMN data 4567 4568 4569 4570

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.

4571 If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data 4572 is present then the VLR or the SGSN shall not apply any HPLMN specific ODB services to the subscriber. This 4573 parameter is used by the VLR and the SGSN. 4574 eMLPP Subscription Data 4575 If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a 4576 call (as defined in clause 7.6). It contains both subparameters of eMLPP. 4577 If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and 4578 therefore discards the received information (no error is sent back). 4579 4580 4581 4582

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.

4583 MC Subscription Data 4584 If included in the Insert Subscriber Data request, this parameter provides the MC Subscription Data as defined in 4585 clause 7.6. 4586 If the VLR does not support the MC service, it returns its code to the HLR in the parameter SS-Code List and therefore 4587 discards the received information (no error is sent back). 4588 4589 4590 4591

MC subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced by the new MC 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.

4592 Roaming Restriction Due To Unsupported Feature 4593 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 4594 supported by the MSC/VLR (e.g. Advice of Charge Charging Level). 4595 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 4596 the VLR and if the SGSN receives this parameter it shall ignore it. 4597 Regional Subscription Data 4598 4599 4600 4601 4602 4603

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 clause 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.

4604 Regional subscription data that have been stored previously in a subscriber data record in the VLR or in the SGSN are 4605 completely replaced by the regional subscription data received in an Insert Subscriber Data indication during either an 4606 Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure.

526

4607 After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are 4608 allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional 4609 Subscription Response. 4610 The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has 4611 been detected in one of the following cases: 4612 4613 4614 4615

527 Release 4 528 529

133

3GPP TS 29.002 V4.17.0 (2006-06)

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.

4616 Zone codes which have no mapping to location areas shall be ignored. 4617 If a sequence of MAP_INSERT_SUBSCRIBER_DATA services is used during a dialogue, Regional Subscription Data 4618 shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with 4619 the error Unexpected Data Value. 4620 If Regional Subscription Data are not included in any MAP_INSERT_SUBSCRIBER_DATA service, there is no 4621 restriction of roaming due to Regional Subscription. This parameter is used by the VLR and the SGSN. 4622 Voice Broadcast Data 4623 This parameter contains a list of group id's a user might have subscribed to; (VBS-Data is defined in clause 7.6). It 4624 includes VBS information either at location updating or at restoration or when it is changed. 4625 At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data. 4626 When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All 4627 subsequent VBS-data received within this dialogue shall be interpreted as add-on data. 4628 If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data. 4629 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4630 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4631 it. 4632 Voice Group Call Data 4633 This parameter contains a list of group id's a user might have subscribed to; see clause 7.6. 4634 At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete 4635 VGCS-Data. 4636 When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. 4637 All VGCS-Data received within this dialogue shall be interpreted as add-on data. 4638 If VBCS-Data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VGCS-Data. 4639 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4640 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4641 it. 4642 North American Equal Access preferred Carrier Id List 4643 A list of the preferred carrier identity codes that are subscribed to. 4644 4645 4646 4647

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.

530

4648 LSA Information 4649 4650 4651 4652 4653 4654 4655

531 Release 4 532 533

134

3GPP TS 29.002 V4.17.0 (2006-06)

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 clause 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.

4656 At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA 4657 Information. 4658 When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data. 4659 When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access 4660 indicator. 4661 4662 4663 4664

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.

4665 If the entire LSA information is received, it shall always include the LSA only access indicator value together with the 4666 LSA data applicable for the PLMN (if any). 4667 If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously 4668 stored LSA Information. 4669 If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the 4670 error Unexpected Data Value. This parameter is used by the VLR and the SGSN. 4671 IST Alert Timer 4672 This parameter contains the IST Alert timer value that must be used to inform the HLR about the call activities that the 4673 subscriber performs. 4674 At Location Updating, restoration, or when there is a change in the IST data defined for the Subscriber, the HLR shall 4675 include the IST Alert timer. 4676 LMU Identifier 4677 This parameter indicates the presence of an LMU. This parameter is used only by the VLR and shall be ignored if 4678 received by an SGSN. 4679 LCS Information 4680 This parameter provides the following LCS related information for an MS subscriber: 4681 4682 4683

list of GMLCs in the HPLMN; privacy exception list; MO-LR list.

4684 At restoration and location updating, the HLR shall include the complete LCS data of the subscriber. 4685 When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS 4686 data that is not modified need not be included. 4687 The VLR/SGSN shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data 4688 operation. 4689 If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the 4690 error Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the 4691 SS-Data List, then the VLR shall not interpret this as overlapping data.

534

4692 Super-Charger Supported In HLR 4693 This parameter is used by the HLR to indicate support for the Super-Charger functionality. If this parameter is present it 4694 shall include an indication of the age of the subscription data stored in the HLR. 4695 If this parameter is absent then the HLR does not support the Super-Charger functionality. 4696 Subscribed Charging Characteristics 4697 This parameter refers to the Subscribed Charging Characteristics as defined in 3GPP TS 32.215 [123]. 4698 For a detailed description of the use of the parameter, see 3GPP TS 32.215 [123x]. 4699 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4700 SS-Code List 4701 4702 4703 4704 4705

535 Release 4 536 537

135

3GPP TS 29.002 V4.17.0 (2006-06)

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 clause 7.6). The list can only include individual SS-Codes that were sent in the service request. For the VLR, this list can also include 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.

4706 Regional Subscription Response 4707 If included in the response this parameter indicates one of: 4708 4709 4710 4711 4712

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.

4713 If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR 4714 shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted 4715 is not sent. The HLR shall check whether the current MSC area is no longer restricted. 4716 4717 4718 4719

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.

4720 VLR CAMEL Subscription Info 4721 4722 4723 4724 4725 4726

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. In CAMEL Phase 2, this parameter may contain OCSI, SS-CSI and TIF-CSI. In CAMEL Phase 3, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, SMS-CSI, M-CSI and TIF-CSI. In CAMEL Phase 2 TDP-Criteria for O-CSI may be associated with O-CSI. In CAMEL Phase 3, additionally, TDPCriteria for VT-CSI may be associated with VT-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.

4727 At location updating, the complete set of VLR CAMEL Subscription Info is sent in one dialogue. 4728 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the VLR, then: 4729 4730 4731

for CAMEL Phase 1 and CAMEL Phase 2, the complete set of VLR CAMEL Subscription Info is sent in one dialogue; for CAMEL Phase 3, one or more specific elements of VLR CAMEL Subscription Info are sent in one dialogue.

4732 When the VLR receives a specific element of VLR CAMEL Subscription Info, it shall overwrite the corresponding 4733 specific element of VLR CAMEL Subscription Info (if any) which it has stored for that subscriber.

538

4734 For CAMEL Phase 1 and CAMEL Phase 2 , the VLR CAMEL Subscription Info consists of any one or more of: 4735 4736 4737 4738

539 Release 4 540 541

136

3GPP TS 29.002 V4.17.0 (2006-06)

O-CSI (irrespective of the value of the CAMEL Capability Handling inside O-CSI),TDP-Criteria for OCSI,SS-CSI and TIF-CSI. (The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The omitted elements of above list will be withdrawn in the VLR.)

4739 From CAMEL phase 3 onwards, the specific elements of VLR CAMEL Subscription Info which may be sent are:

4740
4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753

-O-CSI (irrespective of the value of the CAMEL Capability Handling inside O-CSI), TDP criteria for OCSI, SS-CSI and TIF-CSI; (The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The omitted elements of above list will be withdrawn in the VLR.) D-CSI; VT-CSI; TDP-Criteria for VT-CSI; SMS-CSI; M-CSI.

If the VLR CAMEL Subscription Info is omitted 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.

4754 The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag) for CAMEL Phase 2 and 4755 3. See 3GPP TS 23.072 for the use of this parameter and the conditions for its presence. 4756 Supported CAMEL Phases 4757 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. This parameter is used 4758 by the VLR and SGSN. 4759 A VLR or SGSN not supporting any CAMEL Phase may omit this parameter. 4760 GPRS Subscription Data 4761 This parameter contains a list of PDP-contexts a user has subscribed to; see clause 7.6. 4762 At GPRS location updating the HLR shall include the complete GPRS Subscription Data. 4763 When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts. 4764 4765 4766 4767

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.

4768 If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored 4769 GPRS Subscription Data. 4770 If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error 4771 Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 4772 it. 4773 SGSN CAMEL Subscription Info

542

4774 The SGSN CAMEL Subscription Info is sent at GPRS location updating or when any information in the applicable 4775 SGSN CAMEL Subscription Info in the HLR has been changed. In CAMEL Phase 3, this parameter may contain one or 4776 both of GPRS-CSI and SMS-CSI. 4777 At GPRS location updating the complete set of SGSN CAMEL Subscription Info is sent. 4778 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the SGSN, then 4779 one or more specific elements of SGSN CAMEL Subscription Info are sent in one dialogue. 4780 When the SGSN receives a specific element of SGSN CAMEL Subscription Info, it shall overwrite the corresponding 4781 specific element of SGSN CAMEL Subscription Info (if any) which it has stored for that subscriber. 4782 The specific elements of SGSN CAMEL Subscription Info which may be sent are: 4783 4784

543 Release 4 544 545

137

3GPP TS 29.002 V4.17.0 (2006-06)

SMS-CSI; GPRS-CSI.

4785 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4786 Roaming Restricted In SGSN Due To Unsupported Feature 4787 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 4788 supported by the SGSN. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 4789 it. 4790 CS Allocation/Retention priority 4791 The CS Allocation/Retention priority is used only for Circuit Switched (CS). This parameter specifies relative 4792 importance to compare with other bearers about allocation and retention of bearer. This parameter is used only by the 4793 VLR and if the SGSN receives this parameter it shall ignore it. 4794 User error 4795 Only one of the following values is applicable: 4796 4797 4798

Unidentified subscriber; Data missing; Unexpected data value.

4799 8.8.1.4
4800 4801 4802 4803

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 clause explains how this information is to be interpreted. Supplementary service parameters to which this clause is applicable only apply to the basic service groups described in this clause, and only those basic service groups shall be overwritten at the VLR.

4804 The Basic Service Group (or Basic Service Group List) is optional. 4805 If present the Basic Service Group (or the elements of the Basic Service Group List) shall be one of: 4806 4807 4808 4809 4810 4811 4812 4813

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.

4814 If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic 4815 Service Groups.

546

4816 If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as 4817 applying individually to all the Elementary Basic Service Groups for which: 4818 4819

547 Release 4 548 549

138

3GPP TS 29.002 V4.17.0 (2006-06)

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.

4820 The VLR is not required to store supplementary services data for Basic Service Groups that are not supported at the 4821 VLR.

4822 4823 8.8.2.1

8.8.2 MAP-DELETE-SUBSCRIBER-DATA service


Definition

4824 This service is used by an HLR to remove certain subscriber data from a VLR if the subscription of one or more 4825 supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or 4826 deactivation of supplementary services. 4827 Also this service is used by an HLR to remove GPRS subscription data from a SGSN. 4828 It is a confirmed service and consists of the primitives shown in table 8.8/2.

4829 8.8.2.2
4830

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 Specific CSI 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 IST Information Withdraw Regional Subscription Response GMLC List Withdraw Subscribed Charging Characteristics Withdraw User error Provider error

Request M M C C C 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(=)

Response M(=)

Confirm M(=)

C C(=) C(=) C

C(=)

C(=) O

4831

4832 8.8.2.3

Parameter use

4833 All parameters are described in clause 7.6. The following clarifications are applicable: 4834 Basic service List 4835 4836 4837 4838

A list of Extensible Basic service parameters (Extensible Basic service is defined in clause 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.

4839 SS-Code List

550

4840 A list of SS-Code parameters (SS-Code is defined in clause 7.6). It is used when several or all supplementary services 4841 are to be withdrawn from the subscriber. 4842 There are three possible options: 4843 4844 4845 4846 4847 4848

551 Release 4 552 553

139

3GPP TS 29.002 V4.17.0 (2006-06)

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.

4849 This parameter is used by the VLR and SGSN for LCS. Otherwise, this parameter is used only by the VLR and if the 4850 SGSN receives this parameter it shall ignore it. 4851 Roaming Restriction Due To Unsupported Feature 4852 This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This 4853 may occur if unsupported features or services are removed from the subscriber data in the HLR. 4854 If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is 4855 used only by the VLR and if the SGSN receives this parameter it shall ignore it. 4856 CAMEL Subscription Info Withdraw 4857 This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR or from the SGSN. All 4858 CAMEL Subscription Info for the subscriber shall be deleted. This parameter is used by the VLR and by the SGSN. 4859 This parameter should not be sent in the same message as the Specific CSI Withdraw parameter. 4860 Specific CSI Withdraw 4861 This parameter is used to indicate that one or more specific elements of CAMEL Subscription Info shall be deleted from 4862 the VLR or from the SGSN. 4863 The specific elements of CAMEL Subscription Info which may be withdrawn are: 4864 4865 4866 4867 4868 4869 4870 4871

O-CSI with TDP criteria for O-CSI; SS-CSI; TIF-CSI; D-CSI; VT-CSI with TDP criteria for VT-CSI; SMS-CSI; M-CSI; GPRS-CSI.

4872 This parameter is used by the VLR and by the SGSN. It shall not be sent to VLRs that do not support CAMEL phase 3. 4873 This parameter should not be sent in the same message as the CAMEL Subscription Info Withdraw parameter. 4874 Regional Subscription Identifier 4875 4876 4877 4878 4879

Contains one single Zone Code (as defined in clause 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".

554

4880 The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the 4881 VLR or by the SGSN. 4882 Note that support of this parameter is a network operator option and it shall not be sent to networks which do not 4883 support Regional Subscription. 4884 If Regional Subscription is not supported by the VLR or by the SGSN, the request for deletion of Zone Codes is refused 4885 by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR. 4886 If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information 4887 shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR and by 4888 the SGSN. 4889 VBS Group Indication 4890 Contains an indication (flag) which is used if all Group Ids shall be deleted from the subscriber data for the Voice 4891 Broadcast teleservice. 4892 If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request 4893 for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN receives this 4894 parameter it shall ignore it. 4895 VGCS Group Indication 4896 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice 4897 Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4898 it. 4899 If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the 4900 request for deletion of all Group Ids shall be ignored. 4901 GPRS Subscription Data Withdraw 4902 4903 4904 4905

555 Release 4 556 557

140

3GPP TS 29.002 V4.17.0 (2006-06)

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 contexts 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.

4906 Roaming Restricted In SGSN Due To Unsupported Feature 4907 This parameter is used if Roaming Restricted In SGSN Due To Unsupported Feature is deleted from the GPRS 4908 subscriber data. This may occur if unsupported features or services are removed from the GPRS subscriber data in the 4909 HLR. 4910 If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is 4911 used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4912 LSA Information Withdraw 4913 4914 4915 4916

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.

4917 IST Information Withdraw 4918 This parameter is used to indicate that the IST condition has been removed for the subscriber. See 3GPP TS 43.035 for 4919 the use of this parameter. 4920 Regional Subscription Response 4921 If included in the Delete Subscriber Data response this parameter indicates one of: 4922 4923

MSC Area Restricted; SGSN Area Restricted;

558

4924

559 Release 4 560 561

141

3GPP TS 29.002 V4.17.0 (2006-06)

Regional Subscription Not Supported.

4925 This parameter is used by the VLR and by the SGSN. 4926 GMLC List Withdraw 4927 This parameter indicates that the subscriber's LCS GMLC List shall be deleted from the VLR or SGSN. 4928 Subscribed Charging Characteristics Withdraw 4929 This parameter indicates that the Subscribed Charging Characteristics shall be replaced with a local default value in the 4930 SGSN (see 3GPP TS 32.215 [123]). 4931 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4932 User error 4933 Only one of the following values is applicable: 4934 4935 4936

Unidentified subscriber; Data missing; Unexpected data value.

4937 4938 4939 8.9.1.1

8.9 Identity management services


8.9.1 MAP-PROVIDE-IMSI service
Definition

4940 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 4941 identified itself with a TMSI not allocated to any subscriber in the VLR). 4942 It is a confirmed service and consists of the primitives shown in table 8.9/1.

4943 8.9.1.2
4944

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

4945

4946 8.9.1.3
4948 IMSI

Parameter use

4947 All parameters are described in clause 7.6. The following clarifications are applicable:

4949 This parameter is received when the request is successfully carried out. It contains the requested IMSI. 4950 User error 4951 Only one of the following values is applicable: 4952

Absent subscriber.

4953

8.9.2 MAP-FORWARD-NEW-TMSI service

562

4954 8.9.2.1

563 Release 4 564 565

142

3GPP TS 29.002 V4.17.0 (2006-06)

Definition

4955 This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call 4956 set-up, location updating or supplementary services operation). 4957 It is a confirmed service and consists of the primitives shown in table 8.9/2.

4958 8.9.2.2
4959

Service primitives
Table 8.9/2: MAP-FORWARD-NEW-TMSI
Parameter name Invoke Id TMSI Provider error Request M M Indication M(=) M(=) Response M(=) Confirm M(=) O

4960

4961 8.9.2.3

Parameter use

4962 The parameter TMSI is described in clause 7.6.

4963 4964 4965 8.10.1.1

8.10 Fault recovery services


8.10.1 MAP_RESET service
Definition

4966 This service is used by the HLR, after a restart, to indicate to a list of VLRs or SGSNs that a failure occurred. 4967 The MAP_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1.

4968 8.10.1.2
4969

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(=)

4970

4971 8.10.1.3
4972 Invoke Id

Parameter definition and use

4973 See definition in clause 7.6.1. 4974 HLR number 4975 See definition in clause 7.6.2. 4976 HLR Id LIST 4977 4978 4979 4980

The HLR Id List is a list of HLR Ids. 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.

4981

8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service

566

4982 8.10.2.1
4983 4984 4985 4986 4987

567 Release 4 568 569

143

3GPP TS 29.002 V4.17.0 (2006-06)

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.

4988 The MAP_FORWARD_CHECK_SS_INDICATION service is a non-confirmed service using the service primitives 4989 defined in table 8.10/2.

4990 8.10.2.2
4991

Service primitives
Table 8.10/2: MAP_FORWARD_CHECK_SS_INDICATION
Parameter name Invoke Id Request M Indication M(=)

4992

4993 8.10.2.3
4994 Invoke Id

Parameter definition and use

4995 See definition in clause 7.6.1.

4996 4997 8.10.3.1


4998 4999 5000 5001

8.10.3 MAP_RESTORE_DATA service


Definition

This service is invoked by the VLR on receipt of a MAP_PROVIDE_ROAMING_NUMBER indication for an unknown IMSI, or for a known IMSI with the indicator "Confirmed by HLR" set to "Not confirmed". The service is 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 stored in the subscriber's IMSI record.

5002 The MAP_RESTORE_DATA service is a confirmed service using the service primitives defined in table 8.10/3.

5003 8.10.3.2
5004

Service primitives
Table 8.10/3: MAP_RESTORE_DATA
Parameter name Invoke Id IMSI LMSI Supported CAMEL phases SoLSA Support Indicator IST Support Indicator Super-Charger Supported in Serving Network Entity Long FTN Supported Supported LCS Capability Sets HLR number MS Not Reachable Flag User error Provider error Request M M U C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C C C(=) C(=) C(=) O Response M(=) Confirm M(=)

5005

5006 8.10.3.3
5007 Invoke Id

Parameter definitions and use

570

5008 See definition in clause 7.6.1. 5009 IMSI 5010 See definition in clause 7.6.2. 5011 LMSI 5012 See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR 5013 to support the LMSI handling procedures. 5014 Supported CAMEL Phases 5015 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 5016 phase 1 is supported. Otherwise may be absent. 5017 SoLSA Support Indicator 5018 This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If 5019 this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling. 5020 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 5021 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 5022 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 5023 IST Support Indicator 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034

571 Release 4 572 573

144

3GPP TS 29.002 V4.17.0 (2006-06)

This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Restore Data indication and the Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the basic IST mechanism available. This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Restore Data indication and the HLR supports the IST Command capability, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the IST Command mechanism available.

5035 Long FTN Supported 5036 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 5037 Super-Charger Supported in Serving Network Entity 5038 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 5039 that subscriber data is required. 5040 If this parameter is absent then the VLR does not support the Super-Charger functionality. 5041 Supported LCS Capability Sets 5042 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 5043 capability set is marked as supported then the VLR does not support LCS at all. 5044 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 5045 version. 5046 HLR number 5047 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful outcome of the service. 5048 MS Not Reachable Flag

574

5049 See definition in clause 7.6.8. This parameter shall be present in case of successful outcome of the service, if the "MS 5050 Not Reachable flag" was set in the HLR. 5051 User error 5052 In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes 5053 defined in clause 7.6.1 may be used, depending on the nature of the fault: 5054 5055 5056 5057

575 Release 4 576 577

145

3GPP TS 29.002 V4.17.0 (2006-06)

unknown subscriber; system failure; unexpected data value; data missing.

5058 Provider error 5059 For definition of provider errors see clause 7.6.1.

5060 5061 5062 8.11.1.1

8.11 Subscriber Information services


8.11.1 MAP-ANY-TIME-INTERROGATION service
Definition

5063 This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR or the 5064 GMLC at any time. 5065 When this service is used to the HLR, the subscriber state or location may be requested. 5066 When this service is used to the GMLC, only the location may be requested. 5067 The MAP-ANY-TIME-INTERROGATION service is a confirmed service using the service primitives defined in 5068 table 8.11/1.

5069 8.11.1.2
5070

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

5071

5072 8.11.1.3

Parameter definition and use

5073 All parameters are described in clause 7.6. 5074 The HLR or GMLC may be able to use the value of the parameter gsmSCF-address to screen a 5075 MAP_Any_Time_Interrogation indication. 5076 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5077 User error

578

5078 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5079 5080 5081 5082 5083

579 Release 4 580 581

146

3GPP TS 29.002 V4.17.0 (2006-06)

System Failure; Any Time Interrogation Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber.

5084 Provider error 5085 These are defined in clause 7.6.1.

5086 5087 8.11.2.1

8.11.2 MAP-PROVIDE-SUBSCRIBER-Info service


Definition

5088 This service is used to request information (e.g. subscriber state and location) from the VLR at any time. 5089 The MAP-PROVIDE-SUBSCRIBER-Info service is a confirmed service using the primitives defined in table 8.11/2.

5090 8.11.2.2
5091

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

5092

5093 8.11.2.3

Parameter definition and use

5094 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 5095 specified in 3GPP TS 23.018 [97]. 5096 User error 5097 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5098 5099

Data Missing; Unexpected Data Value.

5100 Provider error 5101 These are defined in clause 7.6.1.

5102 5103 8.11.3.1

8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service


Definition

5104 This service is used by the gsmSCF, to request subscription information (e.g. call forwarding supplementary service 5105 data or CSI) from the HLR at any time.

582

5106 8.11.3.2
5107

583 Release 4 584 585

147

3GPP TS 29.002 V4.17.0 (2006-06)

Service primitives
Table 8.11/3: Any_Time_Subscription_Interrogation

Parameter name Invoke id Requested Subscription Info GsmSCF-Address IMSI MSISDN Long FTN Supported Call Forwarding Data Call Barring Data ODB Info CAMEL Subscription Info Supported CAMEL phases in VLR Supported CAMEL phases in SGSN User error Provider error

Request M M M C C C

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

Response M(=)

Confirm M(=)

C C C C C C C

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

5108

5109 8.11.3.3

Parameter definition and use

5110 All parameters are described in clause 7.6. 5111 The HLR may be able to use the value of the parameter gsmSCF-address to screen a 5112 MAP_Any_Time_Subscription_Interrogation indication. 5113 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5114 User error 5115 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125

Unexpected Data Value; Unknown Subscriber; BearerServiceNotProvisioned; TeleserviceNotProvisioned; CallBarred; IllegalSS-Operation; SS-NotAvailable; InformationNotAvailable; Any Time Subscription Interrogation Not Allowed; Data Missing.

5126 Provider error 5127 These are defined in clause 7.6.1.

5128 5129 8.11.4.1

8.11.4 MAP-ANY-TIME-MODIFICATION service


Definition

5130 This service is used by the gsmSCF, to modify information of the HLR at any time.

586

5131 8.11.4.2
5132

587 Release 4 588 589

148

3GPP TS 29.002 V4.17.0 (2006-06)

Service primitives
Table 8.11/4: Any_Time_Modification

Parameter name Invoke id gsmSCF-Address IMSI MSISDN Modification request for SS information Modification request for CSI Long FTN Supported Ext Forwarding information-for-CSE Ext Call barring information-for-CSE CAMEL subscription info User error Provider error

Request M M C C C C C

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

Response M(=)

Confirm M(=)

C C C C

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

5133

5134 8.11.4.3

Parameter definition and use

5135 All parameters are described in clause 7.6. 5136 The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Modification 5137 indication. 5138 The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5139 User error 5140 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154

Any Time Modification Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber; 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 incompatibility; SS subscription violation; Information Not Available.

5155 Provider error 5156 These are defined in clause 7.6.1.

5157

8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service

590

591 Release 4 592 593

149

3GPP TS 29.002 V4.17.0 (2006-06)

8.11.5.1

Definition

This service is used by the HLR to inform the gsmSCF that subscriber data have been modified.

8.11.5.2

Service primitives
Table 8.11/5: Note_Subscriber_Data_Modified
Parameter name Invoke id IMSI MSISDN Ext Forwarding information-for-CSE Ext Call barring information-for-CSE ODB Info CAMEL subscription info All Information Sent User error Provider error Request M M M C C C C C Indication M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C C(=) O Response M(=) Confirm M(=)

8.11.5.3
Invoke id

Parameter definition and use

See clause 7.6.1 for the use of this parameter. IMSI See clause 7.6.2 for the use of this parameter. MSISDN See clause 7.6.2 for the use of this parameter. Ext Forwarding information-for-CSE See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078. Ext Call barring information-for-CSE See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078. ODB Info See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078. CAMEL subscription info See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078.
5158 All Information Sent 5159 This parameter is set when the HLR has sent all information to gsmSCF.

User error

594

595 Release 4 596 597

150

3GPP TS 29.002 V4.17.0 (2006-06)

This parameter is sent by the responder when an error is detected and if present, takes one of the following values: Data Missing; Unexpected Data Value; Unknown Subscriber.

5160 5161 5162

Provider error These are defined in clause 7.6.1. The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078.

5163 5164 5165

9 Operation and maintenance services


9.1 Subscriber tracing services
9.1.1 MAP-ACTIVATE-TRACE-MODE service
Definition

5166 9.1.1.1

5167 This service is used between the HLR and the VLR to activate subscriber tracing in the VLR. 5168 Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN. 5169 The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1.

5170 9.1.1.2
5171

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

5172

5173 9.1.1.3
5174 Invoke id

Parameter use

5175 See definition in clause 7.6.1. 5176 IMSI 5177 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 5178 Trace reference 5179 See definition in clause 7.6.10. 5180 Trace type 5181 See definition in clause 7.6.10.

598

5182 OMC Id

599 Release 4 600 601

151

3GPP TS 29.002 V4.17.0 (2006-06)

5183 See definition in clause 7.6.2. The use of this parameter is an operator option. 5184 User error 5185 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5186 5187 5188 5189 5190 5191

Unidentified Subscriber; Facility Not Supported; Tracing Buffer Full; System Failure; Unexpected Data Value; Data missing.

5192 Provider error 5193 For definition of provider errors see clause 7.6.1.

5194 5195 9.1.2.1

9.1.2 MAP-DEACTIVATE-TRACE-MODE service


Definition

5196 This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR. 5197 Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN. 5198 The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2.

5199 9.1.2.2
5200

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

5201

5202 9.1.2.3
5203 Invoke id

Parameter use

5204 See definition in clause 7.6.1. 5205 IMSI 5206 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 5207 Trace reference 5208 See definition in clause 7.6.10. 5209 User error 5210 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5211

Unidentified Subscriber;

602

5212 5213 5214 5215

603 Release 4 604 605

152

3GPP TS 29.002 V4.17.0 (2006-06)

Facility Not Supported; System Failure; Unexpected Data Value; Data missing.

5216 Provider error 5217 For definition of provider errors see clause 7.6.1.

5218 5219 9.1.3.1

9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service


Definition

5220 This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC. 5221 The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3.

5222 9.1.3.2
5223

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(=)

5224

5225 9.1.3.3
5226 Invoke id

Parameter use

5227 See definition in clause 7.6.1. 5228 IMSI 5229 See definition in clause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC. 5230 Trace reference 5231 See definition in clause 7.6.10. 5232 Trace type 5233 See definition in clause 7.6.10. 5234 OMC Id 5235 See definition in clause 7.6.2. The use of this parameter is an operator option.

5236 5237 5238 9.2.1.1

9.2 Other operation and maintenance services


9.2.1 MAP-SEND-IMSI service
Definition

606

5239 This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance 5240 procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber's identity known. 5241 It is a confirmed service and consists of the primitives shown in table 9.2/1.

607 Release 4 608 609

153

3GPP TS 29.002 V4.17.0 (2006-06)

5242 9.2.1.2
5243

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

5244

5245 9.2.1.3
5247 User error

Parameter use

5246 All parameters are described in clause 7.6. The following clarifications are applicable.

5248 Only one of the following values is applicable: 5249 5250 5251

Unknown subscriber; Unexpected data value; Data missing.

5252 5253 5254

10

Call handling services


10.1 MAP_SEND_ROUTING_INFORMATION service
10.1.1 Definition

5255 This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform 5256 the interrogation of the HLR in order to route a call towards the called MS. 5257 This is a confirmed service using the primitives listed in table 10.1/1. 5258 This service is also used between the GMSC and the NPLR.

5259
5260

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 Request M M M M C C C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=)

610

611 Release 4 612 613

154 Request C C C C C C C C C C C C C Indication C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V4.17.0 (2006-06) Response Confirm

Parameter name Suppress T-CSI Suppression of Announcement Call Reference Number Forwarding Reason Basic Service Group Alerting Pattern CCBS Call Supported CCBS Phase Additional Signal Info IST Support Indicator Pre-paging supported Call Diversion Treatment Indicator Long FTN Supported 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 IST Alert Timer Number Portability Status Provider error

C C C C C C C C C C U C U C C C U

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

5261

5262

10.1.3 Parameter use


a conditional parameter whose use is defined only in 3GPP TS 23.078 shall be absent if the sending entity does not support CAMEL; a conditional parameter whose use is defined only in 3GPP TS 23.079 [99] shall be absent if the sending entity does not support optimal routeing; a conditional parameter whose use is defined only in 3GPP TS 23.078 & 3GPP TS 23.079 [99] shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

5263 See clause 7.6 for a definition of the parameters used in addition to the following. Note that: 5264 5265 5266 5267 5268 5269

5270 Interrogation Type 5271 See 3GPP TS 23.079 [99] for the use of this parameter. 5272 GMSC address 5273 The E.164 address of the GMSC. 5274 MSISDN 5275 This is the Mobile Subscriber ISDN number assigned to the called subscriber. In the Request & Indication it is the 5276 number received by the GMSC in the IAM. If the call is to be forwarded and the HLR supports determination of the 5277 redirecting number, the HLR inserts the basic MSISDN in the Response. 5278 See 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence in the response. 5279 OR Interrogation 5280 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence.

614

5281 OR Capability 5282 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5283 CUG Interlock 5284 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5285 CUG Outgoing Access 5286 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5287 Number of Forwarding 5288 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5289 Network Signal Info 5290 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 5291 Supported CAMEL Phases 5292 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5293 T-CSI Suppression 5294 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5295 Suppression Of Announcement 5296 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5297 Call Reference Number 5298 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5299 [99]. 5300 Forwarding Reason 5301 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5302 Basic Service Group 5303 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5304 Alerting Pattern 5305 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5306 CCBS Call 5307 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5308 Supported CCBS Phase 5309 This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported. 5310 Additional Signal Info 5311 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 5312 IST Support Indicator 5313 5314 5315 5316

615 Release 4 616 617

155

3GPP TS 29.002 V4.17.0 (2006-06)

This parameter is used to indicate to the HLR that the GMSC supports basic IST functionality, that is, the GMSC is able to terminate the subscriber call activity that originated the IST Alert when it receives the IST Alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Send Routing Information indication and the subscriber is marked as an IST subscriber, then the HLR may limit the service for the call (by barring the incoming call

618

5317 if it is not subject to forwarding, or suppressing Call Forwarding from the GMSC), or allow the call assuming the 5318 associated risk of not having the basic IST mechanism available. 5319 5320 5321 5322 5323 5324

619 Release 4 620 621

156

3GPP TS 29.002 V4.17.0 (2006-06)

This parameter can also indicate that the GMSC supports the IST Command, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Send Routing Information indication and the subscriber is marked as an IST subscriber, then the HLR may limit the service for the subscriber (by barring the incoming calls if they are not subject to forwarding, or suppressing Call Forwarding from the GMSC), or allow the incoming calls assuming the associated risk of not having the IST Command mechanism available.

5325 Pre-paging supported 5326 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 5327 Call Diversion Treatment Indicator 5328 This parameter indicates whether or not call diversion is allowed. 5329 IMSI 5330 See 3GPP TS 23.018 [97] and 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence. 5331 MSRN 5332 See 3GPP TS 23.018 [97], 3GPP TS 23.066 [108] and 3GPP TS 23.079 [99] for the use of this parameter and the 5333 conditions for its presence. If the NPLR returns only the MSISDN-number without Routeing Number to the GMSC, the 5334 MSISDN-number shall be returned as MSRN. 5335 Forwarding Data 5336 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding 5337 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See 5338 3GPP TS 23.018 [97] and 3GPP TS 23.079 [99] for the conditions for the presence of its components. 5339 Forwarding Interrogation Required 5340 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5341 Long FTN Supported 5342 This parameter indicates that the GMSC supports Long Forwarded-to Numbers. 5343 VMSC address 5344 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5345 GMSC CAMEL Subscription Info 5346 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5347 Location Information 5348 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5349 Subscriber State 5350 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5351 CUG Subscription Flag 5352 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5353 North American Equal Access preferred Carrier Id 5354 This parameter is returned to indicate the preferred carrier identity to be used to set-up the call (i.e. forwarding the call 5355 or establishing the roaming leg).

622

5356 SS-List 5357 5358 5359 5360

623 Release 4 624 625

157

3GPP TS 29.002 V4.17.0 (2006-06)

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.

5361 Basic Service Code 5362 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5363 5364 5365 5366 5367

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.

5368 CCBS Target 5369 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5370 Keep CCBS Call Indicator 5371 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5372 IST Alert Timer 5373 It includes the IST Alert timer value that must be used to inform the HLR about the call activities that the subscriber 5374 performs. This parameter is only sent to the GMSC in response to a Send Routing Information request which indicates 5375 the the GMSC supports IST. 5376 Number Portability Status 5377 This parameter indicates the number portability status of the subscriber. This parameter may be present if the sender of 5378 SRIack is NPLR. 5379 User error 5380 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395

Unknown Subscriber; The diagnostic for the Unknown Subscriber error may indicate NPDB Mismatch.

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 3GPP TS 22.041 [8] 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;

626

5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414

627 Release 4 628 629

158

3GPP TS 29.002 V4.17.0 (2006-06)

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; 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.

5415 See clause 7.6 for a definition of these errors. 5416 Provider error 5417 These are defined in clause 7.6.

5418 5419

10.2 MAP_PROVIDE_ROAMING_NUMBER service


10.2.1 Definition

5420 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a 5421 roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. 5422 This is a confirmed service which uses the primitives described in table 10.2/1.

5423
5424

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 Request M M M U C C C C C C C C Indication M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

630

631 Release 4 632 633

159 Request C C C C C C Indication C(=) C(=) C(=) C(=) C(=) C(=) C C

3GPP TS 29.002 V4.17.0 (2006-06) Response Confirm

Parameter name Alerting Pattern CCBS Call Supported CAMEL Phases in GMSC Additional Signal Info Pre-paging supported Long FTN Supported Roaming Number User error Provider error

C(=) C(=) O

5425

5426

10.2.3 Parameter use


a conditional parameter whose use is defined only in 3GPP TS 23.078 shall be absent if the sending entity does not support CAMEL; a conditional parameter whose use is defined only in 3GPP TS 23.079 [99] shall be absent if the sending entity does not support optimal routeing; a conditional parameter whose use is defined only in 3GPP TS 23.078 & 3GPP TS 23.079 [99] shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

5427 See clause 7.6 for a definition of the parameters used, in addition to the following. Note that: 5428 5429 5430 5431 5432 5433

5434 IMSI 5435 This is the IMSI of the called Subscriber. 5436 MSC Number 5437 This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the 5438 HLR as provided at location updating. 5439 MSISDN 5440 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5441 LMSI 5442 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5443 GSM Bearer Capability 5444 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5445 This information is passed according to the rules specified in TS 3GPP TS 29.007 [56]. 5446 There may be two GSM Bearer Capabilities supplied. 5447 Network Signal Info 5448 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 5449 Suppression Of Announcement 5450 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5451 Call Reference Number 5452 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5453 [99]. 5454 GMSC Address

634

5455 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5456 [99]. 5457 OR Interrogation 5458 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5459 OR Not Supported in GMSC 5460 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5461 Supported CAMEL Phases in GMSC 5462 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5463 Alerting Pattern 5464 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5465 CCBS Call 5466 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5467 Additional Signal Info 5468 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 5469 Pre-paging supported 5470 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 5471 Long FTN supported 5472 See 3GPP TS 23.082 for the use of this parameter and the conditions for its presence. 5473 Roaming Number 5474 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5475 User error 5476 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486

635 Release 4 636 637

160

3GPP TS 29.002 V4.17.0 (2006-06)

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.

5487 See clause 7.6 for a definition of these reasons. 5488 Provider error 5489 These are defined in clause 7.6.

638

639 Release 4 640 641

161

3GPP TS 29.002 V4.17.0 (2006-06)

5490 5491

10.3 MAP_RESUME_CALL_HANDLING service


10.3.1 Definition

5492 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC 5493 to request the GMSC to resume handling the call and forward it to the specified destination. 5494 This is a confirmed service which uses the Primitives listed in table 10.3/1.

5495
5496

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 D-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 C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=) O

5497

5498

10.3.3 Parameter use

5499 Information received in subsequent segment of a segmented dialogue shall not overwrite information received in an 5500 earlier segment. 5501 See clause 7.6 for a definition of the parameters used, in addition to the following. 5502 Call Reference Number 5503 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in a first segment of the 5504 dialogue. 5505 Basic Service Group 5506 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in a first segment of the 5507 dialogue. 5508 IMSI 5509 This is the IMSI of the forwarding Subscriber. This parameter shall be present in a first segment of the dialogue. 5510 Forwarding Data 5511 5512 5513 5514

This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See 3GPP TS 23.079 [99] for the conditions for the presence of its components. This parameter shall be present in a first segment of the dialogue.

5515 CUG Interlock

642

5516 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5517 CUG Outgoing Access 5518 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5519 O-CSI 5520 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 5521 For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data. 5522 D-CSI 5523 The Dialled Services-CSI. 5524 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 5525 CCBS Target 5526 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5527 UU Data 5528 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 5529 UUS CF Interaction 5530 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 5531 All Information Sent 5532 This parameter is set when the VMSC has sent all information to GMSC. 5533 MSISDN 5534 This parameter is the basic MSISDN of the forwarding subscriber. It shall be present if the VMSC supports 5535 determination of the redirecting number. 5536 User error 5537 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5538 5539 5540 5541

643 Release 4 644 645

162

3GPP TS 29.002 V4.17.0 (2006-06)

Optimal Routeing not allowed; Forwarding failed; Unexpected Data Value; Data Missing.

5542 Provider error 5543 These are defined in clause 7.6.

5544 5545

10.4 MAP_PREPARE_GROUP_CALL service


10.4.1 Definition

5546 This service is used by the Anchor_MSC to inform the Relay_MSC about a group call set-up. 5547 The MAP_PREPARE_GROUP_CALL service is a confirmed service using the service primitives given in table 10.4/1.

646

5548

647 Release 4 648 649

163

3GPP TS 29.002 V4.17.0 (2006-06)

10.4.2 Service primitives


Table 10.4/1: MAP_PREPARE_GROUP_CALL service
Request M M M M C C C M M Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) M(=) M(=) Response M(=) Confirm M(=)

5549

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

M C

M(=) C(=) O

5550

5551
5552 Invoke Id

10.4.3 Parameter definitions and use

5553 See definition in clause 7.6.1. 5554 Teleservice 5555 Voice Broadcast Service or Voice Group Call Service. 5556 ASCI Call Reference 5557 Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the 5558 Relay_MSC. 5559 Ciphering Algorithm 5560 The ciphering algorithm to be used for the group call. 5561 Group Key Number 5562 This number has to be broadcasted and is used by the mobile station to select the chosen group key. 5563 Shall be present if the ciphering applies. 5564 Group Key 5565 This key is used for ciphering on the radio interface. 5566 Shall be present if the ciphering applies. 5567 Priority 5568 Default priority level related to the call if eMLPP applies. 5569 CODEC-Information 5570 Information on the codecs allowed for this call. 5571 Uplink Free Indicator 5572 A flag indicating whether the call is initiated from a dispatcher. 5573 Group Call Number 5574 This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC.

650

5575 User Error 5576 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on 5577 the nature of the fault: 5578 5579 5580

651 Release 4 652 653

164

3GPP TS 29.002 V4.17.0 (2006-06)

No Group Call Number available; System Failure; Unexpected Data Value.

5581 Provider Error 5582 See definition of provider error in clause 7.6.1.

5583 5584 5585

10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service


10.5.1 Definitions

5586 This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications. 5587 The MAP_PROCESS_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives 5588 given in table 10.5/1.

5589
5590

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(=)

5591

5592
5593 Invoke Id

10.5.3 Parameter definitions and use

5594 See definition in clause 7.6.1 5595 Uplink Request 5596 This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests 5597 access to the uplink. 5598 Uplink Release Indication 5599 This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free. 5600 Release Group Call 5601 This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who 5602 has initiated the call and who currently has access to the uplink terminates the call.

5603 5604

10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service

654

5605

655 Release 4 656 657

165

3GPP TS 29.002 V4.17.0 (2006-06)

10.6.1 Definitions

5606 This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications. 5607 The MAP_FORWARD_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service 5608 primitives given in table 10.6/1.

5609
5610

10.6.2 Service primitives


Table 10.6/1: 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 State Attributes Request M C C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

5611

5612
5613 IMSI

10.6.3 Parameter definitions and use

5614 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 5615 Invoke Id 5616 See definition in clause 7.6.1. 5617 Uplink Request Acknowledgement 5618 This information element is used for positive acknowledgement of an uplink request. 5619 Uplink Release Indication 5620 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free. 5621 Uplink Reject Command 5622 This information element is used for negative acknowledgement of an uplink request. 5623 Uplink Seized Command 5624 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free. 5625 Uplink Release Command 5626 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted 5627 to a MS in the relay MSC area shall be released. 5628 State Attributes 5629 This information element is used to allow service logic running in an Anchor MSC to mute a VGCS talker even when 5630 the talker is served on a Relay MSC. The IE is used to build a GCC message that provides a mechanism to induce the 5631 VGCS talker terminal to mute/unmute the downlink at the Anchor MSC, as defined in 3GPP TS 44.068.

5632

10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service

658

5633

659 Release 4 660 661

166

3GPP TS 29.002 V4.17.0 (2006-06)

10.7.1 Definitions

5634 This service is used between the Relay MSC and the Anchor MSC indicating that VGCS / VBS channels have been 5635 established in the Relay MSC area. The response is used by the Anchor MSC to inform the Relay MSC that all 5636 resources for the call can be released in the Relay MSC because the call has been released in the Anchor MSC. 5637 The MAP_SEND_GROUP_CALL_END_SIGNAL service is a confirmed service using the service primitives given in 5638 table 10.7/1.

5639
5640

10.7.2 Service primitives


Table 10.7/1: 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

5641

5642
5643 IMSI

10.7.3 Parameter definitions and use

5644 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 5645 Shall be present if the call was established by a service subscriber roaming in the relay MSC area. 5646 Invoke Id 5647 See definition in clause 7.6.1 5648 Provider Error 5649 See definition of provider error in clause 7.6.1.

5650 5651

10.8 MAP_Provide_SIWFS_Number
10.8.1 Definition

5652 This service is used between an MSC and SIWFS. It is invoked by an MSC receiving an incoming call (call to or from 5653 MS) to request the SIWFS to allocate IWU resources. The service is defined in GSM 03.54. 5654 This is a confirmed service using the primitives described in table 10.8/1.

5655
5656

10.8.2 Service primitive


Table 10.8/1: 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

662

5657

663 Release 4 664 665

167

3GPP TS 29.002 V4.17.0 (2006-06)

5658

10.8.3 Parameter use

5659 See clause 7.6 for a definition of the parameters used, in addition to the following. 5660 GSM Bearer Capability 5661 This information is the result from the negotiation with the mobile station. The information is sent from the MSC to the 5662 SIWFS to allocate the correct IWU. 5663 ISDN Bearer Capability 5664 5665 5666 5667

This parameter refers to the ISDN Bearer Capability information element. For the MTC this parameter is received in the ISUP User Service Information parameter. For the MOC call this parameter is mapped from the GSM BC parameter according to 3GPP TS 29.007 [56]. The parameter is used by the SIWFS to route the call and to allocate the outgoing circuit.

5668 Call Direction 5669 This parameter indicates the direction of the call (mobile originated or mobile terminated) at call set-up. 5670 B-subscriber address 5671 5672 5673 5674

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.

5675 Chosen Channel 5676 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 5677 parameter is defined in 3GPP TS 48.008 [49]. 5678 Lower Layer Compatibility 5679 This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This 5680 parameter is handled as specified in 3GPP TS 29.007 [56]. This parameter is defined in 3GPP TS 24.008 [35]. 5681 High Layer Compatibility 5682 This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This 5683 parameter is handled as specified in 3GPP TS 29.007 [56]. This parameter is defined in 3GPP TS 24.008 [35]. 5684 SIWFS number 5685 5686 5687 5688

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.

5689 User error 5690 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5691 5692 5693 5694

Resource limitation; Facility Not Supported; Unexpected Data Value; System Failure.

5695 See clause 7.6 for a definition of these reasons. 5696 Provider error

666

5697 These are defined in clause 7.6.

667 Release 4 668 669

168

3GPP TS 29.002 V4.17.0 (2006-06)

5698 5699

10.9 MAP_SIWFS_Signalling_Modify
10.9.1 Definition

5700 This service is used to transport signalling information between an MSC and an SIWFS in the case of a request to 5701 modify the configuration (e.g. HSCSD). It is invoked either by an MSC or by the SIWFS. The service is defined in 5702 GSM 03.54. 5703 This is a confirmed service using the primitives described in table 10.9/1.

5704
5705

10.9.2 Service primitive


Table 10.9/1: 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

5706

5707

10.9.3 Parameter use

5708 See clause 7.6 for a definition of the parameter used, in addition to the following. 5709 Channel Type 5710 This parameter is the result of a Channel Mode Modification for TS61/62. It contains the changed Air Interface User 5711 Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is 5712 defined in 3GPP TS 48.008 [49]. 5713 Chosen Channel 5714 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 5715 parameter is defined in 3GPP TS 48.008 [49]. 5716 User error 5717 This parameter is sent by the responder when an error is detected and if present , takes one of the following values: 5718 5719 5720 5721 5722

Resource limitation; Facility Not Supported; Data Missing; Unexpected Data Value; System Failure.

5723 See clause 7.6 for a definition of these reasons. 5724 Provider error 5725 These are defined in clause 7.6.

670

671 Release 4 672 673

169

3GPP TS 29.002 V4.17.0 (2006-06)

5726 5727

10.10 MAP_SET_REPORTING_STATE service


10.10.1 Definition

5728 This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed 5729 service using the service primitives shown in table 10.10/1.

5730
5731

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(=)

C C

C(=) C(=) O

5732

5733

10.10.3 Parameter use

5734 See clause 7.6 for a definition of the parameters used, in addition to the following. 5735 IMSI 5736 The IMSI is a mandatory parameter if the service is used as the only one in a dialogue. 5737 CCBS Monitoring 5738 This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall 5739 be started this service corresponds to the message 'Start Reporting' in 3GPP TS 23.093 [107]; if it indicates that 5740 monitoring shall be stopped this service corresponds to the message 'Stop Reporting' in 3GPP TS 23.093 [107]. 5741 CCBS Subscriber Status 5742 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5743 User error 5744 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5745 values defined in clause 7.6.1: 5746 5747 5748 5749 5750 5751 5752

System Failure; Unidentified Subscriber; Unexpected Data Value; Data Missing; Resource Limitation; Facility Not Supported. This error is reserved for future use.

NOTE:

5753 Provider error 5754 These are defined in clause 7.6.

674

675 Release 4 676 677

170

3GPP TS 29.002 V4.17.0 (2006-06)

5755 5756

10.11 MAP_STATUS_REPORT service


10.11.1 Definition

5757 This service is used by the VLR to report an event or call outcome to the HLR. It is a confirmed service using the 5758 service primitives shown in table 10.11/1.

5759
5760

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(=) Response M(=) Confirm M(=)

C(=) O

5761

5762

10.11.3 Parameter use

5763 See clause 7.6 for a definition of the parameters used, in addition to the following. 5764 CCBS Subscriber Status 5765 If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message 'Event 5766 Report' in 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its 5767 presence. 5768 Monitoring Mode 5769 If this parameter is present with CCBS Call Outcome this service corresponds to the message 'CCBS Call Report' in 5770 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5771 Call Outcome 5772 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5773 User error 5774 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5775 values defined in clause 7.6.1: 5776 5777 5778 5779

Unknown Subscriber; System Failure; Unexpected Data Value; Data Missing.

5780 Provider error 5781 These are defined in clause 7.6.

678

679 Release 4 680 681

171

3GPP TS 29.002 V4.17.0 (2006-06)

5782 5783

10.12 MAP_REMOTE_USER_FREE service


10.12.1 Definition

5784 This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber 5785 can be notified. It is a confirmed service using the service primitives shown in table 10.12/1.

5786
5787

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(=)

C C

C(=) C(=) O

5788

5789

10.12.3 Parameter use

5790 See clause 7.6 for a definition of the parameters used, in addition to the following. 5791 Call Info 5792 See 3GPP TS 23.093 [107] for the use of this parameter. 5793 CCBS Feature 5794 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 5795 Translated B Number 5796 See 3GPP TS 23.093 [107] for the use of this parameter. 5797 Replace B Number 5798 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5799 Alerting Pattern 5800 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5801 RUF Outcome 5802 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5803 User error 5804 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5805 values defined in clause 7.6.1: 5806 5807 5808

Unexpected Data Value; Data Missing; Incompatible Terminal;

682

5809 5810 5811 5812 5813

683 Release 4 684 685

172

3GPP TS 29.002 V4.17.0 (2006-06)

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 3GPP TS 24.008 [35]; Absent Subscriber (IMSI Detach; Restricted Area; No Page Response); System Failure; Busy Subscriber (CCBS Busy).

5814 Provider error 5815 These are defined in clause 7.6.

5816 5817

10.13 MAP_IST_ALERT service


10.13.1 Definition

5818 This service is used between the MSC (Visited MSC or Gateway MSC) and the HLR, to report that the IST timer 5819 running for a call for the Subscriber has expired. It is a confirmed service using the service primitives shown in 5820 table 10.13/1.

5821
5822

10.13.2 Service primitives


Table 10.13/1: MAP_IST_ALERT parameters
Parameter name Invoke Id IMSI IST Alert Timer IST Information Withdraw Call termination Indicator User error Provider error Request M M Indication M(=) M(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=) O

5823

5824

10.13.3 Parameter use

5825 All parameters are described in clause 7.6. The following clarifications are applicable: 5826 IST Alert Timer 5827 If included in the IST Alert response, it includes the new IST Alert timer value that must be used to inform the HLR 5828 about the call activities that the subscriber performs. 5829 IST Information Withdraw 5830 If included in the IST Alert response, this parameter is used to indicate that the IST condition has been removed for the 5831 subscriber. When the MSC receives this parameter, IST control for that call shall be terminated. 5832 Call termination Indicator 5833 5834 5835 5836 5837

If included in the IST Alert response, this parameter is used to indicate whether the MSC shall terminate the call activity that had previously triggered the IST Alert procedure, or it shall also release all other call activities for the specified subscriber (outgoing call activities if the IST Alert is initiated by the VMSC, or incoming call activities if the IST Alert is initiated by the GMSC). Release of all other call activities is possible only if the MSC has the capability to link the call activities for the Subscriber by using the IMSI as key.

5838 User error 5839 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5840

System Failure;

686

5841 5842 5843 5844

687 Release 4 688 689

173

3GPP TS 29.002 V4.17.0 (2006-06)

Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.

5845 5846

10.14 MAP_IST_COMMAND service


10.14.1 Definition

5847 This service is used by the HLR to instruct the MSC (Visited MSC or Gateway MSC) to terminate ongoing call 5848 activities for a specific subscriber. It is a confirmed service using the service primitives shown in table 10.14/1.

5849
5850

10.14.2 Service primitives


Table 10.14/1: MAP_IST_COMMAND parameters
Parameter name Invoke Id IMSI User error Provider error Request M M Indication M(=) M(=) Response M(=) C Confirm M(=) C(=) O

5851

5852

10.14.3 Parameter use

5853 All parameters are described in clause 7.6. The following clarifications are applicable: 5854 User error 5855 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5856 5857 5858 5859 5860

System Failure; Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.

5861 5862 5863

11

Supplementary services related services


11.1 MAP_REGISTER_SS service
11.1.1 Definition

5864 This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a 5865 supplementary service. The VLR will relay the message to the HLR. 5866 The service is a confirmed service and uses the service primitives shown in table 11.1./1.

690

5867

691 Release 4 692 693

174

3GPP TS 29.002 V4.17.0 (2006-06)

11.1.2 Service primitives


Table 11.1/1: MAP_REGISTER_SS parameters
Request M M C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

5868

Parameter name Invoke id SS-Code Basic service Forwarded-to number with subaddress No reply condition time EMLPP default priority Long FTN Supported NbrUser Forwarding information User error Provider error

C C C C

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

5869

5870
5871 Invoke id

11.1.3 Parameter use

5872 See clause 7.6.1 for the use of this parameter. 5873 SS-Code 5874 This parameter indicates the supplementary service which the mobile subscriber wants to register. 5875 Basic service 5876 This parameter indicates for which basic service group the supplementary service is to be registered. If it is not 5877 included, the registration request applies to all basic services. 5878 Forwarded-to number with subaddress 5879 This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can 5880 optionally include a sub-address. 5881 No reply condition time 5882 This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a 5883 superset of this service) and the mobile subscriber supplies a value for this time. 5884 EMLPP default priority 5885 This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at 5886 successful outcome of the service. 5887 Long FTN Supported 5888 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 5889 NbrUser 5890 This parameter is sent by the initiator to register the MC maximum number of user defined circuit switched bearers to 5891 be used. 5892 Forwarding information 5893 This parameter is returned by the responder at successful outcome of the service, if the registration request concerned 5894 one or a group of Call Forwarding supplementary services.

694

5895 User error

695 Release 4 696 697

175

3GPP TS 29.002 V4.17.0 (2006-06)

5896 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5897 values defined in clause 7.6.1: 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908

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.

5909 Provider error 5910 See clause 7.6.1 for the use of this parameter.

5911 5912

11.2 MAP_ERASE_SS service


11.2.1 Definition

5913 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a 5914 supplementary service. The VLR will relay the message to the HLR. 5915 The service is a confirmed service and uses the service primitives shown in table 11.2/1.

5916
5917

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(=) Confirm M(=)

C C

C(=) C(=) O

5918

5919
5920 Invoke id

11.2.3 Parameter use

5921 See clause 7.6.1 for the use of this parameter. 5922 SS-Code 5923 This parameter indicates the supplementary service which the mobile subscriber wants to erase.

698

5924 Basic service 5925 This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, 5926 the erasure request applies to all basic services. 5927 Forwarding information 5928 This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or 5929 a group of Call Forwarding supplementary services. 5930 User error 5931 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5932 values, defined in clause 7.6.1: 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942

699 Release 4 700 701

176

3GPP TS 29.002 V4.17.0 (2006-06)

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.

5943 Provider error 5944 See clause 7.6.1 for the use of this parameter.

5945 5946

11.3 MAP_ACTIVATE_SS service


11.3.1 Definition

5947 This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary 5948 service. The VLR will relay the message to the HLR. 5949 The service is a confirmed service and uses the service primitives shown in table 11.3/1.

5950
5951

11.3.2 Service primitives


Table 11.3/1: MAP_ACTIVATE_SS parameters
Parameter name Invoke id SS-Code Long FTN Supported Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C C C C

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

5952

702

5953

703 Release 4 704 705

177

3GPP TS 29.002 V4.17.0 (2006-06)

11.3.3 Parameter use

5954 Invoke id 5955 See clause 7.6.1 for the use of this parameter. 5956 SS-Code 5957 This parameter indicates the supplementary service which the mobile subscriber wants to activate. 5958 Basic service 5959 This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it 5960 is not included, the activation request applies to all basic services. 5961 Forwarding information 5962 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 5963 Call Forwarding. 5964 Long FTN Supported 5965 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 5966 Call barring information 5967 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 5968 Call Barring. 5969 SS-Data 5970 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for 5971 example Call Waiting. 5972 User error 5973 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5974 values, defined in clause 7.6.1: 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988

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.

706

5989 Provider error 5990 See clause 7.6.1 for the use of this parameter.

707 Release 4 708 709

178

3GPP TS 29.002 V4.17.0 (2006-06)

5991 5992

11.4 MAP_DEACTIVATE_SS service


11.4.1 Definitions

5993 This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary 5994 service. The VLR will relay the message to the HLR. 5995 The service is a confirmed service and uses the service primitives shown in table 11.4/1.

5996
5997

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(=) Confirm M(=)

C C C C

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

5998

5999
6000 Invoke id

11.4.3 Parameter use

6001 See clause 7.6.1 for the use of this parameter. 6002 SS-Code 6003 This parameter indicates the supplementary service which the mobile subscriber wants to deactivate. 6004 Basic service 6005 This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If 6006 it is not included the deactivation request applies to all basic services. 6007 Forwarding information 6008 This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned 6009 one or a group of Call Forwarding supplementary services. 6010 Call barring information 6011 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one 6012 or a group of Call Barring supplementary services. 6013 SS-Data 6014 This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request 6015 concerned the Call Waiting supplementary service.

710

6016 User error

711 Release 4 712 713

179

3GPP TS 29.002 V4.17.0 (2006-06)

6017 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6018 values, defined in clause 7.6.1: 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031

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.

6032 Provider error 6033 See clause 7.6.1 for the use of this parameter.

6034 6035

11.5 MAP_INTERROGATE_SS service


11.5.1 Definitions

6036 This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related 6037 to a supplementary service. The VLR will relay the message to the HLR if necessary. 6038 The service is a confirmed service and consists of four service primitives.

6039

11.5.2 Service primitives


Table 11.5/1: MAP_INTERROGATE_SS parameters
Parameter name Invoke id SS-Code Basic service Long FTN Supported SS-Status Basic service Group LIST Forwarding feature LIST CLI restriction Info EMLPP Info MC Information CCBS Feature LIST User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

6040 The service primitives are shown in table 11.5/1. 6041

C C C C C C C C

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

714

6042

715 Release 4 716 717

180

3GPP TS 29.002 V4.17.0 (2006-06)

6043

11.5.3 Parameter use

6044 For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications. 6045 Invoke id 6046 See clause 7.6.1 for the use of this parameter. 6047 SS-Code 6048 The mobile subscriber can only interrogate a single supplementary service per service request. 6049 Basic service 6050 This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not 6051 included, the interrogation request applies to all basic services. 6052 SS-Status 6053 This parameter is included by the responder if: 6054 6055 6056 6057 6058

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.

6059 Basic service group LIST 6060 This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary 6061 service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) 6062 basic service groups, the SS-Status parameter is returned. 6063 Long FTN Supported 6064 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6065 Forwarding feature LIST 6066 The forwarding feature parameter is described in clause 7.6.4. A list of one or more forwarding features is returned by 6067 the responder when the interrogation request applied to Call Forwarding supplementary service. 6068 If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all 6069 provisioned basic services. 6070 CLI restriction Info 6071 The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR 6072 supplementary service. 6073 EMLPP Info 6074 The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation 6075 request applies to the eMLPP supplementary service. 6076 MC Information 6077 The MC information (NbrSB, NbrUser and NbrSN) is returned by the responder if the interrogation request applies to 6078 the MC supplementary service. For a definition of these 3 components, refer to 3GPP TS 23.135 and 3GPP TS 24.135.

718

6079 CCBS Feature LIST 6080 The CCBS feature parameter is described in clause 7.6. A list of one or more CCBS features is returned by the 6081 responder when the interrogation request applied to the CCBS supplementary service. See 3GPP TS 23.093 [107] for 6082 the conditions for the presence of the parameters included in the CCBS feature. 6083 User error 6084 This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the 6085 following values, defined in clause 7.6.1: 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095

719 Release 4 720 721

181

3GPP TS 29.002 V4.17.0 (2006-06)

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.

6096 Provider error 6097 See clause 7.6.1 for the use of this parameter.

6098 6099

11.6 MAP_INVOKE_SS service


11.6.1 Definitions

6100 This service is used between the MSC and the VLR to check the subscriber's subscription to a given supplementary 6101 service in the VLR, in connection with in-call invocation of that supplementary service, i.e. after the call set-up phase is 6102 finished. For supplementary service invocation during call set-up phase, please refer to the call handling descriptions. 6103 The service is a confirmed service and consists of four service primitives.

6104

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

6105 The service primitives are shown in table 11.6/1. 6106

6107

722

6108

723 Release 4 724 725

182

3GPP TS 29.002 V4.17.0 (2006-06)

11.6.3 Parameter use

6109 Invoke id 6110 See clause 7.6.1 for the use of this parameter. 6111 SS-Code 6112 This SS-Code can only refer to a single supplementary service, e.g. the Call Hold or Multi Party supplementary 6113 services. 6114 Basic service 6115 This parameter indicates for which basic service the supplementary service invocation is required. 6116 User error 6117 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6118 values: 6119 6120 6121 6122 6123 6124 6125

System Failure; Data Missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS not available.

6126 Provider error 6127 See clause 7.6.1 for the use of this parameter.

6128 6129

11.7 MAP_REGISTER_PASSWORD service


11.7.1 Definitions

6130 This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber 6131 requests to register a new password. The VLR will relay the message to the HLR. 6132 The service is a confirmed service and consists of four service primitives.

6133

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

6134 The service primitives are shown in table 11.7/1. 6135

6136

726

6137

727 Release 4 728 729

183

3GPP TS 29.002 V4.17.0 (2006-06)

11.7.3 Parameter use

6138 Invoke id 6139 See clause 7.6.1 for the use of this parameter. 6140 SS-Code 6141 This parameter indicates for which supplementary service(s) the password should be registered. 6142 New Password 6143 See clause 7.6.4 for the use of this parameter. 6144 User error 6145 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6146 values, defined in clause 7.6.1: 6147 6148 6149 6150 6151 6152 6153 6154

System failure; Data Missing; Unexpected data value; Call Barred; SS subscription violation; Password registration failure; Negative PW check; Number Of PW Attempts Violation.

6155 Provider error 6156 See clause 7.6.1 for the use of this parameter.

6157 6158

11.8 MAP_GET_PASSWORD service


11.8.1 Definitions

6159 This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a 6160 request from the mobile subscriber for an operation on a supplementary service which requires a password from the 6161 subscriber. The VLR will relay the message to the MSC. 6162 The service is a confirmed service and uses the service primitives shown in table 11.8/1.

6163
6164

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(=) Confirm M(=)

M(=) O

6165

730

6166

731 Release 4 732 733

184

3GPP TS 29.002 V4.17.0 (2006-06)

11.8.3 Parameter use

6167 Invoke id 6168 See clause 7.6.1 for the use of this parameter. 6169 Linked Id 6170 See clause 7.6.1 for the use of this parameter. If the MAP_GET_PASSWORD service is used in conjunction with the 6171 MAP_REGISTER_PASSWORD service, this parameter must be present; otherwise it must be absent. 6172 Guidance info 6173 See clause 7.6.4 for the use of this parameter. 6174 Current password 6175 See clause 7.6.4 for the use of this parameter. 6176 Provider error 6177 See clause 7.6.1 for the use of this parameter.

6178 6179 6180

11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service


11.9.1 Definitions

6181 This service is used between the MSC and the VLR, between the VLR and the HLR, between the HLR and gsmSCF 6182 and between the HLR and HLR to relay information in order to allow unstructured supplementary service operation. 6183 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from 6184 table 11.9/1.

6185
6186

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

6187

6188
6189 Invoke id

11.9.3 Parameter use

6190 See clause 7.6.1 for the use of this parameter. 6191 USSD Data Coding Scheme 6192 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the 6193 unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be 6194 present.

734

6195 USSD String 6196 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the 6197 unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme 6198 parameter has to be present. 6199 MSISDN 6200 The subscribers basic MSISDN. 6201 See definition in clause 7.6.2. The MSISDN is included as an operator option, e.g. to allow addressing the subscribers 6202 data in the gsmSCF with the MSISDN. 6203 User error 6204 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6205 values defined in clause 7.6.1: 6206 6207 6208 6209 6210 6211

735 Release 4 736 737

185

3GPP TS 29.002 V4.17.0 (2006-06)

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.

6212 Provider error 6213 See clause 7.6.1 for the use of this parameter.

6214 6215

11.10 MAP_UNSTRUCTURED_SS_REQUEST service


11.10.1 Definitions

6216 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6217 when the invoking entity requires information from the mobile user, in connection with unstructured supplementary 6218 service handling. 6219 The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.10/1.

6220
6221

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

6222

6223
6224 Invoke id

11.10.3 Parameter use

6225 See clause 7.6.1 for the use of this parameter.

738

6226 USSD Data Coding Scheme 6227 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6228 user's MMI input. If this parameter is present, then the USSD String parameter has to be present. 6229 USSD String 6230 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6231 user's MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. 6232 Alerting Pattern 6233 See clause 7.6.3 for the use of this parameter. 6234 User error 6235 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6236 values defined in clause 7.6.1: 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247

739 Release 4 740 741

186

3GPP TS 29.002 V4.17.0 (2006-06)

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.

6248 Provider error 6249 See clause 7.6.1 for the use of this parameter.

6250 6251

11.11 MAP_UNSTRUCTURED_SS_NOTIFY service


11.11.1 Definitions

6252 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6253 when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured 6254 supplementary services handling. 6255 The MAP_UNSTRUCTURED_SS_NOTIFY service is a confirmed service using the primitives from table 11.11/1.

742

6256

743 Release 4 744 745

187

3GPP TS 29.002 V4.17.0 (2006-06)

11.11.2 Service primitives


Table 11.11/1: MAP_UNSTRUCTURED_SS_NOTIFY parameters
Request M M M C Indication M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

6257

Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error

C(=) O

6258

6259
6260 Invoke id

11.11.3 Parameter use

6261 See clause 7.6.1 for the use of this parameter. 6262 USSD Data Coding Scheme: 6263 See clause 7.6.4 for the use of this parameter. 6264 USSD String: 6265 See clause 7.6.1 for the use of this parameter. 6266 Alerting Pattern 6267 See clause 7.6.3 for the use of this parameter. 6268 User error 6269 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6270 values defined in clause 7.6.1: 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281

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.

6282 Provider error 6283 See clause 7.6.1 for the use of this parameter.

746

747 Release 4 748 749

188

3GPP TS 29.002 V4.17.0 (2006-06)

6284 6285

11.12 MAP_SS_INVOCATION_NOTIFY
11.12.1 Definition

6286 This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following 6287 supplementary services; Call Deflection (CD), Explicit Call Transfer (ECT) or Multi Party (MPTY). 6288 This service is used between the HLR and the gsmSCF when the subscriber invokes the CCBS supplementary service.

6289

11.12.2 Service primitives


Table 11.12/1: SS_INVOCATION_NOTIFY parameters
Parameter name Invoke id MSISDN IMSI SS- event SS- event data B-subscriber Number CCBS Request State User error Provider error Request M M M M C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

6290 The service primitives are shown in table 11.12/1. 6291

C(=) O

6292

6293

11.12.3 Parameter use

6294 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are 6295 specified in 3GPP TS 23.078. 6296 User error 6297 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6298 6299 6300

Data Missing; Unexpected Data Value; Unknown Subscriber.

6301 Provider error 6302 This is defined in clause 7.6.1.

6303 6304

11.13 MAP_REGISTER_CC_ENTRY service


11.13.1 Definition

6305 This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested 6306 call completion supplementary service. The VLR will relay the message to the HLR. 6307 The service is a confirmed service and uses the service primitives shown in table 11.13/1.

750

6308

751 Release 4 752 753

189

3GPP TS 29.002 V4.17.0 (2006-06)

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(=)

6309

C(=) O

6310

6311

11.13.3 Parameter use

6312 See clause 7.6 for a definition of the parameters used, in addition to the following. 6313 SS-Code 6314 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an 6315 entry. 6316 CCBS Feature 6317 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 6318 Translated B Number 6319 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6320 Service Indicator 6321 This parameter corresponds to the parameters 'Presentation Indicator' and 'CAMEL Invoked' in 3GPP TS 23.093 [107]. 6322 It indicates which services have been invoked for the original call (e.g. CLIR, CAMEL). See 3GPP TS 23.093 [107] for 6323 the use of this parameter and the conditions for its presence. 6324 Call Info 6325 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6326 Network Signal Info 6327 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6328 User error 6329 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6330 values, defined in clause 7.6.1: 6331 6332 6333 6334 6335 6336 6337

System failure; Data missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS incompatibility.

754

6338 6339 6340 6341

755 Release 4 756 757

190

3GPP TS 29.002 V4.17.0 (2006-06)

Short Term Denial; Long Term Denial; Facility Not Supported; This error is reserved for future use.

NOTE:

6342 Private Extensions shall not be sent with these user errors for this operation. 6343 Provider error 6344 See clause 7.6.1 for the use of this parameter.

6345 6346

11.14 MAP_ERASE_CC_ENTRY service


11.14.1 Definition

6347 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call 6348 completion supplementary service. The VLR will relay the message to the HLR. 6349 The service is a confirmed service and uses the service primitives shown in table 11.14/1.

6350
6351

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

6352

6353

11.14.3 Parameter use

6354 See clause 7.6 for a definition of the parameters used, in addition to the following. 6355 SS-Code 6356 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an 6357 entry/entries. 6358 CCBS Index 6359 See 3GPP TS 23.093 [107] for the use of this parameter and the condition for its presence. 6360 SS-Status 6361 Depending on the outcome of the service request this parameter may indicate either provisioned and active or not 6362 provisioned. 6363 User error 6364 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6365 values, defined in clause 7.6.1: 6366 6367

System failure; Data Missing;

758

6368 6369 6370 6371

759 Release 4 760 761

191

3GPP TS 29.002 V4.17.0 (2006-06)

Unexpected data value; Call Barred; Illegal SS operation; SS error status.

6372 Private Extensions shall not be sent with these user errors for this operation. 6373 Provider error 6374 See clause 7.6.1 for the use of this parameter.

6375 6376 6377

12

Short message service management services


12.1 MAP-SEND-ROUTING-INFO-FOR-SM service
12.1.1 Definition

6378 This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the 6379 short message to the servicing MSC. 6380 The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1.

6381
6382

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(=)

C C C C C C

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

6383

6384
6385 Invoke id

12.1.3 Parameter use

6386 See definition in clause 7.6.1. 6387 MSISDN 6388 See definition in clause 7.6.2. 6389 SM-RP-PRI 6390 See definition in clause 7.6.8.

762

6391 Service Centre Address 6392 See definition in clause 7.6.2. 6393 SM-RP-MTI 6394 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6395 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6396 layer protocol. 6397 SM-RP-SMEA 6398 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6399 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6400 layer protocol. 6401 GPRS Support Indicator 6402 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of the 6403 two numbers from the HLR. 6404 IMSI 6405 See definition in clause 7.6.2. The presence of this parameter is mandatory in a successful case. 6406 Network Node Number 6407 See definition in clause 7.6.2. This parameter is provided in a successful response. 6408 LMSI 6409 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 6410 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6411 GPRS Node Indicator 6412 See definition in clause 7.6.8. The presence of this parameter is mandatory if only the SGSN number is sent in the 6413 Network Node Number. 6414 Additional Number 6415 See definition in clause 7.6.2. This parameter is provided in a successful response. 6416 User error 6417 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6418 6419 6420 6421 6422 6423 6424 6425

763 Release 4 764 765

192

3GPP TS 29.002 V4.17.0 (2006-06)

Unknown subscriber; Call Barred; Teleservice Not Provisioned; Absent Subscriber_SM; Facility Not Supported; System failure; Unexpected Data Value; Data missing.

6426 Provider error 6427 For definition of provider errors see clause 7.6.1.

766

767 Release 4 768 769

193

3GPP TS 29.002 V4.17.0 (2006-06)

6428 6429

12.2 MAP-MO-FORWARD-SHORT-MESSAGE service


12.2.1 Definition

6430 This service is used between the serving MSC or the SGSN and the SMS Interworking MSC to forward mobile 6431 originated short messages. 6432 The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 6433 table 12.2/1.

6434
6435

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

6436

6437
6438 Invoke id

12.2.3 Parameter use

6439 See definition in clause 7.6.1. 6440 SM RP DA 6441 See definition in clause 7.6.8. 6442 In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile 6443 station. 6444 SM RP OA 6445 See definition in clause 7.6.8. 6446 The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM 6447 transfer. 6448 SM RP UI 6449 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 6450 in this parameter. 6451 IMSI 6452 See definition in clause 7.6.2.1. The IMSI of the originating subscriber is inserted in this parameter in the mobile 6453 originated SM transfer. 6454 This parameter shall be included if the sending entity, whether MSC or SGSN, supports mobile number portability. 6455 User error 6456 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6457 6458

Facility Not Supported; System Failure;

770

6459 6460 6461 6462 6463 6464 6465 6466

771 Release 4 772 773

194

3GPP TS 29.002 V4.17.0 (2006-06)

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

6467 Provider error 6468 For definition of provider errors see clause 7.6.1.

6469 6470

12.3 MAP-REPORT-SM-DELIVERY-STATUS service


12.3.1 Definition

6471 This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is 6472 used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This 6473 service is invoked by the gateway MSC. 6474 The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in 6475 table 12.3/1.

6476
6477

12.3.2 Service primitives


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(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

6478

6479
6480 Invoke id

12.3.3 Parameter use

6481 See definition in clause 7.6.1. 6482 MSISDN 6483 See definition in clause 7.6.2. 6484 Service Centre Address 6485 See definition in clause 7.6.2.

774

6486 SM Delivery Outcome 6487 See definition in clause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. 6488 Absent Subscriber Diagnostic SM 6489 See definition in clause 7.6.8. 6490 GPRS Support Indicator 6491 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of two 6492 delivery outcomes. 6493 Delivery Outcome Indicator 6494 See definition in clause 7.6.8. 6495 Additional SM Delivery Outcome 6496 See definition in clause 7.6.8. 6497 Additional Absent Subscriber Diagnostic SM 6498 See definition in clause 7.6.8. 6499 MSIsdn-Alert 6500 See definition in clause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN 6501 received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned 6502 to the gateway MSC. 6503 User error 6504 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6505 6506 6507 6508

775 Release 4 776 777

195

3GPP TS 29.002 V4.17.0 (2006-06)

Unknown Subscriber; Message Waiting List Full; Unexpected Data Value; Data missing.

6509 Provider error 6510 For definition of provider errors see clause 7.6.1.

6511 6512

12.4 MAP-READY-FOR-SM service


12.4.1 Definition

6513 This service is used between the MSC and VLR as well as between the VLR and the HLR. The MSC initiates this 6514 service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. 6515 The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the 6516 MSC. 6517 Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates 6518 memory available situation. The SGSN uses the service to indicate this to the HLR. 6519 The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in 6520 the GPRS. 6521 The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1.

778

6522

779 Release 4 780 781

196

3GPP TS 29.002 V4.17.0 (2006-06)

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(=)

6523

C(=) O

6524

6525
6526 Invoke id

12.4.3 Parameter use

6527 See definition in clause 7.6.1. 6528 IMSI 6529 See definition in clause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the 6530 HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI. 6531 TMSI 6532 See definition in clause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR. 6533 Alert Reason 6534 See definition in clause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory 6535 available. 6536 Alert Reason Indicator 6537 See definition in clause 7.6.8. 6538 User error 6539 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6540 6541 6542 6543 6544

Unknown Subscriber; Facility Not Supported; System Failure; Unexpected Data Value; Data missing.

6545 Provider error 6546 For definition of provider errors see clause 7.6.1.

6547 6548

12.5 MAP-ALERT-SERVICE-CENTRE service


12.5.1 Definition

6549 This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects 6550 that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available.

782

6551 The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1.

783 Release 4 784 785

197

3GPP TS 29.002 V4.17.0 (2006-06)

6552
6553

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

6554

6555
6556 Invoke id

12.5.3 Parameter use

6557 See definition in clause 7.6.1. 6558 MSIsdn-Alert 6559 See definition in clause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data file. 6560 Service Centre Address 6561 See definition in clause 7.6.2. 6562 User error 6563 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6564 6565 6566

System Failure; Unexpected Data Value; Data missing.

6567 Provider error 6568 For definition of provider errors see clause 7.6.1.

6569 6570
6571 6572 6573 6574

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 as 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.

6575 Additionally the status of MCEF, MNRF and MNRG flags and the inclusion of the particular Service Centre address in 6576 the Message Waiting Data list is informed to the gateway MSC when appropriate. 6577 If the HLR has stored a single MNRR, the value is included in the Absent Subscriber Diagnostic SM parameter. 6578 If the HLR has stored a second MNRR, the value of the MNRR for the MSC is included in the Absent Subscriber 6579 Diagnostic SM parameter and the value of the MNRR for the SGSN is included in the Additional Absent Subscriber 6580 Diagnostic SM parameter. 6581 The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1.

786

6582

787 Release 4 788 789

198

3GPP TS 29.002 V4.17.0 (2006-06)

12.6.2 Service primitives


Table 12.6/1: MAP-INFORM-SERVICE-CENTRE
Parameter name Invoke Id MSIsdn-Alert MWD Status Absent Subscriber Diagnostic SM Additional Absent Subscriber Diagnostic SM Request M C C C C Indication M(=) C(=) C(=) C(=) C(=)

6583

6584

6585
6586 Invoke id

12.6.3 Parameter use

6587 See definition in clause 7.6.1. 6588 MSIsdn-Alert 6589 See definition in clause 7.6.2. This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR. 6590 MWD Status 6591 See definition in clause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the status 6592 of the particular SC address presence in the Message Waiting Data list. 6593 Absent Subscriber Diagnostic SM 6594 See definition in clause 7.6.8. 6595 Additional Absent Subscriber Diagnostic SM 6596 See definition in clause 7.6.8.

6597 6598

12.7 MAP-SEND-INFO-FOR-MT-SMS service


12.7.1 Definition

6599 This service is used between the MSC and the VLR. The service is invoked by the MSC receiving an mobile terminated 6600 short message to request subscriber related information from the VLR. 6601 The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1.

6602
6603

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

6604

6605

12.7.3 Parameter use

790

6606 Invoke id

791 Release 4 792 793

199

3GPP TS 29.002 V4.17.0 (2006-06)

6607 See definition in clause 7.6.1. 6608 SM RP DA 6609 See definition in clause 7.6.8. This parameter shall contain either an IMSI or a LMSI. 6610 MSISDN 6611 See definition in clause 7.6.2. 6612 User error 6613 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6614 6615 6616 6617 6618 6619 6620 6621 6622

Unknown subscriber; Unidentified Subscriber; Absent subscriber; Unexpected Data Value; Data Missing; Illegal subscriber; Illegal equipment; Subscriber busy for MT SMS; System Failure.

6623 Provider error 6624 For definition of provider errors see clause 7.6.1.

6625 6626

12.8 MAP-SEND-INFO-FOR-MO-SMS service


12.8.1 Definition

6627 This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile 6628 originated short message request to request the subscriber related information from the VLR. 6629 The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1.

6630
6631

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

6632

6633
6634 Invoke id

12.8.3 Parameter use

794

6635 See definition in clause 7.6.1. 6636 Service Centre Address 6637 See definition in clause 7.6.2. 6638 MSISDN 6639 See definition in clause 7.6.2. 6640 User error 6641 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6642 6643 6644 6645

795 Release 4 796 797

200

3GPP TS 29.002 V4.17.0 (2006-06)

Teleservice Not Provisioned; Call Barred; Unexpected Data Value; Data Missing.

6646 Provider error 6647 For definition of provider errors see clause 7.6.1.

6648 6649

12.9 MAP-MT-FORWARD-SHORT-MESSAGE service


12.9.1 Definition

6650 This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile terminated short 6651 messages. 6652 The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 6653 table 12.9/1.

6654
6655

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(=) Confirm M(=)

C C

C(=) C(=) O

6656

6657
6658 Invoke id

12.9.3 Parameter use

6659 See definition in clause 7.6.1. 6660 SM RP DA 6661 See definition in clause 7.6.8. This parameter can contain either an IMSI or a LMSI. The use of the LMSI is an operator 6662 option. The LMSI can be provided if it is received from the HLR. The IMSI is used if the use of the LMSI is not 6663 available. 6664 This parameter is omitted in the mobile terminated subsequent SM transfers.

798

6665 SM RP OA 6666 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in 6667 this parameter. 6668 This parameter is omitted in the mobile terminated subsequent SM transfers. 6669 SM RP UI 6670 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 6671 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message 6672 delivery acknowledgement from the MSC or from the SGSN to the Service Centre. 6673 More Messages To Send 6674 See definition in clause 7.6.8. The information from the MMS indication received from the Service Centre is inserted in 6675 this parameter. 6676 User error 6677 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6678

799 Release 4 800 801

201

3GPP TS 29.002 V4.17.0 (2006-06)

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; 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.

6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692

Unexpected Data Value; Data Missing.

6693 Provider error 6694 For definition of provider errors see clause 7.6.1.

6695 6696 6697

13

Network-Requested PDP Context Activation services


13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service
13.1.1 Definition

6698 This service is used by the GGSN to request GPRS routing information from the HLR.

802

6699

803 Release 4 804 805

202

3GPP TS 29.002 V4.17.0 (2006-06)

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

6700

6701

6702
6703 Invoke Id

13.1.3 Parameter definition and use

6704 See definition in clause 7.6.1. 6705 IMSI 6706 See definition in clause 7.6.2. 6707 GGSN address 6708 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6709 GGSN number 6710 See definition in clause 7.6.2. 6711 SGSN address 6712 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 6713 process in the HLR is positive. 6714 Mobile Not Reachable Reason 6715 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 6716 process in the HLR is positive and the MNRG flag in the HLR is set. See definition in clause 7.6.3.51. 6717 User error 6718 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6719 6720 6721 6722 6723

Absent Subscriber; System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

6724 The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown. 6725 6726 6727

Call Barred; This error will indicate that the received PDP PDUs in the GGSN shall be barred for this MS due to Operator Determined Barring. (The CallBarringCause must be the operatorBarring.)

6728 Provider error

806

6729 These are defined in clause 7.6.1.

807 Release 4 808 809

203

3GPP TS 29.002 V4.17.0 (2006-06)

6730 6731

13.2 MAP_FAILURE_REPORT service


13.2.1 Definition

6732 This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed.

6733
6734

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

6735

6736
6737 Invoke Id

13.2.3 Parameter definition and use

6738 See definition in clause 7.6.1. 6739 IMSI 6740 See definition in clause 7.6.2. 6741 GGSN address 6742 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6743 GGSN number 6744 See definition in clause 7.6.2. 6745 User error 6746 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6747 6748 6749 6750

System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

6751 Provider error 6752 These are defined in clause 7.6.1.

6753 6754

13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service


13.3.1 Definition

6755 This service is used by the HLR to inform the GGSN that the MS is present for GPRS again.

810

6756

811 Release 4 812 813

204

3GPP TS 29.002 V4.17.0 (2006-06)

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(=)

6757

C(=) O

6758

6759
6760 Invoke Id

13.3.3 Parameter definition and use

6761 See definition in clause 7.6.1. 6762 IMSI 6763 See definition in clause 7.6.2. 6764 GGSN address 6765 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6766 SGSN address 6767 See definition in clause 7.6.2. 6768 User error 6769 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6770 6771 6772 6773

System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

6774 Provider error 6775 These are defined in clause 7.6.1.

6776 6777 6778

13A

Location Service Management Services


13A.1MAP-SEND-ROUTING-INFO-FOR-LCS Service
13A.1.1 Definition

6779 This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location 6780 service request to the servicing VMSC or SGSN. The MAP-SEND-ROUTING-INFO-FOR-LCS is a confirmed service 6781 using the primitives from table 13A.1/1.

814

6782

815 Release 4 816 817

205

3GPP TS 29.002 V4.17.0 (2006-06)

13A.1.2 Service Primitives


Table 13A.1/1: MAP-SEND-ROUTING-INFO-FOR-LCS
Parameter name Invoke Id MLC Number MSISDN IMSI LMSI Network Node Number GPRS Node Indicator Additional Number User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) C C C C C C C Confirm M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O

6783

6784

6785
6786 Invoke id

13A.1.3 Parameter Use

6787 See definition in clause 7.6.1. 6788 MLC Number 6789 See definition in clause 7.6.2. 6790 MSISDN 6791 See definition in clause 7.6.2. The request shall carry either the IMSI or MSISDN. The response shall carry whichever 6792 of these was not included in the request (see 3GPP TS 23.271 for details). 6793 IMSI 6794 See definition in clause 7.6.2. 6795 LMSI 6796 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 6797 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6798 Network Node Number 6799 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 6800 Additional Number are received in the GMLC, the "Network Node Number" is used in preference to the "Additional 6801 Number". 6802 GPRS Node Indicator 6803 See definition in clause 7.6.8. The presence of this parameter is mandatory only if the SGSN number is sent in the 6804 Network Node Number. 6805 Additional Number 6806 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 6807 Additional Number are received in the GMLC, the "Network Node Number" is used in preference to the "Additional 6808 Number". 6809 User error 6810 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6811 6812 -

Unknown subscriber; Absent Subscriber;

818

6813 6814 6815 6816 6817 -

819 Release 4 820 821

206

3GPP TS 29.002 V4.17.0 (2006-06)

Facility Not Supported; System failure; Unexpected Data Value; Data missing; Unauthorised requesting network.

6818 Provider error 6819 For definition of provider errors see clause 7.6.1.

6820 6821

13A.2MAP-PROVIDE-SUBSCRIBER-LOCATION Service
13A.2.1 Definition

6822 This service is used by a GMLC to request the location of a target MS from the visited MSC or SGSN at any time. This 6823 is a confirmed service using the primitives from table 13A.2/1.

6824
6825

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 Supported GAD Shapes LCS-Reference Number Location Estimate Age of Location Estimate Additional Location Estimate Deferred MT-LR Response Indicator User error Provider error Request M M M M U C C C C C U C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

M C C C C

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

6826

6827

13A.2.3 Parameter Definition and Use

6828 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 6829 specified in. 3GPP TS 23.271 6830 Location Type 6831 This parameter identifies the type of location information requested. 6832 MLC Number 6833 This is the E.164 number of the requesting GMLC.

822

6834 LCS Client ID 6835 This parameter provides information related to the identity of an LCS client. 6836 Privacy Override 6837 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC or SGSN for an 6838 MT-LR are in the same country. 6839 IMSI 6840 The IMSI is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 6841 MSISDN 6842 The MSISDN is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 6843 LMSI 6844 The LMSI shall be provided if previously supplied by the HLR. This parameter is only used in the case of the MT-LR 6845 for CS domain. 6846 LCS Priority 6847 This parameter indicates the priority of the location request. 6848 LCS QoS 6849 This parameter indicates the required quality of service in terms of response time and accuracy. 6850 IMEI 6851 Inclusion of the IMEI is optional. 6852 Supported GAD Shapes 6853 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. 6854 LCS-Reference Number 6855 This parameter shall be included if a deferred mt-lr procedure is performed. 6856 Location Estimate 6857 This parameter provides the location estimate if this is encoded in one of the supported geographical shapes. Otherwise 6858 this parameter shall consist of one octet, which shall be discarded by the receiving node. 6859 Age of Location Estimate 6860 This parameter indicates how long ago the location estimate was obtained. 6861 Additional Location Estimate 6862 This parameter provides the location estimate when not provided by the Location Estimate parameter. It may be sent 6863 only if the parameter Supported GAD Shapes has been received in the Provide Subscriber Location indication and the 6864 shape to be included is supported by the GMLC. 6865 Deferred MT-LR Response Indicator 6866 See definition in clause 7.6.11.2. 6867 User error 6868 This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one 6869 of the following values defined in clause 7.6.1. 6870 -

823 Release 4 824 825

207

3GPP TS 29.002 V4.17.0 (2006-06)

System Failure;

826

6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 -

827 Release 4 828 829

208

3GPP TS 29.002 V4.17.0 (2006-06)

Data Missing; Unexpected Data Value; Facility Not Supported; Unidentified Subscriber; Illegal Subscriber; Illegal Equipment; Absent Subscriber (diagnostic information may also be provided); Unauthorised requesting network; Unauthorised LCS Client with detailed reason; Position method failure with detailed reason.

6881 Provider error 6882 These are defined in clause 7.6.1.

6883 6884

13A.3MAP-SUBSCRIBER-LOCATION-REPORT Service
13A.3.1 Definition

6885 This service is used by a VMSC or SGSN to provide the location of a target MS to a GMLC when a request for location 6886 is either implicitly administered or made at some earlier time. This is a confirmed service using the primitives from 6887 table 13A.3/1.

6888
6889

13A.3.2 Service Primitives


Table 13A.3/1: Subscriber_Location_Report
Parameter name Invoke id LCS Event LCS Client ID Network Node Number IMSI MSISDN NA-ESRD NA-ESRK IMEI Location Estimate Age of Location Estimate LMSI GPRS Node Indicator Additional Location Estimate Deferred MT-LR Data LCS-Reference Number NA-ESRK Request User error Provider error Request M M M M C C C C U C C U C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=)

C(=) O

6890

6891

13A.3.3 Parameter Definition and Use

6892 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 6893 specified in. 3GPP TS 23.271

830

6894 LCS Event 6895 This parameter indicates the event that triggered the Subscriber Location Report. 6896 LCS Client ID 6897 This parameter provides information related to the identity of the recipient LCS client. 6898 Network Node Number 6899 See definition in clause 7.6.2. This parameter provides the address of the sending node. 6900 IMSI 6901 The IMSI shall be provided if available to the VMSC or SGSN. 6902 MSISDN 6903 The MSISDN shall be provided if available to the VMSC or SGSN. 6904 NA-ESRD 6905 If the target MS has originated an emergency service call in North America, the NA-ESRD shall be provided by the 6906 VMSC if available. 6907 NA-ESRK 6908 If the target MS has originated an emergency service call in North America, the NA-ESRK shall be provided by the 6909 VMSC if assigned. 6910 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in 6911 Subscriber_Location_Report-Arg, NA-ESRK may also be included in the response to the MSC, see 3GPP TS 23.271 6912 [26a]. 6913 IMEI 6914 Inclusion of the IMEI is optional. 6915 Location Estimate 6916 This parameter provides the location estimate. The absence of this parameter implies that a location estimate was not 6917 available or could not be successfully obtained. If the obtained location estimate is not encoded in one of the supported 6918 geographical shapes then this parameter shall consist of one octet, which shall be discarded by the receiving node. 6919 6920 Age of Location Estimate 6921 This parameter indicates how long ago the location estimate was obtained. 6922 LMSI 6923 The LMSI may be provided if assigned by the VLR. 6924 GPRS Node Indicator 6925 See definition in clause 7.6.8. This presence of this parameter is mandatory only if the SGSN number is sent in the 6926 Network Node Number. 6927 Additional Location Estimate 6928 This parameter provides the location estimate when not provided by the Location Estimate parameter.. 6929 Deferred MT-LR Data 6930 See definition in clause 7.6.11.3. 6931 LCS-Reference Number

831 Release 4 832 833

209

3GPP TS 29.002 V4.17.0 (2006-06)

834

6932 This parameter shall be included if the Subscriber Location Report is the reponse to a deferred MT location request. 6933 NA-ESRK Request 6934 If the target MS has originated an emergency service call in North America, NA-ESRK Request may be included to 6935 indicate that the MSC is able to accept NA-ESRK in the Response message, see section 7.6.11.19. 6936 User error 6937 This parameter is sent by the responder when the received message contains an error, cannot be forwarded or stored for 6938 an LCS client or cannot be accepted for some other reason and if present, takes one of the following values defined in 6939 clause 7.6.1. 6940 6941 6942 6943 6944 6945 6946 -

835 Release 4 836 837

210

3GPP TS 29.002 V4.17.0 (2006-06)

System Failure; Data Missing; Unexpected Data Value; Resource Limitation; Unknown Subscriber; Unauthorised requesting network; Unknown or unreachable LCS Client.

6947 Provider error 6948 These are defined in clause 7.6.1.

6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960

13A.4Void
13A.4.1 Void 13A.4.2 Void 13A.4.3 Void

13A.5Void
13A.5.1 Void 13A.5.2 Void 13A.5.3 Void

13A.6Void
13A.6.1 Void 13A.6.2 Void 13A.6.3 Void

838

839 Release 4 840 841

211

3GPP TS 29.002 V4.17.0 (2006-06)

6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972

13A.7Void
13A.7.1 Void 13A.7.2 Void 13A.7.3 Void

13A.8Void
13A.8.1 Void 13A.8.2 Void 13A.8.3 Void

13A.9Void
13A.9.1 Void 13A.9.2 Void 13A.9.3 Void

6973 6974

14

General
14.1 Overview

6975 Clauses 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. 6976 Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping onto TC service 6977 primitives. Clause 17 specifies the application contexts, operation packages and abstract syntaxes for the MAP protocol 6978 as well as the encoding rules to be applied.

6979

14.2 Underlying services

6980 The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of Signalling System Number 6981 No. 7, as referenced in clause 6.

6982
6983 6984 6985 6986

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).

842

6987 A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a TC-BEGIN 6988 indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific service invoked 6989 during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is created at the performer's side. 6990 This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not intended to 6991 suggest any implementation. SDL descriptions are organised according to this model. 6992 How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local 6993 implementation matter. 6994 How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter.

843 Release 4 844 845

212

3GPP TS 29.002 V4.17.0 (2006-06)

6995

14.4 Conventions

6996 The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major 6997 difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do 6998 not belong to the so-called "version one context set". 6999 The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1 implementation 7000 according to the latest phase 1 version of GSM 09.02. This set is defined in clause 15. 7001 The procedures described in clause 15 are used when the application-context-name does not refer to a dialogue between 7002 an MSC and its VLR. When the application-context-name refers to a dialogue between an MSC and its VLR the MAP 7003 PM procedures are a local implementation matter.

7004 7005
7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020

15

Elements of procedure
15.1 Handling of unknown operations

Unknown operations (i.e. a standard operation introduced in a later version of the MAP specification, or a private operation) can be introduced into 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. Note that if the dialogue structure is affected as described in this paragraph the TC-CONTINUE shall include the dialogue portion required to confirm the acceptance of the dialogue.

7021 Unknown operations may be invoked in the following types of message (there is no restriction as to how many 7022 unknown operations can be invoked in a message): 7023 7024 7025 7026 7027 7028 7029

TC-BEGIN: the component to invoke the unknown operation shall follow the component of the standard operation which 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 may 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

846

7030 The TC-REJECT component may be sent in the following messages: 7031 7032 7033 7034 7035 7036 7037 7038 7039

847 Release 4 848 849

213

3GPP TS 29.002 V4.17.0 (2006-06)

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. Neither a specific distribution of the components to the TC messages nor a specific sequencing of components is required.

7040 Note that the SDL diagrams of clauses 19 - 25 do not show the report to the MAP-Service User about the reception of 7041 the unknown operation. This has been done for simplicity of description; the MAP PM may inform the MAP-Service 7042 User. 7043 The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown 7044 operation.

7045

15.2 Dialogue establishment

7046 The establishment of a MAP dialogue involves two MAP-service-users: the dialogue-initiator and the dialogue7047 responder. 7048 This procedure is driven by the following signals: 7049 7050 7051 7052

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;

7053 and under specific conditions: 7054 7055 7056

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.

7057 One instance of the MAP dialogue state machine runs at the initiating side, and one at the responding side.

7058

15.2.1 Behaviour at the initiating side

7059 The behaviour of the MAP dialogue state machine at the initiating side is defined in sheets 1 8 of the process 7060 MAP_DSM (fugure 15.6/3). 7061 Sheet 3: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, 7062 a TC-END indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the 7063 dialogue. 7064 Sheet 3: If the dialogue opening is accepted, any components included in the TC-END are processed and passed to the 7065 MAP-Service User. The dialogue is closed by sending a MAP-CLOSE to the MAP-Service User. 7066 Sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8: when a dialogue is terminated, the MAP dialogue state machine 7067 terminates all instances of the Requesting_MAP_SSM which are active for this dialogue. 7068 Sheet 4: A TC-P-ABORT with an abort parameter Incorrect_Transaction_Portion indicates that the responding side 7069 does not support a MAP version higher than 1. This triggers a MAP-OPEN confirm indicating that the dialogue is 7070 refused, with a refuse reason potential version incompatibility. The MAP-Service User may then decide to retry the

850

7071 dialogue at MAP version 1. If secure transport is required and fallback to unsecured transport is acceptable, the dialogue 7072 machine retries the dialogue with unsecured transport. 7073 7074 Sheet 8: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, 7075 a TC-CONTINUE indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the 7076 dialogue. 7077 Sheet 8: If the dialogue opening is accepted, any components included in the TC-CONTINUE are processed and passed 7078 to the MAP-Service User. The dialogue has then reached the established state.

851 Release 4 852 853

214

3GPP TS 29.002 V4.17.0 (2006-06)

7079

15.2.2 Behaviour at the responding side

7080 The behaviour of the MAP dialogue state machine at the responding side is defined in sheets 9 14 of the process 7081 MAP_DSM (figure 15.6/3). 7082 Sheet 9: If no application context information is included in the TC-BEGIN indication, this implies a MAP version 1 7083 dialogue. An explicit application context indicating version 1 is treated as abnormal behaviour. 7084 Sheet 11: The v1 application context name which corresponds to a v1 operation is derived using the information in table 7085 15.2/1. 7086

Table 15.2/1: Mapping of V1 operation codes on to application-context-names


Operation updateLocation cancelLocation provideRoamingNumber insertSubscriberData deleteSubscriberData sendParameters beginSubscriberActivity sendRoutingInfo performHandover reset activateTraceMode deactivateTraceMode sendRoutingInfoForSM forwardSM reportSM-deliveryStatus noteSubscriberPresent alertServiceCentreWithoutResult checkIMEI Application-context-name (note 1) networkLocUpContext-v1 locationCancellationContext-v1 roamingNumberEnquiryContext-v1 subscriberDataMngtContext-v1 subscriberDataMngtContext-v1 infoRetrievalContext-v1 networkLocUpContext-v1 (note 2) networkFunctionalSsContext-v1 locationInfoRetrievalContext-v1 handoverControlContext-v1 resetContext-v1 tracingContext-v1 tracingContext-v1 shortMsgGatewayContext-v1 shortMsgRelayContext-v1 shortMsgGatewayContext-v1 mwdMngtContext-v1 shortMsgAlertContext-v1 EquipmentMngtContext-v1

7087

7092 Sheet 12: If the dialogue is accepted, each component present in the TC-BEGIN is forwarded to an instance of a 7093 Performing_MAP_SSM, by executing the procedure Process_Components. 7094 Sheet 13: If the MAP dialogue state machine receives a MAP-OPEN response with a result accepted, it waits for any 7095 MAP specific service request or response primitives or a MAP-DELIMITER request. 7096 Sheet 13, sheet 14: When a dialogue is terminated, the MAP dialogue state machine terminates all instances of the 7097 Requesting_MAP_SSM or Performing_MAP_SSM which are active for this dialogue. 7098 Sheet 14: A MAP-DELIMITER request triggers a TC-CONTINUE request to accept the dialogue. The dialogue has 7099 then reached the established state.

7088 7089 7090 7091

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.

854

855 Release 4 856 857

215

3GPP TS 29.002 V4.17.0 (2006-06)

7100

15.3 Dialogue continuation

7101 Once established the dialogue is said to be in a continuation phase. The behaviour of the MAP dialogue state machine in 7102 this phase is defined in sheets 15 17 of the process MAP_DSM (figure 15.6/3). 7103 Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue. 7104 Normal closure of an established dialogue is shown on sheet 16; abnormal termination is shown on sheet 17.

7105

15.4 Load control

7106 If an entity which should respond to a MAP dialogue opening request is overloaded, it uses the AC of the request to 7107 determine whether to discard the request. 7108 The priority level allocated to each application-context is described in clause 5, tables 5.1/1, 5.1/2 and 5.1/3.

7109

15.5 Procedures for MAP specific services

7110 This clause describes the MAP procedures for MAP specific services. These procedures are driven by the following 7111 types of event: 7112 7113

a MAP specific request or a MAP specific response primitive; a component handling primitive from TC.

7114 A Service State Machine is activated when of one of the following signals is received: 7115 7116

a MAP request primitive, which activates a requesting SSM; a TC-INVOKE indication primitive without a linked identifier, which activates a performing SSM.

7117 For component handling primitives there are two types of event: 7118 7119

events which activate a Service State Machine or which can be related to an existing one; events which cannot be related to a Service State Machine.

7120
7121 7122 7123 7124 7125 7126 7127 7128 7129 7130

15.5.1 Service invocation


The behaviour of the requesting SSM which handles a service is defined by the SDL for the process Requesting_MAP_SSM. The requesting SSM receives a MAP service request from the MAP-Service User via the MAP dialogue state machine and sends a TC-INVOKE request to TCAP. When a confirm is received from TCAP via the MAP dialogue state machine, the requesting SSM forwards a MAP service confirm to the MAP-Service User. The response to a MAP service invocation may come in the form of a linked request. If the linked request corresponds to a class 4 operation, this is handled by the requesting SSM. If the linked request corresponds to a class 1, 2 or 3 operation, the MAP dialogue state machine sends a notification to the requesting SSM and creates an instance of a performing SSM to handle the linked request. The test "Linked_Operation_Allowed" on sheet 3 of the process Requesting_MAP_SSM takes the (TRUE) exit if the definition of the parent operation includes the received linked operation as a permitted linked operation; otherwise the test takes the (FALSE) exit.

7131 The mapping of MAP specific services on to remote operations is given in table 16.2/1.

7132 7133

15.5.2 void 15.5.3 Service invocation receipt

7134 The behaviour of the performing SSM which handles a service is defined by the SDL for the process 7135 Performing_MAP_SSM. The performing SSM receives a TC-INVOKE component from TCAP via the MAP dialogue 7136 state machine and sends a MAP service indication to the MAP-Service User. When a MAP service response is received

858

7137 from the MAP-Service User via the MAP dialogue state machine, the performing SSM forwards a TC-RESULT or TC7138 U-ERROR component to TCAP.

859 Release 4 860 861

216

3GPP TS 29.002 V4.17.0 (2006-06)

7139 7140

15.5.4 void 15.5.5 Handling of components received from TC

7141 The procedure Process_Components shows the handling of components received in a TC-BEGIN, TC-CONTINUE or 7142 TC-END message. 7143 7144 7145 7146

Sheet 2: If a linked invoke component corresponds to a class 4 operation, the MAP dialogue state machine sends it to the requesting SSM instance identified by the linked invoke ID. If a linked invoke component corresponds to any other class of operation, the MAP dialogue state machine sends a notification to the requesting SSM instance identified by the linked invoke ID, creates an instance of a performing SSM and sends the invoke component to it.

7147

15.6 SDL descriptions

7148 The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. 7149 Such a system resides in each network component supporting MAP and communicates with its peers via the lower 7150 layers of the signalling network which are part of the environment. 7151 Only the MAP-provider is fully described in this clause. The various types of processes which form the MAP-User 7152 block and the TC block are described respectively in clauses 18 to 25 of the present document and in CCITT 7153 Recommendation Q.774. 7154 The MAP-Provider block communicates with the MAP_USER via two channels U1 and U2. Via U1 the MAP-provider 7155 receives the MAP request and response primitives. Via U2 it sends the MAP indication and confirm primitives. 7156 The MAP-Provider block communicates with TC via two channels P1 and P2. Via P1 the MAP-Provider sends all the 7157 TC request primitives. Via P2 it receives all the TC indication primitives. 7158 The MAP-Provider block is composed of the four following types of process: 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168

a) MAP_DSM: This type of process handles a dialogue for transport of MAP messages. 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) Requesting_MAP_SSM: This type of process handles a MAP service requested during a dialogue. An instance of this process is created by the instance of the Secure_MAP_DSM process for each requested MAP service. d) Performing_MAP_SSM: This type of process handles a MAP service performed during a dialogue. An instance of this process is created by the instance of the Secure_MAP_DSM process for each MAP service to be performed.

7169 A process MAP_DSM exchanges external signals with other blocks as well as internal signals with the other processes 7170 of the MAP-Provider block. The external signals are either MAP service primitives or TC service primitives. 7171 The signal routes used by the various processes are organised as follows: 7172 7173 7174 7175 7176 7177

a) A process MAP_DSM receives and sends events from/to the MAP_user via signal route User1/User2. These routes use channels U1 and U2 respectively. b) A process MAP_DSM receives and sends events from/to the TCAP via signal route TC1/TC2. These routes use channels P1 and P2 respectively. c) A process MAP_DSM receives and sends events from/to the LOAD_CTRL process via signal route Load1/Load2. These routes are internal.

862

7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189

863 Release 4 864 865

217

3GPP TS 29.002 V4.17.0 (2006-06)

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 Performing_MAP_SSM sends events to the MAP_USER via signal route User3. This route uses channel U2. g) A process Performing_MAP_SSM sends events to the TCAP via signal route TC3. This route uses channel P1. h) A process Requesting_MAP_SSM sends events to the MAP_USER via signal route User4. This route uses channel U2. i) A process Requesting_MAP_SSM sends events to the TCAP via signal route TC4. This route uses channel P1.

866

867 Release 4 868 869

218

3GPP TS 29.002 V4.17.0 (2006-06)

System MAP_Stack

Map_Stack1(1)

MAP_USER
U2

(MAP_REQ_SM)
U1

MAP_IND_SP

MAP_ Provider

P2

TC_REQ_SP
P1

TC_IND_SP

TCAP

7190
7191

Figure 15.6/1: System MAP_Stack

870

871 Release 4 872 873

219

3GPP TS 29.002 V4.17.0 (2006-06)

Block MAPProvider

MAP_Provider1(1)

TC2 TC1 Intern2

MAP_DSM

User1 User2 Intern1

Load2 Load1 Load_Ctrl

TC4

Requesting_ _MAP_SSM

Performing_ _MAP_SSM

User3

TC3

User4

7192
7193

Figure 15.6/2: Block MAP_Provider

874

875 Release 4 876 877

220

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue Comment 'MAP Dialogue State Machine'; DCL Components_Present, AC_Name_Unchanged, AC_Included, AC_Supported, Invoke_ID_Active, Last_Component, Operation_Exists, Alternative_Name_Exists, User_Info_Included BOOLEAN, Op_Code INTEGER;

MAP_DSM1(17)

IDLE

MAP_OPEN_ req

Store_AC_and_ user_data

For dialogue portion of TC-BEGIN

WAIT_FOR_ USER_ REQUESTS

7194
7195

Figure 15.6/3a: Process MAP_DSM (sheet 1)

878

879 Release 4 880 881

221

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue

MAP_DSM2(17)

WAIT_FOR_ USER_ REQUESTS

Any MAP specific request primitive

MAP_req

MAP_ DELIMITER_ req

MAP_U_ ABORT_ req

Set_Abort_ Reason:User_ Specific

Set_User_Info: MAP_User_ Abort_PDU

TC_U_ABORT_ req_VIA_TC1

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

TC_BEGIN_ req_VIA_TC1

Terminated_ VIA_Intern2

To all active RSSMs

WAIT_FOR_ USER_ REQUESTS

DIALOGUE_ INITIATED

IDLE

7196
7197

Figure 15.6/3b: Process MAP_DSM (sheet 2)

882

883 Release 4 884 885

222

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM3(17)

TC_END_ ind

TC_ NOTICE_ ind

(FALSE) AC_Name_ Unchanged (TRUE) Set_Provider_ Reason: Abnormal_ MAP_Dialogue Set_Refuse_ Reason: Node_ Not_Reachable Set_Result: Dialogue_Refused

MAP_P_ABORT_ ind_VIA_User2 Set_Result: Dialogue_ Accepted

MAP_OPEN_ cnf_VIA_User2

MAP_OPEN_ cnf_VIA_User2

(FALSE) Components_ Present (TRUE)

Process_ Components

MAP_CLOSE_ ind_VIA_User2

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

IDLE

7198
7199

Figure 15.6/3c: Process MAP_DSM (sheet 3)

886

887 Release 4 888 889

223

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM4(17)

TC_P_ ABORT_ind

Incorrect_ Transaction_ Portion P-Abort_ Parameter No_Common_ Dialogue_Portion

Else

Set_Provider_ Reason: Version_ Incompatibility

Set_Result: Dialogue_Refused

MAP_P_ABORT ind_VIA_User2

Set_Refuse_Reason: Potential_Version_ Incompatibility

MAP_OPEN_ cnf_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

To all active RSSMs

Terminated_ VIA_Intern2

IDLE IDLE

7200
7201

Figure 15.6/3d: Process MAP_DSM (sheet 4)

890

891 Release 4 892 893

224

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM5(17)

TC_U_ ABORT_ind

TC_L_ CANCEL_ind

AC_Not_Supported Abort_Reason User_Specific MAP_OPEN_ cnf_VIA_User2

Accepted. The dialogue is considered implictly accepted when something is received

(FALSE) Invoke_ID_ Active (TRUE)

Timer_Expiry_ VIA_Intern2

Set_Result: Dialogue_Refused

DIALOGUE_ INITIATED

Set_Refuse_ Reason: AC_ Not_Supported

MAP_OPEN_ cnf_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7202
7203

Figure 15.6/3e: Process MAP_DSM (sheet 5)

894

895 Release 4 896 897

225

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue 4

MAP_DSM6(17)

User_ Information

User_Abort_PDU

Provider_Abort_PDU

Dialogue_Refused Set_Result: Dialogue_ Refused

No_User_Info Set_Result: Dialogue_ Refused

MAP_ Refuse_PDU_ Error

Invalid_ Destination_ Reference Set_Refuse_Reason: Invalid_Destination_ Reference

Invalid_ Originating_ Reference Set_Refuse_Reason: Invalid_Originating_ Reference

No_ Reason_ Given

Set_Refuse_Reason: No_Reason_Given

Set_Refuse_Reason: Potential_Version_ Incompatibility

MAP_P_ABORT_ ind_VIA_User2

MAP_P_ABORT_ ind_VIA_User2

MAP_OPEN_ cnf_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7204
7205

Figure 15.6/3f: Process MAP_DSM (sheet 6)

898

899 Release 4 900 901

226

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM7(17)

MAP_U_ ABORT_req

MAP_CLOSE_ req

Set_Abort_Reason: User_Specific

Set_User_Info: MAP_User_ Abort_Info

Local

TC_U_ABORT_ req_VIA_TC1

Pre-arranged

TC_END_ req_VIA_TC1

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7206
7207

Figure 15.6/3g: Process MAP_DSM (sheet 7)

902

903 Release 4 904 905

227

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM8(17)

TC_ CONTINUE_ ind

The first one

(FALSE) AC_Name_ Unchanged (TRUE)

Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue

MAP_P_ABORT_ ind_VIA_User2

Set_Result: Dialogue_ Accepted

Set_Abort_Reason_ User_Specific

MAP_OPEN_ cnf_VIA_User2

Set_User_Information: MAP_Provider_ Abort_Info

MAP_Provider_ Abort_Reason:= Abnormal_Dialogue

(FALSE) Components_ Present (TRUE) TC_U_ABORT_ req_VIA_TC1

Process_ Components

MAP_ DELIMITER_ req_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

DIALOGUE_ ESTABLISHED

IDLE

7208
7209

Figure 15.6/3h: Process MAP_DSM (sheet 8)

906

907 Release 4 908 909

228

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue IDLE

MAP_DSM9(17)

TC_BEGIN_ ind

(FALSE) AC_ Included (TRUE)

AC_Vession =1 (FALSE) (TRUE)

(FALSE)

MAP_ Dialogue_PDU_ included

(TRUE)

Extract_User_ Information

MAP-OPEN dialogue PDU? Yes Yes User_Info required for AC? No No Invalid Parameter?

No

Yes

(FALSE) Components_ Present (TRUE) Check_Load_ VIA_Load1 TC_U_ABORT_ req_VIA_TC1

WAIT_FOR_ LOAD_CHECK_ RESULT1

IDLE

WAIT_FOR_ INIT_DATA

7210
7211

Figure 15.6/3i: Process MAP_DSM (sheet 9)

910

911 Release 4 912 913

229

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue

MAP_DSM10(17)

Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue

Set_User_Info: MAP_Provider_ Abort_Info

Set_Abort_Reason: User_Specific

TC_U_ABORT_ req_VIA_TC1

IDLE

7212
7213

Figure 15.6/3j: Process MAP_DSM (sheet 10)

914

915 Release 4 916 917

230

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue

MAP_DSM11(17)

WAIT_FOR_ INIT_DATA

WAIT_FOR_ LOAD_CHECK_ RESULT2

TC_INVOKE_ ind (Op_Code)

TC_L_ REJECT_ ind

Any_ OTHER_ ind

Load_OK

Overload

(FALSE) Operation_ Exists (TRUE) IDLE

ELSE Derive_ V1_AC Op_Code begin_ subscriber_ activity (FALSE) Last_ Component (TRUE)

Check_Load_ VIA_Load1

TC_U_ ABORT_req VIA_TC1

TC_U_ ABORT_req VIA_TC1

Build_ MAP_OPEN_ind_ Primitive

WAIT_FOR_ LOAD_CHECK_ RESULT2

IDLE

MAP_OPEN_ ind_VIA_ User2

Perform_ version_1_ protocol

IDLE

7214
7215

Figure 15.6/3k: Process MAP_DSM (sheet 11)

918

919 Release 4 920 921

231

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue WAIT_FOR_ LOAD_CHECK_ RESULT1

MAP_DSM12(17)

Load_OK

Overload

IDLE (FALSE) AC_ Supported (TRUE)

AC_Name:= Received_ AC_Name

(FALSE)

Alternative_ Name_ Exists (TRUE)

Set_ User_Data

AC_Name:= Received_ AC_Name

AC_Name:= Alternative_ AC_Name

MAP_OPEN_ ind_VIA_User2

(FALSE) Components_ Present (TRUE)

Process_ Components

Set_Abort_ Reason: AC_Not_ Supported

MAP_ DELIMITER_ ind_VIA_User2

TC_U_ABORT_ req_VIA_TC1

DIALOGUE_ PENDING

IDLE

7216
7217

Figure 15.6/3l: Process MAP_DSM (sheet 12)

922

923 Release 4 924 925

232

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ PENDING

MAP_DSM13(17)

MAP_OPEN_ rsp

MAP_U_ ABORT_ req

Refused Result Accepted

Set_Abort_ Reason: User_Specific

Set_Abort_ Reason: User_Specific

Build_MAP_ Refuse_PDU

Set_User_Info: MAP_User_ Abort_Info

TC_U_ ABORT_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

DIALOGUE_ ACCEPTED

IDLE

7218
7219

Figure 15.6/3m: Process MAP_DSM (sheet 13)

926

927 Release 4 928 929

233

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ACCEPTED

MAP_DSM14(17)

MAP_req

Any MAP specific request primitive

MAP_rsp

Any MAP specific response primitive

MAP_ DELIMITER_ req

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

Response_ Issued_ VIA_Intern1

TC_ CONTINUE_ req_VIA_TC1

DIALOGUE_ ACCEPTED

DIALOGUE_ ESTABLISHED

MAP_CLOSE_ req

MAP_U_ ABORT_ req

Set_Abort_ Reason: User_Specific

User_Info:= MAPUserAbortInfo

TC_END_ req_VIA_TC1

TC_U_ ABORT_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7220
7221

Figure 15.6/3n: Process MAP_DSM (sheet 14)

930

931 Release 4 932 933

234

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM15(17)

MAP_req

Any MAP specific request primitive

MAP_rsp

Any MAP specific response primitive

MAP_ DELIMITER_ req

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

Response_ Issued_ VIA_Intern1

TC_ CONTINUE_ req_VIA_TC1

DIALOGUE_ ESTABLISHED

DIALOGUE_ ESTABLISHED

TC_L_ CANCEL_ ind

TC_ NOTICE_ ind

TC_ CONTINUE_ ind

(FALSE) And SSM active Invoke_ ID_Active (TRUE) Components_ Present (TRUE)

(FALSE)

Process_ Components

Timer_Expiry_ VIA_Intern2

MAP_ NOTICE_ ind_VIA_User2

MAP_ DELIMITER_ ind_VIA_User2

DIALOGUE_ ESTABLISHED

7222
7223

Figure 15.6/3o: Process MAP_DSM (sheet 15)

934

935 Release 4 936 937

235

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM16(17)

TC_END_ ind

MAP_ CLOSE_ req

(FALSE) Components_ Present (TRUE)

Process_ Components

MAP_CLOSE_ ind_VIA_User2

TC_END_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7224
7225

Figure 15.6/3p: Process MAP_DSM (sheet 16)

938

939 Release 4 940 941

236

3GPP TS 29.002 V4.17.0 (2006-06)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM17(17)

TC_U_ ABORT_ ind

TC_P_ ABORT_ ind

MAP_U_ ABORT_ req

Provider_Abort_PDU User_Info User_Abort_PDU

Set_Abort_ Reason: User_Specific

Set_User_Info: MAP_User_ Abort_Info

MAP_U_ ABORT_ ind_VIA_User2

MAP_P_ ABORT_ ind_VIA_User2

TC_U_ ABORT_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7226
7227

Figure 15.6/3q: Process MAP_DSM (sheet 17)

942

943 Release 4 944 945

237

3GPP TS 29.002 V4.17.0 (2006-06)

Procedure Process_Components
Procedure to process components received in a TC message

Proc_Comp1(5)

Comment: 'Components from TCAP' DCL Op_Code, Operation_Class INTEGER, Operation_Exists, Last_Component, Invoke_ID_Present, Invoke_ID_Assigned, Linked_ID_Present, Linked_ID_Assigned, Linked_Operation_Allowed, v3_Or_Higher_Dialogue BOOLEAN;

WAIT_FOR_ COMPONENTS

TC_INVOKE_ ind(Op_Code)

Invoke_ ID_ Assigned (TRUE)

(FALSE)

(TRUE) For this AC Operation_ Exists (FALSE) Linked_ ID_ Present (TRUE)

(FALSE) Set_Problem_ Code: Duplicated_ Invoke_ID Set_Problem_ Code: Unrecognised_ Operation 1

TC_U_ REJECT_ req_VIA_TC1

TC_U_ REJECT_ req_VIA_TC1

Performing_ MAP_SSM

(FALSE)

v3_Or_ Higher_ Dialogue (TRUE)

Service_ Invocation_ Received_ VIA_Intern1

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

MAP_NOTICE_ ind_VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7228
7229

Figure 15.6/4a: Procedure Process_Components (sheet 1)

946

947 Release 4 948 949

238

3GPP TS 29.002 V4.17.0 (2006-06)

Procedure Process_Components
Procedure to process components received in a TC message

Proc_Comp2(5)

(FALSE)

Linked_ ID_ Assigned (TRUE)

Set_Problem_ Code: Linked_ID_ Not_Assigned

(4) Operation_ Class (1,2,3)

TC_U_REJECT_ req_VIA_TC1

Linked_ Service_ Invoked_ VIA_Intern2

Linked_ Request_ Received_ VIA_Intern2

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

Performing_ MAP_SSM

MAP_NOTICE_ ind_VIA_User2

Service_ Invocation_ Received_ VIA_Intern1

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7230
7231

Figure 15.6/4b: Procedure Process_Components (sheet 2)

950

951 Release 4 952 953

239

3GPP TS 29.002 V4.17.0 (2006-06)

Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS

Proc_Comp3(5)

TC_ RESULT_L_ ind

TC_ RESULT_NL_ ind

TC_U_ ERROR_ ind

(FALSE) Invoke_ID_ Assigned (TRUE) Invoke_ID_ Assigned (TRUE)

(FALSE) Invoke_ID_ Assigned (TRUE)

(FALSE)

Set_Problem_ Code: Invoke_ID_ Not_Assigned

TC_U_REJECT_ req_VIA_TC1

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

Result_ Received_ VIA_Intern2

Partial_ Result_ Received_ VIA_Intern2

Negative_ Result_ Received_ VIA_Intern2

MAP_NOTICE_ ind_VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7232
7233

Figure 15.6/4c: Procedure Process_Components (sheet 3)

954

955 Release 4 956 957

240

3GPP TS 29.002 V4.17.0 (2006-06)

Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS

Proc_Comp4(5)

TC_L_ REJECT_ ind

TC_R_ REJECT_ ind

(FALSE) Invoke_ID_ Present (TRUE) rr_problem, re_problem, general_problem Problem Type invoke_problem Problem Type invoke_problem rr_problem, re_problem, general_problem

(FALSE) Invoke_ID_ Assigned (TRUE) Invoke_ID_ Assigned (TRUE)

(FALSE)

Provider_ Reject_ Received_ VIA_Intern2

MAP_ NOTICE_ind_ VIA_User2

Provider_ Reject_ Received_ VIA_Intern2

MAP_ NOTICE_ind_ VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7234
7235

Figure 15.6/4d: Procedure Process_Components (sheet 4)

958

959 Release 4 960 961

241

3GPP TS 29.002 V4.17.0 (2006-06)

Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS

Proc_Comp5(5)

TC_U_ REJECT_ ind

rr_problem, re_problem Problem Type invoke_problem

(FALSE) Invoke_ID_ Assigned (TRUE)

User_Reject_ Received_ VIA_Intern2

MAP_ NOTICE_ind_ VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7236
7237

Figure 15.6/4e: Procedure Process_Components (sheet 5)

962

963 Release 4 964 965

242

3GPP TS 29.002 V4.17.0 (2006-06)

Process Load_Ctrl
Process to verify whether offered dialogue should be discarded because of overload Comment 'LOAD CONTROL'; DCL Congestion, Dialogue_Acceptable BOOLEAN

Load_Ctrl1(1)

IDLE

Check_Load

(FALSE) Congestion

(TRUE)

(FALSE) Dialogue_ Acceptable (TRUE)

Load_OK_ VIA_Load2

Overload_ VIA_Load2

Load_OK_ VIA_Load2

IDLE

7238
7239

Figure 15.6/5: Process Load_Ctrl

966

967 Release 4 968 969

243

3GPP TS 29.002 V4.17.0 (2006-06)

Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity

MAP_RSSM1(4)

Comment 'Requesting MAP Service State Machine': DCL Argument_Correct, Error_Code_Correct, Linked_Request_Defined, Syntax_Correct, MAP_Iinitiated, Unexpected_Data, Implicit_Cnf, Linked_Operation_Allowed, W ait_For_Cnf, Service_Parameter_Available BOOLEAN, Operation_Class INTEGER;

IDLE

Service_ Invoked

A service has been invoked by the MAP user

Set_Operation__ Code_and_TCAP_ Parameters

TC_INVOKE_ req_VIA_TC4

(FALSE) W ait_ For_Cnf (TRUE)

W AIT_FOR_ CONFIRM

7240
7241

Figure 15.6/6a: Process Requesting_MAP_SSM (sheet 1)

970

971 Release 4 972 973

244

3GPP TS 29.002 V4.17.0 (2006-06)

Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity WAIT_FOR_ CONFIRM

MAP_RSSM2(4)

Result_ Received

Partial_ Result_ Received

Negative_ Result_ Received

(FALSE) Syntax_ Correct (TRUE)

(FALSE) Syntax_ Correct (TRUE) Error_Code_ Correct (TRUE)

(FALSE)

Partial_ Result_ Correct (TRUE)

(FALSE)

TC_U_ CANCEL_ req_VIA_TC4

Store_ Partial_ Info

(FALSE) Syntax_ Correct (TRUE) 1

Append_ Partial_ Info

WAIT_FOR_ CONFIRM

Service_ Parameters_ Available (TRUE)

(FALSE)

Service_ Parameter_ Available (TRUE)

(FALSE)

Set_Provider_ Error: Invalid_ Response_ Received

(TRUE) Unexpected_ Data_Value (FALSE)

(TRUE) Unexpected_ Data (FALSE) MAP_cnf_ VIA_User4

Set_Provider_ Error: Invalid_ Response_ Received

Set_Problem_ Code: Mistyped_ Parameter'

Set_User_ Error

Set_Provider_ Error: Invalid_ Response_ Received

MAP_cnf_ VIA_User4

TC_U_REJECT_ req_VIA_TC4

MAP_cnf_ VIA_User4

7242
7243

Figure 15.6/6b: Process Requesting_MAP_SSM (sheet 2)

974

975 Release 4 976 977

245

3GPP TS 29.002 V4.17.0 (2006-06)

Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity W AIT_FOR_ CONFIRM

MAP_RSSM3(4)

Linked_ Request_ Received

Terminated

User_ Reject_ Received

Linked_ Service_ Invoked

Find_Parent_ Operation_ Code

Implicit_Cnf:= TRUE

Linked_ Operation_ Allowed (TRUE)

(FALSE) W AIT_FOR_ CONFIRM

1 (FALSE)

Argument_ Correct (TRUE) (TRUE) (FALSE) MAP_ Initiated (TRUE) (FALSE)

Service_ Parameters_ Available

Set_ Problem_ Code

Set_Provider_ Error: Data_ Missing

TC_U_ REJECT_ req_VIA_TC4

Set_Provider_ Error

Set_User_ Error

MAP_cnf_ VIA_User4

MAP_cnf_ VIA_User4

7244
7245

Figure 15.6/6c: Process Requesting_MAP_SSM (sheet 3)

978

979 Release 4 980 981

246

3GPP TS 29.002 V4.17.0 (2006-06)

Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity WAIT_FOR_ CONFIRM

MAP_RSSM4(4)

Provider_ Reject_ Received

Timer_ Expiry

(4) Associated with the service Operation_ Class (1,3)

(2)

'A linked operation should have been invoked'

Linked_ Request_ Defined (TRUE)

(FALSE)

(FALSE) Implicit_ Cnf (TRUE)

Set_Provider_ Error

Set_Provider_ Error

MAP_cnf_ VIA_User4

MAP_cnf_ VIA_User4

MAP_cnf_ VIA_User4

7246
7247

Figure 15.6/6d: Process Requesting_MAP_SSM (sheet 4)

982

983 Release 4 984 985

247

3GPP TS 29.002 V4.17.0 (2006-06)

Process Performing_MAP_SSM
Process to handle an invoke component received from the peer and the response from the user

MAP_PSSM1(2)

Comment 'Performing MAP Service State Machine': DCL Argument_Correct, Service_Identifiable, Service_Parameters_Available, Unexpected_Data, Length_OK, User_Error_Present, Linked_Request, Specific_Error, More_Data, Cnf_Required BOOLEAN, Operation_Class INTEGER, TIMER Guard_Timer COMMENT 'expires if MAP user does not respond';

IDLE

Service_ Invocation_ Received

(FALSE) Is the syntax correct ? Argument_ Correct (TRUE) (TRUE) Service_ Identifiable (FALSE) Service_ Parameters_ Available (TRUE) (FALSE) Discard_ Invocation

Discard_ Invocation

Operation_ Class

Associated with the service

(1,2) Operation_ Class Associated with the service 1

(3,4)

(3,4)

(1,2) Set_Error: Unexpected_ Data_Value

Set_Error: Data_Missing

(TRUE) Unexpected_ Data (FALSE) Set_Problem_ Code: Mistyped_ Parameter

MAP_ind_ VIA_User3

Discard_ Invocation

(FALSE) Cnf_ Required (TRUE) (1,2) Set_ (Guard_Timer) (3,4) MAP_NOTICE_ ind_VIA_User3 MAP_NOTICE_ ind_VIA_User3 Operation_ Class Associated with the service TC_U_ERROR_ req_VIA_TC3 TC_U_REJECT_ req_VIA_TC3

WAIT_FOR_ RESPONSE

7248
7249

Figure 15.6/8a: Process Performing_MAP_SSM (sheet 1)

986

987 Release 4 988 989

248

3GPP TS 29.002 V4.17.0 (2006-06)

Process Performing_MAP_SSM
Process to handle an invoke component received from the peer and the response from the user WAIT_FOR_ RESPONSE

MAP_PSSM2(2)

Guard_ Timer_ Expired

Response_ Issued

by the MAP user or the Secure_ Performing_MAP_SSM

Terminated

(TRUE) User_Error_ Present (FALSE)

(FALSE) Linked_ Request (TRUE) Specific_ Error (TRUE)

(FALSE)

(TRUE) Length_ O.K. (FALSE)

Split_ info

TC_ RESULT_NL_ req_VIA_TC3

(FALSE) more_ data (TRUE)

Set_Operation_ Code_and_ TCAP_Param

Set_Error_ Code

Set_Problem_ Code

TC_ RESULT_L_ req_VIA_TC3

TC_INVOKE_ req_VIA_TC3

TC_U_ERROR_ req_VIA_TC3

TC_U_REJECT_ req_VIA_TC3

7250
7251

Figure 15.6/8b: Process Performing_MAP_SSM (sheet 2)

990

991 Release 4 992 993

249

3GPP TS 29.002 V4.17.0 (2006-06)

7252 7253

16

Mapping on to TC services
16.1 Dialogue control

7254 Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP 7255 PM.

7256

16.1.1 Directly mapped parameters

7257 The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the 7258 corresponding parameters of the TC-BEGIN primitives: 7259 7260

destination address; originating address.

7261 7262 16.1.2.1

16.1.2 Use of other parameters of dialogue handling primitives


Dialogue Id

7263 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

7264 16.1.2.2

Application-context-name

7265 The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of 7266 TC dialogue handling primitives according to the rules described in clause 15.1.

7267 16.1.2.3

User information

7268 The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs.

7269 16.1.2.4

Component present

7270 This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP 7271 user.

7272 16.1.2.5

Termination

7273 The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method 7274 parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE 7275 INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end".

7276 16.1.2.6
7277 7278 7279 7280 7281

P-Abort-Cause

Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the MAP-P-ABORT 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".

7282 16.1.2.7
-

Quality of service

7283 The quality of service of TC request primitives is set by the MAP as shown below. 7284

Return option: "Return message on error" or "Discard message on error" as required by the network operator;

994

7285 7286 7287 7288 7289

995 Release 4 996 997

250

3GPP TS 29.002 V4.17.0 (2006-06)

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.

7290 It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue 7291 initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue 7292 responder shall ensure that this requirement is met by: 7293 7294 7295 7296 7297 7298

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. 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 unrecognised message type provider malfunction unrecognised 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.

7299

7300

16.2 Service specific procedures


16.2.1 Directly mapped parameters

7301 Specific services are mapped to TC component handling services.

7302

7303 The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter 7304 of the component handling primitives.

7305 7306 16.2.2.1

16.2.2 Use of other parameters of component handling primitives


Dialogue Id

7307 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

7308 16.2.2.2

Class

7309 The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.

7310 16.2.2.3
7311 7312 7313 7314

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.

998

7315 16.2.2.4

999 Release 4 1000 1001

251

3GPP TS 29.002 V4.17.0 (2006-06)

Operation

7316 When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code 7317 according to the mapping described in table 16.2/1. 7318 When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the 7319 TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time. 7320

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_AUTHENTICATION_FAILURE_REPORT MAP-ANY-TIME-MODIFICATION MAP-ANY-TIME-SUBSCRIPTION-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-IST-ALERT MAP-IST-COMMAND MAP-NOTE-MS-PRESENT-FOR-GPRS MAP-NOTE-SUBSCRIBER-DATA-MODIFIED 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 operation activateSS activateTraceMode alertServiceCentre anyTimeInterrogaton authenticationFailureReport anyTimeModification anyTimeSubscriptionInterrogation cancelLocation checkIMEI deactivateSS deactivateTraceMode deleteSubscriberData eraseCC-Entry eraseSS failureReport forwardAccessSignalling forwardCheckSsIndication forwardGroupCallSignalling mt-forwardSM mo-forwardSM getPassword informServiceCentre insertSubscriberData interrogateSs istAlert istCommand noteMsPresentForGprs noteSubscriberDataModified 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

1002

1003 Release 4 252 1004 1005 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-INVOCATION-NOTIFICATION MAP-UNSTRUCTURED-SS-NOTIFY MAP-UNSTRUCTURED-SS-REQUEST MAP-UPDATE-GPRS-LOCATION MAP-UPDATE-LOCATION MAP-NOTE-MM-EVENT 7321

3GPP TS 29.002 V4.17.0 (2006-06) sendRoutingInfoForLCS sendRoutingInfo setReportingState SIWFSSignallingModify statusReport subscriberLocationReport ss-Invocation-Notification unstructuredSS-Notify unstructuredSS-Request updateGprsLocation updateLocation NoteMM-Event

7322 16.2.2.5

Error

7323 The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm 7324 primitive of the service associated with the operation to which the error is attached. 7325 The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request 7326 primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of 7327 the TC-U-REJECT request primitive.

7328 16.2.2.6

Parameters

7329 The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC7330 INVOKE primitives. 7331 The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L 7332 primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on 7333 linked class 4 operations is used.

7334 16.2.2.7

Time out

7335 The value of this parameter is set by the MAP PM according to the type of operation invoked.

7336 16.2.2.8

Last component

7337 This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP 7338 user.

7339 16.2.2.9 7340 16.2.2.9.1

Problem code
Mapping to MAP User Error

7341 The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. 7342 These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the 7343 MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive. 7344 7345

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

7346

7347 16.2.2.9.2

Mapping to MAP Provider Error parameter

7348 The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as 7349 follows to values of the MAP Provider Error parameter of the MAP confirm primitive.

1006

7350

1007 Release 4 1008 1009

253

3GPP TS 29.002 V4.17.0 (2006-06)

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 unrecognised operation mistyped parameter MAP Provider Error duplicated invoke id service not supported mistyped parameter

7351 7352 The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the 7353 provider error parameter of the MAP confirm primitive as follows. 7354

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

7355

7356 16.2.2.9.3

Mapping to diagnostic parameter

7357 The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to 7358 values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: 7359 7360

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 Invoke problem - unrecognised linked ID - linked response unexpected - unexpected linked operation Return result problem - unrecognised invoke ID - return result unexpected - mistyped parameter Return error problem - unrecognised invoke ID - return error unexpected - unrecognised error - unexpected error - mistyped parameter MAP diagnostic - abnormal event detected by the peer - 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

7361 7362 The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the 7363 diagnostic parameter of the MAP-NOTICE indication primitive as follows. 7364

Table 16.2/6: Mapping of TC problem code of TC-L-REJECT on to diagnostic parameter


TC problem code General problems Invoke problem - unrecognised linked ID Return result problem - unrecognised invoke ID Return error problem - unrecognised 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

7365

1010

1011 Release 4 1012 1013

254

3GPP TS 29.002 V4.17.0 (2006-06)

7366 7367
7368 7369 7370 7371

17

Abstract syntax of the MAP protocol


17.1 General

This clause 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 clause 17.1.4 on Compatibility Considerations and the OPERATION and ERROR external MACROs, defined in CCITT Recommendation Q.773.

7372 The Abstract Syntax is defined for all interfaces specified in clause 4.4 except for the A- and B-interfaces. 7373 The Mobile Application Part protocol is defined by two Abstract Syntaxes: 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385

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.

7386

17.1.1 Encoding rules

7387 The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract 7388 Syntax Notation One, defined in CCITT Recommendation X.690 with the same exceptions as in CCITT 7389 Recommendation Q.773 clause 4 Message Representation. 7390 When the definite form is used for length encoding, a data value of length less than 128 octets must have the length 7391 encoded in the short form. 7392 When the long form is employed to code a length, the minimum number of octets shall be used to code the length field. 7393 OCTET STRING values and BIT STRING values must be encoded in a primitive form. 7394 There is no restriction to the use of empty constructors (e.g. an empty SEQUENCE type). That is, the encoding of the 7395 content of any data value shall consist of zero, one or more octets.

7396

17.1.2 Use of TC

7397 The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on 7398 CCITT Recommendation Q.773 (1992). 7399 7400 7401 7402 7403 7404

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.

1014

7405 7406 7407 7408

1015 Release 4 1016 1017

255

3GPP TS 29.002 V4.17.0 (2006-06)

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.

7409 When an optional element is missing in an invoke component or in an inner data structure while it is required by the 7410 context, an error component is returned if specified in the operation type; the associated type of error is DataMissing. 7411 This holds also when the entire parameter of an invoke component is missing while it is required by the context. 7412 7413

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".

7414 The Timer Values used in the operation type definitions are indicated as ASN.1 comments. The Timer Value Ranges 7415 are: 7416 7417 7418 7419

= 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.

7420 17.1.2.1
7421 7422 7423 7424 7425 7426 7427 7428 7429

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 clause 17.5). Related restrictions regarding the use of Object Identifiers 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.

7430 Handling of an unknown operation codes by the receiving entity is defined in clause 15.1.1.

7431

17.1.3 Use of information elements defined outside MAP

7432 An information element or a set of information elements (messages) transparently carried in the Mobile Application 7433 Part but defined in other recommendations/technical specifications are handled in one of the following ways: 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443

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.

1018

7444

1019 Release 4 1020 1021

256

3GPP TS 29.002 V4.17.0 (2006-06)

17.1.4 Compatibility considerations

7445 The following ASN.1 modules conform to CCITT Recommendation X.208 (1988) or X.680 (1994) (the only module 7446 which makes use of X.680 is MAP-ExtensionDataTypes), but in addition Ellipsis Notation ("..." - notation) is used as 7447 described in ITU-T Recommendation X.680 Amendment 1 (1995) wherever future protocol extensions are foreseen. 7448 7449 7450 7451

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 clause 17.1.1 apply to every element of the whole Transfer Syntax especially to the ASN.1 type EXTERNAL.

7452 The extension container "privateExtensionList" is defined in this specification in order to carry extensions which are 7453 defined outside this specification. Private extensions can be defined by, for example, network operators, manufacturers, 7454 and regional standardisation bodies. 7455 Private extensions shall: 7456 7457 7458 7459 7460 7461

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.

7462 Private extensions shall not be included in v2 supplementary service operations. 7463 Private extensions shall not be included within user error for RegisterCCEntry and EraseCCEntry operations. 7464 PCS extensions shall be included in the PCS Extension Container that is defined in this specification. 7465 7466 7467 7468

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.

7469
7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485

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 capitalised, e.g. "no reply condition time" is mapped to "noReplyConditionTime"). Additionally some words may be abbreviated as follows: bs basic service ch call handling cug closed user group

ho handover ic incoming call id identity info mm information mobility management

lcs location services ms mobile service oc outgoing call

1022

7486 7487 7488 7489 7490 7491 7492 7493 7494 7495

1023 Release 4 1024 1025

257

3GPP TS 29.002 V4.17.0 (2006-06)

om operation & maintenance pw Password sm short message service ss 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. 3GPP TS 24.080 [38]). 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.

7496 The module containing the definition of the operation packages for MAP is: 7497

1. MAP-OperationPackages.

7498 The module containing the definition of the application contexts for MAP is: 7499

2. MAP-ApplicationContexts.

7500 The module containing the data types for the Abstract Syntax to be used for TCAPMessages.DialoguePortion for MAP 7501 is: 7502

3. MAP-DialogueInformation.

7503 The module containing the operation codes and error codes for MAP is: 7504

4. MAP-Protocol.

7505 The modules containing all operation type definitions for MAP are: 7506 7507 7508 7509 7510 7511 7512

5. MAP-MobileServiceOperations; 6. MAP-OperationAndMaintenanceOperations; 7. MAP-CallHandlingOperations; 8. MAP-SupplementaryServiceOperations; 9. MAP-ShortMessageServiceOperations; 10. MAP-Group-Call-Operations; 11. MAP-LocationServiceOperations

7513 The module containing all error type definitions for MAP is: 7514

12. MAP-Errors.

7515 Modules containing all data type definitions for MAP are: 7516 7517 7518 7519 7520 7521 7522

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;

1026

7523 7524 7525 7526 7527 7528

1027 Release 4 1028 1029

258

3GPP TS 29.002 V4.17.0 (2006-06)

20. MAP-CommonDataTypes; 21. MAP-TS-Code; 22. MAP-BS-Code; 23. MAP-ExtensionDataTypes; 24. MAP-GR-DataTypes; 25. MAP-LCS-DataTypes.

7529 References are made also to modules defined outside of the present document. They are defined in the technical 7530 specification Mobile Services Domain and technical specification Transaction Capability respectively: 7531 7532 7533

MobileDomainDefinitions; TCAPMessages; DialoguePDUs.

7534

17.1.6 Application Contexts

7535 The following informative table lists the latest versions of the Application Contexts used in this specification, with the 7536 operations used by them and, where applicable, whether or not the operation description is exactly the same as for 7537 previous versions. Information in 17.6 & 17.7 relates only to the ACs in this table. 7538

AC Name
locationCancellationContext equipmentMngtContext imsiRetrievalContext infoRetrievalContext interVlrInfoRetrievalContext handoverControlContext

AC Version
v3 v2 v2 v3 v3 v3

Operations Used
cancelLocation checkIMEI sendIMSI sendAuthenticationInfo sendIdentification prepareHandover forwardAccessSignalling sendEndSignal processAccessSignalling prepareSubsequentHandover readyForSM purgeMS alertServiceCentre reset processUnstructuredSS-Request unstructuredSS-Request unstructuredSS-Notify activateTraceMode deactivateTraceMode registerSS eraseSS activateSS deactivateSS registerPassword interrogateSS getPassword mo-forwardSM mt-forwardSM sendRoutingInfoForSM reportSM-DeliveryStatus InformServiceCentre updateLocation forwardCheckSs-Indication

Comments

the syntax of this operation has been extended in comparison with release 98 version

mwdMngtContext msPurgingContext shortMsgAlertContext resetContext networkUnstructuredSsContext tracingContext networkFunctionalSsContext

v3 v3 v2 v2 v2 v3 v2

shortMsgMO-RelayContext shortMsgMT-RelayContext shortMsgGatewayContext

v3 v3 v3

networkLocUpContext

v3

the syntax of this operation has been extended in comparison with release 96 version the syntax is the same in v1 & v2

1030

1031 Release 4 1032 1033

259

3GPP TS 29.002 V4.17.0 (2006-06)

AC Name

AC Version

Operations Used
restoreData insertSubscriberData activateTraceMode updateGprsLocation insertSubscriberData activateTraceMode insertSubscriberData deleteSubscriberData provideRoamingNumber sendRoutingInfo noteMsPresentForGprs sendRoutingInfoForGprs failureReport resumeCallHandling provideSubscriberInfo anyTimeInterrogation anyTimeSubscriptionInterrogation anyTimeModification ss-InvocationNotification provideSIWFSNumber sIWFSSignallingModify prepareGroupCall processGroupCallSignalling forwardGroupCallSignalling sendGroupCallEndSignal setReportingState statusReport remoteUserFree registerCC-Entry eraseCC-Entry istAlert istCommand provideSubscriberLocation subscriberLocationReport sendRoutingInfoForLCS

Comments

gprsLocationUpdateContext subscriberDataMngtContext roamingNumberEnquiryContext locationInfoRetrievalContext gprsNotifyContext gprsLocationInfoRetrievalContext failureReportContext callControlTransferContext subscriberInfoEnquiryContext anyTimeEnquiryContext anyTimeInfoHandlingContext ss-InvocationNotificationContext sIWFSAllocationContext groupCallControlContext

v3 v3 v3 v3 v3 v4 v3 v4 v3 v3 v3 v3 v3 v3

reportingContext callCompletionContext istAlertingContext ImmediateTerminationContext locationSvcEnquiryContext locationSvcGatewayContext

v3 v3 v3 v3 v3 v3

mm-EventReportingContext

v3

noteMM-Event
noteSubscriberDataModified authenticationFailureReport

subscriberDataModificationNotificati v3 onContext authenticationFailureReportContext v3

7539 7540

NOTE (*):

The syntax of the operations is not the same as in previous versions unless explicitly stated

7574 7575

17.2 Operation packages


17.2.1 General aspects

7576 This clause describes the operation-packages which are used to build the application-contexts defined in clause 17.3. 7577 Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), 7578 in terms of operations which they can invoke of each other. 7579 The grouping of operations into one or several packages does not necessarily imply any grouping in terms of 7580 Application Service Elements. 7581 The following ASN.1 MACRO is used to describe operation-packages in this clause:

1034

1035 Release 4 1036 1037


7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597

260

3GPP TS 29.002 V4.17.0 (2006-06)

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

7598 Since the application-context definitions provided in clause 17.3 use only an informal description technique, only the 7599 type notation is used in the following clauses to define operation-packages. 7600 The following definitions are used throughout this clause (n>=2): 7601 7602 7603 7604 7605 7606 7607 7608

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.

7609 The names of vn-packages are suffixed by "-vn" where n>=2. 7610 For each operation package which is not vn-only (n>=2) and which does not include only v(n-1)-operations, there is a 7611 v(n-1)-equivalent package. Except when a definition is explicitly provided in the following clauses, the 7612 v(n-1)-equivalent package includes the v(n-1)-equivalent operations of the operations which belong to this package.

7613 7614 17.2.2.1

17.2.2 Packages specifications


Location updating

7615 This operation package includes the operations required for location management procedures between HLR and VLR.
7616 7617 7618 7619 7620 7621 7622

LocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { updateLocation} SUPPLIER INVOKES { forwardCheckSs-Indication}

7623 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

7624 17.2.2.2

Location cancellation

7625 This operation package includes the operations required for location cancellation and MS purging procedures between 7626 HLR and VLR and between HLR and SGSN.
7627 7628 7629 7630 7631

LocationCancellationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { cancelLocation}

7632 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

1038

7633 17.2.2.3

1039 Release 4 1040 1041

261

3GPP TS 29.002 V4.17.0 (2006-06)

Roaming number enquiry

7634 This operation package includes the operations required for roaming number enquiry procedures between HLR and 7635 VLR.
7636 7637 7638 7639 7640

RoamingNumberEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideRoamingNumber}

7641 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

7642 17.2.2.4

Information retrieval

7643 This operation package includes the operation required for the authentication information retrieval procedure between 7644 HLR and VLR and between HLR and SGSN.
7645 7646 7647 7648 7649 7650

InfoRetrievalPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo}

7651 The v2-equivalent package is defined as follows:


7652 7653 7654 7655 7656 7657

InfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo}

7658 The v1-equivalent package is defined as follows:


7659 7660 7661 7662 7663 7664

InfoRetrievalPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR or VLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendParameters}

7665 17.2.2.5

Inter-VLR information retrieval

7666 This operation package includes the operations required for inter VLR information retrieval procedures.
7667 7668 7669 7670 7671

InterVlrInfoRetrievalPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification}

7672 The v2-equivalent package is defined as follows:


7673 7674 7675 7676 7677

InterVlrInfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification}

7678 The v1-equivalent package is : InfoRetrievalPackage-v1.

7679 17.2.2.6

IMSI retrieval

7680 This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR.
7681 7682 7683 7684 7685

IMSIRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { sendIMSI}

7686 This package is v2 only.

1042

7687 17.2.2.7

1043 Release 4 1044 1045

262

3GPP TS 29.002 V4.17.0 (2006-06)

Call control transfer

7688 This operation package includes the operation required for the call control transfer procedure between VMSC and 7689 GMSC.
7690 7691 7692 7693 7694

CallControlTransferPackage-v4 ::= OPERATION-PACKAGE -- Supplier is GMSC if Consumer is VMSC CONSUMER INVOKES { resumeCallHandling}

7695 The v3-equivalent package can be determined according to the rules described in clause 17.2.1.

7696 17.2.2.8 7697 17.2.2.9 7698 17.2.2.10

void Void Interrogation

7699 This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR.
7700 7701 7702 7703 7704

InterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR or NPLR if Consumer is MSC CONSUMER INVOKES { sendRoutingInfo}

7705 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

7706 17.2.2.11 7707 17.2.2.12

Void Handover Control

7708 This operation package includes the operations required for handover procedures between MSCs.
7709 7710 7711 7712 7713 7714 7715 7716 7717 7718

HandoverControlPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { prepareHandover, forwardAccessSignalling} SUPPLIER INVOKES { sendEndSignal, processAccessSignalling, prepareSubsequentHandover}

7719 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 7720 The v1-equivalent package is defined as follows.
7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732

HandoverControlPackage-v1 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { performHandover, forwardAccessSignalling, traceSubscriberActivity} SUPPLIER INVOKES { sendEndSignal, noteInternalHandover, processAccessSignalling, performSubsequentHandover}

1046

7733 17.2.2.13

1047 Release 4 1048 1049

263

3GPP TS 29.002 V4.17.0 (2006-06)

Subscriber Data management stand alone

7734 This operation package includes the operations required for stand alone subscriber data management procedures 7735 between HLR and VLR or between HLR and SGSN.
7736 7737 7738 7739 7740 7741

SubscriberDataMngtStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData, deleteSubscriberData}

7742 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

7743 17.2.2.14

Equipment management

7744 This operation package includes the operations required for equipment management procedures between EIR and MSC 7745 or between EIR and SGSN.
7746 7747 7748 7749 7750 7751

EquipmentMngtPackage-v2 ::= OPERATION-PACKAGE -- Supplier is EIR if Consumer is MSC -- Supplier is EIR if Consumer is SGSN CONSUMER INVOKES { checkIMEI}

7752 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

7753 17.2.2.15

Subscriber data management

7754 This operation package includes the operations required for subscriber data management procedures between HLR and 7755 VLR or between HLR and SGSN.
7756 7757 7758 7759 7760

SubscriberDataMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData}

7761 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

7762 17.2.2.16

Location register restart

7763 This operation package includes the operations required for location register restart procedures between HLR and VLR 7764 or between HLR and SGSN.
7765 7766 7767 7768 7769

ResetPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { reset}

7770 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

7771 17.2.2.17

Tracing stand-alone

7772 This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or 7773 between HLR and SGSN.
7774 7775 7776 7777 7778 7779

TracingStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode, deactivateTraceMode}

7780 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

1050

7781 17.2.2.18

1051 Release 4 1052 1053

264

3GPP TS 29.002 V4.17.0 (2006-06)

Functional SS handling

7782 This operation package includes the operations required for functional supplementary services procedures between VLR 7783 and HLR.
7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795

FunctionalSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerSS, eraseSS, activateSS, deactivateSS, registerPassword, interrogateSS} SUPPLIER INVOKES { getPassword}

7796 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

7797 17.2.2.19

Tracing

7798 This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR 7799 and SGSN.
7800 7801 7802 7803 7804

TracingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode}

7805 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

7806 17.2.2.20

Binding

7807 This operation package includes the operation required to initialise a supplementary service procedure between VLR 7808 and HLR or between gsmSCF and HLR.
7809 7810 7811 7812 7813

BindingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { beginSubscriberActivity}

7814 This package is v1 only.

7815 17.2.2.21

Unstructured SS handling

7816 This operation package includes the operations required for unstructured supplementary services procedures between 7817 VLR and HLR, between the HLR and the gsmSCF, and between HLR and HLR.
7818 7819 7820 7821 7822 7823 7824 7825 7826

UnstructuredSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF or HLR if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Request} SUPPLIER INVOKES { unstructuredSS-Request, unstructuredSS-Notify}

7827 The v1-equivalent package is defined as follows:


7828 7829 7830 7831 7832 7833

UnstructuredSsPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Data}

1054

7834 17.2.2.22

1055 Release 4 1056 1057

265

3GPP TS 29.002 V4.17.0 (2006-06)

MO Short message relay services

7835 This operation package includes the operations required for short message relay service procedures between IWMSC 7836 and VMSC or between GMSC and MSC or between SGSN and IWMSC.
7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850

MOShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is MSC -- Supplier is IWMSC if Consumer is SGSN CONSUMER INVOKES { MO-forwardSM} The v2-equivalent package is defined as follows: 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}

7851 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

7852 17.2.2.23

Short message gateway services

7853 This operation package includes the operations required for short message service gateway procedures between MSC 7854 and HLR.
7855 7856 7857 7858 7859 7860 7861 7862 7863

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 clause 17.2.1.

7864 The v1-equivalent package is defined as follows:


7865 7866 7867 7868 7869 7870

ShortMsgGatewayPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM, reportSMDeliveryStatus}

7871 17.2.2.24

MT Short message relay services

7872 This operation package includes the operations required for short message relay service procedures between GMSC and 7873 MSC or between GMSC and SGSN.
7874 7875 7876 7877 7878

MTShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSC or SGSN if Consumer is GMSC CONSUMER INVOKES { MT-forwardSM}

7879 The v2-equivalent package is: ShortMsgRelayPackage-v2

1058

7880 17.2.2.25 7881 17.2.2.26

1059 Release 4 1060 1061

266

3GPP TS 29.002 V4.17.0 (2006-06)

Void Message waiting data management

7882 This operation package includes the operations required for short message waiting data procedures between HLR and 7883 VLR, between HLR and SGSN.
7884 7885 7886 7887 7888 7889

MwdMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { readyForSM}

7890 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.
7891

7892 The v1-equivalent package is defined as follows:


7893 7894 7895 7896 7897

MwdMngtPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { noteSubscriberPresent}

7898 17.2.2.27

Alerting

7899 This operation package includes the operations required for alerting between HLR and IWMSC.
7900 7901 7902 7903 7904

AlertingPackage-v2 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentre}

7905 The v1-equivalent package is defined as follows.


7906 7907 7908 7909 7910

AlertingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentreWithoutResult}

7911 17.2.2.28

Data restoration

7912 This operation package includes the operations required for VLR data restoration between HLR and VLR.
7913 7914 7915 7916 7917

DataRestorationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { restoreData}

7918 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 7919 The v1-equivalent package is: InfoRetrievalPackage-v1

7920 17.2.2.29

Purging

7921 This operation package includes the operations required for purging between HLR and VLR or between HLR and 7922 SGSN.
7923 7924 7925 7926 7927 7928

PurgingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { purgeMS}

7929 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.

1062

7930 17.2.2.30

1063 Release 4 1064 1065

267

3GPP TS 29.002 V4.17.0 (2006-06)

Subscriber information enquiry

7931 This operation package includes the operations required for subscriber information enquiry procedures between HLR 7932 and VLR.
7933 7934 7935 7936 7937

SubscriberInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideSubscriberInfo}

7938 This package is v3 only.

7939 17.2.2.31

Any time information enquiry

7940 This operation package includes the operations required for any time information enquiry procedures between gsmSCF 7941 and HLR or GMLC.
7942 7943 7944 7945 7946

AnyTimeInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR or GMLC if Consumer is gsmSCF CONSUMER INVOKES { anyTimeInterrogation}

7947 This package is v3 only.

7948 17.2.2.32

Group Call Control

7949 This operation package includes the operations required for group call and broadcast call procedures between MSCs.
7950 7951 7952 7953 7954 7955 7956 7957 7958

GroupCallControlPackage-v3 ::= OPERATION-PACKAGE -- Supplier is relay MSC if Consumer is anchor MSC CONSUMER INVOKES { prepareGroupCall, forwardGroupCallSignalling} SUPPLIER INVOKES { sendGroupCallEndSignal, processGroupCallSignalling}

7959 This package is v3 only.

7960 17.2.2.33

Provide SIWFS number

7961 This operation package includes the operations required between VMSC and SIWF for requesting resources from an 7962 SIWF.
7963 7964 7965 7966 7967

ProvideSIWFSNumberPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { provideSIWFSNumber}

7968 This package is v3 only.

7969 17.2.2.34

SIWFS Signalling Modify

7970 This operation package includes the operations required for the modification of the resources in an SIWF between the 7971 VMSC and SIWF.
7972 7973 7974 7975 7976

SIWFSSignallingModifyPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { sIWFSSignallingModify}

7977 This package is v3 only.

1066

7978 17.2.2.35

1067 Release 4 1068 1069

268

3GPP TS 29.002 V4.17.0 (2006-06)

Gprs location updating

7979 This operation package includes the operations required for the gprs location management procedures between HLR 7980 and SGSN.
7981 7982 7983 7984

GprsLocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { updateGprsLocation}

7985 7986 This package is v3 only.

7987 17.2.2.36

Gprs Interrogation

7988 This operation package includes the operations required for interrogation procedures between HLR and GGSN.
7989 7990 7991 7992

GprsInterrogationPackage-v4 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs}

7993 7994 The v3-equivalent package is defined as follows. 7995


7996 7997 7998 7999

GprsInterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs}

8000

8001 17.2.2.37

Failure reporting

8002 This operation package includes the operations required for failure reporting between HLR and GGSN.
8003 8004 8005 8006

FailureReportingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { failureReport}

8007 8008 This package is v3 only.

8009 17.2.2.38

GPRS notifying

8010 This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and 8011 GGSN.
8012 8013 8014 8015

GprsNotifyingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is GGSN if Consumer is HLR CONSUMER INVOKES { noteMsPresentForGprs}

8016 8017 This package is v3 only.

1070

8018 17.2.2.39

1071 Release 4 1072 1073

269

3GPP TS 29.002 V4.17.0 (2006-06)

Supplementary Service invocation notification

8019 This operation package includes the operations required for Supplementary Service invocation notification procedures 8020 between the MSC and the gsmSCF and between the HLR and the gsmSCF.
8021 8022 8023 8024 8025 8026

SS-InvocationNotificationPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is gsmSCF if Consumer is MSC -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { ss-InvocationNotification}

8027 This package is v3 only.

8028 17.2.2.40

Set Reporting State

8029 This operation package includes the operation required for procedures between HLR and VLR to set the reporting state.
8030 8031 8032 8033 8034

SetReportingStatePackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { setReportingState}

8035 This package is v3 only.

8036 17.2.2.41

Status Report

8037 This operation package includes the operation required for procedures between VLR and HLR to report call results and 8038 events.
8039 8040 8041 8042 8043

StatusReportPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { statusReport}

8044 This package is v3 only.

8045 17.2.2.42

Remote User Free

8046 This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free.
8047 8048 8049 8050 8051

RemoteUserFreePackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { remoteUserFree}

8052 This package is v3 only.

8053 17.2.2.43

Call Completion

8054 This operation package includes the operations required for procedures between VLR and HLR for subscriber control of 8055 call completion services.
8056 8057 8058 8059 8060 8061

CallCompletionPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerCC-Entry, eraseCC-Entry}

8062 This package is v3 only.

8063 17.2.2.44

Location service gateway services

8064 This operation package includes the operations required for location service gateway procedures between GMLC and 8065 HLR.

1074

1075 Release 4 1076 1077


8066 8067 8068 8069 8070 8071

270

3GPP TS 29.002 V4.17.0 (2006-06)

LocationSvcGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMLC CONSUMER INVOKES { sendRoutingInfoForLCS}

This package is v3 only.

8072 17.2.2.45

Location service enquiry

8073 This operation package includes the operations required for the location service enquiry procedures between GMLC and 8074 MSC and between GMLC and SGSN.
8075 8076 8077 8078 8079

LocationSvcEnquiryPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is MSC or SGSN if Consumer is GMLC CONSUMER INVOKES { provideSubscriberLocation}

8080 This package is v3 only.

8081 17.2.2.45A

Location service reporting

8082 This operation package includes the operations required for the location service enquiry procedures between MSC and 8083 GMLC and between SGSN and GMLC.
8084 8085 8086 8087 8088

LocationSvcReportingPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is GMLC if Consumer is MSC -- Supplier is GMLC if Consumer is SGSN CONSUMER INVOKES { subscriberLocationReport}

8089 8090 17.2.2.46 8091 17.2.2.47 8092 17.2.2.48 8093 17.2.2.49 Void Void Void IST Alerting

8094 This operation package includes the operation required for alerting procedures between the MSC (Visited MSC or 8095 Gateway MSC) and HLR.
8096 8097 8098 8099 8100 8101

IST-AlertingPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is VMSC -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { istAlert}

8102 This package is v3 only.

8103 17.2.2.50

Service Termination

8104 This operation package includes the operation required for immediate service termination procedures between the HLR 8105 and the Visited MSC or between the HLR and the Gateway MSC.
8106 8107 8108 8109 8110

ServiceTerminationPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is VMSC or GMSC if Consumer is HLR CONSUMER INVOKES { istCommand}

8111 This package is v3 only.

1078

8112 17.2.2.51

1079 Release 4 1080 1081

271

3GPP TS 29.002 V4.17.0 (2006-06)

Mobility Management event notification

8113 This operation package includes the operations required for Mobility Management event notification procedures 8114 between VLR and gsmSCF.
8115 8116 8117 8118

MM-EventReportingPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is gsmSCF if Consumer is VLR CONSUMER INVOKES { noteMM-Event}

8119 This package is v3 only.

8120 17.2.2.52

Any time information handling

8121 This operation package includes the operations required for any time information handling procedures between gsmSCF 8122 and HLR.
8123 8124 8125 8126 8127 8128

AnyTimeInformationHandlingPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeSubscriptionInterrogation, anyTimeModification}

8129 This package is v3 only.

17.2.2.53

Subscriber Data modification notification

This operation package includes the operations required for Subscriber Data modification notification procedures between HLR and gsmSCF.
SubscriberDataModificationNotificationPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { noteSubscriberDataModified}

This package is v3 only.

8130 17.2.2.54

Authentication Failure Report

8131 This operation package includes the operation required for procedures between VLR and HLR or the SGSN and the 8132 HLR for reporting of authentication failures.
8133 8134 8135 8136 8137 8138

AuthenticationFailureReportPackage-v3 ::= OPERATION-PACKAGE


-- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { authenticationFailureReport}

8139 This package is v3 only.

8140 8141

17.3 Application contexts


17.3.1 General aspects

8142 An application-context is assigned for each dialogue established by a MAP-user. In the present document each 8143 application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and 8144 transmitted to the peer under certain circumstances.

1082

8145 The following ASN.1 MACRO is used to describe the main aspects of application-contexts in the following clauses:
8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167

1083 Release 4 1084 1085

272

3GPP TS 29.002 V4.17.0 (2006-06)

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

8168 8169 The following definitions are used throughout this clause: 8170 8171 8172

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;

8173 The names of v1-application-contexts are suffixed by "-v1" while other names are suffixed by "-vn" where n>=2. 8174 Application-contexts which do not belong to the v1 context set use v2 TC facilities. 8175 The last component of each application-context-name (i.e. the last component of the object identifier value) assigned to 8176 an application-context which belongs to the v1 context set indicates explicitly "version1". 8177 For each application-context which does not belong to the "v1 context set" there is a v1-equivalent application context. 8178 This is a v1-application-context which includes the v1-equivalents of the packages included in the original context. 8179 Each application-context uses the abstract-syntax associated with the operation-packages it includes and uses the 8180 transfer-syntax derived from it by applying the encoding rules defined in clause 17.1.1. 8181 ACs which do not belong to the v1 context set require the support of the abstract-syntax identified by the object 8182 identifier value: MAP-DialogueInformation.map-Dialogue-AS defined in clause 17.4.

8183 8184 17.3.2.1 8185 17.3.2.2

17.3.2 Application context definitions


Void Location Updating

8186 This application context is used between HLR and VLR for location updating procedures.
8187 8188 8189 8190 8191 8192 8193 8194 8195 8196

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)}

1086

8197 The following application-context-name is assigned to the v2-equivalent application-context:


8198 8199

1087 Release 4 1088 1089

273

3GPP TS 29.002 V4.17.0 (2006-06)

{map-ac networkLocUp(1) version2(2)}

8200 The following application-context-name is assigned to the v1-equivalent application-context:


8201 8202

{map-ac networkLocUp(1) version1(1)}

8203 17.3.2.3

Location Cancellation

8204 This application context is used between HLR and VLR or between HLR and SGSN for location cancellation 8205 procedures. For the HLR - SGSN interface only version 3 of this application context is applicable.
8206 8207 8208 8209 8210 8211

locationCancellationContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { LocationCancellationPackage-v3} ::= {map-ac locationCancel(2) version3(3)}

8212 The following application-context-name is assigned to the v2-equivalent application-context:


8213

map-ac locationCancel(2) version2(2)

8214 8215 The following application-context-name is assigned to the v1-equivalent application-context:


8216 8217

map-ac locationCancel(2) version1(1)

8218 17.3.2.4

Roaming number enquiry

8219 This application context is used between HLR and VLR for roaming number enquiry procedures.
8220 8221 8222 8223 8224 8225

roamingNumberEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { RoamingNumberEnquiryPackage-v3} ::= {map-ac roamingNbEnquiry(3) version3(3)}

8226 The following application-context-name is assigned to the v2-equivalent application-context:


8227 8228

{map-ac roamingNbEnquiry(3) version2(2)}

8229 The following application-context-name is assigned to the v1-equivalent application-context:


8230 8231

{map-ac roamingNbEnquiry(3) version1(1)}

8232 17.3.2.5 8233 17.3.2.6

Void Location Information Retrieval

8234 This application-context is used between GMSC and HLR or between GMSC and NPLR when retrieving location 8235 information. For the GMSC - NPLR interface version 1, version 2 and version 3 of this application context are 8236 applicable.
8237 8238 8239 8240 8241 8242

locationInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR or NPLR if Initiator is GMSC INITIATOR CONSUMER OF { InterrogationPackage-v3} ::= {map-ac locInfoRetrieval(5) version3(3)}

8243 The following application-context-name is assigned to the v2-equivalent application-context:


8244 8245 8246

{map-ac locInfoRetrieval(5) version2(2)}

8247 The following application-context-name is assigned to the v1-equivalent application-context:


8248

{map-ac locInfoRetrieval(5) version1(1)}

1090

1091 Release 4 1092 1093


8249

274

3GPP TS 29.002 V4.17.0 (2006-06)

8250 17.3.2.7

Call control transfer

8251 This application context is used for the call control transfer procedure between the VMSC and the GMSC.
8252 8253 8254 8255 8256 8257

callControlTransferContext-v4 APPLICATION-CONTEXT -- Responder is GMSC if Initiator is VMSC INITIATOR CONSUMER OF { CallControlTransferPackage-v4} ::= {map-ac callControlTransfer(6) version4(4)}

8258 The following application-context-name is assigned to the v3-equivalent application-context:


8259

{map-ac callControlTransfer(6) version3(3)}

8260 17.3.2.8

void

8261 17.3.2.9 - 17.3.2.10 Void 8262 17.3.2.11 Location registers restart

8263 This application context is used between HLR and VLR or between HLR and SGSN for location register restart 8264 procedures. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable.
8265 8266 8267 8268 8269 8270

resetContext-v2 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { ResetPackage-v2} ::= {map-ac reset(10) version2(2)}

8271 The following application-context-name is assigned to the v1-equivalent application-context:


8272 8273

{map-ac reset(10) version1(1)}

8274 17.3.2.12

Handover control

8275 This application context is used for handover procedures between MSCs.
8276 8277 8278 8279 8280

handoverControlContext-v3 APPLICATION-CONTEXT -- Responder is MSCB if Initiator is MSCA INITIATOR CONSUMER OF { HandoverControlPackage-v3} ::= {map-ac handoverControl(11) version3(3)}

8281 8282 The following application-context-name is assigned to the v2-equivalent application-context:


8283

{map-ac handoverControl(11) version2(2)}

8284
8285

8286 The following application-context-name is assigned to the v1-equivalent application-context:


8287 8288

{map-ac handoverControl(11) version1(1)}

8289 17.3.2.13

IMSI Retrieval

8290 This application context is used for IMSI retrieval between HLR and VLR.
8291 8292 8293 8294 8295 8296

imsiRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { IMSIRetrievalPackage-v2} ::= {map-ac imsiRetrieval(26) version2(2)}

8297 This application-context is v2 only.

1094

8298 17.3.2.14

1095 Release 4 1096 1097

275

3GPP TS 29.002 V4.17.0 (2006-06)

Equipment Management

8299 This application context is used for equipment checking between MSC and EIR or between SGSN and EIR. For the 8300 SGSN - EIR interface version 1 and version 2 of this application context are applicable:
8301 8302 8303 8304 8305 8306 8307

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)}

8308 The following application-context-name is assigned to the v1-equivalent application-context:


8309 8310

{map-ac equipmentMngt(13) version1(1)}

8311 17.3.2.15

Information retrieval

8312 This application context is used for authentication information retrieval between HLR and VLR or between HLR and 8313 SGSN. For the HLR - SGSN interface version 1 and version 2 and version 3 of this application context are applicable.
8314 8315 8316 8317 8318 8319 8320

infoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { InfoRetrievalPackage-v3} ::= {map-ac infoRetrieval(14) version3(3)}

8321 The following application-context-name is assigned to the v2-equivalent application-context:


8322 8323 8324 8325 8326 8327 8328

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)}

8329 The following application-context-name is assigned to the v1-equivalent application-context:


8330 8331

{map-ac infoRetrieval(14) version1(1)}

8332 17.3.2.16

Inter-VLR information retrieval

8333 This application context is used for information retrieval between VLRs.
8334 8335 8336 8337 8338 8339

interVlrInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { InterVlrInfoRetrievalPackage-v3} ::= {map-ac interVlrInfoRetrieval(15) version3(3)}

8340 The v2-equivalent application-context is:


8341 8342 8343 8344 8345 8346

interVlrInfoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { InterVlrInfoRetrievalPackage-v2} ::= {map-ac interVlrInfoRetrieval(15) version2(2)}

8347 The v1-equivalent application-context is:


8348 8349

{map-ac infoRetrieval(14) version1(1)}

1098

8350 17.3.2.17

1099 Release 4 1100 1101

276

3GPP TS 29.002 V4.17.0 (2006-06)

Stand Alone Subscriber Data Management

8351 This application context is used for stand alone subscriber data management between HLR and VLR or between HLR 8352 and SGSN. For the HLR - SGSN interface only version 3 of this application context is applicable:
8353 8354 8355 8356 8357 8358

subscriberDataMngtContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { SubscriberDataMngtStandAlonePackage-v3} ::= {map-ac subscriberDataMngt(16) version3(3)}

8359 The following application-context-name is assigned to the v2-equivalent application-context:


8360 8361

{map-ac subscriberDataMngt(16) version2(2)}

8362 The following application-context-name is assigned to the v1-equivalent application-context:


8363 8364

{map-ac subscriberDataMngt(16) version1(1)}

8365 17.3.2.18

Tracing

8366 This application context is used between HLR and VLR or between HLR and SGSN for stand alone tracing control 8367 procedures. For the HLR - SGSN interface version 1, version 2 and version 3 of this application context are applicable.
8368 8369 8370 8371 8372

tracingContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { TracingStandAlonePackage-v3} ::= {map-ac tracing(17) version3(3)}

8373 8374 The following application-context-name is assigned to the v2-equivalent application-context:


8375 8376

{map-ac tracing(17) version2(2)}

8377 The following application-context-name is assigned to the v1-equivalent application-context:


8378 8379

{map-ac tracing(17) version1(1)}

8380 17.3.2.19

Network functional SS handling

8381 This application context is used for functional-like SS handling procedures between VLR and HLR.
8382 8383 8384 8385 8386 8387

networkFunctionalSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { FunctionalSsPackage-v2} ::= {map-ac networkFunctionalSs(18) version2(2)}

8388 The v1-equivalent application-context is defined as follows:


8389 8390 8391 8392 8393 8394 8395 8396

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)}

1102

8397 17.3.2.20

1103 Release 4 1104 1105

277

3GPP TS 29.002 V4.17.0 (2006-06)

Network unstructured SS handling

8398 This application context is used for handling stimuli-like procedures between HLR and VLR, between the HLR and 8399 gsmSCF, and between HLR and HLR.
8400 8401 8402 8403 8404 8405 8406 8407 8408 8409

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 -- Responder is HLR, Initiator is HLR OPERATIONS OF { UnstructuredSsPackage-v2} ::= {map-ac networkUnstructuredSs(19) version2(2)}

8410 The following application-context-name is assigned to the v1-equivalent application-context:


8411 8412

{map-ac networkFunctionalSs(18) version1(1)}

8413 17.3.2.21

Short Message Gateway

8414 This application context is used for short message gateway procedures.
8415 8416 8417 8418 8419 8420

shortMsgGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { ShortMsgGatewayPackage-v3} ::= {map-ac shortMsgGateway(20) version3(3)}

8421 The following application-context-name is assigned to the v2-equivalent application-context:


8422 8423

{map-ac shortMsgGateway(20) version2(2)}

8424 The following application-context-name is assigned to the v1-equivalent application-context:


8425 8426

{map-ac shortMsgGateway(20) version1(1)}

8427 17.3.2.22

Mobile originating Short Message Relay

8428 This application context is used between MSC and IWMSC or between SGSN and IWMSC for mobile originating short 8429 message relay procedures. For the SGSN - IWMSC interface version 1, version 2 and version 3 of this application 8430 context are applicable.
8431 8432 8433 8434 8435 8436 8437

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)}

8438 The following application-context-name is assigned to the v2-equivalent application-context:


8439 8440

{map-ac shortMsgMO-Relay(21) version2(2)}

8441 The following application-context-name is assigned to the v1-equivalent application-context:


8442 8443

{map-ac shortMsg-Relay(21) version1(1)}

1106

8444 17.3.2.23 8445 17.3.2.24

1107 Release 4 1108 1109

278

3GPP TS 29.002 V4.17.0 (2006-06)

Void Short message alert

8446 This application context is used for short message alerting procedures.
8447 8448 8449 8450 8451 8452

shortMsgAlertContext-v2 APPLICATION-CONTEXT -- Responder is IWMSC if Initiator is HLR INITIATOR CONSUMER OF { AlertingPackage-v2} ::= {map-ac shortMsgAlert(23) version2(2)}

8453 The following application-context-name is symbolically assigned to the v1-equivalent application-context:


8454 8455

{map-ac shortMsgAlert(23) version1(1)}

8456 17.3.2.25

Short message waiting data management

8457 This application context is used between VLR and HLR or between SGSN and HLR for short message waiting data 8458 management procedures. For the SGSN - HLR interface only version 3 of this application context is applicable.
8459 8460 8461 8462 8463 8464

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)}

8465 8466 The following application-context-name is assigned to the v2-equivalent application-context:


8467

{map-ac mwdMngt(24) version2(2)}

8468 8469 The following application-context-name is assigned to the v1-equivalent application-context:


8470 8471

{map-ac mwdMngt(24) version1(1)}

8472 17.3.2.26

Mobile terminating Short Message Relay

8473 This application context is used between GMSC and MSC or between GMSC and SGSN for mobile terminating short 8474 message relay procedures. For the GMSC - SGSN interface version 2 and version 3 of this application context and the 8475 equivalent version 1 application context are applicable.
8476 8477 8478 8479 8480 8481

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)}

8482 The following application-context-name is assigned to the v2-equivalent application-context:


8483 8484

{map-ac shortMsgMT-Relay(25) version2(2)}

8485 The following application-context-name is assigned to the v1-equivalent application-context:


8486 8487

{map-ac shortMsgMO-Relay(21) version1(1)}

1110

8488 17.3.2.27

1111 Release 4 1112 1113

279

3GPP TS 29.002 V4.17.0 (2006-06)

MS purging

8489 This application context is used between HLR and VLR or between HLR and SGSN for MS purging procedures. For 8490 the SGSN - HLR interface only version 3 of this application context is applicable.
8491 8492 8493 8494 8495 8496 8497

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)}

8498 The following application-context-name is assigned to the v2-equivalent application-context:


8499

{map-ac msPurging(27) version2(2)}

8500

8501 17.3.2.28

Subscriber information enquiry

8502 This application context is used between HLR and VLR for subscriber information enquiry procedures.
8503 8504 8505 8506 8507 8508

subscriberInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { SubscriberInformationEnquiryPackage-v3} ::= {map-ac subscriberInfoEnquiry(28) version3(3)}

8509 This application-context is v3 only.

8510 17.3.2.29

Any time information enquiry

8511 This application context is used between gsmSCF and HLR or GMLC for any time information enquiry procedures.
8512 8513 8514 8515 8516 8517

anyTimeInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is HLR or GMLC if Initiator is gsmSCF INITIATOR CONSUMER OF { AnyTimeInformationEnquiryPackage-v3} ::= {map-ac anyTimeInfoEnquiry(29) version3(3)}

8518 This application-context is v3 only.

8519 17.3.2.30

Group Call Control

8520 This application context is used between anchor MSC and relay MSC for group call and broadcast call procedures.
8521 8522 8523 8524 8525 8526

groupCallControlContext-v3 APPLICATION-CONTEXT -- Responder is relay MSC if Initiator is anchor MSC INITIATOR CONSUMER OF { GroupCallControlPackage-v3} ::= {map-ac groupCallControl(31) version3(3)}

8527 This application-context is v3 only.

8528 17.3.2.31

Provide SIWFS Number

8529 This application context is used for activation or modification of SIWF resources.
8530 8531 8532 8533 8534 8535 8536

sIWFSAllocationContext-v3 APPLICATION-CONTEXT

-- Responder is SIWF if Initiater is VMSC INITIATOR CONSUMER OF { ProvideSIWFSNumberPackage-v3, SIWFSSignallingModifyPackage-v3} ::= {map-ac sIWFSAllocation (12) version3(3)}

8537 This application-context is v3 only.

1114

8538 17.3.2.32

1115 Release 4 1116 1117

280

3GPP TS 29.002 V4.17.0 (2006-06)

Gprs Location Updating

8539 This application context is used between HLR and SGSN for gprs location updating procedures.
8540 8541 8542 8543 8544 8545 8546 8547 8548

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)}

8549 This application-context is v3 only.

8550 17.3.2.33

Gprs Location Information Retreival

8551 This application context is used between HLR and GGSN when retrieving gprs location information.
8552 8553 8554 8555 8556

gprsLocationInfoRetrievalContext-v4 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { GprsInterrogationPackage-v4} ::= {map-ac gprsLocationInfoRetrieval(33) version4(4)}

8557 8558 The following application-context-name is assigned to the v3-equivalent application-context:


8559 8560 8561

{map-ac gprsLocationInfoRetrieval(33) version3(3)}

8562 17.3.2.34

Failure Reporting

8563 This application context is used between HLR and GGSN to inform that network requested PDP-context activation has 8564 failed.
8565 8566 8567 8568 8569 8570

failureReportContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { FailureReportingPackage-v3} ::= {map-ac failureReport(34) version3(3)}

8571 This application-context is v3 only.

8572 17.3.2.35

GPRS Notifying

8573 This application context is used between HLR and GGSN for notifying that GPRS subscriber is present again.
8574 8575 8576 8577 8578 8579

gprsNotifyContext-v3 APPLICATION-CONTEXT -- Responder is GGSN if Initiator is HLR INITIATOR CONSUMER OF { GprsNotifyingPackage-v3} ::= {map-ac gprsNotify(35) version3(3)}

8580 This application-context is v3 only.

8581 17.3.2.36

Supplementary Service invocation notification

8582 This application context is used between the MSC and the gsmSCF and between the HLR and the gsmSCF for 8583 Supplementary Service invocation notification procedures.
8584 8585 8586 8587 8588 8589 8590

ss-InvocationNotificationContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is MSC -- Responder is gsmSCF, Initiator is HLR INITIATOR CONSUMER OF { SS-InvocationNotificationPackage-v3} ::= {map-ac ss-InvocationNotification(36) version3(3)}

8591 This application-context is v3 only.

1118

8592 17.3.2.37

1119 Release 4 1120 1121

281

3GPP TS 29.002 V4.17.0 (2006-06)

Reporting

8593 This application context is used between HLR and VLR for reporting procedures.
8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605

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)}

8606 This application-context is v3 only.

8607 17.3.2.38

Call Completion

8608 This application context is used between VLR and the HLR for subscriber control of call completion services.
8609 8610 8611 8612 8613 8614

callCompletionContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { CallCompletionPackage-v3} ::= {map-ac callCompletion(8) version3(3)}

8615 This application-context is v3 only.

1122

8616 17.3.2.39

1123 Release 4 1124 1125

282

3GPP TS 29.002 V4.17.0 (2006-06)

Location Service Gateway

8617 This application context is used for location service gateway procedures.
8618 8619 8620 8621 8622

locationSvcGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMLC INITIATOR CONSUMER OF { locationSvcGatewayPackage-v3} ::= {map-ac locationSvcGateway(37) version3(3)}

8623 8624 17.3.2.40 Location Service Enquiry

8625 This application context is used for location service enquiry procedures.
8626 8627 8628 8629 8630 8631 8632 8633

locationSvcEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is MSC or SGSN if Initiator is GMLC -- Responder is GMLC if Initiator is MSC -- Responder is GMLC if Initiator is SGSN INITIATOR CONSUMER OF { locationSvcEnquiryPackage-v3, locationSvcReportingPackage-v3} ::= {map-ac locationSvcEnquiry(38) version3 (3)}

8634

8635 17.3.2.41 8636 17.3.2.42 8637 17.3.2.43 8638 17.3.2.44

Void Void Void IST Alerting

8639 This application context is used between MSC (Visited MSC or Gateway MSC) and HLR for alerting services within 8640 IST procedures.
8641 8642 8643 8644 8645 8646 8647

istAlertingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VMSC -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { IST-AlertingPackage-v3} ::= {map-ac alerting(4) version3(3)}

8648 This application-context is v3 only.

8649 17.3.2.45

Service Termination

8650 This application context is used between HLR and MSC (Visited MSC or Gateway MSC) for service termination 8651 services within IST procedures.
8652 8653 8654 8655 8656 8657

serviceTerminationContext-v3 APPLICATION-CONTEXT -- Responder is VMSC or GMSC if Initiator is HLR INITIATOR CONSUMER OF { ServiceTerminationPackage-v3} ::= {map-ac serviceTermination(9) version3(3)}

8658 This application-context is v3 only.

1126

8659 17.3.2.46

1127 Release 4 1128 1129

283

3GPP TS 29.002 V4.17.0 (2006-06)

Mobility Management event notification

8660 This application context is used between VLR and gsmSCF for Mobility Management event notification procedures.
8661 8662 8663 8664 8665 8666

mm-EventReportingContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is VLR INITIATOR CONSUMER OF { MM-EventReportingPackage-v3} ::= {map-ac mm-EventReporting(42) version3(3)}

8667 This application-context is v3 only.

8668 17.3.2.47

Any time information handling

8669 This application context is used between gsmSCF and HLR for any time information handling procedures.
8670 8671 8672 8673 8674 8675

anyTimeInfohandlingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is gsmSCF INITIATOR CONSUMER OF { AnyTimeInformationHandlingPackage-v3} ::= {map-ac anyTimeInfoHandling(43) version3(3)}

8676 This application-context is v3 only.

8677 17.3.2.48

Subscriber Data modification notification

This application context is used between HLR and gsmSCF for Subscriber Data modification notification procedures.
subscriberDataModificationNotificationContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is HLR INITIATOR CONSUMER OF { SubscriberDataModificationNotificationPackage-v3} ::= {map-ac subscriberDataModificationNotification(22) version3(3)}

This application-context is v3 only.

8678 17.3.2.49

Authentication Failure Report

8679 This application context is used between VLR and HLR or SGSN and HLR for reporting of authentication failures.
8680 8681 8682 8683 8684 8685 8686

authenticationFailureReportContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { AuthenticationFailureReportPackage-v3 } ::= {map-ac authenticationFailureReport(39) version3(3)}

8687 This application-context is v3 only.

8688

17.3.3 ASN.1 Module for application-context-names


The following ASN.1 module summarises the application-context-name assigned to MAP application-contexts.
MAP-ApplicationContexts { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ApplicationContexts (2) version7 (7)} DEFINITIONS ::= BEGIN -- EXPORTS everything IMPORTS gsm-NetworkId, ac-Id

8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705

1130

1131 Release 4 1132 1133


8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780

284

3GPP TS 29.002 V4.17.0 (2006-06)

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)} authenticationFailureReportContext-v3 OBJECT IDENTIFIER ::= {map-ac authenticationFailureReport(39) version3(3)} locationInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac locInfoRetrieval(5) version3(3)} resetContext-v2 OBJECT IDENTIFIER ::= {map-ac reset(10) version2(2)} handoverControlContext-v3 OBJECT IDENTIFIER ::= {map-ac handoverControl(11) version3(3)} equipmentMngtContext-v2 OBJECT IDENTIFIER ::= {map-ac equipmentMngt(13) version2(2)} infoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac infoRetrieval(14) version3(3)} interVlrInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac interVlrInfoRetrieval(15) version3(3)} 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

OBJECT IDENTIFIER ::= {map-ac subscriberInfoEnquiry(28) version3(3)}

1134

1135 Release 4 1136 1137 8781 anyTimeInfoEnquiryContext-v3


8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839

285

3GPP TS 29.002 V4.17.0 (2006-06)

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-v4 OBJECT IDENTIFIER ::= {map-ac gprsLocationInfoRetrieval(33) version4(4)} 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)} istAlertingContext-v3 OBJECT IDENTIFIER ::= {map-ac istAlerting(4) version3(3)} serviceTerminationContext-v3 OBJECT IDENTIFIER ::= {map-ac immediateTermination(9) version3(3)} locationSvcGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcGateway(37) version3(3)} locationSvcEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcEnquiry(38) version3(3)} mm-EventReportingContext-v3 OBJECT IDENTIFIER ::= {map-ac mm-EventReporting(42) version3(3)}

anyTimeInfoHandlingContext-v3

OBJECT IDENTIFIER ::= {map-ac anyTimeInfoHandling(43) version3(3)}

subscriberDataModificationNotificationContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberDataModificationNotification(22) version3(3)} -- The following Object Identifiers are reserved for application-- contexts existing in previous versions of the protocol

1138

1139 Release 4 1140 1141


8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874

286

3GPP TS 29.002 V4.17.0 (2006-06)

-- AC Name & Version

--- networkLocUpContext-v1 -- networkLocUpContext-v2 -- locationCancellationContext-v1 -- locationCancellationContext-v2 -- roamingNumberEnquiryContext-v1 -- roamingNumberEnquiryContext-v2 -- locationInfoRetrievalContext-v1 -- locationInfoRetrievalContext-v2 -- resetContext-v1 -- handoverControlContext-v1 -- handoverControlContext-v2 -- equipmentMngtContext-v1 -- infoRetrievalContext-v1 -- infoRetrievalContext-v2 -- interVlrInfoRetrievalContext-v2 -- 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 -- gprsLocationInfoRetrievalContext-v3

Object Identifier
map-ac networkLocUp (1) version1 (1) map-ac networkLocUp (1) version2 (2) map-ac locationCancellation (2) version1 (1) map-ac locationCancellation (2) version2 (2) map-ac roamingNumberEnquiry (3) version1 (1) map-ac roamingNumberEnquiry (3) version2 (2) map-ac locationInfoRetrieval (5) version1 (1) map-ac locationInfoRetrieval (5) version2 (2) map-ac reset (10) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version2 (2) map-ac equipmentMngt (13) version1 (1) map-ac infoRetrieval (14) version1 (1) map-ac infoRetrieval (14) version2 (2) map-ac interVlrInfoRetrieval (15) version2 (2) map-ac subscriberDataMngt (16) version1 (1) map-ac subscriberDataMngt (16) version2 (2) map-ac tracing (17) version1 (1) map-ac tracing (17) version2 (2) map-ac networkFunctionalSs (18) version1 (1) map-ac shortMsgGateway (20) version1 (1) map-ac shortMsgGateway (20) version2 (2) map-ac shortMsgRelay (21) version1 (1) map-ac shortMsgAlert (23) version1 (1) map-ac mwdMngt (24) version1 (1) map-ac mwdMngt (24) version2 (2) map-ac shortMsgMT-Relay (25) version2 (2) map-ac msPurging (27) version2 (2) map-ac callControlTransferContext (6) version3 (3) map-ac gprsLocationInfoRetrievalContext (33) version3 (3)

END

8875
8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914

17.4 MAP Dialogue Information


MAP-DialogueInformation { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-DialogueInformation (3) version7 (7)} 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) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ;

1142

1143 Release 4 1144 1145


8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987

287

3GPP TS 29.002 V4.17.0 (2006-06)

-- 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 map-refuse map-userAbort map-providerAbort [0] [1] [2] [3] [4] [5] MAP-OpenInfo, MAP-AcceptInfo, MAP-CloseInfo, MAP-RefuseInfo, MAP-UserAbortInfo, 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 alternativeApplicationContext OBJECT IDENTIFIER -- alternativeApplicationContext must not be used in version 2 } Reason ::= ENUMERATED { noReasonGiven invalidDestinationReference invalidOriginatingReference (0), (1), (2) }

OPTIONAL

OPTIONAL

OPTIONAL, OPTIONAL

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)}

1146

1147 Release 4 1148 1149


8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000

288

3GPP TS 29.002 V4.17.0 (2006-06)

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

9001
9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062

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) version7 (7)} DEFINITIONS ::= BEGIN IMPORTS UpdateLocation, CancelLocation, PurgeMS, SendIdentification, UpdateGprsLocation, PrepareHandover, SendEndSignal, ProcessAccessSignalling, ForwardAccessSignalling, PrepareSubsequentHandover, SendAuthenticationInfo, AuthenticationFailureReport, CheckIMEI, InsertSubscriberData, DeleteSubscriberData, Reset, ForwardCheckSS-Indication, RestoreData, ProvideSubscriberInfo, AnyTimeInterrogation, AnyTimeSubscriptionInterrogation, AnyTimeModification, SendRoutingInfoForGprs, FailureReport, NoteMsPresentForGprs, NoteMM-Event, NoteSubscriberDataModified FROM MAP-MobileServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version7 (7)} ActivateTraceMode, DeactivateTraceMode, SendIMSI FROM MAP-OperationAndMaintenanceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version7 (7)} SendRoutingInfo, ProvideRoamingNumber, ResumeCallHandling, ProvideSIWFSNumber, SIWFSSignallingModify, SetReportingState, StatusReport, RemoteUserFree,

1150

1151 Release 4 1152 1153


9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141

289

3GPP TS 29.002 V4.17.0 (2006-06)

IST-Alert, IST-Command FROM MAP-CallHandlingOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version7 (7)} RegisterSS, EraseSS, 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) version7 (7)} 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) version7 (7)} 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) version7 (7)} ProvideSubscriberLocation, SendRoutingInfoForLCS, SubscriberLocationReport FROM MAP-LocationServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version7 (7)} 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,

1154

1155 Release 4 1156 1157


9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218
9162

290

3GPP TS 29.002 V4.17.0 (2006-06)

ForwardingFailed, CUG-Reject, ATI-NotAllowed, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM, ResourceLimitation, NoGroupCallNumberAvailable, ShortTermDenial, LongTermDenial, IncompatibleTerminal, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, UnknownOrUnreachableLCSClient, ATSI-NotAllowed, ATM-NotAllowed, InformationNotAvailable, MM-EventNotSupported, TargetCellOutsideGroupCallArea

FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} ; -- 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 authenticationFailureReport AuthenticationFailureReport ::= localValue 15 -- IMEI MANAGEMENT operation codes checkIMEI CheckIMEI ::= localValue 43

-- subscriber management operation codes insertSubscriberData deleteSubscriberData InsertSubscriberData ::= localValue 7 DeleteSubscriberData ::= localValue 8

-- fault recovery operation codes

1158

1159 Release 4 1160 1161


9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294

291

3GPP TS 29.002 V4.17.0 (2006-06)

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 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 istAlert IST-Alert ::= localValue 87 istCommand IST-Command ::= localValue 88 -- 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

-- any time information handling operation codes

anyTimeSubscriptionInterrogation AnyTimeSubscriptionInterrogation ::= localValue 62 anyTimeModification AnyTimeModification ::= localValue 65


-- subscriber data modification notification operation codes

noteSubscriberDataModified

NoteSubscriberDataModified ::= localValue 5

-- supplementary service invocation notification operation codes

ss-InvocationNotification

SS-InvocationNotification ::= localValue 72

1162

1163 Release 4 1164 1165


9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371

292

3GPP TS 29.002 V4.17.0 (2006-06)

--Group Call operation codes 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

-- Location service operation codes provideSubscriberLocation ProvideSubscriberLocation ::= localValue 83 sendRoutingInfoForLCS SendRoutingInfoForLCS ::= localValue 85 subscriberLocationReport SubscriberLocationReport ::= localValue 86 -- Mobility Management operation codes noteMM-Event NoteMM-Event ::= localValue 89

-- 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 NoHandoverNumberAvailable ::= localValue 25 subsequentHandoverFailure SubsequentHandoverFailure ::= localValue 26 targetCellOutsideGroupCallArea TargetCellOutsideGroupCallArea ::= localValue 42

1166

1167 Release 4 1168 1169


9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444

293

3GPP TS 29.002 V4.17.0 (2006-06)

-- operation and maintenance error codes tracingBufferFull TracingBufferFull ::= localValue 40

-- call handling error codes 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

-- any time information handling error codes atsi-NotAllowed ATSI-NotAllowed ::= localValue 60 atm-NotAllowed ATM-NotAllowed ::= localValue 61 informationNotAvailable InformationNotAvailable ::= localValue 62 -- Group Call error codes noGroupCallNumberAvailable

NoGroupCallNumberAvailable ::= localValue 50

-- supplementary service error codes 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

-- Mobility Management error codes mm-EventNotSupported MM-EventNotSupported ::= localValue 59

-- The following operation codes are reserved for operations -- existing in previous versions of the protocol

1170

1171 Release 4 1172 1173


9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467

294
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)

3GPP TS 29.002 V4.17.0 (2006-06)


Oper. Code localValue 9 localValue 19 localValue 28 localValue 30 localValue 35 localValue 48 localValue 49 localValue 52 localValue 54

-- Operation Name --- sendParameters -- processUnstructuredSS-Data -- performHandover -- performSubsequentHandover -- noteInternalHandover -- noteSubscriberPresent -- alertServiceCentreWithoutResult -- traceSubscriberActivity -- beginSubscriberActivity

-- 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

9468 9469
9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516

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) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS -- location registration operations UpdateLocation, CancelLocation, PurgeMS, SendIdentification, -- gprs location registration operations UpdateGprsLocation, -- subscriber information enquiry operations ProvideSubscriberInfo, -- any time information enquiry operations AnyTimeInterrogation, -- any time information handling operations AnyTimeSubscriptionInterrogation, AnyTimeModification, -- subscriber data modification notification operations NoteSubscriberDataModified, -- handover operations PrepareHandover, SendEndSignal, ProcessAccessSignalling, ForwardAccessSignalling, PrepareSubsequentHandover, -- authentication management operations SendAuthenticationInfo, AuthenticationFailureReport,

1174

1175 Release 4 1176 1177


9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595

295

3GPP TS 29.002 V4.17.0 (2006-06)

-- 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, -- Mobility Management operations NoteMM-Event

; 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, MM-EventNotSupported, ATSI-NotAllowed, ATM-NotAllowed, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-Incompatibility, SS-SubscriptionViolation, InformationNotAvailable, TargetCellOutsideGroupCallArea FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationArg, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes, PrepareHO-Arg, PrepareHO-Res, ForwardAccessSignalling-Arg, ProcessAccessSignalling-Arg,

1178

1179 Release 4 1180 1181


9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613 9614 9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666

296

3GPP TS 29.002 V4.17.0 (2006-06)

SendEndSignal-Arg, SendEndSignal-Res, PrepareSubsequentHO-Res, PrepareSubsequentHO-Arg, SendAuthenticationInfoArg, SendAuthenticationInfoRes, AuthenticationFailureReportArg, AuthenticationFailureReportRes, EquipmentStatus, InsertSubscriberDataArg, InsertSubscriberDataRes, DeleteSubscriberDataArg, DeleteSubscriberDataRes, ResetArg, RestoreDataArg, RestoreDataRes, ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, AnyTimeSubscriptionInterrogationArg, AnyTimeSubscriptionInterrogationRes, AnyTimeModificationArg, AnyTimeModificationRes, NoteSubscriberDataModifiedArg, NoteSubscriberDataModifiedRes, AnyTimeInterrogationArg, AnyTimeInterrogationRes, SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, FailureReportArg, FailureReportRes, NoteMsPresentForGprsArg, NoteMsPresentForGprsRes, NoteMM-EventArg, NoteMM-EventRes

FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version7 (7)} IMEI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ; -- 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} --Timer m UpdateLocationArg UpdateLocationRes

--Timer m CancelLocationArg CancelLocationRes

1182

1183 Release 4 1184 1185


9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743

297

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer m

PurgeMS ::= OPERATION ARGUMENT purgeMS-Arg RESULT purgeMS-Res -- optional ERRORS{ DataMissing, UnexpectedDataValue, UnknownSubscriber} SendIdentification ::= OPERATION ARGUMENT sendIdentificationArg RESULT sendIdentificationRes ERRORS { DataMissing, UnidentifiedSubscriber} -- gprs location registration operations UpdateGprsLocation ::= OPERATION ARGUMENT updateGprsLocationArg RESULT updateGprsLocationRes ERRORS { SystemFailure, UnexpectedDataValue, UnknownSubscriber, RoamingNotAllowed}

PurgeMS-Arg PurgeMS-Res

--Timer s SendIdentificationArg 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

-- any time information handling operations

AnyTimeSubscriptionInterrogation ::= OPERATION

--Timer m ARGUMENT anyTimeSubscriptionInterrogationArg AnyTimeSubscriptionInterrogationArg RESULT anyTimeSubscriptionInterrogationRes AnyTimeSubscriptionInterrogationRes ERRORS { ATSI-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-NotAvailable, InformationNotAvailable}

1186

1187 Release 4 1188 1189


9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818

298

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer m

AnyTimeModification ::= OPERATION ARGUMENT anyTimeModificationArg RESULT anyTimeModificationRes ERRORS { ATM-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-SubscriptionViolation, SS-ErrorStatus, SS-Incompatibility, InformationNotAvailable}

AnyTimeModificationArg AnyTimeModificationRes

-- subscriber data modification notification operations NoteSubscriberDataModified ::= OPERATION ARGUMENT noteSubscriberDataModifiedArg NoteSubscriberDataModifiedArg RESULT noteSubscriberDataModifiedRes NoteSubscriberDataModifiedRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber} -- handover operations PrepareHandover ::= OPERATION ARGUMENT prepareHO-Arg PrepareHO-Arg RESULT prepareHO-Res PrepareHO-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, NoHandoverNumberAvailable, TargetCellOutsideGroupCallArea } SendEndSignal ::= OPERATION ARGUMENT sendEndSignal-Arg RESULT sendEndSignal-Res ProcessAccessSignalling ::= OPERATION ARGUMENT processAccessSignalling-Arg ForwardAccessSignalling ::= OPERATION ARGUMENT forwardAccessSignalling-Arg PrepareSubsequentHandover ::= OPERATION ARGUMENT prepareSubsequentHO-Arg RESULT prepareSubsequentHO-Res ERRORS { UnexpectedDataValue, DataMissing, UnknownMSC, SubsequentHandoverFailure} -- authentication management operations --Timer m --Timer m

--Timer l SendEndSignal-Arg SendEndSignal-Res --Timer s ProcessAccessSignalling-Arg --Timer s ForwardAccessSignalling-Arg --Timer m PrepareSubsequentHO-Arg PrepareSubsequentHO-Res

1190

1191 Release 4 1192 1193


9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890

299

3GPP TS 29.002 V4.17.0 (2006-06)

SendAuthenticationInfo ::= OPERATION --Timer m ARGUMENT sendAuthenticationInfoArg SendAuthenticationInfoArg -- optional -- within a dialogue sendAuthenticationInfoArg shall not be present in -- subsequent invoke components. If received in a subsequent invoke component -- it shall be discarded. RESULT sendAuthenticationInfoRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} SendAuthenticationInfoRes

AuthenticationFailureReport ::= OPERATION --Timer m ARGUMENT authenticationFailureReportArg AuthenticationFailureReportArg RESULT authenticationFailureReportRes AuthenticationFailureReportRes -- optional ERRORS { SystemFailure, 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 ResetArg --Timer s --Timer m InsertSubscriberDataArg InsertSubscriberDataRes --Timer m IMEI EquipmentStatus

--Timer m DeleteSubscriberDataArg DeleteSubscriberDataRes

1194

1195 Release 4 1196 1197


9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957

300

3GPP TS 29.002 V4.17.0 (2006-06)


--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, CallBarred } -- 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} NoteMM-Event ::= OPERATION ARGUMENT noteMM-EventArg RESULT noteMM-EventRes ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber, MM-EventNotSupported} END --Timer m NoteMsPresentForGprsArg NoteMsPresentForGprsRes --Timer m FailureReportArg FailureReportRes --Timer m SendRoutingInfoForGprsArg SendRoutingInfoForGprsRes

--Timer m NoteMM-EventArg NoteMM-EventRes

9958
9959 9960 9961 9962 9963 9964 9965 9966

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) version7 (7)} DEFINITIONS ::=

1198

9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002 10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044

1199 Release 4 1200 1201


BEGIN EXPORTS ActivateTraceMode, DeactivateTraceMode, SendIMSI ;

301

3GPP TS 29.002 V4.17.0 (2006-06)

IMPORTS OPERATION FROM TCAPMessages { 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) version7 (7)} 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) version7 (7)} ISDN-AddressString, IMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ; 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} --Timer m ActivateTraceModeArg ActivateTraceModeRes

--Timer m DeactivateTraceModeArg DeactivateTraceModeRes

--Timer m ISDN-AddressString IMSI

1202

10045

1203 Release 4 1204 1205


END

302

3GPP TS 29.002 V4.17.0 (2006-06)

10046
10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080 10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 10111 10112 10113 10114 10115 10116 10117 10118 10119 10120 10121
10093 10094

17.6.3 Call Handling Operations


MAP-CallHandlingOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS SendRoutingInfo, ProvideRoamingNumber, ResumeCallHandling, ProvideSIWFSNumber, SIWFSSignallingModify, SetReportingState, StatusReport, RemoteUserFree, IST-Alert, IST-Command ; 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) version7 (7)} SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg, ResumeCallHandlingRes, ProvideSIWFSNumberArg, ProvideSIWFSNumberRes, SIWFSSignallingModifyArg, SIWFSSignallingModifyRes, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes, IST-AlertArg, IST-AlertRes, IST-CommandArg, IST-CommandRes FROM MAP-CH-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0)

1206

10122 10123 10124 10125 10126 10127 10128 10129 10130 10131 10132 10133 10134 10135 10136 10137 10138 10139 10140 10141 10142 10143 10144 10145 10146 10147 10148 10149 10150 10151 10152 10153 10154 10155 10156 10157 10158 10159 10160 10161 10162 10163 10164 10165 10166 10167 10168 10169 10170 10171 10172 10173 10174 10175 10176 10177 10178 10179 10180 10181 10182 10183 10184 10185 10186 10187 10188 10189 10190 10191 10192 10193 10194 10195 10196 10197 10198

1207 Release 4 1208 1209


;

303

3GPP TS 29.002 V4.17.0 (2006-06)

gsm-Network (1) modules (3) map-CH-DataTypes (13) version7 (7)}

SendRoutingInfo ::= OPERATION --Timer m -- The timer is set to the upper limit of the range if the GMSC supports pre-paging. ARGUMENT sendRoutingInfoArg SendRoutingInfoArg RESULT sendRoutingInfoRes SendRoutingInfoRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, UnknownSubscriber, NumberChanged, BearerServiceNotProvisioned, TeleserviceNotProvisioned, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, CUG-Reject, ForwardingViolation} ProvideRoamingNumber ::= OPERATION --Timer m -- The timer is set to the upper limit of the range if the HLR supports pre-paging. ARGUMENT provideRoamingNumberArg ProvideRoamingNumberArg RESULT provideRoamingNumberRes 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} --Timer m ResumeCallHandlingArg ResumeCallHandlingRes

--Timer m ProvideSIWFSNumberArg ProvideSIWFSNumberRes

--Timer m SIWFSSignallingModifyArg SIWFSSignallingModifyRes

1210

10199 10200 10201 10202 10203 10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225 10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264

1211 Release 4 1212 1213

304

3GPP TS 29.002 V4.17.0 (2006-06)


--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} IST-Alert ::= OPERATION ARGUMENT istAlertArg RESULT istAlertRes -- optional ERRORS { UnexpectedDataValue, ResourceLimitation, UnknownSubscriber, SystemFailure, FacilityNotSupported} IST-Command ::= OPERATION ARGUMENT istCommandArg RESULT istCommandRes -- optional ERRORS { UnexpectedDataValue, ResourceLimitation, UnknownSubscriber, SystemFailure, FacilityNotSupported} END

SetReportingStateArg SetReportingStateRes

--Timer m StatusReportArg StatusReportRes

--Timer ml RemoteUserFreeArg RemoteUserFreeRes

--Timer m IST-AlertArg IST-AlertRes

--Timer m IST-CommandArg IST-CommandRes

10265
10266 10267 10268 10269 10270 10271 10272 10273 10274

17.6.4 Supplementary service operations


MAP-SupplementaryServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version7 (7)} DEFINITIONS ::=

1214

10275 10276 10277 10278 10279 10280 10281 10282 10283 10284 10285 10286 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301 10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351
10287 10288

1215 Release 4 1216 1217


BEGIN EXPORTS RegisterSS, EraseSS, ActivateSS, DeactivateSS, InterrogateSS, ProcessUnstructuredSS-Request, UnstructuredSS-Request, UnstructuredSS-Notify, RegisterPassword, GetPassword, SS-InvocationNotification, RegisterCC-Entry, EraseCC-Entry ;

305

3GPP TS 29.002 V4.17.0 (2006-06)

IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, 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) version7 (7)} 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) version7 (7)} SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)} ; -- supplementary service handling operations

1218

10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364 10365 10366 10367 10368 10369 10370 10371 10372 10373 10374 10375 10376 10377 10378 10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419 10420 10421 10422 10423 10424

1219 Release 4 1220 1221

306

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer m

RegisterSS ::= OPERATION ARGUMENT registerSS-Arg RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-Incompatibility} 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}

RegisterSS-Arg SS-Info

--Timer m SS-ForBS-Code SS-Info

--Timer m SS-ForBS-Code SS-Info

--Timer m SS-ForBS-Code SS-Info

1222

10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448 10449 10450 10451 10452 10453 10454 10455 10456 10457 10458 10459 10460 10461 10462 10463 10464 10465 10466 10467 10468 10469 10470 10471 10472 10473 10474 10475 10476 10477 10478 10479 10480 10481 10482 10483 10484 10485 10486 10487 10488 10489 10490 10491 10492 10493 10494 10495 10496 10497 10498

1223 Release 4 1224 1225

307

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer m

InterrogateSS ::= OPERATION ARGUMENT ss-ForBS RESULT interrogateSS-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-NotAvailable}

SS-ForBS-Code InterrogateSS-Res

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}

--Timer 10 minutes

--Timer ml USSD-Arg USSD-Res

--Timer ml USSD-Arg

--Timer ml SS-Code Password

1226

10499 10500 10501 10502 10503 10504


10505 10506 10507 10508 10509 10510 10511 10512 10513 10514

1227 Release 4 1228 1229

308

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer m

GetPassword ::= OPERATION ARGUMENT guidanceInfo RESULT currentPassword SS-InvocationNotification ::= OPERATION ARGUMENT ss-InvocationNotificationArg RESULT ss-InvocationNotificationRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber} 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

GuidanceInfo Password --Timer m SS-InvocationNotificationArg SS-InvocationNotificationRes

10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530 10531 10532 10533 10534 10535 10536 10537 10538 10539 10540 10541 10542 10543 10544 10545 10546

--Timer m RegisterCC-EntryArg RegisterCC-EntryRes

--Timer m EraseCC-EntryArg EraseCC-EntryRes

10547
10548 10549 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 10565 10566 10567 10568 10569 10570 10571 10572 10573 10574 10575 10576

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) version7 (7)} 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,

1230

10577 10578 10579 10580 10581 10582 10583 10584 10585 10586 10587 10588 10589 10590 10591 10592 10593 10594 10595 10596 10597 10598 10599 10600 10601 10602 10603 10604 10605 10606 10607 10608 10609 10610 10611 10612 10613 10614 10615 10616 10617 10618 10619 10620 10621 10622 10623 10624 10625 10626 10627 10628 10629 10630 10631 10632 10633 10634 10635 10636 10637 10638 10639

1231 Release 4 1232 1233

309

3GPP TS 29.002 V4.17.0 (2006-06)

FacilityNotSupported, UnknownSubscriber, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, TeleserviceNotProvisioned, 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) version7 (7)} 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) version7 (7)}

; 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} --Timer m RoutingInfoForSM-Arg RoutingInfoForSM-Res

--Timer ml MO-ForwardSM-Arg MO-ForwardSM-Res

1234

10640 10641 10642 10643 10644 10645 10646 10647 10648 10649 10650 10651 10652 10653 10654 10655 10656 10657 10658 10659 10660 10661 10662 10663 10664 10665 10666 10667 10668 10669 10670 10671 10672 10673 10674 10675 10676 10677 10678 10679 10680 10681 10682 10683 10684 10685 10686 10687 10688 10689 10690 10691 10692 10693 10694 10695

1235 Release 4 1236 1237

310

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer ml

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} 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

MT-ForwardSM-Arg MT-ForwardSM-Res

--Timer s ReportSM-DeliveryStatusArg ReportSM-DeliveryStatusRes

--Timer s AlertServiceCentreArg

--Timer s InformServiceCentreArg --Timer m ReadyForSM-Arg ReadyForSM-Res

10696
10697 10698 10699 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 10712 10713 10714 10715

17.6.6 Errors
MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS -- generic errors SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, IncompatibleTerminal, ResourceLimitation,

1238

10716 10717 10718 10719 10720 10721 10722 10723 10724 10725 10726 10727 10728 10729 10730 10731 10732 10733 10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784 10785 10786 10787 10788 10789 10790 10791 10792 10793 10794

1239 Release 4 1240 1241


-- identification and numbering errors UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, -- subscription errors RoamingNotAllowed, IllegalSubscriber, IllegalEquipment, BearerServiceNotProvisioned, TeleserviceNotProvisioned, -- handover errors NoHandoverNumberAvailable, SubsequentHandoverFailure, TargetCellOutsideGroupCallArea, -- 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, -- any time information handling errors ATSI-NotAllowed, ATM-NotAllowed, InformationNotAvailable, -- 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, -- Mobility Management errors MM-EventNotSupported ; IMPORTS ERROR

311

3GPP TS 29.002 V4.17.0 (2006-06)

1242

10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812 10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868 10869 10870 10871

1243 Release 4 1244 1245

312

3GPP TS 29.002 V4.17.0 (2006-06)

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) version7 (7)} SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, RoamingNotAllowedParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam, TracingBufferFullParam, NoRoamingNbParam, OR-NotAllowedParam, AbsentSubscriberParam, BusySubscriberParam, 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, MM-EventNotSupported-Param, ATSI-NotAllowedParam, ATM-NotAllowedParam, IllegalSS-OperationParam, SS-NotAvailableParam, SS-SubscriptionViolationParam, InformationNotAvailableParam, TargetCellOutsideGCA-Param

FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version7 (7)} ; -- generic errors SystemFailure ::= ERROR PARAMETER systemFailureParam -- optional

SystemFailureParam

DataMissing ::= ERROR PARAMETER dataMissingParam DataMissingParam -- optional -- dataMissingParam must not be used in version <3

1246

10872 10873 10874 10875 10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889 10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948

1247 Release 4 1248 1249

313

3GPP TS 29.002 V4.17.0 (2006-06)

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 UnidentifiedSubscriber ::= ERROR PARAMETER unidentifiedSubParam UnidentifiedSubParam -- optional -- unidentifiedSubParam must not be used in version <3 UnknownEquipment ::= ERROR -- subscription errors RoamingNotAllowed ::= ERROR PARAMETER roamingNotAllowedParam

IncompatibleTerminalParam

ResourceLimitationParam

NumberChangedParam

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

1250

10949 10950 10951 10952 10953 10954 10955 10956 10957 10958 10959 10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021 11022 11023 11024

1251 Release 4 1252 1253

314

3GPP TS 29.002 V4.17.0 (2006-06)

-- handover errors NoHandoverNumberAvailable ::= ERROR SubsequentHandoverFailure ::= ERROR TargetCellOutsideGroupCallArea ::= ERROR PARAMETER targetCellOutsideGCA-Param TargetCellOutsideGCA-Param -- optional -- operation and maintenance errors TracingBufferFull ::= ERROR PARAMETER tracingBufferFullParam -- optional -- call handling errors NoRoamingNumberAvailable ::= ERROR PARAMETER noRoamingNbParam -- optional

TracingBufferFullParam

NoRoamingNbParam

AbsentSubscriber ::= ERROR PARAMETER absentSubscriberParam AbsentSubscriberParam -- optional -- absentSubscriberParam must not be used in version <3 BusySubscriber ::= ERROR PARAMETER busySubscriberParam -- optional 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

BusySubscriberParam

NoSubscriberReplyParam

CallBarredParam

ForwardingViolationParam

ForwardingFailedParam

CUG-RejectParam

OR-NotAllowedParam

ATI-NotAllowedParam

1254

11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040 11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056 11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072 11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088 11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101

1255 Release 4 1256 1257

315

3GPP TS 29.002 V4.17.0 (2006-06)

-- any time information handling errors ATSI-NotAllowed ::= ERROR PARAMETER atsi-NotAllowedParam -- optional ATM-NotAllowed ::= ERROR PARAMETER atm-NotAllowedParam -- optional InformationNotAvailable ::= ERROR PARAMETER informationNotAvailableParam -- optional -- supplementary service errors

ATSI-NotAllowedParam

ATM-NotAllowedParam

InformationNotAvailableParam

IllegalSS-Operation ::= ERROR PARAMETER illegalSS-OperationParam IllegalSS-OperationParam -- optional -- illegalSS-OperationParam must not be used in version <3 SS-ErrorStatus ::= ERROR PARAMETER ss-Status -- optional

SS-Status

SS-NotAvailable ::= ERROR PARAMETER ss-NotAvailableParam SS-NotAvailableParam -- optional -- ss-NotAvailableParam must not be used in version <3 SS-SubscriptionViolation ::= ERROR PARAMETER ss-SubscriptionViolationParam SS-SubscriptionViolationParam -- optional -- ss-NotAvailableParam must not be used in version <3 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 LongTermDenial ::= ERROR PARAMETER longTermDenialParam -- optional -- short message service errors SubscriberBusyForMT-SMS ::= ERROR PARAMETER subBusyForMT-SMS-Param -- optional

SS-IncompatibilityCause

PW-RegistrationFailureCause

ShortTermDenialParam

LongTermDenialParam

SubBusyForMT-SMS-Param

1258

11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120 11121 11122 11123 11124 11125 11126 11127 11128 11129 11130 11131 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11149 11150 11151 11152

1259 Release 4 1260 1261

316

3GPP TS 29.002 V4.17.0 (2006-06)

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

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

UnknownOrUnreachableLCSClient-Param

MM-EventNotSupported ::= ERROR

PARAMETER mm-EventNotSupported-Param -- optional

MM-EventNotSupported-Param

END

11153
11154 11155 11156 11157 11158 11159 11160 11161 11162 11163 11164 11165 11166 11167 11168 11169 11170 11171 11172 11173 11174 11175 11176

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) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS PrepareGroupCall, SendGroupCallEndSignal, ForwardGroupCallSignalling, ProcessGroupCallSignalling ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)}

1262

11177 11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224

1263 Release 4 1264 1265

317

3GPP TS 29.002 V4.17.0 (2006-06)

SystemFailure, UnexpectedDataValue, NoGroupCallNumberAvailable FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} 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) version7 (7)}

; PrepareGroupCall ::= OPERATION ARGUMENT prepareGroupCallArg RESULT prepareGroupCallRes ERRORS { SystemFailure, NoGroupCallNumberAvailable, UnexpectedDataValue} SendGroupCallEndSignal ::= OPERATION ARGUMENT sendGroupCallEndSignalArg RESULT sendGroupCallEndSignalRes --Timer m PrepareGroupCallArg PrepareGroupCallRes

--Timer l SendGroupCallEndSignalArg SendGroupCallEndSignalRes --Timer s

ProcessGroupCallSignalling ::= OPERATION ARGUMENT processGroupCallSignallingArg ProcessGroupCallSignallingArg ForwardGroupCallSignalling ::= OPERATION ARGUMENT forwardGroupCallSignallingArg ForwardGroupCallSignallingArg END

--Timer s

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) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS ProvideSubscriberLocation, SendRoutingInfoForLCS, SubscriberLocationReport ;

1266

1267 Release 4 1268 1269


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

318

3GPP TS 29.002 V4.17.0 (2006-06)

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) version7 (7)} 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) version7 (7)} ; SendRoutingInfoForLCS ::= OPERATION ARGUMENT routingInfoForLCS-Arg RoutingInfoForLCS-Arg RESULT routingInfoForLCS-Res RoutingInfoForLCS-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, AbsentSubscriber, UnauthorizedRequestingNetwork } --Timer m

ProvideSubscriberLocation ::= OPERATION


ARGUMENT provideSubscriberLocation-Arg RESULT provideSubscriberLocation-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, AbsentSubscriber, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure } ProvideSubscriberLocation-Arg ProvideSubscriberLocation-Res

--Timer ml

1270

1271 Release 4 1272 1273


84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100

319

3GPP TS 29.002 V4.17.0 (2006-06)


--Timer m

SubscriberLocationReport ::= OPERATION ARGUMENT subscriberLocationReport-Arg RESULT subscriberLocationReport-Res ERRORS { SystemFailure, DataMissing, ResourceLimitation, UnexpectedDataValue, UnknownSubscriber, UnauthorizedRequestingNetwork, UnknownOrUnreachableLCSClient} END

SubscriberLocationReport-Arg SubscriberLocationReport-Res

17.6.9 void
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

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) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS -- location registration types UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationArg, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes, IST-SupportIndicator, SupportedLCS-CapabilitySets, -- gprs location registration types GSN-Address, -- handover types ForwardAccessSignalling-Arg, PrepareHO-Arg, PrepareHO-Res, PrepareSubsequentHO-Arg, PrepareSubsequentHO-Res, ProcessAccessSignalling-Arg, SendEndSignal-Arg, SendEndSignal-Res, -- authentication management types SendAuthenticationInfoArg, SendAuthenticationInfoRes, AuthenticationFailureReportArg, AuthenticationFailureReportRes,

1274

1275 Release 4 1276 1277


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 217 218 219 220 221 222 223 224 225 226 227 228 229 230

320

3GPP TS 29.002 V4.17.0 (2006-06)

-- security management types EquipmentStatus, Kc, -- subscriber management types InsertSubscriberDataArg, InsertSubscriberDataRes, LSAIdentity, DeleteSubscriberDataArg, DeleteSubscriberDataRes, Ext-QoS-Subscribed, SubscriberData, ODB-Data, SubscriberStatus, ZoneCodeList, maxNumOfZoneCodes, O-CSI, D-CSI, O-BcsmCamelTDPCriteriaList, T-BCSM-CAMEL-TDP-CriteriaList, SS-CSI, ServiceKey, DefaultCallHandling, CamelCapabilityHandling, BasicServiceCriteria, SupportedCamelPhases, maxNumOfCamelTDPData, CUG-Index, CUG-Info, CUG-Interlock, InterCUG-Restrictions, IntraCUG-Options, NotificationToMSUser, QoS-Subscribed, IST-AlertTimerValue, T-CSI, T-BcsmTriggerDetectionPoint, APN, -- fault recovery types ResetArg, RestoreDataArg, RestoreDataRes,

-- provide subscriber info types GeographicalInformation, -- subscriber information enquiry types ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, SubscriberInfo, LocationInformation, SubscriberState, -- any time information enquiry types AnyTimeInterrogationArg, AnyTimeInterrogationRes, -- any time information handling types AnyTimeSubscriptionInterrogationArg, AnyTimeSubscriptionInterrogationRes, AnyTimeModificationArg, AnyTimeModificationRes, -- subscriber data modification notification types NoteSubscriberDataModifiedArg, NoteSubscriberDataModifiedRes, -- gprs location information retrieval types SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, -- failure reporting types FailureReportArg, FailureReportRes, -- gprs notification types NoteMsPresentForGprsArg,

1278

1279 Release 4 1280 1281


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 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309

321

3GPP TS 29.002 V4.17.0 (2006-06)

NoteMsPresentForGprsRes, -- Mobility Management types NoteMM-EventArg, NoteMM-EventRes

; IMPORTS maxNumOfSS, SS-SubscriptionOption, SS-List, SS-ForBS-Code, Password FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)}

FROM MAP-SS-Code {

SS-Code

ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)}

FROM MAP-BS-Code {

Ext-BearerServiceCode ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version7 (7)}

FROM MAP-TS-Code {

Ext-TeleserviceCode ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version7 (7)}

AddressString, ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString, AccessNetworkSignalInfo, IMSI, TMSI, HLR-List, LMSI, Identity, GlobalCellId, CellGlobalIdOrServiceAreaIdOrLAI, Ext-BasicServiceCode, NAEA-PreferredCI, EMLPP-Info, MC-SS-Info, SubscriberIdentity, AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, Ext-SS-Status, ASCI-CallReference, TBCD-STRING

FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version7 (7)} ;

1282

1283 Release 4 1284 1285


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 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384

322

3GPP TS 29.002 V4.17.0 (2006-06)

-- location registration types UpdateLocationArg ::= SEQUENCE { imsi msc-Number vlr-Number lmsi extensionContainer ... , vlr-Capability informPreviousNetworkEntity IMSI, [1] ISDN-AddressString, ISDN-AddressString, [10] LMSI OPTIONAL, Extens