Вы находитесь на странице: 1из 1277

1

3GPP TS 29.002 V6.11.0 (2005-09)


Technical Specification

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

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.

3GPP

2 3 4

3 Release 6 4 5

3GPP TS 29.002 V6.11.0 (2005-09)

Keywords
GSM, UMTS, network, MAP, SS7

3GPP Postal address 3GPP support office address


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

Internet
http://www.3gpp.org

Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2005, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.

3GPP

7 Release 6 8 9

3GPP TS 29.002 V6.11.0 (2005-09)

Contents

7 Contents....................................................................................................................................................3 8 Foreword.................................................................................................................................................26 9 1 Scope....................................................................................................................................................27 10 2 References............................................................................................................................................27 11 3 Abbreviations.......................................................................................................................................33 12 4 Void.....................................................................................................................................................33 13 5 Overload and compatibility overview..................................................................................................33
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...................................................................................................................................................33 5.1.1 Overload control for MSC (outside MAP)........................................................................................................33 5.1.2 Overload control for MAP entities....................................................................................................................33 5.1.3 Congestion control for Signalling System No. 7..............................................................................................37 5.2 Compatibility........................................................................................................................................................37 5.2.1 General 37 5.2.2 Strategy for selecting the Application Context (AC) version...........................................................................37 5.2.2.1 Proposed method............................................................................................................................................37 5.2.2.2 Managing the version look-up table...............................................................................................................38 5.2.2.3 Optimising the method...................................................................................................................................39 6.1 Use of SCCP........................................................................................................................................................39 6.1.1 SCCP Class.......................................................................................................................................................39 6.1.2 Sub-System Number (SSN)..............................................................................................................................39 6.1.3 SCCP addressing...............................................................................................................................................40 6.1.3.1 Introduction....................................................................................................................................................40 6.1.3.2 The Mobile-services Switching Centre (MSC)..............................................................................................42 6.1.3.2.1 MSC interaction during handover or relocation..........................................................................................42 6.1.3.2.2 MSC for short message routing...................................................................................................................42 6.1.3.2.3 MSC for location request routing................................................................................................................42 6.1.3.2.4 MSC for LMU Control................................................................................................................................42 6.1.3.3 The Home Location Register (HLR)..............................................................................................................42 6.1.3.3.1 During call set-up........................................................................................................................................42 6.1.3.3.2 Before location updating completion..........................................................................................................43 6.1.3.3.3 After location updating completion............................................................................................................43 6.1.3.3.4 VLR restoration...........................................................................................................................................44 6.1.3.3.5 During Network-Requested PDP Context Activation.................................................................................44 6.1.3.3.6 Before GPRS location updating completion...............................................................................................44 6.1.3.3.7 After GPRS location updating completion.................................................................................................45 6.1.3.3.8 Query for a Location Request.....................................................................................................................45 6.1.3.4 The Visitor Location Register (VLR)............................................................................................................45 6.1.3.4.1 Inter-VLR information retrieval..................................................................................................................45 6.1.3.4.2 HLR request................................................................................................................................................45 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service......................................................................45 6.1.3.6 The Equipment Identity Register (EIR).........................................................................................................45 6.1.3.7 Void 46 6.1.3.8 The Serving GPRS Support Node (SGSN)....................................................................................................46 6.1.3.9 The Gateway GPRS Support Node (GGSN).................................................................................................46 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service.............................................................................46 6.1.3.10A Void 46 6.1.3.10A.1 Void 46 6.1.3.10A.2 Void 46 6.1.3.10B The Gateway Mobile Location Centre (GMLC).......................................................................................46 6.1.3.11 Summary table.............................................................................................................................................46 6.2 Use of TC.............................................................................................................................................................48

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

10

3GPP

59 7 General on MAP services.....................................................................................................................48


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 6 12 13

3GPP TS 29.002 V6.11.0 (2005-09)

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

14

3GPP

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 6 16 17

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.2.31 GMSC Address............................................................................................................................................67 7.6.2.32 VMSC Address............................................................................................................................................67 7.6.2.33 Group Id.......................................................................................................................................................67 7.6.2.34 North American Equal Access preferred Carrier Id.....................................................................................67 7.6.2.35 Void 67 7.6.2.36 Void 67 7.6.2.37 Serving cell Id..............................................................................................................................................67 7.6.2.38 SGSN number..............................................................................................................................................68 7.6.2.39 SGSN address...............................................................................................................................................68 7.6.2.40 GGSN address..............................................................................................................................................68 7.6.2.41 GGSN number..............................................................................................................................................68 7.6.2.42 APN 68 7.6.2.43 Network Node number.................................................................................................................................68 7.6.2.44 PDP-Type.....................................................................................................................................................68 7.6.2.45 PDP-Address................................................................................................................................................68 7.6.2.46 Additional number.......................................................................................................................................68 7.6.2.47 P-TMSI 68 7.6.2.48 B-subscriber number....................................................................................................................................68 7.6.2.49 B-subscriber subaddress...............................................................................................................................68 7.6.2.50 LMU Number ..............................................................................................................................................68 7.6.2.51 MLC Number ..............................................................................................................................................68 7.6.2.52 Multicall Bearer Information.......................................................................................................................69 7.6.2.53 Multiple Bearer Requested...........................................................................................................................69 7.6.2.54 Multiple Bearer Not Supported....................................................................................................................69 7.6.2.55 PDP-Charging Characteristics.....................................................................................................................69 7.6.2.56 Selected RAB ID..........................................................................................................................................69 7.6.2.57 RAB ID 69 7.6.2.58 gsmSCF Address..........................................................................................................................................69 7.6.2.59 V-GMLC Address........................................................................................................................................69 7.6.2.60 Void 69 7.6.2.61 H-GMLC Address........................................................................................................................................69 7.6.2.62 PPR Address.................................................................................................................................................69 7.6.2.63 Routeing Number.........................................................................................................................................69 7.6.2.64 Additional V-GMLC Address......................................................................................................................69 7.6.3 Subscriber management parameters..................................................................................................................69 7.6.3.1 Category 70 7.6.3.2 Equipment status............................................................................................................................................70 7.6.3.2a BMUEF 70 7.6.3.3 Extensible Bearer service...............................................................................................................................70 7.6.3.4 Extensible Teleservice...................................................................................................................................70 7.6.3.5 Extensible Basic Service Group.....................................................................................................................70 7.6.3.6 GSM bearer capability...................................................................................................................................70 7.6.3.7 Subscriber Status............................................................................................................................................70 7.6.3.8 CUG Outgoing Access indicator....................................................................................................................70 7.6.3.9 Operator Determined Barring General Data..................................................................................................70 7.6.3.10 ODB HPLMN Specific Data........................................................................................................................73 7.6.3.11 Regional Subscription Data..........................................................................................................................73 7.6.3.12 Regional Subscription Response..................................................................................................................73 7.6.3.13 Roaming Restriction Due To Unsupported Feature.....................................................................................73 7.6.3.14 Extensible SS-Info.......................................................................................................................................73 7.6.3.15 Extensible forwarding information..............................................................................................................73 7.6.3.16 Extensible forwarding feature......................................................................................................................73 7.6.3.17 Extensible SS-Status....................................................................................................................................74 7.6.3.18 Extensible Forwarding Options....................................................................................................................74 7.6.3.19 Extensible No reply condition timer............................................................................................................74 7.6.3.20 Extensible Call barring information.............................................................................................................74 7.6.3.21 Extensible Call barring feature.....................................................................................................................74 7.6.3.22 CUG info......................................................................................................................................................75 7.6.3.23 CUG subscription.........................................................................................................................................75 7.6.3.24 CUG interlock..............................................................................................................................................75 7.6.3.25 CUG index...................................................................................................................................................75

18

3GPP

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 6 20 21

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.3.26 CUG feature.................................................................................................................................................75 7.6.3.27 Inter CUG options........................................................................................................................................75 7.6.3.28 Intra CUG restrictions..................................................................................................................................75 7.6.3.29 Extensible SS-Data.......................................................................................................................................76 7.6.3.30 Subscriber State............................................................................................................................................76 7.6.3.31 Requested Info.............................................................................................................................................76 7.6.3.31A Requested Domain....................................................................................................................................76 7.6.3.32 Suppression of Announcement....................................................................................................................76 7.6.3.33 Suppress T-CSI............................................................................................................................................76 7.6.3.34 GMSC CAMEL Subscription Info...............................................................................................................76 7.6.3.35 VLR CAMEL Subscription Info..................................................................................................................76 7.6.3.36 Supported CAMEL Phases in the VLR.......................................................................................................76 7.6.3.36A Supported CAMEL Phases in the SGSN..................................................................................................77 7.6.3.36B Offered CAMEL4 CSIs in the VLR..........................................................................................................77 7.6.3.36C Offered CAMEL4 CSIs in the SGSN........................................................................................................77 7.6.3.36D Offered CAMEL4 CSIs.............................................................................................................................77 7.6.3.36E Offered CAMEL4 CSIs in interrogating node...........................................................................................77 7.6.3.36F Offered CAMEL4 CSIs in VMSC.............................................................................................................77 7.6.3.36G Offered CAMEL4 Functionalities............................................................................................................77 7.6.3.36H Supported CAMEL Phases........................................................................................................................77 7.6.3.36I Supported CAMEL Phases in interrogating node.......................................................................................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.....................................................................................................77 7.6.3.40 Voice Broadcast Service (VBS) Data..........................................................................................................77 7.6.3.41 ISDN bearer capability.................................................................................................................................77 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........................................................................................................................................78 7.6.3.53 All GPRS Data.............................................................................................................................................78 7.6.3.54 Complete Data List Included.......................................................................................................................78 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.62A Additional 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.65D Service Type List .....................................................................................................................................80 7.6.3.66 IST Alert Timer............................................................................................................................................80 7.6.3.67 Call Termination Indicator...........................................................................................................................81 7.6.3.68 IST Information Withdraw...........................................................................................................................81 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

22

3GPP

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 6 24 25

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.3.72 Age Indicator................................................................................................................................................81 7.6.3.73 GPRS enhancements support indicator........................................................................................................81 7.6.3.74 Extension QoS-Subscribed...........................................................................................................................81 7.6.3.75 SGSN CAMEL Subscription Info................................................................................................................81 7.6.3.75A Extension-2 QoS-Subscribed....................................................................................................................81 7.6.3.76 MO-SMS-CSI..............................................................................................................................................81 7.6.3.76a MT-SMS-CSI.............................................................................................................................................82 7.6.3.77 GPRS-CSI....................................................................................................................................................82 7.6.3.78 CAMEL subscription info............................................................................................................................82 7.6.3.83 Call Barring Data.........................................................................................................................................82 7.6.3.84 Call Forwarding Data...................................................................................................................................82 7.6.3.85 ODB Data.....................................................................................................................................................83 7.6.3.86 Requested Subscription Info........................................................................................................................83 7.6.3.87 CS Allocation/Retention priority.................................................................................................................83 7.6.3.88 ODB Info......................................................................................................................................................83 7.6.3.89 Suppress VT-CSI.........................................................................................................................................83 7.6.3.90 Suppress Incoming Call Barring..................................................................................................................83 7.6.3.91 gsmSCF Initiated Call..................................................................................................................................83 7.6.3.92 Call barring support indicator......................................................................................................................83 7.6.3.93 MNP Info Result..........................................................................................................................................83 7.6.3.94 Allowed Services.........................................................................................................................................83 7.6.3.95 Unavailability Cause....................................................................................................................................83 7.6.3.96 MNP Requested Info....................................................................................................................................84 7.6.3.97 Access Restriction Data..............................................................................................................................84 7.6.4 Supplementary services parameters..................................................................................................................84 7.6.4.1 SS-Code 84 7.6.4.1A SS-Code 2....................................................................................................................................................84 7.6.4.2 SS-Status 85 7.6.4.3 SS-Data 85 7.6.4.4 Override Category..........................................................................................................................................85 7.6.4.5 CLI Restriction Option...................................................................................................................................85 7.6.4.6 Forwarding Options.......................................................................................................................................85 7.6.4.7 No reply condition timer................................................................................................................................85 7.6.4.8 - 7.6.4.14 Void...............................................................................................................................................85 7.6.4.15 Forwarding information...............................................................................................................................85 7.6.4.16 Forwarding feature.......................................................................................................................................86 7.6.4.17 Void 86 7.6.4.18 Call barring information...............................................................................................................................86 7.6.4.19 Call barring feature......................................................................................................................................86 7.6.4.20 New password..............................................................................................................................................86 7.6.4.21 Current password.........................................................................................................................................86 7.6.4.22 Guidance information...................................................................................................................................87 7.6.4.23 Void 87 7.6.4.24 SS-Info 87 7.6.4.25 - 7.6.4.35 Void.............................................................................................................................................87 7.6.4.36 USSD Data Coding Scheme.........................................................................................................................87 7.6.4.37 USSD String.................................................................................................................................................87 7.6.4.38 Bearer service...............................................................................................................................................87 7,6,4.38A Bearer Service 2........................................................................................................................................87 7.6.4.39 Teleservice...................................................................................................................................................87 7.6.4.39A Teleservice 2.............................................................................................................................................88 7.6.4.40 Basic Service Group.....................................................................................................................................88 7.6.4.41 eMLPP information......................................................................................................................................88 7.6.4.42 SS-event.......................................................................................................................................................88 7.6.4.43 SS-event data................................................................................................................................................88 7.6.4.44 LCS Privacy Exceptions .............................................................................................................................88 7.6.4.45 Mobile Originating Location Request (MO-LR).........................................................................................88 7.6.4.46 NbrUser 89 7.6.4.47 MC Subscription Data..................................................................................................................................89 7.6.4.48 MC Information...........................................................................................................................................89 7.6.4.49 CCBS Request State.....................................................................................................................................89

26

3GPP

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 6 28 29

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.4.50 Basic Service Group 2..................................................................................................................................90 7.6.5 Call parameters..................................................................................................................................................90 7.6.5.1 Call reference number....................................................................................................................................90 7.6.5.2 Interrogation type...........................................................................................................................................90 7.6.5.3 OR interrogation.............................................................................................................................................90 7.6.5.4 OR capability.................................................................................................................................................90 7.6.5.5 Forwarding reason..........................................................................................................................................90 7.6.5.6 Forwarding interrogation required.................................................................................................................90 7.6.5.7 O-CSI 90 7.6.5.7A D-CSI 90 7.6.5.7B T-CSI 90 7.6.5.7C VT-CSI 90 7.6.5.7D O-IM-CSI....................................................................................................................................................91 7.6.5.7E D-IM-CSI.....................................................................................................................................................91 7.6.5.7F VT-IM-CSI..................................................................................................................................................91 7.6.5.8 Void 91 7.6.5.9 Void 91 7.6.5.10 Void 91 7.6.5.11 CCBS Feature...............................................................................................................................................91 7.6.5.12 UU Data91 7.6.5.14 Number Portability Status............................................................................................................................91 7.6.5.15 Pre-paging supported...................................................................................................................................91 7.6.6 Radio parameters...............................................................................................................................................91 7.6.6.1 - 7.6.6.3 Void................................................................................................................................................92 7.6.6.4 GERAN Classmark ......................................................................................................................................92 7.6.6.5 BSSMAP Service Handover.........................................................................................................................92 7.6.6.5A BSSMAP Service Handover List...............................................................................................................92 7.6.6.6 RANAP Service Handover...........................................................................................................................92 7.6.6.7 HO-Number Not Required.............................................................................................................................92 7.6.6.8 Integrity Protection Information....................................................................................................................92 7.6.6.9 Encryption Information..................................................................................................................................92 7.6.6.10 Radio Resource Information........................................................................................................................92 7.6.6.10A Radio Resource List..................................................................................................................................92 7.6.6.10B Chosen Radio Resource Information.........................................................................................................92 7.6.6.11 Key Status....................................................................................................................................................92 7.6.6.12 Selected UMTS Algorithms.........................................................................................................................92 7.6.6.13 Allowed GSM Algorithms...........................................................................................................................92 7.6.6.14 Allowed UMTS Algorithms.........................................................................................................................93 7.6.6.15 Selected GSM Algorithm.............................................................................................................................93 7.6.6.16 Iu-Currently Used Codec.............................................................................................................................93 7.6.6.17 Iu-Supported Codecs List.............................................................................................................................93 7.6.6.17A Iu-Available Codecs List...........................................................................................................................93 7.6.6.18 Iu-Selected Codec........................................................................................................................................93 7.6.6.19 RAB Configuration Indicator.......................................................................................................................93 7.6.6.20 UESBI-Iu......................................................................................................................................................93 7.6.6.21 Alternative Channel Type............................................................................................................................93 7.6.7 Authentication parameters................................................................................................................................93 7.6.7.1 Authentication set list.....................................................................................................................................93 7.6.7.2 Rand 94 7.6.7.3 Sres 94 7.6.7.4 Kc 94 7.6.7.5 Xres 94 7.6.7.5A Ck 94 7.6.7.5B Ik 94 7.6.7.5C Autn 94 7.6.7.6 Cksn 94 7.6.7.6A Ksi 94 7.6.7.6B Auts 94 7.6.7.7 Ciphering mode..............................................................................................................................................94 7.6.7.8 Current Security Context................................................................................................................................94 7.6.7.9 Failure cause...................................................................................................................................................94

30

3GPP

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

31 Release 6 32 33

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.7.10 Re-attempt....................................................................................................................................................95 7.6.7.11 Access Type.................................................................................................................................................95 7.6.8 Short message parameters.................................................................................................................................95 7.6.8.1 SM-RP-DA.....................................................................................................................................................95 7.6.8.2 SM-RP-OA.....................................................................................................................................................95 7.6.8.3 MWD status...................................................................................................................................................95 7.6.8.4 SM-RP-UI......................................................................................................................................................95 7.6.8.5 SM-RP-PRI....................................................................................................................................................95 7.6.8.6 SM Delivery Outcome...................................................................................................................................95 7.6.8.7 More Messages To Send................................................................................................................................96 7.6.8.8 Alert Reason...................................................................................................................................................96 7.6.8.9 Absent Subscriber Diagnostic SM.................................................................................................................96 7.6.8.10 Alert Reason Indicator.................................................................................................................................96 7.6.8.11 Additional SM Delivery Outcome...............................................................................................................96 7.6.8.12 Additional Absent Subscriber Diagnostic SM.............................................................................................96 7.6.8.13 Delivery Outcome Indicator.........................................................................................................................96 7.6.8.14 GPRS Node Indicator...................................................................................................................................96 7.6.8.15 GPRS Support Indicator...............................................................................................................................96 7.6.8.16 SM-RP-MTI.................................................................................................................................................96 7.6.8.17 SM-RP-SMEA.............................................................................................................................................96 7.6.9 Access and signalling system related parameters.............................................................................................97 7.6.9.1 AN-apdu 97 7.6.9.2 CM service type.............................................................................................................................................97 7.6.9.3 Access connection status................................................................................................................................97 7.6.9.4 External Signal Information...........................................................................................................................97 7.6.9.5 Access signalling information........................................................................................................................97 7.6.9.6 Location update type......................................................................................................................................97 7.6.9.7 Protocol ID.....................................................................................................................................................97 7.6.9.8 Network signal information...........................................................................................................................98 7.6.9.8A Network signal information 2.....................................................................................................................98 7.6.9.9 Call Info 98 7.6.9.10 Additional signal info...................................................................................................................................99 7.6.10 System operations parameters.........................................................................................................................99 7.6.10.1 Network resources........................................................................................................................................99 7.6.10.2 Trace reference.............................................................................................................................................99 7.6.10.2A Trace reference 2.......................................................................................................................................99 7.6.10.3 Trace type.....................................................................................................................................................99 7.6.10.4 Additional network resources......................................................................................................................99 7.6.10.5 Trace depth list...........................................................................................................................................100 7.6.10.6 Trace NE type list.......................................................................................................................................100 7.6.10.7 Trace interface list......................................................................................................................................100 7.6.10.X Trace event list..........................................................................................................................................100 7.6.10.X Trace support indicator..............................................................................................................................100 7.6.11 Location Service Parameters ........................................................................................................................100 7.6.11.1 Age of Location Estimate...........................................................................................................................100 7.6.11.2 Deferred MT-LR Response Indicator .......................................................................................................100 7.6.11.3 Deferred MT-LR Data................................................................................................................................100 7.6.11.4 LCS Client ID............................................................................................................................................100 7.6.11.5 LCS Event..................................................................................................................................................101 7.6.11.7 LCS Priority...............................................................................................................................................101 7.6.11.8 LCS QoS....................................................................................................................................................101 7.6.11.9 CS LCS Not Supported by UE...................................................................................................................101 This parameter is used by the VLR to indicate to the HLR that the UE does not support neither UE Based nor UE Assisted positioning metheds for Circuit Switched Location Services. VLR defines the presence of this parameter on the basis of the Classmark 3 information...................................................101 7.6.11.10 PS LCS Not Supported by UE.................................................................................................................101 7.6.11.11 Location Estimate.....................................................................................................................................101 7.6.11.11A GERAN Positioning Data.....................................................................................................................102 7.6.11.11B UTRAN Positioning Data......................................................................................................................102 7.6.11.12 Location Type..........................................................................................................................................102 7.6.11.13 NA-ESRD................................................................................................................................................102

34

3GPP

425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 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 6 36 37

10

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.11.14 NA-ESRK................................................................................................................................................102 7.6.11.15 LCS Service Type Id...............................................................................................................................102 7.6.11.16 Privacy Override......................................................................................................................................102 7.6.11.17 Supported LCS Capability Sets................................................................................................................102 7.6.11.18 LCS Codeword........................................................................................................................................102 7.6.11.19 NA-ESRK Request...................................................................................................................................102 7.6.11.20 Supported GAD Shapes...........................................................................................................................103 7.6.11.21 Additional Location Estimate..................................................................................................................103 7.6.11.22 Cell Id Or SAI..........................................................................................................................................103 7.6.11.23 LCS-Reference Number...........................................................................................................................103 7.6.11.24 LCS Privacy Check..................................................................................................................................103 7.6.11.25 Additional LCS Capability Sets...............................................................................................................103 7.6.11.26 Area Event Info........................................................................................................................................103 7.6.11.27 Accuracy Fulfilment Indicator.................................................................................................................103 7.6.12 Secure Transport Parameters.........................................................................................................................104 7.6.12.1 Security Header..........................................................................................................................................104 7.7 Representation of a list of a basic parameter in service-primitives...................................................................104 8.1 Location management services..........................................................................................................................105 8.1.1 Void 105 8.1.1.1 Void 105 8.1.1.2 Void 105 8.1.1.3 Void 105 8.1.2 MAP_UPDATE_LOCATION service............................................................................................................105 8.1.2.1 Definition.....................................................................................................................................................105 8.1.2.2 Service primitives.........................................................................................................................................105 8.1.2.3 Parameter definitions and use......................................................................................................................105 8.1.3 MAP_CANCEL_LOCATION service...........................................................................................................107 8.1.3.1 Definition.....................................................................................................................................................107 8.1.3.2 Service primitives.........................................................................................................................................108 8.1.3.3 Parameter definitions and use......................................................................................................................108 8.1.4 MAP_SEND_IDENTIFICATION service.....................................................................................................108 8.1.4.1 Definition.....................................................................................................................................................108 8.1.4.2 Service primitives.........................................................................................................................................109 8.1.4.3 Parameter definitions and use......................................................................................................................109 8.1.5 Void 110 8.1.5.1 Void 110 8.1.5.2 Void 110 8.1.5.3 Void 110 8.1.6 MAP_PURGE_MS service.............................................................................................................................110 8.1.6.1 Definition.....................................................................................................................................................110 8.1.6.2 Service primitives.........................................................................................................................................110 8.1.6.3 Parameter definitions and use......................................................................................................................110 8.1.7 MAP_UPDATE_GPRS_LOCATION service................................................................................................111 8.1.7.1 Definition.....................................................................................................................................................111 8.1.7.2 Service primitives.........................................................................................................................................111 8.1.7.3 Parameter definitions and use......................................................................................................................112 8.1.8 MAP-NOTE-MM-EVENT.............................................................................................................................114 8.1.8.1 Definition.....................................................................................................................................................114 8.1.8.2 Service primitives.........................................................................................................................................114 8.1.8.3 Parameter use...............................................................................................................................................114 8.2 Paging and search...............................................................................................................................................115 8.2.1 MAP_PAGE service.......................................................................................................................................115 8.2.1.1 Definition.....................................................................................................................................................115 8.2.1.2 Service primitives.........................................................................................................................................115 8.2.1.3 Parameter definitions and use......................................................................................................................116 8.2.2 MAP_SEARCH_FOR_MS service................................................................................................................116 8.2.2.1 Definition.....................................................................................................................................................116 8.2.2.2 Service primitives.........................................................................................................................................116 8.2.2.3 Parameter definitions and use......................................................................................................................117

442 8 Mobility services................................................................................................................................104

38

3GPP

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 533 534 535 536 537 538 539 540 541 542 543 544 545

39 Release 6 40 41

11

3GPP TS 29.002 V6.11.0 (2005-09)

8.3 Access management services.............................................................................................................................117 8.3.1 MAP_PROCESS_ACCESS_REQUEST service...........................................................................................117 8.3.1.1 Definition.....................................................................................................................................................117 8.3.1.2 Service primitives.........................................................................................................................................117 8.3.1.3 Parameter definitions and use......................................................................................................................118 8.4 Handover services..............................................................................................................................................119 8.4.1 MAP_PREPARE_HANDOVER service........................................................................................................119 8.4.1.1 Definition.....................................................................................................................................................119 8.4.1.2 Service primitives.........................................................................................................................................119 8.4.1.3 Parameter use...............................................................................................................................................120 8.4.2 MAP_SEND_END_SIGNAL service............................................................................................................123 8.4.2.1 Definition.....................................................................................................................................................123 8.4.2.2 Service primitives.........................................................................................................................................123 8.4.2.3 Parameter use...............................................................................................................................................124 8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service.....................................................................................124 8.4.3.1 Definition.....................................................................................................................................................124 8.4.3.2 Service primitives.........................................................................................................................................124 8.4.3.3 Parameter use...............................................................................................................................................124 8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service..................................................................................125 8.4.4.1 Definition.....................................................................................................................................................125 8.4.4.2 Service primitives.........................................................................................................................................125 8.4.4.3 Parameter use...............................................................................................................................................126 8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service............................................................................127 8.4.5.1 Definition.....................................................................................................................................................127 8.4.5.2 Service primitives.........................................................................................................................................128 8.4.5.3 Parameter use...............................................................................................................................................128 8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service.................................................................................129 8.4.6.1 Definition.....................................................................................................................................................129 8.4.6.2 Service primitives.........................................................................................................................................129 8.4.6.3 Parameter use...............................................................................................................................................129 8.4.7 MAP_SEND_HANDOVER_REPORT service..............................................................................................129 8.4.7.1 Definition.....................................................................................................................................................129 8.4.7.2 Service primitives.........................................................................................................................................130 8.4.7.3 Parameter use...............................................................................................................................................130 8.5 Authentication management services.................................................................................................................130 8.5.1 MAP_AUTHENTICATE service...................................................................................................................130 8.5.1.1 Definition.....................................................................................................................................................130 8.5.1.2 Service primitives.........................................................................................................................................130 8.5.1.3 Parameter use...............................................................................................................................................131 8.5.2 MAP_SEND_AUTHENTICATION_INFO service.......................................................................................131 8.5.2.1 Definition.....................................................................................................................................................131 8.5.2.2 Service primitives.........................................................................................................................................131 8.5.2.3 Parameter use...............................................................................................................................................132 8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service..........................................................................133 8.5.3.1 Definition.....................................................................................................................................................133 8.5.3.2 Service primitives.........................................................................................................................................133 8.5.3.3 Parameter use...............................................................................................................................................133 8.6 Security management services...........................................................................................................................134 8.6.1 MAP_SET_CIPHERING_MODE service......................................................................................................134 8.6.1.1 Definitions....................................................................................................................................................134 8.6.1.2 Service primitives.........................................................................................................................................134 8.6.1.3 Parameter use...............................................................................................................................................134 8.7 International mobile equipment identities management services......................................................................135 8.7.1 MAP_CHECK_IMEI service..........................................................................................................................135 8.7.1.1 Definition.....................................................................................................................................................135 8.7.1.2 Service primitives.........................................................................................................................................135 8.7.1.3 Parameter use...............................................................................................................................................135 8.7.2 MAP_OBTAIN_IMEI service........................................................................................................................136 8.7.2.1 Definition.....................................................................................................................................................136 8.7.2.2 Service primitives.........................................................................................................................................136 8.7.2.3 Parameter use...............................................................................................................................................136

42

3GPP

546 547 548 549 550 551 552 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 600 601 602 603 604 605

43 Release 6 44 45

12

3GPP TS 29.002 V6.11.0 (2005-09)

8.8 Subscriber management services.......................................................................................................................137 8.8.1 MAP-INSERT-SUBSCRIBER-DATA service..............................................................................................137 8.8.1.1 Definition.....................................................................................................................................................137 8.8.1.2 Service primitives.........................................................................................................................................137 8.8.1.3 Parameter use...............................................................................................................................................138 8.8.1.4 Basic service information related to supplementary services......................................................................147 8.8.2 MAP-DELETE-SUBSCRIBER-DATA service.............................................................................................148 8.8.2.1 Definition.....................................................................................................................................................148 8.8.2.2 Service primitives.........................................................................................................................................148 8.8.2.3 Parameter use...............................................................................................................................................148 8.9 Identity management services............................................................................................................................151 8.9.1 MAP-PROVIDE-IMSI service.......................................................................................................................151 8.9.1.1 Definition.....................................................................................................................................................151 8.9.1.2 Service primitives.........................................................................................................................................151 8.9.1.3 Parameter use...............................................................................................................................................151 8.9.2 MAP-FORWARD-NEW-TMSI service.........................................................................................................152 8.9.2.1 Definition.....................................................................................................................................................152 8.9.2.2 Service primitives.........................................................................................................................................152 8.9.2.3 Parameter use...............................................................................................................................................152 8.10 Fault recovery services.....................................................................................................................................152 8.10.1 MAP_RESET service....................................................................................................................................152 8.10.1.1 Definition...................................................................................................................................................152 8.10.1.2 Service primitives.......................................................................................................................................152 8.10.1.3 Parameter definition and use......................................................................................................................152 8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service............................................................................153 8.10.2.1 Definition...................................................................................................................................................153 8.10.2.2 Service primitives.......................................................................................................................................153 8.10.2.3 Parameter definition and use......................................................................................................................153 8.10.3 MAP_RESTORE_DATA service.................................................................................................................153 8.10.3.1 Definition...................................................................................................................................................153 8.10.3.2 Service primitives.......................................................................................................................................153 8.10.3.3 Parameter definitions and use....................................................................................................................154 8.11 Subscriber Information services.......................................................................................................................155 8.11.1 MAP-ANY-TIME-INTERROGATION service...........................................................................................155 8.11.1.1 Definition...................................................................................................................................................155 8.11.1.2 Service primitives.......................................................................................................................................155 8.11.1.3 Parameter definition and use......................................................................................................................156 8.11.2 MAP-PROVIDE-SUBSCRIBER-INFO service...........................................................................................156 8.11.2.1 Definition...................................................................................................................................................156 8.11.2.2 Service primitives.......................................................................................................................................157 8.11.2.3 Parameter definition and use......................................................................................................................157 8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service.............................................................157 8.11.3.1 Definition...................................................................................................................................................157 8.11.3.2 Service primitives.......................................................................................................................................157 8.11.3.3 Parameter definition and use......................................................................................................................158 8.11.4 MAP-ANY-TIME-MODIFICATION service..............................................................................................158 8.11.4.1 Definition...................................................................................................................................................158 8.11.4.2 Service primitives.......................................................................................................................................158 8.11.4.3 Parameter definition and use......................................................................................................................159 8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service...........................................................................159 8.11.5.1 Definition...................................................................................................................................................159 8.11.5.2 Service primitives.......................................................................................................................................160 8.11.5.3 Parameter definition and use......................................................................................................................160 9.1 Subscriber tracing services.................................................................................................................................161 9.1.1 MAP-ACTIVATE-TRACE-MODE service...................................................................................................161 9.1.1.1 Definition.....................................................................................................................................................161 9.1.1.2 Service primitives.........................................................................................................................................161 9.1.1.3 Parameter use...............................................................................................................................................161 9.1.2 MAP-DEACTIVATE-TRACE-MODE service..............................................................................................162

599 9 Operation and maintenance services..................................................................................................161

46

3GPP

606 607 608 609 610 611 612 613 614 615 616 617 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 665

47 Release 6 48 49

13

3GPP TS 29.002 V6.11.0 (2005-09)

9.1.2.1 Definition.....................................................................................................................................................162 9.1.2.2 Service primitives.........................................................................................................................................163 9.1.2.3 Parameter use...............................................................................................................................................163 9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service.......................................................................................163 9.1.3.1 Definition.....................................................................................................................................................163 9.1.3.2 Service primitives.........................................................................................................................................163 9.1.3.3 Parameter use...............................................................................................................................................164 9.2 Other operation and maintenance services.........................................................................................................164 9.2.1 MAP-SEND-IMSI service..............................................................................................................................164 9.2.1.1 Definition.....................................................................................................................................................164 9.2.1.2 Service primitives.........................................................................................................................................164 9.2.1.3 Parameter use...............................................................................................................................................164 10.1 MAP_SEND_ROUTING_INFORMATION service......................................................................................165 10.1.1 Definition......................................................................................................................................................165 10.1.2 Service primitives..........................................................................................................................................165 10.1.3 Parameter use................................................................................................................................................166 10.2 MAP_PROVIDE_ROAMING_NUMBER service.........................................................................................171 10.2.1 Definition......................................................................................................................................................171 10.2.2 Service primitives..........................................................................................................................................171 10.2.3 Parameter use................................................................................................................................................171 10.3 MAP_RESUME_CALL_HANDLING service...............................................................................................174 10.3.1 Definition......................................................................................................................................................174 10.3.2 Service primitives..........................................................................................................................................174 10.3.3 Parameter use................................................................................................................................................174 10.4 MAP_PREPARE_GROUP_CALL service.....................................................................................................175 10.4.1 Definition......................................................................................................................................................175 10.4.2 Service primitives..........................................................................................................................................176 10.4.3 Parameter definitions and use.......................................................................................................................176 10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service............................................................................177 10.5.1 Definitions.....................................................................................................................................................177 10.5.2 Service primitives..........................................................................................................................................177 10.5.3 Parameter definitions and use.......................................................................................................................177 10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service.........................................................................178 10.6.1 Definitions.....................................................................................................................................................178 10.6.2 Service primitives..........................................................................................................................................178 10.6.3 Parameter definitions and use.......................................................................................................................178 10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service.................................................................................179 10.7.1 Definitions.....................................................................................................................................................179 10.7.2 Service primitives..........................................................................................................................................179 10.7.3 Parameter definitions and use.......................................................................................................................179 10.8 Void 179 10.9 Void 179 10.10 MAP_SET_REPORTING_STATE service...................................................................................................179 10.10.1 Definition....................................................................................................................................................179 10.10.2 Service primitives........................................................................................................................................179 10.10.3 Parameter use..............................................................................................................................................180 10.11 MAP_STATUS_REPORT service................................................................................................................180 10.11.1 Definition....................................................................................................................................................180 10.11.2 Service primitives........................................................................................................................................180 10.11.3 Parameter use..............................................................................................................................................181 10.12 MAP_REMOTE_USER_FREE service........................................................................................................181 10.12.1 Definition....................................................................................................................................................181 10.12.2 Service primitives........................................................................................................................................181 10.12.3 Parameter use..............................................................................................................................................182 10.13 MAP_IST_ALERT service............................................................................................................................182 10.13.1 Definition....................................................................................................................................................182 10.13.2 Service primitives........................................................................................................................................183 10.13.3 Parameter use..............................................................................................................................................183 10.14 MAP_IST_COMMAND service...................................................................................................................183

618 10 Call handling services......................................................................................................................165

50

3GPP

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

51 Release 6 52 53

14

3GPP TS 29.002 V6.11.0 (2005-09)

10.14.1 Definition....................................................................................................................................................183 10.14.2 Service primitives........................................................................................................................................184 10.14.3 Parameter use..............................................................................................................................................184 10.15 MAP_RELEASE_RESOURCES service......................................................................................................184 10.15.1 Definition....................................................................................................................................................184 10.15.2 Service primitives........................................................................................................................................184 10.15.3 Parameter use..............................................................................................................................................184 11.1 MAP_REGISTER_SS service.........................................................................................................................185 11.1.1 Definition......................................................................................................................................................185 11.1.2 Service primitives..........................................................................................................................................185 11.1.3 Parameter use................................................................................................................................................185 11.2 MAP_ERASE_SS service................................................................................................................................186 11.2.1 Definition......................................................................................................................................................186 11.2.2 Service primitives..........................................................................................................................................186 11.2.3 Parameter use................................................................................................................................................187 11.3 MAP_ACTIVATE_SS service........................................................................................................................187 11.3.1 Definition......................................................................................................................................................187 11.3.2 Service primitives..........................................................................................................................................188 11.3.3 Parameter use................................................................................................................................................188 11.4 MAP_DEACTIVATE_SS service...................................................................................................................189 11.4.1 Definitions.....................................................................................................................................................189 11.4.2 Service primitives..........................................................................................................................................189 11.4.3 Parameter use................................................................................................................................................189 11.5 MAP_INTERROGATE_SS service................................................................................................................190 11.5.1 Definitions.....................................................................................................................................................190 11.5.2 Service primitives..........................................................................................................................................190 11.5.3 Parameter use................................................................................................................................................191 11.6 Void 192 11.7 MAP_REGISTER_PASSWORD service........................................................................................................192 11.7.1 Definitions.....................................................................................................................................................192 11.7.2 Service primitives..........................................................................................................................................192 11.7.3 Parameter use................................................................................................................................................193 11.8 MAP_GET_PASSWORD service...................................................................................................................193 11.8.1 Definitions.....................................................................................................................................................193 11.8.2 Service primitives..........................................................................................................................................193 11.8.3 Parameter use................................................................................................................................................194 11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service.....................................................................194 11.9.1 Definitions.....................................................................................................................................................194 11.9.2 Service primitives..........................................................................................................................................194 11.9.3 Parameter use................................................................................................................................................194 11.10 MAP_UNSTRUCTURED_SS_REQUEST service......................................................................................195 11.10.1 Definitions...................................................................................................................................................195 11.10.2 Service primitives........................................................................................................................................195 11.10.3 Parameter use..............................................................................................................................................196 11.11 MAP_UNSTRUCTURED_SS_NOTIFY service..........................................................................................196 11.11.1 Definitions...................................................................................................................................................196 11.11.2 Service primitives........................................................................................................................................197 11.11.3 Parameter use..............................................................................................................................................197 11.12 MAP_SS_INVOCATION_NOTIFY.............................................................................................................198 11.12.1 Definition....................................................................................................................................................198 11.12.2 Service primitives........................................................................................................................................198 11.12.3 Parameter use..............................................................................................................................................198 11.13 MAP_REGISTER_CC_ENTRY service.......................................................................................................198 11.13.1 Definition....................................................................................................................................................198 11.13.2 Service primitives........................................................................................................................................199 11.13.3 Parameter use..............................................................................................................................................199 11.14 MAP_ERASE_CC_ENTRY service.............................................................................................................200 11.14.1 Definition....................................................................................................................................................200 11.14.2 Service primitives........................................................................................................................................200

673 11 Supplementary services related services..........................................................................................185

54

3GPP

726 11.14.3 Parameter use..............................................................................................................................................200

55 Release 6 56 57

15

3GPP TS 29.002 V6.11.0 (2005-09)

727 12 Short message service management services....................................................................................201


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

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

764 13 Network-Requested PDP Context Activation services.....................................................................211

777 13A Location Service Management Services........................................................................................214

58

3GPP

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

59 Release 6 60 61

16

3GPP TS 29.002 V6.11.0 (2005-09)

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

814 14 General.............................................................................................................................................223

819 15 Elements of procedure......................................................................................................................224

833 16 Mapping on to TC services..............................................................................................................270

62

3GPP

844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 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 6 64 65

17

3GPP TS 29.002 V6.11.0 (2005-09)

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

859 17 Abstract syntax of the MAP protocol...............................................................................................275

66

3GPP

904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964

67 Release 6 68 69

18

3GPP TS 29.002 V6.11.0 (2005-09)

17.2.2.34 Void 289 17.2.2.35 Gprs location updating.............................................................................................................................289 17.2.2.36 Gprs Interrogation....................................................................................................................................289 17.2.2.37 Failure reporting.......................................................................................................................................289 17.2.2.38 GPRS notifying........................................................................................................................................289 17.2.2.39 Supplementary Service invocation notification.......................................................................................290 17.2.2.40 Set Reporting State...................................................................................................................................290 17.2.2.41 Status Report............................................................................................................................................290 17.2.2.42 Remote User Free.....................................................................................................................................290 17.2.2.43 Call Completion.......................................................................................................................................290 17.2.2.44 Location service gateway services...........................................................................................................290 17.2.2.45 Location service enquiry..........................................................................................................................291 17.2.2.45A Location service reporting.....................................................................................................................291 17.2.2.46 Void 291 17.2.2.47 Void 291 17.2.2.48 Void 291 17.2.2.49 IST Alerting.............................................................................................................................................291 17.2.2.50 Service Termination.................................................................................................................................291 17.2.2.51 Mobility Management event notification.................................................................................................292 17.2.2.53 Subscriber Data modification notification...............................................................................................292 17.2.2.54 Authentication Failure Report..................................................................................................................292 17.2.2.55 Resource Management.............................................................................................................................292 17.3 Application contexts.........................................................................................................................................293 17.3.1 General aspects..............................................................................................................................................293 17.3.2 Application context definitions.....................................................................................................................293 17.3.2.1 Void 293 17.3.2.2 Location Updating......................................................................................................................................293 17.3.2.3 Location Cancellation................................................................................................................................294 17.3.2.4 Roaming number enquiry...........................................................................................................................294 17.3.2.5 Void 294 17.3.2.6 Location Information Retrieval..................................................................................................................294 17.3.2.7 Call control transfer....................................................................................................................................295 17.3.2.8 Secure transport..........................................................................................................................................295 17.3.2.9 - 17.3.2.10 Void.........................................................................................................................................295 17.3.2.11 Location registers restart..........................................................................................................................295 17.3.2.12 Handover control......................................................................................................................................295 17.3.2.13 IMSI Retrieval..........................................................................................................................................296 17.3.2.14 Equipment Management..........................................................................................................................296 17.3.2.15 Information retrieval................................................................................................................................296 17.3.2.16 Inter-VLR information retrieval...............................................................................................................297 17.3.2.17 Stand Alone Subscriber Data Management.............................................................................................297 17.3.2.18 Tracing.....................................................................................................................................................297 17.3.2.19 Network functional SS handling..............................................................................................................298 17.3.2.20 Network unstructured SS handling..........................................................................................................298 17.3.2.21 Short Message Gateway...........................................................................................................................298 17.3.2.22 Mobile originating Short Message Relay.................................................................................................298 17.3.2.23 Void 299 17.3.2.24 Short message alert..................................................................................................................................299 17.3.2.25 Short message waiting data management................................................................................................299 17.3.2.26 Mobile terminating Short Message Relay................................................................................................299 17.3.2.27 MS purging...............................................................................................................................................300 17.3.2.28 Subscriber information enquiry................................................................................................................300 17.3.2.29 Any time information enquiry..................................................................................................................300 17.3.2.30 Group Call Control...................................................................................................................................300 17.3.2.31 Void 301 17.3.2.32 Gprs Location Updating...........................................................................................................................301 17.3.2.33 Gprs Location Information Retreival.......................................................................................................301 17.3.2.34 Failure Reporting.....................................................................................................................................301 17.3.2.35 GPRS Notifying.......................................................................................................................................301 17.3.2.36 Supplementary Service invocation notification.......................................................................................302 17.3.2.37 Reporting..................................................................................................................................................302

70

3GPP

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 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1020 1021 1022 1023 1024

71 Release 6 72 73

19

3GPP TS 29.002 V6.11.0 (2005-09)

17.3.2.38 Call Completion.......................................................................................................................................302 17.3.2.39 Location Service Gateway.......................................................................................................................303 17.3.2.40 Location Service Enquiry.........................................................................................................................303 17.3.2.41 Void 303 17.3.2.42 Void 303 17.3.2.43 Void 303 17.3.2.44 IST Alerting.............................................................................................................................................303 17.3.2.45 Service Termination.................................................................................................................................303 17.3.2.46 Mobility Management event notification.................................................................................................304 17.3.2.48 Subscriber Data modification notification...............................................................................................304 17.3.2.49 Authentication Failure Report..................................................................................................................304 17.3.2.50 Resource Management.............................................................................................................................304 17.3.3 ASN.1 Module for application-context-names.............................................................................................304 17.4 MAP Dialogue Information.............................................................................................................................307 17.5 MAP operation and error codes.......................................................................................................................309 17.6 MAP operations and errors..............................................................................................................................311 17.6.1 Mobile Service Operations............................................................................................................................311 17.6.2 Operation and Maintenance Operations........................................................................................................318 17.6.3 Call Handling Operations..............................................................................................................................319 17.6.4 Supplementary service operations.................................................................................................................322 17.6.5 Short message service operations..................................................................................................................326 17.6.6 Errors 328 17.6.7 Group Call operations...................................................................................................................................335 17.6.8 Location service operations...........................................................................................................................336 17.6.9 Secure transport operations...........................................................................................................................337 17.7 MAP constants and data types.........................................................................................................................339 17.7.1 Mobile Service data types.............................................................................................................................339 17.7.2 Operation and maintenance data types..........................................................................................................372 17.7.3 Call handling data types................................................................................................................................375 17.7.4 Supplementary service data types.................................................................................................................382 17.7.5 Supplementary service codes........................................................................................................................386 17.7.6 Short message data types..............................................................................................................................389 17.7.7 Error data types.............................................................................................................................................392 17.7.8 Common data types.......................................................................................................................................398 17.7.9 Teleservice Codes.........................................................................................................................................406 17.7.10 Bearer Service Codes..................................................................................................................................407 17.7.11 Extension data types....................................................................................................................................409 17.7.12 Group Call data types..................................................................................................................................410 17.7.13 Location service data types.........................................................................................................................412 17.7.14 Secure transport data types.........................................................................................................................420 18.1 Introduction......................................................................................................................................................422 18.2 Common aspects of user procedure descriptions.............................................................................................422 18.2.1 General conventions......................................................................................................................................422 18.2.2 Naming conventions......................................................................................................................................423 18.2.3 Convention on primitives parameters...........................................................................................................424 18.2.3.1 Open service...............................................................................................................................................424 18.2.3.2 Close service..............................................................................................................................................424 18.2.4 Version handling at dialogue establishment.................................................................................................424 18.2.4.1 Behaviour at the initiating side..................................................................................................................424 18.2.4.2 Behaviour at the responding side...............................................................................................................424 18.2.5 Abort Handling..............................................................................................................................................424 18.2.6 SDL conventions...........................................................................................................................................425 18.3 Interaction between MAP Provider and MAP Users.......................................................................................425 19.1 Location management Procedures...................................................................................................................426 19.1.1 Location updating..........................................................................................................................................427 19.1.1.1 General 427 19.1.1.2 Procedures in the VLR...............................................................................................................................432 19.1.1.3 Procedure in the PVLR..............................................................................................................................432

1005 18 General on MAP user procedures.....................................................................................................422

1019 19 Mobility procedures.........................................................................................................................426

74

3GPP

1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084

75 Release 6 76 77

20

3GPP TS 29.002 V6.11.0 (2005-09)

19.1.1.4 Procedure in the SGSN..............................................................................................................................432 19.1.1.5 Procedures in the HLR...............................................................................................................................433 19.1.2 Location Cancellation...................................................................................................................................453 19.1.2.1 General 453 19.1.2.2 Procedure in the HLR.................................................................................................................................453 19.1.2.3 Procedure in the VLR.................................................................................................................................454 19.1.2.4 Procedure in the SGSN..............................................................................................................................454 19.1.3 Void 461 19.1.4 MS Purging...................................................................................................................................................461 19.1.4.1 General 461 19.1.4.2 Procedure in the VLR.................................................................................................................................461 19.1.4.3 Procedure in the SGSN .............................................................................................................................461 19.1.4.4 Procedure in the HLR.................................................................................................................................462 19.2 Handover procedures.......................................................................................................................................467 19.2.1 General..........................................................................................................................................................467 19.2.2 Procedure in MSC-A.....................................................................................................................................470 19.2.2.1 Basic handover...........................................................................................................................................470 19.2.2.2 Handling of access signalling.....................................................................................................................471 19.2.2.3 Subsequent handover.................................................................................................................................471 19.2.3 Procedure in MSC-B.....................................................................................................................................471 19.2.3.1 Basic handover...........................................................................................................................................472 19.2.3.2 Handling of access signalling.....................................................................................................................472 19.2.3.3 Subsequent handover.................................................................................................................................472 19.2.4 Macro Receive_Error_From_HO_CA..........................................................................................................472 19.2.5 Procedure in VLR-B.....................................................................................................................................472 19.3 Fault recovery procedures................................................................................................................................491 19.3.1 VLR fault recovery procedures.....................................................................................................................491 19.3.1.1 General 491 19.3.1.2 Procedure in the VLR.................................................................................................................................492 19.3.1.3 Procedure in the HLR.................................................................................................................................492 19.3.2 HLR fault recovery procedures.....................................................................................................................494 19.3.2.1 General 494 19.3.2.2 Procedure in the HLR.................................................................................................................................495 19.3.2.3 Procedure in the VLR.................................................................................................................................495 19.3.2.4 Procedure in the SGSN..............................................................................................................................496 19.4 Mobility Management event notification procedure........................................................................................502 19.4.1 General..........................................................................................................................................................502 19.4.2 Procedure in the VLR or SGSN....................................................................................................................502 19.4.3 Procedure in the gsmSCF..............................................................................................................................502 19.4 HLR Insert Subscriber Data macros................................................................................................................505 19.5.1 Macro Insert_Subs_Data_Framed_HLR.......................................................................................................505 19.5.2 Macro Insert_GPRS_Subs_Data_Framed_HLR...........................................................................................505 20.1 General.............................................................................................................................................................508 20.1.1 Tracing Co-ordinator for the VLR................................................................................................................508 20.1.2 Tracing Co-ordinator for the SGSN..............................................................................................................508 20.1.3 Subscriber Data Management Co-ordinator for the VLR.............................................................................508 20.1.4 Subscriber Data Management Co-ordinator for the SGSN...........................................................................508 20.2 Tracing procedures...........................................................................................................................................513 20.2.1 Subscriber tracing activation procedure........................................................................................................516 20.2.1.1 Procedures in the HLR...............................................................................................................................516 20.2.1.2 Procedure in the VLR.................................................................................................................................516 20.2.1.3 Procedure in the SGSN..............................................................................................................................516 20.2.2 Subscriber tracing deactivation procedure....................................................................................................516 20.2.2.1 Procedures in the HLR...............................................................................................................................516 20.2.2.2 Procedure in the VLR.................................................................................................................................517 20.2.2.3 Procedure in the SGSN..............................................................................................................................517 20.3 Subscriber data management procedures.........................................................................................................530 20.3.1 Subscriber deletion procedure.......................................................................................................................531 20.3.1.1 Procedure in the HLR.................................................................................................................................531

1067 20 Operation and maintenance procedures............................................................................................508

78

3GPP

1085 1086 1087 1088 1089 1090 1091 1092 1093 1095 1096 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 1138 1139 1140 1141 1142 1143 1144

79 Release 6 80 81

21

3GPP TS 29.002 V6.11.0 (2005-09)

20.3.1.2 Procedure in the VLR.................................................................................................................................531 20.3.1.3 Procedure in the SGSN..............................................................................................................................531 20.3.2 Subscriber data modification procedure........................................................................................................532 20.3.2.1 Procedure in the HLR.................................................................................................................................532 20.3.2.2 Procedures in the VLR...............................................................................................................................533 20.3.2.3 Procedures in the SGSN.............................................................................................................................533 20.4 Subscriber Identity procedure..........................................................................................................................545 20.4.1 Procedure in the VLR....................................................................................................................................545 20.4.2 Procedure in the HLR....................................................................................................................................545 21.1 General.............................................................................................................................................................548 21.2 Retrieval of routing information......................................................................................................................548 21.2.1 General..........................................................................................................................................................548 21.2.2 Procedure in the GMSC................................................................................................................................551 21.2.9 Process in the gsmSCF..................................................................................................................................552 21.2.4 Procedure in the HLR....................................................................................................................................552 21.2.5 Procedure in the VLR to provide a roaming number....................................................................................552 21.2.6 Procedure in the VLR to restore subscriber data..........................................................................................552 21.2.7 Procedure in the VLR to provide subscriber information.............................................................................552 21.3 Transfer of call handling..................................................................................................................................561 21.3.1 General..........................................................................................................................................................561 21.3.2 Process in the VMSC....................................................................................................................................561 21.3.3 Process in the GMSC....................................................................................................................................562 21.4 Inter MSC Group Call Procedures...................................................................................................................565 21.4.1 General..........................................................................................................................................................565 21.4.2 Process in the Anchor MSC..........................................................................................................................565 21.4.3 Process in the Relay MSC.............................................................................................................................566 21.5 Void 571 21.6 CCBS: monitoring and reporting the status of the subscriber..........................................................................571 21.6.1 Reporting co-ordinator process in the VLR..................................................................................................571 21.6.2 Setting the reporting state stand-alone.......................................................................................................571 21.6.2.1 Process in the HLR.....................................................................................................................................571 21.6.2.2 Process in the VLR.....................................................................................................................................571 21.6.3 Status Reporting............................................................................................................................................571 21.6.3.1 Process in the VLR ....................................................................................................................................572 21.6.3.2 Process in the HLR ....................................................................................................................................573 21.6.4 CCBS: Remote User Free.............................................................................................................................573 21.6.4.1 Process in the HLR ....................................................................................................................................574 21.6.3.2 Process in the VLR ....................................................................................................................................574 21.7 Void 587 21.8 Void 587 21.9 Immediate Service Termination (IST).............................................................................................................587 21.9.1 IST Alert........................................................................................................................................................587 21.9.1.1 Procedure in the MSC................................................................................................................................587 21.9.1.2 Procedure in the HLR.................................................................................................................................587 21.9.2 IST Command...............................................................................................................................................587 21.9.2.1 Procedure in the HLR.................................................................................................................................588 21.9.2.2 Procedure in the MSC................................................................................................................................588 21.10 Resource Management...................................................................................................................................593 21.10.1 General........................................................................................................................................................593 21.3.2 Process in the GMSC....................................................................................................................................593 21.3.3 Process in the VMSC....................................................................................................................................593 22.1 Supplementary service co-ordinator processes................................................................................................596 22.1.1 Supplementary service co-ordinator process for the MSC...........................................................................596 22.1.2 Void 596 22.1.3 Functional supplementary service co-ordinator process for the HLR..........................................................596 22.1.4 Call completion supplementary service co-ordinator process for the HLR..................................................596 22.2 Registration procedure.....................................................................................................................................601 22.2.1 General..........................................................................................................................................................601

1094 21 Call handling procedures..................................................................................................................548

1137 22 Supplementary services procedures..................................................................................................596

82

3GPP

1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200

83 Release 6 84 85

22

3GPP TS 29.002 V6.11.0 (2005-09)

22.2.2 Procedure in the MSC...................................................................................................................................602 22.2.3 Procedure in the VLR....................................................................................................................................602 22.2.4 Procedure in the HLR....................................................................................................................................602 22.3 Erasure procedure.............................................................................................................................................608 22.3.1 General..........................................................................................................................................................608 22.3.2 Procedure in the MSC...................................................................................................................................609 22.3.3 Procedure in the VLR....................................................................................................................................609 22.3.4 Procedure in the HLR....................................................................................................................................609 22.4 Activation procedure........................................................................................................................................609 22.4.1 General..........................................................................................................................................................609 22.4.2 Procedure in the MSC...................................................................................................................................610 22.4.3 Procedure in the VLR....................................................................................................................................611 22.4.4 Procedure in the HLR....................................................................................................................................611 22.5 Deactivation procedure....................................................................................................................................617 22.5.1 General..........................................................................................................................................................617 22.5.2 Procedure in the MSC...................................................................................................................................618 22.5.3 Procedures in the VLR..................................................................................................................................618 22.5.4 Procedures in the HLR..................................................................................................................................618 22.6 Interrogation procedure....................................................................................................................................618 22.6.1 General..........................................................................................................................................................618 22.6.2 Procedure in the MSC...................................................................................................................................619 22.6.3 Procedures in the VLR..................................................................................................................................619 22.6.4 Procedure in the HLR....................................................................................................................................620 22.7 Void 624 22.8 Password registration procedure......................................................................................................................625 22.8.1 General..........................................................................................................................................................625 22.8.2 Procedure in the MSC...................................................................................................................................627 22.8.3 Procedure in the VLR....................................................................................................................................627 22.8.4 Procedure in the HLR....................................................................................................................................627 22.9 Mobile Initiated USSD procedure....................................................................................................................630 22.9.1 General..........................................................................................................................................................630 22.9.2 Procedure in the MSC...................................................................................................................................630 22.9.3 Procedure in the VLR....................................................................................................................................630 22.9.4 Procedure in the HLR....................................................................................................................................631 22.9.5 Procedures in the gsmSCF/secondary HLR..................................................................................................631 22.10 Network initiated USSD procedure...............................................................................................................645 22.10.1 General........................................................................................................................................................645 22.10.2 Procedure in the MSC.................................................................................................................................645 22.10.3 Procedure in the VLR..................................................................................................................................645 22.10.4 Procedure in the HLR..................................................................................................................................646 22.10.5 Procedure in the gsmSCF or secondary HLR.............................................................................................646 22.11 Common macros for clause 22.......................................................................................................................666 22.11.1 SS Password handling macros....................................................................................................................666 22.11.2 Void 666 22.12 Supplementary Service Invocation Notification procedure...........................................................................670 22.12.1 General........................................................................................................................................................670 22.12.2 Procedure in the MSC.................................................................................................................................670 22.12.3 Procedure in the gsmSCF............................................................................................................................670 22.13 Activation of a CCBS request........................................................................................................................673 22.13.1 General........................................................................................................................................................673 22.13.2 Procedure in the VLR..................................................................................................................................673 22.13.3 Procedure in the HLR..................................................................................................................................673 22.14 Deactivation of a CCBS request....................................................................................................................676 22.14.1 General........................................................................................................................................................676 22.14.2 Procedure in the VLR..................................................................................................................................676 22.14.3 Procedure in the HLR..................................................................................................................................676

1201 23 Short message service procedures....................................................................................................679


1202 23.1 General.............................................................................................................................................................679 1203 23.1.1 Mobile originated short message service Co-ordinator for the MSC...........................................................679 1204 23.1.2 Short message Gateway Co-ordinator for the HLR......................................................................................679

86

3GPP

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

87 Release 6 88 89

23

3GPP TS 29.002 V6.11.0 (2005-09)

23.2 The mobile originated short message transfer procedure................................................................................683 23.2.1 Procedure in the serving MSC......................................................................................................................684 23.2.2 Procedure in the VLR....................................................................................................................................684 23.2.3 Procedure in the SGSN.................................................................................................................................685 23.2.4 Procedure in the SMS Interworking MSC (SMS-IWMSC)..........................................................................685 23.3 The mobile terminated short message transfer procedure................................................................................697 23.3.1 Procedure in the SMS-GMSC.......................................................................................................................700 23.3.2 Procedure in the HLR....................................................................................................................................702 23.3.3 Procedure in the Serving MSC......................................................................................................................702 23.3.4 Procedure in the VLR....................................................................................................................................703 23.3.5 Procedure in the SGSN.................................................................................................................................703 23.4 The Short Message Alert procedure.................................................................................................................740 23.4.1 Procedure in the Serving MSC the MS has memory available..................................................................742 23.4.2 Procedures in the VLR..................................................................................................................................742 23.4.2.1 The Mobile Subscriber is present...............................................................................................................742 23.4.2.2 The MS has memory available...................................................................................................................742 23.4.3 Procedures in the SGSN................................................................................................................................743 23.4.3.1 The Mobile Subscriber is present...............................................................................................................743 23.4.3.2 The Mobile Equipment has memory available..........................................................................................743 23.4.4 Procedure in the HLR....................................................................................................................................743 23.4.5 Procedure in the SMS Interworking MSC....................................................................................................743 23.5 The SM delivery status report procedure.........................................................................................................752 23.5.1 Procedure in the SMS-GMSC.......................................................................................................................752 23.5.2 Procedure in the HLR....................................................................................................................................752 23.6 The macro Report_SM_Delivery_Stat_HLR...................................................................................................756 24.1 Procedure for retrieval of routeing information for GPRS..............................................................................759 24.1.1 Process in the GGSN ....................................................................................................................................759 24.1.2 Process in the HLR .......................................................................................................................................759 24.2 Procedure for reporting failure to establish a network requested PDP context...............................................762 24.2.1 Process in the GGSN.....................................................................................................................................762 24.2.2 Process in the HLR........................................................................................................................................762 24.3 Procedure for reporting that an MS has become reachable for GPRS.............................................................765 24.3.1 Process in the HLR........................................................................................................................................765 24.3.2 Process in the GGSN for Note Ms Present For Gprs....................................................................................765 24A.1 General..........................................................................................................................................................768 24A.2 Any Time Subscription Interrogation procedure..........................................................................................770 24A.2.1 General.......................................................................................................................................................770 24A.2.2 Process in the gsmSCF...............................................................................................................................770 24A.2.3 Process in the HLR.....................................................................................................................................770 24A.3 Any Time Modification procedure................................................................................................................773 24A.3.1 General.......................................................................................................................................................773 24A.3.2 Process in the gsmSCF...............................................................................................................................773 24A.3.3 Process in the HLR.....................................................................................................................................773 24A.4 Subscriber Data Modification Notification procedure..................................................................................776 24A.4.1 General.......................................................................................................................................................776 24A.4.2 Process in the HLR.....................................................................................................................................776 24A.4.3 Process in the gsmSCF...............................................................................................................................776 24A.5 Any Time Interrogation procedure................................................................................................................781 24A.5.1 General.......................................................................................................................................................781 24A.5.2 Procedures in the gsmSCF.........................................................................................................................782 24A.5.3 Procedure in the HLR.................................................................................................................................782 24A.5.4 Procedure in the GMLC.............................................................................................................................782 24B.1 Routeing information retrieval procedure for LCS.......................................................................................788 24B.1.1 General.......................................................................................................................................................788 24B.1.2 Process in the GMLC.................................................................................................................................788 24B.1.3 Process in the HLR.....................................................................................................................................788

1230 24 GPRS process description................................................................................................................759

1240 24A CSE interrogation and control of subscriber data..........................................................................768

1259 24B Location Services process description...........................................................................................788

90

3GPP

1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323

91 Release 6 92 93

24

3GPP TS 29.002 V6.11.0 (2005-09)

24B.2 Provide Subscriber Location procedure........................................................................................................791 24B.2.1 General.......................................................................................................................................................791 24B.2.2 Process in the GMLC.................................................................................................................................791 24B.2.3 Process in the MSC....................................................................................................................................791 24B.2.4 Process in the SGSN...................................................................................................................................791 24B.3 Subscriber Location Report procedure..........................................................................................................795 24B.3.1 General.......................................................................................................................................................795 24B.3.2 Process in the MSC....................................................................................................................................795 24B.3.3 Process in the SGSN...................................................................................................................................795 24B.3.4 Process in the GMLC.................................................................................................................................795 25.1 MAP_OPEN handling macros.........................................................................................................................799 25.1.1 Macro Receive_Open_Ind............................................................................................................................799 25.1.2 Macro Receive_Open_Cnf............................................................................................................................799 25.2 Macros to check the content of indication and confirmation primitives..........................................................804 25.2.1 Macro Check_Indication...............................................................................................................................804 25.2.2 Macro Check_Confirmation..........................................................................................................................804 25.3 The page and search macros............................................................................................................................807 25.3.1 Macro PAGE_MSC......................................................................................................................................807 25.3.2 Macro Search_For_MS_MSC.......................................................................................................................807 25.4 Macros for handling an Access Request..........................................................................................................810 25.4.1 Macro Process_Access_Request_MSC........................................................................................................810 25.4.2 Macro Process_Access_Request_VLR.........................................................................................................810 25.4.3 Macro Obtain_Identity_VLR........................................................................................................................810 25.4.4 Process Update_Location_Child_VLR.........................................................................................................810 25.5 Authentication macros and processes..............................................................................................................820 25.5.1 Macro Authenticate_MSC............................................................................................................................820 25.5.2 Macro Authenticate_VLR.............................................................................................................................820 25.5.3 Macro Obtain_Authent_Params_VLR..........................................................................................................820 25.5.4 Process Obtain_Authentication_Sets_VLR..................................................................................................820 25.5.6 Process Obtain_Authent_Sets_SGSN...........................................................................................................820 25.5.6 Process Obtain_Authent_Sets_HLR.............................................................................................................820 25.5.7 Authentication Failure Reporting..................................................................................................................821 25.5.7.1 General 821 25.5.7.2 Process in the VLR.....................................................................................................................................821 25.5.7.3 Process in the SGSN..................................................................................................................................821 25.5.7.4 Process in the HLR.....................................................................................................................................821 25.6 IMEI Handling Macros....................................................................................................................................837 25.6.1 Macro Check_IMEI_MSC............................................................................................................................837 25.6.2 Macro Check_IMEI_VLR............................................................................................................................837 25.6.3 Process Check_IMEI_SGSN........................................................................................................................837 25.6.4 Process Check_IMEI_EIR............................................................................................................................837 25.6.5 Macro Obtain_IMEI_MSC...........................................................................................................................837 25.6.6 Macro Obtain_IMEI_VLR............................................................................................................................837 25.7 Insert Subscriber Data macros and processes..................................................................................................846 25.7.1 Macro Insert_Subs_Data_VLR.....................................................................................................................846 25.7.2 Macro Insert_Subs_Data_SGSN...................................................................................................................846 25.7.3 Process Insert_Subs_Data_Stand_Alone_HLR............................................................................................846 25.7.4 Process Insert_GPRS_Subs_Data_Stand_Alone_HLR................................................................................846 25.7.5 Macro Wait_for_Insert_Subs_Data_Cnf......................................................................................................847 25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf..........................................................................................847 25.7.7 Process Send_Insert_Subs_Data_HLR.........................................................................................................847 25.8 Request IMSI Macros......................................................................................................................................857 25.8.1 Macro Obtain_IMSI_MSC............................................................................................................................857 25.8.2 Macro Obtain_IMSI_VLR............................................................................................................................857 25.9 Tracing macros.................................................................................................................................................860 25.9.1 Macro Trace_Subscriber_Activity_MSC......................................................................................................860 25.9.2 Macro Trace_Subscriber_Activity_VLR......................................................................................................860 25.9.3 Macro Trace_Subscriber_Activity_SGSN....................................................................................................860 25.9.4 Macro Activate_Tracing_VLR.....................................................................................................................860

1274 25 General macro description................................................................................................................799

94

3GPP

1324 1325 1326 1327 1328 1329 1330 1331

95 Release 6 96 97

25

3GPP TS 29.002 V6.11.0 (2005-09)

25.9.5 Macro Activate_Tracing_SGSN...................................................................................................................860 25.9.6 Macro Control_Tracing_With_VLR_HLR...................................................................................................860 25.9.7 Macro Control_Tracing_With_SGSN_HLR................................................................................................860 25.10 Short Message Alert procedures....................................................................................................................868 25.10.1 Process Subscriber_Present_VLR ..............................................................................................................868 25.10.2 Process SubscriberPresent_SGSN..............................................................................................................868 25.10.3 Macro Alert_Service_Centre_HLR............................................................................................................868 25.10.4 Process Alert_SC_HLR..............................................................................................................................868

1332 Annex A (informative): 1333 1334 Annex B (informative): 1335

Cross-reference for abstract syntaxes of MAP.................................872 Fully expanded ASN.1 sources for abstract syntaxes of MAP.......1114

1336 B.1 Fully Expanded ASN.1 Source of MAP-Protocol/TCAPMessages..............................................1114 1337 B.2 Fully Expanded ASN.1 Source of MAP-DialogueInformation.....................................................1250 1338 Annex C (informative): 1339
1340 1341 1342 1343 1344 1345 1346 1347 1348

Message Segmentation Mechanisms................................................1255

C.1 SCCP segmentation.........................................................................................................................................1255 C.2 TCAP segmentation.........................................................................................................................................1255 C.2.1 Empty Begin.................................................................................................................................................1255 C.2.2 Empty Continue............................................................................................................................................1255 C.2.3 TC-Result-NL...............................................................................................................................................1255 C.3 MAP Segmentation.........................................................................................................................................1256 C.3.1 Invoke without explicit indication................................................................................................................1256 C.3.2 Invoke with explicit indication.....................................................................................................................1256 C.3.3 Result 1256

1349 Annex D (informative): Void............................................................................................................1264 1350 Annex E (informative): 1351 1352


Change History..................................................................................1265

98

3GPP

99 Release 6 100 101

26

3GPP TS 29.002 V6.11.0 (2005-09)

1353

Foreword

1354 This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). 1355 The present document specifies the Mobile Application Part (MAP), the requirements for the signalling system and 1356 procedures within the 3GPP system at application level. 1357 The contents of the present document are subject to continuing work within the TSG and may change following formal 1358 TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an 1359 identifying change of release date and an increase in version number as follows: 1360 1361 1362 1363 1364 1365 1366 1367 1368

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.

102

3GPP

103 Release 6 104 105

27

3GPP TS 29.002 V6.11.0 (2005-09)

1384

1 Scope

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

1393
1394

Figure 1.1/1: Modelling principles

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

1399

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

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

1402
1403

1404 1405
1406 1407 1408 1409 1410 1411 1412 1413 1414 1415

106

3GPP

1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450

107 Release 6 108 109

28

3GPP TS 29.002 V6.11.0 (2005-09)

[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". Void 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 management procedures". 3GPP TS 43.020: "Security related network functions". 3GPP TS 23.038: "Alphabets and language". 3GPP TS 23.039: " Interface protocols for the connection of Short Message Service Centres (SMSCs) to Short Message Entities (SMEs)". 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". 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".

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

110

3GPP

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 1483 1484 1485 1486 1487 1488 1489 1490

111 Release 6 112 113

29

3GPP TS 29.002 V6.11.0 (2005-09)

[37]

3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". 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". Void Void Void 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)". 3GPP TS 29.011: "Signalling interworking for Supplementary Services".

[37a] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [49a1] [49b] [50] [51] [52] [53] [54] [55]

[56]

[57] [58]

[59]

114

3GPP

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 1525 1526 1527 1528 1529 1530 1531 1532 1533

115 Release 6 116 117

30

3GPP TS 29.002 V6.11.0 (2005-09)

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

3GPP TS 49.031: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". Void 3GPP TS 52.008: " GSM 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". ETR 091: "ETSI object identifier tree; Common domain Mobile domain" ITU-T Recommendation E.164: " The international public telecommunication numbering plan". ITU-T Recommendation E.212: " The international identification plan for mobile terminals and mobile users". ITU-T Recommendation E.213: " Telephone and ISDN numbering plan for land mobile stations in public land mobile networks (PLMN) ". ITU-T Recommendation E.214: " Structure of the land mobile global title for the signalling connection control part (SCCP) ". ITU-T Recommendation Q.699: " Interworking between ISDN access and non-ISDN access over ISDN User Part of Signalling System No. 7 ". 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".

[66b] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81]

118

3GPP

1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575

119 Release 6 120 121

31

3GPP TS 29.002 V6.11.0 (2005-09)

[82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93]

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.680: "Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation". ITU-T Recommendation X.681: "Information technology Abstract Syntax Notation One (ASN.1): Information object specification" ITU-T Recommendation X.690: "Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)". 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 4 - 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". Void 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".

[93b] [94]

[95] [97] [98] [99] [100] [101] [102] [103] [104] [105]

122

3GPP

1576 1577 1578 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 1608 1609 1610 1611 1612

123 Release 6 124 125

32

3GPP TS 29.002 V6.11.0 (2005-09)

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

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". 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." Void. Void Void Void Void ITU-T Recommendation 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 22.071: " Location Services (LCS); Service description, Stage 1" ITU-T Recommendation X.880: "Data networks and open system communication - Open System Interconnection - Service definitions - Remote operations: Concepts, model and notation". 3GPP TS 23.278: Customised Applications for Mobile Network Enhanced Logic (CAMEL) Phase 4 Stage 2 IM CN Interworking (Rel-5) 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification" 3GPP TS 26.103: "Speech codec list for GSM and UMTS". 3GPP TS 23.141: "Presence Service; Architecture and Functional Description" 3GPP TS 23.094: "Follow Me (FM) Stage 2" 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management (CM)". 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements". 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management".

126

3GPP

127 Release 6 128 129

33

3GPP TS 29.002 V6.11.0 (2005-09)

1613

3 Abbreviations

1614 ADD Automatic Device Detection 1615 All other abbreviations used in the present document are listed in 3GPP TS 21.905.

1616 1617 1618

4 Void 5 Overload and compatibility overview


5.1 Overload control

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

1621

5.1.1 Overload control for MSC (outside MAP)


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

1622 For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load: 1623 1624 1625 1626 1627

1628

5.1.2 Overload control for MAP entities

1629 For all MAP entities, especially the HLR, the following overload control method is applied. 1630 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) 1631 may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP 1632 service provider and is based upon the priority of the application context. 1633 Since most of the affected MAP operations are supervised in the originating entity by TC timers (medium) an additional 1634 delay effect is achieved for the incoming traffic. 1635 If overload levels are applicable in the Location Registers the MAP operations should be discarded taking into account 1636 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 1637 and table 5.1/4 for the SMLC; the lowest priority is discarded first). 1638 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 1639 a proposal that might be changed due to network operator/implementation matters. 1640 If secure transport is used, the encapsulated application context for the requested dialogue determines the priority for 1641 discarding the received MAP operation.

130

3GPP

1642

131 Release 6 132 133

34

3GPP TS 29.002 V6.11.0 (2005-09)

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


Responder = HLR Initiating Entity VLR

1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673

Priority high 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/v3) reporting (statusReport)

SGSN VLR/SGSN MSC msPurging SGSN GMSC

VLR

GMSC gsmSCF VLR

1674 1675 1676


1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700

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) Priority low

GMLC
VLR

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

1701 1702

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.

134

3GPP

1703

135 Release 6 136 137

35

3GPP TS 29.002 V6.11.0 (2005-09)

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


Initiating Entity HLR HLR HLR HLR

1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1732 1733 1734 1735 1736

Responder = SGSN Priority high Mobility and Location Register Management locationCancel (cancelLocation v3) reset (reset) subscriberDataMngt (insertSubscriberData v3), (deleteSubscriberData v3) tracing (activateTraceMode), (deactivateTraceMode) Short Message Service shortMsgMT-Relay (MT-ForwardSM v3), (forwardSM v1/v2) Location Services locationSvcEnquiry (provideSubscriberLocation v3) Network-Requested PDP context activation gprsNotify (noteMsPresentForGprs v3), (Subscriber Location & State retrieval) subscriberInfoEnquiry (provideSubscriberInformation/v3) Priority low

MSC

GMLC

HLR

HLR

1737 1738

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.

138

3GPP

1739

139 Release 6 140 141

36

3GPP TS 29.002 V6.11.0 (2005-09)

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 resourceMngt (releaseResources) roamingNbEnquiry (provideRoamingNumber) callControlTransfer (resumeCallHandling) subscriberInfoEnquiry (provideSubscriberInformation/v3) reporting (remoteUserFree), (SetReportingState)

MSC

HLR HLR HLR VLR HLR HLR

MSC/SGSN MSC HLR

GMSC HLR MSC HLR HLR

Location Services locationSvcEnquiry (provideSubscriberLocation/v3)


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

GMLC

HLR

1741 1742

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.

142

3GPP

1743

143 Release 6 144 145

37

3GPP TS 29.002 V6.11.0 (2005-09)

5.1.3 Congestion control for Signalling System No. 7

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

1746 1747

5.2 Compatibility
5.2.1 General

1748 The present document of the Mobile Application Part is designed in such a way that an implementation which conforms 1749 to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR 1750 interface. 1751 A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol 1752 version used between two entities for supporting a MAP-user signalling procedure. 1753 1754 1755 1756

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.

1757 A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of 1758 version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP 1759 operational version 1). 1760 1761 1762 1763 1764 1765 1766 1767

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.

1768

5.2.2 Strategy for selecting the Application Context (AC) version

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

1772 5.2.2.1
1773 1774 1775 1776 1777 1778 1779

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.

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

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;

146

3GPP

1786 1787 1788 1789

147 Release 6 148 149

38

3GPP TS 29.002 V6.11.0 (2005-09)

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.

1790 5.2.2.2

Managing the version look-up table

1791 WHEN it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the 1792 originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the 1793 IMSI or the MSISDN. 1794 IF the entity number is known: 1795 1796 1797 1798

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.

1799 WHEN starting a procedure, the originating MAP-user looks up its version control table. 1800 IF the destination address is known and not timed-out. 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822

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.

150

3GPP

1823 1824

151 Release 6 152 153

39

3GPP TS 29.002 V6.11.0 (2005-09)

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

1825 5.2.2.3

Optimising the method

1826 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 1827 each subscriber the version of the AC-name used at location updating. Then: 1828 1829 1830 1831 1832 1833 1834 1835 1836

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.

1837 1838

6 Requirements concerning the use of SCCP and TC


6.1 Use of SCCP

1839 The Mobile Application Part (MAP) makes use of the services offered by the Signalling Connection Control Part 1840 (SCCP). 1841 MAP supports the following SCCP versions:

1842 1843
1844 1845 1846 1847 1848 1849 1850

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.

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

1856

6.1.1 SCCP Class

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

1858

6.1.2 Sub-System Number (SSN)

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

154

3GPP

1861 When the SGSN emulates MSC behaviour for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, 1862 MAP_CHECK_IMEI, MAP_SUBSCRIBER_LOCATION_REPORT) towards entities which do not support 1863 interworking to SGSNs, it shall use the MSC SSN in the calling party address instead of the SGSN SSN. 1864 When present in the network, the Presence Network Agent emulates the behaviour of the GSM Service Control 1865 Function (gsm SCF) for processing of messages (MAP-NOTE-MM-EVENT, MAP-ANY-TIME-INTERROGATION 1866 and MAP-ANY-TIME-MODIFICATION).

155 Release 6 156 157

40

3GPP TS 29.002 V6.11.0 (2005-09)

1867 1868 6.1.3.1

6.1.3 SCCP addressing


Introduction

1869 Within the GSM System there will be a need to communicate between entities within the same PLMN and in different 1870 PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) 1871 and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. 1872 Only the entities that should be addressed are described below. If the CCITT or ITU-T SCCP is used, the format and 1873 coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 1874 with the following restrictions: 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896

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

1897 If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall 1898 comply with ANSI specification T1.112 with the following restrictions: 1899 1900 1901

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.

158

3GPP

1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920

159 Release 6 160 161

41

3GPP TS 29.002 V6.11.0 (2005-09)

2) Inter-PLMN addressing a) Called Party Address SSN indicator = 1 (MAP SSN always included); Global title indicator = 0010 (Global title includes translation type); the Translation Type (TT) field will be coded as follows: TT = 9, if IMSI is included; TT = 14, if MSISDN is included; Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked). Routing indicator = 0 (Routing on global title);

b) Calling Party Address SSN indicator = 1 (MAP SSNs always included); Point code indicator = 0; Global Title indicator = 0010 (Global title includes translation type); TT = 9, if IMSI is included; TT = 14, if MSISDN is included; Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked). Routing indicator = 0 (Routing on Global Title).

1921 If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and 1922 E.214 is applicable. 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943

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.

162

3GPP

1944 The following clauses describe the method of SCCP addressing appropriate for each entity both for the simple 1945 intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered: 1946 1947 1948 1949 1950 1951 1952 1953 1954

163 Release 6 164 165

42

3GPP TS 29.002 V6.11.0 (2005-09)

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 Serving GPRS Support Node (SGSN); the Gateway GPRS Support Node (GGSN); the Gateway Mobile Location Centre (GMLC).

1955 6.1.3.2

The Mobile-services Switching Centre (MSC)

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

1957 6.1.3.2.1

MSC interaction during handover or relocation

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

1959 6.1.3.2.2

MSC for short message routing

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

1963 6.1.3.2.3

MSC for location request routing

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

1966 6.1.3.2.4

MSC for LMU Control

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

1969 6.1.3.3

The Home Location Register (HLR)

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

1971 6.1.3.3.1
1972 1973 1974 1975

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

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

166

3GPP

1979 6.1.3.3.2
1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990

167 Release 6 168 169

43

3GPP TS 29.002 V6.11.0 (2005-09)

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.

1991 When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of 1992 the SCCP message containing the first responding CONTINUE message. 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004

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.

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

2009 6.1.3.3.3
2010 2011 2012 2013 2014 2015

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.

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

170

3GPP

2019 6.1.3.3.4
2020 2021 2022 2023 2024 2025 2026 2027 2028

171 Release 6 172 173

44

3GPP TS 29.002 V6.11.0 (2005-09)

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.

2029 6.1.3.3.5
2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046

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.

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

2049 6.1.3.3.6
2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066

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;

174

3GPP

2067 2068 2069 2070

175 Release 6 176 177

45

3GPP TS 29.002 V6.11.0 (2005-09)

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.

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

2073 6.1.3.3.7
2074 2075 2076 2077 2078

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.

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

2081 6.1.3.3.8
2082 2083 2084 2085

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.

2086 6.1.3.4

The Visitor Location Register (VLR)

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

2088 6.1.3.4.1

Inter-VLR information retrieval

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

2092 6.1.3.4.2

HLR request

2093 The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR service area. 2094 This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has 2095 indicated successful completion of the update location procedure to the VLR. 2096 2097 2098 2099 2100

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.

2101 6.1.3.5

The Interworking MSC (IWMSC) for Short Message Service

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

2104 6.1.3.6

The Equipment Identity Register (EIR)

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

178

3GPP

2106 6.1.3.7 2107 6.1.3.8


2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120

179 Release 6 180 181

46

3GPP TS 29.002 V6.11.0 (2005-09)

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

2121 6.1.3.9
2122 2123 2124 2125

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.

2126 6.1.3.10

The Gateway MSC (GMSC) for Short Message Service

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

2129 6.1.3.10A 2130 6.1.3.10A.1 2131 6.1.3.10A.2 2132 6.1.3.10B


2133 2134 2135 2136

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.

2137 6.1.3.11

Summary table

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

182

3GPP

2144

183 Release 6 184 185

47

3GPP TS 29.002 V6.11.0 (2005-09)

Table 6.1/1
fixed net work
-----

to from fixed network Home Location Register Visitor Location Register

HLR
E:GT T:MSISDN ---

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

MSC
-----

EIR
-----

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

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

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

---

mobileservices switching centre gsm Service Control Function 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:MGT/ MSISDN/HL R NUMBER I:SPC/GT E:GT T:MGT I:SPC/GT

---

---

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

---

---

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

2145 2146
to from fixed network Home Location Register Visitor Location Register Mobile-services Switching Centre gsm Service Control Function Serving GPRS Support Node Gateway

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

186

3GPP

187 Release 6 188 189

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

3GPP TS 29.002 V6.11.0 (2005-09)

2147

2148

6.2 Use of TC

2149 The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of Signalling 2150 System No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be 2151 consulted for the full specification of TC. 2152 The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility. 2153 From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is 2154 for further study. 2155 Transaction Capabilities refers to a protocol structure above the network layer interface (i.e., the SCCP service 2156 interface) up to the application layer including common application service elements but not the specific application 2157 service elements using them. 2158 TC is structured as a Component sub-layer above a Transaction sub-layer. 2159 The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues 2160 and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives 2161 and TC-Component handling primitives respectively. 2162 Services for dialogue control include the ability to exchange information related to application-context negotiation as 2163 well as initialisation data. 2164 2165 2166 2167 2168 2169 2170

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

2171 2172

7 General on MAP services


7.1 Terminology and definitions

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

2175

7.2 Modelling principles

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

190

3GPP

191 Release 6 192 193

49

3GPP TS 29.002 V6.11.0 (2005-09)

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

2178
2179

Figure 7.2/1: Modelling principles

2180 The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the 2181 service interface. 2182 A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such 2183 cases the overall procedure is synchronised by the service-user. 2184 The MAP service-primitives are named using the following notation: 2185

MAP-ServicePrimitiveName type

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

2195

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.

2196 All MAP service-users require access to services for performing basic application layer functions: 2197 2198 2199 2200 2201

2202 For these purposes the following common services are defined: 2203 2204 2205 2206 2207 2208 2209

MAP-OPEN service; MAP-CLOSE service; MAP-DELIMITER service; MAP-U-ABORT service; MAP-P-ABORT service; MAP-NOTICE service; MAP-SECURE-TRANSPORT-CLASS-1 service;

194

3GPP

2210 2211 2212

195 Release 6 196 197

50

3GPP TS 29.002 V6.11.0 (2005-09)

MAP-SECURE-TRANSPORT-CLASS-2 service; MAP-SECURE-TRANSPORT-CLASS-3 service; MAP-SECURE-TRANSPORT-CLASS-4 service.

2213 In defining the service-primitives the following convention is used for categorising parameters: 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232

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

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

2235

7.3.1 MAP-OPEN service

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

2239 2240 Application context name: 2241 This parameter identifies the type of application context being established. If the dialogue is accepted the received 2242 application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version 2243 supported.

198

3GPP

2244 Destination address: 2245 A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this 2246 parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is 2247 issued. 2248 Destination-reference: 2249 This parameter is a reference that refines the identification of the called process. It may be identical to Destination 2250 address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only 2251 these services are allowed to use it. 2252

199 Release 6 200 201

51

3GPP TS 29.002 V6.11.0 (2005-09)

Table 7.3/2: Use of the destination reference MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTURED-SS-NOTIFY MAP-FORWARD-SHORT-MESSAGE MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY Reference type IMSI IMSI IMSI IMSI IMSI IMSI IMSI (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

2253 2254 2255 2256 2257 2259 2260


2258

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.

2261 Originating address: 2262 A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, 2263 this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is 2264 issued. 2265 Originating-reference: 2266 This parameter is a reference that refines the identification of the calling process. It may be identical to the Originating 2267 address but its value is to be carried at MAP level. Table 7.3/3 describes the MAP services using the parameter. Only

202

3GPP

2268 these services are allowed to use it. Processing of the Originating-reference shall be performed according to the 2269 supplementary service descriptions and other service descriptions, e.g. operator determined barring. Furthermore the 2270 receiving entity may be able to use the value of the Originating-reference to screen the service indication. 2271

203 Release 6 204 205

52

3GPP TS 29.002 V6.11.0 (2005-09)

Table 7.3/3: Use of the originating reference MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-NOTIFY MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY Reference type ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String (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

2272 2273

NOTE:

The Originating reference may be omitted.

2274 Specific information: 2275 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2276 information is not specified by GSM and shall be performed according to operator specific requirements. 2277 Responding address: 2278 An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is 2279 different from the destination address). 2280 Result: 2281 This parameter indicates whether the peer accepts the dialogue. 2282 Refuse reason: 2283 This parameter is present only if the Result parameter indicates that the dialogue is refused. It takes one of the following 2284 values:

2285 2286 2287 2288

-Application-context-not-supported; -Invalid-destination-reference; -Invalid-originating-reference; -No-reason-given;

206

3GPP

2289 2290 2291 2292 2293

207 Release 6 208 209

53

3GPP TS 29.002 V6.11.0 (2005-09)

-Remote node not reachable; -Potential version incompatibility; -Secured transport not possible; -Transport protection not adequate.

7.3.2 MAP-CLOSE service

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

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


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

2298 2299 Release method: 2300 This parameter can take the following two values: 2301 2302 2303

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.

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

2307

7.3.3 MAP-DELIMITER service

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

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


Parameters Request Indication

2312

2313

7.3.4 MAP-U-ABORT service

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

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

2317

210

3GPP

2318 User reason: 2319 This parameter can take the following values: 2320 2321 2322 2323 2324 2325 2326 2327

211 Release 6 212 213

54

3GPP TS 29.002 V6.11.0 (2005-09)

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

resource unavailable; 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.

2328 Diagnostic information: 2329 This parameter may be used to give additional information for some of the values of the user-reason parameter: 2330

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

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

2335

7.3.5 MAP-P-ABORT service

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

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


Parameters Provider reason Source Indication M M

2339 2340 Provider reason: 2341 This parameter indicates the reason for aborting the MAP dialogue: 2342 2343 2344

provider malfunction; supporting dialogue/transaction released; resource limitation;

214

3GPP

2345 2346 2347

215 Release 6 216 217

55

3GPP TS 29.002 V6.11.0 (2005-09)

maintenance activity; version incompatibility; abnormal MAP dialogue.

2348 Source: 2349 This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take 2350 the following values: 2351 2352 2353 2354 2355

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

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

2356

2357

7.3.6 MAP-NOTICE service

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

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


Parameters Problem diagnostic Indication M

2362 2363 Problem diagnostic: 2364 This parameter can take one of the following values: 2365 2366 2367 2368

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

218

3GPP

2369

219 Release 6 220 221

56

3GPP TS 29.002 V6.11.0 (2005-09)

7.3.7 MAP-SECURE-TRANSPORT-CLASS-1 service

2370 This service is used for secure transport of a specific confirmed MAP service which is mapped on to a TCAP class 1 2371 operation (i.e. one which can return a result or an error). The service is a confirmed service with service primitives as 2372 shown in table 7.3/11. 2373

Table 7.3/11: Service-primitives for the MAP-SECURE-TRANSPORT-CLASS-1 service


Parameters Security header Protected payload User error Provider error Request M C Indication M(=) C(=) Response M U U Confirm M(=) C(=) C(=) O

2374 2375 Security header: 2376 This parameter carries the security header information required for secure transport of MAP messages. The details of 2377 this parameter are given in clause 7.6.12. 2378 Protected payload: 2379 This parameter represents in protected mode the complete Request, Indication, Response or Confirm primitive of the 2380 service which makes use of the MAP-SECURE-TRANSPORT-CLASS-1 service. 2381 User error: 2382 If the application at the responding entity returns an error to be carried in the secure transport envelope, this parameter 2383 contains the Secure transport error defined in clause 7.6.1. 2384 Provider error 2385 For the definition of provider errors see clause 7.6.1.

2386

7.3.8 MAP-SECURE-TRANSPORT-CLASS-2 service

2387 This service is used for secure transport of a specific confirmed MAP service which is mapped on to a TCAP class 2 2388 operation (i.e. one which can return an error but no result). The service is a confirmed service with service primitives as 2389 shown in table 7.3/12. 2390

Table 7.3/12: Service-primitives for the MAP-SECURE-TRANSPORT-CLASS-2 service


Parameters Security header Protected payload User error Provider error Request M C Indication M(=) C(=) Response M U Confirm M(=) C(=) O

2391 2392 Security header: 2393 This parameter carries the security header information required for secure transport of MAP messages. The details of 2394 this parameter are given in clause 7.6.12. 2395 Protected payload: 2396 This parameter represents in protected mode the complete Request, Indication, Response or Confirm primitive of the 2397 service which makes use of the MAP-SECURE-TRANSPORT-CLASS-2 service. 2398 User error: 2399 If the application at the responding entity returns an error to be carried in the secure transport envelope, this parameter 2400 contains the Secure transport error defined in clause 7.6.1. 2401 Provider error 2402 For the definition of provider errors see clause 7.6.1.

222

3GPP

2403

223 Release 6 224 225

57

3GPP TS 29.002 V6.11.0 (2005-09)

7.3.9 MAP-SECURE-TRANSPORT-CLASS-3 service

2404 This service is used for secure transport of a specific confirmed MAP service which is mapped on to a TCAP class 3 2405 operation (i.e. one which can return a result but no error). The service is a confirmed service with service primitives as 2406 shown in table 7.3/13. 2407

Table 7.3/13: Service-primitives for the MAP-SECURE-TRANSPORT-CLASS-3 service


Parameters Security header Protected payload Provider error Request M C Indication M(=) C(=) Response M U Confirm M(=) C(=) O

2408 2409 Security header: 2410 This parameter carries the security header information required for secure transport of MAP messages. The details of 2411 this parameter are given in clause 7.6.12. 2412 Protected payload: 2413 This parameter represents in protected mode the complete Request, Indication, Response or Confirm primitive of the 2414 service which makes use of the MAP-SECURE-TRANSPORT-CLASS-3 service. 2415 Provider error 2416 For the definition of provider errors see clause 7.6.1.

2417

7.3.10 MAP-SECURE-TRANSPORT-CLASS-4 service

2418 This service is used for secure transport of a specific unconfirmed MAP service which is mapped on to a TCAP class 4 2419 operation (i.e. one which can return neither a result nor an error). The service is an unconfirmed service with service 2420 primitives as shown in table 7.3/14. 2421

Table 7.3/14: Service-primitives for the MAP-SECURE-TRANSPORT-CLASS-4 service


Parameters Security header Protected payload Request M C Indication M(=) C(=)

2422 2423 Security header: 2424 This parameter carries the security header information required for secure transport of MAP messages. The details of 2425 this parameter are given in clause 7.6.12. 2426 Protected payload: 2427 This parameter represents in protected mode the complete Request or Indication primitive of the service which makes 2428 use of the MAP-SECURE-TRANSPORT-CLASS-4 service.

2429

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:

2430 The sequencing of services is shown in figure 7.4/1 and is as follows: 2431 2432 2433 2434 2435 2436 2437

226

3GPP

2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451

227 Release 6 228 229

58

3GPP TS 29.002 V6.11.0 (2005-09)

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.

2452 The MAP service-provider may issue at any time a MAP-P-ABORT primitive towards a MAP service-user for which a 2453 MAP dialogue exists. 2454 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

2455
2456

a) Opening

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

2457
2458

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

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

2459
2460

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

2461
2462

d) Aborting

230

3GPP

2463

231 Release 6 232 233

59

3GPP TS 29.002 V6.11.0 (2005-09)

Figure 7.4/1: Sequencing of services

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

2469 2470

7.5 General rules for mapping of services onto TC


7.5.1 Mapping of common services

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

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 MAP-U-ABORT request
NOTE:

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) TC-U-ABORT request

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

2475 2476

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

234

3GPP

235 Release 6 60 3GPP TS 29.002 V6.11.0 (2005-09) 236 237 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.

2477

2478

7.5.2 Mapping of user specific services

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

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)

2483 2484

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


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

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

2485 2486 2487 2488 2489 2490 2491

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.

2492 2493

7.6 Definition of parameters


7.6.1 Common parameters

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

2495 7.6.1.1

Invoke Id

238

3GPP

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

239 Release 6 240 241

61

3GPP TS 29.002 V6.11.0 (2005-09)

2498 7.6.1.2

Linked Id

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

2500 7.6.1.3
-

Provider error

2501 This parameter is used to indicate a protocol related type of error: 2502 2503 2504 2505 2506 2507 2508 2509 2510

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

2511 7.6.1.4
NOTE:

User error

2512 This parameter can take values as follows: 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531

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 or additional 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; Needed LCS capability not supported in serving node;

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;

242

3GPP

2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543

243 Release 6 244 245

62

3GPP TS 29.002 V6.11.0 (2005-09)

unidentified subscriber, i.e. if the subscriber is not contained in the database and it has not or cannot be established whether or not a subscription exists; unallocated roaming number; unknown equipment; unknown location area.

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

d) Handover problem: -no handover number available, 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.

2544
2545

2546 2547
2548 2549 2550 2551 2552

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.

2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568

g) Supplementary services problem:

246

3GPP

2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581

247 Release 6 248 249

63

3GPP TS 29.002 V6.11.0 (2005-09)

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

2582 For definition of these errors see 3GPP TS 24.080 [38]. 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605

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.040, 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.040;

250

3GPP

251 Release 6 252 253

64

3GPP TS 29.002 V6.11.0 (2005-09)

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.

2606

i) Location services problem: -Unauthorised Requesting Network -Unauthorised LCS Client with detailed reasons as follows: - NoAdditional Information - Client not in MS Privacy Exception List - Call to Client not setup - Disallowed by Local Regulatory Requirements Unauthorised Privacy Class Unauthorised Call/Session Unrelated External Client Unauthorised Call/Session Related External Client Privacy override not applicable

2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625
2626 2627 2628 2629 2630 2631

-Position method failure with detailed reasons as follows: Congestion Insufficient resources 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.

2632 7.6.1.5

All Information Sent

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

2634 2635 7.6.2.1

7.6.2 Numbering and identification parameters


IMSI

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

254

3GPP

2637 7.6.2.2

255 Release 6 256 257

65

3GPP TS 29.002 V6.11.0 (2005-09)

TMSI

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

2639 7.6.2.3

IMEI

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

2641 7.6.2.3a

IMEISV

2642 This parameter is the International Mobile Equipment Identity and Software Version Number defined in 3GPP TS 2643 23.003 [17].

2644 7.6.2.4

Previous location area Id

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

2646 7.6.2.5

Stored location area Id

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

2648 7.6.2.6

Current location area Id

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

2650 7.6.2.7

Target location area Id

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

2652 7.6.2.8

Target cell Id

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

2654 7.6.2.8A

Target RNC Id

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

2656 7.6.2.9 2657 7.6.2.10

Void Originating entity number

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

2660 7.6.2.11

MSC number

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

2662 7.6.2.12

Target MSC number

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

2664 7.6.2.13

HLR number

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

2666 7.6.2.14

VLR number

258

3GPP

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

259 Release 6 260 261

66

3GPP TS 29.002 V6.11.0 (2005-09)

2668 7.6.2.15

HLR Id

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

2670 7.6.2.16

LMSI

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

2673 7.6.2.17

MS ISDN

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

2676 7.6.2.18

OMC Id

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

2678 7.6.2.19

Roaming number

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

2680 7.6.2.19A

Relocation Number List

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

2682 7.6.2.20 2683 7.6.2.21

Void Handover number

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

2685 7.6.2.22

Forwarded-to number

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

2688 7.6.2.22A

Long forwarded-to number

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

2691 7.6.2.22B

Long FTN Supported

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

2693 7.6.2.23

Forwarded-to subaddress

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

2695 7.6.2.24

Called number

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

2697 7.6.2.25

Calling number

262

3GPP

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

263 Release 6 264 265

67

3GPP TS 29.002 V6.11.0 (2005-09)

2699 7.6.2.26

Originally dialled number

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

2701 7.6.2.27

Service centre address

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

2703 7.6.2.28

Zone Code

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

2707 7.6.2.29

MSIsdn-Alert

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

2710 7.6.2.30

Location Information

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

2712 7.6.2.30a

Location Information for GPRS

2713 This parameter indicates the location of the served subscriber as defined in 3GPP TS 23.078 [98].

2714 7.6.2.31

GMSC Address

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

2716 7.6.2.32

VMSC Address

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

2718 7.6.2.33

Group Id

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

2721 7.6.2.34

North American Equal Access preferred Carrier Id

2722 This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an inter-exchange 2723 carrier. This identity is used at: 2724 2725 2726

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.

2727 7.6.2.35 2728 7.6.2.36 2729 7.6.2.37

Void Void Serving cell Id

266

3GPP

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

267 Release 6 268 269

68

3GPP TS 29.002 V6.11.0 (2005-09)

2731 7.6.2.38

SGSN number

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

2733 7.6.2.39

SGSN address

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

2735 7.6.2.40

GGSN address

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

2737 7.6.2.41

GGSN number

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

2740 7.6.2.42

APN

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

2742 7.6.2.43

Network Node number

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

2744 7.6.2.44

PDP-Type

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

2746 7.6.2.45

PDP-Address

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

2748 7.6.2.46

Additional number

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

2750 7.6.2.47

P-TMSI

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

2752 7.6.2.48

B-subscriber number

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

2754 7.6.2.49

B-subscriber subaddress

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

2756 7.6.2.50

LMU Number

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

2758 7.6.2.51

MLC Number

270

3GPP

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

271 Release 6 272 273

69

3GPP TS 29.002 V6.11.0 (2005-09)

2760 7.6.2.52

Multicall Bearer Information

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

2762 7.6.2.53

Multiple Bearer Requested

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

2764 7.6.2.54

Multiple Bearer Not Supported

2765 This parameter indicates whether multiple bearers are supported.

2766 7.6.2.55

PDP-Charging Characteristics

2767 This parameter indicates the charging characteristics associated with a specific PDP context as defined in 3GPP 2768 TS 32.215.

2769 7.6.2.56

Selected RAB ID

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

2771 7.6.2.57

RAB ID

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

2774 7.6.2.58

gsmSCF Address

2775 This parameter refers to the ISDN number assigned to the gsmSCF address. In an IP Multimedia Core Network, the 2776 gsmSCF-address shall contain the IM-SSF address when the IM-SSF takes the role of the gsmSCF.

2777 7.6.2.59

V-GMLC Address

2778 This parameter refers to the IP address of a V-GMLC.

2779 7.6.2.60 2780 7.6.2.61

Void H-GMLC Address

2781 This parameter refers to the IP address of a H-GMLC.

2782 7.6.2.62

PPR Address

2783 This parameter refers to the IP address of a Privacy Profile Register.

2784 7.6.2.63

Routeing Number

2785 This parameter refers to a number used for routeing purpose and identifying a network operator. See 3GPP TS 23.066 2786 [108].

2787 7.6.2.64

Additional V-GMLC Address

2788 This parameter refers to the IP address of a V-GMLC.

2789

7.6.3 Subscriber management parameters


3GPP

274

2790 7.6.3.1

275 Release 6 276 277

70

3GPP TS 29.002 V6.11.0 (2005-09)

Category

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

2792 7.6.3.2

Equipment status

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

2794 7.6.3.2a

BMUEF

2795 This parameter refers to the Bit Map of UE Faults and corresponds to the UESBI-Iu parameter defined in 3GPP TS 2796 25.413 [120].

2797 7.6.3.3

Extensible Bearer service

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

2801 7.6.3.4

Extensible Teleservice

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

2805 7.6.3.5
2806 2807 2808 2809

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.

2810 7.6.3.6

GSM bearer capability

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

2812 7.6.3.7
-

Subscriber Status

2813 This parameter refers to the barring status of the subscriber: 2814 2815

service granted; Operator Determined Barring.

2816 7.6.3.8

CUG Outgoing Access indicator

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

2818 7.6.3.9

Operator Determined Barring General Data

2819 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate. 2820 This set only includes those limitations that can be 2821 2822 2823 2824

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:

278

3GPP

2825

279 Release 6 280 281

71

3GPP TS 29.002 V6.11.0 (2005-09)

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

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

X X X

X X

X X

X X

X X X

X X X

282

3GPP

283 Release 6 284 285

72

3GPP TS 29.002 V6.11.0 (2005-09)

Invocation of call transfer if there is already an ongoing transferred call for the served subscriber in the serving MSC/VLR 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

X X X

X X X X

X X

X X X X

2826

286

3GPP

2827

287 Release 6 288 289

73

3GPP TS 29.002 V6.11.0 (2005-09)

2828 7.6.3.10

ODB HPLMN Specific Data

2829 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate only 2830 when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in the 2831 VLR or in the SGSN: 2832 2833 2834 2835

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

2836 7.6.3.11

Regional Subscription Data

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

2839 7.6.3.12

Regional Subscription Response

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

2842 7.6.3.13

Roaming Restriction Due To Unsupported Feature

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

2845 7.6.3.14
-

Extensible SS-Info

2846 This parameter refers to all the information related to a supplementary service and is a choice between: 2847 2848 2849 2850

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

2851 7.6.3.15
-

Extensible forwarding information

2852 This parameter represents the information related to each call forwarding service: 2853 2854 2855

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

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

2856 7.6.3.16

Extensible forwarding feature

2857 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 2858 following information, as required: 2859 2860

extensible Basic Service Group extensible SS-Status

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

290

3GPP

2861 2862 2863 2864 2865 2866 2867 2868 2869 2870

291 Release 6 292 293

74

3GPP TS 29.002 V6.11.0 (2005-09)

forwarded-to number forwarded-to subaddress extensible forwarding options extensible no reply condition timer long forwarded-to number

(see clause 7.6.2.22); (see clause 7.6.2.23); (see clause 7.6.3.18); (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.

2871 7.6.3.17

Extensible SS-Status

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

2873 7.6.3.18

Extensible Forwarding Options

2874 This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following 2875 information: 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885

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

2886 7.6.3.19

Extensible No reply condition timer

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

2888 7.6.3.20
SS-Code

Extensible Call barring information


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

2889 This parameter contains for each call barring service: 2890 2891 2892

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

2893 7.6.3.21

Extensible Call barring feature

2894 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 2895 contains the following information: 2896 2897

Extensible Basic Service Group provisioned SS-Status

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

294

3GPP

2898 7.6.3.22
-

295 Release 6 296 297

75

3GPP TS 29.002 V6.11.0 (2005-09)

CUG info

2899 This parameter refers to the overall information required for operation for each CUG: 2900 2901

CUG subscriptionList; CUG featureList.

2902 7.6.3.23

CUG subscription

2903 This parameter refers to the set of basic information for each CUG defined in that subscription. The following 2904 information is stored: 2905 2906 2907 2908

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

2909 7.6.3.24

CUG interlock

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

2911 7.6.3.25

CUG index

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

2913 7.6.3.26

CUG feature

2914 This parameter contains two parameters that are associated with the Basic Service Group. If the Basic Service Group 2915 Code is not present the feature applies to all Basic Services. The following parameters are included: 2916 2917 2918 2919 2920 2921

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.

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

2923 7.6.3.27

Inter CUG options

2924 This parameter indicates the subscribers' ability to make and receive calls outside a specific closed user group. It takes 2925 any of the following values: 2926 2927 2928 2929

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

2930 7.6.3.28

Intra CUG restrictions

298

3GPP

2931 This parameter describes whether or not the subscriber is allowed to originate calls to or to receive calls from within the 2932 CUG. It can take any of the following values: 2933 2934 2935

299 Release 6 300 301

76

3GPP TS 29.002 V6.11.0 (2005-09)

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

2936 7.6.3.29
SS-Code

Extensible SS-Data

2937 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 2938 2939 2940 2941 2942

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

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

2943 7.6.3.30

Subscriber State

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

2945 7.6.3.31

Requested Info

2946 This parameter indicates the subscriber information being requested as defined in 3GPP TS 23.018 [97] and 3GPP 2947 TS 23.078 [98].

2948 7.6.3.31A

Requested Domain

2949 This parameter indicates the domain (circuit switched, i.e. from the MSC/VLR, or packet switched, i.e. from the SGSN) 2950 from which the requested information should be retrieved.

2951 7.6.3.32

Suppression of Announcement

2952 This parameter indicates if the announcement or tones shall be suppressed as defined in 3GPP TS 23.078 [98].

2953 7.6.3.33

Suppress T-CSI

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

2955 7.6.3.34

GMSC CAMEL Subscription Info

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

2958 7.6.3.35

VLR CAMEL Subscription Info

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

2960 7.6.3.36

Supported CAMEL Phases in the VLR

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

302

3GPP

2962 7.6.3.36A

303 Release 6 304 305

77

3GPP TS 29.002 V6.11.0 (2005-09)

Supported CAMEL Phases in the SGSN

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

2964 7.6.3.36B

Offered CAMEL4 CSIs in the VLR

2965 This parameter indicates which CSIs of CAMEL phase 4 are offered in the VLR as defined in 3GPP TS 23.078.

2966 7.6.3.36C

Offered CAMEL4 CSIs in the SGSN

2967 This parameter indicates which CSIs of CAMEL phase 4 are offered in the SGSN as defined in 3GPP TS 23.078.

2968 7.6.3.36D

Offered CAMEL4 CSIs

2969 This parameter indicates which CSIs of CAMEL phase 4 are offered as defined in 3GPP TS 23.078.

2970 7.6.3.36E

Offered CAMEL4 CSIs in interrogating node

2971 This parameter indicates which CSIs of CAMEL phase 4 are offered in the GMSC or in the gsmSCF as defined in 2972 3GPP TS 23.078.

2973 7.6.3.36F

Offered CAMEL4 CSIs in VMSC

2974 This parameter indicates which CSIs of CAMEL phase 4 are offered in the VMSC as defined in 3GPP TS 23.078.

2975 7.6.3.36G 2976 7.6.3.36H

Offered CAMEL4 Functionalities Supported CAMEL Phases

2977 This parameter indicates which phases of CAMEL are supported as defined in 3GPP TS 23.078.

2978 7.6.3.36I

Supported CAMEL Phases in interrogating node

2979 This parameter indicates which phases of CAMEL are supported as defined in 3GPP TS 23.078. The interrogating node 2980 may be a GMSC or a gsmSCF. 2981 This parameter indicates which functionalities of CAMEL phase 4 are offered as defined in 3GPP TS 23.078.

2982 7.6.3.37

CUG Subscription Flag

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

2984 7.6.3.38

CAMEL Subscription Info Withdraw

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

2986 7.6.3.39

Voice Group Call Service (VGCS) Data

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

2988 7.6.3.40

Voice Broadcast Service (VBS) Data

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

2992 7.6.3.41

ISDN bearer capability

306

3GPP

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

307 Release 6 308 309

78

3GPP TS 29.002 V6.11.0 (2005-09)

2994 7.6.3.42

Lower layer Compatibility

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

2996 7.6.3.43

High Layer Compatibility

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

2998 7.6.3.44

Alerting Pattern

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

3001 7.6.3.45

GPRS Subscription Data Withdraw

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

3003 7.6.3.46

GPRS Subscription Data

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

3005 7.6.3.47

QoS-Subscribed

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

3007 7.6.3.48

VPLMN address allowed

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

3010 7.6.3.49

Roaming Restricted In SGSN Due To Unsupported Feature

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

3013 7.6.3.50

Network Access Mode

3014 This parameter is defined in 3GPP TS 23.108.

3015 7.6.3.51

Mobile Not Reachable Reason

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

3018 7.6.3.52

Cancellation Type

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

3020 7.6.3.53

All GPRS Data

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

3022 7.6.3.54

Complete Data List Included

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

310

3GPP

3025 7.6.3.55

311 Release 6 312 313

79

3GPP TS 29.002 V6.11.0 (2005-09)

PDP Context Identifier

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

3027 7.6.3.56

LSA Information

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

3031 7.6.3.57

SoLSA support indicator

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

3033 7.6.3.58

LSA Information Withdraw

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

3035 7.6.3.59

LMU Indicator

3036 This parameter indicates the presence of an LMU.

3037 7.6.3.60
-

LCS Information

3038 This parameter defines the LCS related information for an MS subscriber and contains the following components: 3039 3040 3041 3042 3043

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). (see clause 7.6.3.62A).

Additional LCS Privacy Exception List

3044 7.6.3.61

GMLC List

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

3047 7.6.3.62

LCS Privacy Exception List

3048 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 3049 information is provided: 3050 3051

SS-Code a list of LCS privacy exception parameters

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

3052 7.6.3.62A

Additional LCS Privacy Exception List

3053 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 3054 information is provided: 3055 3056

SS-Code a list of LCS privacy exception parameters

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

3057 The Additional LCS Privacy Exception List shall be present only if the LCS Privacy Exception List is present and 3058 contains LCS privacy exception parameters for 4 privacy exception classes.

314

3GPP

3059 7.6.3.63

315 Release 6 316 317

80

3GPP TS 29.002 V6.11.0 (2005-09)

LCS Privacy Exception Parameters

3060 This parameter gives the status of each LCS privacy exception class and any additional parameters relevant to this class. 3061 The parameter contains the following information: 3062 3063 3064 3065 3066 3067

provisioned SS-Status privacy notification to MS user external client List internal client List service type 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). (see clause 7.6.3.65D);

3068 7.6.3.64
3069 3070 3071 3072 3073 3074

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.

3075 7.6.3.65

Internal Client List

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

3079 7.6.3.65A

MO-LR List

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

SS-Code

(see clause 7.6.4.1).

3083 7.6.3.65B
3084 3085 3086 3087

Privacy Notification to MS User

This parameter is applicable to the call/session unrelated privacy class and call/session related privacy class. For noncall/call related privacy class it indicates whether the MS user shall be notified for that 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.

3088 7.6.3.65C

GMLC List Withdraw

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

3090 7.6.3.65D

Service Type List

3091 This parameter is only applicable to the Service type privacy class and gives the identities of the service type of the 3092 clients that are allowed to locate a target MS for an MT-LR. Usage of this parameter is defined in 3GPP TS 23.271.

3093 7.6.3.66

IST Alert Timer

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

318

3GPP

3096 7.6.3.67

319 Release 6 320 321

81

3GPP TS 29.002 V6.11.0 (2005-09)

Call Termination Indicator

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

3099 7.6.3.68

IST Information Withdraw

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

3101 7.6.3.69

IST Support Indicator

3102 This parameter indicates the degree of IST functionality supported by the MSC (Visited MSC or Gateway MSC). It can 3103 take one of the following values: 3104 3105 3106

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

3107 7.6.3.70

Super-Charger Supported In HLR

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

3110 7.6.3.71

Super-Charger Supported In Serving Network Entity

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

3113 7.6.3.72

Age Indicator

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

3116 7.6.3.73

GPRS enhancements support indicator

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

3118 7.6.3.74

Extension QoS-Subscribed

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

3121 7.6.3.75

SGSN CAMEL Subscription Info

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

3123 7.6.3.75A

Extension-2 QoS-Subscribed

3124 This parameter indicates the additional QoS information to the Extension QoS-subscribed parameter. It is a further 3125 extension to Extension QoS-Subscribed. This parameter shall be used when the maximum bit rate exceeds 8640 kbps. 3126 For more details, refer to 3GPP TS 24.008 [35].

3127 7.6.3.76

MO-SMS-CSI

3128 This parameter identifies the subscriber as having mobile originating SMS CAMEL services as defined in 3GPP TS 3129 23.078. For the CAMEL phase 3 the MO-SMS-CSI is the same as the SMS-CSI.

322

3GPP

3130 7.6.3.76a

323 Release 6 324 325

82

3GPP TS 29.002 V6.11.0 (2005-09)

MT-SMS-CSI

3131 This parameter identifies the subscriber as having mobile terminating SMS CAMEL services as defined in 3GPP TS 3132 23.078.

3133 7.6.3.77

GPRS-CSI

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

3135 7.6.3.78

CAMEL subscription info

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

3137 7.6.3.79
SS-Code;

Extensible Call barring information for CSE

3138 This parameter contains for each call barring service for CSE: 3139 3140 3141 3142 3143 3144

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

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

3145 7.6.3.80
-

Extensible Forwarding information for CSE

3146 This parameter represents the information for CSE related to each call forwarding service: 3147 3148 3149 3150

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.

3151 7.6.3.81

Modification Request for CSI

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

3153 7.6.3.81a

Modification Request for ODB data

3154 This parameter indicates the operator determined barring data to be modified by CSE.

3155 7.6.3.82

Modification Request for SS Information

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

3157 7.6.3.83

Call Barring Data

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

3159 7.6.3.84

Call Forwarding Data

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

326

3GPP

3161 7.6.3.85

327 Release 6 328 329

83

3GPP TS 29.002 V6.11.0 (2005-09)

ODB Data

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

3163 7.6.3.86

Requested Subscription Info

3164 This parameter indicates the subscription information being requested.

3165 7.6.3.87

CS Allocation/Retention priority

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

3168 7.6.3.88

ODB Info

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

3170 7.6.3.89

Suppress VT-CSI

3171 This parameter is used to suppress the invocation of terminating CAMEL services at the VMSC.

3172 7.6.3.90

Suppress Incoming Call Barring

3173 This parameter is used to suppress the invocation of Incoming Call Barrings.

3174 7.6.3.91

gsmSCF Initiated Call

3175 This parameter is used to indicate that the call was initiated by the gsmSCF.

3176 7.6.3.92

Call barring support indicator

3177 This parameter is used to indicate that the SGSN supports the call barring services for SMS.

3178 7.6.3.93

MNP Info Result

3179 This parameter refers to the Mobile Number Portability (MNP) information result (see 3GPP TS 23.078 [98] and 3GPP 3180 TS 23.066 [108]). This parameter may contain the following information: 3181 3182 3183 3184

Routeing Number IMSI MSISDN Number Portability Status

(see clause 7.6.2.63). (see 3GPP TS 23.078[98], see also clause 7.6.2.1). (see clause 7.6.2.17). (see clause 7.6.5.14).

3185 7.6.3.94

Allowed Services

3186 This parameter is used by the HLR to indicate which service is available for a call when two services have been 3187 requested, for the SCUDIF feature described in 3GPP TS 23.172 [126].

3188 7.6.3.95
3189 3190 3191

Unavailability Cause

This parameter is used to indicate the reason for the unavailability of one of the services as indicated by the Allowed Services IE (see 7.6.3.94) when two services have been requested, for the SCUDIF feature described in 3GPP TS 23.172 [126].

330

3GPP

3192 7.6.3.96

331 Release 6 332 333

84

3GPP TS 29.002 V6.11.0 (2005-09)

MNP Requested Info

3193 This parameter indicates by its presence that Mobile Number Portability (MNP) information is requested for the 3194 subscriber, as defined in 3GPP TS 23.078 [98].

3195 7.6.3.97

Access Restriction Data

3196 This parameter refers to the radio access technologies that are possibly restricted to a subscriber via subscription data. 3197 For the use of the parameter, see 3GPP TS 23.012[23] for CS domain and 3GPP TS 23.060[104] for PS domain.

3198 3199 7.6.4.1

7.6.4 Supplementary services parameters


SS-Code

3200 This parameter may refer to one supplementary service or a set of supplementary services as defined in 3GPP TS 3201 22.004. For MAP this includes: 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220

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, including Call Deflection; 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).

3221 7.6.4.1A

SS-Code 2

3222 This parameter is used to refer to one or a set of supplementary services (as 7.6.4.1 "SS-Code") related to Network 3223 Signal Info 2 for SCUDIF calls (see 3GPP TS 23.172 [126]).

334

3GPP

3224 7.6.4.2

335 Release 6 336 337

85

3GPP TS 29.002 V6.11.0 (2005-09)

SS-Status

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

3226 7.6.4.3
SS-Code

SS-Data

3227 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 3228 3229 3230 3231 3232

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

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

3233 7.6.4.4

Override Category

3234 This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the 3235 following two values: 3236 3237

Enabled; Disabled.

3238 7.6.4.5

CLI Restriction Option

3239 This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can 3240 take the following three values: 3241 3242 3243

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

3244 7.6.4.6

Forwarding Options

3245 This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following 3246 values: 3247 3248 3249 3250

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

3251 7.6.4.7

No reply condition timer

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

3253 7.6.4.8 - 7.6.4.14 Void 3254 7.6.4.15


-

Forwarding information

3255 This parameter represents the information related to each call forwarding service: 3256

the SS-Code of the relevant call forwarding service

(see clause 7.6.4.1);

338

3GPP

3257 3258

339 Release 6 340 341

86

3GPP TS 29.002 V6.11.0 (2005-09)

if required, a list of forwarding feature parameters the list may contain one item per Basic Service Group.

(see clause 7.6.4.16).

3259 7.6.4.16

Forwarding feature

3260 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 3261 following information, as required: 3262 3263 3264 3265 3266 3267 3268

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

3269 If a number is required to define the forwarded-to destination then: 3270 3271 3272 3273

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.

3274 7.6.4.17 3275 7.6.4.18


SS-Code

Void Call barring information


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

3276 This parameter contains for each call barring service: 3277 3278 3279

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

3280 7.6.4.19

Call barring feature

3281 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 3282 contains the following information: 3283 3284

Basic Service Group SS-Status

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

3285 7.6.4.20

New password

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

3288 7.6.4.21

Current password

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

342

3GPP

3290 7.6.4.22

343 Release 6 344 345

87

3GPP TS 29.002 V6.11.0 (2005-09)

Guidance information

3291 This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the 3292 following information may be given: 3293 3294 3295 3296 3297 3298

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

3299 7.6.4.23 3300 7.6.4.24


-

Void SS-Info
(see clause 7.6.4.15); (see clause 7.6.4.18); (see clause 7.6.4.8); (see clause 7.6.4.3). (see clause 7.6.4.41).

3301 This parameter refers to all the information related to a supplementary service and is a choice between: 3302 3303 3304 3305 3306

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

3307 7.6.4.25 - 7.6.4.35 Void 3308 7.6.4.36 USSD Data Coding Scheme

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

3312 7.6.4.37

USSD String

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

3316 7.6.4.38

Bearer service

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

3319 7,6,4.38A

Bearer Service 2

3320 This parameter is used to indicate the bearer service or set of bearer services (as 7.6.4.38 "Bearer service") related to 3321 Network Signal Info 2 for SCUDIF calls (see 3GPP TS 23.172 [126]).

3322 7.6.4.39

Teleservice

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

346

3GPP

3325 7.6.4.39A

347 Release 6 348 349

88

3GPP TS 29.002 V6.11.0 (2005-09)

Teleservice 2

3326 This parameter is used to indicate the teleservice or set of teleservices (as 7.6.4.39 "Teleservice") related to Network 3327 Signal Info 2 for SCUDIF calls (see 3GPP TS 23.172 [126]).

3328 7.6.4.40

Basic Service Group

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

3332 7.6.4.41

eMLPP information

3333 This parameter contains two parameters which are associated with the eMLPP service. The following two parameters 3334 are included: 3335 3336 3337 3338

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.

3339 7.6.4.42

SS-event

3340 This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It 3341 can indicate one of the following services: 3342 3343 3344 3345

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

3346 7.6.4.43

SS-event data

3347 This parameter contains additional information related to Supplementary Service invocation. Depending on the service 3348 invoked it can contain the following information: 3349 3350

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

3351 7.6.4.44
-

LCS Privacy Exceptions

3352 Distinct SS codes are assigned to the following classes of LCS client in a target MS subscribers privacy exception list. 3353 3354 3355 3356 3357 3358

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

3359 7.6.4.45

Mobile Originating Location Request (MO-LR)

350

3GPP

3360 Distinct SS codes are assigned to the following classes of MO-LR: 3361 3362 3363

351 Release 6 352 353

89

3GPP TS 29.002 V6.11.0 (2005-09)

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

3364 7.6.4.46

NbrUser

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

3367 7.6.4.47

MC Subscription Data

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

3370
3371 3372

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.

3373
3374

3375 7.6.4.48

MC Information

3376 This parameter contains three parameters which are associated with the MC service. The following parameters are 3377 included: 3378 3379 3380

NbrSB; NbrUser; NbrSN.

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

3382 7.6.4.49
request; recall; active;

CCBS Request State

3383 This parameter indicates the current state of the CCBS request. It can take one of seven values: 3384 3385 3386 3387 3388 3389 3390

completed; suspended; frozen; deleted.

354

3GPP

3391 7.6.4.50

355 Release 6 356 357

90

3GPP TS 29.002 V6.11.0 (2005-09)

Basic Service Group 2

3392 This parameter refers to the Basic Service Group either as a bearer service (see clause 7.6.4.38) or a teleservice (see 3393 clause 7.6.4.39). This parameter is used only for supplementary service management.

3394 3395 7.6.5.1

7.6.5 Call parameters


Call reference number

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

3397 7.6.5.2

Interrogation type

3398 This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can 3399 take either of two values: 3400 3401 3402

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.

3403 7.6.5.3

OR interrogation

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

3406 7.6.5.4

OR capability

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

3408 7.6.5.5
-

Forwarding reason

3409 This parameter indicates the reason for which the call is to be forwarded. It can take one of three values: 3410 3411 3412

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

3413 7.6.5.6

Forwarding interrogation required

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

3416 7.6.5.7

O-CSI

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

3418 7.6.5.7A

D-CSI

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

3420 7.6.5.7B

T-CSI

3421 This parameter identifies the subscriber as having terminating CAMEL services in the GMSC, as defined in 3GPP 3422 TS 23.078.

3423 7.6.5.7C

VT-CSI

358

3GPP

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

359 Release 6 360 361

91

3GPP TS 29.002 V6.11.0 (2005-09)

3426 7.6.5.7D

O-IM-CSI

3427 This parameter identifies the subscriber as having originating IP Multimedia Core Network CAMEL services as defined 3428 in 3GPP TS 23.278.

3429 7.6.5.7E

D-IM-CSI

3430 This parameter identifies the subscriber as having originating IP Multimedia Core Network CAMEL dialled services as 3431 defined in 3GPP TS 23.278.

3432 7.6.5.7F

VT-IM-CSI

3433 This parameter identifies the subscriber as having terminating IP Multimedia Core Network CAMEL services as 3434 defined in 3GPP TS 23.278.

3435 7.6.5.8 3436 7.6.5.9 3437 7.6.5.10 3438 7.6.5.11

Void Void Void CCBS Feature

3439 This parameter corresponds to the 'CCBS Description' parameter in 3GPP TS 23.093. It refers to the necessary set of 3440 information required in order to characterise a certain CCBS request. The parameter may contain the following 3441 information: 3442 3443 3444 3445

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

3446 7.6.5.12

UU Data

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

3448 7.6.5.13

UUS CF Interaction

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

3451 7.6.5.14

Number Portability Status

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

3453 7.6.5.15

Pre-paging supported

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

3455

7.6.6 Radio parameters

362

3GPP

3456 7.6.6.1 - 7.6.6.3 3457 7.6.6.4

363 Release 6 364 365

92

3GPP TS 29.002 V6.11.0 (2005-09)

Void

GERAN Classmark

3458 This information element is sent from one MSC to the other MSC in the signalling for inter MSC handover. It is used 3459 to convey information related to cell capabilities, as defined in 3GPP TS 48.008.

3460 7.6.6.5

BSSMAP Service Handover

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

3462 7.6.6.5A

BSSMAP Service Handover List

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

3466 7.6.6.6

RANAP Service Handover

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

3468 7.6.6.7

HO-Number Not Required

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

3470 7.6.6.8

Integrity Protection Information

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

3472 7.6.6.9

Encryption Information

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

3474 7.6.6.10

Radio Resource Information

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

3476 7.6.6.10A

Radio Resource List

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

3480 7.6.6.10B

Chosen Radio Resource Information

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

3482 7.6.6.11

Key Status

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

3484 7.6.6.12

Selected UMTS Algorithms

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

3487 7.6.6.13

Allowed GSM Algorithms

366

3GPP

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

367 Release 6 368 369

93

3GPP TS 29.002 V6.11.0 (2005-09)

3490 7.6.6.14

Allowed UMTS Algorithms

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

3493 7.6.6.15

Selected GSM Algorithm

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

3496 7.6.6.16

Iu-Currently Used Codec

3497 This parameter indicates the codec used at the Iu interface before handover.

3498 7.6.6.17

Iu-Supported Codecs List

3499 This parameter indicates the codecs supported by the UE and by MSC-A and the associated modes in priority order (the 3500 first entry being the highest priority codec). MSC-B uses this information to select the associated transcoder resources.

3501 7.6.6.17A

Iu-Available Codecs List

3502 This parameter indicates the codecs available at the Iu interface in MSC-B and the associated modes. MSC-A uses this 3503 information to decide whether a change to a different codec at the Iu interface is possible.

3504 7.6.6.18

Iu-Selected Codec

3505 When sent by MSC-B, this parameter indicates the codec selected by MSC-B for the Iu interface. When sent by MSC3506 A, this parameter indicates the codec to be used by MSC-B at the Iu interface.

3507 7.6.6.19

RAB Configuration Indicator

3508 This parameter indicates by its presence that MSC-A (or MSC-B in case of subsequent handover) has generated the 3509 RAB parameters according to the preferred codec (first entry in the Available Codecs List).

3510 7.6.6.20

UESBI-Iu

3511 This parameter refers to the UESBI-Iu (UE Specific Behaviour Information over the Iu interface) information element 3512 defined in 3GPP TS 25.413.

3513 7.6.6.21

Alternative Channel Type

3514 This parameter refers to the Channel Type information element defined in 3GPP TS 48.008 [49] for the alternative radio 3515 access bearer. This parameter is used for SCUDIF calls (see 3GPP TS 23.172 [126]).

3516 3517 7.6.7.1

7.6.7 Authentication parameters


Authentication set list

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

370

3GPP

3522 7.6.7.2

371 Release 6 372 373

94

3GPP TS 29.002 V6.11.0 (2005-09)

Rand

3523 This parameter represents a random number used for authentication.

3524 7.6.7.3

Sres

3525 This parameter represents the response to an authentication request.

3526 7.6.7.4

Kc

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

3528 7.6.7.5

Xres

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

3530 7.6.7.5A

Ck

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

3532 7.6.7.5B

Ik

3533 This parameter refers to the Integrity Key.

3534 7.6.7.5C

Autn

3535 This parameter refers to the Authentication Token.

3536 7.6.7.6

Cksn

3537 This parameter refers to a ciphering key sequence number.

3538 7.6.7.6A

Ksi

3539 This parameter refers to a key set identifier.

3540 7.6.7.6B

Auts

3541 This parameter refers to the resynchronisation token.

3542 7.6.7.7
-

Ciphering mode

3543 This parameter refers to the ciphering mode which is associated with a radio channel. It may take values as follows: 3544 3545

no encryption; identification of specific ciphering algorithm.

3546 7.6.7.8

Current Security Context

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

3549 7.6.7.9
-

Failure cause

3550 This parameter refers to an authentication failure which has occurred. It may take values as follows: 3551

wrong user response;

374

3GPP

3552

375 Release 6 376 377

95

3GPP TS 29.002 V6.11.0 (2005-09)

wrong network signature.

3553 7.6.7.10

Re-attempt

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

3556 7.6.7.11

Access Type

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

3560 3561 7.6.8.1

7.6.8 Short message parameters


SM-RP-DA

3562 This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be 3563 either of the following: 3564 3565 3566 3567 3568

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

3569 7.6.8.2

SM-RP-OA

3570 This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be 3571 either of the following: 3572 3573

MS-ISDN service centre address

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

3574 7.6.8.3
3575 3576 3577 3578

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

3579 7.6.8.4

SM-RP-UI

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

3581 7.6.8.5

SM-RP-PRI

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

3584 7.6.8.6
-

SM Delivery Outcome

3585 This parameter indicates the cause for setting the message waiting data. It can take one of the following values: 3586

Absent subscriber;

378

3GPP

3587 3588

379 Release 6 380 381

96

3GPP TS 29.002 V6.11.0 (2005-09)

MS memory capacity exceeded; Successful transfer.

3589 7.6.8.7

More Messages To Send

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

3591 7.6.8.8
-

Alert Reason

3592 This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values: 3593 3594

MS present; Memory Available.

3595 7.6.8.9

Absent Subscriber Diagnostic SM

3596 This parameter is used to indicate the reason why the subscriber is absent. For the values for this parameter see 3GPP 3597 TS 23.040.

3598 7.6.8.10

Alert Reason Indicator

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

3600 7.6.8.11

Additional SM Delivery Outcome

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

3603 7.6.8.12

Additional Absent Subscriber Diagnostic SM

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

3605 7.6.8.13

Delivery Outcome Indicator

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

3607 7.6.8.14

GPRS Node Indicator

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

3609 7.6.8.15

GPRS Support Indicator

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

3612 7.6.8.16

SM-RP-MTI

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

3616 7.6.8.17

SM-RP-SMEA

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

382

3GPP

3620

383 Release 6 384 385

97

3GPP TS 29.002 V6.11.0 (2005-09)

7.6.9 Access and signalling system related parameters


AN-apdu

3621 7.6.9.1
3622 3623 3624 3625

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

3626 7.6.9.2
-

CM service type

3627 This parameter identifies the service category being requested by the subscriber: 3628 3629 3630 3631 3632 3633 3634 3635

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.

3636 7.6.9.3
-

Access connection status

3637 This parameter represents the following access connection status information: 3638 3639 3640

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

3641 7.6.9.4

External Signal Information

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

3645 7.6.9.5

Access signalling information

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

3647 7.6.9.6

Location update type

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

3650 7.6.9.7

Protocol ID

3651 This parameter refers to the protocol to which the coding of the content of the associated External Signal Information 3652 conforms.

386

3GPP

3653 The following values are defined: 3654 3655 3656

387 Release 6 388 389

98

3GPP TS 29.002 V6.11.0 (2005-09)

04.08; 08.06; ETS 300 102-1.

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

3658 7.6.9.8

Network signal information

3659 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1". 3660 The network signal information may include the following information elements as defined in 3GPP TS 29.007 [56]: 3661 3662 3663 3664 3665 3666

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

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

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

3668
3669

Figure 7.6/1: Network signal information parameter

3670 7.6.9.8A

Network signal information 2

3671 This parameter is transported as additional external signal information for SCUDIF calls, described in 3GPP TS 23.172 3672 [126]. The protocol ID and possibly included information elements are identical to Network Signal Information, defined 3673 in 7.6.9.8, "Network signal information".

3674 7.6.9.9

Call Info

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

390

3GPP

3678 7.6.9.10

391 Release 6 392 393

99

3GPP TS 29.002 V6.11.0 (2005-09)

Additional signal info

3679 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 356". 3680 The additional signal information may include the following information elements: 3681 3682

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

3683 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

3684
3685

LENGTH CONTENT
Figure 7.6/2: Additional signal information parameter

3686 3687 7.6.10.1


-

7.6.10 System operations parameters


Network resources

3688 This parameter refers to a class or type of network resource: 3689 3690 3691 3692 3693 3694

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

3695 7.6.10.2

Trace reference

3696 This parameter represents a reference associated with a GSM only tracing request as defined in 3GPP TS 52.008 [61]. 3697 The parameter is managed by OMC/EM.

3698 7.6.10.2A

Trace reference 2

3699 This parameter represents a reference associated with a tracing request as defined in 3GPP TS 32.421 [131] and 3GPP 3700 TS 32.422 [132]. The parameter is managed by EM.

3701 7.6.10.3

Trace type

3702 This parameter identifies the type of trace for GSM only tracing request. Trace types are fully defined in 3GPP 3703 TS 52.008 [61]. If the activation of the tracing is requested only for UMTS, then this parameter shall contain value "No 3704 MSC Trace" for MSC Record Type and value "No BSS Trace" for BSS Record Type.

3705 7.6.10.4

Additional network resources

394

3GPP

3706 This parameter refers to a class or type of network resource: 3707 3708 3709 3710 3711 3712

395 Release 6 396 397

100

3GPP TS 29.002 V6.11.0 (2005-09)

-SGSN; -GGSN; -GMLC; -gsmSCF; -NPLR; -AuC.

3713 7.6.10.5

Trace depth list

3714 This parameter identifies the list of depths of trace per network element. See 3GPP TS 32.422 [132].

3715 7.6.10.6

Trace NE type list

3716 This parameter identifies the list of network elements to be traced. See 3GPP TS 32.422 [132].

3717 7.6.10.7

Trace interface list

3718 This parameter identifies the list of interfaces or protocols per network element to be traced. See 3GPP TS 32.422 3719 [132].

3720 7.6.10.X

Trace event list

3721 This parameter identifies the list of events per network element, which trigger a Trace Recording Session. See 3GPP TS 3722 32.422 [132].

3723 7.6.10.X

Trace support indicator

3724 This parameter indicates that UMTS trace parameters are supported in the VLR or in the SGSN.

3725 3726 7.6.11.1

7.6.11 Location Service Parameters


Age of Location Estimate

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

3728 7.6.11.2

Deferred MT-LR Response Indicator

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

3730 7.6.11.3
3731 3732 3733 3734 3735 3736 3737 3738

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.

3739 7.6.11.4

LCS Client ID

398

3GPP

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

399 Release 6 400 401

101

3GPP TS 29.002 V6.11.0 (2005-09)

3741 7.6.11.5
3743 7.6.11.6

LCS Event

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

Void

3744 7.6.11.7

LCS Priority

3745 This parameter gives the priority of the location request.

3746 7.6.11.8

LCS QoS

3747 This parameter defines the Quality of Service (QoS) for any location request. It is composed of the following elements. 3748 3749 3750 3751 3752 3753 3754 3755

1) Response Time Indicates the category of response time low delay or delay tolerant. 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).

3756 7.6.11.9

CS LCS Not Supported by UE

3757 This parameter is used by the VLR to indicate to the HLR that the UE does not support 3758 neither UE Based nor UE Assisted positioning metheds for Circuit Switched 3759 Location Services. VLR defines the presence of this parameter on the basis 3760 of the Classmark 3 information. 3761 7.6.11.10 PS LCS Not Supported by UE

3762 This parameter is used by the SGSN to indicate to the HLR that the UE does not support neither UE Based nor UE 3763 Assisted positioning metheds for Packet Switched Location Services. SGSN defines the presence of this parameter on 3764 the basis of the UE capability information and the access technology supported by the SGSN.

3765 7.6.11.11
3766 3767 3768 3769 3770 3771 3772 3773 3774

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

402

3GPP

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

403 Release 6 404 405

102

3GPP TS 29.002 V6.11.0 (2005-09)

3777 7.6.11.11A

GERAN Positioning Data

3778 This parameter provides positioning data associated with a successful or unsuccessful location attempt for a target MS 3779 described in 3GPP TS 49.031 [59a].

3780 7.6.11.11B

UTRAN Positioning Data

3781 This parameter provides positioning data associated with a successful location attempt for a target MS as described in 3782 3GPP TS 25.413 [120]. It contains the positioningDataDiscriminator and positioningDataSet parts of the RANAP 3783 PositionData element only.

3784 7.6.11.12

Location Type

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

3787 3788 3789 3790

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

3791 7.6.11.13

NA-ESRD

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

3794 7.6.11.14

NA-ESRK

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

3797 7.6.11.15

LCS Service Type Id

3798 This parameter defines the LCS Service Type of the current positioning request. The possible values are defined in 3799 3GPP TS 22.071 [123]

3800 7.6.11.16

Privacy Override

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

3803 7.6.11.17

Supported LCS Capability Sets

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

3805 7.6.11.18

LCS Codeword

3806 This parameter contains the codeword associated to current positioning request as described in 3GPP TS 23.271 [26a].

3807 7.6.11.19

NA-ESRK Request

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

406

3GPP

3810 7.6.11.20

407 Release 6 408 409

103

3GPP TS 29.002 V6.11.0 (2005-09)

Supported GAD Shapes

3811 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. If the parameter is not provided 3812 then the receiving node shall assume that the sending entity supports the following shapes: 3813 3814 3815 3816 3817

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

3818 7.6.11.21

Additional Location Estimate

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

3822 7.6.11.22

Cell Id Or SAI

3823 For GERAN access, this parameter contains the Global Cell Identifier for the cell that the subscriber is currently 3824 attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is 3825 currently attached to.

3826 7.6.11.23

LCS-Reference Number

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

3829 7.6.11.24

LCS Privacy Check

3830 This parameter refers to the requested privacy check related actions (call/session unrelated and/or call/session related) 3831 from MSC or SGSN provided by H-GMLC. Possible requested actions are:

3832 3833 3834 3835

positioning allowed without notifying the UE user; positioning allowed with notification to the UE user; positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user; positioning not allowed.

3836 3837

3838 -

3839 7.6.11.25

Additional LCS Capability Sets

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

3841 7.6.11.26

Area Event Info

3842 This parameter defines the requested deferred MT-LR area event information. The parameter consists of 3843 area definition, type of area event, occurrence info and minimum interval time.

3844 7.6.11.27

Accuracy Fulfilment Indicator

410

3GPP

3845 This parameter indicates the fulfilled accuracy of the positioning procedure. For details see 3GPP TS 23.271 3846 [26a].

411 Release 6 412 413

104

3GPP TS 29.002 V6.11.0 (2005-09)

3847 3848 7.6.12.1

7.6.12 Secure Transport Parameters


Security Header

3849 This parameter carries the security header information, which is required by a receiving entity in order to extract the 3850 protected information from a securely transported MAP message. The components of the security header are shown in 3851 table 7.6.12/1. 3852 See 3GPP TS 33.200 for the use of these parameters. 3853
Component name

Table 7.6.12/1: Components of the Security Header


Presence requirement Description

Security Parameters Index Original component identifier

M M

TVP NE-Id Prop

O O O

Identifies the Security Association for the component. Identifies the type of component to be securely transported one of: - Operation, identified by the operation code; - Error, defined by the error code; - User information. A parameter based on time that is used to ensure the current message is fresh. This is only present if required for the current Protection Mode. The identity of the Network Element sending the message. This is only present if required for the current Protection Mode. Bytes used to ensure the IV is unique for a given TVP and NE-Id. This is only present if required for the current Protection Mode.

3854 3855

3856 3857

7.7 Representation of a list of a basic parameter in serviceprimitives

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

ParameterNameLIST

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

3863
3864

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

3865

8 Mobility services

414

3GPP

415 Release 6 416 417

105

3GPP TS 29.002 V6.11.0 (2005-09)

3866 3867 3868 8.1.1.1 3869 8.1.1.2 3870 8.1.1.3 3871 3872 8.1.2.1

8.1 Location management services


8.1.1 Void
Void Void Void

8.1.2 MAP_UPDATE_LOCATION service


Definition

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

3875 8.1.2.2
3876

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 Offered CAMEL 4 CSIs Inform Previous Network Entity CS LCS Not Supported by UE V-GMLC Address IMEISV Skip Subscriber Data Update ADD Capability HLR number User error Provider error

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

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

Response M(=)

Confirm M(=)

U C C

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

3877

3878 8.1.2.3
3879 Invoke Id

Parameter definitions and use

3880 See definition in clause 7.6.1. 3881 IMSI 3882 See definition in clause 7.6.2. 3883 MSC Address

418

3GPP

3884 See definition for MSC number in clause 7.6.2. The MSC address is used for short message delivery only and for each 3885 incoming call set-up attempt the MSRN will be requested from the VLR. 3886 VLR number 3887 See definition in clause 7.6.2. 3888 LMSI 3889 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 3890 to support the LMSI handling procedures. 3891 Supported CAMEL Phases 3892 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 3893 phase 1 is supported. Otherwise may be absent. 3894 HLR number 3895 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3896 SoLSA Support Indicator 3897 3898 3899 3900

419 Release 6 420 421

106

3GPP TS 29.002 V6.11.0 (2005-09)

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.

3901 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 3902 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 3903 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 3904 IST Support Indicator 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915

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.

3916 Long FTN Supported 3917 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 3918 Super-Charger Supported in Serving Network Entity 3919 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 3920 whether subscription data has been retained by the VLR. If subscription data has been retained by the VLR the age 3921 indicator shall be included. Otherwise the VLR shall indicate that subscriber data is required. 3922 If this parameter is absent then the VLR does not support the Super-Charger functionality. 3923 Supported LCS Capability Sets 3924 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 3925 capability set is marked as supported then the VLR does not support LCS at all. 3926 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 3927 version.

422

3GPP

3928 Offered CAMEL 4 CSIs 3929 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D). 3930 Inform Previous Network Entity

423 Release 6 424 425

107

3GPP TS 29.002 V6.11.0 (2005-09)

3931 3932 3933 3934

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.

3935 CS LCS Not Supported by UE 3936 See definition in clause 7.6.11. 3937 V-GMLC address 3938 See definition in clause 7.6.2. 3939 IMEISV 3940 For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.012. IMEISV shall be 3941 present if ADD function is supported and a new IMEISV is to be notified to the HLR (The functional requirements for 3942 the presence of IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4). 3943 Skip Subscriber Data Update 3944 The presence of the parameter is optional and if present it indicates that the service is solely used to inform the HLR 3945 about change of IMEISV. The parameter is used to optimise signalling load during Location Update procedure. 3946 ADD Capability 3947 This parameter indicates, if present, the support of ADD function by the HLR. 3948 User error 3949 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3950 clause 7.6.1 may be used, depending on the nature of the fault: 3951 3952 3953 3954 3955 3956 3957

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.

3958 Provider error 3959 For definition of provider errors see clause 7.6.1.

3960 3961 8.1.3.1

8.1.3 MAP_CANCEL_LOCATION service


Definition

3962 This service is used between HLR and VLR to delete a subscriber record from the VLR. It may be invoked 3963 automatically when an MS moves from one VLR area to another, to remove the subscriber record from the old VLR, or 3964 by the HLR operator to enforce a location updating from the VLR to the HLR, e.g. on withdrawal of a subscription.

426

3GPP

3965 Also this service is used between HLR and SGSN to delete a subscriber record from the SGSN. It may be invoked 3966 automatically when an MS moves from one SGSN area to another, to remove the subscriber record from the old SGSN, 3967 or by the HLR operator to enforce a location updating from the SGSN to the HLR. 3968 The MAP_CANCEL_LOCATION service is a confirmed service using the primitives defined in table 8.1/3.

427 Release 6 428 429

108

3GPP TS 29.002 V6.11.0 (2005-09)

3969 8.1.3.2
3970

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

3971

3972 8.1.3.3
3973 Invoke Id

Parameter definitions and use

3974 See definition in clause 7.6.1. 3975 IMSI 3976 See definition in clause 7.6.2. 3977 LMSI 3978 See definition in clause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable 3979 between SGSN and HLR. 3980 Value 0000 0000 can be used to indicate that the LMSI is not in use. 3981 Cancellation Type 3982 See definition in clause 7.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the 3983 SGSN. If the VLR receives this parameter and do not understand it the VLR shall ignore it. 3984 User error 3985 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. One of the following error causes 3986 defined in clause 7.6.1 shall be used: 3987 3988

unexpected data value; data missing.

3989 Provider error 3990 For definition of provider errors see clause 7.6.1.

3991 3992 8.1.4.1

8.1.4 MAP_SEND_IDENTIFICATION service


Definition

3993 The MAP_SEND_IDENTIFICATION service is used between a VLR and a previous VLR to retrieve IMSI and 3994 authentication data for a subscriber registering afresh in that VLR. 3995 It may also be used to send the MSC number from a VLR to a previous VLR. 3996 The MAP_SEND_IDENTIFICATION service is a confirmed service using the service primitives defined in table 8.1/4.

430

3GPP

3997 8.1.4.2
3998

431 Release 6 432 433

109

3GPP TS 29.002 V6.11.0 (2005-09)

Service primitives
Table 8.1/4: MAP_SEND_IDENTIFICATION

Parameter name Invoke Id TMSI Number of requested vectors Segmentation prohibited indicator MSC Number Previous Location Area Id Hop Counter IMSI Authentication set Current Security Context User error Provider error

Request M M M C U U U

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

Response M(=)

Confirm M(=)

C U U C

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

3999

4000 8.1.4.3
4001 Invoke Id

Parameter definitions and use

4002 See definition in clause 7.6.1. 4003 TMSI 4004 See definition in clause 7.6.2. 4005 If multiple service requests are present in a dialogue then this parameter shall be present in every service request. 4006 Number of requested vectors 4007 A number indicating how many authentication vectors the new VLR is prepared to receive. The previous VLR shall not 4008 return more vectors than indicated by this parameter. 4009 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4010 dialogue then this parameter shall not be present in any service request other than the first one 4011 Segmentation prohibited indicator 4012 This parameter indicates if the new VLR or SGSN allows segmentation of the response at MAP user level. 4013 This parameter may be present only in the first request of the dialogue. 4014 IMSI 4015 See definition in clause 7.6.2. The IMSI is to be returned if the service succeeds. 4016 If multiple service requests are present in a dialogue and the service succeeds then this parameter shall not be present in 4017 any service response other than the first one 4018 MSC Number 4019 This is the ISDN number assigned to the MSC currently serving the MS. 4020 Previous Location Area Id 4021 See definition in clause 7.6.2. Together with the TMSI the Previous Location Area Id can be used to derive the IMSI. 4022 Authentication set 4023 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 4024 available. 4025 Current Security Context

434

3GPP

4026 See definition in clause 7.6.7. If the service succeeds, a list of either GSM or UMTS Security Context parameters can be 4027 returned. 4028 Hop Counter 4029 For the use of this parameter see 3GPP TS 23.012 [23]. 4030 User error 4031 This parameter is mandatory if the service fails. The following error cause defined in clause 7.6.1 may be used, 4032 depending on the nature of the fault: 4033

435 Release 6 436 437

110

3GPP TS 29.002 V6.11.0 (2005-09)

unidentified subscriber.

4034 Provider error 4035 For definition of provider errors see clause 7.6.1.

4036 4037 8.1.5.1 4038 8.1.5.2 4039 8.1.5.3 4040 4041 8.1.6.1
4042 4043 4044 4045 4046 4047 4048 4049 4050 4051

8.1.5 Void
Void Void Void

8.1.6 MAP_PURGE_MS service


Definition

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

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

4053 8.1.6.2
4054

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

4055

4056 8.1.6.3

Parameter definitions and use

438

3GPP

4057 Invoke ID

439 Release 6 440 441

111

3GPP TS 29.002 V6.11.0 (2005-09)

4058 See definition in clause 7.6.1. 4059 IMSI 4060 See definition in clause 7.6.2. 4061 VLR number 4062 Shall be present if the sender is VLR. See definition in clause 7.6.2. 4063 SGSN number 4064 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 4065 Freeze TMSI 4066 This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR 4067 number matches the stored VLR number. 4068 Freeze P-TMSI 4069 This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received 4070 SGSN number matches the stored SGSN number. 4071 User error 4072 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4073 4074 4075

Data Missing; Unexpected Data Value; Unknown Subscriber.

4076 Provider error 4077 See definition of provider errors in clause 7.6.1.

4078 4079 8.1.7.1

8.1.7 MAP_UPDATE_GPRS_LOCATION service


Definition

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

4083 8.1.7.2
4084

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 Offered CAMEL 4 CSIs Inform Previous Network Entity

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

Confirm M(=)

442

3GPP

443 Release 6 444 445

112 Request C U C C U

3GPP TS 29.002 V6.11.0 (2005-09) Indication C(=) C(=) C(=) C(=) C(=) Response Confirm

Parameter name PS LCS Not Supported by UE V-GMLC Address Call barring support indicator IMEISV Skip Subscriber Data Update ADD Capability HLR number User error Provider error

U C C

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

4085

4086 8.1.7.3
4087 Invoke Id

Parameter definitions and use

4088 See definition in clause 7.6.1. 4089 IMSI 4090 See definition in clause 7.6.2. 4091 SGSN number 4092 See definition in clause 7.6.2. 4093 SGSN address 4094 See definition in clause 7.6.2. 4095 Supported CAMEL Phases 4096 This parameter indicates which phases of CAMEL are supported. The SGSN can only support CAMEL phase 3 or 4097 greater. 4098 SoLSA Support Indicator 4099 4100 4101 4102

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

4103 This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a 4104 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support 4105 indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted. 4106 Super-Charger Supported in Serving Network Entity 4107 This parameter is used by the SGSN to indicate to the HLR that the SGSN supports the Super-Charger functionality and 4108 whether subscription data has been retained by the SGSN. If subscription data has been retained by the SGSN the age 4109 indicator shall be included. Otherwise the SGSN shall indicate that subscriber data is required. 4110 If this parameter is absent then the SGSN does not support the Super-Charger functionality. 4111 GPRS enhancements support indicator 4112 4113 4114 4115

This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that GPRS enhancements are supported. If this parameter is included in the Update GPRS Location indication the HLR may send the extension QoS parameter in the PDP contexts to the SGSN. The HLR may send the extension-2 QoS parameter with the extension QoS parameter.

4116 HLR number 4117 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 4118 Supported LCS Capability Sets

446

3GPP

4119 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 4120 capability set is marked as supported then the SGSN does not support LCS at all. 4121 The SGSN is not allowed to indicate support for LCS capability set 1. 4122 If this parameter is absent then the SGSN does not support LCS at all. 4123 Offered CAMEL 4 CSIs 4124 This parameter indicates the CAMEL phase 4 CSIs offered in the SGSN (see clause 7.6.3.36D). 4125 Inform Previous Network Entity

447 Release 6 448 449

113

3GPP TS 29.002 V6.11.0 (2005-09)

4126 4127 4128 4129

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.

4130 PS LCS Not Supported by UE 4131 See definition in clause 7.6.11. 4132 V-GMLC address 4133 See definition in clause 7.6.2. 4134 Call Barring support indicator 4135 See definition in clause 7.6.3.92. 4136 IMEISV 4137 For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.060. IMEISV shall be 4138 present if ADD function is supported and the IMEISV is new in SGSN (The functional requirements for the presence of 4139 IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4). 4140 Skip Subscriber Data Update 4141 The presence of the parameter is optional and if present it indicates that the service is solely used to inform the HLR 4142 about change of IMEISV. The parameter is used to optimise signalling load during Location Update procedure. 4143 ADD Capability 4144 This parameter indicates, if present, the support of ADD function by the HLR. 4145 User error 4146 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 4147 clause 7.6.1 may be used, depending on the nature of the fault: 4148 4149 4150 4151 4152 4153 4154

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.

4155 Provider error 4156 For definition of provider errors see clause 7.6.1.

450

3GPP

4157

451 Release 6 452 453

114

3GPP TS 29.002 V6.11.0 (2005-09)

8.1.8 MAP-NOTE-MM-EVENT
Definition

4158 8.1.8.1

4159 This service is used between the VLR and the gsmSCF or between the SGSN and the gsmSCF when a mobility 4160 management event for a subscriber has been processed successfully, that subscriber is provisioned with M-CSI or MG4161 CSI and the relevant mobility management event is marked for reporting. 4162 4163 4164 4165

This service is also used between the VLR and the Presence Network Agent or between the SGSN and the Presence Network Agent to notify the Presence Network Agent when a mobility management event for a subscriber has been processed successfully, that subscriber is provisioned with M-CSI or MG-CSI and the relevant mobility management event is marked for reporting (see 3GPP TS 23.141 [128]).

4166 8.1.8.2

Service primitives

4167 The service primitives are shown in table 8.1/8. 4168

Table 8.1/8: MAP_NOTE_MM_EVENT parameters


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

C(=) O

4169

4170 8.1.8.3

Parameter use

4171 Event Met 4172 This parameter indicates the mobility management event that has lead to the notification. It shall have one of the 4173 following values for a mobility management event reported by the VLR: 4174 4175 4176 4177 4178

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

4179 It shall have one of the following values for a mobility management event reported by the SGSN: 4180 4181 4182 4183 4184 4185

Routeing area update in the same SGSN service area; Routeing area update to another SGSN service area; GPRS attach; MS initiated GPRS detach; Network initiated GPRS detach; Network initiated transfer to the "not reachable for paging" state.

454

3GPP

4186 Service Key 4187 See clause 7.6.x. 4188 IMSI 4189 See clause 7.6.x. 4190 Basic MSISDN 4191 See clause 7.6.x. 4192 Location Information 4193 See clause 7.6.2.30. This information shall be sent when the event is reported by a VLR, if available. 4194 Location Information for GPRS 4195 See clause 7.6.2.30a. This information shall be sent when the event is reported by an SGSN, if available. 4196 LSA Identity 4197 See clause 7.6.x. This information shall be sent, if available. 4198 Supported CAMEL Phases 4199 See clause 7.6.x. This information shall always be sent. 4200 Offered CAMEL 4 Functionalities 4201 This parameter indicates the CAMEL phase 4 functionalities offered by the sending entity, VMSC/VLR or SGSN (see 4202 clause 7.6.3.36G). 4203 User error 4204 This parameter is sent by the receiving entity when an error is detected. It shall have one of the following values: 4205 4206 4207 4208

455 Release 6 456 457

115

3GPP TS 29.002 V6.11.0 (2005-09)

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

4209 Provider error 4210 This is defined in clause 7.6.1.

4211 4212 4213 8.2.1.1

8.2 Paging and search


8.2.1 MAP_PAGE service
Definition

4214 This service is used between VLR and MSC to initiate paging of an MS for mobile terminated short message or 4215 unstructured SS notification. 4216 The MAP_PAGE service is a confirmed service using the primitives from table 8.2/1.

4217 8.2.1.2
4218

Service primitives
Table 8.2/1: MAP_PAGE

458

3GPP

459 Release 6 460 461

116 Parameter name Invoke Id IMSI Stored location area Id TMSI User error Provider error Request M M M U Indication M(=) M(=) M(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09) Response M(=) Confirm M(=)

C(=) O

4219

4220 8.2.1.3
4221 Invoke Id

Parameter definitions and use

4222 See definition in clause 7.6.1. 4223 IMSI 4224 See definition in clause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging on 4225 the radio path uses the IMSI as an identifier. 4226 Stored location area Id 4227 See definition in clause 7.6.2. 4228 TMSI 4229 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. 4230 User error 4231 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 4232 failure reason: 4233 4234 4235 4236 4237 4238 4239

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.

4240 Provider error 4241 See definition in clause 7.6.1.

4242 4243 8.2.2.1

8.2.2 MAP_SEARCH_FOR_MS service


Definition

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

4247 8.2.2.2
4248

Service primitives
Table 8.2/2: MAP_SEARCH_FOR_MS
Parameter name Request Indication Response Confirm

462

3GPP

463 Release 6 464 465

117 Invoke Id IMSI Current location area Id User error Provider error M M M(=) M(=)

3GPP TS 29.002 V6.11.0 (2005-09) M(=) C C M(=) C(=) C(=) O

4249

4250 8.2.2.3
4251 Invoke Id

Parameter definitions and use

4252 See definition in clause 7.6.1. 4253 IMSI 4254 See definition in clause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path. 4255 Current location area Id 4256 See definition in clause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the 4257 Location Area Id of the area in which the MS responded is given in the response. 4258 User error 4259 The following error causes defined in clause 7.6.1 shall be sent by the user if the search procedure fails, depending on 4260 the failure reason: 4261 4262 4263 4264 4265 4266 4267

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

system failure; this corresponds to the case where there is no call associated with the MAP_SEARCH_FOR_MS service, i.e. if the call has been released but the dialogue to the VLR has not been aborted; busy subscriber; unexpected data value.

4268 Provider error 4269 See definition in clause 7.6.1.

4270 4271 4272 8.3.1.1

8.3 Access management services


8.3.1 MAP_PROCESS_ACCESS_REQUEST service
Definition

4273 This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. for mobile 4274 originated short message submission or after being paged by the network. 4275 The MAP_PROCESS_ACCESS_REQUEST service is a confirmed service using the primitives from table 8.3/1.

4276 8.3.1.2
4277

Service primitives
Table 8.3/1: MAP_PROCESS_ACCESS_REQUEST
Parameter name Invoke Id CM service type Request M M Indication M(=) M(=) Response M(=) Confirm M(=)

466

3GPP

467 Release 6 468 469 Access connection status Current Location Area Id Serving cell Id TMSI Cksn IMSI IMEI MSISDN User error Provider error

118 M M M C C C C M(=) M(=) M(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09)

C C U C

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

4278

4279 8.3.1.3
4280 Invoke Id

Parameter definitions and use

4281 See definition in clause 7.6.1. 4282 CM service type 4283 See definition in clause 7.6.9. 4284 Access connection status 4285 See definition in clause 7.6.9. 4286 Current Location Area Id 4287 See definition in clause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure. 4288 Serving cell Id 4289 See definition in clause 7.6.2. 4290 TMSI 4291 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 4292 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 4293 Cksn 4294 See definition in clause 7.6.7. In case of access with TMSI, the Cksn shall be present. 4295 IMSI 4296 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 4297 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 4298 In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM 4299 Service Type "Emergency Call Establishment", IMEI may replace IMSI. 4300 IMEI 4301 See definition in clause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the 4302 Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment". 4303 MSISDN 4304 See definition in clause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator 4305 option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding. 4306 User error 4307 One of the following error causes defined in clause 7.6.1 shall be sent by the user if the access request fails, depending 4308 on the failure reason:

470

3GPP

4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320

471 Release 6 472 473

119

3GPP TS 29.002 V6.11.0 (2005-09)

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.

4321 Provider error 4322 For definition of provider errors see clause 7.6.1.

4323

8.4 Handover services

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

4327 4328 8.4.1.1

8.4.1 MAP_PREPARE_HANDOVER service


Definition

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

4332 8.4.1.2
4333

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 GERAN Classmark BSSMAP Service Handover BSSMAP Service Handover List Request M 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(=) Response M(=) Confirm M(=)

C(=)

474

3GPP

475 Release 6 476 477 RANAP Service Handover Iu-Currently Used Codec Iu-Supported Codecs List RAB Configuration Indicator ASCI Call Reference UESBI-Iu IMEISV Alternative Channel Type Handover Number Relocation Number List Multicall Bearer Information Multiple Bearer Requested Multiple Bearer Not Supported Selected UMTS Algorithms Chosen Radio Resource Information Iu-Selected Codec Iu-Available Codecs List User error Provider error

120 C C C C C C C C C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09)

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

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

4334

4335 8.4.1.3
4336 Invoke Id

Parameter use

4337 For definition of this parameter see clause 7.6.1. 4338 Target Cell Id 4339 For definition of this parameter see clause 7.6.2. This parameter is only included if the service is not in an ongoing 4340 transaction. This parameter shall also be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure 4341 or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009. 4342 Target RNC Id 4343 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter4344 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4345 23.009. 4346 HO-Number Not Required 4347 For definition of this parameter see clause 7.6.6. 4348 IMSI 4349 For definition of this parameter see clause 7.6.2. This UMTS parameter shall be included if:

4350 4351 4352

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

4353 Integrity Protection Information 4354 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 4355 network protocol is BSSAP. 4356 Encryption Information 4357 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 4358 network protocol is BSSAP. 4359 Radio Resource Information

478

3GPP

4360 For definition of this parameter see clause 7.6.6. This GSM parameter shall be included if the access network protocol 4361 is RANAP and there is an indication that the UE also supports GSM. If the parameter Radio Resource List is sent , the 4362 parameter Radio Resource Information shall not be sent. 4363 AN-APDU 4364 For definition of this parameter see clause 7.6.9. 4365 Allowed GSM Algorithms 4366 For definition of this parameter see clause 7.6.6. This parameters includes allowed GSM algorithms. This GSM 4367 parameter shall be included if:

479 Release 6 480 481

121

3GPP TS 29.002 V6.11.0 (2005-09)

4368 4369 4370

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.

4371 Allowed UMTS Algorithms 4372 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if all of the following 4373 conditions apply:

4374 4375

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

4376 Ciphering or Security Mode Setting procedure has been performed. 4377 Radio Resource List 4378 4379 4380 4381

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.

4382 RAB ID 4383 For definition of this parameter see subclause 7.6.2. This parameter shall be included when MSC-A supports multiple 4384 bearers and access network protocol is BSSAP and the RAB ID has a value other than 1. 4385 GERAN Classmark 4386 For definition of this parameter see subclause 7.6.6 This parameter shall be included if available. 4387 BSSMAP Service Handover 4388 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4389 RANAP. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not 4390 be sent. 4391 BSSMAP Service Handover List 4392 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4393 RANAP. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter BSSMAP 4394 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4395 RANAP Service Handover 4396 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4397 BSSAP. 4398 Iu-Currently Used Codec

482

3GPP

4399 For definition of this parameter see subclause 7.6.6. This parameter shall be included if the handover is requested for a 4400 speech bearer and the MS is in UMTS or GERAN Iu-mode access. This parameter shall not be included if the Iu4401 Supported Codecs List is not included. 4402 Iu-Supported Codecs List 4403 For definition of this parameter see subclause 7.6.6. This parameter shall be included by MSC-A, if the handover is 4404 requested for a speech bearer. 4405 RAB Configuration Indicator 4406 For definition of this parameter see subclause 7.6.6. This parameter may be included if the handover is requested for a 4407 speech bearer and MSC-A knows by means of configuration information that MSC-B supports the use of the Iu4408 Supported Codecs List parameter. This parameter shall not be included if the Iu-Supported Codecs List is not included. 4409 ASCI Call Reference 4410 This parameter contains either the broadcast call reference or group call reference. It shall be included if a subscriber is 4411 undergoing handover during a VGCS or VBS call, where MSC-B already has a Bearer established, so that MSC-B can 4412 determine the Group or Broadcast Call to which it shall attach the subscriber, see 3GPP TS 48.008 [49]. 4413 4414 UESBI-Iu 4415 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4416 BSSAP. 4417 IMEISV 4418 For definition of the parameter see clause 7.6.2. This parameter is used for Management based Trace Activation (see 4419 3GPP TS 32.422) and shall be present, if available. 4420 Alternative Channel Type 4421 For definition of this parameter see clause 7.6.6 It shall be present for a SCUDIF call if the access network protocol is 4422 BSSAP. 4423 Handover Number 4424 For definition of this parameter see clause 7.6.2. This parameter shall be returned at handover, unless the parameter 4425 HO-NumberNotRequired is sent. If the parameter Handover Number is returned, the parameter Relocation Number List 4426 shall not be returned. 4427 Relocation Number List 4428 For definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation, unless the parameter 4429 HO-NumberNotRequired is sent. If the parameter Relocation Number List is returned, the parameter Handover Number 4430 shall not be returned. 4431 Multicall Bearer Information 4432 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation in the case that MSC-B 4433 supports multiple bearers. 4434 4435 Multiple Bearer Requested 4436 For a definition of this parameter see clause 7.6.2. This parameter shall be sent when MSC-A requests multiple bearers 4437 to MSC-B. 4438 Multiple Bearer Not Supported 4439 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation when MSC-B receives 4440 Multiple Bearer Requested parameter and MSC-B does not support multiple bearers.

483 Release 6 484 485

122

3GPP TS 29.002 V6.11.0 (2005-09)

486

3GPP

4441 Selected UMTS Algorithms 4442 For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally 4443 encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the 4444 service is a part of the inter MSC inter system handover from GSM to UMTS. 4445 Chosen Radio Resource Information 4446 For definition of this parameter see clause 7.6.6. This parameter shall be returned at relocation if the encapsulated PDU 4447 is RANAP RAB Assignment Response and MS is in GSM access. 4448 Iu-Selected Codec 4449 4450 4451 4452

487 Release 6 488 489

123

3GPP TS 29.002 V6.11.0 (2005-09)

For definition of this parameter see subclause 7.6.6. This parameter shall be included if an Iu-Supported Codecs List was received in the service request and MSC-B supports the selection of codec based on the Iu-Supported Codecs List, even if the Iu-Selected Codec is equal to the Iu-Currently Used Codec received in the service request. This parameter shall not be included if the Iu-Supported Codecs List was not received in the service request.

4453 Iu-Available Codecs List 4454 For definition of this parameter see subclause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO, if 4455 the Iu-Supported Codecs List was included by MSC-A and the target radio access is UMTS or GERAN Iu-mode. 4456 User error 4457 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4458 on the nature of the fault: 4459 4460 4461 4462 4463

No handover number available. Target cell outside group call area; System failure. Unexpected data value. Data Missing.

4464 Provider error 4465 See definition of provider errors in clause 7.6.1.

4466 4467 8.4.2.1

8.4.2 MAP_SEND_END_SIGNAL service


Definition

4468 This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by 4469 MSC-B to the MS. MSC-A retains then the main control of the call until it clears. 4470 The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either 4471 because the call has been released in MSC-A or because the call has been successfully handed over or relocated from 4472 MSC-B to another MSC. 4473 The MAP_SEND_END_SIGNAL service is a confirmed service using the primitives from table 8.4/2.

4474 8.4.2.2
4475

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

4476

490

3GPP

4477 8.4.2.3

491 Release 6 492 493

124

3GPP TS 29.002 V6.11.0 (2005-09)

Parameter use

4478 Invoke Id 4479 For definition of this parameter see clause 7.6.1. 4480 AN-APDU 4481 For definition of this parameter see clause 7.6.9. 4482 Provider error 4483 For definition of this parameter see clause 7.6.1.

4484 4485 8.4.3.1

8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service


Definition

4486 This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A-interface or Iu4487 interface in MSC-B to MSC-A. 4488 The MAP_PROCESS_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4489 table 8.4/3.

4490 8.4.3.2
4491

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 Iu-Selected Codec Iu-Available Codecs List Request M M C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=)

4492

4493 8.4.3.3
4494 Invoke Id

Parameter use

4495 For definition of this parameter see clause 7.6.1. 4496 AN-APDU 4497 For definition of this parameter see clause 7.6.9. 4498 Selected GSM algorithm 4499 For definition of this parameter see clause 7.6.6. This parameter shall be present if the encapsulated PDU is Security 4500 Mode Complete and MS is in GSM access. 4501 Selected UMTS Algorithms 4502 4503 4504 4505

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.

4506 Chosen Radio Resource Information

494

3GPP

4507 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4508 Assignment Response and MS is in GSM access. 4509 Selected RAB ID 4510 The selected radio access bearer that was kept at subsequent intra-MSC handover from UMTS to GSM after multiple 4511 bearers were used. 4512 Iu-Selected Codec 4513 For definition of this parameter see subclause 7.6.6. This parameter shall be included

495 Release 6 496 497

125

3GPP TS 29.002 V6.11.0 (2005-09)

4514 4515 4516


4517

if MSC-B changes the selected codec; if intersystem handover to UMTS or GERAN Iu-mode is performed in MSC-B; or if MSC-B received a Forward Access Signalling service request including an Iu-Supported Codecs List and the MS is in UMTS or GERAN Iu-mode access.

4518 This parameter shall not be included if the Iu-Supported Codecs List was not received either in the Prepare Handover 4519 service request or in the Forward Access Signalling service request. 4520 Iu-Available Codecs List 4521 For definition of this parameter see subclause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO

4522 4523 4524


4525 4526

if the Iu-Available Codecs List has changed in MSC-B; if intersystem handover to UMTS or GERAN Iu-mode is performed in MSC-B; or if MSC-B received a Forward Access Signalling service request including an Iu-Supported Codecs List and the MS is in UMTS or GERAN Iu-mode access.

4527 4528 8.4.4.1

8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service


Definition

4529 This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface 4530 or Iu-interface of MSC-B. 4531 The MAP_FORWARD_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4532 table 8.4/4.

4533 8.4.4.2
4534

Service primitives
Table 8.4/4: MAP_FORWARD_ACCESS_SIGNALLING
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 Iu-Currently Used Codec Iu-Supported Codecs List Request M C C C M C C C C C C C C C Indication M(=) C(=) C(=) C(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

498

3GPP

499 Release 6 500 501

126 RAB Configuration Indicator Iu-Selected Codec Alternative Channel Type C C C

3GPP TS 29.002 V6.11.0 (2005-09) C(=) C(=) C(=)

4535

4536 8.4.4.3
4538 Invoke Id

Parameter use

4537 For the definition and use of all parameters and errors, see clause 7.6.1.

4539 For definition of this parameter see clause 7.6.1. 4540 Integrity Protection Information 4541 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4542 encapsulated PDU is BSSMAP Cipher Mode Command. 4543 Encryption Information 4544 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4545 encapsulated PDU is BSSMAP Cipher Mode Command. 4546 Key Status 4547 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4548 encapsulated PDU is BSSMAP Cipher Mode Command. 4549 AN-APDU 4550 For definition of this parameter see clause 7.6.9. 4551 Allowed GSM Algorithms 4552 This parameters includes allowed GSM algorithms. This GSM parameter shall be included if the encapsulated PDU is 4553 RANAP Security Mode Command and there is an indication that the UE also supports GSM. 4554 Allowed UMTS Algorithms 4555 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if Integrity Protection 4556 Information and Encryption Information are not available and the encapsulated PDU is BSSMAP Cipher Mode 4557 Command. 4558 Radio Resource Information 4559 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4560 Assignment Request. If the parameter Radio Resource List is sent, the parameter Radio Resource Information shall not 4561 be sent. 4562 Radio Resource List 4563 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4564 Assignment Request and MSC-A requests modification of multiple bearers. If the parameter Radio Resource 4565 Information is sent, the parameter Radio Resource List shall not be sent. 4566 BSSMAP Service Handover 4567 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4568 RANAP RAB Assignment Request. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP 4569 Service Handover shall not be sent. 4570 BSSMAP Service Handover List 4571 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4572 RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter BSSMAP 4573 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent.

502

3GPP

4574 RANAP Service Handover 4575 For definition of this parameter see clause 7.6.6.. It shall be present if it is available and the encapsulated PDU is 4576 BSSMAP Assignment Request. 4577 Iu-Currently Used Codec 4578 For definition of this parameter see subclause 7.6.6. This parameter shall be included if the encapsulated PDU is a 4579 RANAP RAB Assignment Request or BSSMAP Assignment Request for a speech bearer and the MS is in UMTS or 4580 GERAN Iu-mode access. This parameter shall not be included if the Iu-Supported Codecs List is not included. 4581 Iu-Supported Codecs List 4582 For definition of this parameter see subclause 7.6.6. This parameter shall be included if the encapsulated PDU is a 4583 RANAP RAB Assignment Request or BSSMAP Assignment Request and

503 Release 6 504 505

127

3GPP TS 29.002 V6.11.0 (2005-09)

4584 4585 4586

a new bearer is allocated for speech; an existing bearer is modified from data to speech; or for an existing speech bearer the order of priority in the Iu-Supported Codecs List needs to be modified.

4587 This parameter shall not be included if the Iu-Selected Codec is included. 4588 RAB Configuration Indicator 4589 4590 4591 4592

For definition of this parameter see subclause 7.6.6. This parameter may be included if the encapsulated PDU is a RANAP RAB Assignment Request for a speech bearer, and MSC-A knows by means of configuration information that MSC-B supports the use of the Iu-Supported Codecs List parameter. This parameter shall not be included if the IuSupported Codecs List is not included.

4593 Iu-Selected Codec 4594 For definition of this parameter see subclause 7.6.6. This parameter shall be included if

4595
4596

the encapsulated PDU is a RANAP RAB Assignment Request or BSSMAP Assignment Request for an existing speech bearer; the MS is in UMTS or GERAN Iu-mode access; and an Iu-Available Codecs List was received by MSC-A for this speech bearer before, either in the Prepare Handover service response or in the Process Access Signalling service request.

4597 4598
4599

4600 This parameter shall not be included if the Iu-Supported Codecs List is included. 4601 Alternative Channel Type 4602 For definition of this parameter see clause 7.6.6. This parameter shall be present for a SCUDIF call if the encapsulated 4603 PDU is BSSMAP Assignment Request. 4604

4605 4606 8.4.5.1

8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service


Definition

4607 This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a 4608 handover or relocation to either MSC-A or a third MSC (MSC-B') is required. 4609 The MAP_PREPARE_SUBSEQUENT_HANDOVER service is a confirmed service using the primitives from 4610 table 8.4/5.

506

3GPP

4611 8.4.5.2
4612

507 Release 6 508 509

128

3GPP TS 29.002 V6.11.0 (2005-09)

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 GERAN Classmark RAB Configuration Indicator AN-APDU User error Provider error

Request M C C M C C C M

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

Response M(=)

Confirm M(=)

C C

C(=) C(=) O

4613

4614 8.4.5.3
4615 Invoke Id

Parameter use

4616 For definition of this parameter see clause 7.6.1. 4617 Target Cell Id 4618 For definition of this parameter see clause 7.6.2. This parameter shall be excluded if the service is a part of the Inter4619 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4620 23.009. 4621 Target RNC Id 4622 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter4623 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4624 23.009. 4625 Target MSC Number 4626 For definition of this parameter see clause 7.6.2. 4627 Selected RAB ID 4628 For definition of this parameter see clause 7.6.2. 4629 GERAN Classmark 4630 For definition of this parameter see subclause 7.6.6 This parameter shall be included if available. 4631 RAB Configuration Indicator 4632 For definition of this parameter see subclause 7.6.6. This parameter may be included if the call is a speech call and 4633 MSC-B knows by means of configuration information that MSC-B' (and MSC-A) supports the use of Available Codecs 4634 List parameter. 4635 AN-APDU 4636 For definition of this parameter see clause 7.6.9. 4637 User error 4638 For definition of this parameter see clause 7.6.1. The following error causes defined in clause 7.6.1 may be used, 4639 depending on the nature of the fault: 4640 4641

Unknown MSC; Subsequent handover failure;

510

3GPP

4642 4643

511 Release 6 512 513

129

3GPP TS 29.002 V6.11.0 (2005-09)

Unexpected data value; Data Missing.

4644 Provider error 4645 For definition of this parameter see clause 7.6.1.

4646 4647 8.4.6.1

8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service


Definition

4648 This service is used between MSC and VLR (B-interface) to request a handover number. 4649 The MAP_ALLOCATE_HANDOVER_NUMBER service is a confirmed service using the primitives from table 8.4/6.

4650 8.4.6.2
4651

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

4652

4653 8.4.6.3
4654 Invoke Id

Parameter use

4655 For definition of this parameter see clause 7.6.1. 4656 User error 4657 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4658 on the nature of the fault: 4659

No handover number available.

4660 Provider error 4661 For definition of this parameter see clause 7.6.1.

4662 4663 8.4.7.1

8.4.7 MAP_SEND_HANDOVER_REPORT service


Definition

4664 This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and 4665 used by MSC-A. 4666 The MAP_SEND_HANDOVER_REPORT service is a confirmed service using the primitives from table 8.4/7.

514

3GPP

4667 8.4.7.2
4668

515 Release 6 516 517

130

3GPP TS 29.002 V6.11.0 (2005-09)

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

4669

4670 8.4.7.3
4671 Invoke Id

Parameter use

4672 For definition of this parameter see clause 7.6.1. 4673 Handover Number 4674 For definition of this parameter see clause 7.6.2. 4675 Linked Id 4676 For definition of this parameter see clause 7.6.1. This service is linked with 4677 MAP_ALLOCATE_HANDOVER_NUMBER. 4678 Provider error 4679 For definition of this parameter see clause 7.6.1.

4680 4681

8.5 Authentication management services


8.5.1 MAP_AUTHENTICATE service

4682 The MAP_AUTHENTICATE service is used on the MAP B interface. This interface is not fully operational specified. 4683 It is strongly recommended not to implement the B-interface as an external interface.

4684 8.5.1.1

Definition

4685 This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC 4686 concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to 4687 initiate authentication. 4688 The service is a confirmed service and consists of four service primitives.

4689 8.5.1.2

Service primitives

4690 The service primitives are shown in table 8.5/1. 4691


Parameter name Invoke id RAND CKSN SRES Provider error

Table 8.5/1: MAP_AUTHENTICATE parameters


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

4692

518

3GPP

4693 8.5.1.3

519 Release 6 520 521

131

3GPP TS 29.002 V6.11.0 (2005-09)

Parameter use

4694 Invoke id 4695 See clause 7.6.1 for the use of this parameter. 4696 RAND 4697 See clause 7.6.7 for the use of this parameter. 4698 CKSN 4699 See clause 7.6.7 for the use of this parameter. 4700 SRES 4701 See clause 7.6.7 for the use of this parameter. 4702 Provider error 4703 See clause 7.6.1 for the use of this parameter.

4704 4705 8.5.2.1

8.5.2 MAP_SEND_AUTHENTICATION_INFO service


Definition

4706 This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. 4707 The VLR requests up to five authentication vectors. 4708 Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information from the 4709 HLR. The SGSN requests up to five authentication vectors. 4710 If the user is a UMTS subscriber, the HLR shall return authentication quintuplets. If the user is a GSM subscriber, the 4711 HLR shall return authentication triplets. 4712 If the HLR cannot provide the VLR or the SGSN with triplets, an empty response is returned. The VLR or the SGSN 4713 may then re-use old authentication triplets, except where this is forbidden under the conditions specified in 3GPP TS 4714 43.020 [24]. 4715 If the HLR cannot provide the VLR or the SGSN with quintuplets, an empty response is returned. The VLR or the 4716 SGSN shall not re-use old authentication quintuplets. 4717 If the VLR or SGSN receives a MAP_SEND_AUTHENTICATION_INFO response containing a User Error parameter 4718 as part of the handling of an authentication procedure, the authentication procedure in the VLR or SGSN shall fail. 4719 Security related network functions are further described in 3GPP TS 43.020 [24] and 3GPP TS 33.200. 4720 The service is a confirmed service and consists of four service primitives.

4721 8.5.2.2

Service primitives

4722 The service primitives are shown in table 8.5/2. 4723

Table 8.5/2: MAP_SEND_AUTHENTICATION_INFO parameters


Parameter name Invoke id IMSI Number of requested vectors Requesting node type Re-synchronisation Info Segmentation prohibited indicator Immediate response preferred indicator Requesting PLMN ID Request M C C C C C U C Indication M(=) C(=) C(=) C(=) C(=) C (=) C (=) C(=) Response M(=) Confirm M(=)

522

3GPP

523 Release 6 524 525 AuthenticationSetList User error Provider error

132

3GPP TS 29.002 V6.11.0 (2005-09) C C C(=) C(=) O

4724

4725 8.5.2.3
4726 Invoke id

Parameter use

4727 See clause 7.6.1 for the use of this parameter. 4728 IMSI 4729 See clause 7.6.2 for the use of this parameter. 4730 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4731 dialogue then this parameter shall not be present in any service request other than the first one. 4732 Number of requested vectors 4733 A number indicating how many authentication vectors the VLR or SGSN is prepared to receive. The HLR shall not 4734 return more vectors than indicated by this parameter. 4735 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4736 dialogue then this parameter shall not be present in any service request other than the first one. 4737 Requesting node type 4738 The type of the requesting node (SGSN or VLR). 4739 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4740 dialogue then this parameter shall not be present in any service request other than the first one. 4741 Re-synchronisation Info 4742 For definition and use of this parameter see 3GPP TS 33.200. 4743 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4744 than the first one.. 4745 Segmentation prohibited indicator 4746 This parameter indicates if the VLR or SGSN allows segmentation of the response at MAP user level. 4747 This parameter may be present only in the first request of the dialogue. 4748 Immediate response preferred indicator 4749 4750 4751 4752

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.

4753 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4754 than the first one. 4755 Requesting PLMN ID 4756 The PLMN-ID of the requesting node. See3GPP TS 23.003. 4757 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4758 dialogue then this parameter shall not be present in any service request other than the first one. 4759 AuthenticationSetList

526

3GPP

4760 A set of one to five authentication vectors are transferred from the HLR to the VLR or from the HLR to the SGSN, if 4761 the outcome of the service was successful. 4762 User error 4763 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4764 the service, depending on the respective failure reason: 4765 4766 4767 4768

527 Release 6 528 529

133

3GPP TS 29.002 V6.11.0 (2005-09)

unknown subscriber; unexpected data value; system failure; data missing.

4769 Provider error 4770 See clause 7.6.1 for the use of this parameter.

4771 4772 8.5.3.1

8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service


Definition

4773 This service is used between the VLR and the HLR or between the SGSN or HLR for reporting of authentication 4774 failures.

4775 8.5.3.2

Service primitives

4776 The service primitives are shown in table 8.5/3. 4777

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

4778

4779 8.5.3.3
4780 Invoke id

Parameter use

4781 See clause 7.6.1 for the use of this parameter. 4782 IMSI 4783 See clause 7.6.2 for the use of this parameter. 4784 Failure Cause 4785 See clause 7.6.7 for use of this parameter. 4786 4787 Re-attempt

530

3GPP

4788 See clause 7.6.7 for use of this parameter. 4789 Access Type 4790 See clause 7.6.7 for use of this parameter. 4791 Rand 4792 This parameter identifies the specific AV that failed authentication. 4793 See clause 7.6.7 for use of this parameter. 4794 VLR number 4795 Shall be present if the sender is VLR. See definition in clause 7.6.2. 4796 SGSN number 4797 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 4798 User error 4799 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 4800 values defined in clause 7.6.1: 4801 4802 4803

531 Release 6 532 533

134

3GPP TS 29.002 V6.11.0 (2005-09)

Unknown Subscriber; System Failure; Unexpected Data Value.

4804 Provider error 4805 These are defined in clause 7.6.

4806 4807 4808 8.6.1.1

8.6 Security management services


8.6.1 MAP_SET_CIPHERING_MODE service
Definitions

4809 This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is 4810 called when another service requires that information is to be sent on the radio path in encrypted form. 4811 The service is a non-confirmed service and consists of two service primitives.

4812 8.6.1.2

Service primitives

4813 The service primitives are shown in table 8.6/1. 4814

Table 8.6/1: MAP_SET_CIPHERING_MODE parameters


Parameter name Invoke id Ciphering mode Kc Request M M C Indication M(=) M(=) C(=)

4815

4816 8.6.1.3
4817 Invoke id

Parameter use

4818 See clause 7.6.1 for the use of this parameter.

534

3GPP

4819 Ciphering mode 4820 See clause 7.6.7 for the use of this parameter. 4821 Kc 4822 The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed.

535 Release 6 536 537

135

3GPP TS 29.002 V6.11.0 (2005-09)

4823 4824 4825 4826 8.7.1.1

8.7 International mobile equipment identities management services


8.7.1 MAP_CHECK_IMEI service
Definition

4827 This service is used between the VLR and the MSC and between the MSC and the EIR and between the SGSN and EIR 4828 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 4829 transferred to the EIR in the service request. 4830 This service may also be used to request the BMUEF from the EIR. 4831 The service is a confirmed service and consists of four service primitives.

4832 8.7.1.2

Service primitives

4833 The service primitives are shown in table 8.7/1. 4834


Parameter name Invoke id IMEI IMEISV Requested Equipment Info Equipment status BMUEF User error Provider error

Table 8.7/1: MAP_CHECK_IMEI parameters


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

4835

4836 8.7.1.3
4837 Invoke id

Parameter use

4838 See clause 7.6.1 for the use of this parameter. 4839 Requested Equipment Info 4840 This parameter indicates whether Equipment Status or BMUEF or both is requested. 4841 IMEI 4842 4843 4844 4845

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 one of IMEI and IMEISV 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 one of IMEI and IMEISV is mandatory in the service response from the MSC to the VLR on successful outcome.

4846 IMEISV 4847 See clause 7.6.2 for the use of this parameter. IMEISV shall be present if BMUEF is requested.

538

3GPP

4848 Equipment status 4849 See clause 7.6.3 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of 4850 the service if Equipment status was requested. 4851 BMUEF 4852 See clause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of 4853 the service if BMUEF was requested. 4854 User error 4855 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4856 the service, depending on the respective failure reason: 4857 4858 4859 4860

539 Release 6 540 541

136

3GPP TS 29.002 V6.11.0 (2005-09)

unknown equipment; this error is returned by the responder when the IMEI is not known in the EIR;

system failure; unexpected data value.

4861 Provider error 4862 See clause 7.6.1 for the use of this parameter.

4863 4864 8.7.2.1

8.7.2 MAP_OBTAIN_IMEI service


Definition

4865 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 4866 requested from the MS. 4867 The service is a confirmed service and consists of four service primitives.

4868 8.7.2.2

Service primitives

4869 The service primitives are shown in table 8.7/2. 4870


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

4871

4872 8.7.2.3
4873 Invoke id

Parameter use

4874 See clause 7.6.1 for the use of this parameter. 4875 IMEI 4876 See clause 7.6.2 for the use of this parameter. The parameter is included in the service response from the MSC to the 4877 VLR on successful outcome of the service.

542

3GPP

4878 User error

543 Release 6 544 545

137

3GPP TS 29.002 V6.11.0 (2005-09)

4879 If the service fails, the VLR sends the user error System Failure (see clause 7.6.1) to the MSC. 4880 Provider error 4881 See clause 7.6.1 for the use of this parameter.

4882 4883 4884 8.8.1.1


-

8.8 Subscriber management services


8.8.1 MAP-INSERT-SUBSCRIBER-DATA service
Definition

4885 This service is used by an HLR to update a VLR with certain subscriber data in the following occasions: 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895

the operator has changed the subscription of one or more supplementary services, basic services or data of a subscriber. Note that in case of withdrawal of a Basic or Supplementary service this primitive shall not be used; the operator has applied, changed or removed Operator Determined Barring; the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; the HLR provides the VLR with subscriber parameters at location updating of a subscriber or at restoration. In this case, this service is used to indicate explicitly that a supplementary service is not provisioned, if the supplementary service specification requires it. The only supplementary services which have this requirement are the CLIR and COLR services. Network access mode is provided only in restoration. 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.

4896 Also this service is used by an HLR to update an SGSN with certain subscriber data in the following occasions: 4897 4898 4899 4900 4901 4902 4903

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.

4904 It is a confirmed service and consists of the primitives shown in table 8.8/1.

4905 8.8.1.2
4906

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

Request M C C C C C C C C C C C

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

Response M(=)

Confirm M(=)

C C

C(=) C(=)

546

3GPP

547 Release 6 548 549

138 Request C C C C C C C C C C C U C C C C C C C C C Indication C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09) Response C Confirm C(=)

Parameter name 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 Access Restriction Data Regional Subscription Response Supported CAMEL Phases Offered CAMEL 4 CSIs User error Provider error

C C(=) C(=) C(=) C(=) C(=) C(=) C C C U

C(=)

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

4907

4908 8.8.1.3

Parameter use

4909 All parameters are described in clause 7.6. The following clarifications are applicable: 4910 Network access mode 4911 4912 4913 4914

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.

4915 IMSI 4916 It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by 4917 the VLR and the SGSN. 4918 MSISDN 4919 It is included either at location updating or when it is changed. The MSISDN sent shall be the basic MSISDN. This 4920 parameter is used by the VLR and the SGSN. 4921 Category 4922 It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN 4923 receives this parameter it shall ignore it. 4924 Subscriber Status 4925 It is included either at location updating or when it is changed. 4926 To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator 4927 Determined Barring. In this case ODB General Data shall also be present. If the Operator Determined Barring applies

550

3GPP

4928 and the subscriber is registered in the HPLMN and HPLMN specific Operator Determined Barring applies then ODB 4929 HPLMN Specific Data shall also be present. 4930 To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This 4931 parameter is used by the VLR and the SGSN. 4932 Bearer service List 4933 A list of Extensible Bearer service parameters (Extensible Bearer service is defined in clause 7.6). An Extensible Bearer 4934 service parameter must be the code for an individual Bearer service, except in the cases described below. 4935 4936 4937 4938

551 Release 6 552 553

139

3GPP TS 29.002 V6.11.0 (2005-09)

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.

4939 If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location 4940 updating or at restoration) or only the ones added (at subscriber data modification). 4941 If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not 4942 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no 4943 error is sent back), except in the cases described below. 4944 4945 4946 4947 4948 4949 4950 4951

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.

4952 Teleservice List 4953 A list of Extensible Teleservice parameters (Extensible Teleservice is defined in clause 7.6). An Extensible Teleservice 4954 parameter must be the code for an individual Teleservice. 4955 If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating 4956 or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant 4957 to the node at which the message is received should be included in the Teleservice List. 4958 If the VLR or the SGSN receives an Indication containing any Extensible Teleservice parameters which it does not 4959 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Teleservices (no 4960 error is sent back). This parameter is used by the VLR and the SGSN. 4961 Forwarding information List 4962 A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in clause 7.6). It 4963 includes Call Forwarding services either at location updating or at restoration or when they are changed. Each 4964 Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive. 4965 The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary 4966 service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible 4967 Forwarding Feature is defined in clause 7.6). 4968 The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according 4969 to the rules in clause 8.8.1.4. 4970 The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter. 4971 4972 4973 4974

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

554

3GPP

4975 subaddress shall not be included. If the VLR does not receive a forwarded-to subaddress then it shall assume that a 4976 forwarded-to subaddress has not been registered. 4977 The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding 4978 unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding 4979 options shall be ignored by the VLR, and may be set to any value by the HLR. 4980 For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the 4981 Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply 4982 condition timer shall not be included. 4983 For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not 4984 contain a no reply condition timer. 4985 4986 4987 4988

555 Release 6 556 557

140

3GPP TS 29.002 V6.11.0 (2005-09)

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.

4989 Call barring information List 4990 A list of Extensible Call barring information parameters (Extensible Call barring information is defined in clause 7.6). It 4991 includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible 4992 Call barring information parameter shall be treated independently of all other parameters in the primitive. 4993 The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. 4994 The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call 4995 Barring Feature is defined in clause 7.6). 4996 The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted 4997 according to the rules in clause 8.8.1.4. 4998 The Extensible Call Barring Feature shall contain an extensible SS-Status parameter. 4999 If the VLR or the SGSN receives an Indication containing any Extensible Call Barring service codes which it does not 5000 support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Extensible Call 5001 Barring service codes (no error is sent back). 5002 CUG information List 5003 A list of CUG information list parameters (CUG information is defined in clause 7.6). It includes CUG information 5004 either at location updating or at restoration or when it is changed. 5005 At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete 5006 CUG-SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If 5007 there are not options per extensible basic service group the CUG-FeatureList shall not be included. 5008 In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty 5009 CUG-SubscriptionList. 5010 When the VLR receives CUG data it shall replace the stored CUG data with the received data set. 5011 If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible 5012 basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no 5013 preferential CUG exists. 5014 If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies. 5015 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 5016 Unexpected Data Value. 5017 Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR. 5018 If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards 5019 the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this 5020 parameter it shall ignore it.

558

3GPP

5021 SS-Data List 5022 5023 5024 5025

559 Release 6 560 561

141

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5026 The Extensible SS-Data shall include the SS-Code for an individual supplementary service. 5027 The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are 5028 applicable to the service defined by the SS-Code. 5029 The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in clause 8.8.1.4. 5030 If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it 5031 returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received 5032 (no error is sent back). 5033 5034 5035 5036

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 it returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received (no error is sent back). SS-codes not related to the supported LCS capability set shall be discarded.

5037 Operator Determined Barring General data 5038 5039 5040 5041 5042 5043 5044 5045

If it is included in a Request/Indication, it includes all the Operator Determined Barring categories that may be applied to a subscriber registered in any PLMN. This parameter is only included in a Request/Indication when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all General Operator Determined Barring Categories shall be set to their actual status. If the VLR or the SGSN receives an Indication containing Operator Determined Barring General Data which shows that the subscriber is subject to barring not supported / not allocated by the VLR or by the SGSN, it returns Operator Determined Barring General Data in the response to the HLR to show the barring categories which are not supported / not allocated by the VLR or by the SGSN. This parameter is used by the VLR and the SGSN.

5046 Operator Determined Barring HPLMN data 5047 5048 5049 5050

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.

5051 If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data 5052 is present then the VLR or the SGSN shall not apply any HPLMN specific ODB services to the subscriber. This 5053 parameter is used by the VLR and the SGSN. 5054 eMLPP Subscription Data 5055 If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a 5056 call (as defined in clause 7.6). It contains both subparameters of eMLPP. 5057 If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and 5058 therefore discards the received information (no error is sent back). 5059 5060 5061 5062

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.

5063 MC Subscription Data 5064 If included in the Insert Subscriber Data request, this parameter provides the MC Subscription Data as defined in 5065 clause 7.6.

562

3GPP

5066 If the VLR does not support the MC service, it returns its code to the HLR in the parameter SS-Code List and therefore 5067 discards the received information (no error is sent back). 5068 5069 5070 5071

563 Release 6 564 565

142

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5072 Roaming Restriction Due To Unsupported Feature 5073 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 5074 supported by the MSC/VLR (e.g. Advice of Charge Charging Level). 5075 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 5076 the VLR and if the SGSN receives this parameter it shall ignore it. 5077 Regional Subscription Data 5078 5079 5080 5081 5082 5083

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.

5084 Regional subscription data that have been stored previously in a subscriber data record in the VLR or in the SGSN are 5085 completely replaced by the regional subscription data received in an Insert Subscriber Data indication during either an 5086 Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. 5087 After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are 5088 allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional 5089 Subscription Response. 5090 The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has 5091 been detected in one of the following cases: 5092 5093 5094 5095

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.

5096 Zone codes which have no mapping to location areas shall be ignored. 5097 If a sequence of MAP_INSERT_SUBSCRIBER_DATA services is used during a dialogue, Regional Subscription Data 5098 shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with 5099 the error Unexpected Data Value. 5100 If Regional Subscription Data are not included in any MAP_INSERT_SUBSCRIBER_DATA service, there is no 5101 restriction of roaming due to Regional Subscription. This parameter is used by the VLR and the SGSN. 5102 Voice Broadcast Data 5103 This parameter contains a list of group id's a user might have subscribed to; (VBS-Data is defined in clause 7.6). It 5104 includes VBS information either at location updating or at restoration or when it is changed. 5105 At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data. 5106 When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All 5107 subsequent VBS-data received within this dialogue shall be interpreted as add-on data. 5108 If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data.

566

3GPP

5109 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 5110 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 5111 it. 5112 Voice Group Call Data 5113 This parameter contains a list of group id's a user might have subscribed to; see clause 7.6. 5114 At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete 5115 VGCS-Data. 5116 When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. 5117 All VGCS-Data received within this dialogue shall be interpreted as add-on data. 5118 If VBCS-Data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VGCS-Data. 5119 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 5120 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 5121 it. 5122 North American Equal Access preferred Carrier Id List 5123 A list of the preferred carrier identity codes that are subscribed to. 5124 5125 5126 5127

567 Release 6 568 569

143

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5128 LSA Information 5129 5130 5131 5132 5133 5134 5135

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.

5136 At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA 5137 Information. 5138 When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data. 5139 When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access 5140 indicator. 5141 5142 5143 5144

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.

5145 If the entire LSA information is received, it shall always include the LSA only access indicator value together with the 5146 LSA data applicable for the PLMN (if any). 5147 If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously 5148 stored LSA Information. 5149 If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the 5150 error Unexpected Data Value. This parameter is used by the VLR and the SGSN. 5151 IST Alert Timer 5152 This parameter contains the IST Alert timer value that must be used to inform the HLR about the call activities that the 5153 subscriber performs.

570

3GPP

5154 At Location Updating, restoration, or when there is a change in the IST data defined for the Subscriber, the HLR shall 5155 include the IST Alert timer. 5156 LMU Identifier 5157 This parameter indicates the presence of an LMU. This parameter is used only by the VLR and shall be ignored if 5158 received by an SGSN. 5159 LCS Information 5160 This parameter provides the following LCS related information for an MS subscriber: 5161 5162 5163

571 Release 6 572 573

144

3GPP TS 29.002 V6.11.0 (2005-09)

list of GMLCs in the HPLMN; privacy exception list; MO-LR list.

5164 At restoration and location updating, the HLR shall include the complete LCS data of the subscriber. 5165 When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS 5166 data that is not modified need not be included. 5167 The VLR/SGSN shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data 5168 operation. 5169 If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the 5170 error Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the 5171 SS-Data List, then the VLR shall not interpret this as overlapping data. 5172 Super-Charger Supported In HLR 5173 This parameter is used by the HLR to indicate support for the Super-Charger functionality. If this parameter is present it 5174 shall include an indication of the age of the subscription data stored in the HLR. 5175 If this parameter is absent then the HLR does not support the Super-Charger functionality. 5176 SS-Code List 5177 5178 5179 5180 5181

The list of SS-Code parameters for the services that are provided to a subscriber but are not supported/allocated by the VLR/SGSN (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).

5182 Regional Subscription Response 5183 If included in the response this parameter indicates one of: 5184 5185 5186 5187 5188

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.

5189 If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR 5190 shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted 5191 is not sent. The HLR shall check whether the current MSC area is no longer restricted. 5192 5193 5194 5195

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.

574

3GPP

5196 VLR CAMEL Subscription Info 5197 This parameter is sent for subscribers who have CAMEL services which are invoked in the MSC. 5198 5199 5200 5201 5202
-

575 Release 6 576 577

145

3GPP TS 29.002 V6.11.0 (2005-09)

In CAMEL phase 1, this parameter contains only the O-CSI. In CAMEL Phase 2, this parameter may contain O-CSI, SS-CSI and TIF-CSI. In CAMEL Phase 2 and onwards, TDP-Criteria for O-CSI may be associated with O-CSI. In CAMEL Phase 3, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, M-CSI and TIF-CSI. In CAMEL Phase 3 and onwards, TDP-Criteria for VT-CSI may be associated with VT-CSI. In CAMEL Phase 4, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, MT-SMSCSI, M-CSI and TIF-CSI. In CAMEL Phase 4, TDP-Criteria for MT-SMS-CSI may be associated with MTSMS-CSI.

5203
5204 5205

5206 The VLR CAMEL Subscription Info is sent at location updating or when any information in the applicable CAMEL 5207 Subscription Info in the HLR has been changed. 5208 At location updating, the complete set of VLR CAMEL Subscription Info is sent in one dialogue. 5209 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the VLR, then: 5210 5211 5212 5213

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 or higher, one or more specific elements of VLR CAMEL Subscription Info are sent in one dialogue.

5214 When the VLR receives a specific element of VLR CAMEL Subscription Info, it shall overwrite the corresponding 5215 specific element of VLR CAMEL Subscription Info (if any) which it has stored for that subscriber. 5216 For CAMEL Phase 1 and CAMEL Phase 2 , the VLR CAMEL Subscription Info consists of any one or more of: 5217 5218 5219 5220

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

5221 From CAMEL phase 3 onwards, the specific elements of VLR CAMEL Subscription Info which may be sent are:

5222
5223 5224 5225 5226 5227 5228 5229 5230

-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; MO-SMS-CSI; MT-SMS-CSI; -TDP-Criteria for MT-SMS-CSI; M-CSI.

5231
5232

5233 If the VLR CAMEL Subscription Info is omitted in the Insert Subscriber Data operation the VLR shall keep the 5234 previously stored VLR CAMEL Subscription Info. Within one dialogue subsequent received data are interpreted as 5235 add-on data. If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the

578

3GPP

5236 error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall 5237 ignore it. 5238 The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag) for CAMEL Phase 2 and 5239 higher. See 3GPP TS 23.072 for the use of this parameter and the conditions for its presence. 5240 Supported CAMEL Phases 5241 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. This parameter is used 5242 by the VLR and SGSN. 5243 A VLR or SGSN not supporting any CAMEL Phase may omit this parameter. 5244 GPRS Subscription Data 5245 This parameter contains a list of PDP-contexts a user has subscribed to; see clause 7.6. 5246 At GPRS location updating the HLR shall include the complete GPRS Subscription Data. 5247 When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts. 5248 5249 5250 5251

579 Release 6 580 581

146

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5252 If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored 5253 GPRS Subscription Data. 5254 If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error 5255 Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 5256 it. 5257 SGSN CAMEL Subscription Info 5258 The SGSN CAMEL Subscription Info is sent at GPRS location updating or when any information in the applicable 5259 SGSN CAMEL Subscription Info in the HLR has been changed. 5260 5261 5262
-

In CAMEL Phase 3, this parameter may contain one or both of GPRS-CSI and MO-SMS-CSI. In CAMEL Phase 4, this parameter may contain GPRS-CSI, MO-SMS-CSI and MT-SMS-CSI and TDPCriteria for MT-SMS-CSI.

5263 At GPRS location updating the complete set of SGSN CAMEL Subscription Info is sent. 5264 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the SGSN, then 5265 one or more specific elements of SGSN CAMEL Subscription Info are sent in one dialogue. 5266 When the SGSN receives a specific element of SGSN CAMEL Subscription Info, it shall overwrite the corresponding 5267 specific element of SGSN CAMEL Subscription Info (if any) which it has stored for that subscriber. 5268 The specific elements of SGSN CAMEL Subscription Info which may be sent are: 5269 5270 5271 5272 5273 5274 5275 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it.

MO-SMS-CSI; MT-SMS-CSI; TDP-Criteria for MT-SMS-CSI; GPRS-CSI; MC-CSI.

582

3GPP

5276 Roaming Restricted In SGSN Due To Unsupported Feature 5277 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 5278 supported by the SGSN. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 5279 it. 5280 CS Allocation/Retention priority 5281 The CS Allocation/Retention priority is used only for Circuit Switched (CS). This parameter specifies relative 5282 importance to compare with other bearers about allocation and retention of bearer. This parameter is used only by the 5283 VLR and if the SGSN receives this parameter it shall ignore it. 5284 Offered CAMEL 4 CSIs 5285 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR or SGSN (see clause 7.6.3.36D). 5286 Subscribed Charging Characteristics 5287 This parameter refers to the Subscribed Charging Characteristics as defined in 3GPP TS 32.251. 5288 For a detailed description of the use of the parameter, see 3GPP TS 32.251. 5289 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 5290 Access Restriction Data 5291 This parameter indicates the allowed RAT according to subscription data. (see clause 7.6.3.96) 5292 If the VLR/SGSN supports the Access Restriction feature but does not receive the Access Restriction Data parameter 5293 from the HLR at location updating or restoration, the VLR/SGSN shall assume that the subscriber's profile does not 5294 have any restrictions enabled. 5295 For a detailed description of the use of the parameter, see 3GPP TS 23.012[23] for CS domain and 3GPP TS 5296 23.060[104] for PS domain. 5297 User error 5298 Only one of the following values is applicable: 5299 5300 5301

583 Release 6 584 585

147

3GPP TS 29.002 V6.11.0 (2005-09)

Unidentified subscriber; Data missing; Unexpected data value.

5302 8.8.1.4
5303 5304 5305 5306

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 or the SGSN.

5307 The Basic Service Group (or Basic Service Group List) is optional. 5308 If present the Basic Service Group (or each element of the Basic Service Group List) shall be one of: 5309 5310 5311 5312 5313 5314 5315 5316

an Elementary Basic Service Group for which the supplementary service is applicable to at least one basic service in the group and for 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 which 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 which is in the same Elementary Basic Service Group as a basic service to which the service is applicable.

586

3GPP

5317 If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic 5318 Service Groups. 5319 If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as 5320 applying individually to all the Elementary Basic Service Groups for which: 5321 5322

587 Release 6 588 589

148

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5323 The VLR and the SGSN are not required to store supplementary services data for Basic Service Groups which are not 5324 supported at the VLR or the SGSN respectively.

5325 5326 8.8.2.1

8.8.2 MAP-DELETE-SUBSCRIBER-DATA service


Definition

5327 This service is used by an HLR to remove certain subscriber data from a VLR or SGSN if the subscription of one or 5328 more supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or 5329 deactivation of supplementary services. 5330 This service is also used by an HLR to remove GPRS subscription data from an SGSN. 5331 It is a confirmed service and consists of the primitives shown in table 8.8/2.

5332 8.8.2.2
5333

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

5334

5335 8.8.2.3

Parameter use

5336 All parameters are described in clause 7.6. The following clarifications are applicable: 5337 Basic service List 5338 A list of Extensible Basic service parameters (Extensible Basic service is defined in clause 7.6). It is used when one, 5339 several or all basic services are to be withdrawn from the subscriber. If the VLR or the SGSN receives a value for an

590

3GPP

5340 Extensible Basic Service which it does not support, it shall ignore that value. This parameter is used by the VLR and by 5341 the SGSN. 5342 SS-Code List 5343 A list of SS-Code parameters (SS-Code is defined in clause 7.6). It is used when several or all supplementary services 5344 are to be withdrawn from the subscriber. 5345 There are three possible options: 5346 5347 5348 5349 5350 5351

591 Release 6 592 593

149

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5352 This parameter is used by the VLR and SGSN for Call Barring and LCS. Otherwise, this parameter is used only by the 5353 VLR and if the SGSN receives this parameter it shall ignore it. 5354 Roaming Restriction Due To Unsupported Feature 5355 This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This 5356 may occur if unsupported features or services are removed from the subscriber data in the HLR. 5357 If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is 5358 used only by the VLR and if the SGSN receives this parameter it shall ignore it. 5359 CAMEL Subscription Info Withdraw 5360 This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR or from the SGSN. All 5361 CAMEL Subscription Info for the subscriber shall be deleted. This parameter is used by the VLR and by the SGSN. 5362 This parameter should not be sent in the same message as the Specific CSI Withdraw parameter. 5363 Specific CSI Withdraw 5364 This parameter is used to indicate that one or more specific elements of CAMEL Subscription Info shall be deleted from 5365 the VLR or from the SGSN. 5366 The specific elements of CAMEL Subscription Info which may be withdrawn are: 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376

O-CSI with TDP criteria for O-CSI; SS-CSI; TIF-CSI; D-CSI; VT-CSI with TDP criteria for VT-CSI; MO-SMS-CSI; MT-SMS-CSI with TDP-Criteria for MT-SMS-CSI; M-CSI; MG-CSI; GPRS-CSI.

594

3GPP

5377 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 5378 or higher. This parameter should not be sent in the same message as the CAMEL Subscription Info Withdraw 5379 parameter. 5380 Regional Subscription Identifier 5381 5382 5383 5384 5385

595 Release 6 596 597

150

3GPP TS 29.002 V6.11.0 (2005-09)

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

5386 The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the 5387 VLR or by the SGSN. 5388 Note that support of this parameter is a network operator option and it shall not be sent to networks which do not 5389 support Regional Subscription. 5390 If Regional Subscription is not supported by the VLR or by the SGSN, the request for deletion of Zone Codes is refused 5391 by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR. 5392 If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information 5393 shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR and by 5394 the SGSN. 5395 VBS Group Indication 5396 Contains an indication (flag) which is used if all Group Ids shall be deleted from the subscriber data for the Voice 5397 Broadcast teleservice. 5398 If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request 5399 for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN receives this 5400 parameter it shall ignore it. 5401 VGCS Group Indication 5402 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice 5403 Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 5404 it. 5405 If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the 5406 request for deletion of all Group Ids shall be ignored. 5407 GPRS Subscription Data Withdraw 5408 5409 5410 5411

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.

5412 Roaming Restricted In SGSN Due To Unsupported Feature 5413 This parameter is used if Roaming Restricted In SGSN Due To Unsupported Feature is deleted from the GPRS 5414 subscriber data. This may occur if unsupported features or services are removed from the GPRS subscriber data in the 5415 HLR. 5416 If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is 5417 used only by the SGSN and if the VLR receives this parameter it shall ignore it. 5418 LSA Information Withdraw 5419 5420 5421 5422

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.

598

3GPP

5423 IST Information Withdraw 5424 This parameter is used to indicate that the IST condition has been removed for the subscriber. See 3GPP TS 43.035 for 5425 the use of this parameter. 5426 Regional Subscription Response 5427 If included in the Delete Subscriber Data response this parameter indicates one of: 5428 5429 5430

599 Release 6 600 601

151

3GPP TS 29.002 V6.11.0 (2005-09)

MSC Area Restricted; SGSN Area Restricted; Regional Subscription Not Supported.

5431 This parameter is used by the VLR and by the SGSN. 5432 GMLC List Withdraw 5433 This parameter indicates that the subscriber's LCS GMLC List shall be deleted from the VLR or SGSN. 5434 Subscribed Charging Characteristics Withdraw 5435 This parameter indicates that the Subscribed Charging Characteristics shall be replaced with a local default value in the 5436 SGSN (see 3GPP TS 32.251). 5437 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 5438 User error 5439 Only one of the following values is applicable: 5440 5441 5442

Unidentified subscriber; Data missing; Unexpected data value.

5443 5444 5445 8.9.1.1

8.9 Identity management services


8.9.1 MAP-PROVIDE-IMSI service
Definition

5446 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 5447 identified itself with a TMSI not allocated to any subscriber in the VLR). 5448 It is a confirmed service and consists of the primitives shown in table 8.9/1.

5449 8.9.1.2
5450

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

5451

5452 8.9.1.3

Parameter use

5453 All parameters are described in clause 7.6. The following clarifications are applicable:

602

3GPP

5454 IMSI

603 Release 6 604 605

152

3GPP TS 29.002 V6.11.0 (2005-09)

5455 This parameter is received when the request is successfully carried out. It contains the requested IMSI. 5456 User error 5457 Only one of the following values is applicable: 5458

Absent subscriber.

5459 5460 8.9.2.1

8.9.2 MAP-FORWARD-NEW-TMSI service


Definition

5461 This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call 5462 set-up, location updating or supplementary services operation). 5463 It is a confirmed service and consists of the primitives shown in table 8.9/2.

5464 8.9.2.2
5465

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

5466

5467 8.9.2.3

Parameter use

5468 The parameter TMSI is described in clause 7.6.

5469 5470 5471 8.10.1.1

8.10 Fault recovery services


8.10.1 MAP_RESET service
Definition

5472 This service is used by the HLR, after a restart, to indicate to a list of VLRs or SGSNs that a failure occurred. 5473 The MAP_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1.

5474 8.10.1.2
5475

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

5476

5477 8.10.1.3
5478 Invoke Id

Parameter definition and use

5479 See definition in clause 7.6.1. 5480 HLR number

606

3GPP

5481 See definition in clause 7.6.2. 5482 HLR Id LIST 5483 5484 5485 5486

607 Release 6 608 609

153

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5487 5488 8.10.2.1


5489 5490 5491 5492 5493

8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service


Definition

This service may be used by an HLR as an implementation option, to indicate to a mobile subscriber that supplementary services parameters may have been altered, e.g. due to a restart. If received from the HLR, the VLR shall forward this indication to the MSC, which in turn forwards it to the MS. The HLR only sends this indication after successful completion of the subscriber data retrieval from HLR to VLR that ran embedded in a MAP_UPDATE_LOCATION procedure.

5494 The MAP_FORWARD_CHECK_SS_INDICATION service is a non-confirmed service using the service primitives 5495 defined in table 8.10/2.

5496 8.10.2.2
5497

Service primitives
Table 8.10/2: MAP_FORWARD_CHECK_SS_INDICATION
Parameter name Invoke Id Request M Indication M(=)

5498

5499 8.10.2.3
5500 Invoke Id

Parameter definition and use

5501 See definition in clause 7.6.1.

5502 5503 8.10.3.1


5504 5505 5506 5507

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.

5508 The MAP_RESTORE_DATA service is a confirmed service using the service primitives defined in table 8.10/3.

5509 8.10.3.2
5510

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 Request M M U C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

610

3GPP

611 Release 6 612 613

154 Long FTN Supported Supported LCS Capability Sets Offered CAMEL 4 CSIs HLR number MS Not Reachable Flag User error Provider error C C C C(=) C(=) C(=) C C C

3GPP TS 29.002 V6.11.0 (2005-09)

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

5511

5512 8.10.3.3
5513 Invoke Id

Parameter definitions and use

5514 See definition in clause 7.6.1. 5515 IMSI 5516 See definition in clause 7.6.2. 5517 LMSI 5518 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 5519 to support the LMSI handling procedures. 5520 Supported CAMEL Phases 5521 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 5522 phase 1 is supported. Otherwise may be absent. 5523 SoLSA Support Indicator 5524 This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If 5525 this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling. 5526 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 5527 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 5528 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 5529 IST Support Indicator 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540

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.

5541 Long FTN Supported 5542 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 5543 Super-Charger Supported in Serving Network Entity 5544 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 5545 that subscriber data is required. 5546 If this parameter is absent then the VLR does not support the Super-Charger functionality. 5547 Supported LCS Capability Sets

614

3GPP

5548 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 5549 capability set is marked as supported then the VLR does not support LCS at all. 5550 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 5551 version. 5552 Offered CAMEL 4 CSIs 5553 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D). 5554 HLR number 5555 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful outcome of the service. 5556 MS Not Reachable Flag 5557 See definition in clause 7.6.8. This parameter shall be present in case of successful outcome of the service, if the "MS 5558 Not Reachable flag" was set in the HLR. 5559 User error 5560 In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes 5561 defined in clause 7.6.1 may be used, depending on the nature of the fault: 5562 5563 5564 5565

615 Release 6 616 617

155

3GPP TS 29.002 V6.11.0 (2005-09)

unknown subscriber; system failure; unexpected data value; data missing.

5566 Provider error 5567 For definition of provider errors see clause 7.6.1.

5568 5569 5570 8.11.1.1

8.11 Subscriber Information services


8.11.1 MAP-ANY-TIME-INTERROGATION service
Definition

5571 This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR or the 5572 GMLC at any time. This service may also be used by the gsmSCF to request the Mobile Number Portability (MNP) 5573 information from the NPLR. 5574 This service is also used by the Presence Network Agent to request information, (e.g. subscriber state and location) 5575 about the subscriber (associated with a presentity) from the HLR at any time (see 3GPP TS 23.141 [128]). 5576 When this service is used to the HLR, the subscriber state or location may be requested. 5577 When this service is used to the GMLC, only the location may be requested. 5578 When this service is used to the NPLR, only the MNP information may be requested. 5579 The MAP-ANY-TIME-INTERROGATION service is a confirmed service using the service primitives defined in 5580 table 8.11/1.

5581 8.11.1.2
5582

Service primitives
Table 8.11/1: Any_Time_Interrogation
Parameter name Request Indication Response Confirm

618

3GPP

619 Release 6 620 621

156 Invoke id Requested Info Requested domain MNP Requested Info gsmSCF-Address IMSI MSISDN Location Information Location Information for GPRS Subscriber State PS Subscriber State IMEI MS Classmark 2 GPRS MS Class MNP info Result User error Provider error M M C C M C C M(=) M(=) C(=) C(=) M(=) C(=) C(=) M(=)

3GPP TS 29.002 V6.11.0 (2005-09) M(=)

C C C C C C C C C

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

5583

5584 8.11.1.3

Parameter definition and use

5585 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are 5586 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98]. 5587 The HLR or GMLC may be able to use the value of the parameter gsmSCF-address to screen a 5588 MAP_Any_Time_Interrogation indication. 5589 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5590 User error 5591 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5592 5593 5594 5595 5596

System Failure; Any Time Interrogation Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber.

5597 Provider error 5598 These are defined in clause 7.6.1.

5599 5600 8.11.2.1

8.11.2 MAP-PROVIDE-SUBSCRIBER-INFO service


Definition

5601 This service is used to request information (e.g. subscriber state and location) from the VLR or SGSN at any time. 5602 The MAP-PROVIDE-SUBSCRIBER-INFO service is a confirmed service using the primitives defined in table 8.11/2.

622

3GPP

5603 8.11.2.2
5604

623 Release 6 624 625

157

3GPP TS 29.002 V6.11.0 (2005-09)

Service primitives
Table 8.11/2: Provide_Subscriber_Information
Parameter name Invoke id Requested Info IMSI LMSI Location Information Location Information for GPRS Subscriber State PS Subscriber State IMEI MS Classmark 2 GPRS MS Class User error Provider error Request M M M U Indication M(=) M(=) M(=) O Response M(=) Confirm M(=)

C C C C C C C C

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

5605

5606 8.11.2.3

Parameter definition and use

5607 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 5608 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98]. 5609 User error 5610 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5611 5612

Data Missing; Unexpected Data Value.

5613 Provider error 5614 These are defined in clause 7.6.1.

5615 5616 8.11.3.1

8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service


Definition

5617 This service is used by the gsmSCF, to request subscription information (e.g. call forwarding supplementary service 5618 data or CSI) from the HLR at any time. In an IP Multimedia Core Network, an IM-SSF can take on the role of a 5619 gsmSCF for this service. 5620

5621 8.11.3.2
5622

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

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

626

3GPP

627 Release 6 628 629

158 Supported CAMEL phases in VLR Supported CAMEL phases in SGSN Offered CAMEL 4 CSIs in VLR Offered CAMEL 4 CSIs in SGSN User error Provider error

3GPP TS 29.002 V6.11.0 (2005-09) C C C C C C(=) C(=) C(=) C(=) C(=) O

5623

5624 8.11.3.3

Parameter definition and use

5625 All parameters are described in clause 7.6. 5626 The HLR may be able to use the value of the parameter gsmSCF-address to screen a 5627 MAP_Any_Time_Subscription_Interrogation indication. The gsmSCF-address shall contain the IM-SSF address when 5628 the IM-SSF takes the role of the gsmSCF. 5629 5630 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 and 3GPP TS 5631 23.278. 5632 User error 5633 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643

Unexpected Data Value; Unknown Subscriber; BearerServiceNotProvisioned; TeleserviceNotProvisioned; CallBarred; IllegalSS-Operation; SS-NotAvailable; InformationNotAvailable; Any Time Subscription Interrogation Not Allowed; Data Missing.

5644 Provider error 5645 These are defined in clause 7.6.1.

5646 5647 8.11.4.1

8.11.4 MAP-ANY-TIME-MODIFICATION service


Definition

5648 This service is used by the gsmSCF, to modify information of the HLR at any time. 5649 This service is also used by the Presence Network Agent to activate or deactivate reporting of mobility management 5650 events (associated with a presentity) from the VLR or SGSN (see 3GPP TS 23.141 [128]).

5651 8.11.4.2
5652
Invoke id

Service primitives
Table 8.11/4: Any_Time_Modification
Parameter name Request M Indication M(=) Response M(=) Confirm M(=)

630

3GPP

631 Release 6 632 633 gsmSCF-Address IMSI MSISDN Modification request for ODB data Modification request for SS information Modification request for CSI Long FTN Supported Ext Forwarding information-for-CSE Ext Call barring information-for-CSE ODB Info CAMEL subscription info User error Provider error

159 M C C C C C C M(=) C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09)

C C C C C

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

5653

5654 8.11.4.3

Parameter definition and use

5655 All parameters are described in clause 7.6. 5656 The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Modification 5657 indication. 5658 The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.078 and 3GPP TS 5659 23.278. 5660 User error 5661 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675

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.

5676 Provider error 5677 These are defined in clause 7.6.1.

5678 8.11.5.1

8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service


Definition

634

3GPP

635 Release 6 636 637

160

3GPP TS 29.002 V6.11.0 (2005-09)

This service is used by the HLR to inform the gsmSCF that subscriber data have been modified. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this service.

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. In an IP Multimedia Core Network, if no MSISDN is available, the HLR shall populate this parameter with a dummy MSISDN. 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 and 3GPP TS 23.278.
5679 All Information Sent 5680 This parameter is set when the HLR has sent all information to gsmSCF.

User error

638

3GPP

639 Release 6 640 641

161

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5681 5682 5683

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 and 3GPP TS 23.278.

5684 5685 5686

9 Operation and maintenance services


9.1 Subscriber tracing services
9.1.1 MAP-ACTIVATE-TRACE-MODE service
Definition

5687 9.1.1.1

5688 This service is used between the HLR and the VLR to activate subscriber tracing in the VLR. 5689 Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN. 5690 The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1.

5691 9.1.1.2
5692

Service primitives
Table 9.1/1: MAP-ACTIVATE-TRACE-MODE
Parameter name Invoke id IMSI Trace reference Trace type Trace reference 2 Trace depth list Trace NE type list Trace interface list Trace event list Trace support indicator OMC Id User error Provider error Request M C M M C C C C C U Indication M(=) C(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C C(=) O Response M(=) Confirm M(=)

C(=)

5693

5694 9.1.1.3
5695 Invoke id

Parameter use

5696 See definition in clause 7.6.1. 5697 IMSI 5698 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation.

642

3GPP

5699 Trace reference 5700 See definition in clause 7.6.10. This parameter contains trace reference for GSM only tracing request. 5701 Trace type 5702 See definition in clause 7.6.10. This parameter contains trace type for GSM only tracing request. 5703 OMC Id 5704 See definition in clause 7.6.2. The use of this parameter is an operator option. 5705 Trace reference 2 5706 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5707 Trace depth list 5708 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5709 Trace NE type list 5710 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5711 Trace interface list 5712 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5713 Trace event list 5714 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5715 Trace support indicator 5716 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5717 User error 5718 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5719 5720 5721 5722 5723 5724

643 Release 6 644 645

162

3GPP TS 29.002 V6.11.0 (2005-09)

Unidentified Subscriber; Facility Not Supported; Tracing Buffer Full; System Failure; Unexpected Data Value; Data missing.

5725 Provider error 5726 For definition of provider errors see clause 7.6.1.

5727 5728 9.1.2.1

9.1.2 MAP-DEACTIVATE-TRACE-MODE service


Definition

5729 This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR. 5730 Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN. 5731 The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2.

646

3GPP

5732 9.1.2.2
5733

647 Release 6 648 649

163

3GPP TS 29.002 V6.11.0 (2005-09)

Service primitives
Table 9.1/2: MAP-DEACTIVATE-TRACE-MODE
Parameter name Invoke id IMSI Trace reference Trace reference 2 User error Provider error Request M C M C Indication M(=) C(=) M(=) C(=) Response M(=) Confirm M(=)

C(=) O

5734

5735 9.1.2.3
5736 Invoke id

Parameter use

5737 See definition in clause 7.6.1. 5738 IMSI 5739 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 5740 Trace reference 5741 See definition in clause 7.6.10. 5742 Trace reference 2 5743 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5744 User error 5745 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5746 5747 5748 5749 5750

Unidentified Subscriber; Facility Not Supported; System Failure; Unexpected Data Value; Data missing.

5751 Provider error 5752 For definition of provider errors see clause 7.6.1.

5753 5754 9.1.3.1

9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service


Definition

5755 This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC. 5756 The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3.

5757 9.1.3.2
5758

Service primitives
Table 9.1/3: MAP-TRACE-SUBSCRIBER-ACTIVITY
Parameter name Invoke id IMSI Request M C Indication M(=) C(=)

650

3GPP

651 Release 6 652 653

164 Trace reference Trace type OMC Id M M U M(=) M(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09)

5759

5760 9.1.3.3
5761 Invoke id

Parameter use

5762 See definition in clause 7.6.1. 5763 IMSI 5764 See definition in clause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC. 5765 Trace reference 5766 See definition in clause 7.6.10. 5767 Trace type 5768 See definition in clause 7.6.10. 5769 OMC Id 5770 See definition in clause 7.6.2. The use of this parameter is an operator option.

5771 5772 5773 9.2.1.1

9.2 Other operation and maintenance services


9.2.1 MAP-SEND-IMSI service
Definition

5774 This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance 5775 procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber's identity known. 5776 It is a confirmed service and consists of the primitives shown in table 9.2/1.

5777 9.2.1.2
5778

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

5779

5780 9.2.1.3
5782 User error

Parameter use

5781 All parameters are described in clause 7.6. The following clarifications are applicable.

5783 Only one of the following values is applicable: 5784 5785

Unknown subscriber; Unexpected data value;

654

3GPP

5786

655 Release 6 656 657

165

3GPP TS 29.002 V6.11.0 (2005-09)

Data missing.

5787 5788 5789

10

Call handling services


10.1 MAP_SEND_ROUTING_INFORMATION service
10.1.1 Definition

5790 This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform 5791 the interrogation of the HLR in order to route a call towards the called MS. 5792 This is a confirmed service using the primitives listed in table 10.1/1. 5793 This service is also used between the GMSC and the NPLR and between the gsmSCF and the HLR.

5794
5795

10.1.2 Service primitives


Table 10.1/1: MAP_SEND_ROUTING_INFORMATION parameters
Parameter name Invoke Id Interrogation Type GMSC or gsmSCF Address MSISDN OR Interrogation OR Capability CUG Interlock CUG Outgoing Access Number of Forwarding Network Signal Info Supported CAMEL Phases Suppress T-CSI Offered CAMEL 4 CSIs Suppression of Announcement Call Reference Number Forwarding Reason Basic Service Group Basic Service Group 2 Alerting Pattern CCBS Call Supported CCBS Phase Additional Signal Info IST Support Indicator Pre-paging supported Call Diversion Treatment Indicator Long FTN Supported Suppress VT-CSI Suppress Incoming Call Barring gsmSCF Initiated Call Network Signal Info 2 IMSI MSRN Forwarding Data Forwarding Interrogation Required VMSC address ReleaseResourcesSupported GMSC Camel Subscription Info Location Information Subscriber State Basic Service Code CUG Subscription Flag North American Equal Access preferred Request M M M 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 Indication M(=) M(=) M(=) 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(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=)

C C C C C C C C C C C U

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

658

3GPP

659 Release 6 660 661

166 Request Indication

3GPP TS 29.002 V6.11.0 (2005-09) Response C U C C C U C C C C C C C C Confirm C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O

Parameter name Carrier Id User error SS-List CCBS Target Keep CCBS Call Indicator IST Alert Timer Number Portability Status Supported CAMEL Phases in VMSC Offered CAMEL 4 CSIs in VMSC MSRN 2 Forwarding Data 2 SS-List 2 Basic Service Code 2 Allowed Services Unavailability Cause Provider error

5796

5797

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.

5798 See clause 7.6 for a definition of the parameters used in addition to the following. Note that: 5799 5800 5801 5802 5803 5804

5805 Interrogation Type 5806 See 3GPP TS 23.079 [99] for the use of this parameter. 5807 GMSC or gsmSCF address 5808 The E.164 address of the GMSC or the gsmSCF. This parameter contains the gsmSCF address if the gsmSCF iniated 5809 call parameter is present, otherwise it is the GMSC address. 5810 MSISDN 5811 This is the Mobile Subscriber ISDN number assigned to the called subscriber. In the Request & Indication it is the 5812 number received by the GMSC in the ISUP IAM. If the call is to be forwarded and the HLR supports determination of 5813 the redirecting number, the HLR inserts the basic MSISDN in the Response. 5814 See 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence in the response. 5815 OR Interrogation 5816 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5817 OR Capability 5818 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5819 CUG Interlock 5820 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5821 CUG Outgoing Access 5822 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5823 Number of Forwarding

662

3GPP

5824 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5825 Network Signal Info 5826 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 5827 Supported CAMEL Phases 5828 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5829 T-CSI Suppression 5830 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5831 Offered CAMEL 4 CSIs 5832 This parameter indicates the CAMEL phase 4 CSIs offered in the GMSC/VLR (see clause 7.6.3.36D). 5833 5834 Suppression Of Announcement 5835 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5836 Call Reference Number 5837 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5838 [99]. 5839 Forwarding Reason 5840 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5841 Basic Service Group 5842 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5843 Basic Service Group 2 5844 See 3GPP TS 23.079[99] for the use of this parameter and the conditions for its presence. 5845 Alerting Pattern 5846 See 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5847 CCBS Call 5848 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5849 Supported CCBS Phase 5850 This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported. 5851 Additional Signal Info 5852 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 5853 IST Support Indicator 5854 5855 5856 5857 5858 5859

663 Release 6 664 665

167

3GPP TS 29.002 V6.11.0 (2005-09)

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 if it is not subject to forwarding, or suppressing Call Forwarding from the GMSC), or allow the call assuming the associated risk of not having the basic IST mechanism available.

666

3GPP

5860 5861 5862 5863 5864 5865

667 Release 6 668 669

168

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5866 Pre-paging supported 5867 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 5868 Call Diversion Treatment Indicator 5869 This parameter indicates whether or not call diversion is allowed. 5870 Network Signal Info 2 5871 See 3GPP TS 23.172 [126] for the conditions for the presence of the components of this parameter. 5872 IMSI 5873 See 3GPP TS 23.018 [97] and 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence. 5874 MSRN 5875 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 5876 conditions for its presence. If the NPLR returns only the MSISDN-number without Routeing Number to the GMSC, the 5877 MSISDN-number shall be returned as MSRN. 5878 Forwarding Data 5879 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding 5880 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See 5881 3GPP TS 23.018 [97] and 3GPP TS 23.079 [99] for the conditions for the presence of its components. 5882 Forwarding Interrogation Required 5883 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5884 Long FTN Supported 5885 This parameter indicates that the GMSC supports Long Forwarded-to Numbers. 5886 Suppress VT-CSI 5887 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5888 Suppress Incoming Call Barring 5889 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5890 gsmSCF Initiated Call 5891 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5892 VMSC address 5893 See 3GPP TS 23.079 [99] and 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5894 In addition this parameter shall be present if the ReleaseResourcesSupported parameter is present. 5895 Release Resources Supported 5896 This parameter indicates by its presence that the MAP_RELEASE_RESOURCES service is supported at the VMSC. It 5897 shall be present if so indicated by the VMSC with MAP_PROVIDE_ROAMING_NUMBER confirm. 5898 GMSC CAMEL Subscription Info

670

3GPP

5899 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5900 Location Information 5901 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5902 Subscriber State 5903 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5904 CUG Subscription Flag 5905 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5906 North American Equal Access preferred Carrier Id 5907 This parameter is returned to indicate the preferred carrier identity to be used to set-up the call (i.e. forwarding the call 5908 or establishing the roaming leg). 5909 SS-List 5910 5911 5912 5913

671 Release 6 672 673

169

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5914 Basic Service Code 5915 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5916 5917 5918 5919 5920

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.

5921 CCBS Target 5922 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5923 Keep CCBS Call Indicator 5924 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5925 IST Alert Timer 5926 It includes the IST Alert timer value that must be used to inform the HLR about the call activities that the subscriber 5927 performs. This parameter is only sent to the GMSC in response to a Send Routing Information request which indicates 5928 the the GMSC supports IST. 5929 Number Portability Status 5930 This parameter indicates the number portability status of the subscriber. This parameter may be present if the sender of 5931 SRIack is NPLR. 5932 Supported CAMEL Phases in VMSC 5933 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5934 Offered CAMEL 4 CSIs in VMSC 5935 This parameter is defined in clause 7.6.3.36F. 5936 MSRN 2 5937 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126].

674

3GPP

5938 Forwarding Data 2 5939 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5940 SS-List 2 5941 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5942 Basic Service Code 2 5943 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5944 Allowed Services 5945 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5946 Unavailability Cause 5947 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5948 User error 5949 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976

675 Release 6 676 677

170

3GPP TS 29.002 V6.11.0 (2005-09)

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

678

3GPP

5977 5978 5979 5980 5981 5982 5983

679 Release 6 680 681

171

3GPP TS 29.002 V6.11.0 (2005-09)

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.

5984 See clause 7.6 for a definition of these errors. 5985 Provider error 5986 These are defined in clause 7.6.

5987 5988

10.2 MAP_PROVIDE_ROAMING_NUMBER service


10.2.1 Definition

5989 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a 5990 roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. 5991 This is a confirmed service which uses the primitives described in table 10.2/1.

5992
5993

10.2.2 Service primitives


Table 10.2/1: MAP_PROVIDE_ROAMING_NUMBER parameters
Parameter name Invoke Id IMSI MSC Number MSISDN LMSI GSM Bearer Capability Network Signal Info Suppression Of Announcement Call Reference Number GMSC Address OR Interrogation OR Not Supported in GMSC Alerting Pattern CCBS Call Supported CAMEL Phases in interrogating node Additional Signal Info Pre-paging supported Long FTN Supported Suppress VT-CSI Offered CAMEL 4 CSIs in interrogating node Roaming Number ReleaseResourcesSupported User error Provider error Request M M M U C C C C C C C C C C C C C C C C Indication M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C U C C(=) C(=) C(=) O Response M(=) Confirm M(=)

5994

5995

10.2.3 Parameter use


3GPP

682

5996 See clause 7.6 for a definition of the parameters used, in addition to the following. Note that: 5997 5998 5999 6000 6001 6002

683 Release 6 684 685

172

3GPP TS 29.002 V6.11.0 (2005-09)

a conditional parameter whose use is defined only in 3GPP TS 23.078 [98] 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 [98] & 3GPP TS 23.079 [99] shall be absent if the sending entity supports neither CAMEL nor optimal routeing.

6003 IMSI 6004 This is the IMSI of the called Subscriber. 6005 MSC Number 6006 This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the 6007 HLR as provided at location updating. 6008 MSISDN 6009 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6010 LMSI 6011 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6012 GSM Bearer Capability 6013 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6014 This information is passed according to the rules specified in TS 3GPP TS 29.007 [56]. 6015 There may be two GSM Bearer Capabilities supplied. 6016 Network Signal Info 6017 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 6018 Suppression Of Announcement 6019 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078 [98]. 6020 Call Reference Number 6021 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 6022 [99]. 6023 GMSC Address 6024 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 6025 [99]. 6026 OR Interrogation 6027 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6028 OR Not Supported in GMSC 6029 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6030 Supported CAMEL Phases in interrogating node 6031 This parameter is defined in clause 7.6.3.36I.Alerting Pattern 6032 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence.

686

3GPP

6033 CCBS Call 6034 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6035 Additional Signal Info 6036 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 6037 Pre-paging supported 6038 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 6039 Long FTN supported 6040 See 3GPP TS 23.082 for the use of this parameter and the conditions for its presence. 6041 Suppress VT-CSI 6042 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 6043 Offered CAMEL 4 CSIs in interrogating node 6044 This parameter is defined in clause 7.6.3.36E. 6045 Roaming Number 6046 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6047 ReleaseResourcesSupported 6048 This parameter indicates by its presence that the MAP_RELEASE_RESOURCES service is supported at the VMSC. 6049 User error 6050 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060

687 Release 6 688 689

173

3GPP TS 29.002 V6.11.0 (2005-09)

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.

6061 See clause 7.6 for a definition of these reasons. 6062 Provider error 6063 These are defined in clause 7.6.

690

3GPP

691 Release 6 692 693

174

3GPP TS 29.002 V6.11.0 (2005-09)

6064 6065

10.3 MAP_RESUME_CALL_HANDLING service


10.3.1 Definition

6066 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC 6067 to request the GMSC to resume handling the call and forward it to the specified destination. 6068 This is a confirmed service which uses the Primitives listed in table 10.3/1.

6069
6070

10.3.2 Service primitives


Table 10.3/1: MAP_RESUME_CALL_HANDLING parameters
Parameter name Invoke Id Call Reference Number Basic Service Group Basic Service Group 2 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 C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=) O

6071

6072

10.3.3 Parameter use

6073 Information received in subsequent segment of a segmented dialogue shall not overwrite information received in an 6074 earlier segment. 6075 See clause 7.6 for a definition of the parameters used, in addition to the following. 6076 Call Reference Number 6077 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in the first segment of the 6078 dialogue. 6079 Basic Service Group 6080 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in the first segment of the 6081 dialogue. 6082 Basic Service Group 2 6083 See 3GPP TS 23.079[99] for the use of this parameter. If this parameter is present, it shall be in the first segment of the 6084 dialogue. 6085 IMSI 6086 This is the IMSI of the forwarding Subscriber. This parameter shall be present in the first segment of the dialogue. 6087 Forwarding Data 6088 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding 6089 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See

694

3GPP

6090 3GPP TS 23.079 [99] for the conditions for the presence of its components. This parameter shall be present in a first 6091 segment of the dialogue. 6092 CUG Interlock 6093 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6094 CUG Outgoing Access 6095 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6096 O-CSI 6097 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 6098 For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data. 6099 D-CSI 6100 The Dialled Services-CSI. 6101 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 6102 CCBS Target 6103 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6104 UU Data 6105 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 6106 UUS CF Interaction 6107 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 6108 All Information Sent 6109 This parameter is set when the VMSC has sent all information to GMSC. 6110 MSISDN 6111 This parameter is the basic MSISDN of the forwarding subscriber. It shall be present if the VMSC supports 6112 determination of the redirecting number. 6113 User error 6114 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6115 6116 6117 6118

695 Release 6 696 697

175

3GPP TS 29.002 V6.11.0 (2005-09)

Optimal Routeing not allowed; Forwarding failed; Unexpected Data Value; Data Missing.

6119 Provider error 6120 These are defined in clause 7.6.

6121 6122

10.4 MAP_PREPARE_GROUP_CALL service


10.4.1 Definition

6123 This service is used by the Anchor_MSC to inform the Relay_MSC about a group call set-up.

698

3GPP

6124 The MAP_PREPARE_GROUP_CALL service is a confirmed service using the service primitives given in table 10.4/1.

699 Release 6 700 701

176

3GPP TS 29.002 V6.11.0 (2005-09)

6125
6126

10.4.2 Service primitives


Table 10.4/1: MAP_PREPARE_GROUP_CALL service
Parameter name Invoke Id Teleservice ASCI Call Reference Ciphering Algorithm Group Key Number VK-Id VSTK Key VSTK-RAND Priority CODEC-Information Uplink Free Indicator Group Call Number User Error Provider Error Request M M M M C C C C M M Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) M(=) M(=) Response M(=) Confirm M(=)

M C

M(=) C(=) O

6127

6128
6129 Invoke Id

10.4.3 Parameter definitions and use

6130 See definition in clause 7.6.1. 6131 Teleservice 6132 Voice Broadcast Service or Voice Group Call Service. 6133 ASCI Call Reference 6134 Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the 6135 Relay_MSC. 6136 Ciphering Algorithm 6137 The ciphering algorithm to be used for the group call. 6138 Group Key Number VK-Id 6139 This Group Key Number has to be broadcast and is used by the mobile station to derive the key for ciphering on the 6140 radio interface (see 3GPP TS 43.020 [24]). Values 2 to 15 are reserved for future use. 6141 Shall be present if the ciphering applies. 6142 VSTK 6143 The VGCS/VBS Short Term Key is used to derive the key for ciphering on the radio interface (see 3GPP TS 43.020 6144 [24]). 6145 Shall be present if the ciphering applies. 6146 VSTK-RAND 6147 This random number has to be broadcast and is used by the mobile station to derive the group key for ciphering on the 6148 radio interface (see 3GPP TS 43.020 [24]). 6149 Shall be present if the ciphering applies. 6150 Priority 6151 Default priority level related to the call if eMLPP applies.

702

3GPP

6152 CODEC-Information 6153 Information on the codecs allowed for this call. 6154 Uplink Free Indicator 6155 A flag indicating whether the call is initiated from a dispatcher. 6156 Group Call Number 6157 This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC. 6158 User Error 6159 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on 6160 the nature of the fault: 6161 6162 6163

703 Release 6 704 705

177

3GPP TS 29.002 V6.11.0 (2005-09)

No Group Call Number available; System Failure; Unexpected Data Value.

6164 Provider Error 6165 See definition of provider error in clause 7.6.1.

6166 6167 6168

10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service


10.5.1 Definitions

6169 This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications. 6170 The MAP_PROCESS_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives 6171 given in table 10.5/1.

6172
6173

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

6174

6175
6176 Invoke Id

10.5.3 Parameter definitions and use

6177 See definition in clause 7.6.1 6178 Uplink Request 6179 This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests 6180 access to the uplink. 6181 Uplink Release Indication 6182 This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free.

706

3GPP

6183 Release Group Call 6184 This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who 6185 has initiated the call and who currently has access to the uplink terminates the call.

707 Release 6 708 709

178

3GPP TS 29.002 V6.11.0 (2005-09)

6186 6187 6188

10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service


10.6.1 Definitions

6189 This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications. 6190 The MAP_FORWARD_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service 6191 primitives given in table 10.6/1.

6192
6193

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

6194

6195
6196 IMSI

10.6.3 Parameter definitions and use

6197 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 6198 Invoke Id 6199 See definition in clause 7.6.1. 6200 Uplink Request Acknowledgement 6201 This information element is used for positive acknowledgement of an uplink request. 6202 Uplink Release Indication 6203 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free. 6204 Uplink Reject Command 6205 This information element is used for negative acknowledgement of an uplink request. 6206 Uplink Seized Command 6207 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free. 6208 Uplink Release Command 6209 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted 6210 to a MS in the relay MSC area shall be released.

710

3GPP

6211 State Attributes 6212 This information element is used to allow service logic running in an Anchor MSC to mute a VGCS talker even when 6213 the talker is served on a Relay MSC. The IE is used to build a GCC message that provides a mechanism to induce the 6214 VGCS talker terminal to mute/unmute the downlink at the Anchor MSC, as defined in 3GPP TS 44.068.

711 Release 6 712 713

179

3GPP TS 29.002 V6.11.0 (2005-09)

6215 6216

10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service


10.7.1 Definitions

6217 This service is used between the Relay MSC and the Anchor MSC indicating that VGCS / VBS channels have been 6218 established in the Relay MSC area. The response is used by the Anchor MSC to inform the Relay MSC that all 6219 resources for the call can be released in the Relay MSC because the call has been released in the Anchor MSC. 6220 The MAP_SEND_GROUP_CALL_END_SIGNAL service is a confirmed service using the service primitives given in 6221 table 10.7/1.

6222
6223

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

6224

6225
6226 IMSI

10.7.3 Parameter definitions and use

6227 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 6228 Shall be present if the call was established by a service subscriber roaming in the relay MSC area. 6229 Invoke Id 6230 See definition in clause 7.6.1 6231 Provider Error 6232 See definition of provider error in clause 7.6.1.

6233 6234 6235 6236

10.8 Void 10.9 Void 10.10 MAP_SET_REPORTING_STATE service


10.10.1 Definition

6237 This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed 6238 service using the service primitives shown in table 10.10/1.

6239

10.10.2 Service primitives

714

3GPP

6240

715 Release 6 716 717

180

3GPP TS 29.002 V6.11.0 (2005-09)

Table 10.10/1: MAP_SET_REPORTING_STATE parameters


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

Parameter name Invoke id IMSI LMSI CCBS Monitoring CCBS Subscriber Status User error Provider error

C C

C(=) C(=) O

6241

6242

10.10.3 Parameter use

6243 See clause 7.6 for a definition of the parameters used, in addition to the following. 6244 IMSI 6245 The IMSI is a mandatory parameter if the service is used as the only one in a dialogue. 6246 CCBS Monitoring 6247 This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall 6248 be started this service corresponds to the message 'Start Reporting' in 3GPP TS 23.093 [107]; if it indicates that 6249 monitoring shall be stopped this service corresponds to the message 'Stop Reporting' in 3GPP TS 23.093 [107]. 6250 CCBS Subscriber Status 6251 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6252 User error 6253 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6254 values defined in clause 7.6.1: 6255 6256 6257 6258 6259 6260 6261

System Failure; Unidentified Subscriber; Unexpected Data Value; Data Missing; Resource Limitation; Facility Not Supported. This error is reserved for future use.

NOTE:

6262 Provider error 6263 These are defined in clause 7.6.

6264 6265

10.11 MAP_STATUS_REPORT service


10.11.1 Definition

6266 This service is used by the VLR to report an event or call outcome to the HLR. It is a confirmed service using the 6267 service primitives shown in table 10.11/1.

6268
6269

10.11.2 Service primitives


Table 10.11/1: MAP_STATUS_REPORT parameters

718

3GPP

719 Release 6 720 721 Parameter name Invoke id IMSI CCBS Subscriber Status Monitoring Mode Call Outcome User error Provider error

181 Request M M C C C Indication M(=) M(=) C(=) C(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09) Response M(=) Confirm M(=)

C(=) O

6270

6271

10.11.3 Parameter use

6272 See clause 7.6 for a definition of the parameters used, in addition to the following. 6273 CCBS Subscriber Status 6274 If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message 'Event 6275 Report' in 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its 6276 presence. 6277 Monitoring Mode 6278 If this parameter is present with CCBS Call Outcome this service corresponds to the message 'CCBS Call Report' in 6279 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6280 Call Outcome 6281 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6282 User error 6283 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6284 values defined in clause 7.6.1: 6285 6286 6287 6288

Unknown Subscriber; System Failure; Unexpected Data Value; Data Missing.

6289 Provider error 6290 These are defined in clause 7.6.

6291 6292

10.12 MAP_REMOTE_USER_FREE service


10.12.1 Definition

6293 This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber 6294 can be notified. It is a confirmed service using the service primitives shown in table 10.12/1.

6295
6296

10.12.2 Service primitives


Table 10.12/1: MAP_REMOTE_USER_FREE parameters
Parameter name Invoke id IMSI Call Info CCBS Feature Request M M M M Indication M(=) M(=) M(=) M(=) Response M(=) Confirm M(=)

722

3GPP

723 Release 6 724 725 Translated B Number Replace B Number Alerting Pattern RUF Outcome User error Provider error

182 M C C M(=) C(=) C(=) C C

3GPP TS 29.002 V6.11.0 (2005-09)

C(=) C(=) O

6297

6298

10.12.3 Parameter use

6299 See clause 7.6 for a definition of the parameters used, in addition to the following. 6300 Call Info 6301 See 3GPP TS 23.093 [107] for the use of this parameter. 6302 CCBS Feature 6303 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 6304 Translated B Number 6305 See 3GPP TS 23.093 [107] for the use of this parameter. 6306 Replace B Number 6307 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6308 Alerting Pattern 6309 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6310 RUF Outcome 6311 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6312 User error 6313 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6314 values defined in clause 7.6.1: 6315 6316 6317 6318 6319 6320 6321 6322

Unexpected Data Value; Data Missing; Incompatible Terminal; This error is returned by the responder when the terminal used for CCBS activation is not compatible with the terminal used for the CCBS recall. For details refer to 3GPP TS 24.008 [35]; Absent Subscriber (IMSI Detach; Restricted Area; No Page Response); System Failure; Busy Subscriber (CCBS Busy).

6323 Provider error 6324 These are defined in clause 7.6.

6325 6326

10.13 MAP_IST_ALERT service


10.13.1 Definition

726

3GPP

6327 This service is used between the MSC (Visited MSC or Gateway MSC) and the HLR, to report that the IST timer 6328 running for a call for the Subscriber has expired. It is a confirmed service using the service primitives shown in 6329 table 10.13/1.

727 Release 6 728 729

183

3GPP TS 29.002 V6.11.0 (2005-09)

6330
6331

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

6332

6333

10.13.3 Parameter use

6334 All parameters are described in clause 7.6. The following clarifications are applicable: 6335 IST Alert Timer 6336 If included in the IST Alert response, it includes the new IST Alert timer value that must be used to inform the HLR 6337 about the call activities that the subscriber performs. 6338 IST Information Withdraw 6339 If included in the IST Alert response, this parameter is used to indicate that the IST condition has been removed for the 6340 subscriber. When the MSC receives this parameter, IST control for that call shall be terminated. 6341 Call termination Indicator 6342 6343 6344 6345 6346

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.

6347 User error 6348 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6349 6350 6351 6352 6353

System Failure; Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.

6354 6355

10.14 MAP_IST_COMMAND service


10.14.1 Definition

6356 This service is used by the HLR to instruct the MSC (Visited MSC or Gateway MSC) to terminate ongoing call 6357 activities for a specific subscriber. It is a confirmed service using the service primitives shown in table 10.14/1.

730

3GPP

6358

731 Release 6 732 733

184

3GPP TS 29.002 V6.11.0 (2005-09)

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

6359

6360

6361

10.14.3 Parameter use

6362 All parameters are described in clause 7.6. The following clarifications are applicable: 6363 User error 6364 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6365 6366 6367 6368 6369

System Failure; Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.

6370 6371

10.15 MAP_RELEASE_RESOURCES service


10.15.1 Definition

6372 This service is used between the GMSC and the terminating VMSC. The service is invoked by the GMSC to request the 6373 VMSC to release the resources associated with the specified MSRN. 6374 This is a confirmed service which uses the Primitives listed in table 10.15/1.

6375
6376

10.15.2 Service primitives


Table 10.15/1: MAP_RELEASE_RESOURCES parameters
Parameter name Invoke Id MSRN User error Provider error Request M M Indication M(=) M(=) Response M(=) C Confirm M(=) C(=) O

6377

6378
6379 MSRN

10.15.3 Parameter use

6380 See 3GPP TS 23.018 [97] for the use of this parameter. 6381 User error 6382 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6383

System Failure;

734

3GPP

6384

735 Release 6 736 737

185

3GPP TS 29.002 V6.11.0 (2005-09)

Unexpected Data Value;

6385 Provider error 6386 These are defined in clause 7.6.

6387 6388 6389

11

Supplementary services related services


11.1 MAP_REGISTER_SS service
11.1.1 Definition

6390 This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a 6391 supplementary service. The VLR will relay the message to the HLR. 6392 The service is a confirmed service and uses the service primitives shown in table 11.1./1.

6393
6394

11.1.2 Service primitives


Table 11.1/1: MAP_REGISTER_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarded-to number with subaddress No reply condition time EMLPP default priority Long FTN Supported NbrUser Forwarding information User error Provider error Request M M C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C C C

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

6395

6396
6397 Invoke id

11.1.3 Parameter use

6398 See clause 7.6.1 for the use of this parameter. 6399 SS-Code 6400 This parameter indicates the supplementary service which the mobile subscriber wants to register. 6401 Basic service 6402 This parameter indicates for which basic service group the supplementary service is to be registered. If it is not 6403 included, the registration request applies to all basic services. 6404 Forwarded-to number with subaddress 6405 This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can 6406 optionally include a sub-address. 6407 No reply condition time 6408 This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a 6409 superset of this service) and the mobile subscriber supplies a value for this time.

738

3GPP

6410 EMLPP default priority 6411 This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at 6412 successful outcome of the service. 6413 Long FTN Supported 6414 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6415 NbrUser 6416 This parameter is sent by the initiator to register the MC maximum number of user defined circuit switched bearers to 6417 be used. 6418 Forwarding information 6419 This parameter is returned by the responder at successful outcome of the service, if the registration request concerned 6420 one or a group of Call Forwarding supplementary services. 6421 User error 6422 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6423 values defined in clause 7.6.1: 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434

739 Release 6 740 741

186

3GPP TS 29.002 V6.11.0 (2005-09)

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.

6435 Provider error 6436 See clause 7.6.1 for the use of this parameter.

6437 6438

11.2 MAP_ERASE_SS service


11.2.1 Definition

6439 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a 6440 supplementary service. The VLR will relay the message to the HLR. 6441 The service is a confirmed service and uses the service primitives shown in table 11.2/1.

6442
6443

11.2.2 Service primitives


Table 11.2/1: MAP_ERASE_SS parameters
Parameter name Request Indication Response Confirm

742

3GPP

743 Release 6 744 745

187 Invoke id SS-Code Basic service Forwarding information User error Provider error M M C M(=) M(=) C(=)

3GPP TS 29.002 V6.11.0 (2005-09) M(=) C C M(=) C(=) C(=) O

6444

6445
6446 Invoke id

11.2.3 Parameter use

6447 See clause 7.6.1 for the use of this parameter. 6448 SS-Code 6449 This parameter indicates the supplementary service which the mobile subscriber wants to erase. 6450 Basic service 6451 This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, 6452 the erasure request applies to all basic services. 6453 Forwarding information 6454 This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or 6455 a group of Call Forwarding supplementary services. 6456 User error 6457 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6458 values, defined in clause 7.6.1: 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468

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.

6469 Provider error 6470 See clause 7.6.1 for the use of this parameter.

6471 6472

11.3 MAP_ACTIVATE_SS service


11.3.1 Definition

6473 This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary 6474 service. The VLR will relay the message to the HLR.

746

3GPP

6475 The service is a confirmed service and uses the service primitives shown in table 11.3/1.

747 Release 6 748 749

188

3GPP TS 29.002 V6.11.0 (2005-09)

6476
6477

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

6478

6479
6480 Invoke id

11.3.3 Parameter use

6481 See clause 7.6.1 for the use of this parameter. 6482 SS-Code 6483 This parameter indicates the supplementary service which the mobile subscriber wants to activate. 6484 Basic service 6485 This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it 6486 is not included, the activation request applies to all basic services. 6487 Forwarding information 6488 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 6489 Call Forwarding. 6490 Long FTN Supported 6491 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6492 Call barring information 6493 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 6494 Call Barring. 6495 SS-Data 6496 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for 6497 example Call Waiting. 6498 User error 6499 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6500 values, defined in clause 7.6.1: 6501 6502 6503 6504

System failure; Data Missing; Unexpected data value; Bearer service not provisioned;

750

3GPP

6505 6506 6507 6508 6509 6510 6511 6512 6513 6514

751 Release 6 752 753

189

3GPP TS 29.002 V6.11.0 (2005-09)

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.

6515 Provider error 6516 See clause 7.6.1 for the use of this parameter.

6517 6518

11.4 MAP_DEACTIVATE_SS service


11.4.1 Definitions

6519 This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary 6520 service. The VLR will relay the message to the HLR. 6521 The service is a confirmed service and uses the service primitives shown in table 11.4/1.

6522
6523

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

6524

6525
6526 Invoke id

11.4.3 Parameter use

6527 See clause 7.6.1 for the use of this parameter. 6528 SS-Code 6529 This parameter indicates the supplementary service which the mobile subscriber wants to deactivate. 6530 Basic service 6531 This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If 6532 it is not included the deactivation request applies to all basic services.

754

3GPP

6533 Forwarding information 6534 This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned 6535 one or a group of Call Forwarding supplementary services. 6536 Call barring information 6537 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one 6538 or a group of Call Barring supplementary services. 6539 SS-Data 6540 This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request 6541 concerned the Call Waiting supplementary service. 6542 User error 6543 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6544 values, defined in clause 7.6.1: 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557

755 Release 6 756 757

190

3GPP TS 29.002 V6.11.0 (2005-09)

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.

6558 Provider error 6559 See clause 7.6.1 for the use of this parameter.

6560 6561

11.5 MAP_INTERROGATE_SS service


11.5.1 Definitions

6562 This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related 6563 to a supplementary service. The VLR will relay the message to the HLR if necessary. 6564 The service is a confirmed service and consists of four service primitives.

6565

11.5.2 Service primitives


Table 11.5/1: MAP_INTERROGATE_SS parameters

6566 The service primitives are shown in table 11.5/1. 6567

758

3GPP

759 Release 6 760 761

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

3GPP TS 29.002 V6.11.0 (2005-09) Response M(=) Confirm M(=)

C C C C C C C C

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

6568

6569

11.5.3 Parameter use

6570 For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications. 6571 Invoke id 6572 See clause 7.6.1 for the use of this parameter. 6573 SS-Code 6574 The mobile subscriber can only interrogate a single supplementary service per service request. 6575 Basic service 6576 This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not 6577 included, the interrogation request applies to all basic services. 6578 SS-Status 6579 This parameter is included by the responder if: 6580 6581 6582 6583 6584

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.

6585 Basic service group LIST 6586 This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary 6587 service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) 6588 basic service groups, the SS-Status parameter is returned. 6589 Long FTN Supported 6590 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6591 Forwarding feature LIST 6592 The forwarding feature parameter is described in clause 7.6.4. A list of one or more forwarding features is returned by 6593 the responder when the interrogation request applied to Call Forwarding supplementary service. 6594 If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all 6595 provisioned basic services. 6596 CLI restriction Info

762

3GPP

6597 The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR 6598 supplementary service. 6599 EMLPP Info 6600 The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation 6601 request applies to the eMLPP supplementary service. 6602 MC Information 6603 The MC information (NbrSB, NbrUser and NbrSN) is returned by the responder if the interrogation request applies to 6604 the MC supplementary service. For a definition of these 3 components, refer to 3GPP TS 23.135 and 3GPP TS 24.135. 6605 CCBS Feature LIST 6606 The CCBS feature parameter is described in clause 7.6. A list of one or more CCBS features is returned by the 6607 responder when the interrogation request applied to the CCBS supplementary service. See 3GPP TS 23.093 [107] for 6608 the conditions for the presence of the parameters included in the CCBS feature. 6609 User error 6610 This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the 6611 following values, defined in clause 7.6.1: 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621

763 Release 6 764 765

192

3GPP TS 29.002 V6.11.0 (2005-09)

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.

6622 Provider error 6623 See clause 7.6.1 for the use of this parameter.

6624 6625 6626

11.6 Void 11.7 MAP_REGISTER_PASSWORD service


11.7.1 Definitions

6627 This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber 6628 requests to register a new password. The VLR will relay the message to the HLR. 6629 The service is a confirmed service and consists of four service primitives.

6630

11.7.2 Service primitives

6631 The service primitives are shown in table 11.7/1.

766

3GPP

6632

767 Release 6 768 769

193

3GPP TS 29.002 V6.11.0 (2005-09)

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

6633

6634
6635 Invoke id

11.7.3 Parameter use

6636 See clause 7.6.1 for the use of this parameter. 6637 SS-Code 6638 This parameter indicates for which supplementary service(s) the password should be registered. 6639 New Password 6640 See clause 7.6.4 for the use of this parameter. 6641 User error 6642 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6643 values, defined in clause 7.6.1: 6644 6645 6646 6647 6648 6649 6650 6651

System failure; Data Missing; Unexpected data value; Call Barred; SS subscription violation; Password registration failure; Negative PW check; Number Of PW Attempts Violation.

6652 Provider error 6653 See clause 7.6.1 for the use of this parameter.

6654 6655

11.8 MAP_GET_PASSWORD service


11.8.1 Definitions

6656 This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a 6657 request from the mobile subscriber for an operation on a supplementary service which requires a password from the 6658 subscriber. The VLR will relay the message to the MSC. 6659 The service is a confirmed service and uses the service primitives shown in table 11.8/1.

6660
6661

11.8.2 Service primitives


Table 11.8/1: MAP_GET_PASSWORD parameters

770

3GPP

771 Release 6 772 773

194 Parameter name Invoke id Linked id Guidance info Current password Provider error Request M C M Indication M(=) C(=) M(=)

3GPP TS 29.002 V6.11.0 (2005-09) Response M(=) Confirm M(=)

M(=) O

6662

6663
6664 Invoke id

11.8.3 Parameter use

6665 See clause 7.6.1 for the use of this parameter. 6666 Linked Id 6667 See clause 7.6.1 for the use of this parameter. If the MAP_GET_PASSWORD service is used in conjunction with the 6668 MAP_REGISTER_PASSWORD service, this parameter must be present; otherwise it must be absent. 6669 Guidance info 6670 See clause 7.6.4 for the use of this parameter. 6671 Current password 6672 See clause 7.6.4 for the use of this parameter. 6673 Provider error 6674 See clause 7.6.1 for the use of this parameter.

6675 6676 6677

11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service


11.9.1 Definitions

6678 This service is used between the MSC and the VLR, between the VLR and the HLR, between the HLR and gsmSCF 6679 and between the HLR and HLR to relay information in order to allow unstructured supplementary service operation. 6680 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from 6681 table 11.9/1.

6682
6683

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 C Indication M(=) M(=) M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O

6684

6685
6686 Invoke id

11.9.3 Parameter use

6687 See clause 7.6.1 for the use of this parameter.

774

3GPP

6688 USSD Data Coding Scheme 6689 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the 6690 unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be 6691 present. 6692 USSD String 6693 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the 6694 unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme 6695 parameter has to be present. 6696 MSISDN 6697 The subscribers basic MSISDN. 6698 See definition in clause 7.6.2. For Follow Me when the service request is sent from the HLR of the A subscriber, the 6699 parameter shall contain the MSISDN of the A subscriber, see 3GPP TS 23.094 [129]. For other purposes the MSISDN 6700 may be included as an operator option, e.g. to allow addressing the subscribers data in the gsmSCF with the MSISDN. 6701 User error 6702 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6703 values defined in clause 7.6.1: 6704 6705 6706 6707 6708 6709

775 Release 6 776 777

195

3GPP TS 29.002 V6.11.0 (2005-09)

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.

6710 Provider error 6711 See clause 7.6.1 for the use of this parameter.

6712 6713

11.10 MAP_UNSTRUCTURED_SS_REQUEST service


11.10.1 Definitions

6714 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6715 when the invoking entity requires information from the mobile user, in connection with unstructured supplementary 6716 service handling. 6717 The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.10/1.

6718
6719

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

6720

778

3GPP

6721

779 Release 6 780 781

196

3GPP TS 29.002 V6.11.0 (2005-09)

11.10.3 Parameter use

6722 Invoke id 6723 See clause 7.6.1 for the use of this parameter. 6724 USSD Data Coding Scheme 6725 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6726 user's MMI input. If this parameter is present, then the USSD String parameter has to be present. 6727 USSD String 6728 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6729 user's MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. 6730 Alerting Pattern 6731 See clause 7.6.3 for the use of this parameter. 6732 User error 6733 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6734 values defined in clause 7.6.1: 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745

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.

6746 Provider error 6747 See clause 7.6.1 for the use of this parameter.

6748 6749

11.11 MAP_UNSTRUCTURED_SS_NOTIFY service


11.11.1 Definitions

6750 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6751 when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured 6752 supplementary services handling. 6753 The MAP_UNSTRUCTURED_SS_NOTIFY service is a confirmed service using the primitives from table 11.11/1.

782

3GPP

6754

783 Release 6 784 785

197

3GPP TS 29.002 V6.11.0 (2005-09)

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

6755

Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error

C(=) O

6756

6757
6758 Invoke id

11.11.3 Parameter use

6759 See clause 7.6.1 for the use of this parameter. 6760 USSD Data Coding Scheme: 6761 See clause 7.6.4 for the use of this parameter. 6762 USSD String: 6763 See clause 7.6.1 for the use of this parameter. 6764 Alerting Pattern 6765 See clause 7.6.3 for the use of this parameter. 6766 User error 6767 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6768 values defined in clause 7.6.1: 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779

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.

6780 Provider error 6781 See clause 7.6.1 for the use of this parameter.

786

3GPP

787 Release 6 788 789

198

3GPP TS 29.002 V6.11.0 (2005-09)

6782 6783

11.12 MAP_SS_INVOCATION_NOTIFY
11.12.1 Definition

6784 This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following 6785 supplementary services; Call Deflection (CD), Explicit Call Transfer (ECT) or Multi Party (MPTY). 6786 This service is used between the HLR and the gsmSCF when the subscriber invokes the CCBS supplementary service.

6787

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

6788 The service primitives are shown in table 11.12/1. 6789

C(=) O

6790

6791

11.12.3 Parameter use

6792 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are 6793 specified in 3GPP TS 23.078. 6794 User error 6795 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6796 6797 6798

Data Missing; Unexpected Data Value; Unknown Subscriber.

6799 Provider error 6800 This is defined in clause 7.6.1.

6801 6802

11.13 MAP_REGISTER_CC_ENTRY service


11.13.1 Definition

6803 This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested 6804 call completion supplementary service. The VLR will relay the message to the HLR. 6805 The service is a confirmed service and uses the service primitives shown in table 11.13/1.

790

3GPP

6806

791 Release 6 792 793

199

3GPP TS 29.002 V6.11.0 (2005-09)

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

6807

C(=) O

6808

6809

11.13.3 Parameter use

6810 See clause 7.6 for a definition of the parameters used, in addition to the following. 6811 SS-Code 6812 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an 6813 entry. 6814 CCBS Feature 6815 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 6816 Translated B Number 6817 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6818 Service Indicator 6819 This parameter corresponds to the parameters 'Presentation Indicator' and 'CAMEL Invoked' in 3GPP TS 23.093 [107]. 6820 It indicates which services have been invoked for the original call (e.g. CLIR, CAMEL). See 3GPP TS 23.093 [107] for 6821 the use of this parameter and the conditions for its presence. 6822 Call Info 6823 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6824 Network Signal Info 6825 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6826 User error 6827 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6828 values, defined in clause 7.6.1: 6829 6830 6831 6832 6833 6834 6835

System failure; Data missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS incompatibility.

794

3GPP

6836 6837 6838 6839

795 Release 6 796 797

200

3GPP TS 29.002 V6.11.0 (2005-09)

Short Term Denial; Long Term Denial; Facility Not Supported; This error is reserved for future use.

NOTE:

6840 Private Extensions shall not be sent with these user errors for this operation. 6841 Provider error 6842 See clause 7.6.1 for the use of this parameter.

6843 6844

11.14 MAP_ERASE_CC_ENTRY service


11.14.1 Definition

6845 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call 6846 completion supplementary service. The VLR will relay the message to the HLR. 6847 The service is a confirmed service and uses the service primitives shown in table 11.14/1.

6848
6849

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

6850

6851

11.14.3 Parameter use

6852 See clause 7.6 for a definition of the parameters used, in addition to the following. 6853 SS-Code 6854 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an 6855 entry/entries. 6856 CCBS Index 6857 See 3GPP TS 23.093 [107] for the use of this parameter and the condition for its presence. 6858 SS-Status 6859 Depending on the outcome of the service request this parameter may indicate either provisioned and active or not 6860 provisioned. 6861 User error 6862 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6863 values, defined in clause 7.6.1: 6864 6865

System failure; Data Missing;

798

3GPP

6866 6867 6868 6869

799 Release 6 800 801

201

3GPP TS 29.002 V6.11.0 (2005-09)

Unexpected data value; Call Barred; Illegal SS operation; SS error status.

6870 Private Extensions shall not be sent with these user errors for this operation. 6871 Provider error 6872 See clause 7.6.1 for the use of this parameter.

6873 6874 6875

12

Short message service management services


12.1 MAP-SEND-ROUTING-INFO-FOR-SM service
12.1.1 Definition

6876 This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the 6877 short message to the servicing MSC. 6878 The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1.

6879
6880

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

6881

6882
6883 Invoke id

12.1.3 Parameter use

6884 See definition in clause 7.6.1. 6885 MSISDN 6886 See definition in clause 7.6.2. 6887 SM-RP-PRI 6888 See definition in clause 7.6.8.

802

3GPP

6889 Service Centre Address 6890 See definition in clause 7.6.2. 6891 SM-RP-MTI 6892 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6893 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6894 layer protocol. 6895 SM-RP-SMEA 6896 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6897 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6898 layer protocol. 6899 GPRS Support Indicator 6900 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of the 6901 two numbers from the HLR. 6902 IMSI 6903 See definition in clause 7.6.2. The presence of this parameter is mandatory in a successful case. 6904 Network Node Number 6905 See definition in clause 7.6.2. This parameter is provided in a successful response. 6906 LMSI 6907 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 6908 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6909 GPRS Node Indicator 6910 See definition in clause 7.6.8. The presence of this parameter is mandatory if only the SGSN number is sent in the 6911 Network Node Number. 6912 Additional Number 6913 See definition in clause 7.6.2. This parameter is provided in a successful response. 6914 User error 6915 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6916 6917 6918 6919 6920 6921 6922 6923

803 Release 6 804 805

202

3GPP TS 29.002 V6.11.0 (2005-09)

Unknown subscriber; Call Barred; Teleservice Not Provisioned; Absent Subscriber_SM; Facility Not Supported; System failure; Unexpected Data Value; Data missing.

6924 Provider error 6925 For definition of provider errors see clause 7.6.1.

806

3GPP

807 Release 6 808 809

203

3GPP TS 29.002 V6.11.0 (2005-09)

6926 6927

12.2 MAP-MO-FORWARD-SHORT-MESSAGE service


12.2.1 Definition

6928 This service is used between the serving MSC or the SGSN and the SMS Interworking MSC to forward mobile 6929 originated short messages. 6930 The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 6931 table 12.2/1.

6932
6933

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

6934

6935
6936 Invoke id

12.2.3 Parameter use

6937 See definition in clause 7.6.1. 6938 SM RP DA 6939 See definition in clause 7.6.8. 6940 In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile 6941 station. 6942 SM RP OA 6943 See definition in clause 7.6.8. 6944 The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM 6945 transfer. 6946 SM RP UI 6947 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 6948 in this parameter. 6949 IMSI 6950 See definition in clause 7.6.2.1. The IMSI of the originating subscriber is inserted in this parameter in the mobile 6951 originated SM transfer. 6952 This parameter shall be included if the sending entity, whether MSC or SGSN, supports mobile number portability. 6953 User error 6954 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6955 6956

Facility Not Supported; System Failure;

810

3GPP

6957 6958 6959 6960 6961 6962 6963 6964

811 Release 6 812 813

204

3GPP TS 29.002 V6.11.0 (2005-09)

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

6965 Provider error 6966 For definition of provider errors see clause 7.6.1.

6967 6968

12.3 MAP-REPORT-SM-DELIVERY-STATUS service


12.3.1 Definition

6969 This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is 6970 used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This 6971 service is invoked by the gateway MSC. 6972 The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in 6973 table 12.3/1.

6974
6975

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

6976

6977
6978 Invoke id

12.3.3 Parameter use

6979 See definition in clause 7.6.1. 6980 MSISDN 6981 See definition in clause 7.6.2. 6982 Service Centre Address 6983 See definition in clause 7.6.2.

814

3GPP

6984 SM Delivery Outcome 6985 See definition in clause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. 6986 Absent Subscriber Diagnostic SM 6987 See definition in clause 7.6.8. 6988 GPRS Support Indicator 6989 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of two 6990 delivery outcomes. 6991 Delivery Outcome Indicator 6992 See definition in clause 7.6.8. 6993 Additional SM Delivery Outcome 6994 See definition in clause 7.6.8. 6995 Additional Absent Subscriber Diagnostic SM 6996 See definition in clause 7.6.8. 6997 MSIsdn-Alert 6998 See definition in clause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN 6999 received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned 7000 to the gateway MSC. 7001 User error 7002 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7003 7004 7005 7006

815 Release 6 816 817

205

3GPP TS 29.002 V6.11.0 (2005-09)

Unknown Subscriber; Message Waiting List Full; Unexpected Data Value; Data missing.

7007 Provider error 7008 For definition of provider errors see clause 7.6.1.

7009 7010

12.4 MAP-READY-FOR-SM service


12.4.1 Definition

7011 This service is used between the MSC and VLR as well as between the VLR and the HLR. The MSC initiates this 7012 service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. 7013 The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the 7014 MSC. 7015 Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates 7016 memory available situation. The SGSN uses the service to indicate this to the HLR. 7017 The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in 7018 the GPRS. 7019 The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1.

818

3GPP

7020

819 Release 6 820 821

206

3GPP TS 29.002 V6.11.0 (2005-09)

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

7021

C(=) O

7022

7023
7024 Invoke id

12.4.3 Parameter use

7025 See definition in clause 7.6.1. 7026 IMSI 7027 See definition in clause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the 7028 HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI. 7029 TMSI 7030 See definition in clause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR. 7031 Alert Reason 7032 See definition in clause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory 7033 available. 7034 Alert Reason Indicator 7035 See definition in clause 7.6.8. 7036 User error 7037 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7038 7039 7040 7041 7042

Unknown Subscriber; Facility Not Supported; System Failure; Unexpected Data Value; Data missing.

7043 Provider error 7044 For definition of provider errors see clause 7.6.1.

7045 7046

12.5 MAP-ALERT-SERVICE-CENTRE service


12.5.1 Definition

7047 This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects 7048 that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available.

822

3GPP

7049 The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1.

823 Release 6 824 825

207

3GPP TS 29.002 V6.11.0 (2005-09)

7050
7051

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

7052

7053
7054 Invoke id

12.5.3 Parameter use

7055 See definition in clause 7.6.1. 7056 MSIsdn-Alert 7057 See definition in clause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data file. 7058 Service Centre Address 7059 See definition in clause 7.6.2. 7060 User error 7061 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7062 7063 7064

System Failure; Unexpected Data Value; Data missing.

7065 Provider error 7066 For definition of provider errors see clause 7.6.1.

7067 7068
7069 7070 7071 7072

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.

7073 Additionally the status of MCEF, MNRF and MNRG flags and the inclusion of the particular Service Centre address in 7074 the Message Waiting Data list is informed to the gateway MSC when appropriate. 7075 If the HLR has stored a single MNRR, the value is included in the Absent Subscriber Diagnostic SM parameter. 7076 If the HLR has stored a second MNRR, the value of the MNRR for the MSC is included in the Absent Subscriber 7077 Diagnostic SM parameter and the value of the MNRR for the SGSN is included in the Additional Absent Subscriber 7078 Diagnostic SM parameter. 7079 The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1.

826

3GPP

7080

827 Release 6 828 829

208

3GPP TS 29.002 V6.11.0 (2005-09)

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

7081

7082

7083
7084 Invoke id

12.6.3 Parameter use

7085 See definition in clause 7.6.1. 7086 MSIsdn-Alert 7087 See definition in clause 7.6.2. This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR. 7088 MWD Status 7089 See definition in clause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the status 7090 of the particular SC address presence in the Message Waiting Data list. 7091 Absent Subscriber Diagnostic SM 7092 See definition in clause 7.6.8. 7093 Additional Absent Subscriber Diagnostic SM 7094 See definition in clause 7.6.8.

7095 7096

12.7 MAP-SEND-INFO-FOR-MT-SMS service


12.7.1 Definition

7097 This service is used between the MSC and the VLR. The service is invoked by the MSC receiving a mobile terminated 7098 short message to request subscriber related information from the VLR. 7099 The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1.

7100
7101

12.7.2 Service primitives


Table 12.7/1: MAP-SEND-INFO-FOR-MT-SMS
Parameter name Invoke Id SM RP DA IMSI MSISDN User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O

7102

7103

12.7.3 Parameter use


3GPP

830

7104 Invoke id

831 Release 6 832 833

209

3GPP TS 29.002 V6.11.0 (2005-09)

7105 See definition in clause 7.6.1. 7106 SM RP DA 7107 See definition in clause 7.6.8. This parameter shall contain either an IMSI or an LMSI. 7108 IMSI 7109 See definition in clause 7.6.2. This parameter shall be present if the SM RP DA parameter contains an LMSI; otherwise 7110 it shall be absent. 7111 MSISDN 7112 See definition in clause 7.6.2. 7113 User error 7114 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7115 7116 7117 7118 7119 7120 7121 7122 7123

Unknown subscriber; Unidentified Subscriber; Absent subscriber; Unexpected Data Value; Data Missing; Illegal subscriber; Illegal equipment; Subscriber busy for MT SMS; System Failure.

7124 Provider error 7125 For definition of provider errors see clause 7.6.1.

7126 7127

12.8 MAP-SEND-INFO-FOR-MO-SMS service


12.8.1 Definition

7128 This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile 7129 originated short message request to request the subscriber related information from the VLR. 7130 The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1.

7131
7132

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

7133

834

3GPP

7134

835 Release 6 836 837

210

3GPP TS 29.002 V6.11.0 (2005-09)

12.8.3 Parameter use

7135 Invoke id 7136 See definition in clause 7.6.1. 7137 Service Centre Address 7138 See definition in clause 7.6.2. 7139 MSISDN 7140 See definition in clause 7.6.2. 7141 User error 7142 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7143 7144 7145 7146

Teleservice Not Provisioned; Call Barred; Unexpected Data Value; Data Missing.

7147 Provider error 7148 For definition of provider errors see clause 7.6.1.

7149 7150

12.9 MAP-MT-FORWARD-SHORT-MESSAGE service


12.9.1 Definition

7151 This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile terminated short 7152 messages. 7153 The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 7154 table 12.9/1.

7155
7156

12.9.2 Service primitives


Table 12.9/1: MAP-MT-FORWARD-SHORT-MESSAGE
Parameter name Invoke Id SM RP DA SM RP OA SM RP UI More Messages To Send User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O

7157

7158
7159 Invoke id

12.9.3 Parameter use

7160 See definition in clause 7.6.1. 7161 SM RP DA

838

3GPP

7162 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 7163 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 7164 available. 7165 This parameter is omitted in the mobile terminated subsequent SM transfers. 7166 SM RP OA 7167 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in 7168 this parameter. 7169 This parameter is omitted in the mobile terminated subsequent SM transfers. 7170 SM RP UI 7171 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 7172 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message 7173 delivery acknowledgement from the MSC or from the SGSN to the Service Centre. 7174 More Messages To Send 7175 See definition in clause 7.6.8. The information from the MMS indication received from the Service Centre is inserted in 7176 this parameter. 7177 User error 7178 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7179

839 Release 6 840 841

211

3GPP TS 29.002 V6.11.0 (2005-09)

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.

7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193

Unexpected Data Value; Data Missing.

7194 Provider error 7195 For definition of provider errors see clause 7.6.1.

7196

13

Network-Requested PDP Context Activation services

842

3GPP

843 Release 6 844 845

212

3GPP TS 29.002 V6.11.0 (2005-09)

7197 7198

13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service


13.1.1 Definition

7199 This service is used by the GGSN to request GPRS routing information from the HLR.

7200
7201

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

7202

7203
7204 Invoke Id

13.1.3 Parameter definition and use

7205 See definition in clause 7.6.1. 7206 IMSI 7207 See definition in clause 7.6.2. 7208 GGSN address 7209 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 7210 GGSN number 7211 See definition in clause 7.6.2. 7212 SGSN address 7213 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 7214 process in the HLR is positive. 7215 Mobile Not Reachable Reason 7216 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 7217 process in the HLR is positive and the MNRG flag in the HLR is set. See definition in clause 7.6.3.51. 7218 User error 7219 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 7220 7221 7222 7223 7224

Absent Subscriber; System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

7225 The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown.

846

3GPP

7226 7227 7228

847 Release 6 848 849

213

3GPP TS 29.002 V6.11.0 (2005-09)

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

7229 Provider error 7230 These are defined in clause 7.6.1.

7231 7232

13.2 MAP_FAILURE_REPORT service


13.2.1 Definition

7233 This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed.

7234
7235

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

7236

7237
7238 Invoke Id

13.2.3 Parameter definition and use

7239 See definition in clause 7.6.1. 7240 IMSI 7241 See definition in clause 7.6.2. 7242 GGSN address 7243 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 7244 GGSN number 7245 See definition in clause 7.6.2. 7246 User error 7247 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 7248 7249 7250 7251

System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

7252 Provider error 7253 These are defined in clause 7.6.1.

850

3GPP

851 Release 6 852 853

214

3GPP TS 29.002 V6.11.0 (2005-09)

7254 7255

13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service


13.3.1 Definition

7256 This service is used by the HLR to inform the GGSN that the MS is present for GPRS again.

7257
7258

13.3.2 Service primitives


Table 13.3/1: MAP_NOTE_MS_PRESENT_FOR_GPRS
Parameter name Invoke id IMSI GGSN address SGSN address User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) Confirm M(=)

C(=) O

7259

7260
7261 Invoke Id

13.3.3 Parameter definition and use

7262 See definition in clause 7.6.1. 7263 IMSI 7264 See definition in clause 7.6.2. 7265 GGSN address 7266 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 7267 SGSN address 7268 See definition in clause 7.6.2. 7269 User error 7270 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 7271 7272 7273 7274

System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

7275 Provider error 7276 These are defined in clause 7.6.1.

7277 7278 7279

13A

Location Service Management Services


13A.1MAP-SEND-ROUTING-INFO-FOR-LCS Service
13A.1.1 Definition

854

3GPP

7280 This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location 7281 service request to the servicing VMSC or SGSN. The MAP-SEND-ROUTING-INFO-FOR-LCS is a confirmed service 7282 using the primitives from table 13A.1/1.

855 Release 6 856 857

215

3GPP TS 29.002 V6.11.0 (2005-09)

7283
7284

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 Supported LCS Capability Sets Additional LCS Capability Sets V-GMLC Address Additional V-GMLC Address H-GMLC Address PPR Address User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) C C C C C C C C U U C U C Confirm M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O

7285

7286
7287 Invoke id

13A.1.3 Parameter Use

7288 See definition in clause 7.6.1. 7289 MLC Number 7290 See definition in clause 7.6.2. 7291 MSISDN 7292 See definition in clause 7.6.2. The request shall carry either the IMSI or MSISDN. The response shall carry whichever 7293 of these was not included in the request (see 3GPP TS 23.271 for details). 7294 IMSI 7295 See definition in clause 7.6.2. 7296 LMSI 7297 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 7298 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 7299 Network Node Number 7300 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 7301 Additional Number are received in the GMLC, the Network Node Number is used in preference to the Additional 7302 Number. 7303 GPRS Node Indicator 7304 See definition in clause 7.6.8. The presence of this parameter is mandatory only if the SGSN number is sent in the 7305 Network Node Number.

858

3GPP

7306 Additional Number 7307 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 7308 Additional Number are received in the GMLC, the Network Node Number is used in preference to the Additional 7309 Number. 7310 Supported LCS Capability Sets 7311 See definition in clause 7.6.11. This parameter indicates the LCS capability of the serving node that is indicated by the 7312 Network Node Number. This parameter is provided only if LCS capability sets are available in HLR and Network Node 7313 Number is present in this message. 7314 Additional LCS Capability Sets 7315 See definition in clause 7.6.11. This parameter indicates the LCS capability of the serving node that is indicated by the 7316 Additional Number. This parameter is provided only if LCS capability sets are available in HLR and Additional 7317 Number is present in this message. 7318 V-GMLC address 7319 See definition in clause 7.6.2. . This parameter indicates the V-GMLC address of the serving node that is indicated by 7320 the Network Node Number. 7321 Additional V-GMLC address 7322 See definition in clause 7.6.2. This parameter indicates the V-GMLC address of the serving node that is indicated by the 7323 Additional Number. This parameter is provided only if additional LCS capability sets are available in HLR and 7324 Additional Number is present in this message. 7325 H-GMLC address 7326 See definition in clause 7.6.2. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7327 PPR address 7328 See definition in clause 7.6.2. 7329 User error 7330 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7331 7332 7333 7334 7335 7336 7337 -

859 Release 6 860 861

216

3GPP TS 29.002 V6.11.0 (2005-09)

Unknown subscriber; Absent Subscriber; Facility Not Supported; System failure; Unexpected Data Value; Data missing; Unauthorised requesting network.

7338 Provider error 7339 For definition of provider errors see clause 7.6.1.

7340 7341

13A.2MAP-PROVIDE-SUBSCRIBER-LOCATION Service
13A.2.1 Definition

7342 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 7343 is a confirmed service using the primitives from table 13A.2/1.

862

3GPP

7344

863 Release 6 864 865

217

3GPP TS 29.002 V6.11.0 (2005-09)

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 LCS Codeword LCS Service Type Id LCS Privacy Check Area Event Info H-GMLC Address Location Estimate GERAN Positioning Data UTRAN Positioning Data Age of Location Estimate Additional Location Estimate Deferred MT-LR Response Indicator Cell Id Or SAI Accuracy Fulfilment Indicator User error Provider error Request M M M M U C C C C C U C C C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

7345

M C C C C C C C C

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

7346

7347

13A.2.3 Parameter Definition and Use

7348 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 7349 specified in 3GPP TS 23.271 [26a]. 7350 Location Type 7351 This parameter identifies the type of location information requested. 7352 MLC Number 7353 This is the E.164 number of the requesting GMLC. 7354 LCS Client ID 7355 This parameter provides information related to the identity of an LCS client. 7356 Privacy Override 7357 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC or SGSN for an 7358 MT-LR are in the same country. 7359 IMSI 7360 The IMSI is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 7361 MSISDN

866

3GPP

7362 The MSISDN is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 7363 LMSI 7364 The LMSI shall be provided if previously supplied by the HLR. This parameter is only used in the case of the MT-LR 7365 for CS domain. 7366 LCS Priority 7367 This parameter indicates the priority of the location request. 7368 LCS QoS 7369 This parameter indicates the required quality of service in terms of response time and accuracy. 7370 IMEI 7371 The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7372 Supported GAD Shapes 7373 This parameter indicates which of the shapes defined in 3GPP TS 23.032 [122] are supported. 7374 LCS-Reference Number 7375 This parameter shall be included if a deferred MT-LR procedure is performed for a UE available event or an area event. 7376 LCS Codeword 7377 See definition in clause 7.6.11.18. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7378 LCS Service Type Id 7379 See definition in clause 7.6.11.15. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7380 LCS Privacy Check 7381 See definition in clause 7.6.11. The requirements for its and its components presence are specified in 3GPP TS 23.271 7382 [26a]. 7383 Area Event Info 7384 See definition in clause 7.6.11. The parameter shall be included if a deferred MT-LR procedure is performed for an area 7385 event. 7386 H-GMLC address 7387 See definition in clause 7.6.2. The parameter shall be included if a deferred MT-LR procedure is performed for a UE 7388 available event or an area event. 7389 Location Estimate 7390 This parameter provides the location estimate if this is encoded in one of the supported geographical shapes. Otherwise 7391 this parameter shall consist of one octet, which shall be discarded by the receiving node. 7392 GERAN Positioning Data 7393 7394 7395 7396

867 Release 6 868 869

218

3GPP TS 29.002 V6.11.0 (2005-09)

This parameter indicates the usage of each positioning method that was attempted to determine the location estimate either successfully or unsuccessfully. If Positioning Data received from the RAN contains no Positioning Methods, Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is GERAN, see 3GPP TS 23.271 [26a].

7397 UTRAN Positioning Data 7398 This parameter indicates the usage of each positioning method that was successfully attempted to determine the location 7399 estimate. If Position Data received from the RAN contains no Positioning Methods, UTRAN Positioning Data is

870

3GPP

7400 excluded from the MAP message. It may be included in the message only if the access network is UTRAN, see 3GPP 7401 TS 23.271 [26a]. 7402 7403 Age of Location Estimate 7404 This parameter indicates how long ago the location estimate was obtained. 7405 Additional Location Estimate 7406 This parameter provides the location estimate when not provided by the Location Estimate parameter. It may be sent 7407 only if the parameter Supported GAD Shapes has been received in the Provide Subscriber Location indication and the 7408 shape to be included is supported by the GMLC. 7409 Deferred MT-LR Response Indicator 7410 See definition in clause 7.6.11.2. 7411 Cell Id Or SAI 7412 7413 7414 7415 7416 7417 Accuracy Fulfilment Indicator 7418 See definition in clause 7.6.11.27. 7419 User error 7420 This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one 7421 of the following values defined in clause 7.6.1. 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 -

871 Release 6 872 873

219

3GPP TS 29.002 V6.11.0 (2005-09)

For GERAN access, this parameter indicates Global Cell Identifier of the cell that the served subscriber is currently attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is currently attached to. This parameter is included only for North American Emergency Calls as described in 3GPP TS 23.271 [26a].

System Failure; 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.

7433 Provider error 7434 These are defined in clause 7.6.1.

7435

13A.3MAP-SUBSCRIBER-LOCATION-REPORT Service

874

3GPP

7436

875 Release 6 876 877

220

3GPP TS 29.002 V6.11.0 (2005-09)

13A.3.1 Definition

7437 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 7438 is either implicitly administered or made at some earlier time. This is a confirmed service using the primitives from 7439 table 13A.3/1.

7440
7441

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 GERAN Positioning Data UTRAN Positioning Data Age of Location Estimate LMSI GPRS Node Indicator Additional Location Estimate Deferred MT-LR Data LCS-Reference Number NA-ESRK Request Cell Id Or SAI H-GMLC Address LCS Service Type Id Pseudonym Indicator User error Provider error Request M M M M C C C C U C C C C U C C C C C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=)

C(=) O

7442

7443

13A.3.3 Parameter Definition and Use

7444 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 7445 specified in. 3GPP TS 23.271 [26a]. 7446 LCS Event 7447 This parameter indicates the event that triggered the Subscriber Location Report. 7448 LCS Client ID 7449 This parameter provides information related to the identity of the recipient LCS client. 7450 Network Node Number 7451 See definition in clause 7.6.2. This parameter provides the address of the sending node. 7452 IMSI 7453 The IMSI shall be provided if available to the VMSC or SGSN. 7454 MSISDN 7455 The MSISDN shall be provided if available to the VMSC or SGSN. 7456 NA-ESRD

878

3GPP

7457 If the target MS has originated an emergency service call in North America, the NA-ESRD shall be provided by the 7458 VMSC if available. 7459 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in 7460 Subscriber_Location_Report-Arg, an NA-ESRK or NA-ESRD, but not both, may also be included in the response to 7461 the MSC, see 3GPP TS 23.271 [26a]. 7462 NA-ESRK 7463 If the target MS has originated an emergency service call in North America, the NA-ESRK shall be provided by the 7464 VMSC if assigned. 7465 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in 7466 Subscriber_Location_Report-Arg, an NA-ESRK or NA-ESRD, but not both, may also be included in the response to 7467 the MSC, see 3GPP TS 23.271 [26a]. 7468 IMEI 7469 The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7470 Location Estimate 7471 This parameter provides the location estimate. The absence of this parameter implies that a location estimate was not 7472 available or could not be successfully obtained. If the obtained location estimate is not encoded in one of the supported 7473 geographical shapes then this parameter shall consist of one octet, which shall be discarded by the receiving node. 7474 GERAN Positioning Data 7475 7476 7477 7478

879 Release 6 880 881

221

3GPP TS 29.002 V6.11.0 (2005-09)

This parameter indicates the usage of each positioning method that was attempted to determine the location estimate either successfully or unsuccessfully. If Positioning Data received from the RAN contains no Positioning Methods, Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is GERAN, see 3GPP TS 23.271 [26a].

7479 UTRAN Positioning Data 7480 7481 7482 7483

This parameter indicates the usage of each positioning method that was successfullyattempted to determine the location estimate. If Position Data received from the RAN contains no Positioning Methods, UTRAN Positioning Data is excluded from the MAP message. It may be included in the message only if the access network is UTRAN, see 3GPP TS 23.271 [26a].

7484 Age of Location Estimate 7485 This parameter indicates how long ago the location estimate was obtained. 7486 LMSI 7487 The LMSI may be provided if assigned by the VLR. 7488 GPRS Node Indicator 7489 See definition in clause 7.6.8. This presence of this parameter is mandatory only if the SGSN number is sent in the 7490 Network Node Number. 7491 Additional Location Estimate 7492 This parameter provides the location estimate when not provided by the Location Estimate parameter.. 7493 Deferred MT-LR Data 7494 See definition in clause 7.6.11.3. 7495 LCS-Reference Number 7496 This parameter shall be included if the Subscriber Location Report is the response to a deferred MT location request. 7497 NA-ESRK Request

882

3GPP

7498 If the target MS has originated an emergency service call in North America, NA-ESRK Request may be included to 7499 indicate that the MSC is able to accept NA-ESRK in the Response message, see section 7.6.11.19. 7500 Cell Id Or SAI 7501 7502 7503 7504

883 Release 6 884 885

222

3GPP TS 29.002 V6.11.0 (2005-09)

For GERAN access, this parameter indicates Global Cell Identifier of the cell that the served subscriber is currently attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is currently attached to. This parameter is included only for North American Emergency Calls as described in 3GPP TS 23.271 [26a].

7505 H-GMLC address 7506 See definition in clause 7.6.2. The parameter shall be included if the Subscriber Location Report is the response to a 7507 deferred MT location request for a UE available event or an area event. 7508 LCS Service Type Id 7509 See definition in clause 7.6.11.15. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7510 Pseudonym Indicator 7511 This parameter indicates by its presence that the pseudonym is required. Refer to 3GPP TS 23.271 [26a]. 7512 User error 7513 This parameter is sent by the responder when the received message contains an error, cannot be forwarded or stored for 7514 an LCS client or cannot be accepted for some other reason and if present, takes one of the following values defined in 7515 clause 7.6.1. 7516 7517 7518 7519 7520 7521 7522 -

System Failure; Data Missing; Unexpected Data Value; Resource Limitation; Unknown Subscriber; Unauthorised requesting network; Unknown or unreachable LCS Client.

7523 Provider error 7524 These are defined in clause 7.6.1.

7525 7526 7527 7528 7529 7530 7531

13A.4Void
13A.4.1 Void 13A.4.2 Void 13A.4.3 Void

13A.5Void
13A.5.1 Void 13A.5.2 Void
3GPP

886

7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548

887 Release 6 888 889

223

3GPP TS 29.002 V6.11.0 (2005-09)

13A.5.3 Void

13A.6Void
13A.6.1 Void 13A.6.2 Void 13A.6.3 Void

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

7549 7550

14

General
14.1 Overview

7551 Clauses 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. 7552 Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping onto TC service 7553 primitives. Clause 17 specifies the application contexts, operation packages and abstract syntaxes for the MAP protocol 7554 as well as the encoding rules to be applied.

890

3GPP

891 Release 6 892 893

224

3GPP TS 29.002 V6.11.0 (2005-09)

7555

14.2 Underlying services

7556 The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of Signalling System Number 7557 No. 7, as referenced in clause 6.

7558
7559 7560 7561 7562

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

7563 A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a TC-BEGIN 7564 indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific service invoked 7565 during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is created at the performer's side. 7566 This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not intended to 7567 suggest any implementation. SDL descriptions are organised according to this model. 7568 How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local 7569 implementation matter. 7570 How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter.

7571

14.4 Conventions

7572 The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major 7573 difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do 7574 not belong to the so-called "version one context set". 7575 The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1 implementation 7576 according to the latest phase 1 version of GSM 09.02. This set is defined in clause 15. 7577 The procedures described in clause 15 are used when the application-context-name does not refer to a dialogue between 7578 an MSC and its VLR. When the application-context-name refers to a dialogue between an MSC and its VLR the MAP 7579 PM procedures are a local implementation matter.

7580 7581
7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596

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.

894

3GPP

7597 Unknown operations may be invoked in the following types of message (there is no restriction as to how many 7598 unknown operations can be invoked in a message): 7599 7600 7601 7602 7603 7604 7605

895 Release 6 896 897

225

3GPP TS 29.002 V6.11.0 (2005-09)

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

7606 The TC-REJECT component may be sent in the following messages: 7607 7608 7609 7610 7611 7612 7613 7614 7615

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.

7616 Note that the SDL diagrams of clauses 19 - 25 do not show the report to the MAP-Service User about the reception of 7617 the unknown operation. This has been done for simplicity of description; the MAP PM may inform the MAP-Service 7618 User. 7619 The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown 7620 operation.

7621

15.2 Dialogue establishment

7622 The establishment of a MAP dialogue involves two MAP-service-users: the dialogue-initiator and the dialogue7623 responder. 7624 This procedure is driven by the following signals: 7625 7626 7627 7628

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;

7629 and under specific conditions: 7630 7631 7632

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.

7633 One instance of the MAP dialogue state machine runs at the initiating side, and one at the responding side.

7634

15.2.1 Behaviour at the initiating side

7635 The behaviour of the MAP dialogue state machine at the initiating side is defined in sheets 1 9 of the process 7636 Secure_MAP_DSM.

898

3GPP

7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648

899 Release 6 900 901

226

3GPP TS 29.002 V6.11.0 (2005-09)

Sheet 1: The MAP protocol machine decides according to the application context name received in the MAP-OPEN request and the identity of the responder whether secure transport of the MAP dialogue is required, and if so what level of protection is required. This decision is based on bilateral agreements between the operators of the network entities concerned; it requires the dialogue initiating entity to store configuration information on which the decision is based. Secure transport of a MAP dialogue is required if any of the operation components (invoke, result or error) used in the application context for the dialogue requires secure transport, as shown in 3GPP TS 33.200. If a dialogue uses secure transport then MAP secure transport services shall be used with a protection mode of "No protection" to produce the same functional effect as unsecured transport for those components which do not need protection. If secure transport is required, the MAP protocol machine builds a protected dialogue portion (including the AC name and any user information received in the MAP-OPEN request, encoded as user information for the TC-BEGIN) for the TC-BEGIN; otherwise it builds a normal dialogue portion using the application context name and any user data included in the MAP-OPEN request.

7649 Sheet 2: If secure transport is used, each MAP specific service request is stored in case drop-back to unsecured transport 7650 is to be invoked. 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660

Sheet 2: If secure transport is required, each MAP specific service request triggers the creation of an instance of the Secure_Requesting_MAP_SSM to handle the secure transport of the request. If secure transport is not required, each MAP specific service request triggers the creation of an instance of the Requesting_MAP_SSM to handle the transport of the request. Sheet 3: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, a TC-END indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the dialogue. If secure transport is required, acceptance of the dialogue opening request which was transported in the secure dialogue opening request is indicated by the encapsulated AC name transported in the user information of the TC-END being equal to the encapsulated AC which was included in the user information of the TC-BEGIN. Mismatch of either the AC name or the encapsulated AC name indicates failure of the dialogue opening.

7661 Sheet 3: If the dialogue opening is accepted, any components included in the TC-END are processed and passed to the 7662 MAP-Service User. The dialogue is closed by sending a MAP-CLOSE to the MAP-Service User. 7663 Sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8, sheet 9: when a dialogue is terminated, the MAP dialogue state 7664 machine terminates all instances of the Requesting_MAP_SSM or Secure_Requesting_MAP_SSM which are active for 7665 this dialogue. 7666 Sheet 4, sheet 5: It is a matter for agreement between the operators of the network entities involved whether fallback to 7667 unsecured transport is acceptable if secure transport is not possible. This requires the dialogue initiating entity to store 7668 configuration information on which this decision is based. 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689

Sheet 4: A TC-P-ABORT with an abort parameter Incorrect_Transaction_Portion indicates that the responding side does not support a MAP version higher than 1. If secure transport is not required, this triggers a MAP-OPEN confirm indicating that the dialogue is refused, with a refuse reason potential version incompatibility. The MAP-Service User may then decide to retry the dialogue at MAP version 1. If secure transport is required and fallback to unsecured transport is acceptable, the dialogue machine retries the dialogue with unsecured transport. If secure transport is required and fallback to unsecured transport is not acceptable, this triggers a MAP-OPEN confirm indicating that the dialogue is refused, with a refuse reason secured transport not possible. No retry of the dialogue with a lower version is allowed. Sheet 5: If the initiating side receives a TC-U-ABORT with an abort reason AC not supported and secure transport is required, then secured transport is not possible. If fallback to unsecured transport is acceptable, the dialogue machine retries the dialogue with unsecured transport. If fallback to unsecured transport is not acceptable, this triggers a MAPOPEN confirm indicating that the dialogue is refused, with a refuse reason secured transport not possible. No retry of the dialogue with a lower version is allowed. Sheet 7: A TC-U-ABORT with a user-specific abort reason leads to a check of the user information. User information carrying a MAP-Refuse PDU with a refuse reason encapsulated AC not supported means that the responding entity supports the secure transport AC, but not the AC required for the protected request. This triggers a MAP-OPEN confirm indicating that the dialogue is refused, with a refuse reason AC not supported. The MAP-Service User may then decide to retry the dialogue with a lower AC version; this will again use secure transport. User information carrying a MAPRefuse PDU with a refuse reason transport protection not adequate means that the responding entity is not prepared to accept a dialogue with the protection mode offered by the initiating entity: either unsecured transport or secured transport with an inadequate protection mode.

902

3GPP

7690 7691 7692 7693 7694 7695

903 Release 6 904 905

227

3GPP TS 29.002 V6.11.0 (2005-09)

Sheet 9: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, a TC-CONTINUE indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the dialogue. If secure transport is required, acceptance of the dialogue opening request which was transported in the secure dialogue opening request is indicated by the encapsulated AC name transported in the user information of the TCCONTINUE being equal to the encapsulated AC which was included in the user information of the TC-BEGIN. Mismatch of either the AC name or the encapsulated AC name indicates failure of the dialogue opening.

7696 Sheet 9: If the dialogue opening is accepted, any components included in the TC-CONTINUE are processed and passed 7697 to the MAP-Service User. The dialogue has then reached the established state.

7698

15.2.2 Behaviour at the responding side

7699 The behaviour of the MAP dialogue state machine at the responding side is defined in sheets 10 15 of the process 7700 Secure_MAP_DSM. 7701 Sheet 10: If no application context information is included in the TC-BEGIN indication, this implies a MAP version 1 7702 dialogue. An explicit application context indicating version 1 is treated as abnormal behaviour. 7703 7704 7705 7706

Sheet 10, sheet 12: The test "Unsecured_Transport_Permitted" takes the "True" exit if there is an agreement between the operators of the dialogue initiating entity and the dialogue responding entity to allow unsecured transport for the application context for the requested dialogue. This requires the dialogue responding entity to store configuration information on which this decision is based.

7707 Sheet 10: The task "Extract_User_Information" includes decryption of the protected user information if confidentiality 7708 protection has been applied. 7709 Sheet 10: The test "Protection mode correct" takes the "yes" exit if the protection mode is acceptable to the receiving 7710 entity, based on the identity of the sending entity and the encapsulated application context for the requested dialogue. 7711 Sheet 12: The v1 application context name which corresponds to a v1 operation is derived using the information in table 7712 15.2/1. 7713

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

7714

7719 7720 7721 7722 7723

7715 7716 7717 7718

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.

Sheet 13: If the AC name received in the TC-BEGIN indicated that secure transport is required, the MAP dialogue state machine checks whether the encapsulated application context name is supported. If it is supported, the dialogue can be accepted. If the encapsulated AC name is not supported, the MAP dialogue machine indicates this by sending a TC-UABORT with a user-specific abort reason and user information indicating that the encapsulated AC name is not supported.

906

3GPP

7724 Sheet 14: If the dialogue is accepted, each component present in the TC-BEGIN is forwarded to an instance of a 7725 Performing_MAP_SSM or Secure_Performing MAP_SSM, by executing the procedure Process_Components. 7726 Sheet 15: If the MAP dialogue state machine receives a MAP-OPEN confirm with a result accepted, it waits for any 7727 MAP specific service request or response primitives or a MAP-DELIMITER request. 7728 Sheet 14, sheet 15: When a dialogue is terminated, the MAP dialogue state machine terminates all instances of the 7729 Requesting_MAP_SSM, Secure_Requesting_MAP_SSM, Performing_MAP_SSM or Secure_Performing_MAP_SSM 7730 which are active for this dialogue. 7731 Sheet 15: A MAP-DELIMITER request triggers a TC-CONTINUE request to accept the dialogue. The dialogue has 7732 then reached the established state.

907 Release 6 908 909

228

3GPP TS 29.002 V6.11.0 (2005-09)

7733

15.3 Dialogue continuation

7734 Once established the dialogue is said to be in a continuation phase. The behaviour of the MAP dialogue state machine in 7735 this phase is defined in sheets 16 18 of the process Secure_MAP_DSM. 7736 Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue. 7737 Normal closure of an established dialogue is shown on sheet 17; abnormal termination is shown on sheet 18.

7738

15.4 Load control

7739 If an entity which should respond to a MAP dialogue opening request is overloaded, it uses the AC of the request to 7740 determine whether to discard the request. If the AC of the request is secure transport, the encapsulated AC (i.e. the AC 7741 of the dialogue for which secure transport is required) is used to determine whether the request is discarded. 7742 The priority level allocated to each application-context is described in clause 5, tables 5.1/1 and 5.1/2.

7743

15.5 Procedures for MAP specific services

7744 This clause describes the MAP procedures for MAP specific services. These procedures are driven by the following 7745 types of event: 7746 7747

a MAP specific request or a MAP specific response primitive; a component handling primitive from TC.

7748 A Service State Machine is activated when of one of the following signals is received: 7749 7750

a MAP request primitive, which activates a requesting SSM; a TC-INVOKE indication primitive without a linked identifier, which activates a performing SSM.

7751 For component handling primitives there are two types of event: 7752 7753

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.

7754
7755 7756 7757 7758

15.5.1 Service invocation for unsecured dialogues


The behaviour of the requesting SSM which handles a service for an unsecured dialogue 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.

7759 The response to a MAP service invocation may come in the form of a linked request. If the linked request corresponds 7760 to a class 4 operation, this is handled by the requesting SSM. If the linked request corresponds to a class 1, 2 or 3 7761 operation, the MAP dialogue state machine sends a notification to the requesting SSM and creates an instance of a

910

3GPP

7762 performing SSM to handle the linked request. The test "Linked_Operation_Allowed" on sheet 3 of the process 7763 Requesting_MAP_SSM takes the (TRUE) exit if the definition of the parent operation includes the received linked 7764 operation as a permitted linked operation; otherwise the test takes the (FALSE) exit. 7765 The mapping of MAP specific services on to remote operations is given in table 16.2/1.

911 Release 6 912 913

229

3GPP TS 29.002 V6.11.0 (2005-09)

7766
7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782

15.5.2 Service invocation for secured dialogues


The behaviour of the requesting SSMs which handle a service for a secured dialogue is defined by the SDL for the processes Secure_Requesting_MAP_SSM and Requesting_MAP_SSM. The secure requesting SSM receives a MAP service request from the MAP-Service User via the MAP dialogue state machine and constructs the corresponding MAP secure transport service request. It then creates an instance of the requesting SSM and sends the MAP secure transport service request to it. The requesting SSM sends a TC-INVOKE request to TCAP. When the MAP dialogue state machine receives a confirm from TCAP, it forwards it to the secure requesting SSM, which unpacks the MAP service confirm from the MAP secure transport service confirm and sends it to the requesting SSM. The requesting SSM forwards the MAP service confirm to the MAP-Service User. The response to a MAP service invocation which was carried in a secure dialogue may come in the form of a linked request. This linked request is carried in a MAP secure transport service request of the class corresponding to the operation; however the MAP secure transport service request is not linked to another MAP secure transport service request. If the linked request which is carried in the MAP secure transport service corresponds to a class 4 operation, this is handled by the secure requesting service state machine, which unpacks the linked request and sends it to the requesting SSM. If the linked request which is carried in the MAP secure transport service corresponds to a class 1, 2 or 3 operation, the MAP dialogue state machine sends a notification to the secure requesting SSM (which passes the notification to the requesting SSM) and creates an instance of a secure performing SSM to handle the linked request.

7783
7784 7785 7786 7787 7788

15.5.3 Service invocation receipt for unsecured dialogues


The behaviour of the performing SSM which handles a service for an unsecured dialogue is defined by the SDL for the process Performing_MAP_SSM. The performing SSM receives a TC-INVOKE component from TCAP via the MAP dialogue state machine and sends a MAP service indication to the MAP-Service User. When a MAP service response is received from the MAP-Service User via the MAP dialogue state machine, the performing SSM forwards a TCRESULT or TC-U-ERROR component to TCAP.

7789
7790 7791 7792 7793 7794 7795 7796 7797

15.5.4 Service invocation receipt for secured dialogues


The behaviour of the performing SSMs which handle a service for a secured dialogue is defined by the SDL for the processes Secure_Performing_MAP_SSM and Performing_MAP_SSM. The secure performing SSM receives a TCINVOKE component containing a secure MAP transport service from TCAP via the MAP dialogue state machine and unpacks the MAP service indication from it. It then creates an instance of the performing SSM and sends the MAP service indication to it. The performing SSM forwards the MAP service indication to the MAP-Service User. When the MAP dialogue state machine receives a MAP service response from the MAP-Service User it forwards it to the secure performing SSM. The secure performing SSM constructs a MAP secure transport service response and sends it to the performing SSM, which forwards a TC-RESULT or TC-U-ERROR component to TCAP.

7798

15.5.5 Handling of components received from TC

7799 The procedure Process_Components shows the handling of components received in a TC-BEGIN, TC-CONTINUE or 7800 TC-END message. 7801 Sheet 1: If a linked invoke component is transported securely, the linked invoke ID is carried as part of the security 7802 header, so that it can be checked without the need to unpack the protected component. 7803 7804 7805 7806

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.

914

3GPP

915 Release 6 916 917

230

3GPP TS 29.002 V6.11.0 (2005-09)

7807

15.6 SDL descriptions

7808 The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. 7809 Such a system resides in each network component supporting MAP and communicates with its peers via the lower 7810 layers of the signalling network which are part of the environment. 7811 Only the MAP-provider is fully described in this clause. The various types of processes which form the MAP-User 7812 block and the TC block are described respectively in clauses 18 to 25 of the present document and in CCITT 7813 Recommendation Q.774. 7814 The MAP-Provider block communicates with the MAP_USER via two channels U1 and U2. Via U1 the MAP-provider 7815 receives the MAP request and response primitives. Via U2 it sends the MAP indication and confirm primitives. 7816 The MAP-Provider block communicates with TC via two channels P1 and P2. Via P1 the MAP-Provider sends all the 7817 TC request primitives. Via P2 it receives all the TC indication primitives. 7818 The MAP-Provider block is composed of the six following types of process: 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838

a) Secure_MAP_DSM: This type of process handles a dialogue for both secured and unsecured 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. For unsecured transport of MAP messages, an instance of this process is created by the instance of the Secure_MAP_DSM process for each requested MAP service. For secured transport of MAP messages, an instance of this process is created by the instance of the Secure_Requesting_MAP_SSM process for each requested MAP-Secure-Transport-service. d) Secure_ Requesting_MAP_SSM: This type of process handles a MAP service requested during a dialogue for secured transport of MAP messages. An instance of this process is created by the Secure_MAP_DSM process for each requested MAP service. e) Performing_MAP_SSM: This type of process handles a MAP service performed during a dialogue. For unsecured transport of MAP messages, an instance of this process is created by the instance of the Secure_MAP_DSM process for each MAP service to be performed. For secured transport of MAP messages, an instance of this process is created by the instance of the Secure_Performing_MAP_SSM process for each MAP-Secure-Transport-service to be performed. f) Secure_Performing_MAP_SSM: This type of process handles a MAP service performed during a dialogue for secured transport of MAP messages. An instance of this process is created by the Secure_MAP_DSM process for each MAP service to be performed.

7839 A process Secure_MAP_DSM exchanges external signals with other blocks as well as internal signals with the other 7840 processes of the MAP-Provider block. The external signals are either MAP service primitives or TC service primitives. 7841 The signal routes used by the various processes are organised as follows: 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851

a) A process Secure_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 Secure_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 Secure_MAP_DSM receives and sends events from/to the LOAD_CTRL process via signal route Load1/Load2. These routes are internal. d) A process Secure_MAP_DSM sends events to the Performing_MAP_SSM processes via signal route Intern1. This route is internal. e) A process Secure_MAP_DSM sends events to the Requesting_MAP_SSM processes via signal route Intern2. This route is internal.

918

3GPP

7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875

919 Release 6 920 921

231

3GPP TS 29.002 V6.11.0 (2005-09)

f) A process Secure_MAP_DSM sends events to the Secure_Performing_MAP_SSM processes via signal route Intern3. This route is internal. g) A process Secure_MAP_DSM sends events to the Secure_Requesting _MAP_SSM processes via signal route Intern4. This route is internal. h) A process Performing_MAP_SSM sends events to the MAP_USER via signal route User3. This route uses channel U2. i) A process Performing_MAP_SSM sends events to the TCAP via signal route TC3. This route uses channel P1. j) A process Requesting_MAP_SSM sends events to the MAP_USER via signal route User4. This route uses channel U2. k) A process Requesting_MAP_SSM sends events to the TCAP via signal route TC4. This route uses channel P1. l) A process Secure_Performing_MAP_SSM sends events to the MAP_USER via signal route User5. This route uses channel U2. m) A process Secure_Performing_MAP_SSM sends events to the TCAP via signal route TC5. This route uses channel P1. n) A process Secure_Performing_MAP_SSM sends events to the corresponding Performing_MAP_SSM process via signal route Intern5. This route is internal. o) A process Secure_Requesting _MAP_SSM sends events to the MAP_USER via signal route User6. This route uses channel U2. p) A process Secure_Requesting _MAP_SSM sends events to the TCAP via signal route TC6. This route uses channel P1. q) A process Secure_Requesting _MAP_SSM sends events to the corresponding Requesting_MAP_SSM process via signal route Intern6. This route is internal.

922

3GPP

923 Release 6 924 925

232

3GPP TS 29.002 V6.11.0 (2005-09)

System Secure_MAP_Stack

1(1)

MAP_USER
U2

(MAP_REQ_SM)

MAP_IND_SP

U1

Secure_MAP_ _Provider TC_REQ_SP

P2

TC_IND_SP

P1

TCAP

7876
7877

Figure 15.6/1: System Secure_MAP_Stack

926

3GPP

927 Release 6 928 929

233

3GPP TS 29.002 V6.11.0 (2005-09)

Block Secure_MAP_Provider

Secure_MAP_Provider1(1)

TC2 TC1 Intern4 Intern2

Secure_ _MAP_DSM

User1 User2 Intern1 Intern3

Load2 Load1 Load_Ctrl Secure_ _Requesting_ _MAP_SSM Intern6 Secure_ _Performing_ _MAP_SSM Intern5

TC6

User6

TC5

User5

TC4

Requesting_ _MAP_SSM

Performing_ _MAP_SSM

User3

TC3

User4

7878
7879

Figure 15.6/2: Block Secure_MAP_Provider

930

3GPP

931 Release 6 932 933

234

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to manage a MAP dialogue Comment 'MAP Dialogue State Machine': DCL Secure_Transport_Required, Components_Present, AC_Name_Unchanged, Encapsulated_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

According to the AC and the identity of the responder

Check_Whether_ Secure_Transport_ Is_Required

Secure_ Transport_ Required (TRUE)

(FALSE)

Set_AC: Secure_ Transport

Store_AC_and_ user_data

For dialogue portion of TC-BEGIN

Build_ Encapsulated_ AC_PDU

WAIT_FOR_ USER_ REQUESTS

7880
7881

Figure 15.6/3a: Process Secure_MAP_DSM (sheet 1)

934

3GPP

935 Release 6 936 937

235

3GPP TS 29.002 V6.11.0 (2005-09)

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

(TRUE) Secure_ Transport_ Required (FALSE)

Set_Abort_ Reason: User_ Specific

Set_User_Info: MAP_User_ Abort_PDU

Store request

TC_U_ABORT_ req_VIA_TC1

Secure_ Requesting_ MAP_SSM

(TRUE) Requesting_ MAP_SSM

Secure_ Transport_ Required (FALSE)

Service_ Invoked_ VIA_Intern4

Service_ Invoked_ VIA_Intern2

TC_BEGIN_ req_VIA_TC1

To all active SRSSMs

Terminated_ VIA_Intern4

Terminated_ VIA_Intern2

To all active RSSMs

WAIT_FOR_ USER_REQUESTS

DIALOGUE_ INITIATED

IDLE

7882
7883

Figure 15.6/3b: Process Secure_MAP_DSM (sheet 2)

938

3GPP

939 Release 6 940 941

236

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM3(17)

TC_END_ ind

TC_ NOTICE_ IND

no AC name unchanged? yes (TRUE) Secure_ Transport_ Required (FALSE) Set_Provider_ Reason: Abnormal_ MAP_Dialogue Set_Refuse_Reason: Node_Not_Reachable Set_Result: Dialogue_Refused

Encapsulated_ AC_Name_ Unchanged (TRUE) Set_Result: Dialogue_ Accepted

(FALSE)

MAP_P_ABORT_ ind_VIA_User2 Set_Result: Dialogue_ Accepted

MAP_OPEN_ cnf_VIA_User2

Secure_ Transport_ Required

(TRUE)

(FALSE) MAP_OPEN_ cnf_VIA_User2 MAP_OPEN_ cnf_VIA_User2 Terminated_ VIA_Intern4

(FALSE) Components_ Present (TRUE)

(FALSE) Components_ Present (TRUE) IDLE

To all active SRSSMs Process_ Components Process_ Components

MAP_CLOSE_ ind_VIA_User2

MAP_CLOSE_ ind_VIA_User2

Terminated_ VIA_Intern3

To all active SPSSMs

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern4

To all active SRSSMs

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

IDLE

IDLE

7884
7885

Figure 15.6/3c: Process Secure_MAP_DSM (sheet 3)

942

3GPP

943 Release 6 944 945

237

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_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 (TRUE)

Else

Secure_ Transport_ Required

Set_Provider_ Reason: Version_ Incompatibility

(FALSE)

Unsecured_ Transport_ Acceptable

(TRUE)

(FALSE)

Set_Result: Dialogue_ Refused

Set_Result: Dialogue_ Refused

MAP_P_ABORT_ ind_VIA_User2

Set_Refuse_Reason: Potential_Version_ Incompatibility

Set_Refuse_Reason: Secured_ Transport_ Not_Possible

Secure_ Transport_ Required (TRUE)

(FALSE)

MAP_OPEN_cnf_ VIA_User2

Indicate 'Dialogue_ Refused'

MAP_OPEN_cnf_ VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

To all active SRSSMs

Terminated_ VIA_Intern4

To all active RSSMs

Terminated_ VIA_Intern2

IDLE

IDLE

IDLE

7886
7887

Figure 15.6/3d: Process Secure_MAP_DSM (sheet 4)

946

3GPP

947 Release 6 948 949

238

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_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 implicitly accepted when something is received

Secure_ Transport_ Required

(TRUE)

(FALSE)

(FALSE)

Secure_ Transport_ Required

(TRUE)

(FALSE) Invoke_ID_ Active (TRUE)

(FALSE) Invoke_ID_ Active (TRUE)

Unsecured_ Transport_ Acceptable

(TRUE) Timer_Expiry_ VIA_Intern2 (FALSE) Timer_Expiry_ VIA_Intern4

Set_Result: Dialogue_ Refused

Set_Result: Dialogue_ Refused

DIALOGUE_ INITIATED

Set_Refuse_ Reason: AC_ Not_Supported

Set_Refuse_Reason: Secured_ Transport_ Not_Possible

MAP_OPEN_ cnf_VIA_User2

MAP_OPEN_cnf_ VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern4

To all active SRSSMs

IDLE

IDLE

7888
7889

Figure 15.6/3e: Process Secure_MAP_DSM (sheet 5)

950

3GPP

951 Release 6 952 953

239

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to manage a MAP dialogue 5

MAP_DSM6(17)

Secure_ Transport_ Required:= FALSE

Terminated_ VIA_Intern4

To all active SRSSMs

Store_AC_and_ user_data

For dialogue portion of TC-BEGIN

(FALSE)

User_ Requests_ Stored (TRUE)

TC_BEGIN_ req_VIA_TC1

Retrieve_ User_ Request

DIALOGUE_ INITIATED

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

7890
7891

Figure 15.6/3f: Process Secure_MAP_DSM (sheet 6)

954

3GPP

955 Release 6 956 957

240

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to manage a MAP dialogue

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

Encapsulated_ AC_Not_ Supported

Invalid_ Destination_ Reference

Invalid_ Originating_ Reference

Transport_ Protection_ Not_Adequate

No_ Reason_ Given

Set_Refuse_ Reason: AC_ Not_Supported

Set_Refuse_Reason: Invalid_Destination_ Reference

Set_Refuse_Reason: Invalid_Originating_ Reference

Set_Refuse_Reason: Transport_Protection_ Not_Adequate

Set_Refuse_Reason: No_Reason_Given

Set_Refuse_Reason: Potential_Version _Incompatibility

MAP_U_ABORT _Ind via USER2

MAP_P_ABORT_ Ind via USER2

MAP_OPEN_ cnf_VIA_User2

(FALSE)

Secure_ Transport_ Required (TRUE)

To all active RSSMs

Terminated_ VIA_Intern2

Terminated_ VIA_Intern4

To all active SRSSMs

IDLE

IDLE

7892
7893

Figure 15.6/3g: Process Secure_MAP_DSM (sheet 7)

958

3GPP

959 Release 6 960 961

241

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

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

(FALSE)

Secure_ Transport_ Required

(TRUE)

To all active RSSMs

Terminated_ VIA_Intern2

To all active SRSSMs

Terminated_ VIA_Intern4

IDLE

IDLE

7894
7895

Figure 15.6/3h: Process Secure_MAP_DSM (sheet 8)

962

3GPP

963 Release 6 964 965

242

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM9(17)

TC_ CONTINUE_ ind

The first one

(FALSE) AC_Name_ Unchanged (TRUE) (FALSE) Secure_ Transport_ Required (TRUE) Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue

Encapsulated_ AC_Name_ Unchanged (TRUE)

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

Secure_ Transport_ Required

(TRUE)

(FALSE)

MAP_ DELIMITER_ req_VIA_User2

To all active RSSMs

Terminated_ VIA_Intern2

To all active SRSSMs

Terminated_ VIA_Intern4

DIALOGUE_ ESTABLISHED

IDLE

IDLE

7896
7897

Figure 15.6/3i: Process Secure_MAP_DSM (sheet 9)

966

3GPP

967 Release 6 968 969

243

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue IDLE

MAP_DSM10(18)

TC_BEGIN_ ind

(FALSE) AC_ Included (TRUE) (FALSE) AC_Vession =1 (TRUE) AC_Name= Secure_ Transport (FALSE) (TRUE)

(FALSE)

MAP_Protected_ Dialogue_PDU_ included (TRUE)

3 Protection mode correct? Yes (FALSE)

No

(FALSE)

Unsecured_ Transport_ Permitted (TRUE)

6 MAP_Protected_ Payl oad_ included (TRUE)

(FALSE)

MAP_ Dialogue_PDU_ included

(TRUE)

No

User_Info required for encapsulated AC? Yes No

Extract_User_ Information

Extract_User_ Information

MAP-OPEN dialogue PDU? Yes

MAP-OPEN dialogue PDU? Yes Yes User_Info required for AC? No No Invalid Parameter?

No

Yes Invalid Parameter? No

Yes

(FALSE) Components_ Present (TRUE) Check_Load_ VIA_Load1 Check_Load_ VIA_Load1 TC_U_ABORT_ req_VIA_TC1

WAIT_FOR_ LOAD_CHECK_ RESULT1

WAIT_FOR_ LOAD_CHECK_ RESULT1

IDLE

WAIT_FOR_ INIT_DATA

7898
7899

Figure 15.6/3j: Process Secure_MAP_DSM (sheet 10)

970

3GPP

971 Release 6 972 973

244

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue

MAP_DSM11(18)

Set_M AP_Provider_ Abort_Reason: Abnormal_Dialogue

Set_User_Info: MAP_Refuse_PDU

Set_User_Info: MAP_Provider_ Abort_Info

Set_Refuse_Reason: Transport_Protection_ Not_Adequate

Set_Abort_Reason: User_Specific

Set_Abort_Reason: User_Specific

TC_U_ABORT_ req_VIA_TC1

TC_U_ABORT_ req_VIA_TC1

IDLE

IDLE

7900
7901

Figure 15.6/3k: Process Secure_MAP_DSM (sheet 11)

974

3GPP

975 Release 6 976 977

245

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue

MAP_DSM12(18)

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 Unsecured_ Transport_ Permitted (TRUE) (FALSE) Last_ Component (TRUE) (FALSE)

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

7902
7903

Figure 15.6/3l: Process Secure_MAP_DSM (sheet 12)

978

3GPP

979 Release 6 980 981

246

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue WAIT_FOR_ LOAD_CHECK_ RESULT1

MAP_DSM13(18)

Load_OK

Overload

IDLE (FALSE) AC_ Supported (TRUE)

(TRUE) AC_Name= Secure_Transport (FALSE) (FALSE) Encapsulated_ AC_Name_ Supported (TRUE)

(FALSE)

Alternative_ Name_ Exists (TRUE)

Secure_Transport_ Required:=TRUE

AC_Name:= Received_ AC_Name

(FALSE)

Alternative_ Name_ Exists (TRUE)

AC_Name:= Received_ AC_Name

AC_Name:= Alternative_ AC_Name

Extract_ Encapsulated_ AC_Name_and_ User_Data

Set_ User_Data

AC_Name:= Received_ AC_Name

AC_Name:= Alternative_ AC_Name

Set_User_Info: MAP_Refuse_PDU

MAP_OPEN_ ind_VIA_User2

Set_Refuse_Reason: Encapsulated_AC_ Not_Supported

(FALSE) Components_ Present (TRUE)

Set_Abort_ Reason: User_ Specific

Process_ Components

Set_Abort_ Reason: AC_Not_ Supported

TC_U_ABORT_ req_VIA_TC1

MAP_ DELIMITER_ ind_VIA_User2

TC_U_ABORT_ req_VIA_TC1

IDLE

DIALOGUE_ PENDING

IDLE

7904
7905

Figure 15.6/3m: Process Secure_MAP_DSM (sheet 13)

982

3GPP

983 Release 6 984 985

247

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue DIALOGUE_ PENDING

MAP_DSM14(18)

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

(FALSE)

Secure_ Transport_ Required (TRUE)

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern3

To all active SPSSM s

DIALOGUE_ ACCEPTED

IDLE

IDLE

7906
7907

Figure 15.6/3n: Process Secure_MAP_DSM (sheet 14)

986

3GPP

987 Release 6 988 989

248

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue DIALOGUE_ ACCEPTED

MAP_DSM15(18)

MAP_req

Any MAP specific request prim itive

MAP_rsp

Any MAP specific response primitive

MAP_ DELIMITER_ req

Secure_ Transport_ Required

(TRUE)

Secure_ Transport_ Required

(TRUE)

(FALSE) Requesting_ MAP_SSM Secure_ Requesting_ MAP_SSM

(FALSE)

Service_ Invoked_ VIA_Inter n2

Service_ Invoked_ VIA_Intern4

Response_ Issued_ VIA_Intern1

Response_ Issued_ VIA_Intern3

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

(FALSE)

Secure_ Transport_ Required

(TRUE)

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern3

To all active SPSSM s

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern4

To all active SRSSMs

IDLE

IDLE

7908
7909

Figure 15.6/30: Process Secure_MAP_DSM (sheet 15)

990

3GPP

991 Release 6 992 993

249

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM16(18)

MAP_req

Any MAP specific request prim itive

MAP_rsp

Any MAP specific response primitive

MAP_ DELIMITER_ req

Secure_ Transport_ Required

(TRUE)

Secure_ Transport_ Required

(TRUE)

(FALSE) Requesting_ MAP_SSM Secure_ Requesting_ MAP_SSM

(FALSE)

Service_ Invoked_ VIA_Inter n2

Service_ Invoked_ VIA_Intern4

Response_ Issued_ VIA_Intern1

Response_ Issued_ VIA_Intern3

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) (TRUE) (TRUE) Process_ Components Components_ Present

(FALSE)

Secure_ Transport_ Required

(FALSE)

Timer_Expiry_ VIA_Intern2

Timer_Expiry_ VIA_Intern4

MAP_ NOTICE_ ind_VIA_User2

MAP_ DELIMITER_ ind_VIA_User2

DIALOGUE_ ESTABLISHED

7910
7911

Figure 15.6/3p: Process Secure_MAP_DSM (sheet 16)

994

3GPP

995 Release 6 996 997

250

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM17(18)

TC_END_ ind

MAP_ CLOSE_ req

(FALSE) Components_ Present (TRUE)

Process_ Components

MAP_CLOSE_ ind_VIA_User2

TC_END_ req_VIA_TC1

Secure_ Transport_ Required

(TRUE)

(FALSE)

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern3

To all active SPSSM s

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern4

To all active SRSSMs

IDLE

IDLE

7912
7913

Figure 15.6/3q: Process Secure_MAP_DSM (sheet 17)

998

3GPP

999 Release 6 1000 1001

251

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_MAP_DSM
Process to m anage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM18(18)

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

(FALSE)

Secure_ Transport_ Required

(TRUE)

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern3

To all active SPSSM s

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern4

To all active SRSSMs

IDLE

IDLE

7914
7915

Figure 15.6/3r: Process Secure_MAP_DSM (sheet 18)

1002

3GPP

1003 Release 6 1004 1005

252

3GPP TS 29.002 V6.11.0 (2005-09)

Procedure Process_Components
Procedure to process components received in a TC message Comments: Components from TCAP: DCL Op_Code, Operation_Class INTEGER, Operation_Exists, Last_Component, Invoke_ID_Present, Invoke_ID_Assigned, Secure_Transport_Required, Linked_ID_Present, Encapsulater_Linked_ID_Present, Linked_ID_Assigned, Encapsulated_Linked_ID_Assigned, Linked_Operation_Allowed, v3_Or_Higher_Dialogue BOOLEAN;

Proc_Comp1(5)

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: Unrecognized_ Operation Secure_ Transport_ Required (TRUE) 1

(FALSE) Secure_ Performing_ MAP_SSM

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

Service_ Invocation_ Received_ VIA_Intern3

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

MAP_NOTICE ind_VIA_User2

(FALSE) Last_ Component (TRUE) WAIT_FOR_ COMPONENTS

7916
7917

Figure 15.6/4a: Procedure Process_Components (sheet 1)

1006

3GPP

1007 Release 6 1008 1009

253

3GPP TS 29.002 V6.11.0 (2005-09)

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

Secure_ Transport_ Required

Secure_ Transport_ Required

(FALSE)

(FALSE)

TC_U_REJECT_ req_VIA_TC1

Linked_ Service_ Invoked_ VIA_Intern2

Linked_ Service_ Invoked_ VIA_Intern4

Linked_ Request_ Received_ VIA_Intern2

Linked_ Request_ Received_ VIA_Intern4

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

Performing_ MAP_SSM

Secure_ Performing_ MAP_SSM

MAP_NOTICE ind_VIA_User2

Service_ Invocation_ Received_ VIA_Intern1

Service_ Invocation_ Received_ VIA_Intern3

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7918
7919

Figure 15.6/4b: Procedure Process_Components (sheet 2)

1010

3GPP

1011 Release 6 1012 1013

254

3GPP TS 29.002 V6.11.0 (2005-09)

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

Invoke_ ID_ Assigned (TRUE)

(FALSE)

Invoke_ ID_ Assigned (TRUE) 2

(FALSE)

Invoke_ ID_ Assigned (TRUE) 2

(FALSE)

Secure_ Transport_ Required

(TRUE)

Secure_ Transport_ Required

(TRUE)

Secure_ Transport_ Required

(TRUE)

(FALSE)

(FALSE)

(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

Result_ Received_ VIA_Intern4

Partial_ Result_ Received_ VIA_Intern2

Partial_ Result_ Received_ VIA_Intern4

Negative_ Result_ Received_ VIA_Intern2

Negative_ Result_ Received_ VIA_Intern4

MAP_NOTICE ind_VIA_User2

(FALSE) Last_ Component (TRUE)

W AIT_FOR_ COMPONENTS

7920
7921

Figure 15.6/4c: Procedure Process_Components (sheet 3)

1014

3GPP

1015 Release 6 1016 1017

255

3GPP TS 29.002 V6.11.0 (2005-09)

Procedure Process_Components
Procedure to process components received in a TC message W AIT_FOR_ COMPONENTS

Proc_Comp4(5)

TC_L_ REJECT_ ind

TC_R_ REJECT_ ind

Invoke_ ID_ Present (TRUE)

(FALSE)

rr_problem, re-problem, general_problem Problem Type invoke_problem Problem Type

rr_problem, re-problem, general_problem

invoke_problem

Invoke_ ID_ Assigned (TRUE)

(FALSE)

Invoke_ ID_ Assigned (TRUE)

(FALSE)

Secure_ Transport_ Required

(TRUE)

Secure_ Transport_ Required

(TRUE)

(FALSE)

(FALSE)

Provider_ Reject_ Received_ VIA_Intern2

Provider_ Reject_ Received_ VIA_Intern4

MAP_ NOTICE_IND_ VIA_USER2

Provider_ Reject_ Received_ VIA_Intern2

Provider_ Reject_ Received_ VIA_Intern4

MAP_ NOTICE_IND_ VIA_USER2

(FALSE) Last_ Component (TRUE)

W AIT_FOR_ COMPONENTS

7922
7923

Figure 15.6/4d: Procedure Process_Components (sheet 4)

1018

3GPP

1019 Release 6 1020 1021

256

3GPP TS 29.002 V6.11.0 (2005-09)

Procedure Process_Components
Procedure to process components received in a TC message W AIT_FOR_ COMPONENTS

Proc_Comp5(5)

TC_U_ REJECT_ ind

rr_problem, re-problem Problem Type invoke_problem

Invoke_ ID_ Assigned (TRUE)

(FALSE)

Secure_ Transport_ Required

(TRUE)

(FALSE)

User_Reject_ Received_ VIA_Intern2

User_Reject_ Received_ VIA_Intern4

MAP_ NOTICE_IND_ VIA_USER2

(FALSE) Last_ Component (TRUE)

W AIT_FOR_ COMPONENTS

7924
7925

Figure 15.6/4e: Procedure Process_Components (sheet 5)

1022

3GPP

1023 Release 6 1024 1025

257

3GPP TS 29.002 V6.11.0 (2005-09)

Process Load_Ctrl
Process to verify whether offered dialogue should be discarded because of overload

Load_Ctrl1(1)
Comment 'LOAD CONTROL': DCL Congestion, Dialogue_Acceptable BOOLEAN;

IDLE

Check_ Load

(FALSE) Congestion (TRUE)

(FALSE) AC=Secure_ Transport (TRUE)

Compare_ Encapsulated_ AC_priority_ with_load

Compare_ AC_priority_ with_load

(FALSE) Dialogue_ Acceptable (TRUE)

Load_OK_ VIA_Load2

Overload_ VIA_Load2

Load_OK_ VIA_Load2

IDLE

7926
7927

Figure 15.6/5: Process Load_Ctrl

1026

3GPP

1027 Release 6 1028 1029

258

3GPP TS 29.002 V6.11.0 (2005-09)

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

7928
7929

Figure 15.6/6a: Process Requesting_MAP_SSM (sheet 1)

1030

3GPP

1031 Release 6 1032 1033

259

3GPP TS 29.002 V6.11.0 (2005-09)

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

7930
7931

Figure 15.6/6b: Process Requesting_MAP_SSM (sheet 2)

1034

3GPP

1035 Release 6 1036 1037

260

3GPP TS 29.002 V6.11.0 (2005-09)

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

7932
7933

Figure 15.6/6c: Process Requesting_MAP_SSM (sheet 3)

1038

3GPP

1039 Release 6 1040 1041

261

3GPP TS 29.002 V6.11.0 (2005-09)

Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity W AIT_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

7934
7935

Figure 15.6/6d: Process Requesting_MAP_SSM (sheet 4)

1042

3GPP

1043 Release 6 1044 1045

262

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity, using secure transport

MAP_SRSSM1(4)

Comment 'Secure 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

Build_Secure_ MAP_Transport_ Service

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern6

(FALSE) W ait_ For_Cnf (TRUE)

W AIT_FOR_ CONFIRM

7936
7937

Figure 15.6/7a: Process Secure_Requesting_MAP_SSM (sheet 1)

1046

3GPP

1047 Release 6 1048 1049

263

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity, using secure transport WAIT_FOR_ CONFIRM

MAP_SRSSM2(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_TC6

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_User6

Extract_ Protected_ Result

Set_Provider_ Error: Invalid_ Response_ Received

Set_Problem_ Code: Mistyped_ Parameter'

Extract_ Protected_ User_Error

Set_Provider_ Error: Invalid_ Response_ Received

Result_ Received_ VIA_Intern6

MAP_cnf_ VIA_User6

TC_U_REJECT_ req_VIA_TC6

Negative_ Result_ Received VIA_User6

MAP_cnf_ VIA_User6

Terminated_ VIA_Intern6

Terminated_ VIA_Intern6

Terminated_ VIA_Intern6

7938
7939

Figure 15.6/7b: Process Secure_Requesting_MAP_SSM (sheet 2)

1050

3GPP

1051 Release 6 1052 1053

264

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity, using secure transport WAIT_FOR_ CONFIRM

MAP_SRSSM3(4)

Linked_ Request_ Received

Linked_ Service_ Invoked

User_ Reject_ Received

Terminated

Extract_ Protected_ Request

Implicit_Cnf:= TRUE

Terminated_ VIA_Intern6

Linked_ Request_ Received_ VIA_User6

Linked_ Service_ Invoked_ VIA_User6

(FALSE) WAIT_FOR_ CONFIRM MAP_ Initiated (TRUE)

Set_Provider_ Error

Set_User_ Error

MAP_cnf_ VIA_User6

Terminated_ VIA_Intern6

7940
7941

Figure 15.6/7c: Process Secure_Requesting_MAP_SSM (sheet 3)

1054

3GPP

1055 Release 6 1056 1057

265

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity, using secure transport W AIT_FOR_ CONFIRM

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

Terminated_ VIA_Intern6

Terminated_ VIA_Intern6

Terminated_ VIA_Intern6

Terminated_ VIA_Intern6

7942
7943

Figure 15.6/7d: Process Secure_Requesting_MAP_SSM (sheet 4)

1058

3GPP

1059 Release 6 1060 1061

266

3GPP TS 29.002 V6.11.0 (2005-09)

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

7944
7945

Figure 15.6/8a: Process Performing_MAP_SSM (sheet 1)

1062

3GPP

1063 Release 6 1064 1065

267

3GPP TS 29.002 V6.11.0 (2005-09)

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

7946
7947

Figure 15.6/8b: Process Performing_MAP_SSM (sheet 2)

1066

3GPP

1067 Release 6 1068 1069

268

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_Performing_MAP_SSM
Process to handle an invoke component received from the peer and the response from the user, using secure transport

MAP_SPSSM1(2)

Comment 'Secure 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 Service_ Parameters_ Available (TRUE) Discard_ Invocation 1 Operation_ Class Associated with the service (FALSE) (FALSE) Discard_ Invocation

Operation_ Class

Associated with the service

(1,2)

(3,4)

(3,4)

(1,2) Set_Error: Data_Missing Set_Error: Unexpected_ Data_Value

(TRUE) Unexpected_ Data (FALSE) Extract_ Protected_ Request Discard_ Invocation

Performing_ MAP_SSM

Service_ Invocation_ Received_ VIA_Intern5 (FALSE) Cnf_ Required (TRUE) (1,2) Set_ (Guard_Timer) (3,4) MAP_NOTICE_ ind_VIA_User5 Operation_ Class Associated with the service TC_U_ERROR_ req_VIA_TC5

Set_Problem_ Code: Mistyped_ Parameter

TC_U_REJECT_ req_VIA_TC5

MAP_NOTICE_ ind_VIA_User5

W AIT_FOR_ RESPONSE

7948
7949

Figure 15.6/9a: Process Secure_Performing_MAP_SSM (sheet 1)

1070

3GPP

1071 Release 6 1072 1073

269

3GPP TS 29.002 V6.11.0 (2005-09)

Process Secure_Performing_MAP_SSM
Process to handle an invoke component received from the peer and the response from the user, using secure transport WAIT_FOR_ RESPONSE

MAP_SPSSM2(2)

Guard_ Timer_ Expired

Response_ Issued

by the MAP user

Terminated

Terminated_ VIA_Intern5

Terminated_ VIA_Intern5

(TRUE) User_Error_ Present (FALSE)

(FALSE) Linked_ Request (TRUE) Specific_ Error (TRUE)

(FALSE)

Set_Problem_ Code

Build_ Protected_ Response

Build_ Protected_ Request

Build_ Protected_ Negative_ Response

TC_U_REJECT_ req_VIA_TC5

Response_ Issued_ VIA_Intern5

Response_ Issued_ VIA_Intern5

Response_ Issued_ VIA_Intern5

Terminated_ VIA_Intern5

7950
7951

Figure 15.6/9b: Process Secure_Performing_MAP_SSM (sheet 2)

1074

3GPP

1075 Release 6 1076 1077

270

3GPP TS 29.002 V6.11.0 (2005-09)

7952 7953

16

Mapping on to TC services
16.1 Dialogue control

7954 Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP 7955 PM.

7956

16.1.1 Directly mapped parameters

7957 The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the 7958 corresponding parameters of the TC-BEGIN primitives: 7959 7960

destination address; originating address.

7961 7962 16.1.2.1

16.1.2 Use of other parameters of dialogue handling primitives


Dialogue Id

7963 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

7964 16.1.2.2

Application-context-name

7965 The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of 7966 TC dialogue handling primitives according to the rules described in clause 15.1.

7967 16.1.2.3

User information

7968 The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs.

7969 16.1.2.4

Component present

7970 This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP 7971 user.

7972 16.1.2.5

Termination

7973 The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method 7974 parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE 7975 INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end".

7976 16.1.2.6
7977 7978 7979 7980 7981

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

7982 16.1.2.7
-

Quality of service

7983 The quality of service of TC request primitives is set by the MAP as shown below. 7984

Return option: "Return message on error" or "Discard message on error" as required by the network operator;

1078

3GPP

7985 7986 7987 7988 7989

1079 Release 6 1080 1081

271

3GPP TS 29.002 V6.11.0 (2005-09)

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.

7990 It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue 7991 initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue 7992 responder shall ensure that this requirement is met by: 7993 7994 7995 7996 7997 7998

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.

7999

8000

16.2 Service specific procedures


16.2.1 Directly mapped parameters

8001 Specific services are mapped to TC component handling services.

8002

8003 The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter 8004 of the component handling primitives.

8005 8006 16.2.2.1

16.2.2 Use of other parameters of component handling primitives


Dialogue Id

8007 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

8008 16.2.2.2

Class

8009 The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.

8010 16.2.2.3
8011 8012 8013 8014

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.

1082

3GPP

8015 16.2.2.4

1083 Release 6 1084 1085

272

3GPP TS 29.002 V6.11.0 (2005-09)

Operation

8016 When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code 8017 according to the mapping described in table 16.2/1. 8018 When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the 8019 TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time. 8020

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-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-SECURE-TRANSPORT-CLASS-1 MAP-SECURE-TRANSPORT-CLASS-2 MAP-SECURE-TRANSPORT-CLASS-3 MAP-SECURE-TRANSPORT-CLASS-4 MAP-SEND_GROUP-CALL_END_SIGNAL MAP-SEND-END-SIGNAL MAP-SEND-AUTHENTICATION-INFO MAP-SEND-IMSI 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 provideSubscriberLocation provideSubscriberInfo purgeMS readyForSM registerCC-Entry registerPassword registerSS remoteUserFree reportSmDeliveryStatus reset restoreData secureTransportClass1 secureTransportClass2 secureTransportClass3 secureTransportClass4 sendGroupCallEndSignal sendEndSignal sendAuthenticationInfo sendIMSI

1086

3GPP

1087 Release 6 273 1088 1089 MAP-SEND-IDENTIFICATION MAP-SEND-ROUTING-INFO-FOR-SM MAP-SEND-ROUTING-INFO-FOR-GPRS MAP-SEND-ROUTING-INFO-FOR-LCS MAP-SEND-ROUTING-INFORMATION MAP-SET-REPORTING-STATE MAP-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 8021

3GPP TS 29.002 V6.11.0 (2005-09) sendIdentification sendRoutingInfoForSM sendRoutingInfoForGprs sendRoutingInfoForLCS sendRoutingInfo setReportingState statusReport subscriberLocationReport ss-Invocation-Notification unstructuredSS-Notify unstructuredSS-Request updateGprsLocation updateLocation NoteMM-Event

8022 16.2.2.5

Error

8023 The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm 8024 primitive of the service associated with the operation to which the error is attached. 8025 The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request 8026 primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of 8027 the TC-U-REJECT request primitive.

8028 16.2.2.6

Parameters

8029 The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC8030 INVOKE primitives. 8031 The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L 8032 primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on 8033 linked class 4 operations is used.

8034 16.2.2.7

Time out

8035 The value of this parameter is set by the MAP PM according to the type of operation invoked.

8036 16.2.2.8

Last component

8037 This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP 8038 user.

8039 16.2.2.9 8040 16.2.2.9.1

Problem code
Mapping to MAP User Error

8041 The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. 8042 These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the 8043 MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive. 8044 8045

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

8046

1090

3GPP

8047 16.2.2.9.2

1091 Release 6 1092 1093

274

3GPP TS 29.002 V6.11.0 (2005-09)

Mapping to MAP Provider Error parameter

8048 The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as 8049 follows to values of the MAP Provider Error parameter of the MAP confirm primitive. 8050

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

8051 8052 The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the 8053 provider error parameter of the MAP confirm primitive as follows. 8054

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

8055

8056 16.2.2.9.3

Mapping to diagnostic parameter

8057 The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to 8058 values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: 8059 8060

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

8061 8062 The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the 8063 diagnostic parameter of the MAP-NOTICE indication primitive as follows. 8064

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

8065

1094

3GPP

1095 Release 6 1096 1097

275

3GPP TS 29.002 V6.11.0 (2005-09)

8066 8067
8068 8069 8070 8071

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 ITU-T Recommendations X.680 and X.681 with additions as defined in clause 17.1.4 on Compatibility Considerations and the OPERATION and ERROR external information object classes, defined in ITU-T Recommendation X.880.

8072 The Abstract Syntax is defined for all interfaces specified in clause 4.4 except for the A- and B-interfaces. 8073 The Mobile Application Part protocol is defined by two Abstract Syntaxes: 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085

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. TCMessage as defined in ITU-T Recommendation Q.773 with the component relationconstraint sections resolved by the operation and error codes included in the ASN.1 modules MAP-*Operations and MAP-Errors. 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.

8086

17.1.1 Encoding rules

8087 The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract 8088 Syntax Notation One, defined in ITU-T Recommendation X.690 with the same exceptions as in ITU-T 8089 Recommendation Q.773, clause 4 Message Representation. 8090 When the definite form is used for length encoding, a data value of length less than 128 octets must have the length 8091 encoded in the short form. 8092 When the long form is employed to code a length, the minimum number of octets shall be used to code the length field. 8093 OCTET STRING values and BIT STRING values must be encoded in a primitive form. 8094 There is no restriction to the use of empty constructors (e.g. an empty SEQUENCE type). That is, the encoding of the 8095 content of any data value shall consist of zero, one or more octets.

8096

17.1.2 Use of TC

8097 The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on 8098 ITU-T Recommendation Q.773. 8099 8100 8101 8102 8103

NOTE 1: The class of an operation is not stated explicitly but is specified as well in the ASN.1 operation definition. Class 1: RESULT and ERROR appear in ASN.1 operation definition. Class 2: only ERROR appears in ASN.1 operation definition. Class 3: only RESULT appears in ASN.1 operation definition. Class 4: both RESULT and ERROR do not appear in ASN.1 operation definition.

8104 The field "ARGUMENT", "PARAMETER" or "RESULT" (for information objects of class OPERATION and 8105 ERROR) is always optional from a syntactic point of view. However, except when specifically mentioned with the

1098

3GPP

8106 ASN.1 comment "-- optional" , the "parameter" part of a component has to be considered as mandatory from a semantic 8107 point of view. 8108 8109 8110 8111 8112 8113

1099 Release 6 1100 1101

276

3GPP TS 29.002 V6.11.0 (2005-09)

When an optional element is missing in an invoke component or in an inner data structure while it is required by the context, an error component is returned if specified in the information object associated with the operation ; the associated type of error is "DataMissing". This holds also when the entire parameter of an invoke component is missing while it is required by the context. 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".

8114 The Timer Values used in the operation definitions are indicated as ASN.1 comments. The Timer Value Ranges are: 8115 8116 8117 8118

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

8119 17.1.2.1
8120 8121 8122 8123 8124 8125 8126 8127 8128

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 29.002, encoded as either an Object Identifier (as defined in ITU-T Recommendation X.690 ) 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 29.002. 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.

8129 Handling of an unknown operation codes by the receiving entity is defined in clause 15.1.1.

8130

17.1.3 Use of information elements defined outside MAP

8131 An information element or a set of information elements (messages) transparently carried in the Mobile Application 8132 Part but defined in other recommendations/technical specifications are handled in one of the following ways: 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142

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

8143

17.1.4 Compatibility considerations

8144 The following ASN.1 modules conform to ITU-T Recommendation X.680 and X.681 . An extension marker ("...") is 8145 used wherever future protocol extensions are foreseen. 8146 The "..." construct applies only to SEQUENCE and ENUMERATED data types. An entity supporting a version greater 8147 than 1 shall not reject an unsupported extension following "..." of that SEQUENCE or ENUMERATED data type. The

1102

3GPP

8148 Encoding Rules from clause 17.1.1 apply to every element of the whole Transfer Syntax especially to the ASN.1 type 8149 EXTERNAL. 8150 The extension container "privateExtensionList" is defined in this specification in order to carry extensions which are 8151 defined outside this specification. Private extensions can be defined by, for example, network operators, manufacturers, 8152 and regional standardisation bodies. 8153 Private extensions shall: 8154 8155 8156 8157 8158 8159

1103 Release 6 1104 1105

277

3GPP TS 29.002 V6.11.0 (2005-09)

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.

8160 Private extensions shall not be included in v2 supplementary service operations. 8161 Private extensions shall not be included within user error for RegisterCCEntry and EraseCCEntry operations. 8162 PCS extensions shall be included in the PCS Extension Container that is defined in this specification. 8163 8164 8165 8166

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.

8167
8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188

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 type) which 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 capital and the first letter of each of the following words ise 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 om operation & maintenance pw Password sm short message service ss supplementary service st secure transport

1106

3GPP

8189 8190 8191 8192 8193

1107 Release 6 1108 1109

278

3GPP TS 29.002 V6.11.0 (2005-09)

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 the code values are given as parameters, in order to allow use of the defined information objects also by other protocols (e.g. 3GPP TS 24.080 [38]). 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.

8194 The module containing the definition of the operation packages for MAP is: 8195

1. MAP-OperationPackages.

8196 The module containing the definition of the application contexts for MAP is: 8197

2. MAP-ApplicationContexts.

8198 The module containing the data types for the Abstract Syntax to be used for TCAPMessages.DialoguePortion for MAP 8199 is: 8200

3. MAP-DialogueInformation.

8201 The module containing the supported operations is: 8202

4. MAP-Protocol.

8203 The modules containing all operation definitions for MAP are: 8204 8205 8206 8207 8208 8209 8210 8211

5. MAP-MobileServiceOperations; 6. MAP-OperationAndMaintenanceOperations; 7. MAP-CallHandlingOperations; 8. MAP-SupplementaryServiceOperations; 9. MAP-ShortMessageServiceOperations; 10. MAP-Group-Call-Operations; 11. MAP-LocationServiceOperations; 12. MAP-SecureTransportOperations.

8212 The module containing all error definitions for MAP is: 8213

13. MAP-Errors.

8214 Modules containing all data type definitions for MAP are: 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225

14. MAP-MS-DataTypes; 15. MAP-OM-DataTypes; 16. MAP-CH-DataTypes; 17. MAP-SS-DataTypes; 18. MAP-SS-Code; 19. MAP-SM-DataTypes; 20. MAP-ER-DataTypes; 21. MAP-CommonDataTypes; 22. MAP-TS-Code; 23. MAP-BS-Code; 24. MAP-ExtensionDataTypes;

1110

3GPP

8226 8227 8228

1111 Release 6 1112 1113

279

3GPP TS 29.002 V6.11.0 (2005-09)

25. MAP-GR-DataTypes; 26. MAP-LCS-DataTypes; 27. MAP-ST-DataTypes.

8229 References are made also to modules defined outside of the present document. They are defined in the technical 8230 specification Mobile Services Domain, technical specification Transaction Capability and ITU-T Recommendation 8231 X.880 respectively: 8232 8233 8234

MobileDomainDefinitions; TCAPMessages, DialoguePDUs ; Remote-Operations-Information-Objects.

8235

17.1.6 Application Contexts

8236 The following informative table lists the latest versions of the Application Contexts used in this specification, with the 8237 operations used by them and, where applicable, whether or not the operation description is exactly the same as for 8238 previous versions. Information in 17.6 & 17.7 relates only to the ACs in this table. 8239

AC Name
locationCancellationContext equipmentMngtContext imsiRetrievalContext infoRetrievalContext interVlrInfoRetrievalContext handoverControlContext

AC Version
v3 V3 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 restoreData insertSubscriberData activateTraceMode updateGprsLocation insertSubscriberData

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

gprsLocationUpdateContext

v3

1114

3GPP

1115 Release 6 1116 1117

280

3GPP TS 29.002 V6.11.0 (2005-09)

AC Name

AC Version
v3 v3 v3 v3 v4 v3 v4 v3 v3 v3 v3 v3

Operations Used
activateTraceMode insertSubscriberData deleteSubscriberData provideRoamingNumber sendRoutingInfo noteMsPresentForGprs sendRoutingInfoForGprs failureReport resumeCallHandling provideSubscriberInfo anyTimeInterrogation anyTimeSubscriptionInterrogation anyTimeModification ss-InvocationNotification prepareGroupCall processGroupCallSignalling forwardGroupCallSignalling sendGroupCallEndSignal setReportingState statusReport remoteUserFree registerCC-Entry eraseCC-Entry istAlert istCommand provideSubscriberLocation subscriberLocationReport sendRoutingInfoForLCS noteMM-Event noteSubscriberDataModified authenticationFailureReport secureTransportClass1 secureTransportClass2 secureTransportClass3 secureTransportClass4 releaseResources

Comments

subscriberDataMngtContext roamingNumberEnquiryContext locationInfoRetrievalContext gprsNotifyContext gprsLocationInfoRetrievalContext failureReportContext callControlTransferContext subscriberInfoEnquiryContext anyTimeEnquiryContext anyTimeInfoHandlingContext ss-InvocationNotificationContext groupCallControlContext

reportingContext callCompletionContext istAlertingContext ServiceTerminationContext locationSvcEnquiryContext

v3 v3 v3 v3 v3

locationSvcGatewayContext v3 mm-EventReportingContext v3 subscriberDataModificationNotificati v3 onContext authenticationFailureReportContext v3 secureTransportHandlingContext v3

resourceManagementContext

v3

8240 8241

NOTE (*):

The syntax of the operations is not the same as in previous versions unless explicitly stated

8275 8276

17.2 Operation packages


17.2.1 General aspects

8277 This clause describes the operation-packages which are used to build the application-contexts defined in clause 17.3. 8278 Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), 8279 in terms of operations which they can invoke of each other. 8280 The grouping of operations into one or several packages does not necessarily imply any grouping in terms of 8281 Application Service Elements. 8282 The following ASN.1 information object class is used to describe operation-packages in this clause:

1118

3GPP

1119 Release 6 1120 1121


8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293

281

3GPP TS 29.002 V6.11.0 (2005-09)

OPERATION-PACKAGE ::= CLASS { &Both OPERATION &Consumer OPERATION &Supplier OPERATION &id OBJECT IDENTIFIER WITH SYNTAX { [ OPERATIONS &Both ] [ CONSUMER INVOKES &Supplier ] [ SUPPLIER INVOKES &Consumer ] [ ID &id ] }

OPTIONAL, OPTIONAL, OPTIONAL, UNIQUE OPTIONAL }

8294 Since the application-context definitions provided in clause 17.3 use only an informal description technique, only the 8295 type notation is used in the following clauses to define operation-packages. 8296 The following definitions are used throughout this clause (n>=2): 8297 8298 8299 8300 8301 8302 8303 8304

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.

8305 The names of vn-packages are suffixed by "-vn" where n>=2. 8306 For each operation package which is not vn-only (n>=2) and which does not include only v(n-1)-operations, there is a 8307 v(n-1)-equivalent package. Except when a definition is explicitly provided in the following clauses, the 8308 v(n-1)-equivalent package includes the v(n-1)-equivalent operations of the operations which belong to this package.

8309 8310 17.2.2.1

17.2.2 Packages specifications


Location updating

8311 This operation package includes the operations required for location management procedures between HLR and VLR.
8312 8313 8314 8315 8316 8317 8318

locationUpdatingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { updateLocation} SUPPLIER INVOKES { forwardCheckSs-Indication} }

8319 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8320 17.2.2.2

Location cancellation

8321 This operation package includes the operations required for location cancellation and MS purging procedures between 8322 HLR and VLR and between HLR and SGSN.
8323 8324 8325 8326 8327

locationCancellationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { cancelLocation} }

8328 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

1122

3GPP

8329 17.2.2.3

1123 Release 6 1124 1125

282

3GPP TS 29.002 V6.11.0 (2005-09)

Roaming number enquiry

8330 This operation package includes the operations required for roaming number enquiry procedures between HLR and 8331 VLR.
8332 8333 8334 8335 8336

roamingNumberEnquiryPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideRoamingNumber} }

8337 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8338 17.2.2.4

Information retrieval

8339 This operation package includes the operation required for the authentication information retrieval procedure between 8340 HLR and VLR and between HLR and SGSN.
8341 8342 8343 8344 8345 8346

infoRetrievalPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo} }

8347 The v2-equivalent package is defined as follows:


8348 8349 8350 8351 8352 8353

infoRetrievalPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo} }

8354 The v1-equivalent package is defined as follows:


8355 8356 8357 8358 8359 8360

infoRetrievalPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR or VLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendParameters} }

8361 17.2.2.5

Inter-VLR information retrieval

8362 This operation package includes the operations required for inter VLR information retrieval procedures.
8363 8364 8365 8366 8367

interVlrInfoRetrievalPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification} }

8368 The v2-equivalent package is defined as follows:


8369 8370 8371 8372 8373

interVlrInfoRetrievalPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification} }

8374 The v1-equivalent package is : infoRetrievalPackage-v1.

8375 17.2.2.6

IMSI retrieval

8376 This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR.
8377 8378 8379 8380 8381

imsiRetrievalPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { sendIMSI} }

8382 This package is v2 only.

1126

3GPP

8383 17.2.2.7

1127 Release 6 1128 1129

283

3GPP TS 29.002 V6.11.0 (2005-09)

Call control transfer

8384 This operation package includes the operation required for the call control transfer procedure between VMSC and 8385 GMSC.
8386 8387 8388 8389 8390

callControlTransferPackage-v4 OPERATION-PACKAGE ::= { -- Supplier is GMSC if Consumer is VMSC CONSUMER INVOKES { resumeCallHandling} }

8391 The v3-equivalent package can be determined according to the rules described in clause 17.2.1.

8392 17.2.2.8

Secure transport

8393 This operation package includes the operations required for the secure transport of MAP messages between any MAP 8394 entities.
8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406

secureTransportHandlingPackage-v3 CONSUMER INVOKES { secureTransportClass1 | secureTransportClass2 | secureTransportClass3 | secureTransportClass4} }

OPERATION-PACKAGE ::= { --------to be used TCAP class to be used TCAP class to be used TCAP class to be used TCAP class if the original 1 operation if the original 2 operation if the original 3 operation if the original 4 operation operation is a operation is a operation is a operation is a

8407 This package is v3 only.

8408 17.2.2.9 8409 17.2.2.10

Void Interrogation

8410 This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR 8411 or between HLR and gsmSCF.
8412 8413 8414 8415 8416 8417

interrogationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR or NPLR if Consumer is MSC -- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { sendRoutingInfo} }

8418 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8419 17.2.2.11 8420 17.2.2.12

Void Handover Control

8421 This operation package includes the operations required for handover procedures between MSCs.
8422 8423 8424 8425 8426 8427 8428 8429 8430 8431

handoverControlPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { prepareHandover | forwardAccessSignalling} SUPPLIER INVOKES { sendEndSignal | processAccessSignalling | prepareSubsequentHandover} }

1130

3GPP

8432 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 8433 The v1-equivalent package is defined as follows.
8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445

1131 Release 6 1132 1133

284

3GPP TS 29.002 V6.11.0 (2005-09)

handoverControlPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { performHandover | forwardAccessSignalling | traceSubscriberActivity} SUPPLIER INVOKES { sendEndSignal | noteInternalHandover | processAccessSignalling | performSubsequentHandover} }

8446 17.2.2.13

Subscriber Data management stand alone

8447 This operation package includes the operations required for stand alone subscriber data management procedures 8448 between HLR and VLR or between HLR and SGSN.
8449 8450 8451 8452 8453 8454

subscriberDataMngtStandAlonePackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData | deleteSubscriberData} }

8455 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8456 17.2.2.14

Equipment management

8457 This operation package includes the operations required for equipment management procedures between EIR and MSC 8458 or between EIR and SGSN.
8459 8460 8461 8462 8463 8464

equipmentMngtPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is EIR if Consumer is MSC -- Supplier is EIR if Consumer is SGSN CONSUMER INVOKES { checkIMEI} }

8465 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8466 17.2.2.15

Subscriber data management

8467 This operation package includes the operations required for subscriber data management procedures between HLR and 8468 VLR or between HLR and SGSN.
8469 8470 8471 8472 8473

subscriberDataMngtPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData} }

8474 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8475 17.2.2.16

Location register restart

8476 This operation package includes the operations required for location register restart procedures between HLR and VLR 8477 or between HLR and SGSN.
8478 8479 8480 8481 8482

resetPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { reset} }

8483 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

1134

3GPP

8484 17.2.2.17

1135 Release 6 1136 1137

285

3GPP TS 29.002 V6.11.0 (2005-09)

Tracing stand-alone

8485 This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or 8486 between HLR and SGSN.
8487 8488 8489 8490 8491 8492

tracingStandAlonePackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode | deactivateTraceMode} }

8493 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8494 17.2.2.18

Functional SS handling

8495 This operation package includes the operations required for functional supplementary services procedures between VLR 8496 and HLR.
8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508

functionalSsPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerSS | eraseSS | activateSS | deactivateSS | registerPassword | interrogateSS} SUPPLIER INVOKES { getPassword} }

8509 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

8510 17.2.2.19

Tracing

8511 This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR 8512 and SGSN.
8513 8514 8515 8516 8517

tracingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode} }

8518 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8519 17.2.2.20

Binding

8520 This operation package includes the operation required to initialise a supplementary service procedure between VLR 8521 and HLR or between gsmSCF and HLR.
8522 8523 8524 8525 8526

bindingPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { beginSubscriberActivity} }

8527 This package is v1 only.

1138

3GPP

8528 17.2.2.21

1139 Release 6 1140 1141

286

3GPP TS 29.002 V6.11.0 (2005-09)

Unstructured SS handling

8529 This operation package includes the operations required for unstructured supplementary services procedures between 8530 VLR and HLR, between the HLR and the gsmSCF, and between HLR and HLR.
8531 8532 8533 8534 8535 8536 8537 8538 8539

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

8540 The v1-equivalent package is defined as follows:


8541 8542 8543 8544 8545 8546

unstructuredSsPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Data} }

8547 17.2.2.22

MO Short message relay services

8548 This operation package includes the operations required for short message relay service procedures between IWMSC 8549 and VMSC or between GMSC and MSC or between SGSN and IWMSC.
8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563

mo-ShortMsgRelayPackage-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} }

8564 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

8565 17.2.2.23

Short message gateway services

8566 This operation package includes the operations required for short message service gateway procedures between MSC 8567 and HLR.
8568 8569 8570 8571 8572 8573 8574 8575 8576

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.

8577 The v1-equivalent package is defined as follows:


8578 8579 8580 8581 8582 8583

shortMsgGatewayPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM | reportSMDeliveryStatus} }

1142

3GPP

8584 17.2.2.24

1143 Release 6 1144 1145

287

3GPP TS 29.002 V6.11.0 (2005-09)

MT Short message relay services

8585 This operation package includes the operations required for short message relay service procedures between GMSC and 8586 MSC or between GMSC and SGSN.
8587 8588 8589 8590 8591

mt-ShortMsgRelayPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is MSC or SGSN if Consumer is GMSC CONSUMER INVOKES { mt-forwardSM} }

8592 The v2-equivalent package is: shortMsgRelayPackage-v2

8593 17.2.2.25 8594 17.2.2.26

Void Message waiting data management

8595 This operation package includes the operations required for short message waiting data procedures between HLR and 8596 VLR, between HLR and SGSN.
8597 8598 8599 8600 8601 8602

mwdMngtPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is SGSN -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { readyForSM} }

8603 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.
8604

8605 The v1-equivalent package is defined as follows:


8606 8607 8608 8609 8610

mwdMngtPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { noteSubscriberPresent} }

8611 17.2.2.27

Alerting

8612 This operation package includes the operations required for alerting between HLR and IWMSC.
8613 8614 8615 8616 8617

alertingPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentre} }

8618 The v1-equivalent package is defined as follows.


8619 8620 8621 8622 8623

alertingPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentreWithoutResult} }

8624 17.2.2.28

Data restoration

8625 This operation package includes the operations required for VLR data restoration between HLR and VLR.
8626 8627 8628 8629 8630

dataRestorationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { restoreData} }

8631 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 8632 The v1-equivalent package is: infoRetrievalPackage-v1

1146

3GPP

8633 17.2.2.29

1147 Release 6 1148 1149

288

3GPP TS 29.002 V6.11.0 (2005-09)

Purging

8634 This operation package includes the operations required for purging between HLR and VLR or between HLR and 8635 SGSN.
8636 8637 8638 8639 8640 8641

purgingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { purgeMS} }

8642 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.

8643 17.2.2.30

Subscriber information enquiry

8644 This operation package includes the operations required for subscriber information enquiry procedures between HLR 8645 and VLR or between HLR and SGSN.
8646 8647 8648 8649 8650

subscriberInformationEnquiryPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { provideSubscriberInfo} }

8651 This package is v3 only.

8652 17.2.2.31

Any time information enquiry

8653 This operation package includes the operations required for any time information enquiry procedures between gsmSCF 8654 and HLR or between gsmSCF and GMLC or between gsmSCF and NPLR.
8655 8656 8657 8658 8659

anyTimeInformationEnquiryPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR or GMLC or NPLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeInterrogation} }

8660 This package is v3 only.

8661 17.2.2.32

Group Call Control

8662 This operation package includes the operations required for group call and broadcast call procedures between MSCs.
8663 8664 8665 8666 8667 8668 8669 8670 8671

groupCallControlPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is relay MSC if Consumer is anchor MSC CONSUMER INVOKES { prepareGroupCall | forwardGroupCallSignalling} SUPPLIER INVOKES { sendGroupCallEndSignal | processGroupCallSignalling} }

8672 This package is v3 only.

1150

3GPP

8673 17.2.2.33 8674 17.2.2.34 8675 17.2.2.35

1151 Release 6 1152 1153

289

3GPP TS 29.002 V6.11.0 (2005-09)

Void Void Gprs location updating

8676 This operation package includes the operations required for the gprs location management procedures between HLR 8677 and SGSN.
8678 8679 8680 8681

gprsLocationUpdatingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { updateGprsLocation} }

8682 8683 This package is v3 only.

8684 17.2.2.36

Gprs Interrogation

8685 This operation package includes the operations required for interrogation procedures between HLR and GGSN.
8686 8687 8688 8689

gprsInterrogationPackage-v4 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs} }

8690 8691 The v3-equivalent package is defined as follows. 8692


8693 8694 8695 8696

gprsInterrogationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs} }

8697

8698 17.2.2.37

Failure reporting

8699 This operation package includes the operations required for failure reporting between HLR and GGSN.
8700 8701 8702 8703

failureReportingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { failureReport} }

8704 8705 This package is v3 only.

8706 17.2.2.38

GPRS notifying

8707 This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and 8708 GGSN.
8709 8710 8711 8712

gprsNotifyingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is GGSN if Consumer is HLR CONSUMER INVOKES { noteMsPresentForGprs} }

8713 8714 This package is v3 only.

1154

3GPP

8715 17.2.2.39

1155 Release 6 1156 1157

290

3GPP TS 29.002 V6.11.0 (2005-09)

Supplementary Service invocation notification

8716 This operation package includes the operations required for Supplementary Service invocation notification procedures 8717 between the MSC and the gsmSCF and between the HLR and the gsmSCF.
8718 8719 8720 8721 8722 8723

ss-InvocationNotificationPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is gsmSCF if Consumer is MSC -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { ss-InvocationNotification} }

8724 This package is v3 only.

8725 17.2.2.40

Set Reporting State

8726 This operation package includes the operation required for procedures between HLR and VLR to set the reporting state.
8727 8728 8729 8730 8731

setReportingStatePackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { setReportingState} }

8732 This package is v3 only.

8733 17.2.2.41

Status Report

8734 This operation package includes the operation required for procedures between VLR and HLR to report call results and 8735 events.
8736 8737 8738 8739 8740

statusReportPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { statusReport} }

8741 This package is v3 only.

8742 17.2.2.42

Remote User Free

8743 This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free.
8744 8745 8746 8747 8748

remoteUserFreePackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { remoteUserFree} }

8749 This package is v3 only.

8750 17.2.2.43

Call Completion

8751 This operation package includes the operations required for procedures between VLR and HLR for subscriber control of 8752 call completion services.
8753 8754 8755 8756 8757 8758

callCompletionPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerCC-Entry | eraseCC-Entry} }

8759 This package is v3 only.

8760 17.2.2.44

Location service gateway services

8761 This operation package includes the operations required for location service gateway procedures between GMLC and 8762 HLR.

1158

3GPP

1159 Release 6 1160 1161


8763 8764 8765 8766 8767 8768

291

3GPP TS 29.002 V6.11.0 (2005-09)

locationSvcGatewayPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GMLC CONSUMER INVOKES { sendRoutingInfoForLCS} }

This package is v3 only.

8769 17.2.2.45

Location service enquiry

8770 This operation package includes the operations required for the location service enquiry procedures between GMLC and 8771 MSC and between GMLC and SGSN.
8772 8773 8774 8775 8776

locationSvcEnquiryPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is MSC or SGSN if Consumer is GMLC CONSUMER INVOKES { provideSubscriberLocation} }

8777 This package is v3 only.

8778 17.2.2.45A

Location service reporting

8779 This operation package includes the operations required for the location service enquiry procedures between MSC and 8780 GMLC and between SGSN and GMLC.
8781 8782 8783 8784 8785

locationSvcReportingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is GMLC if Consumer is MSC -- Supplier is GMLC if Consumer is SGSN CONSUMER INVOKES { subscriberLocationReport} }

8786 8787 17.2.2.46 8788 17.2.2.47 8789 17.2.2.48 8790 17.2.2.49 Void Void Void IST Alerting

8791 This operation package includes the operation required for alerting procedures between the MSC (Visited MSC or 8792 Gateway MSC) and HLR.
8793 8794 8795 8796 8797 8798

ist-AlertingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VMSC -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { istAlert} }

8799 This package is v3 only.

8800 17.2.2.50

Service Termination

8801 This operation package includes the operation required for immediate service termination procedures between the HLR 8802 and the Visited MSC or between the HLR and the Gateway MSC.
8803 8804 8805 8806 8807

serviceTerminationPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VMSC or GMSC if Consumer is HLR CONSUMER INVOKES { istCommand} }

8808 This package is v3 only.

1162

3GPP

8809 17.2.2.51

1163 Release 6 1164 1165

292

3GPP TS 29.002 V6.11.0 (2005-09)

Mobility Management event notification

8810 This operation package includes the operations required for Mobility Management event notification procedures 8811 between VLR and gsmSCF.
8812 8813 8814 8815

mm-EventReportingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is gsmSCF if Consumer is VLR CONSUMER INVOKES { noteMM-Event} }

8816 This package is v3 only.

8817 17.2.2.52

Any time information handling

8818 This operation package includes the operations required for any time information handling procedures between gsmSCF 8819 and HLR.
8820 8821 8822 8823 8824 8825

anyTimeInformationHandlingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeSubscriptionInterrogation | anyTimeModification} }

8826 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
-- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { noteSubscriberDataModified} } OPERATION-PACKAGE ::= {

This package is v3 only.

8827 17.2.2.54

Authentication Failure Report

8828 This operation package includes the operation required for procedures between VLR and HLR or the SGSN and the 8829 HLR for reporting of authentication failures.
8830 8831 8832 8833 8834 8835

authenticationFailureReportPackage-v3

-- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { authenticationFailureReport} }

OPERATION-PACKAGE ::= {

8836 This package is v3 only.

8837 17.2.2.55

Resource Management

8838 This operation package includes the operation required for procedures between GMSC and VMSC for resource 8839 management purpose.
8840 8841 8842 8843 8844

resourceManagementPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VMSC if Consumer is GMSC CONSUMER INVOKES { releaseResources} }

8845 This package is v3 only.

1166

3GPP

1167 Release 6 1168 1169

293

3GPP TS 29.002 V6.11.0 (2005-09)

8846 8847

17.3 Application contexts


17.3.1 General aspects

8848 An application-context is assigned for each dialogue established by a MAP-user. In the present document each 8849 application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and 8850 transmitted to the peer under certain circumstances. 8851 The following ASN.1 information object class is used to describe the main aspects of application-contexts in the 8852 following clauses:
8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863

APPLICATION-CONTEXT ::= CLASS { &Symmetric OPERATION-PACKAGE OPTIONAL, &InitiatorConsumerOf OPERATION-PACKAGE OPTIONAL, &ResponderConsumerOf OPERATION-PACKAGE OPTIONAL, &code OBJECT IDENTIFI