1

3GPP TS 29.002 V7.5.0 (2006-09)

Technical Specification

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

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

3 Release 7 4 5

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

3GPP

7 Release 7 8 9

3GPP TS 29.002 V7.5.0 (2006-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 7 12 13

3GPP TS 29.002 V7.5.0 (2006-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 Void 56 7.3.8 Void 56 7.3.9 Void 56 7.3.10 Void 56 7.4 Sequencing of services.........................................................................................................................................56 7.5 General rules for mapping of services onto TC...................................................................................................57 7.5.1 Mapping of common services...........................................................................................................................57 7.5.2 Mapping of user specific services.....................................................................................................................58 7.6 Definition of parameters......................................................................................................................................59 7.6.1 Common parameters.........................................................................................................................................59 7.6.1.1 Invoke Id 59 7.6.1.2 Linked Id 59 7.6.1.3 Provider error.................................................................................................................................................59 7.6.1.4 User error59 7.6.2 Numbering and identification parameters.........................................................................................................63 7.6.2.1 IMSI 63 7.6.2.2 TMSI 63 7.6.2.3 IMEI 63 7.6.2.3a IMEISV 63 7.6.2.4 Previous location area Id................................................................................................................................63 7.6.2.5 Stored location area Id...................................................................................................................................63 7.6.2.6 Current location area Id..................................................................................................................................63 7.6.2.7 Target location area Id...................................................................................................................................63 7.6.2.8 Target cell Id..................................................................................................................................................63 7.6.2.8A Target RNC Id.............................................................................................................................................63 7.6.2.9 Void 64 7.6.2.10 Originating entity number............................................................................................................................64 7.6.2.11 MSC number................................................................................................................................................64 7.6.2.12 Target MSC number.....................................................................................................................................64 7.6.2.13 HLR number.................................................................................................................................................64 7.6.2.14 VLR number.................................................................................................................................................64 7.6.2.15 HLR Id 64 7.6.2.16 LMSI 64 7.6.2.17 MS ISDN......................................................................................................................................................64 7.6.2.18 OMC Id 64 7.6.2.19 Roaming number..........................................................................................................................................64 7.6.2.19A Relocation Number List............................................................................................................................64 7.6.2.20 Void 64 7.6.2.21 Handover number.........................................................................................................................................64 7.6.2.22 Forwarded-to number...................................................................................................................................64 7.6.2.22A Long forwarded-to number.......................................................................................................................65 7.6.2.22B Long FTN Supported.................................................................................................................................65 7.6.2.23 Forwarded-to subaddress.............................................................................................................................65 7.6.2.24 Called number..............................................................................................................................................65 7.6.2.25 Calling number.............................................................................................................................................65 7.6.2.26 Originally dialled number............................................................................................................................65 7.6.2.27 Service centre address..................................................................................................................................65 7.6.2.28 Zone Code....................................................................................................................................................65 7.6.2.29 MSIsdn-Alert................................................................................................................................................65 7.6.2.30 Location Information...................................................................................................................................65 7.6.2.30a Location Information for GPRS.................................................................................................................65

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

3GPP TS 29.002 V7.5.0 (2006-09)

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

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

3GPP TS 29.002 V7.5.0 (2006-09)

7.6.3.26 CUG feature.................................................................................................................................................73 7.6.3.27 Inter CUG options........................................................................................................................................74 7.6.3.28 Intra CUG restrictions..................................................................................................................................74 7.6.3.29 Extensible SS-Data.......................................................................................................................................74 7.6.3.30 Subscriber State............................................................................................................................................74 7.6.3.31 Requested Info.............................................................................................................................................74 7.6.3.31A Requested Domain....................................................................................................................................74 7.6.3.32 Suppression of Announcement....................................................................................................................74 7.6.3.33 Suppress T-CSI............................................................................................................................................75 7.6.3.34 GMSC CAMEL Subscription Info...............................................................................................................75 7.6.3.35 VLR CAMEL Subscription Info..................................................................................................................75 7.6.3.36 Supported CAMEL Phases in the VLR.......................................................................................................75 7.6.3.36A Supported CAMEL Phases in the SGSN..................................................................................................75 7.6.3.36B Offered CAMEL4 CSIs in the VLR..........................................................................................................75 7.6.3.36C Offered CAMEL4 CSIs in the SGSN........................................................................................................75 7.6.3.36D Offered CAMEL4 CSIs.............................................................................................................................75 7.6.3.36E Offered CAMEL4 CSIs in interrogating node...........................................................................................75 7.6.3.36F Offered CAMEL4 CSIs in VMSC.............................................................................................................75 7.6.3.36G Offered CAMEL4 Functionalities............................................................................................................75 7.6.3.36H Supported CAMEL Phases........................................................................................................................75 7.6.3.36I Supported CAMEL Phases in interrogating node.......................................................................................75 7.6.3.37 CUG Subscription Flag................................................................................................................................75 7.6.3.38 CAMEL Subscription Info Withdraw..........................................................................................................76 7.6.3.39 Voice Group Call Service (VGCS) Data.....................................................................................................76 7.6.3.40 Voice Broadcast Service (VBS) Data..........................................................................................................76 7.6.3.41 ISDN bearer capability.................................................................................................................................76 7.6.3.42 Lower layer Compatibility...........................................................................................................................76 7.6.3.43 High Layer Compatibility............................................................................................................................76 7.6.3.44 Alerting Pattern............................................................................................................................................76 7.6.3.45 GPRS Subscription Data Withdraw.............................................................................................................76 7.6.3.46 GPRS Subscription Data..............................................................................................................................76 7.6.3.47 QoS-Subscribed............................................................................................................................................76 7.6.3.48 VPLMN address allowed.............................................................................................................................76 7.6.3.49 Roaming Restricted In SGSN Due To Unsupported Feature.......................................................................76 7.6.3.50 Network Access Mode.................................................................................................................................76 7.6.3.51 Mobile Not Reachable Reason.....................................................................................................................77 7.6.3.52 Cancellation Type........................................................................................................................................77 7.6.3.53 All GPRS Data.............................................................................................................................................77 7.6.3.54 Complete Data List Included.......................................................................................................................77 7.6.3.55 PDP Context Identifier.................................................................................................................................77 7.6.3.56 LSA Information..........................................................................................................................................77 7.6.3.57 SoLSA support indicator..............................................................................................................................77 7.6.3.58 LSA Information Withdraw.........................................................................................................................77 7.6.3.59 LMU Indicator.............................................................................................................................................77 7.6.3.60 LCS Information..........................................................................................................................................77 7.6.3.61 GMLC List...................................................................................................................................................77 7.6.3.62 LCS Privacy Exception List.........................................................................................................................78 7.6.3.62A Additional LCS Privacy Exception List....................................................................................................78 7.6.3.63 LCS Privacy Exception Parameters.............................................................................................................78 7.6.3.64 External Client List .....................................................................................................................................78 7.6.3.65 Internal Client List ......................................................................................................................................78 7.6.3.65A MO-LR List...............................................................................................................................................78 7.6.3.65B Privacy Notification to MS User...............................................................................................................79 7.6.3.65C GMLC List Withdraw...............................................................................................................................79 7.6.3.65D Service Type List .....................................................................................................................................79 7.6.3.66 IST Alert Timer............................................................................................................................................79 7.6.3.67 Call Termination Indicator...........................................................................................................................79 7.6.3.68 IST Information Withdraw...........................................................................................................................79 7.6.3.69 IST Support Indicator...................................................................................................................................79 7.6.3.70 Super-Charger Supported In HLR...............................................................................................................79 7.6.3.71 Super-Charger Supported In Serving Network Entity.................................................................................79

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

3GPP TS 29.002 V7.5.0 (2006-09)

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

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

3GPP TS 29.002 V7.5.0 (2006-09)

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

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

3GPP TS 29.002 V7.5.0 (2006-09)

7.6.7.9 Failure cause...................................................................................................................................................93 7.6.7.10 Re-attempt....................................................................................................................................................93 7.6.7.11 Access Type.................................................................................................................................................93 7.6.8 Short message parameters.................................................................................................................................93 7.6.8.1 SM-RP-DA.....................................................................................................................................................93 7.6.8.2 SM-RP-OA.....................................................................................................................................................93 7.6.8.3 MWD status...................................................................................................................................................93 7.6.8.4 SM-RP-UI......................................................................................................................................................94 7.6.8.5 SM-RP-PRI....................................................................................................................................................94 7.6.8.6 SM Delivery Outcome...................................................................................................................................94 7.6.8.7 More Messages To Send................................................................................................................................94 7.6.8.8 Alert Reason...................................................................................................................................................94 7.6.8.9 Absent Subscriber Diagnostic SM.................................................................................................................94 7.6.8.10 Alert Reason Indicator.................................................................................................................................94 7.6.8.11 Additional SM Delivery Outcome...............................................................................................................94 7.6.8.12 Additional Absent Subscriber Diagnostic SM.............................................................................................94 7.6.8.13 Delivery Outcome Indicator.........................................................................................................................94 7.6.8.14 GPRS Node Indicator...................................................................................................................................94 7.6.8.15 GPRS Support Indicator...............................................................................................................................94 7.6.8.16 SM-RP-MTI.................................................................................................................................................95 7.6.8.17 SM-RP-SMEA.............................................................................................................................................95 7.6.9 Access and signalling system related parameters.............................................................................................95 7.6.9.1 AN-apdu 95 7.6.9.2 CM service type.............................................................................................................................................95 7.6.9.3 Access connection status................................................................................................................................95 7.6.9.4 External Signal Information...........................................................................................................................95 7.6.9.5 Access signalling information........................................................................................................................95 7.6.9.6 Location update type......................................................................................................................................96 7.6.9.7 Protocol ID.....................................................................................................................................................96 7.6.9.8 Network signal information...........................................................................................................................96 7.6.9.8A Network signal information 2.....................................................................................................................96 7.6.9.9 Call Info 97 7.6.9.10 Additional signal info...................................................................................................................................97 7.6.10 System operations parameters.........................................................................................................................97 7.6.10.1 Network resources........................................................................................................................................97 7.6.10.2 Trace reference.............................................................................................................................................97 7.6.10.2A Trace reference 2.......................................................................................................................................97 7.6.10.3 Trace type.....................................................................................................................................................98 7.6.10.4 Additional network resources......................................................................................................................98 7.6.10.5 Trace depth list.............................................................................................................................................98 7.6.10.6 Trace NE type list.........................................................................................................................................98 7.6.10.7 Trace interface list........................................................................................................................................98 7.6.10.8 Trace event list.............................................................................................................................................98 7.6.10.9 Trace support indicator................................................................................................................................98 7.6.10.10 Trace Propagation List...............................................................................................................................98 7.6.11 Location Service Parameters ..........................................................................................................................98 7.6.11.1 Age of Location Estimate.............................................................................................................................98 7.6.11.2 Deferred MT-LR Response Indicator .........................................................................................................98 7.6.11.3 Deferred MT-LR Data..................................................................................................................................99 7.6.11.4 LCS Client ID..............................................................................................................................................99 7.6.11.5 LCS Event....................................................................................................................................................99 7.6.11.7 LCS Priority.................................................................................................................................................99 7.6.11.8 LCS QoS......................................................................................................................................................99 7.6.11.9 CS LCS Not Supported by UE.....................................................................................................................99 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.....................................................99 7.6.11.10 PS LCS Not Supported by UE...................................................................................................................99 7.6.11.11 Location Estimate.....................................................................................................................................100 7.6.11.11A GERAN Positioning Data.....................................................................................................................100 7.6.11.11B UTRAN Positioning Data......................................................................................................................100

34

3GPP

425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 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 7 36 37

10

3GPP TS 29.002 V7.5.0 (2006-09)

7.6.11.12 Location Type..........................................................................................................................................100 7.6.11.13 NA-ESRD................................................................................................................................................100 7.6.11.14 NA-ESRK................................................................................................................................................100 7.6.11.15 LCS Service Type Id...............................................................................................................................100 7.6.11.16 Privacy Override......................................................................................................................................101 7.6.11.17 Supported LCS Capability Sets................................................................................................................101 7.6.11.18 LCS Codeword........................................................................................................................................101 7.6.11.19 NA-ESRK Request...................................................................................................................................101 7.6.11.20 Supported GAD Shapes...........................................................................................................................101 7.6.11.21 Additional Location Estimate..................................................................................................................101 7.6.11.22 Cell Id Or SAI..........................................................................................................................................101 7.6.11.23 LCS-Reference Number...........................................................................................................................101 7.6.11.24 LCS Privacy Check..................................................................................................................................101 7.6.11.25 Additional LCS Capability Sets...............................................................................................................102 7.6.11.26 Area Event Info........................................................................................................................................102 7.6.11.27 Velocity Estimate.....................................................................................................................................102 7.6.11.28 Accuracy Fulfilment Indicator.................................................................................................................102 7.6.11.29 MO-LR Short Circuit Indicator................................................................................................................102 7.6.11.30 Reporting PLMN List.............................................................................................................................102 7.6.11.31 Periodic LDR information.......................................................................................................................102 7.6.11.32 Sequence Number...................................................................................................................................102 7.6.12 Void 103 7.7 Representation of a list of a basic parameter in service-primitives...................................................................103 8.1 Location management services..........................................................................................................................103 8.1.1 Void 103 8.1.1.1 Void 103 8.1.1.2 Void 103 8.1.1.3 Void 103 8.1.2 MAP_UPDATE_LOCATION service............................................................................................................103 8.1.2.1 Definition.....................................................................................................................................................103 8.1.2.2 Service primitives.........................................................................................................................................103 8.1.2.3 Parameter definitions and use......................................................................................................................104 8.1.3 MAP_CANCEL_LOCATION service...........................................................................................................106 8.1.3.1 Definition.....................................................................................................................................................106 8.1.3.2 Service primitives.........................................................................................................................................106 8.1.3.3 Parameter definitions and use......................................................................................................................106 8.1.4 MAP_SEND_IDENTIFICATION service.....................................................................................................107 8.1.4.1 Definition.....................................................................................................................................................107 8.1.4.2 Service primitives.........................................................................................................................................107 8.1.4.3 Parameter definitions and use......................................................................................................................107 8.1.5 Void 108 8.1.5.1 Void 108 8.1.5.2 Void 108 8.1.5.3 Void 108 8.1.6 MAP_PURGE_MS service.............................................................................................................................108 8.1.6.1 Definition.....................................................................................................................................................109 8.1.6.2 Service primitives.........................................................................................................................................109 8.1.6.3 Parameter definitions and use......................................................................................................................109 8.1.7 MAP_UPDATE_GPRS_LOCATION service................................................................................................110 8.1.7.1 Definition.....................................................................................................................................................110 8.1.7.2 Service primitives.........................................................................................................................................110 8.1.7.3 Parameter definitions and use......................................................................................................................110 8.1.8 MAP-NOTE-MM-EVENT.............................................................................................................................112 8.1.8.1 Definition.....................................................................................................................................................112 8.1.8.2 Service primitives.........................................................................................................................................112 8.1.8.3 Parameter use...............................................................................................................................................113 8.2 Paging and search...............................................................................................................................................114 8.2.1 MAP_PAGE service.......................................................................................................................................114 8.2.1.1 Definition.....................................................................................................................................................114

448 8 Mobility services................................................................................................................................103

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

11

3GPP TS 29.002 V7.5.0 (2006-09)

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

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 599 600 601 602 603 604

43 Release 7 44 45

12

3GPP TS 29.002 V7.5.0 (2006-09)

8.7.1.2 Service primitives.........................................................................................................................................134 8.7.1.3 Parameter use...............................................................................................................................................134 8.7.2 MAP_OBTAIN_IMEI service........................................................................................................................135 8.7.2.1 Definition.....................................................................................................................................................135 8.7.2.2 Service primitives.........................................................................................................................................135 8.7.2.3 Parameter use...............................................................................................................................................135 8.8 Subscriber management services.......................................................................................................................136 8.8.1 MAP-INSERT-SUBSCRIBER-DATA service..............................................................................................136 8.8.1.1 Definition.....................................................................................................................................................136 8.8.1.2 Service primitives.........................................................................................................................................136 8.8.1.3 Parameter use...............................................................................................................................................137 8.8.1.4 Basic service information related to supplementary services......................................................................146 8.8.2 MAP-DELETE-SUBSCRIBER-DATA service.............................................................................................147 8.8.2.1 Definition.....................................................................................................................................................147 8.8.2.2 Service primitives.........................................................................................................................................147 8.8.2.3 Parameter use...............................................................................................................................................147 8.9 Identity management services............................................................................................................................150 8.9.1 MAP-PROVIDE-IMSI service.......................................................................................................................150 8.9.1.1 Definition.....................................................................................................................................................150 8.9.1.2 Service primitives.........................................................................................................................................150 8.9.1.3 Parameter use...............................................................................................................................................150 8.9.2 MAP-FORWARD-NEW-TMSI service.........................................................................................................151 8.9.2.1 Definition.....................................................................................................................................................151 8.9.2.2 Service primitives.........................................................................................................................................151 8.9.2.3 Parameter use...............................................................................................................................................151 8.10 Fault recovery services.....................................................................................................................................151 8.10.1 MAP_RESET service....................................................................................................................................151 8.10.1.1 Definition...................................................................................................................................................151 8.10.1.2 Service primitives.......................................................................................................................................151 8.10.1.3 Parameter definition and use......................................................................................................................151 8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service............................................................................152 8.10.2.1 Definition...................................................................................................................................................152 8.10.2.2 Service primitives.......................................................................................................................................152 8.10.2.3 Parameter definition and use......................................................................................................................152 8.10.3 MAP_RESTORE_DATA service.................................................................................................................152 8.10.3.1 Definition...................................................................................................................................................152 8.10.3.2 Service primitives.......................................................................................................................................152 8.10.3.3 Parameter definitions and use....................................................................................................................153 8.11 Subscriber Information services.......................................................................................................................154 8.11.1 MAP-ANY-TIME-INTERROGATION service...........................................................................................154 8.11.1.1 Definition...................................................................................................................................................154 8.11.1.2 Service primitives.......................................................................................................................................154 8.11.1.3 Parameter definition and use......................................................................................................................155 8.11.2 MAP-PROVIDE-SUBSCRIBER-INFO service...........................................................................................155 8.11.2.1 Definition...................................................................................................................................................155 8.11.2.2 Service primitives.......................................................................................................................................156 8.11.2.3 Parameter definition and use......................................................................................................................156 8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service.............................................................156 8.11.3.1 Definition...................................................................................................................................................156 8.11.3.2 Service primitives.......................................................................................................................................156 8.11.3.3 Parameter definition and use......................................................................................................................157 8.11.4 MAP-ANY-TIME-MODIFICATION service..............................................................................................157 8.11.4.1 Definition...................................................................................................................................................157 8.11.4.2 Service primitives.......................................................................................................................................157 8.11.4.3 Parameter definition and use......................................................................................................................158 8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service...........................................................................158 8.11.5.1 Definition...................................................................................................................................................158 8.11.5.2 Service primitives.......................................................................................................................................159 8.11.5.3 Parameter definition and use......................................................................................................................159

46

3GPP

605 9 Operation and maintenance services..................................................................................................160

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

47 Release 7 48 49

13

3GPP TS 29.002 V7.5.0 (2006-09)

9.1 Subscriber tracing services.................................................................................................................................160 9.1.1 MAP-ACTIVATE-TRACE-MODE service...................................................................................................160 9.1.1.1 Definition.....................................................................................................................................................160 9.1.1.2 Service primitives.........................................................................................................................................160 9.1.1.3 Parameter use...............................................................................................................................................160 9.1.2 MAP-DEACTIVATE-TRACE-MODE service..............................................................................................161 9.1.2.1 Definition.....................................................................................................................................................161 9.1.2.2 Service primitives.........................................................................................................................................162 9.1.2.3 Parameter use...............................................................................................................................................162 9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service.......................................................................................162 9.1.3.1 Definition.....................................................................................................................................................162 9.1.3.2 Service primitives.........................................................................................................................................162 9.1.3.3 Parameter use...............................................................................................................................................163 9.2 Other operation and maintenance services.........................................................................................................163 9.2.1 MAP-SEND-IMSI service..............................................................................................................................163 9.2.1.1 Definition.....................................................................................................................................................163 9.2.1.2 Service primitives.........................................................................................................................................163 9.2.1.3 Parameter use...............................................................................................................................................163 10.1 MAP_SEND_ROUTING_INFORMATION service......................................................................................164 10.1.1 Definition......................................................................................................................................................164 10.1.2 Service primitives..........................................................................................................................................164 10.1.3 Parameter use................................................................................................................................................165 10.2 MAP_PROVIDE_ROAMING_NUMBER service.........................................................................................170 10.2.1 Definition......................................................................................................................................................170 10.2.2 Service primitives..........................................................................................................................................170 10.2.3 Parameter use................................................................................................................................................171 10.3 MAP_RESUME_CALL_HANDLING service...............................................................................................173 10.3.1 Definition......................................................................................................................................................173 10.3.2 Service primitives..........................................................................................................................................173 10.3.3 Parameter use................................................................................................................................................173 10.4 MAP_PREPARE_GROUP_CALL service.....................................................................................................174 10.4.1 Definition......................................................................................................................................................174 10.4.2 Service primitives..........................................................................................................................................175 10.4.3 Parameter definitions and use.......................................................................................................................175 10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service............................................................................176 10.5.1 Definitions.....................................................................................................................................................176 10.5.2 Service primitives..........................................................................................................................................176 10.5.3 Parameter definitions and use.......................................................................................................................176 10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service.........................................................................177 10.6.1 Definitions.....................................................................................................................................................177 10.6.2 Service primitives..........................................................................................................................................177 10.6.3 Parameter definitions and use.......................................................................................................................177 10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service.................................................................................178 10.7.1 Definitions.....................................................................................................................................................178 10.7.2 Service primitives..........................................................................................................................................178 10.7.3 Parameter definitions and use.......................................................................................................................179 10.7A MAP_SEND_GROUP_CALL_INFO service..............................................................................................179 10.7A.1 Definitions..................................................................................................................................................179 10.7A.2 Service primitives.......................................................................................................................................179 10.7A.3 Parameter definitions and use....................................................................................................................180 10.8 Void 181 10.9 Void 181 10.10 MAP_SET_REPORTING_STATE service...................................................................................................181 10.10.1 Definition....................................................................................................................................................181 10.10.2 Service primitives........................................................................................................................................181 10.10.3 Parameter use..............................................................................................................................................181 10.11 MAP_STATUS_REPORT service................................................................................................................182 10.11.1 Definition....................................................................................................................................................182

624 10 Call handling services......................................................................................................................164

50

3GPP

665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682

51 Release 7 52 53

14

3GPP TS 29.002 V7.5.0 (2006-09)

10.11.2 Service primitives........................................................................................................................................182 10.11.3 Parameter use..............................................................................................................................................182 10.12 MAP_REMOTE_USER_FREE service........................................................................................................183 10.12.1 Definition....................................................................................................................................................183 10.12.2 Service primitives........................................................................................................................................183 10.12.3 Parameter use..............................................................................................................................................183 10.13 MAP_IST_ALERT service............................................................................................................................184 10.13.1 Definition....................................................................................................................................................184 10.13.2 Service primitives........................................................................................................................................184 10.13.3 Parameter use..............................................................................................................................................184 10.14 MAP_IST_COMMAND service...................................................................................................................185 10.14.1 Definition....................................................................................................................................................185 10.14.2 Service primitives........................................................................................................................................185 10.14.3 Parameter use..............................................................................................................................................185 10.15 MAP_RELEASE_RESOURCES service......................................................................................................186 10.15.1 Definition....................................................................................................................................................186 10.15.2 Service primitives........................................................................................................................................186 10.15.3 Parameter use..............................................................................................................................................186 11.1 MAP_REGISTER_SS service.........................................................................................................................186 11.1.1 Definition......................................................................................................................................................186 11.1.2 Service primitives..........................................................................................................................................186 11.1.3 Parameter use................................................................................................................................................187 11.2 MAP_ERASE_SS service................................................................................................................................188 11.2.1 Definition......................................................................................................................................................188 11.2.2 Service primitives..........................................................................................................................................188 11.2.3 Parameter use................................................................................................................................................188 11.3 MAP_ACTIVATE_SS service........................................................................................................................189 11.3.1 Definition......................................................................................................................................................189 11.3.2 Service primitives..........................................................................................................................................189 11.3.3 Parameter use................................................................................................................................................189 11.4 MAP_DEACTIVATE_SS service...................................................................................................................190 11.4.1 Definitions.....................................................................................................................................................190 11.4.2 Service primitives..........................................................................................................................................191 11.4.3 Parameter use................................................................................................................................................191 11.5 MAP_INTERROGATE_SS service................................................................................................................192 11.5.1 Definitions.....................................................................................................................................................192 11.5.2 Service primitives..........................................................................................................................................192 11.5.3 Parameter use................................................................................................................................................192 11.6 Void 194 11.7 MAP_REGISTER_PASSWORD service........................................................................................................194 11.7.1 Definitions.....................................................................................................................................................194 11.7.2 Service primitives..........................................................................................................................................194 11.7.3 Parameter use................................................................................................................................................194 11.8 MAP_GET_PASSWORD service...................................................................................................................195 11.8.1 Definitions.....................................................................................................................................................195 11.8.2 Service primitives..........................................................................................................................................195 11.8.3 Parameter use................................................................................................................................................195 11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service.....................................................................195 11.9.1 Definitions.....................................................................................................................................................196 11.9.2 Service primitives..........................................................................................................................................196 11.9.3 Parameter use................................................................................................................................................196 11.10 MAP_UNSTRUCTURED_SS_REQUEST service......................................................................................197 11.10.1 Definitions...................................................................................................................................................197 11.10.2 Service primitives........................................................................................................................................197 11.10.3 Parameter use..............................................................................................................................................197 11.11 MAP_UNSTRUCTURED_SS_NOTIFY service..........................................................................................198 11.11.1 Definitions...................................................................................................................................................198 11.11.2 Service primitives........................................................................................................................................198 11.11.3 Parameter use..............................................................................................................................................198

683 11 Supplementary services related services..........................................................................................186

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

54

3GPP

725 726 727 728 729 730 731 732 733 734 735 736

55 Release 7 56 57

15

3GPP TS 29.002 V7.5.0 (2006-09)

11.12 MAP_SS_INVOCATION_NOTIFY.............................................................................................................199 11.12.1 Definition....................................................................................................................................................199 11.12.2 Service primitives........................................................................................................................................199 11.12.3 Parameter use..............................................................................................................................................199 11.13 MAP_REGISTER_CC_ENTRY service.......................................................................................................200 11.13.1 Definition....................................................................................................................................................200 11.13.2 Service primitives........................................................................................................................................200 11.13.3 Parameter use..............................................................................................................................................200 11.14 MAP_ERASE_CC_ENTRY service.............................................................................................................201 11.14.1 Definition....................................................................................................................................................201 11.14.2 Service primitives........................................................................................................................................201 11.14.3 Parameter use..............................................................................................................................................201 12.1 MAP-SEND-ROUTING-INFO-FOR-SM service...........................................................................................202 12.1.1 Definition......................................................................................................................................................202 12.1.2 Service primitives..........................................................................................................................................202 12.1.3 Parameter use................................................................................................................................................203 12.2 MAP-MO-FORWARD-SHORT-MESSAGE service.....................................................................................204 12.2.1 Definition......................................................................................................................................................204 12.2.2 Service primitives..........................................................................................................................................204 12.2.3 Parameter use................................................................................................................................................204 12.3 MAP-REPORT-SM-DELIVERY-STATUS service.......................................................................................205 12.3.1 Definition......................................................................................................................................................205 12.3.2 Service primitives..........................................................................................................................................205 12.3.3 Parameter use................................................................................................................................................206 12.4 MAP-READY-FOR-SM service.....................................................................................................................206 12.4.1 Definition......................................................................................................................................................207 12.4.2 Service primitives..........................................................................................................................................207 12.4.3 Parameter use................................................................................................................................................207 12.5 MAP-ALERT-SERVICE-CENTRE service....................................................................................................208 12.5.1 Definition......................................................................................................................................................208 12.5.2 Service primitives..........................................................................................................................................208 12.5.3 Parameter use................................................................................................................................................208 12.6 MAP-INFORM-SERVICE-CENTRE service.................................................................................................208 12.6.1 Definition......................................................................................................................................................208 12.6.2 Service primitives..........................................................................................................................................209 12.6.3 Parameter use................................................................................................................................................209 12.7 MAP-SEND-INFO-FOR-MT-SMS service.....................................................................................................209 12.7.1 Definition......................................................................................................................................................209 12.7.2 Service primitives..........................................................................................................................................209 12.7.3 Parameter use................................................................................................................................................210 12.8 MAP-SEND-INFO-FOR-MO-SMS service....................................................................................................210 12.8.1 Definition......................................................................................................................................................210 12.8.2 Service primitives..........................................................................................................................................211 12.8.3 Parameter use................................................................................................................................................211 12.9 MAP-MT-FORWARD-SHORT-MESSAGE service......................................................................................211 12.9.1 Definition......................................................................................................................................................211 12.9.2 Service primitives..........................................................................................................................................211 12.9.3 Parameter use................................................................................................................................................212 12.10 MAP-MT-FORWARD-SM-FOR-VGCS service..........................................................................................213 12.10.1 Definition....................................................................................................................................................213 12.10.2 Service primitives........................................................................................................................................213 12.10.3 Parameter use..............................................................................................................................................213 13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service...................................................................................214 13.1.1 Definition......................................................................................................................................................214 13.1.2 Service primitives..........................................................................................................................................214 13.1.3 Parameter definition and use.........................................................................................................................214 13.2 MAP_FAILURE_REPORT service.................................................................................................................215 13.2.1 Definition......................................................................................................................................................215

737 12 Short message service management services....................................................................................202

738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 779 780 781 782 783 784

778 13 Network-Requested PDP Context Activation services.....................................................................214

58

3GPP

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

59 Release 7 60 61

16

3GPP TS 29.002 V7.5.0 (2006-09)

13.2.2 Service primitives..........................................................................................................................................215 13.2.3 Parameter definition and use.........................................................................................................................215 13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service.......................................................................................216 13.3.1 Definition......................................................................................................................................................216 13.3.2 Service primitives..........................................................................................................................................216 13.3.3 Parameter definition and use.........................................................................................................................216 13A.1 MAP-SEND-ROUTING-INFO-FOR-LCS Service......................................................................................217 13A.1.1 Definition...................................................................................................................................................217 13A.1.2 Service Primitives......................................................................................................................................217 13A.1.3 Parameter Use............................................................................................................................................217 13A.2 MAP-PROVIDE-SUBSCRIBER-LOCATION Service...............................................................................219 13A.2.1 Definition...................................................................................................................................................219 13A.2.2 Service Primitives......................................................................................................................................219 13A.2.3 Parameter Definition and Use....................................................................................................................219 13A.3 MAP-SUBSCRIBER-LOCATION-REPORT Service.................................................................................222 13A.3.1 Definition...................................................................................................................................................222 13A.3.2 Service Primitives......................................................................................................................................222 13A.3.3 Parameter Definition and Use....................................................................................................................223 13A.4 Void...............................................................................................................................................................225 13A.4.1 Void 225 13A.4.2 Void 225 13A.4.3 Void 225 13A.5 Void...............................................................................................................................................................225 13A.5.1 Void 225 13A.5.2 Void 225 13A.5.3 Void 226 13A.6 Void...............................................................................................................................................................226 13A.6.1 Void 226 13A.6.2 Void 226 13A.6.3 Void 226 13A.7 Void...............................................................................................................................................................226 13A.7.1 Void 226 13A.7.2 Void 226 13A.7.3 Void 226 13A.8 Void...............................................................................................................................................................226 13A.8.1 Void 226 13A.8.2 Void 226 13A.8.3 Void 226 13A.9 Void...............................................................................................................................................................226 13A.9.1 Void 226 13A.9.2 Void 226 13A.9.3 Void 226 14.1 Overview..........................................................................................................................................................226 14.2 Underlying services..........................................................................................................................................227 14.3 Model...............................................................................................................................................................227 14.4 Conventions......................................................................................................................................................227 15.1 Handling of unknown operations.....................................................................................................................227 15.2 Dialogue establishment....................................................................................................................................228 15.2.1 Behaviour at the initiating side.....................................................................................................................228 15.2.2 Behaviour at the responding side..................................................................................................................229 15.3 Dialogue continuation......................................................................................................................................230 15.4 Load control.....................................................................................................................................................230 15.5 Procedures for MAP specific services.............................................................................................................230 15.5.1 Service invocation ........................................................................................................................................230 15.5.2 Void 231 15.5.3 Service invocation receipt ............................................................................................................................231

791 13A Location Service Management Services........................................................................................217

828 14 General.............................................................................................................................................226

833 15 Elements of procedure......................................................................................................................227

62

3GPP

844 15.5.4 Void 231 845 15.5.5 Handling of components received from TC..................................................................................................231 846 15.6 SDL descriptions..............................................................................................................................................231

63 Release 7 64 65

17

3GPP TS 29.002 V7.5.0 (2006-09)

847 16 Mapping on to TC services..............................................................................................................264

848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 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

16.1 Dialogue control...............................................................................................................................................264 16.1.1 Directly mapped parameters.........................................................................................................................264 16.1.2 Use of other parameters of dialogue handling primitives.............................................................................264 16.1.2.1 Dialogue Id.................................................................................................................................................264 16.1.2.2 Application-context-name..........................................................................................................................264 16.1.2.3 User information........................................................................................................................................264 16.1.2.4 Component present.....................................................................................................................................264 16.1.2.5 Termination................................................................................................................................................264 16.1.2.6 P-Abort-Cause............................................................................................................................................264 16.1.2.7 Quality of service.......................................................................................................................................264 16.2 Service specific procedures..............................................................................................................................265 16.2.1 Directly mapped parameters.........................................................................................................................265 16.2.2 Use of other parameters of component handling primitives.........................................................................265 16.2.2.1 Dialogue Id.................................................................................................................................................265 16.2.2.2 Class 265 16.2.2.3 Linked Id....................................................................................................................................................265 16.2.2.4 Operation....................................................................................................................................................266 16.2.2.5 Error 267 16.2.2.6 Parameters..................................................................................................................................................267 16.2.2.7 Time out.....................................................................................................................................................267 16.2.2.8 Last component..........................................................................................................................................267 16.2.2.9 Problem code..............................................................................................................................................267 16.2.2.9.1 Mapping to MAP User Error...................................................................................................................267 16.2.2.9.2 Mapping to MAP Provider Error parameter...........................................................................................268 16.2.2.9.3 Mapping to diagnostic parameter............................................................................................................268 17.1 General.............................................................................................................................................................269 17.1.1 Encoding rules...............................................................................................................................................269 17.1.2 Use of TC......................................................................................................................................................269 17.1.2.1 Use of Global Operation and Error codes defined outside MAP...............................................................270 17.1.3 Use of information elements defined outside MAP......................................................................................270 17.1.4 Compatibility considerations........................................................................................................................270 17.1.5 Structure of the Abstract Syntax of MAP.....................................................................................................271 17.1.6 Application Contexts.....................................................................................................................................273 17.2 Operation packages..........................................................................................................................................274 17.2.1 General aspects..............................................................................................................................................274 17.2.2 Packages specifications.................................................................................................................................275 17.2.2.1 Location updating.......................................................................................................................................275 17.2.2.2 Location cancellation.................................................................................................................................275 17.2.2.3 Roaming number enquiry...........................................................................................................................275 17.2.2.4 Information retrieval..................................................................................................................................276 17.2.2.5 Inter-VLR information retrieval.................................................................................................................276 17.2.2.6 IMSI retrieval.............................................................................................................................................276 17.2.2.7 Call control transfer....................................................................................................................................276 17.2.2.8 Void 277 17.2.2.9 Void 277 17.2.2.10 Interrogation.............................................................................................................................................277 17.2.2.11 Void 277 17.2.2.12 Handover Control.....................................................................................................................................277 17.2.2.13 Subscriber Data management stand alone................................................................................................277 17.2.2.14 Equipment management...........................................................................................................................278 17.2.2.15 Subscriber data management....................................................................................................................278 17.2.2.16 Location register restart............................................................................................................................278 17.2.2.17 Tracing stand-alone..................................................................................................................................278 17.2.2.18 Functional SS handling............................................................................................................................278 17.2.2.19 Tracing.....................................................................................................................................................279

873 17 Abstract syntax of the MAP protocol...............................................................................................269

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

18

3GPP TS 29.002 V7.5.0 (2006-09)

17.2.2.20 Binding.....................................................................................................................................................279 17.2.2.21 Unstructured SS handling........................................................................................................................279 17.2.2.22 MO Short message relay services............................................................................................................279 17.2.2.23 Short message gateway services..............................................................................................................280 17.2.2.24 MT Short message relay services.............................................................................................................280 17.2.2.25 Void 280 17.2.2.26 Message waiting data management..........................................................................................................280 17.2.2.27 Alerting....................................................................................................................................................280 17.2.2.28 Data restoration........................................................................................................................................281 17.2.2.29 Purging.....................................................................................................................................................281 17.2.2.30 Subscriber information enquiry................................................................................................................281 17.2.2.31 Any time information enquiry..................................................................................................................281 17.2.2.32 Group Call Control...................................................................................................................................282 17.2.2.32A Group Call Info Retrieval......................................................................................................................282 17.2.2.33 Void 282 17.2.2.34 Void 282 17.2.2.35 Gprs location updating.............................................................................................................................282 17.2.2.36 Gprs Interrogation....................................................................................................................................283 17.2.2.37 Failure reporting.......................................................................................................................................283 17.2.2.38 GPRS notifying........................................................................................................................................283 17.2.2.39 Supplementary Service invocation notification.......................................................................................283 17.2.2.40 Set Reporting State...................................................................................................................................284 17.2.2.41 Status Report............................................................................................................................................284 17.2.2.42 Remote User Free.....................................................................................................................................284 17.2.2.43 Call Completion.......................................................................................................................................284 17.2.2.44 Location service gateway services...........................................................................................................284 17.2.2.45 Location service enquiry..........................................................................................................................284 17.2.2.45A Location service reporting.....................................................................................................................285 17.2.2.46 Void 285 17.2.2.47 Void 285 17.2.2.48 Void 285 17.2.2.49 IST Alerting.............................................................................................................................................285 17.2.2.50 Service Termination.................................................................................................................................285 17.2.2.51 Mobility Management event notification.................................................................................................285 17.2.2.53 Subscriber Data modification notification...............................................................................................286 17.2.2.54 Authentication Failure Report..................................................................................................................286 17.2.2.55 Resource Management.............................................................................................................................286 17.2.2.56 MT Short message relay VGCS services.................................................................................................286 17.3 Application contexts.........................................................................................................................................287 17.3.1 General aspects..............................................................................................................................................287 17.3.2 Application context definitions.....................................................................................................................287 17.3.2.1 Void 287 17.3.2.2 Location Updating......................................................................................................................................287 17.3.2.3 Location Cancellation................................................................................................................................288 17.3.2.4 Roaming number enquiry...........................................................................................................................288 17.3.2.5 Void 288 17.3.2.6 Location Information Retrieval..................................................................................................................288 17.3.2.7 Call control transfer....................................................................................................................................289 17.3.2.8 Void 289 17.3.2.9 - 17.3.2.10 Void.........................................................................................................................................289 17.3.2.11 Location registers restart..........................................................................................................................289 17.3.2.12 Handover control......................................................................................................................................289 17.3.2.13 IMSI Retrieval..........................................................................................................................................290 17.3.2.14 Equipment Management..........................................................................................................................290 17.3.2.15 Information retrieval................................................................................................................................290 17.3.2.16 Inter-VLR information retrieval...............................................................................................................291 17.3.2.17 Stand Alone Subscriber Data Management.............................................................................................291 17.3.2.18 Tracing.....................................................................................................................................................291 17.3.2.19 Network functional SS handling..............................................................................................................292 17.3.2.20 Network unstructured SS handling..........................................................................................................292 17.3.2.21 Short Message Gateway...........................................................................................................................292

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

71 Release 7 72 73

19

3GPP TS 29.002 V7.5.0 (2006-09)

17.3.2.22 Mobile originating Short Message Relay.................................................................................................292 17.3.2.23 Void 293 17.3.2.24 Short message alert..................................................................................................................................293 17.3.2.25 Short message waiting data management................................................................................................293 17.3.2.26 Mobile terminating Short Message Relay................................................................................................293 17.3.2.27 MS purging...............................................................................................................................................294 17.3.2.28 Subscriber information enquiry................................................................................................................294 17.3.2.29 Any time information enquiry..................................................................................................................294 17.3.2.30 Group Call Control...................................................................................................................................294 17.3.2.30A Group Call Info Retrieval......................................................................................................................294 17.3.2.31 Void 295 17.3.2.32 Gprs Location Updating...........................................................................................................................295 17.3.2.33 Gprs Location Information Retreival.......................................................................................................295 17.3.2.34 Failure Reporting.....................................................................................................................................295 17.3.2.35 GPRS Notifying.......................................................................................................................................295 17.3.2.36 Supplementary Service invocation notification.......................................................................................296 17.3.2.37 Reporting..................................................................................................................................................296 17.3.2.38 Call Completion.......................................................................................................................................296 17.3.2.39 Location Service Gateway.......................................................................................................................297 17.3.2.40 Location Service Enquiry.........................................................................................................................297 17.3.2.41 Void 297 17.3.2.42 Void 297 17.3.2.43 Void 297 17.3.2.44 IST Alerting.............................................................................................................................................297 17.3.2.45 Service Termination.................................................................................................................................297 17.3.2.46 Mobility Management event notification.................................................................................................298 17.3.2.48 Subscriber Data modification notification...............................................................................................298 17.3.2.49 Authentication Failure Report..................................................................................................................298 17.3.2.50 Resource Management.............................................................................................................................298 17.3.2.51 Mobile terminating Short Message Relay VGCS....................................................................................299 17.3.3 ASN.1 Module for application-context-names.............................................................................................299 17.4 MAP Dialogue Information.............................................................................................................................301 17.5 MAP operation and error codes.......................................................................................................................303 17.6 MAP operations and errors..............................................................................................................................305 17.6.1 Mobile Service Operations............................................................................................................................305 17.6.2 Operation and Maintenance Operations........................................................................................................312 17.6.3 Call Handling Operations..............................................................................................................................313 17.6.4 Supplementary service operations.................................................................................................................316 17.6.5 Short message service operations..................................................................................................................320 17.6.6 Errors 323 17.6.7 Group Call operations...................................................................................................................................329 17.6.8 Location service operations...........................................................................................................................331 17.6.9 Void 332 17.7 MAP constants and data types.........................................................................................................................332 17.7.1 Mobile Service data types.............................................................................................................................332 17.7.2 Operation and maintenance data types..........................................................................................................366 17.7.3 Call handling data types................................................................................................................................369 17.7.4 Supplementary service data types.................................................................................................................376 17.7.5 Supplementary service codes........................................................................................................................380 17.7.6 Short message data types..............................................................................................................................383 17.7.7 Error data types.............................................................................................................................................386 17.7.8 Common data types.......................................................................................................................................392 17.7.9 Teleservice Codes.........................................................................................................................................401 17.7.10 Bearer Service Codes..................................................................................................................................402 17.7.11 Extension data types....................................................................................................................................404 17.7.12 Group Call data types..................................................................................................................................405 17.7.13 Location service data types.........................................................................................................................407 17.7.14 Void 417

1023 18 General on MAP user procedures.....................................................................................................418

1024 18.1 Introduction......................................................................................................................................................418

74

3GPP

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

75 Release 7 76 77

20

3GPP TS 29.002 V7.5.0 (2006-09)

18.2 Common aspects of user procedure descriptions.............................................................................................418 18.2.1 General conventions......................................................................................................................................418 18.2.2 Naming conventions......................................................................................................................................418 18.2.3 Convention on primitives parameters...........................................................................................................419 18.2.3.1 Open service...............................................................................................................................................419 18.2.3.2 Close service..............................................................................................................................................420 18.2.4 Version handling at dialogue establishment.................................................................................................420 18.2.4.1 Behaviour at the initiating side..................................................................................................................420 18.2.4.2 Behaviour at the responding side...............................................................................................................420 18.2.5 Abort Handling..............................................................................................................................................420 18.2.6 SDL conventions...........................................................................................................................................420 18.3 Interaction between MAP Provider and MAP Users.......................................................................................421 19.1 Location management Procedures...................................................................................................................422 19.1.1 Location updating..........................................................................................................................................423 19.1.1.1 General 423 19.1.1.2 Procedures in the VLR...............................................................................................................................428 19.1.1.3 Procedure in the PVLR..............................................................................................................................428 19.1.1.4 Procedure in the SGSN..............................................................................................................................428 19.1.1.5 Procedures in the HLR...............................................................................................................................429 19.1.2 Location Cancellation...................................................................................................................................449 19.1.2.1 General 449 19.1.2.2 Procedure in the HLR.................................................................................................................................449 19.1.2.3 Procedure in the VLR.................................................................................................................................450 19.1.2.4 Procedure in the SGSN..............................................................................................................................450 19.1.3 Void 457 19.1.4 MS Purging...................................................................................................................................................457 19.1.4.1 General 457 19.1.4.2 Procedure in the VLR.................................................................................................................................457 19.1.4.3 Procedure in the SGSN .............................................................................................................................457 19.1.4.4 Procedure in the HLR.................................................................................................................................458 19.2 Handover procedures.......................................................................................................................................463 19.2.1 General..........................................................................................................................................................463 19.2.2 Procedure in MSC-A.....................................................................................................................................466 19.2.2.1 Basic handover...........................................................................................................................................466 19.2.2.2 Handling of access signalling.....................................................................................................................467 19.2.2.3 Subsequent handover.................................................................................................................................467 19.2.3 Procedure in MSC-B.....................................................................................................................................467 19.2.3.1 Basic handover...........................................................................................................................................468 19.2.3.2 Handling of access signalling.....................................................................................................................468 19.2.3.3 Subsequent handover.................................................................................................................................468 19.2.4 Macro Receive_Error_From_HO_CA..........................................................................................................468 19.2.5 Procedure in VLR-B.....................................................................................................................................468 19.3 Fault recovery procedures................................................................................................................................487 19.3.1 VLR fault recovery procedures.....................................................................................................................487 19.3.1.1 General 487 19.3.1.2 Procedure in the VLR.................................................................................................................................488 19.3.1.3 Procedure in the HLR.................................................................................................................................488 19.3.2 HLR fault recovery procedures.....................................................................................................................490 19.3.2.1 General 490 19.3.2.2 Procedure in the HLR.................................................................................................................................491 19.3.2.3 Procedure in the VLR.................................................................................................................................491 19.3.2.4 Procedure in the SGSN..............................................................................................................................492 19.4 Mobility Management event notification procedure........................................................................................498 19.4.1 General..........................................................................................................................................................498 19.4.2 Procedure in the VLR or SGSN....................................................................................................................498 19.4.3 Procedure in the gsmSCF..............................................................................................................................498 19.4 HLR Insert Subscriber Data macros................................................................................................................501 19.5.1 Macro Insert_Subs_Data_Framed_HLR.......................................................................................................501 19.5.2 Macro Insert_GPRS_Subs_Data_Framed_HLR...........................................................................................501

1037 19 Mobility procedures.........................................................................................................................422

78

3GPP

1085 20 Operation and maintenance procedures............................................................................................504

1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144

79 Release 7 80 81

21

3GPP TS 29.002 V7.5.0 (2006-09)

20.1 General.............................................................................................................................................................504 20.1.1 Tracing Co-ordinator for the VLR................................................................................................................504 20.1.2 Tracing Co-ordinator for the SGSN..............................................................................................................504 20.1.3 Subscriber Data Management Co-ordinator for the VLR.............................................................................504 20.1.4 Subscriber Data Management Co-ordinator for the SGSN...........................................................................504 20.2 Tracing procedures...........................................................................................................................................509 20.2.1 Subscriber tracing activation procedure........................................................................................................512 20.2.1.1 Procedures in the HLR...............................................................................................................................512 20.2.1.2 Procedure in the VLR.................................................................................................................................512 20.2.1.3 Procedure in the SGSN..............................................................................................................................512 20.2.2 Subscriber tracing deactivation procedure....................................................................................................512 20.2.2.1 Procedures in the HLR...............................................................................................................................512 20.2.2.2 Procedure in the VLR.................................................................................................................................513 20.2.2.3 Procedure in the SGSN..............................................................................................................................513 20.3 Subscriber data management procedures.........................................................................................................526 20.3.1 Subscriber deletion procedure.......................................................................................................................527 20.3.1.1 Procedure in the HLR.................................................................................................................................527 20.3.1.2 Procedure in the VLR.................................................................................................................................527 20.3.1.3 Procedure in the SGSN..............................................................................................................................527 20.3.2 Subscriber data modification procedure........................................................................................................528 20.3.2.1 Procedure in the HLR.................................................................................................................................528 20.3.2.2 Procedures in the VLR...............................................................................................................................529 20.3.2.3 Procedures in the SGSN.............................................................................................................................529 20.4 Subscriber Identity procedure..........................................................................................................................541 20.4.1 Procedure in the VLR....................................................................................................................................541 20.4.2 Procedure in the HLR....................................................................................................................................541 21.1 General.............................................................................................................................................................544 21.2 Retrieval of routing information......................................................................................................................544 21.2.1 General..........................................................................................................................................................544 21.2.2 Procedure in the GMSC................................................................................................................................547 21.2.9 Process in the gsmSCF..................................................................................................................................548 21.2.4 Procedure in the HLR....................................................................................................................................548 21.2.5 Procedure in the VLR to provide a roaming number....................................................................................548 21.2.6 Procedure in the VLR to restore subscriber data..........................................................................................548 21.2.7 Procedure in the VLR to provide subscriber information.............................................................................548 21.3 Transfer of call handling..................................................................................................................................557 21.3.1 General..........................................................................................................................................................557 21.3.2 Process in the VMSC....................................................................................................................................557 21.3.3 Process in the GMSC....................................................................................................................................558 21.4 Inter MSC Group Call Procedures...................................................................................................................561 21.4.1 General..........................................................................................................................................................561 21.4.2 Process in the Anchor MSC..........................................................................................................................561 21.4.3 Process in the Relay MSC.............................................................................................................................562 21.4A Inter MSC Group Call Info Retrieval............................................................................................................567 21.4A.1 General.......................................................................................................................................................567 21.4A.2 Process in the MSC....................................................................................................................................567 21.5 Void 570 21.6 CCBS: monitoring and reporting the status of the subscriber..........................................................................570 21.6.1 Reporting co-ordinator process in the VLR..................................................................................................570 21.6.2 Setting the reporting state stand-alone.......................................................................................................570 21.6.2.1 Process in the HLR.....................................................................................................................................570 21.6.2.2 Process in the VLR.....................................................................................................................................570 21.6.3 Status Reporting............................................................................................................................................570 21.6.3.1 Process in the VLR ....................................................................................................................................571 21.6.3.2 Process in the HLR ....................................................................................................................................572 21.6.4 CCBS: Remote User Free.............................................................................................................................572 21.6.4.1 Process in the HLR ....................................................................................................................................573 21.6.3.2 Process in the VLR ....................................................................................................................................573

1112 21 Call handling procedures..................................................................................................................544

82

3GPP

1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157

83 Release 7 84 85

22

3GPP TS 29.002 V7.5.0 (2006-09)

21.7 Void 586 21.8 Void 586 21.9 Immediate Service Termination (IST).............................................................................................................586 21.9.1 IST Alert........................................................................................................................................................586 21.9.1.1 Procedure in the MSC................................................................................................................................586 21.9.1.2 Procedure in the HLR.................................................................................................................................586 21.9.2 IST Command...............................................................................................................................................586 21.9.2.1 Procedure in the HLR.................................................................................................................................587 21.9.2.2 Procedure in the MSC................................................................................................................................587 21.10 Resource Management...................................................................................................................................592 21.10.1 General........................................................................................................................................................592 21.3.2 Process in the GMSC....................................................................................................................................592 21.3.3 Process in the VMSC....................................................................................................................................592 22.1 Supplementary service co-ordinator processes................................................................................................595 22.1.1 Supplementary service co-ordinator process for the MSC...........................................................................595 22.1.2 Void 595 22.1.3 Functional supplementary service co-ordinator process for the HLR..........................................................595 22.1.4 Call completion supplementary service co-ordinator process for the HLR..................................................595 22.2 Registration procedure.....................................................................................................................................600 22.2.1 General..........................................................................................................................................................600 22.2.2 Procedure in the MSC...................................................................................................................................601 22.2.3 Procedure in the VLR....................................................................................................................................601 22.2.4 Procedure in the HLR....................................................................................................................................601 22.3 Erasure procedure.............................................................................................................................................607 22.3.1 General..........................................................................................................................................................607 22.3.2 Procedure in the MSC...................................................................................................................................608 22.3.3 Procedure in the VLR....................................................................................................................................608 22.3.4 Procedure in the HLR....................................................................................................................................608 22.4 Activation procedure........................................................................................................................................608 22.4.1 General..........................................................................................................................................................608 22.4.2 Procedure in the MSC...................................................................................................................................609 22.4.3 Procedure in the VLR....................................................................................................................................610 22.4.4 Procedure in the HLR....................................................................................................................................610 22.5 Deactivation procedure....................................................................................................................................616 22.5.1 General..........................................................................................................................................................616 22.5.2 Procedure in the MSC...................................................................................................................................617 22.5.3 Procedures in the VLR..................................................................................................................................617 22.5.4 Procedures in the HLR..................................................................................................................................617 22.6 Interrogation procedure....................................................................................................................................617 22.6.1 General..........................................................................................................................................................617 22.6.2 Procedure in the MSC...................................................................................................................................618 22.6.3 Procedures in the VLR..................................................................................................................................618 22.6.4 Procedure in the HLR....................................................................................................................................619 22.7 Void 623 22.8 Password registration procedure......................................................................................................................624 22.8.1 General..........................................................................................................................................................624 22.8.2 Procedure in the MSC...................................................................................................................................626 22.8.3 Procedure in the VLR....................................................................................................................................626 22.8.4 Procedure in the HLR....................................................................................................................................626 22.9 Mobile Initiated USSD procedure....................................................................................................................629 22.9.1 General..........................................................................................................................................................629 22.9.2 Procedure in the MSC...................................................................................................................................629 22.9.3 Procedure in the VLR....................................................................................................................................629 22.9.4 Procedure in the HLR....................................................................................................................................630 22.9.5 Procedures in the gsmSCF/secondary HLR..................................................................................................630 22.10 Network initiated USSD procedure...............................................................................................................644 22.10.1 General........................................................................................................................................................644 22.10.2 Procedure in the MSC.................................................................................................................................644 22.10.3 Procedure in the VLR..................................................................................................................................644

1158 22 Supplementary services procedures..................................................................................................595

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 1201 1202 1203 1204

86

3GPP

1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221

87 Release 7 88 89

23

3GPP TS 29.002 V7.5.0 (2006-09)

22.10.4 Procedure in the HLR..................................................................................................................................645 22.10.5 Procedure in the gsmSCF or secondary HLR.............................................................................................645 22.11 Common macros for clause 22.......................................................................................................................665 22.11.1 SS Password handling macros....................................................................................................................665 22.11.2 Void 665 22.12 Supplementary Service Invocation Notification procedure...........................................................................669 22.12.1 General........................................................................................................................................................669 22.12.2 Procedure in the MSC.................................................................................................................................669 22.12.3 Procedure in the gsmSCF............................................................................................................................669 22.13 Activation of a CCBS request........................................................................................................................672 22.13.1 General........................................................................................................................................................672 22.13.2 Procedure in the VLR..................................................................................................................................672 22.13.3 Procedure in the HLR..................................................................................................................................672 22.14 Deactivation of a CCBS request....................................................................................................................675 22.14.1 General........................................................................................................................................................675 22.14.2 Procedure in the VLR..................................................................................................................................675 22.14.3 Procedure in the HLR..................................................................................................................................675 23.1 General.............................................................................................................................................................678 23.1.1 Mobile originated short message service Co-ordinator for the MSC...........................................................678 23.1.2 Short message Gateway Co-ordinator for the HLR......................................................................................678 23.2 The mobile originated short message transfer procedure................................................................................682 23.2.1 Procedure in the serving MSC......................................................................................................................683 23.2.2 Procedure in the VLR....................................................................................................................................683 23.2.3 Procedure in the SGSN.................................................................................................................................684 23.2.4 Procedure in the SMS Interworking MSC (SMS-IWMSC)..........................................................................684 23.3 The mobile terminated short message transfer procedure................................................................................696 23.3.1 Procedure in the SMS-GMSC.......................................................................................................................699 23.3.2 Procedure in the HLR....................................................................................................................................701 23.3.3 Procedure in the Serving MSC......................................................................................................................701 23.3.4 Procedure in the VLR....................................................................................................................................702 23.3.5 Procedure in the SGSN.................................................................................................................................702 23.4 The Short Message Alert procedure.................................................................................................................739 23.4.1 Procedure in the Serving MSC the MS has memory available..................................................................741 23.4.2 Procedures in the VLR..................................................................................................................................741 23.4.2.1 The Mobile Subscriber is present...............................................................................................................741 23.4.2.2 The MS has memory available...................................................................................................................741 23.4.3 Procedures in the SGSN................................................................................................................................742 23.4.3.1 The Mobile Subscriber is present...............................................................................................................742 23.4.3.2 The Mobile Equipment has memory available..........................................................................................742 23.4.4 Procedure in the HLR....................................................................................................................................742 23.4.5 Procedure in the SMS Interworking MSC....................................................................................................742 23.5 The SM delivery status report procedure.........................................................................................................751 23.5.1 Procedure in the SMS-GMSC.......................................................................................................................751 23.5.2 Procedure in the HLR....................................................................................................................................751 23.6 The macro Report_SM_Delivery_Stat_HLR...................................................................................................755 23.7 The mobile terminated short message transfer procedure for VGCS..............................................................758 23.7.1 Procedure in the SMS-GMSC.......................................................................................................................759 23.7.2 Procedure in the Anchor MSC......................................................................................................................759 24.1 Procedure for retrieval of routeing information for GPRS..............................................................................764 24.1.1 Process in the GGSN ....................................................................................................................................764 24.1.2 Process in the HLR .......................................................................................................................................764 24.2 Procedure for reporting failure to establish a network requested PDP context...............................................767 24.2.1 Process in the GGSN.....................................................................................................................................767 24.2.2 Process in the HLR........................................................................................................................................767 24.3 Procedure for reporting that an MS has become reachable for GPRS.............................................................770 24.3.1 Process in the HLR........................................................................................................................................770 24.3.2 Process in the GGSN for Note Ms Present For Gprs....................................................................................770

1222 23 Short message service procedures....................................................................................................678

1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1255 1256 1257 1258 1259 1260 1261 1262 1263

1254 24 GPRS process description................................................................................................................763

90

3GPP

1264 24A CSE interrogation and control of subscriber data..........................................................................773

1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 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 7 92 93

24

3GPP TS 29.002 V7.5.0 (2006-09)

24A.1 General..........................................................................................................................................................773 24A.2 Any Time Subscription Interrogation procedure..........................................................................................775 24A.2.1 General.......................................................................................................................................................775 24A.2.2 Process in the gsmSCF...............................................................................................................................775 24A.2.3 Process in the HLR.....................................................................................................................................775 24A.3 Any Time Modification procedure................................................................................................................778 24A.3.1 General.......................................................................................................................................................778 24A.3.2 Process in the gsmSCF...............................................................................................................................778 24A.3.3 Process in the HLR.....................................................................................................................................778 24A.4 Subscriber Data Modification Notification procedure..................................................................................781 24A.4.1 General.......................................................................................................................................................781 24A.4.2 Process in the HLR.....................................................................................................................................781 24A.4.3 Process in the gsmSCF...............................................................................................................................781 24A.5 Any Time Interrogation procedure................................................................................................................786 24A.5.1 General.......................................................................................................................................................786 24A.5.2 Procedures in the gsmSCF.........................................................................................................................787 24A.5.3 Procedure in the HLR.................................................................................................................................787 24A.5.4 Procedure in the GMLC.............................................................................................................................787 24B.1 Routeing information retrieval procedure for LCS.......................................................................................793 24B.1.1 General.......................................................................................................................................................793 24B.1.2 Process in the GMLC.................................................................................................................................793 24B.1.3 Process in the HLR.....................................................................................................................................793 24B.2 Provide Subscriber Location procedure........................................................................................................796 24B.2.1 General.......................................................................................................................................................796 24B.2.2 Process in the GMLC.................................................................................................................................796 24B.2.3 Process in the MSC....................................................................................................................................796 24B.2.4 Process in the SGSN...................................................................................................................................796 24B.3 Subscriber Location Report procedure..........................................................................................................800 24B.3.1 General.......................................................................................................................................................800 24B.3.2 Process in the MSC....................................................................................................................................800 24B.3.3 Process in the SGSN...................................................................................................................................800 24B.3.4 Process in the GMLC.................................................................................................................................800 25.1 MAP_OPEN handling macros.........................................................................................................................804 25.1.1 Macro Receive_Open_Ind............................................................................................................................804 25.1.2 Macro Receive_Open_Cnf............................................................................................................................804 25.2 Macros to check the content of indication and confirmation primitives..........................................................809 25.2.1 Macro Check_Indication...............................................................................................................................809 25.2.2 Macro Check_Confirmation..........................................................................................................................809 25.3 The page and search macros............................................................................................................................812 25.3.1 Macro PAGE_MSC......................................................................................................................................812 25.3.2 Macro Search_For_MS_MSC.......................................................................................................................812 25.4 Macros for handling an Access Request..........................................................................................................815 25.4.1 Macro Process_Access_Request_MSC........................................................................................................815 25.4.2 Macro Process_Access_Request_VLR.........................................................................................................815 25.4.3 Macro Obtain_Identity_VLR........................................................................................................................815 25.4.4 Process Update_Location_Child_VLR.........................................................................................................815 25.5 Authentication macros and processes..............................................................................................................825 25.5.1 Macro Authenticate_MSC............................................................................................................................825 25.5.2 Macro Authenticate_VLR.............................................................................................................................825 25.5.3 Macro Obtain_Authent_Params_VLR..........................................................................................................825 25.5.4 Process Obtain_Authentication_Sets_VLR..................................................................................................825 25.5.6 Process Obtain_Authent_Sets_SGSN...........................................................................................................825 25.5.6 Process Obtain_Authent_Sets_HLR.............................................................................................................825 25.5.7 Authentication Failure Reporting..................................................................................................................826 25.5.7.1 General 826 25.5.7.2 Process in the VLR.....................................................................................................................................826 25.5.7.3 Process in the SGSN..................................................................................................................................826

1283 24B Location Services process description...........................................................................................793

1298 25 General macro description................................................................................................................804

94

3GPP

1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355

95 Release 7 96 97

25

3GPP TS 29.002 V7.5.0 (2006-09)

25.5.7.4 Process in the HLR.....................................................................................................................................826 25.6 IMEI Handling Macros....................................................................................................................................842 25.6.1 Macro Check_IMEI_MSC............................................................................................................................842 25.6.2 Macro Check_IMEI_VLR............................................................................................................................842 25.6.3 Process Check_IMEI_SGSN........................................................................................................................842 25.6.4 Process Check_IMEI_EIR............................................................................................................................842 25.6.5 Macro Obtain_IMEI_MSC...........................................................................................................................842 25.6.6 Macro Obtain_IMEI_VLR............................................................................................................................842 25.7 Insert Subscriber Data macros and processes..................................................................................................851 25.7.1 Macro Insert_Subs_Data_VLR.....................................................................................................................851 25.7.2 Macro Insert_Subs_Data_SGSN...................................................................................................................851 25.7.3 Process Insert_Subs_Data_Stand_Alone_HLR............................................................................................851 25.7.4 Process Insert_GPRS_Subs_Data_Stand_Alone_HLR................................................................................851 25.7.5 Macro Wait_for_Insert_Subs_Data_Cnf......................................................................................................852 25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf..........................................................................................852 25.7.7 Process Send_Insert_Subs_Data_HLR.........................................................................................................852 25.8 Request IMSI Macros......................................................................................................................................862 25.8.1 Macro Obtain_IMSI_MSC............................................................................................................................862 25.8.2 Macro Obtain_IMSI_VLR............................................................................................................................862 25.9 Tracing macros.................................................................................................................................................865 25.9.1 Macro Trace_Subscriber_Activity_MSC......................................................................................................865 25.9.2 Macro Trace_Subscriber_Activity_VLR......................................................................................................865 25.9.3 Macro Trace_Subscriber_Activity_SGSN....................................................................................................865 25.9.4 Macro Activate_Tracing_VLR.....................................................................................................................865 25.9.5 Macro Activate_Tracing_SGSN...................................................................................................................865 25.9.6 Macro Control_Tracing_With_VLR_HLR...................................................................................................865 25.9.7 Macro Control_Tracing_With_SGSN_HLR................................................................................................865 25.10 Short Message Alert procedures....................................................................................................................873 25.10.1 Process Subscriber_Present_VLR ..............................................................................................................873 25.10.2 Process SubscriberPresent_SGSN..............................................................................................................873 25.10.3 Macro Alert_Service_Centre_HLR............................................................................................................873 25.10.4 Process Alert_SC_HLR..............................................................................................................................873

1356 Annex A (informative): 1357

ASN.1 Cross-reference listing and fully expanded sources..............877

1358 Annex B (informative): Void..............................................................................................................878 1359 Annex C (informative): 1360

1361 1362 1363 1364 1365 1366 1367 1368 1369

Message Segmentation Mechanisms..................................................879

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

1370 Annex D (informative): Void..............................................................................................................883 1371 Annex E (informative): 1372 1373

Change History....................................................................................884

98

3GPP

99 Release 7 100 101

26

3GPP TS 29.002 V7.5.0 (2006-09)

1374

Foreword

1375 This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). 1376 The present document specifies the Mobile Application Part (MAP), the requirements for the signalling system and 1377 procedures within the 3GPP system at application level. 1378 The contents of the present document are subject to continuing work within the TSG and may change following formal 1379 TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an 1380 identifying change of release date and an increase in version number as follows: 1381 1382 1383 1384 1385 1386 1387 1388 1389

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

27

3GPP TS 29.002 V7.5.0 (2006-09)

1405

1 Scope

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

1414
1415

Figure 1.1/1: Modelling principles

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

1420

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

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

1423
1424

1425 1426
1427 1428 1429 1430 1431 1432 1433 1434 1435 1436

106

3GPP

1437 1438 1439

107 Release 7 108 109

28

3GPP TS 29.002 V7.5.0 (2006-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.204: "3G Security; Network domain security; TCAP user 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]

1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471

110

3GPP

1472 1473

111 Release 7 112 113

29

3GPP TS 29.002 V7.5.0 (2006-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".

1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511

[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

1512 1513

115 Release 7 116 117

30

3GPP TS 29.002 V7.5.0 (2006-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".

1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554

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

118

3GPP

1555 1556 1557 1558

119 Release 7 120 121

31

3GPP TS 29.002 V7.5.0 (2006-09)

[82] [83] [84]

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

1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596

[85] [86] [87] [88] [89] [90] [91] [92] [93] [93b] [94]

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

122

3GPP

1597 1598

123 Release 7 124 125

32

3GPP TS 29.002 V7.5.0 (2006-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] [133]

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". 3GPP TS 23.236: " Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes"

1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635

126

3GPP

127 Release 7 128 129

33

3GPP TS 29.002 V7.5.0 (2006-09)

1636

3 Abbreviations

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

1639 1640 1641

4 Void 5 Overload and compatibility overview

5.1 Overload control

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

1644

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.

1645 For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load: 1646 1647 1648 1649 1650

1651

5.1.2 Overload control for MAP entities

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

130

3GPP

1663

131 Release 7 132 133

34

3GPP TS 29.002 V7.5.0 (2006-09)

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

Responder = HLR Initiating Entity VLR

1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694

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

1695 1696 1697

1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721

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

1722 1723

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

1724
1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1753 1754 1755 1756 1757

135 Release 7 136 137

35

3GPP TS 29.002 V7.5.0 (2006-09)

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

Initiating Entity HLR HLR HLR HLR

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

1758 1759

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

1760

139 Release 7 140 141

36

3GPP TS 29.002 V7.5.0 (2006-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) groupCallInfoRetrieval (sendGroupCallInfo/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 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

142

3GPP

1762 1763

143 Release 7 144 145

37

3GPP TS 29.002 V7.5.0 (2006-09)

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.

1764

5.1.3 Congestion control for Signalling System No. 7

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

1767 1768

5.2 Compatibility
5.2.1 General

1769 The present document of the Mobile Application Part is designed in such a way that an implementation which conforms 1770 to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR 1771 interface. 1772 A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol 1773 version used between two entities for supporting a MAP-user signalling procedure. 1774 1775 1776 1777

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.

1778 A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of 1779 version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP 1780 operational version 1). 1781 1782 1783 1784 1785 1786 1787 1788

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.

1789

5.2.2 Strategy for selecting the Application Context (AC) version

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

1793 5.2.2.1
1794 1795 1796 1797 1798 1799 1800

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.

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

146

3GPP

1805 1806 1807

147 Release 7 148 149

38

3GPP TS 29.002 V7.5.0 (2006-09)

a) the version shown in table 1 is "version n-1", where 'n' is the highest version existing in this specification; table 2 is not used; b) the version shown in table 1 is "unknown"; table 2 is used, and maintained as described in 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.

1808 1809 1810

1811 5.2.2.2

Managing the version look-up table

1812 WHEN it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the 1813 originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the 1814 IMSI or the MSISDN. 1815 IF the entity number is known: 1816 1817 1818 1819

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.

1820 WHEN starting a procedure, the originating MAP-user looks up its version control table. 1821 IF the destination address is known and not timed-out. 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841

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

150

3GPP

1842 1843

151 Release 7 152 153

39

3GPP TS 29.002 V7.5.0 (2006-09)

It adds the destination node in its version control table and includes the new AC-Name in the list of associated highest AC supported. ELSE It replaces the old AC-name by the new one in the list of highest supported AC and reset the timer.

1844 1845

1846 5.2.2.3

Optimising the method

1847 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 1848 each subscriber the version of the AC-name used at location updating. Then: 1849 1850 1851 1852 1853 1854 1855 1856 1857

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.

1858 1859

6 Requirements concerning the use of SCCP and TC

6.1 Use of SCCP

1860 The Mobile Application Part (MAP) makes use of the services offered by the Signalling Connection Control Part 1861 (SCCP). 1862 MAP supports the following SCCP versions:

1863 1864
1865 1866 1867 1868 1869 1870 1871

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.

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

1877

6.1.1 SCCP Class

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

1879

6.1.2 Sub-System Number (SSN)

3GPP

154

1880 The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are 1881 addressed by sub-system numbers (SSNs). The SSNs for MAP are specified in 3GPP TS 23.003 [17]. 1882 When the SGSN emulates MSC behaviour for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, 1883 MAP_CHECK_IMEI, MAP_SUBSCRIBER_LOCATION_REPORT) towards entities which do not support 1884 interworking to SGSNs, it shall use the MSC SSN in the calling party address instead of the SGSN SSN. 1885 When present in the network, the Presence Network Agent emulates the behaviour of the GSM Service Control 1886 Function (gsm SCF) for processing of messages (MAP-NOTE-MM-EVENT, MAP-ANY-TIME-INTERROGATION 1887 and MAP-ANY-TIME-MODIFICATION). 1888 When a FFN (Follow Me Functional Node, see TS 23.094 [129]) is implemented in a network entity different from 1889 HLR, this network entity shall emulate HLR behaviour, i.e. it shall accept MAP-PROCESS-UNSTRUCTURED-SS1890 REQUEST messages addressed with SSN for HLR.

155 Release 7 156 157

40

3GPP TS 29.002 V7.5.0 (2006-09)

1891 1892 6.1.3.1

6.1.3 SCCP addressing

Introduction

1893 Within the GSM System there will be a need to communicate between entities within the same PLMN and in different 1894 PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) 1895 and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. 1896 Only the entities that should be addressed are described below. If the CCITT or ITU-T SCCP is used, the format and 1897 coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 1898 with the following restrictions: 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920

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

158

3GPP

1921 If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall 1922 comply with ANSI specification T1.112 with the following restrictions: 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944

159 Release 7 160 161

41

3GPP TS 29.002 V7.5.0 (2006-09)

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

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

1945 If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and 1946 E.214 is applicable. 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962

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.

162

3GPP

1963 1964 1965 1966 1967

163 Release 7 164 165

42

3GPP TS 29.002 V7.5.0 (2006-09)

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.

1968 The following clauses describe the method of SCCP addressing appropriate for each entity both for the simple 1969 intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered: 1970 1971 1972 1973 1974 1975 1976 1977 1978

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

1979 6.1.3.2

The Mobile-services Switching Centre (MSC)

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

1981 6.1.3.2.1

MSC interaction during handover or relocation

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

1983 6.1.3.2.2

MSC for short message routing

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

1987 6.1.3.2.3

MSC for location request routing

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

1990 6.1.3.2.4

MSC for LMU Control

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

1993 6.1.3.3

The Home Location Register (HLR)

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

1995 6.1.3.3.1

During call set-up

1996 When a call is initiated the HLR of the called mobile subscriber will be interrogated to discover the whereabouts of the 1997 MS. The addressing required by the SCCP will be derived from the MSISDN dialled by the calling subscriber. The

166

3GPP

1998 dialled number will be translated into either an SPC, in the case of communications within a PLMN, or a Global Title if 1999 other networks are involved (i.e. if the communication is across a PLMN boundary). 2000 If the calling subscriber is a fixed network subscriber, the interrogation can be initiated from the Gateway MSC of the 2001 home PLMN in the general case. If the topology of the network allows it, the interrogation could be initiated from any 2002 Signalling Point that has MAP capabilities, e.g. local exchange, outgoing International Switching Centre (ISC), etc.

167 Release 7 168 169

43

3GPP TS 29.002 V7.5.0 (2006-09)

2003 6.1.3.3.2
2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014

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.

2015 When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of 2016 the SCCP message containing the first responding CONTINUE message. 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028

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.

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

2033 6.1.3.3.3
2034 2035 2036 2037 2038 2039

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.

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

2043 6.1.3.3.4
2044 2045 2046 2047 2048 2049 2050 2051 2052

171 Release 7 172 173

44

3GPP TS 29.002 V7.5.0 (2006-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.

2053 6.1.3.3.5
2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070

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.

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

2073 6.1.3.3.6
2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090

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

2091

175 Release 7 176 177

45

3GPP TS 29.002 V7.5.0 (2006-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.

2092 2093 2094

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

2097 6.1.3.3.7
2098 2099 2100 2101 2102

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.

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

2105 6.1.3.3.8
2106 2107 2108 2109

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.

2110 6.1.3.4

The Visitor Location Register (VLR)

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

2112 6.1.3.4.1

Inter-VLR information retrieval

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

2116 6.1.3.4.2

HLR request

2117 The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR service area. 2118 This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has 2119 indicated successful completion of the update location procedure to the VLR. 2120 2121 2122 2123 2124

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.

2125 6.1.3.5

The Interworking MSC (IWMSC) for Short Message Service

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

2128 6.1.3.6

The Equipment Identity Register (EIR)

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

178

3GPP

2130 6.1.3.7 2131 6.1.3.8

2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144

179 Release 7 180 181

46

3GPP TS 29.002 V7.5.0 (2006-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.

2145 6.1.3.9
2146 2147 2148 2149

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.

2150 6.1.3.10

The Gateway MSC (GMSC) for Short Message Service

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

2153 6.1.3.10A 2154 6.1.3.10A.1 2155 6.1.3.10A.2 2156 6.1.3.10B

2157 2158 2159 2160

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.

2161 6.1.3.11

Summary table

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

182

3GPP

2168

183 Release 7 184 185

47

3GPP TS 29.002 V7.5.0 (2006-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

2169 2170
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 7 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 V7.5.0 (2006-09)

2171

2172

6.2 Use of TC

2173 The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of Signalling 2174 System No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be 2175 consulted for the full specification of TC. 2176 The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility. 2177 From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is 2178 for further study. 2179 Transaction Capabilities refers to a protocol structure above the network layer interface (i.e., the SCCP service 2180 interface) up to the application layer including common application service elements but not the specific application 2181 service elements using them. 2182 TC is structured as a Component sub-layer above a Transaction sub-layer. 2183 The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues 2184 and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives 2185 and TC-Component handling primitives respectively. 2186 Services for dialogue control include the ability to exchange information related to application-context negotiation as 2187 well as initialisation data. 2188 2189 2190 2191 2192 2193 2194

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

2195 2196

7 General on MAP services

7.1 Terminology and definitions

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

2199

7.2 Modelling principles

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

190

3GPP

191 Release 7 192 193

49

3GPP TS 29.002 V7.5.0 (2006-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

2202
2203

Figure 7.2/1: Modelling principles

2204 The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the 2205 service interface. 2206 A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such 2207 cases the overall procedure is synchronised by the service-user. 2208 The MAP service-primitives are named using the following notation: 2209

MAP-ServicePrimitiveName type

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

2219

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.

2220 All MAP service-users require access to services for performing basic application layer functions: 2221 2222 2223 2224 2225

2226 For these purposes the following common services are defined: 2227 2228 2229 2230 2231 2232

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

2233 In defining the service-primitives the following convention is used for categorising parameters:

194

3GPP

2234 2235 2236 2237 2238 2239

195 Release 7 196 197

50

3GPP TS 29.002 V7.5.0 (2006-09)

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:

2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252

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.

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

2255

7.3.1 MAP-OPEN service

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

2259 2260 Application context name: 2261 This parameter identifies the type of application context being established. If the dialogue is accepted the received 2262 application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version 2263 supported. 2264 Destination address: 2265 A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this 2266 parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is 2267 issued. 2268 Destination-reference:

198

3GPP

2269 This parameter is a reference that refines the identification of the called process. It may be identical to Destination 2270 address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only 2271 these services are allowed to use it. 2272

199 Release 7 200 201

51

3GPP TS 29.002 V7.5.0 (2006-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

2273 2274 2275 2276 2277 2279 2280

2278

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.

2281 Originating address: 2282 A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, 2283 this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is 2284 issued. 2285 Originating-reference: 2286 2287 2288 2289 2290

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

202

3GPP

2291

203 Release 7 204 205

52

3GPP TS 29.002 V7.5.0 (2006-09)

Table 7.3/3: Use of the originating reference Reference type ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String (note) ISDN-Address-String (note) ISDN-Address-String ISDN-Address-String Use of the parameter Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address

MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-NOTIFY MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY
2292 2293

NOTE:

The Originating reference may be omitted.

2294 Specific information: 2295 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2296 information is not specified by GSM and shall be performed according to operator specific requirements. 2297 Responding address: 2298 An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is 2299 different from the destination address). 2300 Result: 2301 This parameter indicates whether the peer accepts the dialogue. 2302 Refuse reason: 2303 This parameter is present only if the Result parameter indicates that the dialogue is refused. It takes one of the following 2304 values:

2305 2306 2307 2308 2309 2310

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

206

3GPP

2311

207 Release 7 208 209

53

3GPP TS 29.002 V7.5.0 (2006-09)

7.3.2 MAP-CLOSE service

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

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

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

2316 2317 Release method: 2318 This parameter can take the following two values: 2319 2320 2321

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.

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

2325

7.3.3 MAP-DELIMITER service

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

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

Parameters Request Indication

2330

2331

7.3.4 MAP-U-ABORT service

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

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

2335 2336 User reason: 2337 This parameter can take the following values: 2338 2339 2340

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

resource unavailable;

210

3GPP

2341 2342 2343

211 Release 7 212 213

54

3GPP TS 29.002 V7.5.0 (2006-09)

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;

2344 2345

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

2346 Diagnostic information: 2347 This parameter may be used to give additional information for some of the values of the user-reason parameter: 2348

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

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

2353

7.3.5 MAP-P-ABORT service

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

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

Parameters Provider reason Source Indication M M

2357 2358 Provider reason: 2359 This parameter indicates the reason for aborting the MAP dialogue: 2360 2361 2362 2363 2364 2365

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

2366 Source: 2367 This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take 2368 the following values:

214

3GPP

2369

215 Release 7 216 217

55

3GPP TS 29.002 V7.5.0 (2006-09)

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

2370 2371 2372 2373

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

2374

2375

7.3.6 MAP-NOTICE service

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

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

Parameters Problem diagnostic Indication M

2380 2381 Problem diagnostic: 2382 This parameter can take one of the following values: 2383 2384 2385 2386

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

2387 2388 2389

219 Release 7 220 221

56

3GPP TS 29.002 V7.5.0 (2006-09)

7.3.7 Void 7.3.8 Void 7.3.9 Void 7.3.10 Void

2390 2391

7.4 Sequencing of services

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

2392 The sequencing of services is shown in figure 7.4/1 and is as follows: 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413

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

2417
2418

a) Opening

222

3GPP

223 Release 7 224 225

57

3GPP TS 29.002 V7.5.0 (2006-09)

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

2419
2420

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

2421
2422

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

2423
2424 2425

d) Aborting Figure 7.4/1: Sequencing of services

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

2431 2432

7.5 General rules for mapping of services onto TC

7.5.1 Mapping of common services

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

Table 7.5/1: Mapping of common services onto TC services MAP service-primitive MAP-OPEN request (+ any user specific service primitives) + MAP-DELIMITER request MAP-OPEN response (+ any user specific service primitives) + MAP-DELIMITER request (any user specific service primitives) + MAP-DELIMITER request (any user specific service primitives) + MAP-CLOSE request TC service-primitive TC-BEGIN request (+ component handling primitives) TC-CONTINUE request (note) (+ component handling primitives) TC-CONTINUE request (+ component handling primitives) TC-END request (+ component handling primitives)

226

3GPP

227 Release 7 228 229

58

3GPP TS 29.002 V7.5.0 (2006-09)

MAP-U-ABORT request
NOTE:

TC-U-ABORT request

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

2437 2438

Table 7.5/2: Mapping of TC services onto common service TC service-primitive TC-BEGIN indication (+ component handling primitives) TC-CONTINUE indication (+ component handling primitives) MAP service-primitive MAP-OPEN indication (+ user specific service primitives) + MAP-DELIMITER indication (note 1) First time: MAP-OPEN confirm (+ user specific service primitives) + MAP-DELIMITER indication (note 1) Subsequent times: (user specific service primitives) + MAP-DELIMITER indication (note 1) MAP-OPEN confirm (note 6) (user specific service primitives) + MAP-CLOSE indication MAP-U-ABORT indication or MAP-P-ABORT indication (note 2) MAP-OPEN confirmation (note 3) MAP-P-ABORT indication (note 4) MAP-OPEN confirmation (note 5)

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

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

2439

2440

7.5.2 Mapping of user specific services

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

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)

2445 2446

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

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

230

3GPP

231 Release 7 232 233

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

3GPP TS 29.002 V7.5.0 (2006-09)

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

2447 2448 2449 2450 2451 2452 2453

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.

2454 2455

7.6 Definition of parameters

7.6.1 Common parameters

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

2457 7.6.1.1

Invoke Id

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

2460 7.6.1.2

Linked Id

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

2462 7.6.1.3
-

Provider error

2463 This parameter is used to indicate a protocol related type of error: 2464 2465 2466 2467 2468 2469 2470 2471 2472

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.

2473 7.6.1.4
NOTE:

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

2474 This parameter can take values as follows: 2475 2476

a) Generic error:

234

3GPP

2477 2478 2479

235 Release 7 236 237

60

3GPP TS 29.002 V7.5.0 (2006-09)

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;

2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505

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

2506
2507

2508 2509
2510 2511 2512

f) Call set-up problem:

238

3GPP

2513 2514

239 Release 7 240 241

61

3GPP TS 29.002 V7.5.0 (2006-09)

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.

2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543

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

2544 For definition of these errors see 3GPP TS 24.080 [38]. 2545 2546 2547 2548

h) Short message problem: SM delivery failure with detailed reason as follows: memory capacity exceeded; MS protocol error;

242

3GPP

2549

243 Release 7 244 245

62

3GPP TS 29.002 V7.5.0 (2006-09)

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.

2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567

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;

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.

2568

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

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

-Position method failure with detailed reasons as follows: Congestion Insufficient resources Insufficient Measurement Data Inconsistent Measurement Data

246

3GPP

2584 2585 2586 2587

2588

247 Release 7 248 249

63

3GPP TS 29.002 V7.5.0 (2006-09)

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.

2589 7.6.1.5

All Information Sent

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

2591 2592 7.6.2.1

7.6.2 Numbering and identification parameters

IMSI

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

2594 7.6.2.2

TMSI

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

2596 7.6.2.3

IMEI

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

2598 7.6.2.3a

IMEISV

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

2601 7.6.2.4

Previous location area Id

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

2603 7.6.2.5

Stored location area Id

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

2605 7.6.2.6

Current location area Id

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

2607 7.6.2.7

Target location area Id

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

2609 7.6.2.8

Target cell Id

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

2611 7.6.2.8A

Target RNC Id

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

250

3GPP

2613 7.6.2.9

251 Release 7 252 253

64

3GPP TS 29.002 V7.5.0 (2006-09)

Void Originating entity number

2614 7.6.2.10

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

2617 7.6.2.11

MSC number

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

2619 7.6.2.12

Target MSC number

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

2621 7.6.2.13

HLR number

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

2623 7.6.2.14

VLR number

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

2625 7.6.2.15

HLR Id

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

2627 7.6.2.16

LMSI

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

2630 7.6.2.17

MS ISDN

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

2633 7.6.2.18

OMC Id

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

2635 7.6.2.19

Roaming number

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

2637 7.6.2.19A

Relocation Number List

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

2639 7.6.2.20 2640 7.6.2.21

Void Handover number

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

2642 7.6.2.22

Forwarded-to number

254

3GPP

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

255 Release 7 256 257

65

3GPP TS 29.002 V7.5.0 (2006-09)

2645 7.6.2.22A

Long forwarded-to number

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

2648 7.6.2.22B

Long FTN Supported

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

2650 7.6.2.23

Forwarded-to subaddress

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

2652 7.6.2.24

Called number

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

2654 7.6.2.25

Calling number

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

2656 7.6.2.26

Originally dialled number

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

2658 7.6.2.27

Service centre address

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

2660 7.6.2.28

Zone Code

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

2664 7.6.2.29

MSIsdn-Alert

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

2667 7.6.2.30

Location Information

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

2669 7.6.2.30a

Location Information for GPRS

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

2671 7.6.2.31

GMSC Address

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

2673 7.6.2.32

VMSC Address

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

258

3GPP

2675 7.6.2.33

259 Release 7 260 261

66

3GPP TS 29.002 V7.5.0 (2006-09)

Group Id

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

2678 7.6.2.34

North American Equal Access preferred Carrier Id

2679 This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an inter-exchange 2680 carrier. This identity is used at: 2681 2682 2683

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.

2684 7.6.2.35 2685 7.6.2.36 2686 7.6.2.37

Void Void Serving cell Id

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

2688 7.6.2.38

SGSN number

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

2690 7.6.2.39

SGSN address

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

2692 7.6.2.40

GGSN address

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

2694 7.6.2.41

GGSN number

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

2697 7.6.2.42

APN

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

2699 7.6.2.43

Network Node number

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

2701 7.6.2.44

PDP-Type

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

2703 7.6.2.45

PDP-Address

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

262

3GPP

2705 7.6.2.46

263 Release 7 264 265

67

3GPP TS 29.002 V7.5.0 (2006-09)

Additional number

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

2707 7.6.2.47

P-TMSI

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

2709 7.6.2.48

B-subscriber number

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

2711 7.6.2.49

B-subscriber subaddress

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

2713 7.6.2.50

LMU Number

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

2715 7.6.2.51

MLC Number

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

2717 7.6.2.52

Multicall Bearer Information

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

2719 7.6.2.53

Multiple Bearer Requested

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

2721 7.6.2.54

Multiple Bearer Not Supported

2722 This parameter indicates whether multiple bearers are supported.

2723 7.6.2.55

PDP-Charging Characteristics

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

2726 7.6.2.56

Selected RAB ID

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

2728 7.6.2.57

RAB ID

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

2731 7.6.2.58

gsmSCF Address

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

2734 7.6.2.59

V-GMLC Address

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

266

3GPP

2736 7.6.2.60 2737 7.6.2.61

267 Release 7 268 269

68

3GPP TS 29.002 V7.5.0 (2006-09)

Void H-GMLC Address

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

2739 7.6.2.62

PPR Address

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

2741 7.6.2.63

Routeing Number

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

2744 7.6.2.64

Additional V-GMLC Address

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

2746 2747 7.6.3.1

7.6.3 Subscriber management parameters

Category

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

2749 7.6.3.2

Equipment status

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

2751 7.6.3.2a

BMUEF

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

2754 7.6.3.3

Extensible Bearer service

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

2758 7.6.3.4

Extensible Teleservice

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

2762 7.6.3.5
2763 2764 2765 2766

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.

2767 7.6.3.6

GSM bearer capability

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

270

3GPP

2769 7.6.3.7
-

271 Release 7 272 273

69

3GPP TS 29.002 V7.5.0 (2006-09)

Subscriber Status

2770 This parameter refers to the barring status of the subscriber: 2771 2772

service granted; Operator Determined Barring.

2773 7.6.3.8

CUG Outgoing Access indicator

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

2775 7.6.3.9

Operator Determined Barring General Data

2776 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate. 2777 This set only includes those limitations that can be 2778 2779 2780 2781 2782

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

ODB category

Controlled in the VLR Controlled in the SGSN

Controlled in the Interrogatable and SGSN applied for modifyable by the short message transfer gsmSCF only 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

X X X

X X

X X

X X

274

3GPP

275 Release 7 276 277

70

3GPP TS 29.002 V7.5.0 (2006-09)

Supplementary service access barred Invocation of call transfer barred Invocation of chargeable call transfer barred Invocation of internationally chargeable call transfer barred Invocation of interzonally chargeable call transfer barred Invocation of call transfer where both legs are chargeable barred Invocation of call transfer if there is already an ongoing transferred call for the served subscriber in the serving MSC/VLR barred 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

X X X

X X X

X X X

X X X X

X X

X X X

278

3GPP

279 Release 7 280 281

71

3GPP TS 29.002 V7.5.0 (2006-09)

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

2783 2784

2785 7.6.3.10

ODB HPLMN Specific Data

2786 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate only 2787 when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in the 2788 VLR or in the SGSN: 2789 2790 2791 2792

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

2793 7.6.3.11

Regional Subscription Data

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

2796 7.6.3.12

Regional Subscription Response

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

2799 7.6.3.13

Roaming Restriction Due To Unsupported Feature

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

2802 7.6.3.14
-

Extensible SS-Info

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

extensible forwarding information (see clause 7.6.3.15); extensible call barring information (see clause 7.6.3.20);

282

3GPP

2806 2807

283 Release 7 284 285

72

3GPP TS 29.002 V7.5.0 (2006-09)

CUG info extensible SS-Data

(see clause 7.6.3.22); (see clause 7.6.3.29).

2808 7.6.3.15
-

Extensible forwarding information

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

2809 This parameter represents the information related to each call forwarding service: 2810 2811 2812

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.

2813 7.6.3.16

Extensible forwarding feature

2814 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 2815 following information, as required: 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827

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

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

2828 7.6.3.17

Extensible SS-Status

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

2830 7.6.3.18

Extensible Forwarding Options

2831 This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following 2832 information: 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842

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

286

3GPP

2843 7.6.3.19

287 Release 7 288 289

73

3GPP TS 29.002 V7.5.0 (2006-09)

Extensible No reply condition timer

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

2845 7.6.3.20
SS-Code

Extensible Call barring information

2846 This parameter contains for each call barring service: 2847 2848 2849

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

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

2850 7.6.3.21

Extensible Call barring feature

2851 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 2852 contains the following information: 2853 2854

Extensible Basic Service Group provisioned SS-Status

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

2855 7.6.3.22
-

CUG info

2856 This parameter refers to the overall information required for operation for each CUG: 2857 2858

CUG subscriptionList; CUG featureList.

2859 7.6.3.23

CUG subscription

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

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

2866 7.6.3.24

CUG interlock

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

2868 7.6.3.25

CUG index

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

2870 7.6.3.26

CUG feature

2871 This parameter contains two parameters that are associated with the Basic Service Group. If the Basic Service Group 2872 Code is not present the feature applies to all Basic Services. The following parameters are included: 2873 2874 2875

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:

290

3GPP

2876 2877 2878

291 Release 7 292 293

74

3GPP TS 29.002 V7.5.0 (2006-09)

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.

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

2880 7.6.3.27

Inter CUG options

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

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

2887 7.6.3.28

Intra CUG restrictions

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

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

2893 7.6.3.29
SS-Code

Extensible SS-Data

2894 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 2895 2896 2897 2898 2899

(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

2900 7.6.3.30

Subscriber State

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

2902 7.6.3.31

Requested Info

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

2905 7.6.3.31A

Requested Domain

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

2908 7.6.3.32

Suppression of Announcement

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

294

3GPP

2910 7.6.3.33

295 Release 7 296 297

75

3GPP TS 29.002 V7.5.0 (2006-09)

Suppress T-CSI

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

2912 7.6.3.34

GMSC CAMEL Subscription Info

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

2915 7.6.3.35

VLR CAMEL Subscription Info

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

2917 7.6.3.36

Supported CAMEL Phases in the VLR

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

2919 7.6.3.36A

Supported CAMEL Phases in the SGSN

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

2921 7.6.3.36B

Offered CAMEL4 CSIs in the VLR

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

2923 7.6.3.36C

Offered CAMEL4 CSIs in the SGSN

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

2925 7.6.3.36D

Offered CAMEL4 CSIs

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

2927 7.6.3.36E

Offered CAMEL4 CSIs in interrogating node

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

2930 7.6.3.36F

Offered CAMEL4 CSIs in VMSC

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

2932 7.6.3.36G 2933 7.6.3.36H

Offered CAMEL4 Functionalities Supported CAMEL Phases

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

2935 7.6.3.36I

Supported CAMEL Phases in interrogating node

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

2939 7.6.3.37

CUG Subscription Flag

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

298

3GPP

2941 7.6.3.38

299 Release 7 300 301

76

3GPP TS 29.002 V7.5.0 (2006-09)

CAMEL Subscription Info Withdraw

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

2943 7.6.3.39

Voice Group Call Service (VGCS) Data

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

2945 7.6.3.40

Voice Broadcast Service (VBS) Data

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

2949 7.6.3.41

ISDN bearer capability

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

2951 7.6.3.42

Lower layer Compatibility

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

2953 7.6.3.43

High Layer Compatibility

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

2955 7.6.3.44

Alerting Pattern

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

2958 7.6.3.45

GPRS Subscription Data Withdraw

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

2960 7.6.3.46

GPRS Subscription Data

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

2962 7.6.3.47

QoS-Subscribed

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

2964 7.6.3.48

VPLMN address allowed

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

2967 7.6.3.49

Roaming Restricted In SGSN Due To Unsupported Feature

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

2970 7.6.3.50

Network Access Mode

2971 This parameter is defined in 3GPP TS 23.108.

302

3GPP

2972 7.6.3.51

303 Release 7 304 305

77

3GPP TS 29.002 V7.5.0 (2006-09)

Mobile Not Reachable Reason

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

2975 7.6.3.52

Cancellation Type

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

2977 7.6.3.53

All GPRS Data

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

2979 7.6.3.54

Complete Data List Included

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

2982 7.6.3.55

PDP Context Identifier

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

2984 7.6.3.56

LSA Information

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

2988 7.6.3.57

SoLSA support indicator

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

2990 7.6.3.58

LSA Information Withdraw

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

2992 7.6.3.59

LMU Indicator

2993 This parameter indicates the presence of an LMU.

2994 7.6.3.60
-

LCS Information

2995 This parameter defines the LCS related information for an MS subscriber and contains the following components: 2996 2997 2998 2999 3000

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

3001 7.6.3.61

GMLC List

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

306

3GPP

3004 7.6.3.62

307 Release 7 308 309

78

3GPP TS 29.002 V7.5.0 (2006-09)

LCS Privacy Exception List

3005 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 3006 information is provided: 3007 3008

SS-Code a list of LCS privacy exception parameters

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

3009 7.6.3.62A

Additional LCS Privacy Exception List

3010 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 3011 information is provided: 3012 3013

SS-Code a list of LCS privacy exception parameters

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

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

3016 7.6.3.63

LCS Privacy Exception Parameters

3017 This parameter gives the status of each LCS privacy exception class and any additional parameters relevant to this class. 3018 The parameter contains the following information: 3019 3020 3021 3022 3023 3024

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

3025 7.6.3.64
3026 3027 3028 3029 3030 3031

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.

3032 7.6.3.65

Internal Client List

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

3036 7.6.3.65A

MO-LR List

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

SS-Code

(see clause 7.6.4.1).

310

3GPP

3040 7.6.3.65B
3041 3042 3043 3044

311 Release 7 312 313

79

3GPP TS 29.002 V7.5.0 (2006-09)

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.

3045 7.6.3.65C

GMLC List Withdraw

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

3047 7.6.3.65D

Service Type List

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

3050 7.6.3.66

IST Alert Timer

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

3053 7.6.3.67

Call Termination Indicator

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

3056 7.6.3.68

IST Information Withdraw

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

3058 7.6.3.69

IST Support Indicator

3059 This parameter indicates the degree of IST functionality supported by the MSC (Visited MSC or Gateway MSC). It can 3060 take one of the following values: 3061 3062 3063

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

3064 7.6.3.70

Super-Charger Supported In HLR

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

3067 7.6.3.71

Super-Charger Supported In Serving Network Entity

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

3070 7.6.3.72

Age Indicator

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

3073 7.6.3.73

GPRS enhancements support indicator

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

314

3GPP

3075 7.6.3.74

315 Release 7 316 317

80

3GPP TS 29.002 V7.5.0 (2006-09)

Extension QoS-Subscribed

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

3078 7.6.3.75

SGSN CAMEL Subscription Info

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

3080 7.6.3.75A

Extension-2 QoS-Subscribed

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

3084 7.6.3.76

MO-SMS-CSI

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

3087 7.6.3.76a

MT-SMS-CSI

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

3090 7.6.3.77

GPRS-CSI

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

3092 7.6.3.78

CAMEL subscription info

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

3094 7.6.3.79
SS-Code;

Extensible Call barring information for CSE

3095 This parameter contains for each call barring service for CSE: 3096 3097 3098 3099 3100 3101

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.

3102 7.6.3.80
-

Extensible Forwarding information for CSE

3103 This parameter represents the information for CSE related to each call forwarding service: 3104 3105 3106 3107

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.

318

3GPP

3108 7.6.3.81

319 Release 7 320 321

81

3GPP TS 29.002 V7.5.0 (2006-09)

Modification Request for CSI

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

3110 7.6.3.81a

Modification Request for ODB data

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

3112 7.6.3.82

Modification Request for SS Information

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

3114 7.6.3.83

Call Barring Data

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

3116 7.6.3.84

Call Forwarding Data

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

3118 7.6.3.85

ODB Data

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

3120 7.6.3.86

Requested Subscription Info

3121 This parameter indicates the subscription information being requested.

3122 7.6.3.87

CS Allocation/Retention priority

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

3125 7.6.3.88

ODB Info

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

3127 7.6.3.89

Suppress VT-CSI

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

3129 7.6.3.90

Suppress Incoming Call Barring

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

3131 7.6.3.91

gsmSCF Initiated Call

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

3133 7.6.3.92

Call barring support indicator

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

3135 7.6.3.93

MNP Info Result

3136 This parameter refers to the Mobile Number Portability (MNP) information result (see 3GPP TS 23.078 [98] and 3GPP 3137 TS 23.066 [108]). This parameter may contain the following information:

322

3GPP

3138

323 Release 7 324 325

82

3GPP TS 29.002 V7.5.0 (2006-09)

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

3139 3140 3141

3142 7.6.3.94

Allowed Services

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

3145 7.6.3.95
3146 3147 3148

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

3149 7.6.3.96

MNP Requested Info

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

3152 7.6.3.97

Access Restriction Data

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

3155 7.6.3.98

Supported RAT types indicator

3156 This parameter indicates which RAT types are supported/served by the MSC/VLR or SGSN

3157 3158 7.6.4.1

7.6.4 Supplementary services parameters

SS-Code

3159 This parameter may refer to one supplementary service or a set of supplementary services as defined in 3GPP TS 3160 22.004. For MAP this includes: 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171

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;

326

3GPP

3172 3173

327 Release 7 328 329

83

3GPP TS 29.002 V7.5.0 (2006-09)

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

3174 3175 3176 3177 3178 3179

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

3180 7.6.4.1A

SS-Code 2

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

3183 7.6.4.2

SS-Status

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

3185 7.6.4.3
SS-Code

SS-Data

3186 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 3187 3188 3189 3190 3191

(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

3192 7.6.4.4

Override Category

3193 This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the 3194 following two values: 3195 3196

Enabled; Disabled.

3197 7.6.4.5

CLI Restriction Option

3198 This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can 3199 take the following three values: 3200 3201 3202

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

3203 7.6.4.6

Forwarding Options

3204 This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following 3205 values:

330

3GPP

3206 3207 3208 3209

331 Release 7 332 333

84

3GPP TS 29.002 V7.5.0 (2006-09)

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

3210 7.6.4.7

No reply condition timer

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

3212 7.6.4.8 - 7.6.4.14 Void 3213 7.6.4.15

-

Forwarding information

3214 This parameter represents the information related to each call forwarding service: 3215 3216 3217

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

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

3218 7.6.4.16

Forwarding feature

3219 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 3220 following information, as required: 3221 3222 3223 3224 3225 3226 3227

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

3228 If a number is required to define the forwarded-to destination then: 3229 3230 3231 3232

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.

3233 7.6.4.17 3234 7.6.4.18

SS-Code

Void Call barring information

3235 This parameter contains for each call barring service: 3236 3237 3238

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

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

334

3GPP

3239 7.6.4.19

335 Release 7 336 337

85

3GPP TS 29.002 V7.5.0 (2006-09)

Call barring feature

3240 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 3241 contains the following information: 3242 3243

Basic Service Group SS-Status

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

3244 7.6.4.20

New password

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

3247 7.6.4.21

Current password

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

3249 7.6.4.22

Guidance information

3250 This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the 3251 following information may be given: 3252 3253 3254 3255 3256 3257

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

3258 7.6.4.23 3259 7.6.4.24

-

Void SS-Info

3260 This parameter refers to all the information related to a supplementary service and is a choice between: 3261 3262 3263 3264 3265

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

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

3266 7.6.4.25 - 7.6.4.35 Void 3267 7.6.4.36 USSD Data Coding Scheme

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

3271 7.6.4.37

USSD String

338

3GPP

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

339 Release 7 340 341

86

3GPP TS 29.002 V7.5.0 (2006-09)

3275 7.6.4.38

Bearer service

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

3278 7,6,4.38A

Bearer Service 2

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

3281 7.6.4.39

Teleservice

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

3284 7.6.4.39A

Teleservice 2

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

3287 7.6.4.40

Basic Service Group

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

3291 7.6.4.41

eMLPP information

3292 This parameter contains two parameters which are associated with the eMLPP service. The following two parameters 3293 are included: 3294 3295 3296 3297

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.

3298 7.6.4.42

SS-event

3299 This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It 3300 can indicate one of the following services: 3301 3302 3303 3304

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

3305 7.6.4.43

SS-event data

3306 This parameter contains additional information related to Supplementary Service invocation. Depending on the service 3307 invoked it can contain the following information:

342

3GPP

3308

343 Release 7 344 345

87

3GPP TS 29.002 V7.5.0 (2006-09)

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

3309

3310 7.6.4.44
-

LCS Privacy Exceptions

3311 Distinct SS codes are assigned to the following classes of LCS client in a target MS subscribers privacy exception list. 3312 3313 3314 3315 3316 3317

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

3318 7.6.4.45
-

Mobile Originating Location Request (MO-LR)

3319 Distinct SS codes are assigned to the following classes of MO-LR: 3320 3321 3322

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

3323 7.6.4.46

NbrUser

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

3326 7.6.4.47

MC Subscription Data

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

3329
3330 3331

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.

3332
3333

3334 7.6.4.48

MC Information

3335 This parameter contains three parameters which are associated with the MC service. The following parameters are 3336 included: 3337 3338 3339

NbrSB; NbrUser; NbrSN.

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

3341 7.6.4.49

CCBS Request State

346

3GPP

3342 This parameter indicates the current state of the CCBS request. It can take one of seven values: 3343 3344 3345 3346 3347 3348 3349

347 Release 7 348 349

88

3GPP TS 29.002 V7.5.0 (2006-09)

request; recall; active; completed; suspended; frozen; deleted.

3350 7.6.4.50

Basic Service Group 2

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

3353 3354 7.6.5.1

7.6.5 Call parameters

Call reference number

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

3356 7.6.5.2

Interrogation type

3357 This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can 3358 take either of two values: 3359 3360 3361

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.

3362 7.6.5.3

OR interrogation

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

3365 7.6.5.4

OR capability

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

3367 7.6.5.5
-

Forwarding reason

3368 This parameter indicates the reason for which the call is to be forwarded. It can take one of three values: 3369 3370 3371

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

3372 7.6.5.6

Forwarding interrogation required

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

350

3GPP

3375 7.6.5.7

351 Release 7 352 353

89

3GPP TS 29.002 V7.5.0 (2006-09)

O-CSI

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

3377 7.6.5.7A

D-CSI

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

3379 7.6.5.7B

T-CSI

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

3382 7.6.5.7C

VT-CSI

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

3385 7.6.5.7D

O-IM-CSI

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

3388 7.6.5.7E

D-IM-CSI

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

3391 7.6.5.7F

VT-IM-CSI

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

3394 7.6.5.8 3395 7.6.5.9 3396 7.6.5.10 3397 7.6.5.11

Void Void Void CCBS Feature

3398 This parameter corresponds to the 'CCBS Description' parameter in 3GPP TS 23.093. It refers to the necessary set of 3399 information required in order to characterise a certain CCBS request. The parameter may contain the following 3400 information: 3401 3402 3403 3404

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

3405 7.6.5.12

UU Data

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

3407 7.6.5.13

UUS CF Interaction

354

3GPP

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

355 Release 7 356 357

90

3GPP TS 29.002 V7.5.0 (2006-09)

3410 7.6.5.14

Number Portability Status

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

3412 7.6.5.15

Pre-paging supported

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

3414

7.6.6 Radio parameters

Void

3415 7.6.6.1 - 7.6.6.3 3416 7.6.6.4

GERAN Classmark

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

3419 7.6.6.5

BSSMAP Service Handover

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

3421 7.6.6.5A

BSSMAP Service Handover List

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

3425 7.6.6.6

RANAP Service Handover

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

3427 7.6.6.7

HO-Number Not Required

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

3429 7.6.6.8

Integrity Protection Information

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

3431 7.6.6.9

Encryption Information

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

3433 7.6.6.10

Radio Resource Information

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

3435 7.6.6.10A

Radio Resource List

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

358

3GPP

3439 7.6.6.10B

359 Release 7 360 361

91

3GPP TS 29.002 V7.5.0 (2006-09)

Chosen Radio Resource Information

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

3441 7.6.6.11

Key Status

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

3443 7.6.6.12

Selected UMTS Algorithms

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

3446 7.6.6.13

Allowed GSM Algorithms

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

3449 7.6.6.14

Allowed UMTS Algorithms

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

3452 7.6.6.15

Selected GSM Algorithm

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

3455 7.6.6.16

Iu-Currently Used Codec

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

3457 7.6.6.17

Iu-Supported Codecs List

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

3460 7.6.6.17A

Iu-Available Codecs List

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

3463 7.6.6.18

Iu-Selected Codec

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

3466 7.6.6.19

RAB Configuration Indicator

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

3469 7.6.6.20

UESBI-Iu

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

3472 7.6.6.21

Alternative Channel Type

362

3GPP

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

363 Release 7 364 365

92

3GPP TS 29.002 V7.5.0 (2006-09)

3475 3476 7.6.7.1

7.6.7 Authentication parameters

Authentication set list

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

3481 7.6.7.2

Rand

3482 This parameter represents a random number used for authentication.

3483 7.6.7.3

Sres

3484 This parameter represents the response to an authentication request.

3485 7.6.7.4

Kc

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

3487 7.6.7.5

Xres

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

3489 7.6.7.5A

Ck

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

3491 7.6.7.5B

Ik

3492 This parameter refers to the Integrity Key.

3493 7.6.7.5C

Autn

3494 This parameter refers to the Authentication Token.

3495 7.6.7.6

Cksn

3496 This parameter refers to a ciphering key sequence number.

3497 7.6.7.6A

Ksi

3498 This parameter refers to a key set identifier.

3499 7.6.7.6B

Auts

3500 This parameter refers to the resynchronisation token.

3501 7.6.7.7
-

Ciphering mode

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

no encryption;

366

3GPP

3504

367 Release 7 368 369

93

3GPP TS 29.002 V7.5.0 (2006-09)

identification of specific ciphering algorithm.

3505 7.6.7.8

Current Security Context

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

3508 7.6.7.9
-

Failure cause

3509 This parameter refers to an authentication failure which has occurred. It may take values as follows: 3510 3511

wrong user response; wrong network signature.

3512 7.6.7.10

Re-attempt

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

3515 7.6.7.11

Access Type

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

3519 3520 7.6.8.1

7.6.8 Short message parameters

SM-RP-DA

3521 This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be 3522 either of the following: 3523 3524 3525 3526 3527

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

3528 7.6.8.2

SM-RP-OA

3529 This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be 3530 either of the following: 3531 3532

MS-ISDN service centre address

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

3533 7.6.8.3
3534 3535 3536 3537

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

370

3GPP

3538 7.6.8.4

371 Release 7 372 373

94

3GPP TS 29.002 V7.5.0 (2006-09)

SM-RP-UI

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

3540 7.6.8.5

SM-RP-PRI

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

3543 7.6.8.6
-

SM Delivery Outcome

3544 This parameter indicates the cause for setting the message waiting data. It can take one of the following values: 3545 3546 3547

Absent subscriber; MS memory capacity exceeded; Successful transfer.

3548 7.6.8.7

More Messages To Send

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

3550 7.6.8.8
-

Alert Reason

3551 This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values: 3552 3553

MS present; Memory Available.

3554 7.6.8.9

Absent Subscriber Diagnostic SM

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

3557 7.6.8.10

Alert Reason Indicator

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

3559 7.6.8.11

Additional SM Delivery Outcome

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

3562 7.6.8.12

Additional Absent Subscriber Diagnostic SM

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

3564 7.6.8.13

Delivery Outcome Indicator

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

3566 7.6.8.14

GPRS Node Indicator

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

3568 7.6.8.15

GPRS Support Indicator

374

3GPP

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

375 Release 7 376 377

95

3GPP TS 29.002 V7.5.0 (2006-09)

3571 7.6.8.16

SM-RP-MTI

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

3575 7.6.8.17

SM-RP-SMEA

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

3579 3580 7.6.9.1

3581 3582 3583 3584

7.6.9 Access and signalling system related parameters

AN-apdu

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

3585 7.6.9.2
-

CM service type

3586 This parameter identifies the service category being requested by the subscriber: 3587 3588 3589 3590 3591 3592 3593 3594

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.

3595 7.6.9.3
-

Access connection status

3596 This parameter represents the following access connection status information: 3597 3598 3599

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

3600 7.6.9.4

External Signal Information

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

3604 7.6.9.5

Access signalling information

378

3GPP

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

379 Release 7 380 381

96

3GPP TS 29.002 V7.5.0 (2006-09)

3606 7.6.9.6

Location update type

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

3609 7.6.9.7

Protocol ID

3610 This parameter refers to the protocol to which the coding of the content of the associated External Signal Information 3611 conforms. 3612 The following values are defined: 3613 3614 3615

04.08; 08.06; ETS 300 102-1.

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

3617 7.6.9.8

Network signal information

3618 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1". 3619 The network signal information may include the following information elements as defined in 3GPP TS 29.007 [56]: 3620 3621 3622 3623 3624 3625

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

3626 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 CO N TENT H LC TAG LEN G TH CO N TENT LLC TAG LEN G TH CO N TENT

3627
3628

Figure 7.6/1: Network signal information parameter

3629 7.6.9.8A

Network signal information 2

382

3GPP

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

383 Release 7 384 385

97

3GPP TS 29.002 V7.5.0 (2006-09)

3633 7.6.9.9

Call Info

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

3637 7.6.9.10

Additional signal info

3638 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 356". 3639 The additional signal information may include the following information elements: 3640 3641

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

3642 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

3643
3644

LENGTH CONTENT
Figure 7.6/2: Additional signal information parameter

3645 3646 7.6.10.1

-

7.6.10 System operations parameters

Network resources

3647 This parameter refers to a class or type of network resource: 3648 3649 3650 3651 3652 3653

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

3654 7.6.10.2

Trace reference

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

3657 7.6.10.2A

Trace reference 2

386

3GPP

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

387 Release 7 388 389

98

3GPP TS 29.002 V7.5.0 (2006-09)

3660 7.6.10.3

Trace type

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

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

Additional network resources

3665 This parameter refers to a class or type of network resource: 3666 3667 3668 3669 3670 3671

3672 7.6.10.5

Trace depth list

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

3674 7.6.10.6

Trace NE type list

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

3676 7.6.10.7

Trace interface list

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

3679 7.6.10.8

Trace event list

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

3682 7.6.10.9

Trace support indicator

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

3684 7.6.10.10

Trace Propagation List

3685 This parameter indicates UMTS trace propagation parameters sent from one MSC to the other MSC in the signalling 3686 for inter MSC handover/relocation. See 3GPP TS 32.422 [132].

3687 3688 7.6.11.1

7.6.11 Location Service Parameters

Age of Location Estimate

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

3690 7.6.11.2

Deferred MT-LR Response Indicator

390

3GPP

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

391 Release 7 392 393

99

3GPP TS 29.002 V7.5.0 (2006-09)

3692 7.6.11.3
3693 3694 3695 3696 3697 3698 3699 3700

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.

3701 7.6.11.4

LCS Client ID

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

3703 7.6.11.5
3705 7.6.11.6

LCS Event

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

Void

3706 7.6.11.7

LCS Priority

3707 This parameter gives the priority of the location request.

3708 7.6.11.8

LCS QoS

3709 This parameter defines the Quality of Service (QoS) for any location request. It is composed of the following elements. 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719

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). 5) Velocity Request Indicates that velocity should be returned if available (inclusion is optional).

3720 7.6.11.9

CS LCS Not Supported by UE

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

394

3GPP

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

395 Release 7 396 397

100

3GPP TS 29.002 V7.5.0 (2006-09)

3729 7.6.11.11
3730 3731 3732 3733 3734 3735 3736 3737 3738

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

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

3741 7.6.11.11A

GERAN Positioning Data

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

3744 7.6.11.11B

UTRAN Positioning Data

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

3748 7.6.11.12

Location Type

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

3751 3752 3753 3754 3755

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

3756 7.6.11.13

NA-ESRD

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

3759 7.6.11.14

NA-ESRK

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

3762 7.6.11.15

LCS Service Type Id

398

3GPP

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

399 Release 7 400 401

101

3GPP TS 29.002 V7.5.0 (2006-09)

3765 7.6.11.16

Privacy Override

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

3768 7.6.11.17

Supported LCS Capability Sets

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

3770 7.6.11.18

LCS Codeword

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

3772 7.6.11.19

NA-ESRK Request

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

3775 7.6.11.20

Supported GAD Shapes

3776 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. If the parameter is not provided 3777 then the receiving node shall assume that the sending entity supports the following shapes: 3778 3779 3780 3781 3782

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

3783 7.6.11.21

Additional Location Estimate

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

3787 7.6.11.22

Cell Id Or SAI

3788 For GERAN access, this parameter contains the Global Cell Identifier for the cell that the subscriber is currently 3789 attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is 3790 currently attached to.

3791 7.6.11.23

LCS-Reference Number

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

3794 7.6.11.24

LCS Privacy Check

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

3797 -

positioning allowed without notifying the UE user;

402

3GPP

3798 3799 3800

403 Release 7 404 405

102

3GPP TS 29.002 V7.5.0 (2006-09)

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.

3801 3802

3803 -

3804 7.6.11.25

Additional LCS Capability Sets

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

3806 7.6.11.26

Area Event Info

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

3809 7.6.11.27
3810 3811 3812 3813 3814 3815 3816 3817

Velocity Estimate

This parameter gives an estimate of the velocity of an MS and the accuracy of the estimate. The estimate is expressed in terms of speed and bearing as defined by 3GPP TS 23.032 [122], and is composed of the velocity terms plus the encoding of the velocity itself. Only the encoding of the following velocity definitions shall be carried by the Velocity Estimate: - Horizontal Velocity - Horizontal with Vertical Velocity - Horizontal Velocity with Uncertainty - Horizontal with Vertical Velocity and Uncertainty

3818 7.6.11.28
3819 3820

Accuracy Fulfilment Indicator

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

3821 7.6.11.29
3822 3823

MO-LR Short Circuit Indicator

This parameter indicates whether MO-LR short circuit feature is permitted. For details see 3GPP TS 23.271 [26a].

3824 7.6.11.30
3825 3826

Reporting PLMN List

This parameter provides a list of PLMNs in which subsequent periodic MO-LR TTTP requests will be made. For details see 3GPP TS 23.271 [26a].

3827 7.6.11.31
3828 3829

Periodic LDR information

This parameter refers to the periodic reporting interval and reporting amount of the deferred periodic location. For details see 3GPP TS 23.271 [26a].

3830 7.6.11.32
3831 3832 3833 3834

Sequence Number

This parameter refers to the number of the periodic location reports completed. The sequence number would be set to 1 in the first location report and increment by 1 for each new report. When the number reaches the reporting amount value, the H-GMLC (for a periodic MT-LR or a periodic MO-LR transfer to third party) will know the procedure is complete. For details see 3GPP TS 23.271 [26a].

406

3GPP

3835

407 Release 7 408 409

103

3GPP TS 29.002 V7.5.0 (2006-09)

7.6.12 Void

3836

3837 3838

7.7 Representation of a list of a basic parameter in serviceprimitives

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

ParameterNameLIST

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

3844
3845

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

3846 3847 3848

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

3849 8.1.1.1 3850 8.1.1.2 3851 8.1.1.3 3852 3853 8.1.2.1

8.1.2 MAP_UPDATE_LOCATION service

Definition

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

3856 8.1.2.2
3857

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

Request M M M M U C C

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

Response M(=)

Confirm M(=)

410

3GPP

411 Release 7 412 413 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 Supported RAT Types Indicator ADD Capability HLR number User error Provider error

104 C C C C C C C U C U U C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V7.5.0 (2006-09)

U C C

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

3858

3859 8.1.2.3
3860 Invoke Id

Parameter definitions and use

3861 See definition in clause 7.6.1. 3862 IMSI 3863 See definition in clause 7.6.2. 3864 MSC Address 3865 See definition for MSC number in clause 7.6.2. The MSC address is used for short message delivery only and for each 3866 incoming call set-up attempt the MSRN will be requested from the VLR. 3867 VLR number 3868 See definition in clause 7.6.2. 3869 LMSI 3870 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 3871 to support the LMSI handling procedures. 3872 Supported CAMEL Phases 3873 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 3874 phase 1 is supported. Otherwise may be absent. 3875 HLR number 3876 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3877 SoLSA Support Indicator 3878 3879 3880 3881

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.

3882 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 3883 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 3884 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 3885 IST Support Indicator 3886 This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able 3887 to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating 3888 that the call(s) shall be terminated. If this parameter is not included in the Update Location indication and the

414

3GPP

3889 Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an 3890 Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of 3891 not having the basic IST mechanism available. 3892 3893 3894 3895 3896

415 Release 7 416 417

105

3GPP TS 29.002 V7.5.0 (2006-09)

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.

3897 Long FTN Supported 3898 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 3899 Super-Charger Supported in Serving Network Entity 3900 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 3901 whether subscription data has been retained by the VLR. If subscription data has been retained by the VLR the age 3902 indicator shall be included. Otherwise the VLR shall indicate that subscriber data is required. 3903 If this parameter is absent then the VLR does not support the Super-Charger functionality. 3904 Supported LCS Capability Sets 3905 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 3906 capability set is marked as supported then the VLR does not support LCS at all. 3907 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 3908 version. 3909 Offered CAMEL 4 CSIs 3910 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D). 3911 Inform Previous Network Entity

3912 3913 3914 3915

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.

3916 CS LCS Not Supported by UE 3917 See definition in clause 7.6.11. 3918 V-GMLC address 3919 See definition in clause 7.6.2. 3920 IMEISV 3921 For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.012. IMEISV shall be 3922 present if ADD function is supported and a new IMEISV is to be notified to the HLR (The functional requirements for 3923 the presence of IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4). 3924 Skip Subscriber Data Update 3925 The presence of the parameter is optional and if present it indicates that the service is solely used to inform the HLR 3926 about change of IMEISV. The parameter is used to optimise signalling load during Location Update procedure. 3927 Supported RAT Types Indicator 3928 This parameter indicates, if present, which access technologies (e.g. GERAN and / or UTRAN) are served by the 3929 MSC/VLR (see clause 7.6.3) 3930 ADD Capability

418

3GPP

3931 This parameter indicates, if present, the support of ADD function by the HLR. 3932 User error 3933 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3934 clause 7.6.1 may be used, depending on the nature of the fault: 3935 3936 3937 3938 3939 3940 3941 3942

419 Release 7 420 421

106

3GPP TS 29.002 V7.5.0 (2006-09)

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", "Supported RAT Types 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.

3943 Provider error 3944 For definition of provider errors see clause 7.6.1.

3945 3946 8.1.3.1

8.1.3 MAP_CANCEL_LOCATION service

Definition

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

3954 8.1.3.2
3955

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

3956

3957 8.1.3.3
3958 Invoke Id

Parameter definitions and use

3959 See definition in clause 7.6.1. 3960 IMSI 3961 See definition in clause 7.6.2. 3962 LMSI

422

3GPP

3963 See definition in clause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable 3964 between SGSN and HLR. 3965 Value 0000 0000 can be used to indicate that the LMSI is not in use. 3966 Cancellation Type 3967 See definition in clause 7.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the 3968 SGSN. If the VLR receives this parameter and do not understand it the VLR shall ignore it. 3969 User error 3970 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. One of the following error causes 3971 defined in clause 7.6.1 shall be used: 3972 3973

423 Release 7 424 425

107

3GPP TS 29.002 V7.5.0 (2006-09)

unexpected data value; data missing.

3974 Provider error 3975 For definition of provider errors see clause 7.6.1.

3976 3977 8.1.4.1

8.1.4 MAP_SEND_IDENTIFICATION service

Definition

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

3982 8.1.4.2
3983

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

3984

3985 8.1.4.3
3986 Invoke Id

Parameter definitions and use

3987 See definition in clause 7.6.1. 3988 TMSI 3989 See definition in clause 7.6.2. 3990 If multiple service requests are present in a dialogue then this parameter shall be present in every service request.

426

3GPP

3991 Number of requested vectors 3992 A number indicating how many authentication vectors the new VLR is prepared to receive. The previous VLR shall not 3993 return more vectors than indicated by this parameter. 3994 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 3995 dialogue then this parameter shall not be present in any service request other than the first one 3996 Segmentation prohibited indicator 3997 This parameter indicates if the new VLR or SGSN allows segmentation of the response at MAP user level. 3998 This parameter may be present only in the first request of the dialogue. 3999 IMSI 4000 See definition in clause 7.6.2. The IMSI is to be returned if the service succeeds. 4001 If multiple service requests are present in a dialogue and the service succeeds then this parameter shall not be present in 4002 any service response other than the first one 4003 MSC Number 4004 This is the ISDN number assigned to the MSC currently serving the MS. 4005 Previous Location Area Id 4006 See definition in clause 7.6.2. Together with the TMSI the Previous Location Area Id can be used to derive the IMSI. 4007 Authentication set 4008 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 4009 available. 4010 Current Security Context 4011 See definition in clause 7.6.7. If the service succeeds, a list of either GSM or UMTS Security Context parameters can be 4012 returned. 4013 Hop Counter 4014 For the use of this parameter see 3GPP TS 23.012 [23]. 4015 User error 4016 This parameter is mandatory if the service fails. The following error cause defined in clause 7.6.1 may be used, 4017 depending on the nature of the fault: 4018

427 Release 7 428 429

108

3GPP TS 29.002 V7.5.0 (2006-09)

unidentified subscriber.

4019 Provider error 4020 For definition of provider errors see clause 7.6.1.

4021 4022 8.1.5.1 4023 8.1.5.2 4024 8.1.5.3 4025

8.1.5 Void
Void Void Void

8.1.6 MAP_PURGE_MS service

430

3GPP

4026 8.1.6.1
4027 4028 4029 4030 4031 4032 4033 4034 4035 4036

431 Release 7 432 433

109

3GPP TS 29.002 V7.5.0 (2006-09)

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.

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

4038 8.1.6.2
4039

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

4040

4041 8.1.6.3
4042 Invoke ID

Parameter definitions and use

4043 See definition in clause 7.6.1. 4044 IMSI 4045 See definition in clause 7.6.2. 4046 VLR number 4047 Shall be present if the sender is VLR. See definition in clause 7.6.2. 4048 SGSN number 4049 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 4050 Freeze TMSI 4051 This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR 4052 number matches the stored VLR number. 4053 Freeze P-TMSI 4054 This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received 4055 SGSN number matches the stored SGSN number. 4056 User error 4057 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 4058

Data Missing;

434

3GPP

4059

435 Release 7 436 437

110

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected Data Value; Unknown Subscriber.

4060

4061 Provider error 4062 See definition of provider errors in clause 7.6.1.

4063 4064 8.1.7.1

8.1.7 MAP_UPDATE_GPRS_LOCATION service

Definition

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

4068 8.1.7.2
4069

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 PS LCS Not Supported by UE V-GMLC Address Call barring support indicator IMEISV Skip Subscriber Data Update Supported RAT Types Indicator ADD Capability HLR number User error Provider error

Request M M M M C C C C C C C C U C C U 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

4070

4071 8.1.7.3
4072 Invoke Id

Parameter definitions and use

4073 See definition in clause 7.6.1. 4074 IMSI 4075 See definition in clause 7.6.2. 4076 SGSN number 4077 See definition in clause 7.6.2. 4078 SGSN address 4079 See definition in clause 7.6.2. 4080 Supported CAMEL Phases

438

3GPP

4081 This parameter indicates which phases of CAMEL are supported. The SGSN can only support CAMEL phase 3 or 4082 greater. 4083 SoLSA Support Indicator 4084 4085 4086 4087

439 Release 7 440 441

111

3GPP TS 29.002 V7.5.0 (2006-09)

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.

4088 This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a 4089 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support 4090 indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted. 4091 Super-Charger Supported in Serving Network Entity 4092 This parameter is used by the SGSN to indicate to the HLR that the SGSN supports the Super-Charger functionality and 4093 whether subscription data has been retained by the SGSN. If subscription data has been retained by the SGSN the age 4094 indicator shall be included. Otherwise the SGSN shall indicate that subscriber data is required. 4095 If this parameter is absent then the SGSN does not support the Super-Charger functionality. 4096 GPRS enhancements support indicator 4097 4098 4099 4100

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.

4101 HLR number 4102 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 4103 Supported LCS Capability Sets 4104 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 4105 capability set is marked as supported then the SGSN does not support LCS at all. 4106 The SGSN is not allowed to indicate support for LCS capability set 1. 4107 If this parameter is absent then the SGSN does not support LCS at all. 4108 Offered CAMEL 4 CSIs 4109 This parameter indicates the CAMEL phase 4 CSIs offered in the SGSN (see clause 7.6.3.36D). 4110 Inform Previous Network Entity

4111 4112 4113 4114

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.

4115 PS LCS Not Supported by UE 4116 See definition in clause 7.6.11. 4117 V-GMLC address 4118 See definition in clause 7.6.2. 4119 Call Barring support indicator 4120 See definition in clause 7.6.3.92. 4121 IMEISV

442

3GPP

4122 For definition of the parameter see clause 7.6.2. For the use of this parameter see 3GPP TS 23.060. IMEISV shall be 4123 present if ADD function is supported and the IMEISV is new in SGSN (The functional requirements for the presence of 4124 IMEISV due to ADD are described in 3GPP TS 22.101 clause 7.4). 4125 Skip Subscriber Data Update 4126 The presence of the parameter is optional and if present it indicates that the service is solely used to inform the HLR 4127 about change of IMEISV. The parameter is used to optimise signalling load during Location Update procedure. 4128 Supported RAT Types Indicator 4129 This parameter indicates, if present, which access technologies (e.g. GERAN and/or UTRAN) are served by the SGSN 4130 (see clause 7.6.3) 4131 4132 ADD Capability 4133 This parameter indicates, if present, the support of ADD function by the HLR. 4134 User error 4135 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 4136 clause 7.6.1 may be used, depending on the nature of the fault: 4137 4138 4139 4140 4141 4142 4143 4144

443 Release 7 444 445

112

3GPP TS 29.002 V7.5.0 (2006-09)

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", "Supported RAT Types 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.

4145 Provider error 4146 For definition of provider errors see clause 7.6.1.

4147 4148 8.1.8.1

8.1.8 MAP-NOTE-MM-EVENT
Definition

4149 This service is used between the VLR and the gsmSCF or between the SGSN and the gsmSCF when a mobility 4150 management event for a subscriber has been processed successfully, that subscriber is provisioned with M-CSI or MG4151 CSI and the relevant mobility management event is marked for reporting. 4152 4153 4154 4155

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

4156 8.1.8.2

Service primitives

4157 The service primitives are shown in table 8.1/8. 4158

Parameter name Invoke id

Table 8.1/8: MAP_NOTE_MM_EVENT parameters

Request M Indication M(=) Response M(=) Confirm M(=)

446

3GPP

447 Release 7 448 449 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

113 M M M M C C C M C M(=) M(=) M(=) M(=) C(=) C(=) C(=) M(=) C(=)

3GPP TS 29.002 V7.5.0 (2006-09)

C(=) O

4159

4160 8.1.8.3

Parameter use

4161 Event Met 4162 This parameter indicates the mobility management event that has lead to the notification. It shall have one of the 4163 following values for a mobility management event reported by the VLR: 4164 4165 4166 4167 4168

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

4169 It shall have one of the following values for a mobility management event reported by the SGSN: 4170 4171 4172 4173 4174 4175

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.

4176 Service Key 4177 See clause 7.6.x. 4178 IMSI 4179 See clause 7.6.x. 4180 Basic MSISDN 4181 See clause 7.6.x. 4182 Location Information 4183 See clause 7.6.2.30. This information shall be sent when the event is reported by a VLR, if available. 4184 Location Information for GPRS 4185 See clause 7.6.2.30a. This information shall be sent when the event is reported by an SGSN, if available. 4186 LSA Identity 4187 See clause 7.6.x. This information shall be sent, if available.

450

3GPP

4188 Supported CAMEL Phases 4189 See clause 7.6.x. This information shall always be sent. 4190 Offered CAMEL 4 Functionalities 4191 This parameter indicates the CAMEL phase 4 functionalities offered by the sending entity, VMSC/VLR or SGSN (see 4192 clause 7.6.3.36G). 4193 User error 4194 This parameter is sent by the receiving entity when an error is detected. It shall have one of the following values: 4195 4196 4197 4198

451 Release 7 452 453

114

3GPP TS 29.002 V7.5.0 (2006-09)

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

4199 Provider error 4200 This is defined in clause 7.6.1.

4201 4202 4203 8.2.1.1

8.2 Paging and search

8.2.1 MAP_PAGE service
Definition

4204 This service is used between VLR and MSC to initiate paging of an MS for mobile terminated short message or 4205 unstructured SS notification. 4206 The MAP_PAGE service is a confirmed service using the primitives from table 8.2/1.

4207 8.2.1.2
4208

Service primitives
Table 8.2/1: MAP_PAGE
Parameter name Invoke Id IMSI Stored location area Id TMSI User error Provider error Request M M M U Indication M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

C(=) O

4209

4210 8.2.1.3
4211 Invoke Id

Parameter definitions and use

4212 See definition in clause 7.6.1. 4213 IMSI 4214 See definition in clause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging on 4215 the radio path uses the IMSI as an identifier. 4216 Stored location area Id 4217 See definition in clause 7.6.2.

454

3GPP

4218 TMSI

455 Release 7 456 457

115

3GPP TS 29.002 V7.5.0 (2006-09)

4219 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. 4220 User error 4221 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 4222 failure reason: 4223 4224 4225 4226 4227 4228 4229

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.

4230 Provider error 4231 See definition in clause 7.6.1.

4232 4233 8.2.2.1

8.2.2 MAP_SEARCH_FOR_MS service

Definition

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

4237 8.2.2.2
4238

Service primitives
Table 8.2/2: MAP_SEARCH_FOR_MS
Parameter name Invoke Id IMSI Current location area Id User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

4239

4240 8.2.2.3
4241 Invoke Id

Parameter definitions and use

4242 See definition in clause 7.6.1. 4243 IMSI 4244 See definition in clause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path. 4245 Current location area Id 4246 See definition in clause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the 4247 Location Area Id of the area in which the MS responded is given in the response.

458

3GPP

4248 User error

459 Release 7 460 461

116

3GPP TS 29.002 V7.5.0 (2006-09)

4249 The following error causes defined in clause 7.6.1 shall be sent by the user if the search procedure fails, depending on 4250 the failure reason: 4251 4252 4253 4254 4255 4256 4257

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.

4258 Provider error 4259 See definition in clause 7.6.1.

4260 4261 4262 8.3.1.1

8.3 Access management services

8.3.1 MAP_PROCESS_ACCESS_REQUEST service
Definition

4263 This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. for mobile 4264 originated short message submission or after being paged by the network. 4265 The MAP_PROCESS_ACCESS_REQUEST service is a confirmed service using the primitives from table 8.3/1.

4266 8.3.1.2
4267

Service primitives
Table 8.3/1: MAP_PROCESS_ACCESS_REQUEST
Parameter name Invoke Id CM service type Access connection status Current Location Area Id Serving cell Id TMSI Cksn IMSI IMEI MSISDN User error Provider error Request M M M M M C C C C Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C U C

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

4268

4269 8.3.1.3
4270 Invoke Id

Parameter definitions and use

4271 See definition in clause 7.6.1. 4272 CM service type 4273 See definition in clause 7.6.9.

462

3GPP

4274 Access connection status 4275 See definition in clause 7.6.9. 4276 Current Location Area Id 4277 See definition in clause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure. 4278 Serving cell Id 4279 See definition in clause 7.6.2. 4280 TMSI 4281 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 4282 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 4283 Cksn 4284 See definition in clause 7.6.7. In case of access with TMSI, the Cksn shall be present. 4285 IMSI 4286 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 4287 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 4288 In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM 4289 Service Type "Emergency Call Establishment", IMEI may replace IMSI. 4290 IMEI 4291 See definition in clause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the 4292 Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment". 4293 MSISDN 4294 See definition in clause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator 4295 option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding. 4296 User error 4297 One of the following error causes defined in clause 7.6.1 shall be sent by the user if the access request fails, depending 4298 on the failure reason: 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310

463 Release 7 464 465

117

3GPP TS 29.002 V7.5.0 (2006-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.

4311 Provider error

466

3GPP

4312 For definition of provider errors see clause 7.6.1.

467 Release 7 468 469

118

3GPP TS 29.002 V7.5.0 (2006-09)

4313

8.4 Handover services

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

4317 4318 8.4.1.1

8.4.1 MAP_PREPARE_HANDOVER service

Definition

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

4322 8.4.1.2
4323

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 RANAP Service Handover Iu-Currently Used Codec Iu-Supported Codecs List RAB Configuration Indicator ASCI Call Reference UESBI-Iu IMEISV Alternative Channel Type Trace_Propagation_List 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 Request 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 Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C C C C(=) C C C C C C C(=) C(=) C(=) C(=) C(=) C(=) O C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=)

4324

470

3GPP

4325 8.4.1.3

471 Release 7 472 473

119

3GPP TS 29.002 V7.5.0 (2006-09)

Parameter use

4326 Invoke Id 4327 For definition of this parameter see clause 7.6.1. 4328 Target Cell Id 4329 For definition of this parameter see clause 7.6.2. This parameter is only included if the service is not in an ongoing 4330 transaction. This parameter shall also be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure 4331 or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009. 4332 Target RNC Id 4333 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter4334 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4335 23.009. 4336 HO-Number Not Required 4337 For definition of this parameter see clause 7.6.6. 4338 IMSI 4339 For definition of this parameter see clause 7.6.2. This UMTS parameter shall be included if:

4340 4341 4342

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

4343 Integrity Protection Information 4344 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 4345 network protocol is BSSAP. 4346 Encryption Information 4347 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 4348 network protocol is BSSAP. 4349 Radio Resource Information 4350 For definition of this parameter see clause 7.6.6. This GSM parameter shall be included if the access network protocol 4351 is RANAP and there is an indication that the UE also supports GSM. If the parameter Radio Resource List is sent , the 4352 parameter Radio Resource Information shall not be sent. 4353 AN-APDU 4354 For definition of this parameter see clause 7.6.9. 4355 Allowed GSM Algorithms 4356 For definition of this parameter see clause 7.6.6. This parameters includes allowed GSM algorithms. This GSM 4357 parameter shall be included if:

4358 4359 4360

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.

4361 Allowed UMTS Algorithms 4362 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if all of the following 4363 conditions apply:

474

3GPP

4364 4365

475 Release 7 476 477

120

3GPP TS 29.002 V7.5.0 (2006-09)

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

4366 Ciphering or Security Mode Setting procedure has been performed. 4367 Radio Resource List 4368 4369 4370 4371

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.

4372 RAB ID 4373 For definition of this parameter see subclause 7.6.2. This parameter shall be included when MSC-A supports multiple 4374 bearers and access network protocol is BSSAP and the RAB ID has a value other than 1. 4375 GERAN Classmark 4376 For definition of this parameter see subclause 7.6.6 This parameter shall be included if available. 4377 BSSMAP Service Handover 4378 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4379 RANAP. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not 4380 be sent. 4381 BSSMAP Service Handover List 4382 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4383 RANAP. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter BSSMAP 4384 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4385 RANAP Service Handover 4386 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4387 BSSAP. 4388 Iu-Currently Used Codec 4389 For definition of this parameter see subclause 7.6.6. This parameter shall be included if the handover is requested for a 4390 speech bearer and the MS is in UMTS or GERAN Iu-mode access. This parameter shall not be included if the Iu4391 Supported Codecs List is not included. 4392 Iu-Supported Codecs List 4393 For definition of this parameter see subclause 7.6.6. This parameter shall be included by MSC-A, if the handover is 4394 requested for a speech bearer. 4395 RAB Configuration Indicator 4396 For definition of this parameter see subclause 7.6.6. This parameter may be included if the handover is requested for a 4397 speech bearer and MSC-A knows by means of configuration information that MSC-B supports the use of the Iu4398 Supported Codecs List parameter. This parameter shall not be included if the Iu-Supported Codecs List is not included. 4399 ASCI Call Reference 4400 This parameter contains either the broadcast call reference or group call reference. It shall be included if a subscriber is 4401 undergoing handover during a VGCS or VBS call, where MSC-B already has a Bearer established, so that MSC-B can 4402 determine the Group or Broadcast Call to which it shall attach the subscriber, see 3GPP TS 48.008 [49]. 4403 4404 UESBI-Iu

478

3GPP

4405 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4406 BSSAP. 4407 IMEISV 4408 For definition of the parameter see clause 7.6.2. This parameter is used for Management based Trace Activation (see 4409 3GPP TS 32.422) and shall be present, if available. 4410 Alternative Channel Type 4411 For definition of this parameter see clause 7.6.6 It shall be present for a SCUDIF call if the access network protocol is 4412 BSSAP. 4413 Trace Propagation List 4414 See definition in clause 7.6.10. This parameter shall be included when MSC-A requests trace invocation. 4415 Handover Number 4416 For definition of this parameter see clause 7.6.2. This parameter shall be returned at handover, unless the parameter 4417 HO-NumberNotRequired is sent. If the parameter Handover Number is returned, the parameter Relocation Number List 4418 shall not be returned. 4419 Relocation Number List 4420 For definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation, unless the parameter 4421 HO-NumberNotRequired is sent. If the parameter Relocation Number List is returned, the parameter Handover Number 4422 shall not be returned. 4423 Multicall Bearer Information 4424 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation in the case that MSC-B 4425 supports multiple bearers. 4426 4427 Multiple Bearer Requested 4428 For a definition of this parameter see clause 7.6.2. This parameter shall be sent when MSC-A requests multiple bearers 4429 to MSC-B. 4430 Multiple Bearer Not Supported 4431 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation when MSC-B receives 4432 Multiple Bearer Requested parameter and MSC-B does not support multiple bearers. 4433 Selected UMTS Algorithms 4434 For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally 4435 encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the 4436 service is a part of the inter MSC inter system handover from GSM to UMTS. 4437 Chosen Radio Resource Information 4438 For definition of this parameter see clause 7.6.6. This parameter shall be returned at relocation if the encapsulated PDU 4439 is RANAP RAB Assignment Response and MS is in GSM access. 4440 Iu-Selected Codec 4441 4442 4443 4444

479 Release 7 480 481

121

3GPP TS 29.002 V7.5.0 (2006-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.

4445 Iu-Available Codecs List

482

3GPP

4446 For definition of this parameter see subclause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO, if 4447 the Iu-Supported Codecs List was included by MSC-A and the target radio access is UMTS or GERAN Iu-mode. 4448 User error 4449 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4450 on the nature of the fault: 4451 4452 4453 4454 4455

483 Release 7 484 485

122

3GPP TS 29.002 V7.5.0 (2006-09)

No handover number available. Target cell outside group call area; System failure. Unexpected data value. Data Missing.

4456 Provider error 4457 See definition of provider errors in clause 7.6.1.

4458 4459 8.4.2.1

8.4.2 MAP_SEND_END_SIGNAL service

Definition

4460 This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by 4461 MSC-B to the MS. MSC-A retains then the main control of the call until it clears. 4462 The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either 4463 because the call has been released in MSC-A or because the call has been successfully handed over or relocated from 4464 MSC-B to another MSC. 4465 The MAP_SEND_END_SIGNAL service is a confirmed service using the primitives from table 8.4/2.

4466 8.4.2.2
4467

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

4468

4469 8.4.2.3
4470 Invoke Id

Parameter use

4471 For definition of this parameter see clause 7.6.1. 4472 AN-APDU 4473 For definition of this parameter see clause 7.6.9. 4474 Provider error 4475 For definition of this parameter see clause 7.6.1.

4476 4477 8.4.3.1

8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service

Definition

486

3GPP

4478 This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A-interface or Iu4479 interface in MSC-B to MSC-A. 4480 The MAP_PROCESS_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4481 table 8.4/3.

487 Release 7 488 489

123

3GPP TS 29.002 V7.5.0 (2006-09)

4482 8.4.3.2
4483

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

4484

4485 8.4.3.3
4486 Invoke Id

Parameter use

4487 For definition of this parameter see clause 7.6.1. 4488 AN-APDU 4489 For definition of this parameter see clause 7.6.9. 4490 Selected GSM algorithm 4491 For definition of this parameter see clause 7.6.6. This parameter shall be present if the encapsulated PDU is Security 4492 Mode Complete and MS is in GSM access. 4493 Selected UMTS Algorithms 4494 4495 4496 4497

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.

4498 Chosen Radio Resource Information 4499 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4500 Assignment Response and MS is in GSM access. 4501 Selected RAB ID 4502 The selected radio access bearer that was kept at subsequent intra-MSC handover from UMTS to GSM after multiple 4503 bearers were used. 4504 Iu-Selected Codec 4505 For definition of this parameter see subclause 7.6.6. This parameter shall be included

4506 4507 4508

4509

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.

490

3GPP

4510 This parameter shall not be included if the Iu-Supported Codecs List was not received either in the Prepare Handover 4511 service request or in the Forward Access Signalling service request. 4512 Iu-Available Codecs List 4513 For definition of this parameter see subclause 7.6.6. This parameter shall be included by an MSC-B supporting TrFO

491 Release 7 492 493

124

3GPP TS 29.002 V7.5.0 (2006-09)

4514 4515 4516

4517 4518

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.

4519 4520 8.4.4.1

8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service

Definition

4521 This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface 4522 or Iu-interface of MSC-B. 4523 The MAP_FORWARD_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4524 table 8.4/4.

4525 8.4.4.2
4526

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 RAB Configuration Indicator Iu-Selected Codec Alternative Channel Type Trace Propagation List Request M C C C M C C C C C C C C C C C C C Indication M(=) C(=) C(=) C(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)

4527

4528 8.4.4.3
4530 Invoke Id

Parameter use

4529 For the definition and use of all parameters and errors, see clause 7.6.1.

4531 For definition of this parameter see clause 7.6.1. 4532 Integrity Protection Information 4533 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4534 encapsulated PDU is BSSMAP Cipher Mode Command.

494

3GPP

4535 Encryption Information 4536 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4537 encapsulated PDU is BSSMAP Cipher Mode Command. 4538 Key Status 4539 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4540 encapsulated PDU is BSSMAP Cipher Mode Command. 4541 AN-APDU 4542 For definition of this parameter see clause 7.6.9. 4543 Allowed GSM Algorithms 4544 This parameters includes allowed GSM algorithms. This GSM parameter shall be included if the encapsulated PDU is 4545 RANAP Security Mode Command and there is an indication that the UE also supports GSM. 4546 Allowed UMTS Algorithms 4547 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if Integrity Protection 4548 Information and Encryption Information are not available and the encapsulated PDU is BSSMAP Cipher Mode 4549 Command. 4550 Radio Resource Information 4551 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4552 Assignment Request. If the parameter Radio Resource List is sent, the parameter Radio Resource Information shall not 4553 be sent. 4554 Radio Resource List 4555 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4556 Assignment Request and MSC-A requests modification of multiple bearers. If the parameter Radio Resource 4557 Information is sent, the parameter Radio Resource List shall not be sent. 4558 BSSMAP Service Handover 4559 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4560 RANAP RAB Assignment Request. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP 4561 Service Handover shall not be sent. 4562 BSSMAP Service Handover List 4563 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4564 RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter BSSMAP 4565 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4566 RANAP 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 BSSMAP Assignment Request. 4569 Iu-Currently Used Codec 4570 For definition of this parameter see subclause 7.6.6. This parameter shall be included if the encapsulated PDU is a 4571 RANAP RAB Assignment Request or BSSMAP Assignment Request for a speech bearer and the MS is in UMTS or 4572 GERAN Iu-mode access. This parameter shall not be included if the Iu-Supported Codecs List is not included. 4573 Iu-Supported Codecs List 4574 For definition of this parameter see subclause 7.6.6. This parameter shall be included if the encapsulated PDU is a 4575 RANAP RAB Assignment Request or BSSMAP Assignment Request and

495 Release 7 496 497

125

3GPP TS 29.002 V7.5.0 (2006-09)

4576

a new bearer is allocated for speech;

498

3GPP

4577 4578

499 Release 7 500 501

126

3GPP TS 29.002 V7.5.0 (2006-09)

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.

4579 This parameter shall not be included if the Iu-Selected Codec is included. 4580 RAB Configuration Indicator 4581 4582 4583 4584

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.

4585 Iu-Selected Codec 4586 For definition of this parameter see subclause 7.6.6. This parameter shall be included if

4587
4588

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.

4589 4590
4591

4592 This parameter shall not be included if the Iu-Supported Codecs List is included. 4593 Alternative Channel Type 4594 For definition of this parameter see clause 7.6.6. This parameter shall be present for a SCUDIF call if the encapsulated 4595 PDU is BSSMAP Assignment Request. 4596 Trace Propagation List 4597 See definition in clause 7.6.10. This parameter shall be included when MSC-A requests trace invocation. 4598

4599 4600 8.4.5.1

8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service

Definition

4601 This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a 4602 handover or relocation to either MSC-A or a third MSC (MSC-B') is required. 4603 The MAP_PREPARE_SUBSEQUENT_HANDOVER service is a confirmed service using the primitives from 4604 table 8.4/5.

502

3GPP

4605 8.4.5.2
4606

503 Release 7 504 505

127

3GPP TS 29.002 V7.5.0 (2006-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

4607

4608 8.4.5.3
4609 Invoke Id

Parameter use

4610 For definition of this parameter see clause 7.6.1. 4611 Target Cell Id 4612 For definition of this parameter see clause 7.6.2. This parameter shall be excluded if the service is a part of the Inter4613 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4614 23.009. 4615 Target RNC Id 4616 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter4617 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4618 23.009. 4619 Target MSC Number 4620 For definition of this parameter see clause 7.6.2. 4621 Selected RAB ID 4622 For definition of this parameter see clause 7.6.2. 4623 GERAN Classmark 4624 For definition of this parameter see subclause 7.6.6 This parameter shall be included if available. 4625 RAB Configuration Indicator 4626 For definition of this parameter see subclause 7.6.6. This parameter may be included if the call is a speech call and 4627 MSC-B knows by means of configuration information that MSC-B' (and MSC-A) supports the use of Available Codecs 4628 List parameter. 4629 AN-APDU 4630 For definition of this parameter see clause 7.6.9. 4631 User error 4632 For definition of this parameter see clause 7.6.1. The following error causes defined in clause 7.6.1 may be used, 4633 depending on the nature of the fault: 4634 4635

Unknown MSC; Subsequent handover failure;

506

3GPP

4636 4637

507 Release 7 508 509

128

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected data value; Data Missing.

4638 Provider error 4639 For definition of this parameter see clause 7.6.1.

4640 4641 8.4.6.1

8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service

Definition

4642 This service is used between MSC and VLR (B-interface) to request a handover number. 4643 The MAP_ALLOCATE_HANDOVER_NUMBER service is a confirmed service using the primitives from table 8.4/6.

4644 8.4.6.2
4645

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

4646

4647 8.4.6.3
4648 Invoke Id

Parameter use

4649 For definition of this parameter see clause 7.6.1. 4650 User error 4651 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4652 on the nature of the fault: 4653

No handover number available.

4654 Provider error 4655 For definition of this parameter see clause 7.6.1.

4656 4657 8.4.7.1

8.4.7 MAP_SEND_HANDOVER_REPORT service

Definition

4658 This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and 4659 used by MSC-A. 4660 The MAP_SEND_HANDOVER_REPORT service is a confirmed service using the primitives from table 8.4/7.

510

3GPP

4661 8.4.7.2
4662

511 Release 7 512 513

129

3GPP TS 29.002 V7.5.0 (2006-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(=)

4663

4664 8.4.7.3
4665 Invoke Id

Parameter use

4666 For definition of this parameter see clause 7.6.1. 4667 Handover Number 4668 For definition of this parameter see clause 7.6.2. 4669 Linked Id 4670 For definition of this parameter see clause 7.6.1. This service is linked with 4671 MAP_ALLOCATE_HANDOVER_NUMBER. 4672 Provider error 4673 For definition of this parameter see clause 7.6.1.

4674 4675

8.5 Authentication management services

8.5.1 MAP_AUTHENTICATE service

4676 The MAP_AUTHENTICATE service is used on the MAP B interface. This interface is not fully operational specified. 4677 It is strongly recommended not to implement the B-interface as an external interface.

4678 8.5.1.1

Definition

4679 This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC 4680 concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to 4681 initiate authentication. 4682 The service is a confirmed service and consists of four service primitives.

4683 8.5.1.2

Service primitives

4684 The service primitives are shown in table 8.5/1. 4685

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

4686

514

3GPP

4687 8.5.1.3

515 Release 7 516 517

130

3GPP TS 29.002 V7.5.0 (2006-09)

Parameter use

4688 Invoke id 4689 See clause 7.6.1 for the use of this parameter. 4690 RAND 4691 See clause 7.6.7 for the use of this parameter. 4692 CKSN 4693 See clause 7.6.7 for the use of this parameter. 4694 SRES 4695 See clause 7.6.7 for the use of this parameter. 4696 Provider error 4697 See clause 7.6.1 for the use of this parameter.

4698 4699 8.5.2.1

8.5.2 MAP_SEND_AUTHENTICATION_INFO service

Definition

4700 This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. 4701 The VLR requests up to five authentication vectors. 4702 Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information from the 4703 HLR. The SGSN requests up to five authentication vectors. 4704 If the user is a UMTS subscriber, the HLR shall return authentication quintuplets. If the user is a GSM subscriber, the 4705 HLR shall return authentication triplets. 4706 If the HLR cannot provide the VLR or the SGSN with triplets, an empty response is returned. The VLR or the SGSN 4707 may then re-use old authentication triplets, except where this is forbidden under the conditions specified in 3GPP TS 4708 43.020 [24]. 4709 If the HLR cannot provide the VLR or the SGSN with quintuplets, an empty response is returned. The VLR or the 4710 SGSN shall not re-use old authentication quintuplets. 4711 If the VLR or SGSN receives a MAP_SEND_AUTHENTICATION_INFO response containing a User Error parameter 4712 as part of the handling of an authentication procedure, the authentication procedure in the VLR or SGSN shall fail. 4713 Security related network functions are further described in 3GPP TS 43.020 [24] and 3GPP TS 33.200. 4714 The service is a confirmed service and consists of four service primitives.

4715 8.5.2.2

Service primitives

4716 The service primitives are shown in table 8.5/2. 4717

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

518

3GPP

519 Release 7 520 521 AuthenticationSetList User error Provider error

131

3GPP TS 29.002 V7.5.0 (2006-09) C C C(=) C(=) O

4718

4719 8.5.2.3
4720 Invoke id

Parameter use

4721 See clause 7.6.1 for the use of this parameter. 4722 IMSI 4723 See clause 7.6.2 for the use of this parameter. 4724 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4725 dialogue then this parameter shall not be present in any service request other than the first one. 4726 Number of requested vectors 4727 A number indicating how many authentication vectors the VLR or SGSN is prepared to receive. The HLR shall not 4728 return more vectors than indicated by this parameter. 4729 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4730 dialogue then this parameter shall not be present in any service request other than the first one. 4731 Requesting node type 4732 The type of the requesting node (SGSN or VLR). 4733 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4734 dialogue then this parameter shall not be present in any service request other than the first one. 4735 Re-synchronisation Info 4736 For definition and use of this parameter see 3GPP TS 33.200. 4737 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4738 than the first one.. 4739 Segmentation prohibited indicator 4740 This parameter indicates if the VLR or SGSN allows segmentation of the response at MAP user level. 4741 This parameter may be present only in the first request of the dialogue. 4742 Immediate response preferred indicator 4743 4744 4745 4746

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.

4747 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4748 than the first one. 4749 Requesting PLMN ID 4750 The PLMN-ID of the requesting node. See3GPP TS 23.003. 4751 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4752 dialogue then this parameter shall not be present in any service request other than the first one. 4753 AuthenticationSetList

522

3GPP

4754 A set of one to five authentication vectors are transferred from the HLR to the VLR or from the HLR to the SGSN, if 4755 the outcome of the service was successful. 4756 User error 4757 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4758 the service, depending on the respective failure reason: 4759 4760 4761 4762

523 Release 7 524 525

132

3GPP TS 29.002 V7.5.0 (2006-09)

unknown subscriber; unexpected data value; system failure; data missing.

4763 Provider error 4764 See clause 7.6.1 for the use of this parameter.

4765 4766 8.5.3.1

8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service

Definition

4767 This service is used between the VLR and the HLR or between the SGSN or HLR for reporting of authentication 4768 failures.

4769 8.5.3.2

Service primitives

4770 The service primitives are shown in table 8.5/3. 4771

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

4772

4773 8.5.3.3
4774 Invoke id

Parameter use

4775 See clause 7.6.1 for the use of this parameter. 4776 IMSI 4777 See clause 7.6.2 for the use of this parameter. 4778 Failure Cause 4779 See clause 7.6.7 for use of this parameter. 4780 4781 Re-attempt

526

3GPP

4782 See clause 7.6.7 for use of this parameter. 4783 Access Type 4784 See clause 7.6.7 for use of this parameter. 4785 Rand 4786 This parameter identifies the specific AV that failed authentication. 4787 See clause 7.6.7 for use of this parameter. 4788 VLR number 4789 Shall be present if the sender is VLR. See definition in clause 7.6.2. 4790 SGSN number 4791 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 4792 User error 4793 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 4794 values defined in clause 7.6.1: 4795 4796 4797

527 Release 7 528 529

133

3GPP TS 29.002 V7.5.0 (2006-09)

Unknown Subscriber; System Failure; Unexpected Data Value.

4798 Provider error 4799 These are defined in clause 7.6.

4800 4801 4802 8.6.1.1

8.6 Security management services

8.6.1 MAP_SET_CIPHERING_MODE service
Definitions

4803 This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is 4804 called when another service requires that information is to be sent on the radio path in encrypted form. 4805 The service is a non-confirmed service and consists of two service primitives.

4806 8.6.1.2

Service primitives

4807 The service primitives are shown in table 8.6/1. 4808

Table 8.6/1: MAP_SET_CIPHERING_MODE parameters

Parameter name Invoke id Ciphering mode Kc Request M M C Indication M(=) M(=) C(=)

4809

4810 8.6.1.3
4811 Invoke id

Parameter use

4812 See clause 7.6.1 for the use of this parameter.

530

3GPP

4813 Ciphering mode 4814 See clause 7.6.7 for the use of this parameter. 4815 Kc 4816 The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed.

531 Release 7 532 533

134

3GPP TS 29.002 V7.5.0 (2006-09)

4817 4818 4819 4820 8.7.1.1

8.7 International mobile equipment identities management services

8.7.1 MAP_CHECK_IMEI service
Definition

4821 This service is used between the VLR and the MSC and between the MSC and the EIR and between the SGSN and EIR 4822 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 4823 transferred to the EIR in the service request. 4824 This service may also be used to request the BMUEF from the EIR. 4825 The service is a confirmed service and consists of four service primitives.

4826 8.7.1.2

Service primitives

4827 The service primitives are shown in table 8.7/1. 4828

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

4829

4830 8.7.1.3
4831 Invoke id

Parameter use

4832 See clause 7.6.1 for the use of this parameter. 4833 Requested Equipment Info 4834 This parameter indicates whether Equipment Status or BMUEF or both is requested. 4835 IMEI 4836 4837 4838 4839

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.

4840 IMEISV 4841 See clause 7.6.2 for the use of this parameter. IMEISV shall be present if BMUEF is requested.

534

3GPP

4842 Equipment status 4843 See clause 7.6.3 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of 4844 the service if Equipment status was requested. 4845 BMUEF 4846 See clause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of 4847 the service if BMUEF was requested. 4848 User error 4849 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4850 the service, depending on the respective failure reason: 4851 4852 4853 4854

535 Release 7 536 537

135

3GPP TS 29.002 V7.5.0 (2006-09)

unknown equipment; this error is returned by the responder when the IMEI is not known in the EIR;

system failure; unexpected data value.

4855 Provider error 4856 See clause 7.6.1 for the use of this parameter.

4857 4858 8.7.2.1

8.7.2 MAP_OBTAIN_IMEI service

Definition

4859 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 4860 requested from the MS. 4861 The service is a confirmed service and consists of four service primitives.

4862 8.7.2.2

Service primitives

4863 The service primitives are shown in table 8.7/2. 4864

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

4865

4866 8.7.2.3
4867 Invoke id

Parameter use

4868 See clause 7.6.1 for the use of this parameter. 4869 IMEI 4870 See clause 7.6.2 for the use of this parameter. The parameter is included in the service response from the MSC to the 4871 VLR on successful outcome of the service.

538

3GPP

4872 User error

539 Release 7 540 541

136

3GPP TS 29.002 V7.5.0 (2006-09)

4873 If the service fails, the VLR sends the user error System Failure (see clause 7.6.1) to the MSC. 4874 Provider error 4875 See clause 7.6.1 for the use of this parameter.

4876 4877 4878 8.8.1.1

-

8.8 Subscriber management services

8.8.1 MAP-INSERT-SUBSCRIBER-DATA service
Definition

4879 This service is used by an HLR to update a VLR with certain subscriber data in the following occasions: 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889

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.

4890 Also this service is used by an HLR to update an SGSN with certain subscriber data in the following occasions: 4891 4892 4893 4894 4895 4896 4897

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.

4898 It is a confirmed service and consists of the primitives shown in table 8.8/1.

4899 8.8.1.2
4900

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

542

3GPP

543 Release 7 544 545

137 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 V7.5.0 (2006-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

4901

4902 8.8.1.3

Parameter use

4903 All parameters are described in clause 7.6. The following clarifications are applicable: 4904 Network access mode 4905 4906 4907 4908

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.

4909 IMSI 4910 It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by 4911 the VLR and the SGSN. 4912 MSISDN 4913 It is included either at location updating or when it is changed. The MSISDN sent shall be the basic MSISDN. This 4914 parameter is used by the VLR and the SGSN. 4915 Category 4916 It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN 4917 receives this parameter it shall ignore it. 4918 Subscriber Status 4919 It is included either at location updating or when it is changed. 4920 To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator 4921 Determined Barring. In this case ODB General Data shall also be present. If the Operator Determined Barring applies

546

3GPP

4922 and the subscriber is registered in the HPLMN and HPLMN specific Operator Determined Barring applies then ODB 4923 HPLMN Specific Data shall also be present. 4924 To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This 4925 parameter is used by the VLR and the SGSN. 4926 Bearer service List 4927 A list of Extensible Bearer service parameters (Extensible Bearer service is defined in clause 7.6). An Extensible Bearer 4928 service parameter must be the code for an individual Bearer service, except in the cases described below. 4929 4930 4931 4932

547 Release 7 548 549

138

3GPP TS 29.002 V7.5.0 (2006-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.

4933 If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location 4934 updating or at restoration) or only the ones added (at subscriber data modification). 4935 If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not 4936 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no 4937 error is sent back), except in the cases described below. 4938 4939 4940 4941 4942 4943 4944 4945

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.

4946 Teleservice List 4947 A list of Extensible Teleservice parameters (Extensible Teleservice is defined in clause 7.6). An Extensible Teleservice 4948 parameter must be the code for an individual Teleservice. 4949 If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating 4950 or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant 4951 to the node at which the message is received should be included in the Teleservice List. 4952 If the VLR or the SGSN receives an Indication containing any Extensible Teleservice parameters which it does not 4953 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Teleservices (no 4954 error is sent back). This parameter is used by the VLR and the SGSN. 4955 Forwarding information List 4956 A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in clause 7.6). It 4957 includes Call Forwarding services either at location updating or at restoration or when they are changed. Each 4958 Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive. 4959 The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary 4960 service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible 4961 Forwarding Feature is defined in clause 7.6). 4962 The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according 4963 to the rules in clause 8.8.1.4. 4964 The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter. 4965 4966 4967 4968

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

550

3GPP

4969 subaddress shall not be included. If the VLR does not receive a forwarded-to subaddress then it shall assume that a 4970 forwarded-to subaddress has not been registered. 4971 The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding 4972 unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding 4973 options shall be ignored by the VLR, and may be set to any value by the HLR. 4974 For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the 4975 Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply 4976 condition timer shall not be included. 4977 For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not 4978 contain a no reply condition timer. 4979 4980 4981 4982

551 Release 7 552 553

139

3GPP TS 29.002 V7.5.0 (2006-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.

4983 Call barring information List 4984 A list of Extensible Call barring information parameters (Extensible Call barring information is defined in clause 7.6). It 4985 includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible 4986 Call barring information parameter shall be treated independently of all other parameters in the primitive. 4987 The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. 4988 The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call 4989 Barring Feature is defined in clause 7.6). 4990 The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted 4991 according to the rules in clause 8.8.1.4. 4992 The Extensible Call Barring Feature shall contain an extensible SS-Status parameter. 4993 If the VLR or the SGSN receives an Indication containing any Extensible Call Barring service codes which it does not 4994 support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Extensible Call 4995 Barring service codes (no error is sent back). 4996 CUG information List 4997 A list of CUG information list parameters (CUG information is defined in clause 7.6). It includes CUG information 4998 either at location updating or at restoration or when it is changed. 4999 At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete 5000 CUG-SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If 5001 there are not options per extensible basic service group the CUG-FeatureList shall not be included. 5002 In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty 5003 CUG-SubscriptionList. 5004 When the VLR receives CUG data it shall replace the stored CUG data with the received data set. 5005 If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible 5006 basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no 5007 preferential CUG exists. 5008 If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies. 5009 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 5010 Unexpected Data Value. 5011 Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR. 5012 If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards 5013 the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this 5014 parameter it shall ignore it.

554

3GPP

5015 SS-Data List 5016 5017 5018 5019

555 Release 7 556 557

140

3GPP TS 29.002 V7.5.0 (2006-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.

5020 The Extensible SS-Data shall include the SS-Code for an individual supplementary service. 5021 The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are 5022 applicable to the service defined by the SS-Code. 5023 The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in clause 8.8.1.4. 5024 If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it 5025 returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received 5026 (no error is sent back). 5027 5028 5029 5030

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.

5031 Operator Determined Barring General data 5032 5033 5034 5035 5036 5037 5038 5039

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.

5040 Operator Determined Barring HPLMN data 5041 5042 5043 5044

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.

5045 If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data 5046 is present then the VLR or the SGSN shall not apply any HPLMN specific ODB services to the subscriber. This 5047 parameter is used by the VLR and the SGSN. 5048 eMLPP Subscription Data 5049 If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a 5050 call (as defined in clause 7.6). It contains both subparameters of eMLPP. 5051 If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and 5052 therefore discards the received information (no error is sent back). 5053 5054 5055 5056

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.

5057 MC Subscription Data 5058 If included in the Insert Subscriber Data request, this parameter provides the MC Subscription Data as defined in 5059 clause 7.6.

558

3GPP

5060 If the VLR does not support the MC service, it returns its code to the HLR in the parameter SS-Code List and therefore 5061 discards the received information (no error is sent back). 5062 5063 5064 5065

559 Release 7 560 561

141

3GPP TS 29.002 V7.5.0 (2006-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.

5066 Roaming Restriction Due To Unsupported Feature 5067 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 5068 supported by the MSC/VLR (e.g. Advice of Charge Charging Level). 5069 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 5070 the VLR and if the SGSN receives this parameter it shall ignore it. 5071 Regional Subscription Data 5072 5073 5074 5075 5076 5077

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.

5078 Regional subscription data that have been stored previously in a subscriber data record in the VLR or in the SGSN are 5079 completely replaced by the regional subscription data received in an Insert Subscriber Data indication during either an 5080 Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. 5081 After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are 5082 allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional 5083 Subscription Response. 5084 The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has 5085 been detected in one of the following cases: 5086 5087 5088 5089

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.

5090 Zone codes which have no mapping to location areas shall be ignored. 5091 If a sequence of MAP_INSERT_SUBSCRIBER_DATA services is used during a dialogue, Regional Subscription Data 5092 shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with 5093 the error Unexpected Data Value. 5094 If Regional Subscription Data are not included in any MAP_INSERT_SUBSCRIBER_DATA service, there is no 5095 restriction of roaming due to Regional Subscription. This parameter is used by the VLR and the SGSN. 5096 Voice Broadcast Data 5097 This parameter contains a list of group id's a user might have subscribed to; (VBS-Data is defined in clause 7.6). It 5098 includes VBS information either at location updating or at restoration or when it is changed. 5099 At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data. 5100 When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All 5101 subsequent VBS-data received within this dialogue shall be interpreted as add-on data. 5102 If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data.

562

3GPP

5103 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 5104 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 5105 it. 5106 Voice Group Call Data 5107 This parameter contains a list of group id's a user might have subscribed to; see clause 7.6. 5108 At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete 5109 VGCS-Data. 5110 When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. 5111 All VGCS-Data received within this dialogue shall be interpreted as add-on data. 5112 If VBCS-Data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VGCS-Data. 5113 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 5114 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 5115 it. 5116 North American Equal Access preferred Carrier Id List 5117 A list of the preferred carrier identity codes that are subscribed to. 5118 5119 5120 5121

563 Release 7 564 565

142

3GPP TS 29.002 V7.5.0 (2006-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.

5122 LSA Information 5123 5124 5125 5126 5127 5128 5129

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.

5130 At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA 5131 Information. 5132 When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data. 5133 When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access 5134 indicator. 5135 5136 5137 5138

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.

5139 If the entire LSA information is received, it shall always include the LSA only access indicator value together with the 5140 LSA data applicable for the PLMN (if any). 5141 If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously 5142 stored LSA Information. 5143 If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the 5144 error Unexpected Data Value. This parameter is used by the VLR and the SGSN. 5145 IST Alert Timer 5146 This parameter contains the IST Alert timer value that must be used to inform the HLR about the call activities that the 5147 subscriber performs.

566

3GPP

5148 At Location Updating, restoration, or when there is a change in the IST data defined for the Subscriber, the HLR shall 5149 include the IST Alert timer. 5150 LMU Identifier 5151 This parameter indicates the presence of an LMU. This parameter is used only by the VLR and shall be ignored if 5152 received by an SGSN. 5153 LCS Information 5154 This parameter provides the following LCS related information for an MS subscriber: 5155 5156 5157

567 Release 7 568 569

143

3GPP TS 29.002 V7.5.0 (2006-09)

list of GMLCs in the HPLMN; privacy exception list; MO-LR list.

5158 At restoration and location updating, the HLR shall include the complete LCS data of the subscriber. 5159 When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS 5160 data that is not modified need not be included. 5161 The VLR/SGSN shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data 5162 operation. 5163 If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the 5164 error Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the 5165 SS-Data List, then the VLR shall not interpret this as overlapping data. 5166 Super-Charger Supported In HLR 5167 This parameter is used by the HLR to indicate support for the Super-Charger functionality. If this parameter is present it 5168 shall include an indication of the age of the subscription data stored in the HLR. 5169 If this parameter is absent then the HLR does not support the Super-Charger functionality. 5170 SS-Code List 5171 5172 5173 5174 5175

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

5176 Regional Subscription Response 5177 If included in the response this parameter indicates one of: 5178 5179 5180 5181 5182

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.

5183 If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR 5184 shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted 5185 is not sent. The HLR shall check whether the current MSC area is no longer restricted. 5186 5187 5188 5189

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.

570

3GPP

5190 VLR CAMEL Subscription Info 5191 This parameter is sent for subscribers who have CAMEL services which are invoked in the MSC. 5192 5193 5194 5195 5196
-

571 Release 7 572 573

144

3GPP TS 29.002 V7.5.0 (2006-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.

5197
5198 5199

5200 The VLR CAMEL Subscription Info is sent at location updating or when any information in the applicable CAMEL 5201 Subscription Info in the HLR has been changed. 5202 At location updating, the complete set of VLR CAMEL Subscription Info is sent in one dialogue. 5203 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the VLR, then: 5204 5205 5206 5207

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.

5208 When the VLR receives a specific element of VLR CAMEL Subscription Info, it shall overwrite the corresponding 5209 specific element of VLR CAMEL Subscription Info (if any) which it has stored for that subscriber. 5210 For CAMEL Phase 1 and CAMEL Phase 2 , the VLR CAMEL Subscription Info consists of any one or more of: 5211 5212 5213 5214

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

5215 From CAMEL phase 3 onwards, the specific elements of VLR CAMEL Subscription Info which may be sent are:

5216
5217 5218 5219 5220 5221 5222 5223 5224

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

5225
5226

5227 If the VLR CAMEL Subscription Info is omitted in the Insert Subscriber Data operation the VLR shall keep the 5228 previously stored VLR CAMEL Subscription Info. Within one dialogue subsequent received data are interpreted as 5229 add-on data. If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the

574

3GPP

5230 error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall 5231 ignore it. 5232 The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag) for CAMEL Phase 2 and 5233 higher. See 3GPP TS 23.072 for the use of this parameter and the conditions for its presence. 5234 Supported CAMEL Phases 5235 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. This parameter is used 5236 by the VLR and SGSN. 5237 A VLR or SGSN not supporting any CAMEL Phase may omit this parameter. 5238 GPRS Subscription Data 5239 This parameter contains a list of PDP-contexts a user has subscribed to; see clause 7.6. 5240 At GPRS location updating the HLR shall include the complete GPRS Subscription Data. 5241 When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts. 5242 5243 5244 5245

575 Release 7 576 577

145

3GPP TS 29.002 V7.5.0 (2006-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.

5246 If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored 5247 GPRS Subscription Data. 5248 If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error 5249 Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 5250 it. 5251 SGSN CAMEL Subscription Info 5252 The SGSN CAMEL Subscription Info is sent at GPRS location updating or when any information in the applicable 5253 SGSN CAMEL Subscription Info in the HLR has been changed. 5254 5255 5256
-

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.

5257 At GPRS location updating the complete set of SGSN CAMEL Subscription Info is sent. 5258 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the SGSN, then 5259 one or more specific elements of SGSN CAMEL Subscription Info are sent in one dialogue. 5260 When the SGSN receives a specific element of SGSN CAMEL Subscription Info, it shall overwrite the corresponding 5261 specific element of SGSN CAMEL Subscription Info (if any) which it has stored for that subscriber. 5262 The specific elements of SGSN CAMEL Subscription Info which may be sent are: 5263 5264 5265 5266 5267 5268 5269 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.

578

3GPP

5270 Roaming Restricted In SGSN Due To Unsupported Feature 5271 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 5272 supported by the SGSN. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 5273 it. 5274 CS Allocation/Retention priority 5275 The CS Allocation/Retention priority is used only for Circuit Switched (CS). This parameter specifies relative 5276 importance to compare with other bearers about allocation and retention of bearer. This parameter is used only by the 5277 VLR and if the SGSN receives this parameter it shall ignore it. 5278 Offered CAMEL 4 CSIs 5279 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR or SGSN (see clause 7.6.3.36D). 5280 Subscribed Charging Characteristics 5281 This parameter refers to the Subscribed Charging Characteristics as defined in 3GPP TS 32.251. 5282 For a detailed description of the use of the parameter, see 3GPP TS 32.251. 5283 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 5284 Access Restriction Data 5285 This parameter indicates the allowed RAT according to subscription data. (see clause 7.6.3.96) 5286 If the VLR/SGSN supports the Access Restriction feature but does not receive the Access Restriction Data parameter 5287 from the HLR at location updating or restoration, the VLR/SGSN shall assume that the subscriber's profile does not 5288 have any restrictions enabled. 5289 For a detailed description of the use of the parameter, see 3GPP TS 23.012[23] for CS domain and 3GPP TS 5290 23.060[104] for PS domain. 5291 User error 5292 Only one of the following values is applicable: 5293 5294 5295

579 Release 7 580 581

146

3GPP TS 29.002 V7.5.0 (2006-09)

Unidentified subscriber; Data missing; Unexpected data value.

5296 8.8.1.4
5297 5298 5299 5300

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.

5301 The Basic Service Group (or Basic Service Group List) is optional. 5302 If present the Basic Service Group (or each element of the Basic Service Group List) shall be one of: 5303 5304 5305 5306 5307 5308 5309 5310

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.

582

3GPP

5311 If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic 5312 Service Groups. 5313 If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as 5314 applying individually to all the Elementary Basic Service Groups for which: 5315 5316

583 Release 7 584 585

147

3GPP TS 29.002 V7.5.0 (2006-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.

5317 The VLR and the SGSN are not required to store supplementary services data for Basic Service Groups which are not 5318 supported at the VLR or the SGSN respectively.

5319 5320 8.8.2.1

8.8.2 MAP-DELETE-SUBSCRIBER-DATA service

Definition

5321 This service is used by an HLR to remove certain subscriber data from a VLR or SGSN if the subscription of one or 5322 more supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or 5323 deactivation of supplementary services. 5324 This service is also used by an HLR to remove GPRS subscription data from an SGSN. 5325 It is a confirmed service and consists of the primitives shown in table 8.8/2.

5326 8.8.2.2
5327

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

5328

5329 8.8.2.3

Parameter use

5330 All parameters are described in clause 7.6. The following clarifications are applicable: 5331 Basic service List 5332 A list of Extensible Basic service parameters (Extensible Basic service is defined in clause 7.6). It is used when one, 5333 several or all basic services are to be withdrawn from the subscriber. If the VLR or the SGSN receives a value for an

586

3GPP

5334 Extensible Basic Service which it does not support, it shall ignore that value. This parameter is used by the VLR and by 5335 the SGSN. 5336 SS-Code List 5337 A list of SS-Code parameters (SS-Code is defined in clause 7.6). It is used when several or all supplementary services 5338 are to be withdrawn from the subscriber. 5339 There are three possible options: 5340 5341 5342 5343 5344 5345

587 Release 7 588 589

148

3GPP TS 29.002 V7.5.0 (2006-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.

5346 This parameter is used by the VLR and SGSN for Call Barring and LCS. Otherwise, this parameter is used only by the 5347 VLR and if the SGSN receives this parameter it shall ignore it. 5348 Roaming Restriction Due To Unsupported Feature 5349 This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This 5350 may occur if unsupported features or services are removed from the subscriber data in the HLR. 5351 If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is 5352 used only by the VLR and if the SGSN receives this parameter it shall ignore it. 5353 CAMEL Subscription Info Withdraw 5354 This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR or from the SGSN. All 5355 CAMEL Subscription Info for the subscriber shall be deleted. This parameter is used by the VLR and by the SGSN. 5356 This parameter should not be sent in the same message as the Specific CSI Withdraw parameter. 5357 Specific CSI Withdraw 5358 This parameter is used to indicate that one or more specific elements of CAMEL Subscription Info shall be deleted from 5359 the VLR or from the SGSN. 5360 The specific elements of CAMEL Subscription Info which may be withdrawn are: 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370

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.

590

3GPP

5371 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 5372 or higher. This parameter should not be sent in the same message as the CAMEL Subscription Info Withdraw 5373 parameter. 5374 Regional Subscription Identifier 5375 5376 5377 5378 5379

591 Release 7 592 593

149

3GPP TS 29.002 V7.5.0 (2006-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".

5380 The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the 5381 VLR or by the SGSN. 5382 Note that support of this parameter is a network operator option and it shall not be sent to networks which do not 5383 support Regional Subscription. 5384 If Regional Subscription is not supported by the VLR or by the SGSN, the request for deletion of Zone Codes is refused 5385 by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR. 5386 If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information 5387 shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR and by 5388 the SGSN. 5389 VBS Group Indication 5390 Contains an indication (flag) which is used if all Group Ids shall be deleted from the subscriber data for the Voice 5391 Broadcast teleservice. 5392 If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request 5393 for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN receives this 5394 parameter it shall ignore it. 5395 VGCS Group Indication 5396 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice 5397 Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 5398 it. 5399 If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the 5400 request for deletion of all Group Ids shall be ignored. 5401 GPRS Subscription Data Withdraw 5402 5403 5404 5405

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.

5406 Roaming Restricted In SGSN Due To Unsupported Feature 5407 This parameter is used if Roaming Restricted In SGSN Due To Unsupported Feature is deleted from the GPRS 5408 subscriber data. This may occur if unsupported features or services are removed from the GPRS subscriber data in the 5409 HLR. 5410 If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is 5411 used only by the SGSN and if the VLR receives this parameter it shall ignore it. 5412 LSA Information Withdraw 5413 5414 5415 5416

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.

594

3GPP

5417 IST Information Withdraw 5418 This parameter is used to indicate that the IST condition has been removed for the subscriber. See 3GPP TS 43.035 for 5419 the use of this parameter. 5420 Regional Subscription Response 5421 If included in the Delete Subscriber Data response this parameter indicates one of: 5422 5423 5424

595 Release 7 596 597

150

3GPP TS 29.002 V7.5.0 (2006-09)

MSC Area Restricted; SGSN Area Restricted; Regional Subscription Not Supported.

5425 This parameter is used by the VLR and by the SGSN. 5426 GMLC List Withdraw 5427 This parameter indicates that the subscriber's LCS GMLC List shall be deleted from the VLR or SGSN. 5428 Subscribed Charging Characteristics Withdraw 5429 This parameter indicates that the Subscribed Charging Characteristics shall be replaced with a local default value in the 5430 SGSN (see 3GPP TS 32.251). 5431 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 5432 User error 5433 Only one of the following values is applicable: 5434 5435 5436

Unidentified subscriber; Data missing; Unexpected data value.

5437 5438 5439 8.9.1.1

8.9 Identity management services

8.9.1 MAP-PROVIDE-IMSI service
Definition

5440 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 5441 identified itself with a TMSI not allocated to any subscriber in the VLR). 5442 It is a confirmed service and consists of the primitives shown in table 8.9/1.

5443 8.9.1.2
5444

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

5445

5446 8.9.1.3

Parameter use

5447 All parameters are described in clause 7.6. The following clarifications are applicable:

598

3GPP

5448 IMSI

599 Release 7 600 601

151

3GPP TS 29.002 V7.5.0 (2006-09)

5449 This parameter is received when the request is successfully carried out. It contains the requested IMSI. 5450 User error 5451 Only one of the following values is applicable: 5452

Absent subscriber.

5453 5454 8.9.2.1

8.9.2 MAP-FORWARD-NEW-TMSI service

Definition

5455 This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call 5456 set-up, location updating or supplementary services operation). 5457 It is a confirmed service and consists of the primitives shown in table 8.9/2.

5458 8.9.2.2
5459

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

5460

5461 8.9.2.3

Parameter use

5462 The parameter TMSI is described in clause 7.6.

5463 5464 5465 8.10.1.1

8.10 Fault recovery services

8.10.1 MAP_RESET service
Definition

5466 This service is used by the HLR, after a restart, to indicate to a list of VLRs or SGSNs that a failure occurred. 5467 The MAP_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1.

5468 8.10.1.2
5469

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

5470

5471 8.10.1.3
5472 Invoke Id

Parameter definition and use

5473 See definition in clause 7.6.1. 5474 HLR number

602

3GPP

5475 See definition in clause 7.6.2. 5476 HLR Id LIST 5477 5478 5479 5480

603 Release 7 604 605

152

3GPP TS 29.002 V7.5.0 (2006-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.

5481 5482 8.10.2.1

5483 5484 5485 5486 5487

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.

5488 The MAP_FORWARD_CHECK_SS_INDICATION service is a non-confirmed service using the service primitives 5489 defined in table 8.10/2.

5490 8.10.2.2
5491

Service primitives
Table 8.10/2: MAP_FORWARD_CHECK_SS_INDICATION
Parameter name Invoke Id Request M Indication M(=)

5492

5493 8.10.2.3
5494 Invoke Id

Parameter definition and use

5495 See definition in clause 7.6.1.

5496 5497 8.10.3.1

5498 5499 5500 5501

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.

5502 The MAP_RESTORE_DATA service is a confirmed service using the service primitives defined in table 8.10/3.

5503 8.10.3.2
5504

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

606

3GPP

607 Release 7 608 609

153 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 V7.5.0 (2006-09)

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

5505

5506 8.10.3.3
5507 Invoke Id

Parameter definitions and use

5508 See definition in clause 7.6.1. 5509 IMSI 5510 See definition in clause 7.6.2. 5511 LMSI 5512 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 5513 to support the LMSI handling procedures. 5514 Supported CAMEL Phases 5515 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 5516 phase 1 is supported. Otherwise may be absent. 5517 SoLSA Support Indicator 5518 This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If 5519 this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling. 5520 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 5521 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 5522 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 5523 IST Support Indicator 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534

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.

5535 Long FTN Supported 5536 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 5537 Super-Charger Supported in Serving Network Entity 5538 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 5539 that subscriber data is required. 5540 If this parameter is absent then the VLR does not support the Super-Charger functionality. 5541 Supported LCS Capability Sets

610

3GPP

5542 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 5543 capability set is marked as supported then the VLR does not support LCS at all. 5544 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 5545 version. 5546 Offered CAMEL 4 CSIs 5547 This parameter indicates the CAMEL phase 4 CSIs offered in the VMSC/VLR (see clause 7.6.3.36D). 5548 HLR number 5549 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful outcome of the service. 5550 MS Not Reachable Flag 5551 See definition in clause 7.6.8. This parameter shall be present in case of successful outcome of the service, if the "MS 5552 Not Reachable flag" was set in the HLR. 5553 User error 5554 In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes 5555 defined in clause 7.6.1 may be used, depending on the nature of the fault: 5556 5557 5558 5559

611 Release 7 612 613

154

3GPP TS 29.002 V7.5.0 (2006-09)

unknown subscriber; system failure; unexpected data value; data missing.

5560 Provider error 5561 For definition of provider errors see clause 7.6.1.

5562 5563 5564 8.11.1.1

8.11 Subscriber Information services

8.11.1 MAP-ANY-TIME-INTERROGATION service
Definition

5565 This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR or the 5566 GMLC at any time. This service may also be used by the gsmSCF to request the Mobile Number Portability (MNP) 5567 information from the NPLR. 5568 This service is also used by the Presence Network Agent to request information, (e.g. subscriber state and location) 5569 about the subscriber (associated with a presentity) from the HLR at any time (see 3GPP TS 23.141 [128]). 5570 When this service is used to the HLR, the subscriber state or location may be requested. 5571 When this service is used to the GMLC, only the location may be requested. 5572 When this service is used to the NPLR, only the MNP information may be requested. 5573 The MAP-ANY-TIME-INTERROGATION service is a confirmed service using the service primitives defined in 5574 table 8.11/1.

5575 8.11.1.2
5576

Service primitives
Table 8.11/1: Any_Time_Interrogation
Parameter name Request Indication Response Confirm

614

3GPP

615 Release 7 616 617

155 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 V7.5.0 (2006-09) M(=)

C C C C C C C C C

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

5577

5578 8.11.1.3

Parameter definition and use

5579 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are 5580 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98]. 5581 The HLR or GMLC may be able to use the value of the parameter gsmSCF-address to screen a 5582 MAP_Any_Time_Interrogation indication. 5583 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5584 User error 5585 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5586 5587 5588 5589 5590

System Failure; Any Time Interrogation Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber.

5591 Provider error 5592 These are defined in clause 7.6.1.

5593 5594 8.11.2.1

8.11.2 MAP-PROVIDE-SUBSCRIBER-INFO service

Definition

5595 This service is used to request information (e.g. subscriber state and location) from the VLR or SGSN at any time. 5596 The MAP-PROVIDE-SUBSCRIBER-INFO service is a confirmed service using the primitives defined in table 8.11/2.

618

3GPP

5597 8.11.2.2
5598

619 Release 7 620 621

156

3GPP TS 29.002 V7.5.0 (2006-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

5599

5600 8.11.2.3

Parameter definition and use

5601 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 5602 specified in 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98]. 5603 User error 5604 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5605 5606

Data Missing; Unexpected Data Value.

5607 Provider error 5608 These are defined in clause 7.6.1.

5609 5610 8.11.3.1

8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service

Definition

5611 This service is used by the gsmSCF, to request subscription information (e.g. call forwarding supplementary service 5612 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 5613 gsmSCF for this service. 5614

5615 8.11.3.2
5616

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

622

3GPP

623 Release 7 624 625

157 Supported CAMEL phases in VLR Supported CAMEL phases in SGSN Offered CAMEL 4 CSIs in VLR Offered CAMEL 4 CSIs in SGSN MSISDN-BS-List User error Provider error

3GPP TS 29.002 V7.5.0 (2006-09) C C C C C C C(=) C(=) C(=) C(=) C(=) C(=) O

5617

5618 8.11.3.3

Parameter definition and use

5619 All parameters are described in clause 7.6. 5620 The HLR may be able to use the value of the parameter gsmSCF-address to screen a 5621 MAP_Any_Time_Subscription_Interrogation indication. The gsmSCF-address shall contain the IM-SSF address when 5622 the IM-SSF takes the role of the gsmSCF. 5623 5624 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078 and 3GPP TS 5625 23.278. 5626 User error 5627 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637

Unexpected Data Value; Unknown Subscriber; BearerServiceNotProvisioned; TeleserviceNotProvisioned; CallBarred; IllegalSS-Operation; SS-NotAvailable; InformationNotAvailable; Any Time Subscription Interrogation Not Allowed; Data Missing.

5638 Provider error 5639 These are defined in clause 7.6.1.

5640 5641 8.11.4.1

8.11.4 MAP-ANY-TIME-MODIFICATION service

Definition

5642 This service is used by the gsmSCF, to modify information of the HLR at any time. 5643 This service is also used by the Presence Network Agent to activate or deactivate reporting of mobility management 5644 events (associated with a presentity) from the VLR or SGSN (see 3GPP TS 23.141 [128]).

5645 8.11.4.2
5646

Service primitives
Table 8.11/4: Any_Time_Modification
Parameter name Request Indication Response Confirm

626

3GPP

627 Release 7 628 629 Invoke id 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

158 M M C C C C C C M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V7.5.0 (2006-09) M(=) M(=)

C C C C C

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

5647

5648 8.11.4.3

Parameter definition and use

5649 All parameters are described in clause 7.6. 5650 The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Modification 5651 indication. 5652 The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.078 and 3GPP TS 5653 23.278. 5654 User error 5655 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669

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.

5670 Provider error 5671 These are defined in clause 7.6.1.

5672 8.11.5.1

8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service

Definition

630

3GPP

631 Release 7 632 633

159

3GPP TS 29.002 V7.5.0 (2006-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.
5673 All Information Sent 5674 This parameter is set when the HLR has sent all information to gsmSCF.

User error

634

3GPP

635 Release 7 636 637

160

3GPP TS 29.002 V7.5.0 (2006-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.

5675 5676 5677

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.

5678 5679 5680

9 Operation and maintenance services

9.1 Subscriber tracing services
9.1.1 MAP-ACTIVATE-TRACE-MODE service
Definition

5681 9.1.1.1

5682 This service is used between the HLR and the VLR to activate subscriber tracing in the VLR. 5683 Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN. 5684 The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1.

5685 9.1.1.2
5686

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

5687

5688 9.1.1.3
5689 Invoke id

Parameter use

5690 See definition in clause 7.6.1. 5691 IMSI 5692 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation.

638

3GPP

5693 Trace reference 5694 See definition in clause 7.6.10. This parameter contains trace reference for GSM only tracing request. 5695 Trace type 5696 See definition in clause 7.6.10. This parameter contains trace type for GSM only tracing request. 5697 OMC Id 5698 See definition in clause 7.6.2. The use of this parameter is an operator option. 5699 Trace reference 2 5700 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5701 Trace depth list 5702 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5703 Trace NE type list 5704 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5705 Trace interface list 5706 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5707 Trace event list 5708 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5709 Trace support indicator 5710 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5711 User error 5712 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5713 5714 5715 5716 5717 5718

639 Release 7 640 641

161

3GPP TS 29.002 V7.5.0 (2006-09)

Unidentified Subscriber; Facility Not Supported; Tracing Buffer Full; System Failure; Unexpected Data Value; Data missing.

5719 Provider error 5720 For definition of provider errors see clause 7.6.1.

5721 5722 9.1.2.1

9.1.2 MAP-DEACTIVATE-TRACE-MODE service

Definition

5723 This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR. 5724 Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN. 5725 The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2.

642

3GPP

5726 9.1.2.2
5727

643 Release 7 644 645

162

3GPP TS 29.002 V7.5.0 (2006-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

5728

5729 9.1.2.3
5730 Invoke id

Parameter use

5731 See definition in clause 7.6.1. 5732 IMSI 5733 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 5734 Trace reference 5735 See definition in clause 7.6.10. 5736 Trace reference 2 5737 See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation. 5738 User error 5739 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5740 5741 5742 5743 5744

Unidentified Subscriber; Facility Not Supported; System Failure; Unexpected Data Value; Data missing.

5745 Provider error 5746 For definition of provider errors see clause 7.6.1.

5747 5748 9.1.3.1

9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service

Definition

5749 This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC. 5750 The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3.

5751 9.1.3.2
5752

Service primitives
Table 9.1/3: MAP-TRACE-SUBSCRIBER-ACTIVITY
Parameter name Invoke id IMSI Request M C Indication M(=) C(=)

646

3GPP

647 Release 7 648 649

163 Trace reference Trace type OMC Id M M U M(=) M(=) C(=)

3GPP TS 29.002 V7.5.0 (2006-09)

5753

5754 9.1.3.3
5755 Invoke id

Parameter use

5756 See definition in clause 7.6.1. 5757 IMSI 5758 See definition in clause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC. 5759 Trace reference 5760 See definition in clause 7.6.10. 5761 Trace type 5762 See definition in clause 7.6.10. 5763 OMC Id 5764 See definition in clause 7.6.2. The use of this parameter is an operator option.

5765 5766 5767 9.2.1.1

9.2 Other operation and maintenance services

9.2.1 MAP-SEND-IMSI service
Definition

5768 This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance 5769 procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber's identity known. 5770 It is a confirmed service and consists of the primitives shown in table 9.2/1.

5771 9.2.1.2
5772

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

5773

5774 9.2.1.3
5776 User error

Parameter use

5775 All parameters are described in clause 7.6. The following clarifications are applicable.

5777 Only one of the following values is applicable: 5778 5779

Unknown subscriber; Unexpected data value;

650

3GPP

5780

651 Release 7 652 653

164

3GPP TS 29.002 V7.5.0 (2006-09)

Data missing.

5781 5782 5783

10

Call handling services

10.1 MAP_SEND_ROUTING_INFORMATION service
10.1.1 Definition

5784 This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform 5785 the interrogation of the HLR in order to route a call towards the called MS. 5786 This is a confirmed service using the primitives listed in table 10.1/1. 5787 This service is also used between the GMSC and the NPLR and between the gsmSCF and the HLR.

5788
5789

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

654

3GPP

655 Release 7 656 657

165 Request Indication

3GPP TS 29.002 V7.5.0 (2006-09) Response C U C C C U C C C C C C C C U Confirm C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O C (=)

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 GSM Bearer Capability

5790

5791

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.

5792 See clause 7.6 for a definition of the parameters used in addition to the following. Note that: 5793 5794 5795 5796 5797 5798

5799 Interrogation Type 5800 See 3GPP TS 23.079 [99] for the use of this parameter. 5801 GMSC or gsmSCF address 5802 The E.164 address of the GMSC or the gsmSCF. This parameter contains the gsmSCF address if the gsmSCF iniated 5803 call parameter is present, otherwise it is the GMSC address. 5804 MSISDN 5805 This is the Mobile Subscriber ISDN number assigned to the called subscriber. In the Request & Indication it is the 5806 number received by the GMSC in the ISUP IAM. If the call is to be forwarded and the HLR supports determination of 5807 the redirecting number, the HLR inserts the basic MSISDN in the Response. 5808 See 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence in the response. 5809 OR Interrogation 5810 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5811 OR Capability 5812 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5813 CUG Interlock 5814 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5815 CUG Outgoing Access 5816 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5817 Number of Forwarding

658

3GPP

5818 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5819 Network Signal Info 5820 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 5821 Supported CAMEL Phases 5822 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5823 T-CSI Suppression 5824 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5825 Offered CAMEL 4 CSIs 5826 This parameter indicates the CAMEL phase 4 CSIs offered in the GMSC/VLR (see clause 7.6.3.36D). 5827 5828 Suppression Of Announcement 5829 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5830 Call Reference Number 5831 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5832 [99]. 5833 Forwarding Reason 5834 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5835 Basic Service Group 5836 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5837 Basic Service Group 2 5838 See 3GPP TS 23.079[99] for the use of this parameter and the conditions for its presence. 5839 Alerting Pattern 5840 See 3GPP TS 23.018 [97] and 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5841 CCBS Call 5842 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5843 Supported CCBS Phase 5844 This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported. 5845 Additional Signal Info 5846 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 5847 IST Support Indicator 5848 5849 5850 5851 5852 5853

659 Release 7 660 661

166

3GPP TS 29.002 V7.5.0 (2006-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.

662

3GPP

5854 5855 5856 5857 5858 5859

663 Release 7 664 665

167

3GPP TS 29.002 V7.5.0 (2006-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.

5860 Pre-paging supported 5861 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 5862 Call Diversion Treatment Indicator 5863 This parameter indicates whether or not call diversion is allowed. 5864 Network Signal Info 2 5865 See 3GPP TS 23.172 [126] for the conditions for the presence of the components of this parameter. 5866 IMSI 5867 See 3GPP TS 23.018 [97] and 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence. 5868 MSRN 5869 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 5870 conditions for its presence. If the NPLR returns only the MSISDN-number without Routeing Number to the GMSC, the 5871 MSISDN-number shall be returned as MSRN. 5872 Forwarding Data 5873 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding 5874 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See 5875 3GPP TS 23.018 [97] and 3GPP TS 23.079 [99] for the conditions for the presence of its components. 5876 Forwarding Interrogation Required 5877 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5878 Long FTN Supported 5879 This parameter indicates that the GMSC supports Long Forwarded-to Numbers. 5880 Suppress VT-CSI 5881 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5882 Suppress Incoming Call Barring 5883 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5884 gsmSCF Initiated Call 5885 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5886 VMSC address 5887 See 3GPP TS 23.079 [99] and 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5888 In addition this parameter shall be present if the ReleaseResourcesSupported parameter is present. 5889 Release Resources Supported 5890 This parameter indicates by its presence that the MAP_RELEASE_RESOURCES service is supported at the VMSC. It 5891 shall be present if so indicated by the VMSC with MAP_PROVIDE_ROAMING_NUMBER confirm. 5892 GMSC CAMEL Subscription Info

666

3GPP

5893 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5894 Location Information 5895 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5896 Subscriber State 5897 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5898 CUG Subscription Flag 5899 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5900 North American Equal Access preferred Carrier Id 5901 This parameter is returned to indicate the preferred carrier identity to be used to set-up the call (i.e. forwarding the call 5902 or establishing the roaming leg). 5903 SS-List 5904 5905 5906 5907

667 Release 7 668 669

168

3GPP TS 29.002 V7.5.0 (2006-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.

5908 Basic Service Code 5909 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5910 5911 5912 5913 5914

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.

5915 CCBS Target 5916 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5917 Keep CCBS Call Indicator 5918 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5919 IST Alert Timer 5920 It includes the IST Alert timer value that must be used to inform the HLR about the call activities that the subscriber 5921 performs. This parameter is only sent to the GMSC in response to a Send Routing Information request which indicates 5922 the the GMSC supports IST. 5923 Number Portability Status 5924 This parameter indicates the number portability status of the subscriber. This parameter may be present if the sender of 5925 SRIack is NPLR. 5926 Supported CAMEL Phases in VMSC 5927 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5928 Offered CAMEL 4 CSIs in VMSC 5929 This parameter is defined in clause 7.6.3.36F. 5930 MSRN 2 5931 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126].

670

3GPP

5932 Forwarding Data 2 5933 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5934 SS-List 2 5935 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5936 Basic Service Code 2 5937 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5938 Allowed Services 5939 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5940 Unavailability Cause 5941 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.172 [126]. 5942 User error 5943 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970

671 Release 7 672 673

169

3GPP TS 29.002 V7.5.0 (2006-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;

674

3GPP

5971 5972 5973

675 Release 7 676 677

170

3GPP TS 29.002 V7.5.0 (2006-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;

5974 5975 5976 5977

Forwarding Violation; System Failure; Data Missing; Unexpected Data Value.

5978 See clause 7.6 for a definition of these errors. 5979 Provider error 5980 These are defined in clause 7.6. 5981 GSM Bearer Capability 5982 This information is passed according to the rules specified in 3GPP TS 29.007 [56]. There may be two GSM Bearer 5983 Capabilities supplied.

5984 5985

10.2 MAP_PROVIDE_ROAMING_NUMBER service

10.2.1 Definition

5986 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a 5987 roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. 5988 This is a confirmed service which uses the primitives described in table 10.2/1.

5989
5990

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 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(=) Response M(=) Confirm M(=)

678

3GPP

679 Release 7 680 681

171 Request Indication

3GPP TS 29.002 V7.5.0 (2006-09) Response Confirm O

Parameter name Provider error

5991

5992

10.2.3 Parameter use

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.

5993 See clause 7.6 for a definition of the parameters used, in addition to the following. Note that: 5994 5995 5996 5997 5998 5999

6000 IMSI 6001 This is the IMSI of the called Subscriber. 6002 MSC Number 6003 This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the 6004 HLR as provided at location updating. 6005 MSISDN 6006 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6007 LMSI 6008 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6009 GSM Bearer Capability 6010 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6011 This information is passed according to the rules specified in TS 3GPP TS 29.007 [56]. 6012 There may be two GSM Bearer Capabilities supplied. 6013 Network Signal Info 6014 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 6015 Suppression Of Announcement 6016 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078 [98]. 6017 Call Reference Number 6018 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 6019 [99]. 6020 GMSC Address 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 OR Interrogation 6024 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6025 OR Not Supported in GMSC 6026 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence.

682

3GPP

6027 Supported CAMEL Phases in interrogating node 6028 This parameter is defined in clause 7.6.3.36I.Alerting Pattern 6029 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 6030 CCBS Call 6031 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6032 Additional Signal Info 6033 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 6034 Pre-paging supported 6035 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 6036 Long FTN supported 6037 See 3GPP TS 23.082 for the use of this parameter and the conditions for its presence. 6038 Suppress VT-CSI 6039 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 6040 Offered CAMEL 4 CSIs in interrogating node 6041 This parameter is defined in clause 7.6.3.36E. 6042 Roaming Number 6043 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 6044 ReleaseResourcesSupported 6045 This parameter indicates by its presence that the MAP_RELEASE_RESOURCES service is supported at the VMSC. 6046 User error 6047 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057

683 Release 7 684 685

172

3GPP TS 29.002 V7.5.0 (2006-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.

6058 See clause 7.6 for a definition of these reasons. 6059 Provider error 6060 These are defined in clause 7.6.

686

3GPP

687 Release 7 688 689

173

3GPP TS 29.002 V7.5.0 (2006-09)

6061 6062

10.3 MAP_RESUME_CALL_HANDLING service

10.3.1 Definition

6063 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC 6064 to request the GMSC to resume handling the call and forward it to the specified destination. 6065 This is a confirmed service which uses the Primitives listed in table 10.3/1.

6066
6067

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

6068

6069

10.3.3 Parameter use

6070 Information received in subsequent segment of a segmented dialogue shall not overwrite information received in an 6071 earlier segment. 6072 See clause 7.6 for a definition of the parameters used, in addition to the following. 6073 Call Reference Number 6074 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in the first segment of the 6075 dialogue. 6076 Basic Service Group 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 2 6080 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 6081 dialogue. 6082 IMSI 6083 This is the IMSI of the forwarding Subscriber. This parameter shall be present in the first segment of the dialogue. 6084 Forwarding Data 6085 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding 6086 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See

690

3GPP

6087 3GPP TS 23.079 [99] for the conditions for the presence of its components. This parameter shall be present in a first 6088 segment of the dialogue. 6089 CUG Interlock 6090 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6091 CUG Outgoing Access 6092 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 6093 O-CSI 6094 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 6095 For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data. 6096 D-CSI 6097 The Dialled Services-CSI. 6098 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 6099 CCBS Target 6100 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6101 UU Data 6102 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 6103 UUS CF Interaction 6104 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 6105 All Information Sent 6106 This parameter is set when the VMSC has sent all information to GMSC. 6107 MSISDN 6108 This parameter is the basic MSISDN of the forwarding subscriber. It shall be present if the VMSC supports 6109 determination of the redirecting number. 6110 User error 6111 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6112 6113 6114 6115

691 Release 7 692 693

174

3GPP TS 29.002 V7.5.0 (2006-09)

Optimal Routeing not allowed; Forwarding failed; Unexpected Data Value; Data Missing.

6116 Provider error 6117 These are defined in clause 7.6.

6118 6119

10.4 MAP_PREPARE_GROUP_CALL service

10.4.1 Definition

6120 This service is used by the Anchor_MSC to inform the Relay_MSC about a group call set-up.

694

3GPP

6121 The MAP_PREPARE_GROUP_CALL service is a confirmed service using the service primitives given in table 10.4/1.

695 Release 7 696 697

175

3GPP TS 29.002 V7.5.0 (2006-09)

6122
6123

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

6124

6125
6126 Invoke Id

10.4.3 Parameter definitions and use

6127 See definition in clause 7.6.1. 6128 Teleservice 6129 Voice Broadcast Service or Voice Group Call Service. 6130 ASCI Call Reference 6131 Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the 6132 Relay_MSC. 6133 Ciphering Algorithm 6134 The ciphering algorithm to be used for the group call. 6135 Group Key Number VK-Id 6136 This Group Key Number has to be broadcast and is used by the mobile station to derive the key for ciphering on the 6137 radio interface (see 3GPP TS 43.020 [24]). Values 2 to 15 are reserved for future use. 6138 Shall be present if the ciphering applies. 6139 VSTK 6140 The VGCS/VBS Short Term Key is used to derive the key for ciphering on the radio interface (see 3GPP TS 43.020 6141 [24]). 6142 Shall be present if the ciphering applies. 6143 VSTK-RAND 6144 This random number has to be broadcast and is used by the mobile station to derive the group key for ciphering on the 6145 radio interface (see 3GPP TS 43.020 [24]). 6146 Shall be present if the ciphering applies. 6147 Priority 6148 Default priority level related to the call if eMLPP applies.

698

3GPP

6149 CODEC-Information 6150 Information on the codecs allowed for this call. 6151 Uplink Free Indicator 6152 A flag indicating whether the call is initiated from a dispatcher. 6153 Group Call Number 6154 This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC. 6155 User Error 6156 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on 6157 the nature of the fault: 6158 6159 6160

699 Release 7 700 701

176

3GPP TS 29.002 V7.5.0 (2006-09)

No Group Call Number available; System Failure; Unexpected Data Value.

6161 Provider Error 6162 See definition of provider error in clause 7.6.1.

6163 6164 6165

10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service

10.5.1 Definitions

6166 This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications. 6167 The MAP_PROCESS_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives 6168 given in table 10.5/1.

6169
6170

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 Talker Priority Additional Info Emergency Mode Reset Command Flag Request M C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=)

6171

6172
6173 Invoke Id

10.5.3 Parameter definitions and use

6174 See definition in clause 7.6.1 6175 Uplink Request 6176 This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests 6177 access to the uplink.

702

3GPP

6178 Uplink Release Indication 6179 This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free. 6180 Release Group Call 6181 This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who 6182 has initiated the call and who currently has access to the uplink terminates the call. 6183 Talker Priority 6184 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6185 Additional Info 6186 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6187 Emergency Mode Reset Command Flag 6188 For the definition and use of this parameter see 3GPP TS 43.068 [100]

703 Release 7 704 705

177

3GPP TS 29.002 V7.5.0 (2006-09)

6189 6190 6191

10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service

10.6.1 Definitions

6192 This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications. 6193 The MAP_FORWARD_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service 6194 primitives given in table 10.6/1.

6195
6196

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 Talker Priority Additional Info Emergency Mode Reset Command Flag SM RP UI 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(=)

6197

6198
6199 IMSI

10.6.3 Parameter definitions and use

6200 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 6201 Invoke Id 6202 See definition in clause 7.6.1.

706

3GPP

6203 Uplink Request Acknowledgement 6204 This information element is used for positive acknowledgement of an uplink request. 6205 Uplink Release Indication 6206 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free. 6207 Uplink Reject Command 6208 This information element is used for negative acknowledgement of an uplink request. 6209 Uplink Seized Command 6210 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free. 6211 Uplink Release Command 6212 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted 6213 to a MS in the relay MSC area shall be released. 6214 State Attributes 6215 This information element is used to allow service logic running in an Anchor MSC to mute a VGCS talker even when 6216 the talker is served on a Relay MSC. The IE is used to build a GCC message that provides a mechanism to induce the 6217 VGCS talker terminal to mute/unmute the downlink at the Anchor MSC, as defined in 3GPP TS 44.068. 6218 Talker Priority 6219 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6220 Additional Info 6221 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6222 Emergency Mode Reset Command Flag 6223 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6224 SM RP UI 6225 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 6226 in this parameter. 6227

707 Release 7 708 709

178

3GPP TS 29.002 V7.5.0 (2006-09)

6228 6229
6230 6231 6232 6233 6234 6235 6236 6237

10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service

10.7.1 Definitions
This service is used between the Relay MSC and the Anchor MSC. When the VGCS/ VBS calling service subscriber is in the Relay MSC area the MAP_SEND_GROUP_CALL_END_SIGNAL indicates that at least the downlink channel in the originating cell is established. For all other VGCS/ VBS call set-up scenarios (i.e. calling service subscriber in Anchor MSC area, calling service subscriber in other Relay MSC area, dispatcher originated call) the MAP_SEND_GROUP_CALL_END_SIGNAL indicates that at least the downlink channel in any one cell within the VGCS/ VBS call area in the Relay MSC is established. The response is used by the Anchor MSC to inform the Relay MSC that all resources for the call can be released in the Relay MSC because the call has been released in the Anchor MSC.

6238 The MAP_SEND_GROUP_CALL_END_SIGNAL service is a confirmed service using the service primitives given in 6239 table 10.7/1.

6240

10.7.2 Service primitives

710

3GPP

6241

711 Release 7 712 713

179

3GPP TS 29.002 V7.5.0 (2006-09)

Table 10.7/1: MAP_SEND_GROUP_CALL_END_SIGNAL service

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

Parameter name Invoke Id IMSI Talker Priority Additional Info Provider Error

6242

6243
6244 Invoke Id

10.7.3 Parameter definitions and use

6245 See definition in clause 7.6.1 6246 IMSI 6247 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 6248 Shall be present if the call was established by a service subscriber roaming in the relay MSC area. 6249 Talker Priority 6250 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6251 Additional Info 6252 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6253 Provider Error 6254 See definition of provider error in clause 7.6.1.

6255 6256

10.7AMAP_SEND_GROUP_CALL_INFO service
10.7A.1 Definitions

6257 This service is used in a RANflex configuration (see 3GPP TS 23.236 [133]) between the subscriber's visited MSC and 6258 group call serving MSC of the subscriber's location area. 6259 The MAP_SEND_GROUP_CALL_INFO service is a confirmed service using the service primitives given in table 6260 10.7A/1.

6261
6262

10.7A.2 Service primitives

Table 10.7A/1: MAP_SEND_GROUP_CALL_INFO service
Parameter name Invoke Id Requested Info Cell Id Group Id IMSI Talker Priority Additional Info TMSI CKSN Anchor MSC Address ASCI Call Reference Additional Subscriptions Kc Request M M C M C C C C C Indication M(=) M(=) C(=) M(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C C C C C

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

714

3GPP

715 Release 7 716 717 User Error Provider Error

180 C

3GPP TS 29.002 V7.5.0 (2006-09) C(=) O

6263

6264
6265 Invoke Id

10.7A.3 Parameter definitions and use

6266 See definition in clause 7.6.1 6267 Requested Info 6268 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6269 Cell Id 6270 Identity of the initiating service subscriber's current cell. 6271 Group Id 6272 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6273 IMSI 6274 If sent in the request: Identity of the service subscriber who has established the call and who is allowed to terminate the 6275 call. 6276 If sent in the response: Identity of the uplink requesting service subscriber. 6277 Talker Priority 6278 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6279 Additional Info 6280 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6281 TMSI 6282 See definition in clause 7.6.2. 6283 CKSN 6284 See clause 7.6.7 for the use of this parameter. 6285 Anchor MSC Address 6286 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6287 ASCI Call Reference 6288 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6289 Additional Subscriptions 6290 For the definition and use of this parameter see 3GPP TS 43.068 [100] 6291 Kc 6292 See clause 7.6.7 for the use of this parameter. 6293 User Error 6294 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on 6295 the nature of the fault: 6296

System Failure;

718

3GPP

6297 6298 6299

719 Release 7 720 721

181

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected Data Value; Data Missing TeleserviceNotProvisioned; Unknown Subscriber; Ongoing Call.

6300 6301

6302 Provider Error 6303 See definition of provider error in clause 7.6.1.

6304 6305 6306 6307

10.8 Void 10.9 Void 10.10 MAP_SET_REPORTING_STATE service

10.10.1 Definition

6308 This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed 6309 service using the service primitives shown in table 10.10/1.

6310
6311

10.10.2 Service primitives

Table 10.10/1: MAP_SET_REPORTING_STATE parameters
Parameter name Invoke id IMSI LMSI CCBS Monitoring CCBS Subscriber Status User error Provider error Request M C C C Indication M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

6312

6313

10.10.3 Parameter use

6314 See clause 7.6 for a definition of the parameters used, in addition to the following. 6315 IMSI 6316 The IMSI is a mandatory parameter if the service is used as the only one in a dialogue. 6317 CCBS Monitoring 6318 This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall 6319 be started this service corresponds to the message 'Start Reporting' in 3GPP TS 23.093 [107]; if it indicates that 6320 monitoring shall be stopped this service corresponds to the message 'Stop Reporting' in 3GPP TS 23.093 [107]. 6321 CCBS Subscriber Status 6322 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6323 User error

722

3GPP

6324 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6325 values defined in clause 7.6.1: 6326 6327 6328 6329 6330 6331 6332

723 Release 7 724 725

182

3GPP TS 29.002 V7.5.0 (2006-09)

System Failure; Unidentified Subscriber; Unexpected Data Value; Data Missing; Resource Limitation; Facility Not Supported. This error is reserved for future use.

NOTE:

6333 Provider error 6334 These are defined in clause 7.6.

6335 6336

10.11 MAP_STATUS_REPORT service

10.11.1 Definition

6337 This service is used by the VLR to report an event or call outcome to the HLR. It is a confirmed service using the 6338 service primitives shown in table 10.11/1.

6339
6340

10.11.2 Service primitives

Table 10.11/1: MAP_STATUS_REPORT parameters
Parameter name Invoke id IMSI CCBS Subscriber Status Monitoring Mode Call Outcome User error Provider error Request M M C C C Indication M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C(=) O

6341

6342

10.11.3 Parameter use

6343 See clause 7.6 for a definition of the parameters used, in addition to the following. 6344 CCBS Subscriber Status 6345 If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message 'Event 6346 Report' in 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its 6347 presence. 6348 Monitoring Mode 6349 If this parameter is present with CCBS Call Outcome this service corresponds to the message 'CCBS Call Report' in 6350 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6351 Call Outcome 6352 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6353 User error

726

3GPP

6354 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6355 values defined in clause 7.6.1: 6356 6357 6358 6359

727 Release 7 728 729

183

3GPP TS 29.002 V7.5.0 (2006-09)

Unknown Subscriber; System Failure; Unexpected Data Value; Data Missing.

6360 Provider error 6361 These are defined in clause 7.6.

6362 6363

10.12 MAP_REMOTE_USER_FREE service

10.12.1 Definition

6364 This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber 6365 can be notified. It is a confirmed service using the service primitives shown in table 10.12/1.

6366
6367

10.12.2 Service primitives

Table 10.12/1: MAP_REMOTE_USER_FREE parameters
Parameter name Invoke id IMSI Call Info CCBS Feature Translated B Number Replace B Number Alerting Pattern RUF Outcome User error Provider error Request M M M M M C C Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=) O

6368

6369

10.12.3 Parameter use

6370 See clause 7.6 for a definition of the parameters used, in addition to the following. 6371 Call Info 6372 See 3GPP TS 23.093 [107] for the use of this parameter. 6373 CCBS Feature 6374 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 6375 Translated B Number 6376 See 3GPP TS 23.093 [107] for the use of this parameter. 6377 Replace B Number 6378 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6379 Alerting Pattern 6380 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence.

730

3GPP

6381 RUF Outcome 6382 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6383 User error 6384 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6385 values defined in clause 7.6.1: 6386 6387 6388 6389 6390 6391 6392 6393

731 Release 7 732 733

184

3GPP TS 29.002 V7.5.0 (2006-09)

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

6394 Provider error 6395 These are defined in clause 7.6.

6396 6397

10.13 MAP_IST_ALERT service

10.13.1 Definition

6398 This service is used between the MSC (Visited MSC or Gateway MSC) and the HLR, to report that the IST timer 6399 running for a call for the Subscriber has expired. It is a confirmed service using the service primitives shown in 6400 table 10.13/1.

6401
6402

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

6403

6404

10.13.3 Parameter use

6405 All parameters are described in clause 7.6. The following clarifications are applicable: 6406 IST Alert Timer 6407 If included in the IST Alert response, it includes the new IST Alert timer value that must be used to inform the HLR 6408 about the call activities that the subscriber performs. 6409 IST Information Withdraw

734

3GPP

6410 If included in the IST Alert response, this parameter is used to indicate that the IST condition has been removed for the 6411 subscriber. When the MSC receives this parameter, IST control for that call shall be terminated. 6412 Call termination Indicator 6413 6414 6415 6416 6417

735 Release 7 736 737

185

3GPP TS 29.002 V7.5.0 (2006-09)

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.

6418 User error 6419 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6420 6421 6422 6423 6424

System Failure; Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.

6425 6426

10.14 MAP_IST_COMMAND service

10.14.1 Definition

6427 This service is used by the HLR to instruct the MSC (Visited MSC or Gateway MSC) to terminate ongoing call 6428 activities for a specific subscriber. It is a confirmed service using the service primitives shown in table 10.14/1.

6429
6430

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

6431

6432

10.14.3 Parameter use

6433 All parameters are described in clause 7.6. The following clarifications are applicable: 6434 User error 6435 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6436 6437 6438 6439 6440

System Failure; Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.

738

3GPP

739 Release 7 740 741

186

3GPP TS 29.002 V7.5.0 (2006-09)

6441 6442

10.15 MAP_RELEASE_RESOURCES service

10.15.1 Definition

6443 This service is used between the GMSC and the terminating VMSC. The service is invoked by the GMSC to request the 6444 VMSC to release the resources associated with the specified MSRN. 6445 This is a confirmed service which uses the Primitives listed in table 10.15/1.

6446
6447

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

6448

6449
6450 MSRN

10.15.3 Parameter use

6451 See 3GPP TS 23.018 [97] for the use of this parameter. 6452 User error 6453 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6454 6455

System Failure; Unexpected Data Value;

6456 Provider error 6457 These are defined in clause 7.6.

6458 6459 6460

11

Supplementary services related services

11.1 MAP_REGISTER_SS service
11.1.1 Definition

6461 This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a 6462 supplementary service. The VLR will relay the message to the HLR. 6463 The service is a confirmed service and uses the service primitives shown in table 11.1./1.

6464
6465

11.1.2 Service primitives

Table 11.1/1: MAP_REGISTER_SS parameters
Parameter name Invoke id SS-Code Basic service Request M M C Indication M(=) M(=) C(=) Response M(=) Confirm M(=)

742

3GPP

743 Release 7 744 745 Forwarded-to number with subaddress No reply condition time EMLPP default priority Long FTN Supported NbrUser Forwarding information User error Provider error

187 C C C C C C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V7.5.0 (2006-09)

C C C C

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

6466

6467
6468 Invoke id

11.1.3 Parameter use

6469 See clause 7.6.1 for the use of this parameter. 6470 SS-Code 6471 This parameter indicates the supplementary service which the mobile subscriber wants to register. 6472 Basic service 6473 This parameter indicates for which basic service group the supplementary service is to be registered. If it is not 6474 included, the registration request applies to all basic services. 6475 Forwarded-to number with subaddress 6476 This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can 6477 optionally include a sub-address. 6478 No reply condition time 6479 This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a 6480 superset of this service) and the mobile subscriber supplies a value for this time. 6481 EMLPP default priority 6482 This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at 6483 successful outcome of the service. 6484 Long FTN Supported 6485 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6486 NbrUser 6487 This parameter is sent by the initiator to register the MC maximum number of user defined circuit switched bearers to 6488 be used. 6489 Forwarding information 6490 This parameter is returned by the responder at successful outcome of the service, if the registration request concerned 6491 one or a group of Call Forwarding supplementary services. 6492 User error 6493 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6494 values defined in clause 7.6.1: 6495 6496 6497 6498

System failure; Data missing; Unexpected data value; Call Barred;

746

3GPP

6499

747 Release 7 748 749

188

3GPP TS 29.002 V7.5.0 (2006-09)

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;

6500 6501 6502 6503 6504 6505

Illegal SS operation; SS error status; SS incompatibility.

6506 Provider error 6507 See clause 7.6.1 for the use of this parameter.

6508 6509

11.2 MAP_ERASE_SS service

11.2.1 Definition

6510 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a 6511 supplementary service. The VLR will relay the message to the HLR. 6512 The service is a confirmed service and uses the service primitives shown in table 11.2/1.

6513
6514

11.2.2 Service primitives

Table 11.2/1: MAP_ERASE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O

6515

6516
6517 Invoke id

11.2.3 Parameter use

6518 See clause 7.6.1 for the use of this parameter. 6519 SS-Code 6520 This parameter indicates the supplementary service which the mobile subscriber wants to erase. 6521 Basic service 6522 This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, 6523 the erasure request applies to all basic services. 6524 Forwarding information 6525 This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or 6526 a group of Call Forwarding supplementary services. 6527 User error

750

3GPP

6528 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6529 values, defined in clause 7.6.1: 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539

751 Release 7 752 753

189

3GPP TS 29.002 V7.5.0 (2006-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.

6540 Provider error 6541 See clause 7.6.1 for the use of this parameter.

6542 6543

11.3 MAP_ACTIVATE_SS service

11.3.1 Definition

6544 This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary 6545 service. The VLR will relay the message to the HLR. 6546 The service is a confirmed service and uses the service primitives shown in table 11.3/1.

6547
6548

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

6549

6550
6551 Invoke id

11.3.3 Parameter use

6552 See clause 7.6.1 for the use of this parameter. 6553 SS-Code 6554 This parameter indicates the supplementary service which the mobile subscriber wants to activate. 6555 Basic service

754

3GPP

6556 This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it 6557 is not included, the activation request applies to all basic services. 6558 Forwarding information 6559 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 6560 Call Forwarding. 6561 Long FTN Supported 6562 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6563 Call barring information 6564 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 6565 Call Barring. 6566 SS-Data 6567 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for 6568 example Call Waiting. 6569 User error 6570 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6571 values, defined in clause 7.6.1: 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585

755 Release 7 756 757

190

3GPP TS 29.002 V7.5.0 (2006-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; SS incompatibility; Negative PW check; Number Of PW Attempts Violation.

6586 Provider error 6587 See clause 7.6.1 for the use of this parameter.

6588 6589

11.4 MAP_DEACTIVATE_SS service

11.4.1 Definitions

6590 This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary 6591 service. The VLR will relay the message to the HLR.

758

3GPP

6592 The service is a confirmed service and uses the service primitives shown in table 11.4/1.

759 Release 7 760 761

191

3GPP TS 29.002 V7.5.0 (2006-09)

6593
6594

11.4.2 Service primitives

Table 11.4/1: MAP_DEACTIVATE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=) O

6595

6596
6597 Invoke id

11.4.3 Parameter use

6598 See clause 7.6.1 for the use of this parameter. 6599 SS-Code 6600 This parameter indicates the supplementary service which the mobile subscriber wants to deactivate. 6601 Basic service 6602 This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If 6603 it is not included the deactivation request applies to all basic services. 6604 Forwarding information 6605 This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned 6606 one or a group of Call Forwarding supplementary services. 6607 Call barring information 6608 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one 6609 or a group of Call Barring supplementary services. 6610 SS-Data 6611 This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request 6612 concerned the Call Waiting supplementary service. 6613 User error 6614 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6615 values, defined in clause 7.6.1: 6616 6617 6618 6619 6620 6621 6622

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;

762

3GPP

6623

763 Release 7 764 765

192

3GPP TS 29.002 V7.5.0 (2006-09)

Call Barred; Illegal SS operation; SS error status; SS subscription violation; Negative PW check; Number Of PW Attempts Violation.

6624 6625 6626 6627 6628

6629 Provider error 6630 See clause 7.6.1 for the use of this parameter.

6631 6632

11.5 MAP_INTERROGATE_SS service

11.5.1 Definitions

6633 This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related 6634 to a supplementary service. The VLR will relay the message to the HLR if necessary. 6635 The service is a confirmed service and consists of four service primitives.

6636

11.5.2 Service primitives

Table 11.5/1: MAP_INTERROGATE_SS parameters
Parameter name Invoke id SS-Code Basic service Long FTN Supported SS-Status Basic service Group LIST Forwarding feature LIST CLI restriction Info EMLPP Info MC Information CCBS Feature LIST User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)

6637 The service primitives are shown in table 11.5/1. 6638

C C C C C C C C

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

6639

6640

11.5.3 Parameter use

6641 For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications. 6642 Invoke id 6643 See clause 7.6.1 for the use of this parameter. 6644 SS-Code 6645 The mobile subscriber can only interrogate a single supplementary service per service request. 6646 Basic service 6647 This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not 6648 included, the interrogation request applies to all basic services.

766

3GPP

6649 SS-Status

767 Release 7 768 769

193

3GPP TS 29.002 V7.5.0 (2006-09)

6650 This parameter is included by the responder if: 6651 6652 6653 6654 6655

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.

6656 Basic service group LIST 6657 This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary 6658 service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) 6659 basic service groups, the SS-Status parameter is returned. 6660 Long FTN Supported 6661 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6662 Forwarding feature LIST 6663 The forwarding feature parameter is described in clause 7.6.4. A list of one or more forwarding features is returned by 6664 the responder when the interrogation request applied to Call Forwarding supplementary service. 6665 If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all 6666 provisioned basic services. 6667 CLI restriction Info 6668 The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR 6669 supplementary service. 6670 EMLPP Info 6671 The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation 6672 request applies to the eMLPP supplementary service. 6673 MC Information 6674 The MC information (NbrSB, NbrUser and NbrSN) is returned by the responder if the interrogation request applies to 6675 the MC supplementary service. For a definition of these 3 components, refer to 3GPP TS 23.135 and 3GPP TS 24.135. 6676 CCBS Feature LIST 6677 The CCBS feature parameter is described in clause 7.6. A list of one or more CCBS features is returned by the 6678 responder when the interrogation request applied to the CCBS supplementary service. See 3GPP TS 23.093 [107] for 6679 the conditions for the presence of the parameters included in the CCBS feature. 6680 User error 6681 This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the 6682 following values, defined in clause 7.6.1: 6683 6684 6685 6686 6687 6688

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;

770

3GPP

6689

771 Release 7 772 773

194

3GPP TS 29.002 V7.5.0 (2006-09)

This error is returned only if not even a subset of the interrogated teleservices are provided; Call Barred; Illegal SS operation; SS not available.

6690 6691 6692

6693 Provider error 6694 See clause 7.6.1 for the use of this parameter.

6695 6696 6697

11.6 Void 11.7 MAP_REGISTER_PASSWORD service

11.7.1 Definitions

6698 This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber 6699 requests to register a new password. The VLR will relay the message to the HLR. 6700 The service is a confirmed service and consists of four service primitives.

6701

11.7.2 Service primitives

Table 11.7/1: MAP_REGISTER_PASSWORD parameters
Parameter name Invoke id SS-Code New password User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O

6702 The service primitives are shown in table 11.7/1. 6703

6704

6705
6706 Invoke id

11.7.3 Parameter use

6707 See clause 7.6.1 for the use of this parameter. 6708 SS-Code 6709 This parameter indicates for which supplementary service(s) the password should be registered. 6710 New Password 6711 See clause 7.6.4 for the use of this parameter. 6712 User error 6713 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6714 values, defined in clause 7.6.1: 6715 6716 6717

System failure; Data Missing; Unexpected data value;

774

3GPP

6718

775 Release 7 776 777

195

3GPP TS 29.002 V7.5.0 (2006-09)

Call Barred; SS subscription violation; Password registration failure; Negative PW check; Number Of PW Attempts Violation.

6719 6720 6721 6722

6723 Provider error 6724 See clause 7.6.1 for the use of this parameter.

6725 6726

11.8 MAP_GET_PASSWORD service

11.8.1 Definitions

6727 This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a 6728 request from the mobile subscriber for an operation on a supplementary service which requires a password from the 6729 subscriber. The VLR will relay the message to the MSC. 6730 The service is a confirmed service and uses the service primitives shown in table 11.8/1.

6731
6732

11.8.2 Service primitives

Table 11.8/1: MAP_GET_PASSWORD parameters
Parameter name Invoke id Linked id Guidance info Current password Provider error Request M C M Indication M(=) C(=) M(=) Response M(=) Confirm M(=)

M(=) O

6733

6734
6735 Invoke id

11.8.3 Parameter use

6736 See clause 7.6.1 for the use of this parameter. 6737 Linked Id 6738 See clause 7.6.1 for the use of this parameter. If the MAP_GET_PASSWORD service is used in conjunction with the 6739 MAP_REGISTER_PASSWORD service, this parameter must be present; otherwise it must be absent. 6740 Guidance info 6741 See clause 7.6.4 for the use of this parameter. 6742 Current password 6743 See clause 7.6.4 for the use of this parameter. 6744 Provider error 6745 See clause 7.6.1 for the use of this parameter.

6746 6747

11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service

3GPP

778

6748

779 Release 7 780 781

196

3GPP TS 29.002 V7.5.0 (2006-09)

11.9.1 Definitions

6749 This service is used between the MSC and the VLR, between the VLR and the HLR, between the HLR and gsmSCF 6750 and between the HLR and HLR to relay information in order to allow unstructured supplementary service operation. 6751 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from 6752 table 11.9/1.

6753
6754

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

6755

6756
6757 Invoke id

11.9.3 Parameter use

6758 See clause 7.6.1 for the use of this parameter. 6759 USSD Data Coding Scheme 6760 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the 6761 unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be 6762 present. 6763 USSD String 6764 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the 6765 unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme 6766 parameter has to be present. 6767 MSISDN 6768 The subscribers basic MSISDN. 6769 See definition in clause 7.6.2. For Follow Me when the service request is sent from the HLR of the A subscriber, the 6770 parameter shall contain the MSISDN of the A subscriber, see 3GPP TS 23.094 [129]. For other purposes the MSISDN 6771 may be included as an operator option, e.g. to allow addressing the subscribers data in the gsmSCF with the MSISDN. 6772 User error 6773 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6774 values defined in clause 7.6.1: 6775 6776 6777 6778 6779 6780

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.

782

3GPP

6781 Provider error 6782 See clause 7.6.1 for the use of this parameter.

783 Release 7 784 785

197

3GPP TS 29.002 V7.5.0 (2006-09)

6783 6784

11.10 MAP_UNSTRUCTURED_SS_REQUEST service

11.10.1 Definitions

6785 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6786 when the invoking entity requires information from the mobile user, in connection with unstructured supplementary 6787 service handling. 6788 The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.10/1.

6789
6790

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

6791

6792
6793 Invoke id

11.10.3 Parameter use

6794 See clause 7.6.1 for the use of this parameter. 6795 USSD Data Coding Scheme 6796 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6797 user's MMI input. If this parameter is present, then the USSD String parameter has to be present. 6798 USSD String 6799 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6800 user's MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. 6801 Alerting Pattern 6802 See clause 7.6.3 for the use of this parameter. 6803 User error 6804 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6805 values defined in clause 7.6.1: 6806 6807 6808 6809 6810 6811

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;

786

3GPP

6812 6813

787 Release 7 788 789

198

3GPP TS 29.002 V7.5.0 (2006-09)

This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication; Illegal Equipment; USSD Busy; Unknown Alphabet.

6814 6815 6816

6817 Provider error 6818 See clause 7.6.1 for the use of this parameter.

6819 6820

11.11 MAP_UNSTRUCTURED_SS_NOTIFY service

11.11.1 Definitions

6821 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6822 when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured 6823 supplementary services handling. 6824 The MAP_UNSTRUCTURED_SS_NOTIFY service is a confirmed service using the primitives from table 11.11/1.

6825
6826

11.11.2 Service primitives

Table 11.11/1: MAP_UNSTRUCTURED_SS_NOTIFY parameters
Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error Request M M M C Indication M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

C(=) O

6827

6828
6829 Invoke id

11.11.3 Parameter use

6830 See clause 7.6.1 for the use of this parameter. 6831 USSD Data Coding Scheme: 6832 See clause 7.6.4 for the use of this parameter. 6833 USSD String: 6834 See clause 7.6.1 for the use of this parameter. 6835 Alerting Pattern 6836 See clause 7.6.3 for the use of this parameter. 6837 User error 6838 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6839 values defined in clause 7.6.1: 6840 6841

System failure; Data missing;

790

3GPP

6842 6843

791 Release 7 792 793

199

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string.

6844 6845 6846 6847 6848 6849 6850

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.

6851 Provider error 6852 See clause 7.6.1 for the use of this parameter.

6853 6854

11.12 MAP_SS_INVOCATION_NOTIFY
11.12.1 Definition

6855 This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following 6856 supplementary services; Call Deflection (CD), Explicit Call Transfer (ECT) or Multi Party (MPTY). 6857 This service is used between the HLR and the gsmSCF when the subscriber invokes the CCBS supplementary service.

6858

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

6859 The service primitives are shown in table 11.12/1. 6860

C(=) O

6861

6862

11.12.3 Parameter use

6863 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are 6864 specified in 3GPP TS 23.078. 6865 User error 6866 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6867 6868 6869

Data Missing; Unexpected Data Value; Unknown Subscriber.

794

3GPP

6870 Provider error 6871 This is defined in clause 7.6.1.

795 Release 7 796 797

200

3GPP TS 29.002 V7.5.0 (2006-09)

6872 6873

11.13 MAP_REGISTER_CC_ENTRY service

11.13.1 Definition

6874 This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested 6875 call completion supplementary service. The VLR will relay the message to the HLR. 6876 The service is a confirmed service and uses the service primitives shown in table 11.13/1.

6877
6878

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

C(=) O

6879

6880

11.13.3 Parameter use

6881 See clause 7.6 for a definition of the parameters used, in addition to the following. 6882 SS-Code 6883 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an 6884 entry. 6885 CCBS Feature 6886 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 6887 Translated B Number 6888 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6889 Service Indicator 6890 This parameter corresponds to the parameters 'Presentation Indicator' and 'CAMEL Invoked' in 3GPP TS 23.093 [107]. 6891 It indicates which services have been invoked for the original call (e.g. CLIR, CAMEL). See 3GPP TS 23.093 [107] for 6892 the use of this parameter and the conditions for its presence. 6893 Call Info 6894 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6895 Network Signal Info 6896 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6897 User error

798

3GPP

6898 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6899 values, defined in clause 7.6.1: 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910

799 Release 7 800 801

201

3GPP TS 29.002 V7.5.0 (2006-09)

System failure; Data missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS incompatibility. Short Term Denial; Long Term Denial; Facility Not Supported; This error is reserved for future use.

NOTE:

6911 Private Extensions shall not be sent with these user errors for this operation. 6912 Provider error 6913 See clause 7.6.1 for the use of this parameter.

6914 6915

11.14 MAP_ERASE_CC_ENTRY service

11.14.1 Definition

6916 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call 6917 completion supplementary service. The VLR will relay the message to the HLR. 6918 The service is a confirmed service and uses the service primitives shown in table 11.14/1.

6919
6920

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

6921

6922

11.14.3 Parameter use

6923 See clause 7.6 for a definition of the parameters used, in addition to the following. 6924 SS-Code 6925 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an 6926 entry/entries. 6927 CCBS Index

802

3GPP

6928 See 3GPP TS 23.093 [107] for the use of this parameter and the condition for its presence. 6929 SS-Status 6930 Depending on the outcome of the service request this parameter may indicate either provisioned and active or not 6931 provisioned. 6932 User error 6933 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6934 values, defined in clause 7.6.1: 6935 6936 6937 6938 6939 6940

803 Release 7 804 805

202

3GPP TS 29.002 V7.5.0 (2006-09)

System failure; Data Missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status.

6941 Private Extensions shall not be sent with these user errors for this operation. 6942 Provider error 6943 See clause 7.6.1 for the use of this parameter.

6944 6945 6946

12

Short message service management services

12.1 MAP-SEND-ROUTING-INFO-FOR-SM service
12.1.1 Definition

6947 This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the 6948 short message to the servicing MSC. 6949 The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1.

6950
6951

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

6952

806

3GPP

6953

807 Release 7 808 809

203

3GPP TS 29.002 V7.5.0 (2006-09)

12.1.3 Parameter use

6954 Invoke id 6955 See definition in clause 7.6.1. 6956 MSISDN 6957 See definition in clause 7.6.2. 6958 SM-RP-PRI 6959 See definition in clause 7.6.8. 6960 Service Centre Address 6961 See definition in clause 7.6.2. 6962 SM-RP-MTI 6963 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6964 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6965 layer protocol. 6966 SM-RP-SMEA 6967 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6968 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6969 layer protocol. 6970 GPRS Support Indicator 6971 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of the 6972 two numbers from the HLR. 6973 IMSI 6974 See definition in clause 7.6.2. The presence of this parameter is mandatory in a successful case. 6975 Network Node Number 6976 See definition in clause 7.6.2. This parameter is provided in a successful response. 6977 LMSI 6978 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 6979 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6980 GPRS Node Indicator 6981 See definition in clause 7.6.8. The presence of this parameter is mandatory if only the SGSN number is sent in the 6982 Network Node Number. 6983 Additional Number 6984 See definition in clause 7.6.2. This parameter is provided in a successful response. 6985 User error 6986 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6987 6988 6989

Unknown subscriber; Call Barred; Teleservice Not Provisioned;

810

3GPP

6990 6991 6992 6993 6994

811 Release 7 812 813

204

3GPP TS 29.002 V7.5.0 (2006-09)

Absent Subscriber_SM; Facility Not Supported; System failure; Unexpected Data Value; Data missing.

6995 Provider error 6996 For definition of provider errors see clause 7.6.1.

6997 6998

12.2 MAP-MO-FORWARD-SHORT-MESSAGE service

12.2.1 Definition

6999 This service is used between the serving MSC or the SGSN and the SMS Interworking MSC to forward mobile 7000 originated short messages. 7001 The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 7002 table 12.2/1.

7003
7004

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

C C

C(=) C(=) O

7005

7006
7007 Invoke id

12.2.3 Parameter use

7008 See definition in clause 7.6.1. 7009 SM RP DA 7010 See definition in clause 7.6.8. 7011 In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile 7012 station. 7013 SM RP OA 7014 See definition in clause 7.6.8. 7015 The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM 7016 transfer. 7017 SM RP UI 7018 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 7019 in this parameter.

814

3GPP

7020 IMSI

815 Release 7 816 817

205

3GPP TS 29.002 V7.5.0 (2006-09)

7021 See definition in clause 7.6.2.1. The IMSI of the originating subscriber is inserted in this parameter in the mobile 7022 originated SM transfer. 7023 This parameter shall be included if the sending entity, whether MSC or SGSN, supports mobile number portability. 7024 User error 7025 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035

Facility Not Supported; System Failure; SM Delivery Failure; The reason of the SM Delivery Failure can be one of the following in the mobile originated SM: unknown Service Centre address; Service Centre congestion; invalid Short Message Entity address; subscriber not Service Centre subscriber; protocol error.

Unexpected Data Value

7036 Provider error 7037 For definition of provider errors see clause 7.6.1.

7038 7039

12.3 MAP-REPORT-SM-DELIVERY-STATUS service

12.3.1 Definition

7040 This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is 7041 used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This 7042 service is invoked by the gateway MSC. 7043 The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in 7044 table 12.3/1.

7045
7046

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

818

3GPP

7047

819 Release 7 820 821

206

3GPP TS 29.002 V7.5.0 (2006-09)

7048
7049 Invoke id

12.3.3 Parameter use

7050 See definition in clause 7.6.1. 7051 MSISDN 7052 See definition in clause 7.6.2. 7053 Service Centre Address 7054 See definition in clause 7.6.2. 7055 SM Delivery Outcome 7056 See definition in clause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. 7057 Absent Subscriber Diagnostic SM 7058 See definition in clause 7.6.8. 7059 GPRS Support Indicator 7060 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of two 7061 delivery outcomes. 7062 Delivery Outcome Indicator 7063 See definition in clause 7.6.8. 7064 Additional SM Delivery Outcome 7065 See definition in clause 7.6.8. 7066 Additional Absent Subscriber Diagnostic SM 7067 See definition in clause 7.6.8. 7068 MSIsdn-Alert 7069 See definition in clause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN 7070 received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned 7071 to the gateway MSC. 7072 User error 7073 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7074 7075 7076 7077

Unknown Subscriber; Message Waiting List Full; Unexpected Data Value; Data missing.

7078 Provider error 7079 For definition of provider errors see clause 7.6.1.

7080

12.4 MAP-READY-FOR-SM service

822

3GPP

7081

823 Release 7 824 825

207

3GPP TS 29.002 V7.5.0 (2006-09)

12.4.1 Definition

7082 This service is used between the MSC and VLR as well as between the VLR and the HLR. The MSC initiates this 7083 service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. 7084 The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the 7085 MSC. 7086 Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates 7087 memory available situation. The SGSN uses the service to indicate this to the HLR. 7088 The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in 7089 the GPRS. 7090 The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1.

7091
7092

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

C(=) O

7093

7094
7095 Invoke id

12.4.3 Parameter use

7096 See definition in clause 7.6.1. 7097 IMSI 7098 See definition in clause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the 7099 HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI. 7100 TMSI 7101 See definition in clause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR. 7102 Alert Reason 7103 See definition in clause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory 7104 available. 7105 Alert Reason Indicator 7106 See definition in clause 7.6.8. 7107 User error 7108 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7109 7110 7111 7112

Unknown Subscriber; Facility Not Supported; System Failure; Unexpected Data Value;

826

3GPP

7113

827 Release 7 828 829

208

3GPP TS 29.002 V7.5.0 (2006-09)

Data missing.

7114 Provider error 7115 For definition of provider errors see clause 7.6.1.

7116 7117

12.5 MAP-ALERT-SERVICE-CENTRE service

12.5.1 Definition

7118 This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects 7119 that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available. 7120 The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1.

7121
7122

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

7123

7124
7125 Invoke id

12.5.3 Parameter use

7126 See definition in clause 7.6.1. 7127 MSIsdn-Alert 7128 See definition in clause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data file. 7129 Service Centre Address 7130 See definition in clause 7.6.2. 7131 User error 7132 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7133 7134 7135

System Failure; Unexpected Data Value; Data missing.

7136 Provider error 7137 For definition of provider errors see clause 7.6.1.

7138 7139

12.6 MAP-INFORM-SERVICE-CENTRE service

12.6.1 Definition

7140 This service is used between the HLR and the gateway MSC to inform the Service Centre which MSISDN number is 7141 stored in the Message Waiting Data file. If the stored MSISDN number is not the same as the one received from the

830

3GPP

7142 gateway MSC in the MAP-SEND-ROUTING-INFO-FOR-SM service primitive the stored MSISDN number is 7143 included in the message. 7144 Additionally the status of MCEF, MNRF and MNRG flags and the inclusion of the particular Service Centre address in 7145 the Message Waiting Data list is informed to the gateway MSC when appropriate. 7146 If the HLR has stored a single MNRR, the value is included in the Absent Subscriber Diagnostic SM parameter. 7147 If the HLR has stored a second MNRR, the value of the MNRR for the MSC is included in the Absent Subscriber 7148 Diagnostic SM parameter and the value of the MNRR for the SGSN is included in the Additional Absent Subscriber 7149 Diagnostic SM parameter. 7150 The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1.

831 Release 7 832 833

209

3GPP TS 29.002 V7.5.0 (2006-09)

7151
7152

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

7153

7154
7155 Invoke id

12.6.3 Parameter use

7156 See definition in clause 7.6.1. 7157 MSIsdn-Alert 7158 See definition in clause 7.6.2. This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR. 7159 MWD Status 7160 See definition in clause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the status 7161 of the particular SC address presence in the Message Waiting Data list. 7162 Absent Subscriber Diagnostic SM 7163 See definition in clause 7.6.8. 7164 Additional Absent Subscriber Diagnostic SM 7165 See definition in clause 7.6.8.

7166 7167

12.7 MAP-SEND-INFO-FOR-MT-SMS service

12.7.1 Definition

7168 This service is used between the MSC and the VLR. The service is invoked by the MSC receiving a mobile terminated 7169 short message to request subscriber related information from the VLR. 7170 The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1.

7171

12.7.2 Service primitives

3GPP

834

7172

835 Release 7 836 837

210

3GPP TS 29.002 V7.5.0 (2006-09)

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

C C

C(=) C(=) O

7173

7174
7175 Invoke id

12.7.3 Parameter use

7176 See definition in clause 7.6.1. 7177 SM RP DA 7178 See definition in clause 7.6.8. This parameter shall contain either an IMSI or an LMSI. 7179 IMSI 7180 See definition in clause 7.6.2. This parameter shall be present if the SM RP DA parameter contains an LMSI; otherwise 7181 it shall be absent. 7182 MSISDN 7183 See definition in clause 7.6.2. 7184 User error 7185 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7186 7187 7188 7189 7190 7191 7192 7193 7194

Unknown subscriber; Unidentified Subscriber; Absent subscriber; Unexpected Data Value; Data Missing; Illegal subscriber; Illegal equipment; Subscriber busy for MT SMS; System Failure.

7195 Provider error 7196 For definition of provider errors see clause 7.6.1.

7197 7198

12.8 MAP-SEND-INFO-FOR-MO-SMS service

12.8.1 Definition

7199 This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile 7200 originated short message request to request the subscriber related information from the VLR. 7201 The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1.

838

3GPP

7202

839 Release 7 840 841

211

3GPP TS 29.002 V7.5.0 (2006-09)

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

7203

7204

7205
7206 Invoke id

12.8.3 Parameter use

7207 See definition in clause 7.6.1. 7208 Service Centre Address 7209 See definition in clause 7.6.2. 7210 MSISDN 7211 See definition in clause 7.6.2. 7212 User error 7213 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7214 7215 7216 7217

Teleservice Not Provisioned; Call Barred; Unexpected Data Value; Data Missing.

7218 Provider error 7219 For definition of provider errors see clause 7.6.1.

7220 7221

12.9 MAP-MT-FORWARD-SHORT-MESSAGE service

12.9.1 Definition

7222 This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile terminated short 7223 messages. 7224 The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 7225 table 12.9/1.

7226
7227

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 Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)

C(=)

842

3GPP

843 Release 7 844 845

212 User error Provider error C

3GPP TS 29.002 V7.5.0 (2006-09) C(=) O

7228

7229
7230 Invoke id

12.9.3 Parameter use

7231 See definition in clause 7.6.1. 7232 SM RP DA 7233 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 7234 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 7235 available. 7236 This parameter is omitted in the mobile terminated subsequent SM transfers. 7237 SM RP OA 7238 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in 7239 this parameter. 7240 This parameter is omitted in the mobile terminated subsequent SM transfers. 7241 SM RP UI 7242 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 7243 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message 7244 delivery acknowledgement from the MSC or from the SGSN to the Service Centre. 7245 More Messages To Send 7246 See definition in clause 7.6.8. The information from the MMS indication received from the Service Centre is inserted in 7247 this parameter. 7248 User error 7249 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7250

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.

7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262

846

3GPP

7263

847 Release 7 848 849

213

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected Data Value; Data Missing.

7264

7265 Provider error 7266 For definition of provider errors see clause 7.6.1.

7267 7268

12.10 MAP-MT-FORWARD-SM-FOR-VGCS service

12.10.1 Definition

7269 This service is used between the SMS gateway MSC and the Group Call Anchor MSC to forward mobile terminated 7270 short messages into an ongoing voice group call. 7271 The MAP-MT-FORWARD-SM-FOR-VGCS service is a confirmed service using the service primitives given in 7272 table 12.10/1.

7273
7274

12.10.2 Service primitives

Table 12.10/1: MAP-MT-FORWARD-SM-VGCS
Parameter name Invoke Id ASCI Call Reference SM RP OA SM RP UI Dispatcher List Ongoing Call Indicator User error Provider error Request M M M M Indication M(=) M(=) M(=) M(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=) O

7275

7276
7277 Invoke id

12.10.3 Parameter use

7278 See definition in clause 7.6.1. 7279 ASCI Call Reference 7280 Group call reference. This item is used to access the VGCS-GCR within the Anchor_MSC. 7281 SM RP OA 7282 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in 7283 this parameter. 7284 SM RP UI 7285 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 7286 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message 7287 delivery acknowledgement from the MSC to the Service Centre. 7288 Dispatcher List 7289 A list of identities (international E.164 phone numbers) identifying the dispatchers of the VGCS call. It shall be present 7290 if received from the GCR; otherwise shall be absent. 7291 Ongoing Call Indicator 7292 Indicates by its presence that the VGCS call is ongoing.

850

3GPP

7293 User error

851 Release 7 852 853

214

3GPP TS 29.002 V7.5.0 (2006-09)

7294 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7295 7296

System Failure; Unexpected Data Value.

7297 Provider error 7298 For definition of provider errors see clause 7.6.1.

7299 7300 7301

13

Network-Requested PDP Context Activation services

13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service
13.1.1 Definition

7302 This service is used by the GGSN to request GPRS routing information from the HLR.

7303
7304

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

7305

7306
7307 Invoke Id

13.1.3 Parameter definition and use

7308 See definition in clause 7.6.1. 7309 IMSI 7310 See definition in clause 7.6.2. 7311 GGSN address 7312 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 7313 GGSN number 7314 See definition in clause 7.6.2. 7315 SGSN address 7316 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 7317 process in the HLR is positive. 7318 Mobile Not Reachable Reason

854

3GPP

7319 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 7320 process in the HLR is positive and the MNRG flag in the HLR is set. See definition in clause 7.6.3.51. 7321 User error 7322 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 7323 7324 7325 7326 7327

855 Release 7 856 857

215

3GPP TS 29.002 V7.5.0 (2006-09)

Absent Subscriber; System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

7328 The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown. 7329 7330 7331

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

7332 Provider error 7333 These are defined in clause 7.6.1.

7334 7335

13.2 MAP_FAILURE_REPORT service

13.2.1 Definition

7336 This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed.

7337
7338

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

7339

7340
7341 Invoke Id

13.2.3 Parameter definition and use

7342 See definition in clause 7.6.1. 7343 IMSI 7344 See definition in clause 7.6.2. 7345 GGSN address 7346 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 7347 GGSN number

858

3GPP

7348 See definition in clause 7.6.2. 7349 User error 7350 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 7351 7352 7353 7354

859 Release 7 860 861

216

3GPP TS 29.002 V7.5.0 (2006-09)

System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.

7355 Provider error 7356 These are defined in clause 7.6.1.

7357 7358

13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service

13.3.1 Definition

7359 This service is used by the HLR to inform the GGSN that the MS is present for GPRS again.

7360
7361

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

7362

7363
7364 Invoke Id

13.3.3 Parameter definition and use

7365 See definition in clause 7.6.1. 7366 IMSI 7367 See definition in clause 7.6.2. 7368 GGSN address 7369 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 7370 SGSN address 7371 See definition in clause 7.6.2. 7372 User error 7373 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 7374 7375

System Failure; Data Missing;

862

3GPP

7376 7377

863 Release 7 864 865

217

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected Data Value; Unknown Subscriber.

7378 Provider error 7379 These are defined in clause 7.6.1.

7380 7381 7382

13A

Location Service Management Services

13A.1MAP-SEND-ROUTING-INFO-FOR-LCS Service
13A.1.1 Definition

7383 This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location 7384 service request to the servicing VMSC or SGSN. The MAP-SEND-ROUTING-INFO-FOR-LCS is a confirmed service 7385 using the primitives from table 13A.1/1.

7386
7387

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

7388

7389
7390 Invoke id

13A.1.3 Parameter Use

7391 See definition in clause 7.6.1. 7392 MLC Number 7393 See definition in clause 7.6.2. 7394 MSISDN 7395 See definition in clause 7.6.2. The request shall carry either the IMSI or MSISDN. The response shall carry whichever 7396 of these was not included in the request (see 3GPP TS 23.271 for details). 7397 IMSI

866

3GPP

7398 See definition in clause 7.6.2. 7399 LMSI 7400 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 7401 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 7402 Network Node Number 7403 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 7404 Additional Number are received in the GMLC, the Network Node Number is used in preference to the Additional 7405 Number. 7406 GPRS Node Indicator 7407 See definition in clause 7.6.8. The presence of this parameter is mandatory only if the SGSN number is sent in the 7408 Network Node Number. 7409 Additional Number 7410 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 7411 Additional Number are received in the GMLC, the Network Node Number is used in preference to the Additional 7412 Number. 7413 Supported LCS Capability Sets 7414 See definition in clause 7.6.11. This parameter indicates the LCS capability of the serving node that is indicated by the 7415 Network Node Number. This parameter is provided only if LCS capability sets are available in HLR and Network Node 7416 Number is present in this message. 7417 Additional LCS Capability Sets 7418 See definition in clause 7.6.11. This parameter indicates the LCS capability of the serving node that is indicated by the 7419 Additional Number. This parameter is provided only if LCS capability sets are available in HLR and Additional 7420 Number is present in this message. 7421 V-GMLC address 7422 See definition in clause 7.6.2. . This parameter indicates the V-GMLC address of the serving node that is indicated by 7423 the Network Node Number. 7424 Additional V-GMLC address 7425 See definition in clause 7.6.2. This parameter indicates the V-GMLC address of the serving node that is indicated by the 7426 Additional Number. This parameter is provided only if additional LCS capability sets are available in HLR and 7427 Additional Number is present in this message. 7428 H-GMLC address 7429 See definition in clause 7.6.2. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7430 PPR address 7431 See definition in clause 7.6.2. 7432 User error 7433 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 7434 7435 7436 7437 -

867 Release 7 868 869

218

3GPP TS 29.002 V7.5.0 (2006-09)

Unknown subscriber; Absent Subscriber; Facility Not Supported; System failure;

870

3GPP

7438 7439 7440 -

871 Release 7 872 873

219

3GPP TS 29.002 V7.5.0 (2006-09)

Unexpected Data Value; Data missing; Unauthorised requesting network.

7441 Provider error 7442 For definition of provider errors see clause 7.6.1.

7443 7444

13A.2MAP-PROVIDE-SUBSCRIBER-LOCATION Service
13A.2.1 Definition

7445 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 7446 is a confirmed service using the primitives from table 13A.2/1.

7447
7448

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 Reporting PLMN List PeriodicLDRInfo MO-LR Short Circuit Indicator 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 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(=) Response M(=) Confirm M(=)

C M C C C C C C C C

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

7449

7450

13A.2.3 Parameter Definition and Use

874

3GPP

7451 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 7452 specified in 3GPP TS 23.271 [26a]. 7453 Location Type 7454 This parameter identifies the type of location information requested. 7455 MLC Number 7456 This is the E.164 number of the requesting GMLC. 7457 LCS Client ID 7458 This parameter provides information related to the identity of an LCS client. 7459 Privacy Override 7460 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC or SGSN for an 7461 MT-LR are in the same country. 7462 IMSI 7463 The IMSI is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 7464 MSISDN 7465 The MSISDN is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 7466 LMSI 7467 The LMSI shall be provided if previously supplied by the HLR. This parameter is only used in the case of the MT-LR 7468 for CS domain. 7469 LCS Priority 7470 This parameter indicates the priority of the location request. 7471 LCS QoS 7472 This parameter indicates the required quality of service in terms of response time and accuracy. 7473 IMEI 7474 The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7475 Supported GAD Shapes 7476 This parameter indicates which of the shapes defined in 3GPP TS 23.032 [122] are supported. 7477 LCS-Reference Number 7478 This parameter shall be included if a deferred MT-LR procedure is performed for a UE available event, an area event or 7479 a periodic positioning event. 7480 LCS Codeword 7481 See definition in clause 7.6.11.18. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7482 LCS Service Type Id 7483 See definition in clause 7.6.11.15. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7484 LCS Privacy Check 7485 See definition in clause 7.6.11. The requirements for its and its components presence are specified in 3GPP TS 23.271 7486 [26a]. 7487 Area Event Info

875 Release 7 876 877

220

3GPP TS 29.002 V7.5.0 (2006-09)

878

3GPP

7488 See definition in clause 7.6.11. The parameter shall be included if a deferred MT-LR procedure is performed for an area 7489 event. 7490 H-GMLC address 7491 See definition in clause 7.6.2. The parameter shall be included if a deferred MT-LR procedure is performed for a UE 7492 available event, an area event or a periodic positioning event. 7493 Location Estimate 7494 This parameter provides the location estimate if this is encoded in one of the supported geographical shapes. Otherwise 7495 this parameter shall consist of one octet, which shall be discarded by the receiving node. 7496 GERAN Positioning Data 7497 7498 7499 7500

879 Release 7 880 881

221

3GPP TS 29.002 V7.5.0 (2006-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].

7501 UTRAN Positioning Data 7502 7503 7504 7505 7506 7507 Age of Location Estimate 7508 This parameter indicates how long ago the location estimate was obtained. 7509 Additional Location Estimate 7510 This parameter provides the location estimate when not provided by the Location Estimate parameter. It may be sent 7511 only if the parameter Supported GAD Shapes has been received in the Provide Subscriber Location indication and the 7512 shape to be included is supported by the GMLC. 7513 Deferred MT-LR Response Indicator 7514 See definition in clause 7.6.11.2. 7515 Cell Id Or SAI 7516 7517 7518 7519

This parameter indicates the usage of each positioning method that was successfully attempted 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].

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

7520 Accuracy Fulfilment Indicator 7521 See definition in clause 7.6.11.28. 7522 MO-LR Short Circuit Indicator 7523 This parameter indicates whether MO-LR Short Circuit is permitted for periodic location. 7524 Reporting PLMN List 7525 This parameter indicates a list of PLMNs in which subsequent periodic MO-LR TTTP requests will be made. 7526 Periodic LDR information 7527 This parameter indicates the reporting amount and reporting interval of deferred periodic location. 7528 User error

882

3GPP

7529 This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one 7530 of the following values defined in clause 7.6.1. 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 -

883 Release 7 884 885

222

3GPP TS 29.002 V7.5.0 (2006-09)

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.

7542 Provider error 7543 These are defined in clause 7.6.1.

7544 7545

13A.3MAP-SUBSCRIBER-LOCATION-REPORT Service
13A.3.1 Definition

7546 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 7547 is either implicitly administered or made at some earlier time. This is a confirmed service using the primitives from 7548 table 13A.3/1.

7549
7550

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 Request M M M M C C C C U 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(=) C(=) C(=) C(=) Response M(=) Confirm M(=)

C C

C(=) C(=)

C(=)

C(=)

886

3GPP

887 Release 7 888 889

223 LCS Service Type Id Pseudonym Indicator Accuracy Fulfilment Indicator Sequence Number Periodic LDR Info MO-LR Short Circuit Indicator Reporting PLMN List User error Provider error C C C C C C C(=) C(=) C(=) C(=) C(=) C(=)

3GPP TS 29.002 V7.5.0 (2006-09)

C C C

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

7551

7552

13A.3.3 Parameter Definition and Use

7553 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 7554 specified in. 3GPP TS 23.271 [26a]. 7555 LCS Event 7556 This parameter indicates the event that triggered the Subscriber Location Report. 7557 LCS Client ID 7558 This parameter provides information related to the identity of the recipient LCS client. 7559 Network Node Number 7560 See definition in clause 7.6.2. This parameter provides the address of the sending node. 7561 IMSI 7562 The IMSI shall be provided if available to the VMSC or SGSN. 7563 MSISDN 7564 The MSISDN shall be provided if available to the VMSC or SGSN. 7565 NA-ESRD 7566 If the target MS has originated an emergency service call in North America, the NA-ESRD shall be provided by the 7567 VMSC if available. 7568 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in 7569 Subscriber_Location_Report-Arg, an NA-ESRK or NA-ESRD, but not both, may also be included in the response to 7570 the MSC, see 3GPP TS 23.271 [26a]. 7571 NA-ESRK 7572 If the target MS has originated an emergency service call in North America, the NA-ESRK shall be provided by the 7573 VMSC if assigned. 7574 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in 7575 Subscriber_Location_Report-Arg, an NA-ESRK or NA-ESRD, but not both, may also be included in the response to 7576 the MSC, see 3GPP TS 23.271 [26a]. 7577 IMEI 7578 The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7579 Location Estimate 7580 This parameter provides the location estimate. The absence of this parameter implies that a location estimate was not 7581 available or could not be successfully obtained. If the obtained location estimate is not encoded in one of the supported 7582 geographical shapes then this parameter shall consist of one octet, which shall be discarded by the receiving node.

890

3GPP

7583 GERAN Positioning Data 7584 7585 7586 7587

891 Release 7 892 893

224

3GPP TS 29.002 V7.5.0 (2006-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].

7588 UTRAN Positioning Data 7589 7590 7591 7592

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

7593 Age of Location Estimate 7594 This parameter indicates how long ago the location estimate was obtained. 7595 LMSI 7596 The LMSI may be provided if assigned by the VLR. 7597 GPRS Node Indicator 7598 See definition in clause 7.6.8. This presence of this parameter is mandatory only if the SGSN number is sent in the 7599 Network Node Number. 7600 Additional Location Estimate 7601 This parameter provides the location estimate when not provided by the Location Estimate parameter.. 7602 Deferred MT-LR Data 7603 See definition in clause 7.6.11.3. 7604 LCS-Reference Number 7605 This parameter shall be included if the Subscriber Location Report is the response to a deferred MT location request. 7606 NA-ESRK Request 7607 If the target MS has originated an emergency service call in North America, NA-ESRK Request may be included to 7608 indicate that the MSC is able to accept NA-ESRK in the Response message, see section 7.6.11.19. 7609 Cell Id Or SAI 7610 For GERAN access, this parameter indicates Global Cell Identifier of the cell that the served subscriber is currently 7611 attached to. For UTRAN access, this parameter contains the Service Area Identifier for the cell that the subscriber is 7612 currently attached to. This parameter is included only for Emergency Calls as described in 3GPP TS 23.271 [26a]. 7613 H-GMLC address 7614 7615 7616 7617

See definition in clause 7.6.2. The parameter shall be included if the Subscriber Location Report is the response to a deferred MT location request for a UE available event, an area event or a periodic positioning event. This parameter shall be included in a Subscriber Location Report response if a deferred MO-LR TTTP procedure is initiated for a periodic positioning event.

7618 LCS Service Type Id 7619 See definition in clause 7.6.11.15. The requirements for its presence are specified in 3GPP TS 23.271 [26a]. 7620 Pseudonym Indicator 7621 This parameter indicates by its presence that the pseudonym is required. Refer to 3GPP TS 23.271 [26a]. 7622 Accuracy Fulfilment Indicator

894

3GPP

7623 For a mobile terminated periodic LDR, this parameter indicates whether the obtained location estimate satisfies the 7624 requested accuracy or not, provided that this indication is obtained from RAN or the UE with the location estimate. 7625 Periodic LDR Information 7626 This parameter refers to the periodic reporting interval and reporting amount of the deferred periodic location. 7627 MO-LR Short Circuit Indicator 7628 This parameter indicates whether MO-LR Short Circuit is permitted for periodic location. 7629 Reporting PLMN List 7630 This parameter indicates a list of PLMNs in which subsequent periodic MO-LR TTTP requests will be made. 7631 Sequence Number 7632 7633 7634 7635

895 Release 7 896 897

225

3GPP TS 29.002 V7.5.0 (2006-09)

This parameter refers to the number of the periodic location reports completed. The sequence number would be set to 1 in the first location report and increment by 1 for each new report. When the number reaches the reporting amount value, the H-GMLC (for a periodic MT-LR or a periodic MO-LR transfer to third party) will know the procedure is complete. For details see 3GPP TS 23.271 [26a].

7636 User error 7637 This parameter is sent by the responder when the received message contains an error, cannot be forwarded or stored for 7638 an LCS client or cannot be accepted for some other reason and if present, takes one of the following values defined in 7639 clause 7.6.1. 7640 7641 7642 7643 7644 7645 7646 -

System Failure; Data Missing; Unexpected Data Value; Resource Limitation; Unknown Subscriber; Unauthorised requesting network; Unknown or unreachable LCS Client.

7647 Provider error 7648 These are defined in clause 7.6.1.

7649 7650 7651 7652 7653 7654 7655

13A.4Void
13A.4.1 Void 13A.4.2 Void 13A.4.3 Void

13A.5Void
13A.5.1 Void 13A.5.2 Void

898

3GPP

7656 7657 7658 7659

899 Release 7 900 901

226

3GPP TS 29.002 V7.5.0 (2006-09)

13A.5.3 Void

13A.6Void
13A.6.1 Void 13A.6.2 Void 13A.6.3 Void

7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672

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

7673 7674

14

General
14.1 Overview

7675 Clauses 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. 7676 Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping onto TC service 7677 primitives. Clause 17 specifies the application contexts, operation packages and abstract syntaxes for the MAP protocol 7678 as well as the encoding rules to be applied.

902

3GPP

903 Release 7 904 905

227

3GPP TS 29.002 V7.5.0 (2006-09)

7679

14.2 Underlying services

7680 The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of Signalling System Number 7681 No. 7, as referenced in clause 6.

7682
7683 7684 7685 7686

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

7687 A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a TC-BEGIN 7688 indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific service invoked 7689 during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is created at the performer's side. 7690 This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not intended to 7691 suggest any implementation. SDL descriptions are organised according to this model. 7692 How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local 7693 implementation matter. 7694 How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter.

7695

14.4 Conventions

7696 The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major 7697 difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do 7698 not belong to the so-called "version one context set". 7699 The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1 implementation 7700 according to the latest phase 1 version of GSM 09.02. This set is defined in clause 15. 7701 The procedures described in clause 15 are used when the application-context-name does not refer to a dialogue between 7702 an MSC and its VLR. When the application-context-name refers to a dialogue between an MSC and its VLR the MAP 7703 PM procedures are a local implementation matter.

7704 7705
7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720

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.

906

3GPP

7721 Unknown operations may be invoked in the following types of message (there is no restriction as to how many 7722 unknown operations can be invoked in a message): 7723 7724 7725 7726 7727 7728 7729

907 Release 7 908 909

228

3GPP TS 29.002 V7.5.0 (2006-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

7730 The TC-REJECT component may be sent in the following messages: 7731 7732 7733 7734 7735 7736 7737 7738 7739

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.

7740 Note that the SDL diagrams of clauses 19 - 25 do not show the report to the MAP-Service User about the reception of 7741 the unknown operation. This has been done for simplicity of description; the MAP PM may inform the MAP-Service 7742 User. 7743 The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown 7744 operation.

7745

15.2 Dialogue establishment

7746 The establishment of a MAP dialogue involves two MAP-service-users: the dialogue-initiator and the dialogue7747 responder. 7748 This procedure is driven by the following signals: 7749 7750 7751 7752

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;

7753 and under specific conditions: 7754 7755 7756

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.

7757 One instance of the MAP dialogue state machine runs at the initiating side, and one at the responding side.

7758

15.2.1 Behaviour at the initiating side

7759 The behaviour of the MAP dialogue state machine at the initiating side is defined in sheets 1 8 of the process 7760 MAP_DSM (figure 15.6/3).

910

3GPP

7761 Sheet 3: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, 7762 a TC-END indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the 7763 dialogue. 7764 Sheet 3: If the dialogue opening is accepted, any components included in the TC-END are processed and passed to the 7765 MAP-Service User. The dialogue is closed by sending a MAP-CLOSE to the MAP-Service User. 7766 Sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8: when a dialogue is terminated, the MAP dialogue state machine 7767 terminates all instances of the Requesting_MAP_SSM which are active for this dialogue. 7768 7769 7770 7771

911 Release 7 912 913

229

3GPP TS 29.002 V7.5.0 (2006-09)

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

7772 Sheet 8: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, 7773 a TC-CONTINUE indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the 7774 dialogue. 7775 Sheet 8: If the dialogue opening is accepted, any components included in the TC-CONTINUE are processed and passed 7776 to the MAP-Service User. The dialogue has then reached the established state.

7777

15.2.2 Behaviour at the responding side

7778 The behaviour of the MAP dialogue state machine at the responding side is defined in sheets 0 14 of the process 7779 MAP_DSM (figure 15.6/3). 7780 Sheet 9: If no application context information is included in the TC-BEGIN indication, this implies a MAP version 1 7781 dialogue. An explicit application context indicating version 1 is treated as abnormal behaviour. 7782 Sheet 11: The v1 application context name which corresponds to a v1 operation is derived using the information in table 7783 15.2/1. 7784

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

7785
7786 7787 7788 7789

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.

7790 Sheet 12: If the dialogue is accepted, each component present in the TC-BEGIN is forwarded to an instance of a 7791 Performing_MAP_SSM, by executing the procedure Process_Components.

914

3GPP

7792 Sheet 13: If the MAP dialogue state machine receives a MAP-OPEN response with a result accepted, it waits for any 7793 MAP specific service request or response primitives or a MAP-DELIMITER request. 7794 Sheet 13, sheet 14: When a dialogue is terminated, the MAP dialogue state machine terminates all instances of the 7795 Requesting_MAP_SSM or Performing_MAP_SSM which are active for this dialogue. 7796 Sheet 14: A MAP-DELIMITER request triggers a TC-CONTINUE request to accept the dialogue. The dialogue has 7797 then reached the established state.

915 Release 7 916 917

230

3GPP TS 29.002 V7.5.0 (2006-09)

7798

15.3 Dialogue continuation

7799 Once established the dialogue is said to be in a continuation phase. The behaviour of the MAP dialogue state machine 7800 in this phase is defined in sheets 15 17 of the process MAP_DSM (figure 15.6/3). 7801 Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue. 7802 Normal closure of an established dialogue is shown on sheet 16; abnormal termination is shown on sheet 17.

7803

15.4 Load control

7804 If an entity which should respond to a MAP dialogue opening request is overloaded, it uses the AC of the request to 7805 determine whether to discard the request. 7806 The priority level allocated to each application-context is described in clause 5, tables 5.1/1, 5.1/2, and 5.1/3.

7807

15.5 Procedures for MAP specific services

7808 This clause describes the MAP procedures for MAP specific services. These procedures are driven by the following 7809 types of event: 7810 7811

a MAP specific request or a MAP specific response primitive; a component handling primitive from TC.

7812 A Service State Machine is activated when of one of the following signals is received: 7813 7814

a MAP request primitive, which activates a requesting SSM; a TC-INVOKE indication primitive without a linked identifier, which activates a performing SSM.

7815 For component handling primitives there are two types of event: 7816 7817

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.

7818
7819 7820 7821 7822 7823 7824 7825 7826 7827 7828

15.5.1 Service invocation

The behaviour of the requesting SSM which handles a service is defined by the SDL for the process Requesting_MAP_SSM. The requesting SSM receives a MAP service request from the MAP-Service User via the MAP dialogue state machine and sends a TC-INVOKE request to TCAP. When a confirm is received from TCAP via the MAP dialogue state machine, the requesting SSM forwards a MAP service confirm to the MAP-Service User. The response to a MAP service invocation may come in the form of a linked request. If the linked request corresponds to a class 4 operation, this is handled by the requesting SSM. If the linked request corresponds to a class 1, 2 or 3 operation, the MAP dialogue state machine sends a notification to the requesting SSM and creates an instance of a performing SSM to handle the linked request. The test "Linked_Operation_Allowed" on sheet 3 of the process Requesting_MAP_SSM takes the (TRUE) exit if the definition of the parent operation includes the received linked operation as a permitted linked operation; otherwise the test takes the (FALSE) exit.

7829 The mapping of MAP specific services on to remote operations is given in table 16.2/1.

918

3GPP

7830 7831

919 Release 7 920 921

231

3GPP TS 29.002 V7.5.0 (2006-09)

15.5.2 Void 15.5.3 Service invocation receipt

7832 7833 7834 7835 7836

The behaviour of the performing SSM which handles a service 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 TC-RESULT or TCU-ERROR component to TCAP.

7837 7838

15.5.4 Void 15.5.5 Handling of components received from TC

7839 The procedure Process_Components shows the handling of components received in a TC-BEGIN, TC-CONTINUE or 7840 TC-END message. 7841 7842 7843 7844

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.

7845

15.6 SDL descriptions

7846 The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. 7847 Such a system resides in each network component supporting MAP and communicates with its peers via the lower 7848 layers of the signalling network which are part of the environment. 7849 Only the MAP-provider is fully described in this clause. The various types of processes which form the MAP-User 7850 block and the TC block are described respectively in clauses 18 to 25 of the present document and in CCITT 7851 Recommendation Q.774. 7852 The MAP-Provider block communicates with the MAP_USER via two channels U1 and U2. Via U1 the MAP-provider 7853 receives the MAP request and response primitives. Via U2 it sends the MAP indication and confirm primitives. 7854 The MAP-Provider block communicates with TC via two channels P1 and P2. Via P1 the MAP-Provider sends all the 7855 TC request primitives. Via P2 it receives all the TC indication primitives. 7856 The MAP-Provider block is composed of the four following types of process: 7857 7858 7859 7860 7861 7862 7863 7864 7865

a) MAP_DSM: This type of process handles a dialogue for transport of MAP messages. There exists one process instance per MAP dialogue. b) Load_Ctrl: This type of process is in charge of load control. There is only one instance of this process in each system. c) Requesting_MAP_SSM: This type of process handles a MAP service requested during a dialogue. An instance of this process is created by the instance of the MAP_DSM process for each requested MAP service. d) Performing_MAP_SSM: This type of process handles a MAP service performed during a dialogue. An instance of this process is created by the instance of the MAP_DSM process for each MAP service to be performed.

7866 A process MAP_DSM exchanges external signals with other blocks as well as internal signals with the other processes 7867 of the MAP-Provider block. The external signals are either MAP service primitives or TC service primitives.

922

3GPP

7868 The signal routes used by the various processes are organised as follows: 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886

923 Release 7 924 925

232

3GPP TS 29.002 V7.5.0 (2006-09)

a) A process MAP_DSM receives and sends events from/to the MAP_user via signal route User1/User2. These routes use channels U1 and U2 respectively. b) A process MAP_DSM receives and sends events from/to the TCAP via signal route TC1/TC2. These routes use channels P1 and P2 respectively. c) A process MAP_DSM receives and sends events from/to the LOAD_CTRL process via signal route Load1/Load2. These routes are internal. d) A process MAP_DSM sends events to the Performing_MAP_SSM processes via signal route Intern1. This route is internal. e) A process MAP_DSM sends events to the Requesting_MAP_SSM processes via signal route Intern2. This route is internal. f) A process Performing_MAP_SSM sends events to the MAP_USER via signal route User3. This route uses channel U2. g) A process Performing_MAP_SSM sends events to the TCAP via signal route TC3. This route uses channel P1. h) A process Requesting_MAP_SSM sends events to the MAP_USER via signal route User4. This route uses channel U2. i) A process Requesting_MAP_SSM sends events to the TCAP via signal route TC4. This route uses channel P1.

926

3GPP

927 Release 7 928 929

233

3GPP TS 29.002 V7.5.0 (2006-09)

System MAP_Stack

Map_Stack1(1)

MAP_USER
U2

(MAP_REQ_SM)
U1

MAP_IND_SP

MAP_ Provider

P2

TC_REQ_SP
P1

TC_IND_SP

TCAP

7887
7888

Figure 15.6/1: System MAP_Stack

930

3GPP

931 Release 7 932 933

234

3GPP TS 29.002 V7.5.0 (2006-09)

Block MAPProvider

MAP_Provider1(1)

TC2 TC1 Intern2

MAP_DSM

User1 User2 Intern1

Load2 Load1 Load_Ctrl

TC4

Requesting_ _MAP_SSM

Performing_ _MAP_SSM

User3

TC3

User4

7889
7890

Figure 15.6/2: Block MAP_Provider

934

3GPP

935 Release 7 936 937

235

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue Comment 'MAP Dialogue State Machine'; DCL Components_Present, AC_Name_Unchanged, AC_Included, AC_Supported, Invoke_ID_Active, Last_Component, Operation_Exists, Alternative_Name_Exists, User_Info_Included BOOLEAN, Op_Code INTEGER;

MAP_DSM1(17)

IDLE

MAP_OPEN_ req

Store_AC_and_ user_data

For dialogue portion of TC-BEGIN

WAIT_FOR_ USER_ REQUESTS

7891
7892

Figure 15.6/3a: Process MAP_DSM (sheet 1)

938

3GPP

939 Release 7 940 941

236

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue

MAP_DSM2(17)

WAIT_FOR_ USER_ REQUESTS

Any MAP specific request primitive

MAP_req

MAP_ DELIMITER_ req

MAP_U_ ABORT_ req

Set_Abort_ Reason:User_ Specific

Set_User_Info: MAP_User_ Abort_PDU

TC_U_ABORT_ req_VIA_TC1

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

TC_BEGIN_ req_VIA_TC1

Terminated_ VIA_Intern2

To all active RSSMs

WAIT_FOR_ USER_ REQUESTS

DIALOGUE_ INITIATED

IDLE

7893
7894

Figure 15.6/3b: Process MAP_DSM (sheet 2)

942

3GPP

943 Release 7 944 945

237

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM3(17)

TC_END_ ind

TC_ NOTICE_ ind

(FALSE) AC_Name_ Unchanged (TRUE) Set_Provider_ Reason: Abnormal_ MAP_Dialogue Set_Refuse_ Reason: Node_ Not_Reachable Set_Result: Dialogue_Refused

MAP_P_ABORT_ ind_VIA_User2 Set_Result: Dialogue_ Accepted

MAP_OPEN_ cnf_VIA_User2

MAP_OPEN_ cnf_VIA_User2

(FALSE) Components_ Present (TRUE)

Process_ Components

MAP_CLOSE_ ind_VIA_User2

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

IDLE

7895
7896

Figure 15.6/3c: Process MAP_DSM (sheet 3)

946

3GPP

947 Release 7 948 949

238

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM4(17)

TC_P_ ABORT_ind

Incorrect_ Transaction_ Portion P-Abort_ Parameter No_Common_ Dialogue_Portion

Else

Set_Provider_ Reason: Version_ Incompatibility

Set_Result: Dialogue_Refused

MAP_P_ABORT ind_VIA_User2

Set_Refuse_Reason: Potential_Version_ Incompatibility

MAP_OPEN_ cnf_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

To all active RSSMs

Terminated_ VIA_Intern2

IDLE IDLE

7897
7898

Figure 15.6/3d: Process MAP_DSM (sheet 4)

950

3GPP

951 Release 7 952 953

239

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM5(17)

TC_U_ ABORT_ind

TC_L_ CANCEL_ind

AC_Not_Supported Abort_Reason User_Specific MAP_OPEN_ cnf_VIA_User2

Accepted. The dialogue is considered implictly accepted when something is received

(FALSE) Invoke_ID_ Active (TRUE)

Timer_Expiry_ VIA_Intern2

Set_Result: Dialogue_Refused

DIALOGUE_ INITIATED

Set_Refuse_ Reason: AC_ Not_Supported

MAP_OPEN_ cnf_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7899
7900

Figure 15.6/3e: Process MAP_DSM (sheet 5)

954

3GPP

955 Release 7 956 957

240

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue 4

MAP_DSM6(17)

User_ Information

User_Abort_PDU

Provider_Abort_PDU

Dialogue_Refused Set_Result: Dialogue_ Refused

No_User_Info Set_Result: Dialogue_ Refused

MAP_ Refuse_PDU_ Error

Invalid_ Destination_ Reference Set_Refuse_Reason: Invalid_Destination_ Reference

Invalid_ Originating_ Reference Set_Refuse_Reason: Invalid_Originating_ Reference

No_ Reason_ Given

Set_Refuse_Reason: No_Reason_Given

Set_Refuse_Reason: Potential_Version_ Incompatibility

MAP_P_ABORT_ ind_VIA_User2

MAP_P_ABORT_ ind_VIA_User2

MAP_OPEN_ cnf_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7901
7902

Figure 15.6/3f: Process MAP_DSM (sheet 6)

958

3GPP

959 Release 7 960 961

241

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM7(17)

MAP_U_ ABORT_req

MAP_CLOSE_ req

Set_Abort_Reason: User_Specific

Set_User_Info: MAP_User_ Abort_Info

Local

TC_U_ABORT_ req_VIA_TC1

Pre-arranged

TC_END_ req_VIA_TC1

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7903
7904

Figure 15.6/3g: Process MAP_DSM (sheet 7)

962

3GPP

963 Release 7 964 965

242

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED

MAP_DSM8(17)

TC_ CONTINUE_ ind

The first one

(FALSE) AC_Name_ Unchanged (TRUE)

Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue

MAP_P_ABORT_ ind_VIA_User2

Set_Result: Dialogue_ Accepted

Set_Abort_Reason_ User_Specific

MAP_OPEN_ cnf_VIA_User2

Set_User_Information: MAP_Provider_ Abort_Info

MAP_Provider_ Abort_Reason:= Abnormal_Dialogue

(FALSE) Components_ Present (TRUE) TC_U_ABORT_ req_VIA_TC1

Process_ Components

MAP_ DELIMITER_ req_VIA_User2

Terminated_ VIA_Intern2

To all active RSSMs

DIALOGUE_ ESTABLISHED

IDLE

7905
7906

Figure 15.6/3h: Process MAP_DSM (sheet 8)

966

3GPP

967 Release 7 968 969

243

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue IDLE

MAP_DSM9(17)

TC_BEGIN_ ind

(FALSE) AC_ Included (TRUE)

AC_Vession =1 (FALSE) (TRUE)

(FALSE)

MAP_ Dialogue_PDU_ included

(TRUE)

Extract_User_ Information

MAP-OPEN dialogue PDU? Yes Yes User_Info required for AC? No No Invalid Parameter?

No

Yes

(FALSE) Components_ Present (TRUE) Check_Load_ VIA_Load1 TC_U_ABORT_ req_VIA_TC1

WAIT_FOR_ LOAD_CHECK_ RESULT1

IDLE

WAIT_FOR_ INIT_DATA

7907
7908

Figure 15.6/3i: Process MAP_DSM (sheet 9)

970

3GPP

971 Release 7 972 973

244

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue

MAP_DSM10(17)

Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue

Set_User_Info: MAP_Provider_ Abort_Info

Set_Abort_Reason: User_Specific

TC_U_ABORT_ req_VIA_TC1

IDLE

7909
7910

Figure 15.6/3j: Process MAP_DSM (sheet 10)

974

3GPP

975 Release 7 976 977

245

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue

MAP_DSM11(17)

WAIT_FOR_ INIT_DATA

WAIT_FOR_ LOAD_CHECK_ RESULT2

TC_INVOKE_ ind (Op_Code)

TC_L_ REJECT_ ind

Any_ OTHER_ ind

Load_OK

Overload

(FALSE) Operation_ Exists (TRUE) IDLE

ELSE Derive_ V1_AC Op_Code begin_ subscriber_ activity (FALSE) Last_ Component (TRUE)

Check_Load_ VIA_Load1

TC_U_ ABORT_req VIA_TC1

TC_U_ ABORT_req VIA_TC1

Build_ MAP_OPEN_ind_ Primitive

WAIT_FOR_ LOAD_CHECK_ RESULT2

IDLE

MAP_OPEN_ ind_VIA_ User2

Perform_ version_1_ protocol

IDLE

7911
7912

Figure 15.6/3k: Process MAP_DSM (sheet 11)

978

3GPP

979 Release 7 980 981

246

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue WAIT_FOR_ LOAD_CHECK_ RESULT1

MAP_DSM12(17)

Load_OK

Overload

IDLE (FALSE) AC_ Supported (TRUE)

AC_Name:= Received_ AC_Name

(FALSE)

Alternative_ Name_ Exists (TRUE)

Set_ User_Data

AC_Name:= Received_ AC_Name

AC_Name:= Alternative_ AC_Name

MAP_OPEN_ ind_VIA_User2

(FALSE) Components_ Present (TRUE)

Process_ Components

Set_Abort_ Reason: AC_Not_ Supported

MAP_ DELIMITER_ ind_VIA_User2

TC_U_ABORT_ req_VIA_TC1

DIALOGUE_ PENDING

IDLE

7913
7914

Figure 15.6/3l: Process MAP_DSM (sheet 12)

982

3GPP

983 Release 7 984 985

247

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ PENDING

MAP_DSM13(17)

MAP_OPEN_ rsp

MAP_U_ ABORT_ req

Refused Result Accepted

Set_Abort_ Reason: User_Specific

Set_Abort_ Reason: User_Specific

Build_MAP_ Refuse_PDU

Set_User_Info: MAP_User_ Abort_Info

TC_U_ ABORT_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

DIALOGUE_ ACCEPTED

IDLE

7915
7916

Figure 15.6/3m: Process MAP_DSM (sheet 13)

986

3GPP

987 Release 7 988 989

248

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ACCEPTED

MAP_DSM14(17)

MAP_req

Any MAP specific request primitive

MAP_rsp

Any MAP specific response primitive

MAP_ DELIMITER_ req

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

Response_ Issued_ VIA_Intern1

TC_ CONTINUE_ req_VIA_TC1

DIALOGUE_ ACCEPTED

DIALOGUE_ ESTABLISHED

MAP_CLOSE_ req

MAP_U_ ABORT_ req

Set_Abort_ Reason: User_Specific

User_Info:= MAPUserAbortInfo

TC_END_ req_VIA_TC1

TC_U_ ABORT_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7917
7918

Figure 15.6/3n: Process MAP_DSM (sheet 14)

990

3GPP

991 Release 7 992 993

249

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM15(17)

MAP_req

Any MAP specific request primitive

MAP_rsp

Any MAP specific response primitive

MAP_ DELIMITER_ req

Requesting_ MAP_SSM

Service_ Invoked_ VIA_Intern2

Response_ Issued_ VIA_Intern1

TC_ CONTINUE_ req_VIA_TC1

DIALOGUE_ ESTABLISHED

DIALOGUE_ ESTABLISHED

TC_L_ CANCEL_ ind

TC_ NOTICE_ ind

TC_ CONTINUE_ ind

(FALSE) And SSM active Invoke_ ID_Active (TRUE) Components_ Present (TRUE)

(FALSE)

Process_ Components

Timer_Expiry_ VIA_Intern2

MAP_ NOTICE_ ind_VIA_User2

MAP_ DELIMITER_ ind_VIA_User2

DIALOGUE_ ESTABLISHED

7919
7920

Figure 15.6/30: Process MAP_DSM (sheet 15)

994

3GPP

995 Release 7 996 997

250

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM16(17)

TC_END_ ind

MAP_ CLOSE_ req

(FALSE) Components_ Present (TRUE)

Process_ Components

MAP_CLOSE_ ind_VIA_User2

TC_END_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7921
7922

Figure 15.6/3p: Process MAP_DSM (sheet 16)

998

3GPP

999 Release 7 1000 1001

251

3GPP TS 29.002 V7.5.0 (2006-09)

Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED

MAP_DSM17(17)

TC_U_ ABORT_ ind

TC_P_ ABORT_ ind

MAP_U_ ABORT_ req

Provider_Abort_PDU User_Info User_Abort_PDU

Set_Abort_ Reason: User_Specific

Set_User_Info: MAP_User_ Abort_Info

MAP_U_ ABORT_ ind_VIA_User2

MAP_P_ ABORT_ ind_VIA_User2

TC_U_ ABORT_ req_VIA_TC1

Terminated_ VIA_Intern1

To all active PSSMs

Terminated_ VIA_Intern2

To all active RSSMs

IDLE

7923
7924

Figure 15.6/3q: Process MAP_DSM (sheet 17)

1002

3GPP

7925

1003 Release 7 1004 1005

252

3GPP TS 29.002 V7.5.0 (2006-09)

Procedure Process_Components
Procedure to process components received in a TC message

Proc_Comp1(5)

Comment: 'Components from TCAP' DCL Op_Code, Operation_Class INTEGER, Operation_Exists, Last_Component, Invoke_ID_Present, Invoke_ID_Assigned, Linked_ID_Present, Linked_ID_Assigned, Linked_Operation_Allowed, v3_Or_Higher_Dialogue BOOLEAN;

WAIT_FOR_ COMPONENTS

TC_INVOKE_ ind(Op_Code)

Invoke_ ID_ Assigned (TRUE)

(FALSE)

(TRUE) For this AC Operation_ Exists (FALSE) Linked_ ID_ Present (TRUE)

(FALSE) Set_Problem_ Code: Duplicated_ Invoke_ID Set_Problem_ Code: Unrecognised_ Operation 1

TC_U_ REJECT_ req_VIA_TC1

TC_U_ REJECT_ req_VIA_TC1

Performing_ MAP_SSM

(FALSE)

v3_Or_ Higher_ Dialogue (TRUE)

Service_ Invocation_ Received_ VIA_Intern1

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

MAP_NOTICE_ ind_VIA_User2

(FALSE) Last_ Component (TRUE) WAIT_FOR_ COMPONENTS

7926
7927

Figure 15.6/4a: Procedure Process_Components (sheet 1)

1006

3GPP

1007 Release 7 1008 1009

253

3GPP TS 29.002 V7.5.0 (2006-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)

TC_U_REJECT_ req_VIA_TC1

Linked_ Service_ Invoked_ VIA_Intern2

Linked_ Request_ Received_ VIA_Intern2

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

Performing_ MAP_SSM

MAP_NOTICE_ ind_VIA_User2

Service_ Invocation_ Received_ VIA_Intern1

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7928
7929

Figure 15.6/4b: Procedure Process_Components (sheet 2)

1010

3GPP

1011 Release 7 1012 1013

254

3GPP TS 29.002 V7.5.0 (2006-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

(FALSE) Invoke_ID_ Assigned (TRUE) Invoke_ID_ Assigned (TRUE)

(FALSE) Invoke_ID_ Assigned (TRUE)

(FALSE)

Set_Problem_ Code: Invoke_ID_ Not_Assigned

TC_U_REJECT_ req_VIA_TC1

Set_Diagnostic: Abnormal_Event_ Received_ From_Peer

Result_ Received_ VIA_Intern2

Partial_ Result_ Received_ VIA_Intern2

Negative_ Result_ Received_ VIA_Intern2

MAP_NOTICE_ ind_VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7930
7931

Figure 15.6/4c: Procedure Process_Components (sheet 3)

1014

3GPP

1015 Release 7 1016 1017

255

3GPP TS 29.002 V7.5.0 (2006-09)

Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS

Proc_Comp4(5)

TC_L_ REJECT_ ind

TC_R_ REJECT_ ind

(FALSE) Invoke_ID_ Present (TRUE) rr_problem, re_problem, general_problem Problem Type invoke_problem Problem Type invoke_problem rr_problem, re_problem, general_problem

(FALSE) Invoke_ID_ Assigned (TRUE) Invoke_ID_ Assigned (TRUE)

(FALSE)

Provider_ Reject_ Received_ VIA_Intern2

MAP_ NOTICE_ind_ VIA_User2

Provider_ Reject_ Received_ VIA_Intern2

MAP_ NOTICE_ind_ VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7932
7933

Figure 15.6/4d: Procedure Process_Components (sheet 4)

1018

3GPP

1019 Release 7 1020 1021

256

3GPP TS 29.002 V7.5.0 (2006-09)

Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS

Proc_Comp5(5)

TC_U_ REJECT_ ind

rr_problem, re_problem Problem Type invoke_problem

(FALSE) Invoke_ID_ Assigned (TRUE)

User_Reject_ Received_ VIA_Intern2

MAP_ NOTICE_ind_ VIA_User2

(FALSE) Last_ Component (TRUE)

WAIT_FOR_ COMPONENTS

7934
7935

Figure 15.6/4e: Procedure Process_Components (sheet 5)

1022

3GPP

1023 Release 7 1024 1025

257

3GPP TS 29.002 V7.5.0 (2006-09)

Process Load_Ctrl
Process to verify whether offered dialogue should be discarded because of overload Comment 'LOAD CONTROL'; DCL Congestion, Dialogue_Acceptable BOOLEAN

Load_Ctrl1(1)

IDLE

Check_Load

(FALSE) Congestion

(TRUE)

(FALSE) Dialogue_ Acceptable (TRUE)

Load_OK_ VIA_Load2

Overload_ VIA_Load2

Load_OK_ VIA_Load2

IDLE

7936
7937

Figure 15.6/5: Process Load_Ctrl

1026

3GPP

1027 Release 7 1028 1029

258

3GPP TS 29.002 V7.5.0 (2006-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)

WAIT_FOR_ CONFIRM

7938
7939

Figure 15.6/6a: Process Requesting_MAP_SSM (sheet 1)

1030

3GPP

1031 Release 7 1032 1033

259

3GPP TS 29.002 V7.5.0 (2006-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

7940
7941

Figure 15.6/6b: Process Requesting_MAP_SSM (sheet 2)

1034

3GPP

1035 Release 7 1036 1037

260

3GPP TS 29.002 V7.5.0 (2006-09)

Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity WAIT_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

7942
7943

Figure 15.6/6c: Process Requesting_MAP_SSM (sheet 3)

1038

3GPP

1039 Release 7 1040 1041

261

3GPP TS 29.002 V7.5.0 (2006-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

7944
7945

Figure 15.6/6d: Process Requesting_MAP_SSM (sheet 4)

1042

3GPP

7946 7947 7948 7949

1043 Release 7 1044 1045

262

3GPP TS 29.002 V7.5.0 (2006-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: Data_Missing Set_Error: Unexpected_ Data_Value

(TRUE) Unexpected_ Data (FALSE) MAP_ind_ VIA_User3 Discard_ Invocation Set_Problem_ Code: Mistyped_ Parameter

(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

7950
3GPP

1046

7951

1047 Release 7 1048 1049

263

3GPP TS 29.002 V7.5.0 (2006-09)

Figure 15.6/8a: Process Performing_MAP_SSM (sheet 1)

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

7952
7953

Figure 15.6/8b: Process Performing_MAP_SSM (sheet 2)

1050

3GPP

7954 7955

1051 Release 7 1052 1053

264

3GPP TS 29.002 V7.5.0 (2006-09)

7956 7957

16

Mapping on to TC services
16.1 Dialogue control

7958 Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP 7959 PM.

7960

16.1.1 Directly mapped parameters

7961 The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the 7962 corresponding parameters of the TC-BEGIN primitives: 7963 7964

destination address; originating address.

7965 7966 16.1.2.1

16.1.2 Use of other parameters of dialogue handling primitives

Dialogue Id

7967 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

7968 16.1.2.2

Application-context-name

7969 The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of 7970 TC dialogue handling primitives according to the rules described in clause 15.1.

7971 16.1.2.3

User information

7972 The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs.

7973 16.1.2.4

Component present

7974 This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP 7975 user.

7976 16.1.2.5

Termination

7977 The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method 7978 parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE 7979 INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end".

7980 16.1.2.6
7981 7982 7983 7984 7985

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

7986 16.1.2.7

Quality of service

1054

3GPP

7987 The quality of service of TC request primitives is set by the MAP as shown below. 7988 7989 7990 7991 7992 7993

1055 Release 7 1056 1057

265

3GPP TS 29.002 V7.5.0 (2006-09)

Return option: "Return message on error" or "Discard message on error" as required by the network operator; Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the network operator; "Sequence guaranteed" shall be used when a segmented result is to be transferred (e.g. subscriber data in response to SendParameters). It may also be appropriate to use Sequence guaranteed when a series of InsertSubscriberData, ProcessAccessSignalling or ForwardAccessSignalling operations is used.

7994 It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue 7995 initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue 7996 responder shall ensure that this requirement is met by: 7997 7998 7999 8000 8001 8002

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.

8003

8004

16.2 Service specific procedures

16.2.1 Directly mapped parameters

8005 Specific services are mapped to TC component handling services.

8006

8007 The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter 8008 of the component handling primitives.

8009 8010 16.2.2.1

16.2.2 Use of other parameters of component handling primitives

Dialogue Id

8011 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.

8012 16.2.2.2

Class

8013 The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.

8014 16.2.2.3

Linked Id

8015 When a service response is mapped to a class 4 operation, the value of this parameter is set by the MAP PM and 8016 corresponds to the value assigned by the user to the initial service request (i.e. the value of the invoke ID parameter of

1058

3GPP

8017 the request primitive). Otherwise if such a parameter is included in MAP request/indication primitives it is directly 8018 mapped to the linked ID parameter of the associated TC-INVOKE request/indication primitives.

1059 Release 7 1060 1061

266

3GPP TS 29.002 V7.5.0 (2006-09)

8019 16.2.2.4

Operation

8020 When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code 8021 according to the mapping described in table 16.2/1. 8022 When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the 8023 TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time. 8024

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-SEND_GROUP-CALL_END_SIGNAL MAP-SEND-GROUP-CALL-INFO MAP-SEND-END-SIGNAL MAP-SEND-AUTHENTICATION-INFO 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 sendGroupCallEndSignal sendGroupCallInfo sendEndSignal sendAuthenticationInfo

1062

3GPP

1063 Release 7 267 1064 1065 MAP-SEND-IMSI MAP-SEND-IDENTIFICATION MAP-SEND-ROUTING-INFO-FOR-SM MAP-SEND-ROUTING-INFO-FOR-GPRS MAP-SEND-ROUTING-INFO-FOR-LCS MAP-SEND-ROUTING-INFORMATION MAP-SET-REPORTING-STATE MAP-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 8025

3GPP TS 29.002 V7.5.0 (2006-09) sendIMSI sendIdentification sendRoutingInfoForSM sendRoutingInfoForGprs sendRoutingInfoForLCS sendRoutingInfo setReportingState statusReport subscriberLocationReport ss-Invocation-Notification unstructuredSS-Notify unstructuredSS-Request updateGprsLocation updateLocation NoteMM-Event

8026 16.2.2.5

Error

8027 The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm 8028 primitive of the service associated with the operation to which the error is attached. 8029 The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request 8030 primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of 8031 the TC-U-REJECT request primitive.

8032 16.2.2.6

Parameters

8033 The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC8034 INVOKE primitives. 8035 The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L 8036 primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on 8037 linked class 4 operations is used.

8038 16.2.2.7

Time out

8039 The value of this parameter is set by the MAP PM according to the type of operation invoked.

8040 16.2.2.8

Last component

8041 This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP 8042 user.

8043 16.2.2.9 8044 16.2.2.9.1

Problem code
Mapping to MAP User Error

8045 The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. 8046 These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the 8047 MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive. 8048 8049

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

8050

1066

3GPP

8051 16.2.2.9.2

1067 Release 7 1068 1069

268

3GPP TS 29.002 V7.5.0 (2006-09)

Mapping to MAP Provider Error parameter

8052 The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as 8053 follows to values of the MAP Provider Error parameter of the MAP confirm primitive. 8054

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

8055 8056 The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the 8057 provider error parameter of the MAP confirm primitive as follows. 8058

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

8059

8060 16.2.2.9.3

Mapping to diagnostic parameter

8061 The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to 8062 values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: 8063 8064

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 - response rejected - response rejected - response rejected - response rejected by the peer by the peer by the peer by the peer by the peer

8065 8066 The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the 8067 diagnostic parameter of the MAP-NOTICE indication primitive as follows. 8068

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

8069

1070

3GPP

1071 Release 7 1072 1073

269

3GPP TS 29.002 V7.5.0 (2006-09)

8070 8071
8072 8073 8074 8075

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.

8076 The Abstract Syntax is defined for all interfaces specified in clause 4.4 except for the A- and B-interfaces. 8077 The Mobile Application Part protocol is defined by two Abstract Syntaxes: 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089

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.

8090

17.1.1 Encoding rules

8091 The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract 8092 Syntax Notation One, defined in ITU-T Recommendation X.690 with the same exceptions as in ITU-T 8093 Recommendation Q.773, clause 4 Message Representation. 8094 When the definite form is used for length encoding, a data value of length less than 128 octets must have the length 8095 encoded in the short form. 8096 When the long form is employed to code a length, the minimum number of octets shall be used to code the length field. 8097 OCTET STRING values and BIT STRING values must be encoded in a primitive form. 8098 There is no restriction to the use of empty constructors (e.g. an empty SEQUENCE type). That is, the encoding of the 8099 content of any data value shall consist of zero, one or more octets.

8100

17.1.2 Use of TC

8101 The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on 8102 ITU-T Recommendation Q.773. 8103 8104 8105 8106 8107

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.

8108 The field "ARGUMENT", "PARAMETER" or "RESULT" (for information objects of class OPERATION and 8109 ERROR) is always optional from a syntactic point of view. However, except when specifically mentioned with the

1074

3GPP

8110 ASN.1 comment "-- optional" , the "parameter" part of a component has to be considered as mandatory from a semantic 8111 point of view. 8112 8113 8114 8115 8116 8117

1075 Release 7 1076 1077

270

3GPP TS 29.002 V7.5.0 (2006-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".

8118 The Timer Values used in the operation definitions are indicated as ASN.1 comments. The Timer Value Ranges are: 8119 8120 8121 8122

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

8123 17.1.2.1
8124 8125 8126 8127 8128 8129 8130 8131 8132

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.

8133 Handling of an unknown operation codes by the receiving entity is defined in clause 15.1.1.

8134

17.1.3 Use of information elements defined outside MAP

8135 An information element or a set of information elements (messages) transparently carried in the Mobile Application 8136 Part but defined in other recommendations/technical specifications are handled in one of the following ways: 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146

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.

8147

17.1.4 Compatibility considerations

8148 The following ASN.1 modules conform to ITU-T Recommendation X.680 and X.681 . An extension marker ("...") is 8149 used wherever future protocol extensions are foreseen. 8150 The "..." construct applies only to SEQUENCE and ENUMERATED data types. An entity supporting a version greater 8151 than 1 shall not reject an unsupported extension following "..." of that SEQUENCE or ENUMERATED data type. The

1078

3GPP

8152 Encoding Rules from clause 17.1.1 apply to every element of the whole Transfer Syntax especially to the ASN.1 type 8153 EXTERNAL. 8154 The extension container "privateExtensionList" is defined in this specification in order to carry extensions which are 8155 defined outside this specification. Private extensions can be defined by, for example, network operators, manufacturers, 8156 and regional standardisation bodies. 8157 Private extensions shall: 8158 8159 8160 8161 8162 8163

1079 Release 7 1080 1081

271

3GPP TS 29.002 V7.5.0 (2006-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.

8164 Private extensions shall not be included in v2 supplementary service operations. 8165 Private extensions shall not be included within user error for RegisterCCEntry and EraseCCEntry operations. 8166 PCS extensions shall be included in the PCS Extension Container that is defined in this specification. 8167 8168 8169 8170

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.

8171
8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191

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

1082

3GPP

8192 8193 8194 8195 8196

1083 Release 7 1084 1085

272

3GPP TS 29.002 V7.5.0 (2006-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.

8197 The module containing the definition of the operation packages for MAP is: 8198

1. MAP-OperationPackages.

8199 The module containing the definition of the application contexts for MAP is: 8200

2. MAP-ApplicationContexts.

8201 The module containing the data types for the Abstract Syntax to be used for TCAPMessages.DialoguePortion for MAP 8202 is: 8203

3. MAP-DialogueInformation.

8204 The module containing the supported operations is: 8205

4. MAP-Protocol.

8206 The modules containing all operation definitions for MAP are: 8207 8208 8209 8210 8211 8212 8213

5. MAP-MobileServiceOperations; 6. MAP-OperationAndMaintenanceOperations; 7. MAP-CallHandlingOperations; 8. MAP-SupplementaryServiceOperations; 9. MAP-ShortMessageServiceOperations; 10. MAP-Group-Call-Operations; 11. MAP-LocationServiceOperations.

8214 The module containing all error definitions for MAP is: 8215

12. MAP-Errors.

8216 Modules containing all data type definitions for MAP are: 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228

13. MAP-MS-DataTypes; 14. MAP-OM-DataTypes; 15. MAP-CH-DataTypes; 16. MAP-SS-DataTypes; 17. MAP-SS-Code; 18. MAP-SM-DataTypes; 19. MAP-ER-DataTypes; 20. MAP-CommonDataTypes; 21. MAP-TS-Code; 22. MAP-BS-Code; 23. MAP-ExtensionDataTypes; 24. MAP-GR-DataTypes;

1086

3GPP

8229

1087 Release 7 1088 1089

273

3GPP TS 29.002 V7.5.0 (2006-09)

25. MAP-LCS-DataTypes.

8230 References are made also to modules defined outside of the present document. They are defined in the technical 8231 specification Mobile Services Domain, technical specification Transaction Capability and ITU-T Recommendation 8232 X.880 respectively: 8233 8234 8235

MobileDomainDefinitions; TCAPMessages, DialoguePDUs ; Remote-Operations-Information-Objects.

8236

17.1.6 Application Contexts

8237 The following informative table lists the latest versions of the Application Contexts used in this specification, with the 8238 operations used by them and, where applicable, whether or not the operation description is exactly the same as for 8239 previous versions. Information in 17.6 & 17.7 relates only to the ACs in this table. 8240

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 mt-forwardSM-VGCS sendRoutingInfoForSM reportSM-DeliveryStatus InformServiceCentre updateLocation forwardCheckSs-Indication restoreData insertSubscriberData activateTraceMode updateGprsLocation insertSubscriberData activateTraceMode insertSubscriberData deleteSubscriberData

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 shortMsgMT-VGCS-RelayContext shortMsgGatewayContext

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

v3 v3

1090

3GPP

1091 Release 7 1092 1093

274

3GPP TS 29.002 V7.5.0 (2006-09)

AC Name

AC Version
v3 v3 v3 v4 v3 v4 v3 v3 v3 v3 v3

Operations Used
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 releaseResources sendGroupCallInfo

Comments

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 resourceManagementContext groupCallInfoRetievalContext v3 V3

8241 8242

NOTE (*):

The syntax of the operations is not the same as in previous versions unless explicitly stated

8276 8277

17.2 Operation packages

17.2.1 General aspects

8278 This clause describes the operation-packages which are used to build the application-contexts defined in clause 17.3. 8279 Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), 8280 in terms of operations which they can invoke of each other. 8281 The grouping of operations into one or several packages does not necessarily imply any grouping in terms of 8282 Application Service Elements. 8283 The following ASN.1 information object class is used to describe operation-packages in this clause:
8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294

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 }

8295 Since the application-context definitions provided in clause 17.3 use only an informal description technique, only the 8296 type notation is used in the following clauses to define operation-packages.

1094

3GPP

8297 The following definitions are used throughout this clause (n>=2): 8298 8299 8300 8301 8302 8303 8304 8305

1095 Release 7 1096 1097

275

3GPP TS 29.002 V7.5.0 (2006-09)

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.

8306 The names of vn-packages are suffixed by "-vn" where n>=2. 8307 For each operation package which is not vn-only (n>=2) and which does not include only v(n-1)-operations, there is a 8308 v(n-1)-equivalent package. Except when a definition is explicitly provided in the following clauses, the 8309 v(n-1)-equivalent package includes the v(n-1)-equivalent operations of the operations which belong to this package.

8310 8311 17.2.2.1

17.2.2 Packages specifications

Location updating

8312 This operation package includes the operations required for location management procedures between HLR and VLR.
8313 8314 8315 8316 8317 8318 8319

locationUpdatingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { updateLocation} SUPPLIER INVOKES { forwardCheckSs-Indication} }

8320 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8321 17.2.2.2

Location cancellation

8322 This operation package includes the operations required for location cancellation and MS purging procedures between 8323 HLR and VLR and between HLR and SGSN.
8324 8325 8326 8327 8328

locationCancellationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { cancelLocation} }

8329 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8330 17.2.2.3

Roaming number enquiry

8331 This operation package includes the operations required for roaming number enquiry procedures between HLR and 8332 VLR.
8333 8334 8335 8336 8337

roamingNumberEnquiryPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideRoamingNumber} }

8338 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

1098

3GPP

8339 17.2.2.4

1099 Release 7 1100 1101

276

3GPP TS 29.002 V7.5.0 (2006-09)

Information retrieval

8340 This operation package includes the operation required for the authentication information retrieval procedure between 8341 HLR and VLR and between HLR and SGSN.
8342 8343 8344 8345 8346 8347

infoRetrievalPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo} }

8348 The v2-equivalent package is defined as follows:

8349 8350 8351 8352 8353 8354

infoRetrievalPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo} }

8355 The v1-equivalent package is defined as follows:

8356 8357 8358 8359 8360 8361

infoRetrievalPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR or VLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendParameters} }

8362 17.2.2.5

Inter-VLR information retrieval

8363 This operation package includes the operations required for inter VLR information retrieval procedures.
8364 8365 8366 8367 8368

interVlrInfoRetrievalPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification} }

8369 The v2-equivalent package is defined as follows:

8370 8371 8372 8373 8374

interVlrInfoRetrievalPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification} }

8375 The v1-equivalent package is : infoRetrievalPackage-v1.

8376 17.2.2.6

IMSI retrieval

8377 This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR.
8378 8379 8380 8381 8382

imsiRetrievalPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { sendIMSI} }

8383 This package is v2 only.

8384 17.2.2.7

Call control transfer

8385 This operation package includes the operation required for the call control transfer procedure between VMSC and 8386 GMSC.
8387 8388 8389 8390 8391

callControlTransferPackage-v4 OPERATION-PACKAGE ::= { -- Supplier is GMSC if Consumer is VMSC CONSUMER INVOKES { resumeCallHandling} }

8392 The v3-equivalent package can be determined according to the rules described in clause 17.2.1.

1102

3GPP

8393 17.2.2.8 8394 17.2.2.9 8395 17.2.2.10

1103 Release 7 1104 1105

277

3GPP TS 29.002 V7.5.0 (2006-09)

Void Void Interrogation

8396 This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR 8397 or between HLR and gsmSCF.
8398 8399 8400 8401 8402 8403

interrogationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR or NPLR if Consumer is MSC -- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { sendRoutingInfo} }

8404 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8405 17.2.2.11 8406 17.2.2.12

Void Handover Control

8407 This operation package includes the operations required for handover procedures between MSCs.
8408 8409 8410 8411 8412 8413 8414 8415 8416 8417

handoverControlPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { prepareHandover | forwardAccessSignalling} SUPPLIER INVOKES { sendEndSignal | processAccessSignalling | prepareSubsequentHandover} }

8418 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 8419 The v1-equivalent package is defined as follows.
8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431

handoverControlPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { performHandover | forwardAccessSignalling | traceSubscriberActivity} SUPPLIER INVOKES { sendEndSignal | noteInternalHandover | processAccessSignalling | performSubsequentHandover} }

8432 17.2.2.13

Subscriber Data management stand alone

8433 This operation package includes the operations required for stand alone subscriber data management procedures 8434 between HLR and VLR or between HLR and SGSN.
8435 8436 8437 8438 8439 8440

subscriberDataMngtStandAlonePackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData | deleteSubscriberData} }

8441 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

1106

3GPP

8442 17.2.2.14

1107 Release 7 1108 1109

278

3GPP TS 29.002 V7.5.0 (2006-09)

Equipment management

8443 This operation package includes the operations required for equipment management procedures between EIR and MSC 8444 or between EIR and SGSN.
8445 8446 8447 8448 8449 8450

equipmentMngtPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is EIR if Consumer is MSC -- Supplier is EIR if Consumer is SGSN CONSUMER INVOKES { checkIMEI} }

8451 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8452 17.2.2.15

Subscriber data management

8453 This operation package includes the operations required for subscriber data management procedures between HLR and 8454 VLR or between HLR and SGSN.
8455 8456 8457 8458 8459

subscriberDataMngtPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData} }

8460 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8461 17.2.2.16

Location register restart

8462 This operation package includes the operations required for location register restart procedures between HLR and VLR 8463 or between HLR and SGSN.
8464 8465 8466 8467 8468

resetPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { reset} }

8469 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

8470 17.2.2.17

Tracing stand-alone

8471 This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or 8472 between HLR and SGSN.
8473 8474 8475 8476 8477 8478

tracingStandAlonePackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode | deactivateTraceMode} }

8479 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8480 17.2.2.18

Functional SS handling

8481 This operation package includes the operations required for functional supplementary services procedures between VLR 8482 and HLR.
8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494

functionalSsPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerSS | eraseSS | activateSS | deactivateSS | registerPassword | interrogateSS} SUPPLIER INVOKES { getPassword} }

8495 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

1110

3GPP

8496 17.2.2.19

1111 Release 7 1112 1113

279

3GPP TS 29.002 V7.5.0 (2006-09)

Tracing

8497 This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR 8498 and SGSN.
8499 8500 8501 8502 8503

tracingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode} }

8504 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.

8505 17.2.2.20

Binding

8506 This operation package includes the operation required to initialise a supplementary service procedure between VLR 8507 and HLR or between gsmSCF and HLR.
8508 8509 8510 8511 8512

bindingPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { beginSubscriberActivity} }

8513 This package is v1 only.

8514 17.2.2.21

Unstructured SS handling

8515 This operation package includes the operations required for unstructured supplementary services procedures between 8516 VLR and HLR, between the HLR and the gsmSCF, and between HLR and HLR.
8517 8518 8519 8520 8521 8522 8523 8524 8525

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

8526 The v1-equivalent package is defined as follows:

8527 8528 8529 8530 8531 8532

unstructuredSsPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Data} }

8533 17.2.2.22

MO Short message relay services

8534 This operation package includes the operations required for short message relay service procedures between IWMSC 8535 and VMSC or between GMSC and MSC or between SGSN and IWMSC.
8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549

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

8550 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.

1114

3GPP

8551 17.2.2.23

1115 Release 7 1116 1117

280

3GPP TS 29.002 V7.5.0 (2006-09)

Short message gateway services

8552 This operation package includes the operations required for short message service gateway procedures between MSC 8553 and HLR.
8554 8555 8556 8557 8558 8559 8560 8561 8562

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.

8563 The v1-equivalent package is defined as follows:

8564 8565 8566 8567 8568 8569

shortMsgGatewayPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM | reportSMDeliveryStatus} }

8570 17.2.2.24

MT Short message relay services

8571 This operation package includes the operations required for short message relay service procedures between GMSC and 8572 MSC or between GMSC and SGSN.
8573 8574 8575 8576 8577

mt-ShortMsgRelayPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is MSC or SGSN if Consumer is GMSC CONSUMER INVOKES { mt-forwardSM} }

8578 The v2-equivalent package is: shortMsgRelayPackage-v2

8579 17.2.2.25 8580 17.2.2.26

Void Message waiting data management

8581 This operation package includes the operations required for short message waiting data procedures between HLR and 8582 VLR, between HLR and SGSN.
8583 8584 8585 8586 8587 8588

mwdMngtPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is SGSN -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { readyForSM} }

8589 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.
8590

8591 The v1-equivalent package is defined as follows:

8592 8593 8594 8595 8596

mwdMngtPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { noteSubscriberPresent} }

8597 17.2.2.27

Alerting

8598 This operation package includes the operations required for alerting between HLR and IWMSC.
8599 8600 8601 8602 8603

alertingPackage-v2 OPERATION-PACKAGE ::= { -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentre} }

1118

3GPP

8604 The v1-equivalent package is defined as follows.

8605 8606 8607 8608 8609

1119 Release 7 1120 1121

281

3GPP TS 29.002 V7.5.0 (2006-09)

alertingPackage-v1 OPERATION-PACKAGE ::= { -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentreWithoutResult} }

8610 17.2.2.28

Data restoration

8611 This operation package includes the operations required for VLR data restoration between HLR and VLR.
8612 8613 8614 8615 8616

dataRestorationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { restoreData} }

8617 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 8618 The v1-equivalent package is: infoRetrievalPackage-v1

8619 17.2.2.29

Purging

8620 This operation package includes the operations required for purging between HLR and VLR or between HLR and 8621 SGSN.
8622 8623 8624 8625 8626 8627

purgingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { purgeMS} }

8628 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.

8629 17.2.2.30

Subscriber information enquiry

8630 This operation package includes the operations required for subscriber information enquiry procedures between HLR 8631 and VLR or between HLR and SGSN.
8632 8633 8634 8635 8636

subscriberInformationEnquiryPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { provideSubscriberInfo} }

8637 This package is v3 only.

8638 17.2.2.31

Any time information enquiry

8639 This operation package includes the operations required for any time information enquiry procedures between gsmSCF 8640 and HLR or between gsmSCF and GMLC or between gsmSCF and NPLR.
8641 8642 8643 8644 8645

anyTimeInformationEnquiryPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR or GMLC or NPLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeInterrogation} }

8646 This package is v3 only.

1122

3GPP

8647 17.2.2.32

1123 Release 7 1124 1125

282

3GPP TS 29.002 V7.5.0 (2006-09)

Group Call Control

8648 This operation package includes the operations required for group call and broadcast call procedures between MSCs.
8649 8650 8651 8652 8653 8654 8655 8656 8657

groupCallControlPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is relay MSC if Consumer is anchor MSC CONSUMER INVOKES { prepareGroupCall | forwardGroupCallSignalling} SUPPLIER INVOKES { sendGroupCallEndSignal | processGroupCallSignalling} }

8658 This package is v3 only.

8659 17.2.2.32A

Group Call Info Retrieval

8660 This operation package includes the operations required for group call and broadcast call info retrieval between MSCs.
8661 8662 8663 8664 8665 8666

groupCallInfoRetrievalPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is group call serving MSC if Consumer is visited MSC -- Supplier is visited MSC if Consumer is group call serving MSC CONSUMER INVOKES { sendGroupCallInfo} }

8667 This package is v3 only.

8668 17.2.2.33 8669 17.2.2.34 8670 17.2.2.35

Void Void Gprs location updating

8671 This operation package includes the operations required for the gprs location management procedures between HLR 8672 and SGSN.
8673 8674 8675 8676

gprsLocationUpdatingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { updateGprsLocation} }

8677 8678 This package is v3 only.

1126

3GPP

8679 17.2.2.36

1127 Release 7 1128 1129

283

3GPP TS 29.002 V7.5.0 (2006-09)

Gprs Interrogation

8680 This operation package includes the operations required for interrogation procedures between HLR and GGSN.
8681 8682 8683 8684

gprsInterrogationPackage-v4 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs} }

8685 8686 The v3-equivalent package is defined as follows. 8687

8688 8689 8690 8691

gprsInterrogationPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs} }

8692

8693 17.2.2.37

Failure reporting

8694 This operation package includes the operations required for failure reporting between HLR and GGSN.
8695 8696 8697 8698

failureReportingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { failureReport} }

8699 8700 This package is v3 only.

8701 17.2.2.38

GPRS notifying

8702 This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and 8703 GGSN.
8704 8705 8706 8707

gprsNotifyingPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is GGSN if Consumer is HLR CONSUMER INVOKES { noteMsPresentForGprs} }

8708 8709 This package is v3 only.

8710 17.2.2.39

Supplementary Service invocation notification

8711 This operation package includes the operations required for Supplementary Service invocation notification procedures 8712 between the MSC and the gsmSCF and between the HLR and the gsmSCF.
8713 8714 8715 8716 8717 8718

ss-InvocationNotificationPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is gsmSCF if Consumer is MSC -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { ss-InvocationNotification} }

8719 This package is v3 only.

1130

3GPP

8720 17.2.2.40

1131 Release 7 1132 1133

284

3GPP TS 29.002 V7.5.0 (2006-09)

Set Reporting State

8721 This operation package includes the operation required for procedures between HLR and VLR to set the reporting state.
8722 8723 8724 8725 8726

setReportingStatePackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { setReportingState} }

8727 This package is v3 only.

8728 17.2.2.41

Status Report

8729 This operation package includes the operation required for procedures between VLR and HLR to report call results and 8730 events.
8731 8732 8733 8734 8735

statusReportPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { statusReport} }

8736 This package is v3 only.

8737 17.2.2.42

Remote User Free

8738 This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free.
8739 8740 8741 8742 8743

remoteUserFreePackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { remoteUserFree} }

8744 This package is v3 only.

8745 17.2.2.43

Call Completion

8746 This operation package includes the operations required for procedures between VLR and HLR for subscriber control of 8747 call completion services.
8748 8749 8750 8751 8752 8753

callCompletionPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerCC-Entry | eraseCC-Entry} }

8754 This package is v3 only.

8755 17.2.2.44

Location service gateway services

8756 This operation package includes the operations required for location service gateway procedures between GMLC and 8757 HLR.
8758 8759 8760 8761 8762 8763

locationSvcGatewayPackage-v3 OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is GMLC CONSUMER INVOKES { sendRoutingInfoForLCS} }

This package is v3 only.

8764 17.2.2.45

Location service enquiry

8765 This operation package includes the operations required for the location service enquiry procedures between GMLC and 8766 MSC and between GMLC and SGSN.

1134

3GPP

1135 Release 7 1136 1137 8767 locationSvcEnquiryPackage-v3

8768 8769 8770 8771

285

3GPP TS 29.002 V7.5.0 (2006-09)

OPERATION-PACKAGE ::= { -- Supplier is MSC or SGSN if Consumer is GMLC CONSUMER INVOKES { provideSubscriberLocation} }

8772 This package is v3 only.

8773 17.2.2.45A

Location service reporting

8774 This operation package includes the operations required for the location service enquiry procedures between MSC and 8775 GMLC and between SGSN and GMLC.
8776 8777 8778 8779 8780

locationSvcReportingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is GMLC if Consumer is MSC -- Supplier is GMLC if Consumer is SGSN CONSUMER INVOKES { subscriberLocationReport} }

8781 8782 17.2.2.46 8783 17.2.2.47 8784 17.2.2.48 8785 17.2.2.49 Void Void Void IST Alerting

8786 This operation package includes the operation required for alerting procedures between the MSC (Visited MSC or 8787 Gateway MSC) and HLR.
8788 8789 8790 8791 8792 8793

ist-AlertingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is VMSC -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { istAlert} }

8794 This package is v3 only.

8795 17.2.2.50

Service Termination

8796 This operation package includes the operation required for immediate service termination procedures between the HLR 8797 and the Visited MSC or between the HLR and the Gateway MSC.
8798 8799 8800 8801 8802

serviceTerminationPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VMSC or GMSC if Consumer is HLR CONSUMER INVOKES { istCommand} }

8803 This package is v3 only.

8804 17.2.2.51

Mobility Management event notification

8805 This operation package includes the operations required for Mobility Management event notification procedures 8806 between VLR and gsmSCF.
8807 8808 8809 8810

mm-EventReportingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is gsmSCF if Consumer is VLR CONSUMER INVOKES { noteMM-Event} }

8811 This package is v3 only.

1138

3GPP

8812 17.2.2.52

1139 Release 7 1140 1141

286

3GPP TS 29.002 V7.5.0 (2006-09)

Any time information handling

8813 This operation package includes the operations required for any time information handling procedures between gsmSCF 8814 and HLR.
8815 8816 8817 8818 8819 8820

anyTimeInformationHandlingPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeSubscriptionInterrogation | anyTimeModification} }

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

8822 17.2.2.54

Authentication Failure Report

8823 This operation package includes the operation required for procedures between VLR and HLR or the SGSN and the 8824 HLR for reporting of authentication failures.
8825 8826 8827 8828 8829 8830

authenticationFailureReportPackage-v3

-- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { authenticationFailureReport} }

OPERATION-PACKAGE ::= {

8831 This package is v3 only.

8832 17.2.2.55

Resource Management

8833 This operation package includes the operation required for procedures between GMSC and VMSC for resource 8834 management purpose.
8835 8836 8837 8838 8839

resourceManagementPackage-v3

OPERATION-PACKAGE ::= { -- Supplier is VMSC if Consumer is GMSC CONSUMER INVOKES { releaseResources} }

8840 This package is v3 only.

8841 17.2.2.56

MT Short message relay VGCS services

8842 This operation package includes the operations required for short message relay service procedures between SMS 8843 GMSC and MSC.
8844 8845 8846 8847 8848

mt-ShortMsgRelay-VGCS-Package-v3 OPERATION-PACKAGE ::= { -- Supplier is MSC if Consumer is GMSC CONSUMER INVOKES { mt-forwardSM-VGCS} }

8849 This package is v3 only.

1142

3GPP

1143 Release 7 1144 1145

287

3GPP TS 29.002 V7.5.0 (2006-09)

8850 8851

17.3 Application contexts

17.3.1 General aspects

8852 An application-context is assigned for each dialogue established by a MAP-user. In the present document each 8853 application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and 8854 transmitted to the peer under certain circumstances. 8855 The following ASN.1 information object class is used to describe the main aspects of application-contexts in the 8856 following clauses:
8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867

APPLICATION-CONTEXT ::= CLASS { &Symmetric OPERATION-PACKAGE OPTIONAL, &InitiatorConsumerOf OPERATION-PACKAGE OPTIONAL, &ResponderConsumerOf OPERATION-PACKAGE OPTIONAL, &code OBJECT IDENTIFIER } WITH SYNTAX { [ OPERATIONS OF &Symmetric ] [ INITIATOR CONSUMER OF &InitiatorConsumerOf RESPONDER CONSUMER OF &ResponderConsumerOf ] ID &code }

8868 8869 The following definitions are used throughout this clause: 8870 8871 8872

v1-application-context: An application-context which contains only v1-packages and uses only TC v1 facilities; v1 context set: the set of v1-application-contexts defined in the present document. vn-application-context (n>=2): An application-context which contains only vn-packages;

8873 The names of v1-application-contexts are suffixed by "-v1" while other names are suffixed by "-vn" where n>=2. 8874 Application-contexts which do not belong to the v1 context set use v2 TC facilities. 8875 The last component of each application-context-name (i.e. the last component of the object identifier value) assigned to 8876 an application-context which belongs to the v1 context set indicates explicitly "version1". 8877 For each application-context which does not belong to the "v1 context set" there is a v1-equivalent application context. 8878 This is a v1-application-context which includes the v1-equivalents of the packages included in the original context. 8879 Each application-context uses the abstract-syntax associated with the operation-packages it includes and uses the 8880 transfer-syntax derived from it by applying the encoding rules defined in clause 17.1.1. 8881 ACs which do not belong to the v1 context set require the support of the abstract-syntax identified by the object 8882 identifier value: MAP-DialogueInformation.map-Dialogue-AS defined in clause 17.4.

8883 8884 17.3.2.1 8885 17.3.2.2

17.3.2 Application context definitions

Void Location Updating

8886 This application context is used between HLR and VLR for location updating procedures.
8887 8888 8889 8890 8891 8892 8893 8894 8895 8896

networkLocUpContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { locationUpdatingPackage-v3 | dataRestorationPackage-v3} RESPONDER CONSUMER OF { subscriberDataMngtPackage-v3 | tracingPackage-v3} ID {map-ac networkLocUp(1) version3(3)} }

1146

3GPP

8897 The following application-context-name is assigned to the v2-equivalent application-context:

8898 8899

1147 Release 7 1148 1149

ID

288

3GPP TS 29.002 V7.5.0 (2006-09)

{map-ac networkLocUp(1) version2(2)}

8900 The following application-context-name is assigned to the v1-equivalent application-context:

8901 8902

ID

{map-ac networkLocUp(1) version1(1)}

8903 17.3.2.3

Location Cancellation

8904 This application context is used between HLR and VLR or between HLR and SGSN for location cancellation 8905 procedures. For the HLR - SGSN interface only version 3 of this application context is applicable.
8906 8907 8908 8909 8910 8911

locationCancellationContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { locationCancellationPackage-v3} ID {map-ac locationCancel(2) version3(3)} }

8912 The following application-context-name is assigned to the v2-equivalent application-context:

8913

ID

map-ac locationCancel(2) version2(2)

8914 8915 The following application-context-name is assigned to the v1-equivalent application-context:

8916 8917

ID

map-ac locationCancel(2) version1(1)

8918 17.3.2.4

Roaming number enquiry

8919 This application context is used between HLR and VLR for roaming number enquiry procedures.
8920 8921 8922 8923 8924 8925

roamingNumberEnquiryContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { roamingNumberEnquiryPackage-v3} ID {map-ac roamingNbEnquiry(3) version3(3)} }

8926 The following application-context-name is assigned to the v2-equivalent application-context:

8927 8928

ID

{map-ac roamingNbEnquiry(3) version2(2)}

8929 The following application-context-name is assigned to the v1-equivalent application-context:

8930 8931

ID

{map-ac roamingNbEnquiry(3) version1(1)}

8932 17.3.2.5 8933 17.3.2.6

Void Location Information Retrieval

8934 This application-context is used between GMSC and HLR or between GMSC and NPLR or between gsmSCF and HLR 8935 when retrieving location information. For the GMSC - NPLR interface version 1, version 2 and version 3 of this 8936 application context are applicable.
8937 8938 8939 8940 8941 8942 8943

locationInfoRetrievalContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR or NPLR if Initiator is GMSC -- Responder is HLR if Initiator is gsmSCF INITIATOR CONSUMER OF { interrogationPackage-v3} ID {map-ac locInfoRetrieval(5) version3(3)} }

8944 The following application-context-name is assigned to the v2-equivalent application-context:

8945 8946 8947

ID

{map-ac locInfoRetrieval(5) version2(2)}

1150

3GPP

8948 The following application-context-name is assigned to the v1-equivalent application-context:

8949 8950

1151 Release 7 1152 1153

ID

289

3GPP TS 29.002 V7.5.0 (2006-09)

{map-ac locInfoRetrieval(5) version1(1)}

8951 17.3.2.7

Call control transfer

8952 This application context is used for the call control transfer procedure between the VMSC and the GMSC.
8953 8954 8955 8956 8957 8958

callControlTransferContext-v4 APPLICATION-CONTEXT ::= { -- Responder is GMSC if Initiator is VMSC INITIATOR CONSUMER OF { callControlTransferPackage-v4} ID {map-ac callControlTransfer(6) version4(4)} }

8959 The following application-context-name is assigned to the v3-equivalent application-context:

8960

ID

{map-ac callControlTransfer(6) version3(3)}

8961 17.3.2.8

Void

8962 17.3.2.9 - 17.3.2.10 Void 8963 17.3.2.11 Location registers restart

8964 This application context is used between HLR and VLR or between HLR and SGSN for location register restart 8965 procedures. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable.
8966 8967 8968 8969 8970 8971

resetContext-v2 APPLICATION-CONTEXT ::= { -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { resetPackage-v2} ID {map-ac reset(10) version2(2)} }

8972 The following application-context-name is assigned to the v1-equivalent application-context:

8973 8974

ID

{map-ac reset(10) version1(1)}

8975 17.3.2.12

Handover control

8976 This application context is used for handover procedures between MSCs.
8977 8978 8979 8980 8981

handoverControlContext-v3 APPLICATION-CONTEXT ::= { -- Responder is MSCB if Initiator is MSCA INITIATOR CONSUMER OF { handoverControlPackage-v3} ID {map-ac handoverControl(11) version3(3)} }

8982 8983 The following application-context-name is assigned to the v2-equivalent application-context:

8984

ID

{map-ac handoverControl(11) version2(2)}

8985
8986

8987 The following application-context-name is assigned to the v1-equivalent application-context:

8988 8989

ID

{map-ac handoverControl(11) version1(1)}

1154

3GPP

8990 17.3.2.13

1155 Release 7 1156 1157

290

3GPP TS 29.002 V7.5.0 (2006-09)

IMSI Retrieval

8991 This application context is used for IMSI retrieval between HLR and VLR.
8992 8993 8994 8995 8996 8997

imsiRetrievalContext-v2 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { imsi-RetrievalPackage-v2} ID {map-ac imsiRetrieval(26) version2(2)} }

8998 This application-context is v2 only.

8999 17.3.2.14

Equipment Management

9000 This application context is used for equipment checking between MSC and EIR or between SGSN and EIR. For the 9001 SGSN - EIR interface version 1 and version 2 and version 3 of this application context are applicable:
9002 9003 9004 9005 9006 9007 9008

equipmentMngtContext-v3 APPLICATION-CONTEXT ::= { -- Responder is EIR if Initiator is MSC -- Responder is EIR if Initiator is SGSN INITIATOR CONSUMER OF { equipmentMngtPackage-v3} ID {map-ac equipmentMngt(13) version3(3)} }

9009 The following application-context-name is assigned to the v2-equivalent application-context:

9010 9011 9012 9013 9014 9015 9016

equipmentMngtContext-v2 APPLICATION-CONTEXT ::= { -- Responder is EIR if Initiator is MSC -- Responder is EIR if Initiator is SGSN INITIATOR CONSUMER OF { equipmentMngtPackage-v2} ID {map-ac equipmentMngt(13) version2(2)} }

9017 The following application-context-name is assigned to the v1-equivalent application-context:

9018 9019

ID

{map-ac equipmentMngt(13) version1(1)}

9020 17.3.2.15

Information retrieval

9021 This application context is used for authentication information retrieval between HLR and VLR or between HLR and 9022 SGSN. For the HLR - SGSN interface version 1 and version 2 and version 3 of this application context are applicable.
9023 9024 9025 9026 9027 9028 9029

infoRetrievalContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { infoRetrievalPackage-v3} ID {map-ac infoRetrieval(14) version3(3)} }

9030 The following application-context-name is assigned to the v2-equivalent application-context:

9031 9032 9033 9034 9035 9036 9037

infoRetrievalContext-v2 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { infoRetrievalPackage-v2} ID {map-ac infoRetrieval(14) version2(2)} }

9038 The following application-context-name is assigned to the v1-equivalent application-context:

9039 9040

ID

{map-ac infoRetrieval(14) version1(1)}

1158

3GPP

9041 17.3.2.16

1159 Release 7 1160 1161

291

3GPP TS 29.002 V7.5.0 (2006-09)

Inter-VLR information retrieval

9042 This application context is used for information retrieval between VLRs.
9043 9044 9045 9046 9047 9048

interVlrInfoRetrievalContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { interVlrInfoRetrievalPackage-v3} ID {map-ac interVlrInfoRetrieval(15) version3(3)} }

9049 The v2-equivalent application-context is:

9050 9051 9052 9053 9054 9055

interVlrInfoRetrievalContext-v2 APPLICATION-CONTEXT ::= { -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { interVlrInfoRetrievalPackage-v2} ID {map-ac interVlrInfoRetrieval(15) version2(2)} }

9056 The v1-equivalent application-context is:

9057 9058

ID

{map-ac infoRetrieval(14) version1(1)}

9059 17.3.2.17

Stand Alone Subscriber Data Management

9060 This application context is used for stand alone subscriber data management between HLR and VLR or between HLR 9061 and SGSN. For the HLR - SGSN interface only version 3 of this application context is applicable:
9062 9063 9064 9065 9066 9067

subscriberDataMngtContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { subscriberDataMngtStandAlonePackage-v3} ID {map-ac subscriberDataMngt(16) version3(3)} }

9068 The following application-context-name is assigned to the v2-equivalent application-context:

9069 9070

ID

{map-ac subscriberDataMngt(16) version2(2)}

9071 The following application-context-name is assigned to the v1-equivalent application-context:

9072 9073

ID

{map-ac subscriberDataMngt(16) version1(1)}

9074 17.3.2.18

Tracing

9075 This application context is used between HLR and VLR or between HLR and SGSN for stand alone tracing control 9076 procedures. For the HLR - SGSN interface version 1, version 2 and version 3 of this application context are applicable.
9077 9078 9079 9080 9081

tracingContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { tracingStandAlonePackage-v3} ID {map-ac tracing(17) version3(3)} }

9082 9083 The following application-context-name is assigned to the v2-equivalent application-context:

9084 9085

ID

{map-ac tracing(17) version2(2)}

9086 The following application-context-name is assigned to the v1-equivalent application-context:

9087 9088

ID

{map-ac tracing(17) version1(1)}

1162

3GPP

9089 17.3.2.19

1163 Release 7 1164 1165

292

3GPP TS 29.002 V7.5.0 (2006-09)

Network functional SS handling

9090 This application context is used for functional-like SS handling procedures between VLR and HLR.
9091 9092 9093 9094 9095 9096

networkFunctionalSsContext-v2 APPLICATION-CONTEXT ::= { -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { functionalSsPackage-v2} ID {map-ac networkFunctionalSs(18) version2(2)} }

9097 The v1-equivalent application-context is defined as follows:

9098 9099 9100 9101 9102 9103 9104 9105

networkFunctionalSsContext-v1 APPLICATION-CONTEXT ::= { -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { functionalSsPackage-v1 | unstructuredSsPackage-v1 | bindingPackage-v1} ID {map-ac networkFunctionalSs(18) version1(1)} }

9106 17.3.2.20

Network unstructured SS handling

9107 This application context is used for handling stimuli-like procedures between HLR and VLR, between the HLR and 9108 gsmSCF, and between HLR and HLR.
9109 9110 9111 9112 9113 9114 9115 9116 9117 9118

networkUnstructuredSsContext-v2 APPLICATION-CONTEXT ::= { -- Responder is HLR, Initiator is VLR -- Responder is VLR, Initiator is HLR -- Responder is gsmSCF, Initiator is HLR -- Responder is HLR, Initiator is gsmSCF -- Responder is HLR, Initiator is HLR OPERATIONS OF { unstructuredSsPackage-v2} ID {map-ac networkUnstructuredSs(19) version2(2)} }

9119 The following application-context-name is assigned to the v1-equivalent application-context:

9120 9121

ID

{map-ac networkFunctionalSs(18) version1(1)}

9122 17.3.2.21

Short Message Gateway

9123 This application context is used for short message gateway procedures.
9124 9125 9126 9127 9128 9129

shortMsgGatewayContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { shortMsgGatewayPackage-v3} ID {map-ac shortMsgGateway(20) version3(3)} }

9130 The following application-context-name is assigned to the v2-equivalent application-context:

9131 9132

ID

{map-ac shortMsgGateway(20) version2(2)}

9133 The following application-context-name is assigned to the v1-equivalent application-context:

9134 9135

ID

{map-ac shortMsgGateway(20) version1(1)}

9136 17.3.2.22

Mobile originating Short Message Relay

9137 This application context is used between MSC and IWMSC or between SGSN and IWMSC for mobile originating short 9138 message relay procedures. For the SGSN - IWMSC interface version 1, version 2 and version 3 of this application 9139 context are applicable.
9140 9141 9142 9143 9144 9145 9146

shortMsgMO-RelayContext-v3 APPLICATION-CONTEXT ::= { -- Responder is IWMSC if Initiator is MSC -- Responder is IWMSC if Initiator is SGSN INITIATOR CONSUMER OF { mo-ShortMsgRelayPackage-v3} ID {map-ac shortMsgMO-Relay(21) version3(3)} }

1166

3GPP

9147 The following application-context-name is assigned to the v2-equivalent application-context:

9148 9149

1167 Release 7 1168 1169

ID

293

3GPP TS 29.002 V7.5.0 (2006-09)

{map-ac shortMsgMO-Relay(21) version2(2)}

9150 The following application-context-name is assigned to the v1-equivalent application-context:

9151 9152

ID

{map-ac shortMsg-Relay(21) version1(1)}

9153 17.3.2.23 9154 17.3.2.24

Void Short message alert

9155 This application context is used for short message alerting procedures.
9156 9157 9158 9159 9160 9161

shortMsgAlertContext-v2 APPLICATION-CONTEXT ::= { -- Responder is IWMSC if Initiator is HLR INITIATOR CONSUMER OF { alertingPackage-v2} ID {map-ac shortMsgAlert(23) version2(2)} }

9162 The following application-context-name is symbolically assigned to the v1-equivalent application-context:

9163 9164

ID

{map-ac shortMsgAlert(23) version1(1)}

9165 17.3.2.25

Short message waiting data management

9166 This application context is used between VLR and HLR or between SGSN and HLR for short message waiting data 9167 management procedures. For the SGSN - HLR interface only version 3 of this application context is applicable.
9168 9169 9170 9171 9172 9173

mwdMngtContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is SGSN -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { mwdMngtPackage-v3} ID {map-ac mwdMngt(24) version3(3)} }

9174 9175 The following application-context-name is assigned to the v2-equivalent application-context:

9176

ID

{map-ac mwdMngt(24) version2(2)}

9177 9178 The following application-context-name is assigned to the v1-equivalent application-context:

9179 9180

ID

{map-ac mwdMngt(24) version1(1)}

9181 17.3.2.26

Mobile terminating Short Message Relay

9182 This application context is used between GMSC and MSC or between GMSC and SGSN for mobile terminating short 9183 message relay procedures. For the GMSC - SGSN interface version 2 and version 3 of this application context and the 9184 equivalent version 1 application context are applicable.
9185 9186 9187 9188 9189 9190

shortMsgMT-RelayContext-v3 APPLICATION-CONTEXT ::= { -- Responder is MSC or SGSN if Initiator is GMSC INITIATOR CONSUMER OF { mt-ShortMsgRelayPackage-v3} ID {map-ac shortMsgMT-Relay(25) version3(3)} }

9191 The following application-context-name is assigned to the v2-equivalent application-context:

9192 9193

ID

{map-ac shortMsgMT-Relay(25) version2(2)}

9194 The following application-context-name is assigned to the v1-equivalent application-context:

9195 9196

ID

{map-ac shortMsg-Relay(21) version1(1)}

1170

3GPP

9197 17.3.2.27

1171 Release 7 1172 1173

294

3GPP TS 29.002 V7.5.0 (2006-09)

MS purging

9198 This application context is used between HLR and VLR or between HLR and SGSN for MS purging procedures. For 9199 the SGSN - HLR interface only version 3 of this application context is applicable.
9200 9201 9202 9203 9204 9205 9206

msPurgingContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { purgingPackage-v3} ID {map-ac msPurging(27) version3(3)} }

9207 The following application-context-name is assigned to the v2-equivalent application-context:

9208

ID

{map-ac msPurging(27) version2(2)}

9209

9210 17.3.2.28

Subscriber information enquiry

9211 This application context is used between HLR and VLR or between HLR and SGSN for subscriber information enquiry 9212 procedures.
9213 9214 9215 9216 9217 9218

subscriberInfoEnquiryContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { subscriberInformationEnquiryPackage-v3} ID {map-ac subscriberInfoEnquiry(28) version3(3)} }

9219 This application-context is v3 only.

9220 17.3.2.29

Any time information enquiry

9221 This application context is used between gsmSCF and HLR or between gsmSCF and GMLC or between gsmSCF and 9222 NPLR for any time information enquiry procedures.
9223 9224 9225 9226 9227 9228

anyTimeInfoEnquiryContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR or GMLC or NPLR if Initiator is gsmSCF INITIATOR CONSUMER OF { anyTimeInformationEnquiryPackage-v3} ID {map-ac anyTimeInfoEnquiry(29) version3(3)} }

9229 This application-context is v3 only.

9230 17.3.2.30

Group Call Control

9231 This application context is used between anchor MSC and relay MSC for group call and broadcast call procedures.
9232 9233 9234 9235 9236 9237

groupCallControlContext-v3 APPLICATION-CONTEXT ::= { -- Responder is relay MSC if Initiator is anchor MSC INITIATOR CONSUMER OF { groupCallControlPackage-v3} ID {map-ac groupCallControl(31) version3(3)} }

9238 This application-context is v3 only.

9239 17.3.2.30A

Group Call Info Retrieval

9240 This application context is used between group call serving MSC and visited MSC for group call and broadcast call 9241 procedures.
9242 9243 9244 9245 9246 9247 9248

groupCallInfoRetControlContext-v3 APPLICATION-CONTEXT ::= { -- Responder is group call serving MSC if Initiator is visited MSC -- Responder is visited MSC if Initiator is group call serving MSC INITIATOR CONSUMER OF { groupCallInfoRetrievalPackage-v3} ID {map-ac groupCallInfoRetrieval(45) version3(3)} }

9249 This application-context is v3 only.

1174

3GPP

9250 17.3.2.31 9251 17.3.2.32

1175 Release 7 1176 1177

295

3GPP TS 29.002 V7.5.0 (2006-09)

Void Gprs Location Updating

9252 This application context is used between HLR and SGSN for gprs location updating procedures.
9253 9254 9255 9256 9257 9258 9259 9260 9261

gprsLocationUpdateContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { gprsLocationUpdatingPackage-v3} RESPONDER CONSUMER OF { subscriberDataMngtPackage-v3 | tracingPackage-v3} ID {map-ac gprsLocationUpdate(32) version3(3)} }

9262 This application-context is v3 only.

9263 17.3.2.33

Gprs Location Information Retreival

9264 This application context is used between HLR and GGSN when retrieving gprs location information.
9265 9266 9267 9268 9269

gprsLocationInfoRetrievalContext-v4 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { gprsInterrogationPackage-v4} ID {map-ac gprsLocationInfoRetrieval(33) version4(4)} }

9270 9271 The following application-context-name is assigned to the v3-equivalent application-context:

9272 9273 9274

ID

{map-ac gprsLocationInfoRetrieval(33) version3(3)}

9275 17.3.2.34

Failure Reporting

9276 This application context is used between HLR and GGSN to inform that network requested PDP-context activation has 9277 failed.
9278 9279 9280 9281 9282 9283

failureReportContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { failureReportingPackage-v3} ID {map-ac failureReport(34) version3(3)} }

9284 This application-context is v3 only.

9285 17.3.2.35

GPRS Notifying

9286 This application context is used between HLR and GGSN for notifying that GPRS subscriber is present again.
9287 9288 9289 9290 9291 9292

gprsNotifyContext-v3 APPLICATION-CONTEXT ::= { -- Responder is GGSN if Initiator is HLR INITIATOR CONSUMER OF { gprsNotifyingPackage-v3} ID {map-ac gprsNotify(35) version3(3)} }

9293 This application-context is v3 only.

1178

3GPP

9294 17.3.2.36

1179 Release 7 1180 1181

296

3GPP TS 29.002 V7.5.0 (2006-09)

Supplementary Service invocation notification

9295 This application context is used between the MSC and the gsmSCF and between the HLR and the gsmSCF for 9296 Supplementary Service invocation notification procedures.
9297 9298 9299 9300 9301 9302 9303

ss-InvocationNotificationContext-v3 APPLICATION-CONTEXT ::= { -- Responder is gsmSCF, Initiator is MSC -- Responder is gsmSCF, Initiator is HLR INITIATOR CONSUMER OF { ss-InvocationNotificationPackage-v3} ID {map-ac ss-InvocationNotification(36) version3(3)} }

9304 This application-context is v3 only.

9305 17.3.2.37

Reporting

9306 This application context is used between HLR and VLR for reporting procedures.
9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318

reportingContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VLR if Initiator is HLR -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { setReportingStatePackage-v3 | statusReportPackage-v3 | remoteUserFreePackage-v3} RESPONDER CONSUMER OF { setReportingStatePackage-v3 | statusReportPackage-v3} ID {map-ac reporting(7) version3(3)} }

9319 This application-context is v3 only.

9320 17.3.2.38

Call Completion

9321 This application context is used between VLR and the HLR for subscriber control of call completion services.
9322 9323 9324 9325 9326 9327

callCompletionContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { callCompletionPackage-v3} ID {map-ac callCompletion(8) version3(3)} }

9328 This application-context is v3 only.

1182

3GPP

9329 17.3.2.39

1183 Release 7 1184 1185

297

3GPP TS 29.002 V7.5.0 (2006-09)

Location Service Gateway

9330 This application context is used for location service gateway procedures.
9331 9332 9333 9334 9335

locationSvcGatewayContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is GMLC INITIATOR CONSUMER OF { locationSvcGatewayPackage-v3} ID {map-ac locationSvcGateway(37) version3(3)} }

9336 9337 17.3.2.40 Location Service Enquiry

9338 This application context is used for location service enquiry procedures.
9339 9340 9341 9342 9343 9344 9345 9346

locationSvcEnquiryContext-v3 APPLICATION-CONTEXT ::= { -- Responder is MSC or SGSN if Initiator is GMLC -- Responder is GMLC if Initiator is MSC -- Responder is GMLC if Initiator is SGSN INITIATOR CONSUMER OF { locationSvcEnquiryPackage-v3 | locationSvcReportingPackage-v3} ID {map-ac locationSvcEnquiry(38) version3 (3)} }

9347

9348 17.3.2.41 9349 17.3.2.42 9350 17.3.2.43 9351 17.3.2.44

Void Void Void IST Alerting

9352 This application context is used between MSC (Visited MSC or Gateway MSC) and HLR for alerting services within 9353 IST procedures.
9354 9355 9356 9357 9358 9359 9360

istAlertingContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VMSC -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { ist-AlertingPackage-v3} ID {map-ac alerting(4) version3(3)} }

9361 This application-context is v3 only.

9362 17.3.2.45

Service Termination

9363 This application context is used between HLR and MSC (Visited MSC or Gateway MSC) for service termination 9364 services within IST procedures.
9365 9366 9367 9368 9369 9370

serviceTerminationContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VMSC or GMSC if Initiator is HLR INITIATOR CONSUMER OF { serviceTerminationPackage-v3} ID {map-ac serviceTermination(9) version3(3)} }

9371 This application-context is v3 only.

1186

3GPP

9372 17.3.2.46

1187 Release 7 1188 1189

298

3GPP TS 29.002 V7.5.0 (2006-09)

Mobility Management event notification

9373 This application context is used between VLR and gsmSCF for Mobility Management event notification procedures.
9374 9375 9376 9377 9378 9379

mm-EventReportingContext-v3 APPLICATION-CONTEXT ::= { -- Responder is gsmSCF, Initiator is VLR INITIATOR CONSUMER OF { mm-EventReportingPackage-v3} ID {map-ac mm-EventReporting(42) version3(3)} }

9380 This application-context is v3 only.

9381 17.3.2.47

Any time information handling

9382 This application context is used between gsmSCF and HLR for any time information handling procedures.
9383 9384 9385 9386 9387 9388

anyTimeInfohandlingContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is gsmSCF INITIATOR CONSUMER OF { anyTimeInformationHandlingPackage-v3} ID {map-ac anyTimeInfoHandling(43) version3(3)} }

9389 This application-context is v3 only.

9390 17.3.2.48

Subscriber Data modification notification

This application context is used between HLR and gsmSCF for Subscriber Data modification notification procedures.
subscriberDataModificationNotificationContext-v3 APPLICATION-CONTEXT ::= { -- Responder is gsmSCF, Initiator is HLR INITIATOR CONSUMER OF { subscriberDataModificationNotificationPackage-v3} ID {map-ac subscriberDataModificationNotification(22) version3(3)} }

This application-context is v3 only.

9391 17.3.2.49

Authentication Failure Report

9392 This application context is used between VLR and HLR or SGSN and HLR for reporting of authentication failures.
9393 9394 9395 9396 9397 9398 9399

authenticationFailureReportContext-v3 APPLICATION-CONTEXT ::= { -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { authenticationFailureReportPackage-v3 } ID {map-ac authenticationFailureReport(39) version3(3)} }

9400 This application-context is v3 only.

9401 17.3.2.50

Resource Management

9402 This application context is used between GMSC and VMSC for resource management purpose.
9403 9404 9405 9406 9407 9408

resourceManagementContext-v3 APPLICATION-CONTEXT ::= { -- Responder is VMSC if Initiator is GMSC INITIATOR CONSUMER OF { resourceManagementPackage-v3 } ID {map-ac resourceManagement(44) version3(3)} }

9409 This application-context is v3 only.

1190

3GPP

9410 17.3.2.51

1191 Release 7 1192 1193

299

3GPP TS 29.002 V7.5.0 (2006-09)

Mobile terminating Short Message Relay VGCS

9411 This application context is used between SMS-GMSC and MSC for mobile terminating short message relay procedures 9412 for VGCS.
9413 9414 9415 9416 9417 9418

shortMsgMT-Relay-VGCS-Context-v3 APPLICATION-CONTEXT ::= { -- Responder is MSC if Initiator is SMS-GMSC INITIATOR CONSUMER OF { mt-ShortMsgRelay-VGCS-Package-v3} ID {map-ac shortMsgMT-Relay-VGCS(41) version3(3)} }

9419 This application-context is v3 only. 9420

9421

17.3.3 ASN.1 Module for application-context-names

The following ASN.1 module summarises the application-context-name assigned to MAP application-contexts.
MAP-ApplicationContexts { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ApplicationContexts (2) version10 (10)} DEFINITIONS ::= BEGIN -- EXPORTS everything IMPORTS gsm-NetworkId, ac-Id FROM MobileDomainDefinitions { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) mobileDomainDefinitions (0) version1 (1)} ; -- application-context-names map-ac OBJECT IDENTIFIER ::= {gsm-NetworkId ac-Id}

9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444 9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467 9468 9469 9470 9471 9472 9473 9474 9475 9476

networkLocUpContext-v3 OBJECT IDENTIFIER ::= {map-ac networkLocUp(1) version3(3)} locationCancellationContext-v3 OBJECT IDENTIFIER ::= {map-ac locationCancel(2) version3(3)} roamingNumberEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac roamingNbEnquiry(3) version3(3)} authenticationFailureReportContext-v3 OBJECT IDENTIFIER ::= {map-ac authenticationFailureReport(39) version3(3)} locationInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac locInfoRetrieval(5) version3(3)} resetContext-v2 OBJECT IDENTIFIER ::= {map-ac reset(10) version2(2)} handoverControlContext-v3 OBJECT IDENTIFIER ::= {map-ac handoverControl(11) version3(3)} equipmentMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac equipmentMngt(13) version3(3)} infoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac infoRetrieval(14) version3(3)} interVlrInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac interVlrInfoRetrieval(15) version3(3)}

1194

3GPP

1195 Release 7 1196 1197

9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516 9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552

300

3GPP TS 29.002 V7.5.0 (2006-09)

subscriberDataMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberDataMngt(16) version3(3)} tracingContext-v3 OBJECT IDENTIFIER ::= {map-ac tracing(17) version3(3)} networkFunctionalSsContext-v2 OBJECT IDENTIFIER ::= {map-ac networkFunctionalSs(18) version2(2)} networkUnstructuredSsContext-v2 OBJECT IDENTIFIER ::= {map-ac networkUnstructuredSs(19) version2(2)} shortMsgGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgGateway(20) version3(3)} shortMsgMO-RelayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMO-Relay(21) version3(3)} shortMsgAlertContext-v2 OBJECT IDENTIFIER ::= {map-ac shortMsgAlert(23) version2(2)} mwdMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac mwdMngt(24) version3(3)} shortMsgMT-RelayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMT-Relay(25) version3(3)} shortMsgMT-Relay-VGCS-Context-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMT-Relay-VGCS(41) version3(3)} imsiRetrievalContext-v2 OBJECT IDENTIFIER ::= {map-ac imsiRetrieval(26) version2(2)} msPurgingContext-v3 OBJECT IDENTIFIER ::= {map-ac msPurging(27) version3(3)} subscriberInfoEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberInfoEnquiry(28) version3(3)} anyTimeInfoEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac anyTimeInfoEnquiry(29) version3(3)} callControlTransferContext-v4 OBJECT IDENTIFIER ::= {map-ac callControlTransfer(6) version4(4)} ss-InvocationNotificationContext-v3 OBJECT IDENTIFIER ::= {map-ac ss-InvocationNotification(36) version3(3)} groupCallControlContext-v3 OBJECT IDENTIFIER ::= {map-ac groupCallControl(31) version3(3)} groupCallInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac groupCallInfoRetrieval(45) version3(3)} gprsLocationUpdateContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsLocationUpdate(32) version3(3)} gprsLocationInfoRetrievalContext-v4 OBJECT IDENTIFIER ::= {map-ac gprsLocationInfoRetrieval(33) version4(4)} failureReportContext-v3 OBJECT IDENTIFIER ::= {map-ac failureReport(34) version3(3)} gprsNotifyContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsNotify(35) version3(3)} reportingContext-v3 OBJECT IDENTIFIER ::= {map-ac reporting(7) version3(3)} callCompletionContext-v3 OBJECT IDENTIFIER ::= {map-ac callCompletion(8) version3(3)} istAlertingContext-v3 OBJECT IDENTIFIER ::= {map-ac istAlerting(4) version3(3)}

1198

3GPP

1199 Release 7 1200 1201

9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595 9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613

301

3GPP TS 29.002 V7.5.0 (2006-09)

serviceTerminationContext-v3 OBJECT IDENTIFIER ::= {map-ac immediateTermination(9) version3(3)} locationSvcGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcGateway(37) version3(3)} locationSvcEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcEnquiry(38) version3(3)} mm-EventReportingContext-v3 OBJECT IDENTIFIER ::= {map-ac mm-EventReporting(42) version3(3)} anyTimeInfoHandlingContext-v3 OBJECT IDENTIFIER ::= {map-ac anyTimeInfoHandling(43) version3(3)} subscriberDataModificationNotificationContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberDataModificationNotification(22) version3(3)} resourceManagementContext-v3 OBJECT IDENTIFIER ::= {map-ac resourceManagement(44) version3(3)}

-- The following Object Identifiers are reserved for application-contexts -- existing in previous versions of the protocol

-- AC Name & Version

--- networkLocUpContext-v1 -- networkLocUpContext-v2 -- locationCancellationContext-v1 -- locationCancellationContext-v2 -- roamingNumberEnquiryContext-v1 -- roamingNumberEnquiryContext-v2 -- locationInfoRetrievalContext-v1 -- locationInfoRetrievalContext-v2 -- resetContext-v1 -- handoverControlContext-v1 -- handoverControlContext-v2 -- sIWFSAllocationContext-v3 -- equipmentMngtContext-v1 -- equipmentMngtContext-v2 -- infoRetrievalContext-v1 -- infoRetrievalContext-v2 -- interVlrInfoRetrievalContext-v2 -- subscriberDataMngtContext-v1 -- subscriberDataMngtContext-v2 -- tracingContext-v1 -- tracingContext-v2 -- networkFunctionalSsContext-v1 -- shortMsgGatewayContext-v1 -- shortMsgGatewayContext-v2 -- shortMsgRelayContext-v1 -- shortMsgAlertContext-v1 -- mwdMngtContext-v1 -- mwdMngtContext-v2 -- shortMsgMT-RelayContext-v2 -- msPurgingContext-v2 -- callControlTransferContext-v3 -- gprsLocationInfoRetrievalContext-v3

Object Identifier
map-ac networkLocUp (1) version1 (1) map-ac networkLocUp (1) version2 (2) map-ac locationCancellation (2) version1 (1) map-ac locationCancellation (2) version2 (2) map-ac roamingNumberEnquiry (3) version1 (1) map-ac roamingNumberEnquiry (3) version2 (2) map-ac locationInfoRetrieval (5) version1 (1) map-ac locationInfoRetrieval (5) version2 (2) map-ac reset (10) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version2 (2) map-ac sIWFSAllocation (12) version3 (3) map-ac equipmentMngt (13) version1 (1) map-ac equipmentMngt (13) version2 (2) map-ac infoRetrieval (14) version1 (1) map-ac infoRetrieval (14) version2 (2) map-ac interVlrInfoRetrieval (15) version2 (2) map-ac subscriberDataMngt (16) version1 (1) map-ac subscriberDataMngt (16) version2 (2) map-ac tracing (17) version1 (1) map-ac tracing (17) version2 (2) map-ac networkFunctionalSs (18) version1 (1) map-ac shortMsgGateway (20) version1 (1) map-ac shortMsgGateway (20) version2 (2) map-ac shortMsgRelay (21) version1 (1) map-ac shortMsgAlert (23) version1 (1) map-ac mwdMngt (24) version1 (1) map-ac mwdMngt (24) version2 (2) map-ac shortMsgMT-Relay (25) version2 (2) map-ac msPurging (27) version2 (2) map-ac callControlTransferContext (6) version3 (3) map-ac gprsLocationInfoRetrievalContext (33) version3 (3)

END

9614
9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626

17.4 MAP Dialogue Information

MAP-DialogueInformation { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-DialogueInformation (3) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN

1202

3GPP

1203 Release 7 1204 1205

9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666 9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700

302

3GPP TS 29.002 V7.5.0 (2006-09)

EXPORTS map-DialogueAS, MAP-DialoguePDU ; IMPORTS gsm-NetworkId, as-Id FROM MobileDomainDefinitions { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) mobileDomainDefinitions (0) version1 (1)} AddressString FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network(1) modules (3) map-CommonDataTypes (18) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ; -- abstract syntax name for MAP-DialoguePDU map-DialogueAS OBJECT IDENTIFIER ::= {gsm-NetworkId as-Id map-DialoguePDU (1) version1 (1)} MAP-DialoguePDU ::= CHOICE { map-open map-accept map-close map-refuse map-userAbort map-providerAbort [0] [1] [2] [3] [4] [5] MAP-OpenInfo, MAP-AcceptInfo, MAP-CloseInfo, MAP-RefuseInfo, MAP-UserAbortInfo, MAP-ProviderAbortInfo} OPTIONAL, OPTIONAL, OPTIONAL

MAP-OpenInfo ::= SEQUENCE { destinationReference [0] AddressString originationReference [1] AddressString ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-AcceptInfo ::= SEQUENCE { ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-CloseInfo ::= SEQUENCE { ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-RefuseInfo ::= SEQUENCE { reason Reason, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 alternativeApplicationContext OBJECT IDENTIFIER -- alternativeApplicationContext must not be used in version 2 } Reason ::= ENUMERATED { noReasonGiven invalidDestinationReference invalidOriginatingReference (0), (1), (2)}

OPTIONAL

OPTIONAL

OPTIONAL, OPTIONAL

1206

3GPP

1207 Release 7 1208 1209

9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738

303

3GPP TS 29.002 V7.5.0 (2006-09)

MAP-UserAbortInfo ::= SEQUENCE { map-UserAbortChoice MAP-UserAbortChoice, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-UserAbortChoice ::= CHOICE { userSpecificReason userResourceLimitation resourceUnavailable applicationProcedureCancellation [0] [1] [2] [3] NULL, NULL, ResourceUnavailableReason, ProcedureCancellationReason}

OPTIONAL

ResourceUnavailableReason ::= ENUMERATED { shortTermResourceLimitation (0), longTermResourceLimitation (1)} ProcedureCancellationReason ::= ENUMERATED { handoverCancellation (0), radioChannelRelease (1), networkPathRelease (2), callRelease (3), associatedProcedureFailure (4), tandemDialogueRelease (5), remoteOperationsFailure (6)} MAP-ProviderAbortInfo ::= SEQUENCE { map-ProviderAbortReason MAP-ProviderAbortReason, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-ProviderAbortReason ::= ENUMERATED { abnormalDialogue (0), invalidPDU (1)} END

OPTIONAL

9739
9740 9741 9742 9743 9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775

17.5 MAP operation and error codes

MAP-Protocol { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Protocol (4) version10 (10)} DEFINITIONS ::= BEGIN IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} updateLocation, cancelLocation, purgeMS, sendIdentification, updateGprsLocation, prepareHandover, sendEndSignal, processAccessSignalling, forwardAccessSignalling, prepareSubsequentHandover, sendAuthenticationInfo, authenticationFailureReport, checkIMEI, insertSubscriberData, deleteSubscriberData, reset, forwardCheckSS-Indication, restoreData, provideSubscriberInfo, anyTimeInterrogation, anyTimeSubscriptionInterrogation,

1210

3GPP

1211 Release 7 1212 1213

9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818 9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850

304

3GPP TS 29.002 V7.5.0 (2006-09)

anyTimeModification, sendRoutingInfoForGprs, failureReport, noteMsPresentForGprs, noteMM-Event, noteSubscriberDataModified

FROM MAP-MobileServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version10 (10)} activateTraceMode, deactivateTraceMode, sendIMSI FROM MAP-OperationAndMaintenanceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version10 (10)} sendRoutingInfo, provideRoamingNumber, resumeCallHandling, setReportingState, statusReport, remoteUserFree, ist-Alert, ist-Command, releaseResources FROM MAP-CallHandlingOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version10 (10)} registerSS, eraseSS, activateSS, deactivateSS, interrogateSS, processUnstructuredSS-Request, unstructuredSS-Request, unstructuredSS-Notify, registerPassword, getPassword, ss-InvocationNotification, registerCC-Entry, eraseCC-Entry FROM MAP-SupplementaryServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version10 (10)} sendRoutingInfoForSM, mo-ForwardSM, mt-ForwardSM, reportSM-DeliveryStatus, alertServiceCentre, informServiceCentre, readyForSM, mt-ForwardSM-VGCS FROM MAP-ShortMessageServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) version10 (10)} prepareGroupCall, processGroupCallSignalling, forwardGroupCallSignalling, sendGroupCallEndSignal, sendGroupCallInfo FROM MAP-Group-Call-Operations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Group-Call-Operations (22) version10 (10)}

1214

3GPP

1215 Release 7 1216 1217

9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890 9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910

305

3GPP TS 29.002 V7.5.0 (2006-09)

provideSubscriberLocation, sendRoutingInfoForLCS, subscriberLocationReport FROM MAP-LocationServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version10 (10)} ; Supported-MAP-Operations OPERATION ::= {updateLocation | cancelLocation | purgeMS | sendIdentification | updateGprsLocation | prepareHandover | sendEndSignal | processAccessSignalling | forwardAccessSignalling | prepareSubsequentHandover | sendAuthenticationInfo | authenticationFailureReport | checkIMEI | insertSubscriberData | deleteSubscriberData | reset | forwardCheckSS-Indication | restoreData | provideSubscriberInfo | anyTimeInterrogation | anyTimeSubscriptionInterrogation | anyTimeModification | sendRoutingInfoForGprs | failureReport |noteMsPresentForGprs | noteMM-Event | noteSubscriberDataModified | activateTraceMode | deactivateTraceMode | sendIMSI | sendRoutingInfo | provideRoamingNumber | resumeCallHandling | setReportingState | statusReport | remoteUserFree | ist-Alert | ist-Command | registerSS | eraseSS | activateSS | deactivateSS | interrogateSS | processUnstructuredSS-Request | unstructuredSS-Request | unstructuredSS-Notify | registerPassword | getPassword | ss-InvocationNotification | registerCC-Entry | eraseCC-Entry | sendRoutingInfoForSM | mo-ForwardSM | mt-ForwardSM | reportSM-DeliveryStatus | alertServiceCentre | informServiceCentre | readyForSM | prepareGroupCall | processGroupCallSignalling | forwardGroupCallSignalling | sendGroupCallEndSignal | provideSubscriberLocation | sendRoutingInfoForLCS | subscriberLocationReport | releaseResources | mt-ForwardSM-VGCS | sendGroupCallInfo }

-- The following operation codes are reserved for operations -- existing in previous versions of the protocol -- Operation Name --- sendParameters -- processUnstructuredSS-Data -- performHandover -- performSubsequentHandover -- provideSIWFSNumber -- siwfs-SignallingModify -- noteInternalHandover -- noteSubscriberPresent -- alertServiceCentreWithoutResult -- traceSubscriberActivity -- beginSubscriberActivity AC used map-ac infoRetrieval (14) version1 (1) map-ac networkFunctionalSs (18) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac sIWFSAllocation (12) version3 (3) map-ac sIWFSAllocation (12) version3 (3) map-ac handoverControl (11) version1 (1) map-ac mwdMngt (24) version1 (1) map-ac shortMsgAlert (23) version1 (1) map-ac handoverControl (11) version1 (1) map-ac networkFunctionalSs (18) version1 (1) Oper. Code local:9 local:19 local:28 local:30 local:31 local:32 local:35 local:48 local:49 local:52 local:54

-- The following error codes are reserved for errors -- existing in previous versions of the protocol -- Error Name --- unknownBaseStation -- invalidTargetBaseStation -- noRadioResourceAvailable END AC used map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) Error Code local:2 local:23 local:24

9911 9912
9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923

17.6 MAP operations and errors

17.6.1 Mobile Service Operations
MAP-MobileServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version10 (10)} DEFINITIONS ::= BEGIN

1218

3GPP

9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957 9958 9959 9960 9961 9962 9963 9964 9965 9966 9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002

1219 Release 7 1220 1221

EXPORTS -- location registration operations updateLocation, cancelLocation, purgeMS, sendIdentification, -- gprs location registration operations updateGprsLocation, -- subscriber information enquiry operations provideSubscriberInfo, -- any time information enquiry operations anyTimeInterrogation, -- any time information handling operations anyTimeSubscriptionInterrogation, anyTimeModification,

306

3GPP TS 29.002 V7.5.0 (2006-09)

-- subscriber data modification notification operations noteSubscriberDataModified, -- handover operations prepareHandover, sendEndSignal, processAccessSignalling, forwardAccessSignalling, prepareSubsequentHandover, -- authentication management operations sendAuthenticationInfo, authenticationFailureReport, -- IMEI management operations checkIMEI, -- subscriber management operations insertSubscriberData, deleteSubscriberData, -- fault recovery operations reset, forwardCheckSS-Indication, restoreData, -- gprs location information retrieval operations sendRoutingInfoForGprs, -- failure reporting operations failureReport, -- gprs notification operations noteMsPresentForGprs, -- Mobility Management operations noteMM-Event ; IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} systemFailure, dataMissing, unexpectedDataValue, unknownSubscriber, unknownMSC, unidentifiedSubscriber, unknownEquipment, roamingNotAllowed, ati-NotAllowed, noHandoverNumberAvailable, subsequentHandoverFailure,

1222

3GPP

10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080

1223 Release 7 1224 1225

307

3GPP TS 29.002 V7.5.0 (2006-09)

absentSubscriber, mm-EventNotSupported, atsi-NotAllowed, atm-NotAllowed, bearerServiceNotProvisioned, teleserviceNotProvisioned, callBarred, illegalSS-Operation, ss-ErrorStatus, ss-NotAvailable, ss-Incompatibility, ss-SubscriptionViolation, informationNotAvailable, targetCellOutsideGroupCallArea

FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationArg, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes, PrepareHO-Arg, PrepareHO-Res, ForwardAccessSignalling-Arg, ProcessAccessSignalling-Arg, SendEndSignal-Arg, SendEndSignal-Res, PrepareSubsequentHO-Res, PrepareSubsequentHO-Arg, SendAuthenticationInfoArg, SendAuthenticationInfoRes, AuthenticationFailureReportArg, AuthenticationFailureReportRes, CheckIMEI-Arg, CheckIMEI-Res, InsertSubscriberDataArg, InsertSubscriberDataRes, DeleteSubscriberDataArg, DeleteSubscriberDataRes, ResetArg, RestoreDataArg, RestoreDataRes, ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, AnyTimeSubscriptionInterrogationArg, AnyTimeSubscriptionInterrogationRes, AnyTimeModificationArg, AnyTimeModificationRes, NoteSubscriberDataModifiedArg, NoteSubscriberDataModifiedRes, AnyTimeInterrogationArg, AnyTimeInterrogationRes, SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, FailureReportArg, FailureReportRes, NoteMsPresentForGprsArg, NoteMsPresentForGprsRes, NoteMM-EventArg, NoteMM-EventRes FROM MAP-MS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version10 (10)} ;

1226

3GPP

10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10093 10094 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 10111 10112 10113 10114 10115 10116 10117 10118 10119 10120 10121 10122 10123 10124 10125 10126 10127 10128 10129 10130 10131 10132 10133 10134 10135 10136 10137 10138 10139 10140 10141 10142 10143 10144 10145 10146 10147 10148 10149 10150 10151 10152 10153 10154 10155 10156

1227 Release 7 1228 1229

308

3GPP TS 29.002 V7.5.0 (2006-09)

-- location registration operations updateLocation OPERATION ::= { ARGUMENT UpdateLocationArg RESULT UpdateLocationRes ERRORS { systemFailure | dataMissing | unexpectedDataValue | unknownSubscriber | roamingNotAllowed} CODE local:2 } cancelLocation OPERATION ::= { ARGUMENT CancelLocationArg RESULT CancelLocationRes -- optional ERRORS { dataMissing | unexpectedDataValue} CODE local:3 } purgeMS OPERATION ::= { ARGUMENT PurgeMS-Arg RESULT PurgeMS-Res -- optional ERRORS{ dataMissing | unexpectedDataValue| unknownSubscriber} CODE local:67 } sendIdentification OPERATION ::= { ARGUMENT SendIdentificationArg RESULT SendIdentificationRes ERRORS { dataMissing | unidentifiedSubscriber} CODE local:55 } -- gprs location registration operations updateGprsLocation OPERATION ::= { ARGUMENT UpdateGprsLocationArg RESULT UpdateGprsLocationRes ERRORS { systemFailure | unexpectedDataValue | unknownSubscriber | roamingNotAllowed} CODE local:23 } -- subscriber information enquiry operations provideSubscriberInfo OPERATION ::= { ARGUMENT ProvideSubscriberInfoArg RESULT ProvideSubscriberInfoRes ERRORS { dataMissing | unexpectedDataValue} CODE local:70 } -- any time information enquiry operations --Timer m --Timer m --Timer m

--Timer m

--Timer m

--Timer s

1230

3GPP

10157 10158 10159 10160 10161 10162 10163 10164 10165 10166 10167 10168 10169 10170 10171 10172 10173 10174 10175 10176 10177 10178 10179 10180 10181 10182 10183 10184 10185 10186 10187 10188 10189 10190 10191 10192 10193 10194 10195 10196 10197 10198 10199 10200 10201 10202 10203 10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225

1231 Release 7 1232 1233

309

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

anyTimeInterrogation OPERATION ::= { ARGUMENT AnyTimeInterrogationArg RESULT AnyTimeInterrogationRes ERRORS { systemFailure | ati-NotAllowed | dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:71 }

-- any time information handling operations anyTimeSubscriptionInterrogation OPERATION ::= { ARGUMENT AnyTimeSubscriptionInterrogationArg RESULT AnyTimeSubscriptionInterrogationRes ERRORS { atsi-NotAllowed | dataMissing | unexpectedDataValue | unknownSubscriber | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-NotAvailable | informationNotAvailable} CODE local:62 } anyTimeModification OPERATION ::= { ARGUMENT AnyTimeModificationArg RESULT AnyTimeModificationRes ERRORS { atm-NotAllowed | dataMissing | unexpectedDataValue | unknownSubscriber | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-SubscriptionViolation | ss-ErrorStatus | ss-Incompatibility | informationNotAvailable} CODE local:65 } -- subscriber data modification notification operations noteSubscriberDataModified OPERATION ::= { ARGUMENT NoteSubscriberDataModifiedArg RESULT NoteSubscriberDataModifiedRes -- optional ERRORS { dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:5 } -- handover operations --Timer m --Timer m

--Timer m

1234

3GPP

10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264 10265 10266 10267 10268 10269 10270 10271 10272 10273 10274 10275 10276 10277 10278 10279 10280 10281 10282 10283 10284 10285 10286 10287 10288 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301

1235 Release 7 1236 1237

310

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

prepareHandover OPERATION ::= { ARGUMENT PrepareHO-Arg RESULT PrepareHO-Res ERRORS { systemFailure | dataMissing | unexpectedDataValue | noHandoverNumberAvailable | targetCellOutsideGroupCallArea } CODE local:68 } sendEndSignal OPERATION ::= { ARGUMENT SendEndSignal-Arg RESULT SendEndSignal-Res CODE local:29 } processAccessSignalling OPERATION ::= { ARGUMENT ProcessAccessSignalling-Arg CODE local:33 } forwardAccessSignalling OPERATION ::= { ARGUMENT ForwardAccessSignalling-Arg CODE local:34 } prepareSubsequentHandover OPERATION ::= { ARGUMENT PrepareSubsequentHO-Arg RESULT PrepareSubsequentHO-Res ERRORS { unexpectedDataValue | dataMissing | unknownMSC | subsequentHandoverFailure} CODE local:69 }

--Timer l

--Timer s

--Timer s

--Timer m

-- authentication management operations sendAuthenticationInfo OPERATION ::= { --Timer m ARGUMENT SendAuthenticationInfoArg -- optional -- within a dialogue sendAuthenticationInfoArg shall not be present in -- subsequent invoke components. If received in a subsequent invoke component -- it shall be discarded. RESULT SendAuthenticationInfoRes -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:56 } authenticationFailureReport OPERATION ::= { ARGUMENT AuthenticationFailureReportArg RESULT AuthenticationFailureReportRes -- optional ERRORS { systemFailure | unexpectedDataValue | unknownSubscriber} CODE local:15 } -- IMEI management operations --Timer m

1238

3GPP

10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351 10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364 10365 10366 10367 10368 10369 10370 10371 10372 10373 10374 10375 10376 10377 10378

1239 Release 7 1240 1241

311

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

checkIMEI OPERATION ::= { ARGUMENT CheckIMEI-Arg RESULT CheckIMEI-Res ERRORS { systemFailure | dataMissing | unknownEquipment} CODE local:43 }

-- subscriber management operations insertSubscriberData OPERATION ::= { ARGUMENT InsertSubscriberDataArg RESULT InsertSubscriberDataRes -- optional ERRORS { dataMissing | unexpectedDataValue | unidentifiedSubscriber} CODE local:7 } deleteSubscriberData OPERATION ::= { ARGUMENT DeleteSubscriberDataArg RESULT DeleteSubscriberDataRes -- optional ERRORS { dataMissing | unexpectedDataValue | unidentifiedSubscriber} CODE local:8 } -- fault recovery operations reset OPERATION ::= { ARGUMENT ResetArg CODE local:37 } forwardCheckSS-Indication CODE local:38 } OPERATION ::= { --Timer m --Timer m

--Timer m

--Timer s --Timer m

restoreData OPERATION ::= { ARGUMENT RestoreDataArg RESULT RestoreDataRes ERRORS { systemFailure | dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:57 } -- gprs location information retrieval operations sendRoutingInfoForGprs OPERATION ::= { ARGUMENT SendRoutingInfoForGprsArg RESULT SendRoutingInfoForGprsRes ERRORS { absentSubscriber | systemFailure | dataMissing | unexpectedDataValue | unknownSubscriber | callBarred } CODE local:24 } -- failure reporting operations

--Timer m

1242

3GPP

10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419

1243 Release 7 1244 1245

312

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

failureReport OPERATION ::= { ARGUMENT FailureReportArg RESULT FailureReportRes -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:25 }

-- gprs notification operations noteMsPresentForGprs OPERATION ::= { ARGUMENT NoteMsPresentForGprsArg RESULT NoteMsPresentForGprsRes -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:26 } noteMM-Event OPERATION ::= { ARGUMENT NoteMM-EventArg RESULT NoteMM-EventRes ERRORS { dataMissing | unexpectedDataValue | unknownSubscriber | mm-EventNotSupported} CODE local:89 } END --Timer m

--Timer m

10420
10421 10422 10423 10424 10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448 10449 10450 10451 10452 10453 10454

17.6.2 Operation and Maintenance Operations

MAP-OperationAndMaintenanceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version10 (10)} DEFINITIONS ::= BEGIN EXPORTS activateTraceMode, deactivateTraceMode, sendIMSI ; IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} systemFailure, dataMissing, unexpectedDataValue, facilityNotSupported, unknownSubscriber, unidentifiedSubscriber, tracingBufferFull FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)}

1246

3GPP

10455 10456 10457 10458 10459 10460 10461 10462 10463 10464 10465 10466 10467 10468 10469 10470 10471 10472 10473 10474 10475 10476 10477 10478 10479 10480 10481 10482 10483 10484 10485 10486 10487 10488 10489 10490 10491 10492 10493 10494 10495 10496 10497 10498 10499 10500 10501 10502 10503 10504 10505 10506 10507 10508 10509 10510 10511

1247 Release 7 1248 1249

313

3GPP TS 29.002 V7.5.0 (2006-09)

ActivateTraceModeArg, ActivateTraceModeRes, DeactivateTraceModeArg, DeactivateTraceModeRes FROM MAP-OM-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version10 (10)} ISDN-AddressString, IMSI FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} ; activateTraceMode OPERATION ::= { ARGUMENT ActivateTraceModeArg RESULT ActivateTraceModeRes -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unidentifiedSubscriber | tracingBufferFull} CODE local:50 } deactivateTraceMode OPERATION ::= { ARGUMENT DeactivateTraceModeArg RESULT DeactivateTraceModeRes -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unidentifiedSubscriber} CODE local:51 } sendIMSI OPERATION ::= { ARGUMENT ISDN-AddressString RESULT IMSI ERRORS { dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:58 } END --Timer m

--Timer m

--Timer m

10512
10513 10514 10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530

17.6.3 Call Handling Operations

MAP-CallHandlingOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version10 (10)} DEFINITIONS ::= BEGIN EXPORTS sendRoutingInfo, provideRoamingNumber, resumeCallHandling, setReportingState, statusReport, remoteUserFree,

1250

3GPP

10531 10532 10533 10534 10535 10536 10537 10538 10539 10540 10541 10542 10543 10544 10545 10546 10547 10548 10549 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 10565 10566 10567 10568 10569 10570 10571 10572 10573 10574 10575 10576 10577 10578 10579 10580 10581 10582 10583 10584 10585 10586 10587 10588 10589

1251 Release 7 1252 1253

314

3GPP TS 29.002 V7.5.0 (2006-09)

ist-Alert, ist-Command, releaseResources

IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} systemFailure, dataMissing, unexpectedDataValue, facilityNotSupported, or-NotAllowed, unknownSubscriber, numberChanged, bearerServiceNotProvisioned, teleserviceNotProvisioned, noRoamingNumberAvailable, absentSubscriber, busySubscriber, noSubscriberReply, callBarred, forwardingViolation, forwardingFailed, cug-Reject, resourceLimitation, incompatibleTerminal, unidentifiedSubscriber FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg, ResumeCallHandlingRes, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes, IST-AlertArg, IST-AlertRes, IST-CommandArg, IST-CommandRes, ReleaseResourcesArg, ReleaseResourcesRes FROM MAP-CH-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CH-DataTypes (13) version10 (10)} ;

1254

3GPP

10590 10591 10592 10593 10594 10595 10596 10597 10598 10599 10600 10601 10602 10603 10604 10605 10606 10607 10608 10609 10610 10611 10612 10613 10614 10615 10616 10617 10618 10619 10620 10621 10622 10623 10624 10625 10626 10627 10628 10629 10630 10631 10632 10633 10634 10635 10636 10637 10638 10639 10640 10641 10642 10643 10644 10645 10646 10647 10648 10649 10650 10651 10652 10653 10654 10655 10656 10657

1255 Release 7 1256 1257

315

3GPP TS 29.002 V7.5.0 (2006-09)

sendRoutingInfo OPERATION ::= { --Timer m -- The timer is set to the upper limit of the range if the GMSC supports pre-paging. ARGUMENT SendRoutingInfoArg RESULT SendRoutingInfoRes ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | or-NotAllowed | unknownSubscriber | numberChanged | bearerServiceNotProvisioned | teleserviceNotProvisioned | absentSubscriber | busySubscriber | noSubscriberReply | callBarred | cug-Reject | forwardingViolation} CODE local:22 } provideRoamingNumber OPERATION ::= { --Timer m -- The timer is set to the upper limit of the range if the HLR supports pre-paging. ARGUMENT ProvideRoamingNumberArg RESULT ProvideRoamingNumberRes ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | or-NotAllowed | absentSubscriber | noRoamingNumberAvailable} CODE local:4 } resumeCallHandling OPERATION ::= { ARGUMENT ResumeCallHandlingArg RESULT ResumeCallHandlingRes -- optional ERRORS { forwardingFailed | or-NotAllowed | unexpectedDataValue | dataMissing } CODE local:6 } setReportingState OPERATION ::= { ARGUMENT SetReportingStateArg RESULT SetReportingStateRes -- optional ERRORS { systemFailure | unidentifiedSubscriber | unexpectedDataValue | dataMissing | resourceLimitation | facilityNotSupported} CODE local:73 } --Timer m

--Timer m

1258

3GPP

10658 10659 10660 10661 10662 10663 10664 10665 10666 10667 10668 10669 10670 10671 10672 10673 10674 10675 10676 10677 10678 10679 10680 10681 10682 10683 10684 10685 10686 10687 10688 10689 10690 10691 10692 10693 10694 10695 10696 10697 10698 10699 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 10712 10713 10714 10715 10716 10717 10718 10719 10720 10721 10722 10723 10724

1259 Release 7 1260 1261

316

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

statusReport OPERATION ::= { ARGUMENT StatusReportArg RESULT StatusReportRes -- optional ERRORS { unknownSubscriber | systemFailure | unexpectedDataValue | dataMissing} CODE local:74 } remoteUserFree OPERATION ::= { ARGUMENT RemoteUserFreeArg RESULT RemoteUserFreeRes ERRORS { unexpectedDataValue | dataMissing | incompatibleTerminal | absentSubscriber | systemFailure | busySubscriber} CODE local:75 } ist-Alert OPERATION ::= { ARGUMENT IST-AlertArg RESULT IST-AlertRes -- optional ERRORS { unexpectedDataValue | resourceLimitation | unknownSubscriber | systemFailure | facilityNotSupported} CODE local:87 } ist-Command OPERATION::= { ARGUMENT IST-CommandArg RESULT IST-CommandRes -- optional ERRORS { unexpectedDataValue | resourceLimitation | unknownSubscriber | systemFailure | facilityNotSupported} CODE local:88 } releaseResources OPERATION::= { ARGUMENT ReleaseResourcesArg RESULT ReleaseResourcesRes -- optional ERRORS { unexpectedDataValue | systemFailure } CODE local:20 }

--Timer ml

--Timer m

--Timer m

--Timer m

END

10725
10726 10727 10728 10729 10730 10731 10732 10733

17.6.4 Supplementary service operations

MAP-SupplementaryServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version10 (10)} DEFINITIONS ::=

1262

3GPP

10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784 10785 10786 10787 10788 10789 10790 10791 10792 10793 10794 10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812

1263 Release 7 1264 1265

BEGIN EXPORTS registerSS, eraseSS, activateSS, deactivateSS, interrogateSS, processUnstructuredSS-Request, unstructuredSS-Request, unstructuredSS-Notify, registerPassword, getPassword, ss-InvocationNotification, registerCC-Entry, eraseCC-Entry ; IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)}

317

3GPP TS 29.002 V7.5.0 (2006-09)

systemFailure, dataMissing, unexpectedDataValue, unknownSubscriber, bearerServiceNotProvisioned, teleserviceNotProvisioned, callBarred, illegalSS-Operation, ss-ErrorStatus, ss-NotAvailable, ss-SubscriptionViolation, ss-Incompatibility, pw-RegistrationFailure, negativePW-Check, numberOfPW-AttemptsViolation, unknownAlphabet, ussd-Busy, absentSubscriber, illegalSubscriber, illegalEquipment, shortTermDenial, longTermDenial, facilityNotSupported FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} RegisterSS-Arg, SS-Info, SS-ForBS-Code, InterrogateSS-Res, USSD-Arg, USSD-Res, Password, GuidanceInfo, SS-InvocationNotificationArg, SS-InvocationNotificationRes, RegisterCC-EntryArg, RegisterCC-EntryRes, EraseCC-EntryArg, EraseCC-EntryRes FROM MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} SS-Code FROM MAP-SS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version10 (10)} ; -- supplementary service handling operations

1266

3GPP

10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868 10869 10870 10871 10872 10873 10874 10875 10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889

1267 Release 7 1268 1269

318

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

registerSS OPERATION ::= { ARGUMENT RegisterSS-Arg RESULT SS-Info -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-ErrorStatus | ss-Incompatibility} CODE local:10 } eraseSS OPERATION ::= { ARGUMENT SS-ForBS-Code RESULT SS-Info -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-ErrorStatus } CODE local:11 } activateSS OPERATION ::= { ARGUMENT SS-ForBS-Code RESULT SS-Info -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-ErrorStatus | ss-SubscriptionViolation | ss-Incompatibility | negativePW-Check | numberOfPW-AttemptsViolation} CODE local:12 } deactivateSS OPERATION ::= { ARGUMENT SS-ForBS-Code RESULT SS-Info -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-ErrorStatus | ss-SubscriptionViolation | negativePW-Check | numberOfPW-AttemptsViolation} CODE local:13 }

--Timer m

--Timer m

--Timer m

1270

3GPP

10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948 10949 10950 10951

1271 Release 7 1272 1273

319

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer m

interrogateSS OPERATION ::= { ARGUMENT SS-ForBS-Code RESULT InterrogateSS-Res ERRORS { systemFailure | dataMissing | unexpectedDataValue | bearerServiceNotProvisioned | teleserviceNotProvisioned | callBarred | illegalSS-Operation | ss-NotAvailable} CODE local:14 } processUnstructuredSS-Request OPERATION ::= { minutes ARGUMENT USSD-Arg RESULT USSD-Res ERRORS { systemFailure | dataMissing | unexpectedDataValue | unknownAlphabet | callBarred} CODE local:59 } unstructuredSS-Request OPERATION ::= { ARGUMENT USSD-Arg RESULT USSD-Res -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | absentSubscriber | illegalSubscriber | illegalEquipment | unknownAlphabet | ussd-Busy} CODE local:60 } unstructuredSS-Notify OPERATION ::= { ARGUMENT USSD-Arg RETURN RESULT TRUE ERRORS { systemFailure | dataMissing | unexpectedDataValue | absentSubscriber | illegalSubscriber | illegalEquipment | unknownAlphabet | ussd-Busy} CODE local:61 }

--Timer 10

--Timer ml

--Timer ml

1274

3GPP

10952 10953 10954 10955 10956 10957 10958 10959 10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021

1275 Release 7 1276 1277

320

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer ml

registerPassword OPERATION ::= { ARGUMENT SS-Code RESULT Password ERRORS { systemFailure | dataMissing | unexpectedDataValue | callBarred | ss-SubscriptionViolation | pw-RegistrationFailure | negativePW-Check | numberOfPW-AttemptsViolation} LINKED { getPassword} CODE local:17 } getPassword OPERATION ::= { ARGUMENT GuidanceInfo RESULT Password CODE local:18 } ss-InvocationNotification OPERATION ::= { ARGUMENT SS-InvocationNotificationArg RESULT SS-InvocationNotificationRes -- optional ERRORS { dataMissing | unexpectedDataValue | unknownSubscriber} CODE local:72 } registerCC-Entry OPERATION ::= { ARGUMENT RegisterCC-EntryArg RESULT RegisterCC-EntryRes ERRORS { systemFailure | dataMissing | unexpectedDataValue | callBarred | illegalSS-Operation | ss-ErrorStatus | ss-Incompatibility | shortTermDenial | longTermDenial | facilityNotSupported} CODE local:76 } eraseCC-Entry OPERATION ::= { ARGUMENT EraseCC-EntryArg RESULT EraseCC-EntryRes ERRORS { systemFailure | dataMissing | unexpectedDataValue | callBarred | illegalSS-Operation | ss-ErrorStatus} CODE local:77 }

--Timer m

--Timer m

--Timer m

--Timer m

END

11022
11023 11024 11025 11026

17.6.5 Short message service operations

MAP-ShortMessageServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) version10 (10)}

1278

3GPP

11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040 11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056 11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072 11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088 11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101 11102 11103 11104

1279 Release 7 1280 1281

DEFINITIONS ::= BEGIN EXPORTS sendRoutingInfoForSM, mo-ForwardSM, mt-ForwardSM, reportSM-DeliveryStatus, alertServiceCentre, informServiceCentre, readyForSM, mt-ForwardSM-VGCS ; IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)}

321

3GPP TS 29.002 V7.5.0 (2006-09)

systemFailure, dataMissing, unexpectedDataValue, facilityNotSupported, unknownSubscriber, unidentifiedSubscriber, illegalSubscriber, illegalEquipment, teleserviceNotProvisioned, callBarred, subscriberBusyForMT-SMS, sm-DeliveryFailure, messageWaitingListFull, absentSubscriberSM FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} RoutingInfoForSM-Arg, RoutingInfoForSM-Res, MO-ForwardSM-Arg, MO-ForwardSM-Res, MT-ForwardSM-Arg, MT-ForwardSM-Res, ReportSM-DeliveryStatusArg, ReportSM-DeliveryStatusRes, AlertServiceCentreArg, InformServiceCentreArg, ReadyForSM-Arg, ReadyForSM-Res, MT-ForwardSM-VGCS-Arg, MT-ForwardSM-VGCS-Res FROM MAP-SM-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version10 (10)} ; sendRoutingInfoForSM OPERATION ::= { ARGUMENT RoutingInfoForSM-Arg RESULT RoutingInfoForSM-Res ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unknownSubscriber | teleserviceNotProvisioned | callBarred | absentSubscriberSM} CODE local:45 } --Timer m

1282

3GPP

11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120 11121 11122 11123 11124 11125 11126 11127 11128 11129 11130 11131 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11149 11150 11151 11152 11153 11154 11155 11156 11157 11158 11159 11160 11161 11162 11163 11164 11165 11166 11167 11168 11169 11170 11171 11172 11173 11174 11175 11176 11177

1283 Release 7 1284 1285

322

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer ml

mo-ForwardSM OPERATION ::= { ARGUMENT MO-ForwardSM-Arg RESULT MO-ForwardSM-Res -- optional ERRORS { systemFailure | unexpectedDataValue | facilityNotSupported | sm-DeliveryFailure} CODE local:46 } mt-ForwardSM OPERATION ::= { ARGUMENT MT-ForwardSM-Arg RESULT MT-ForwardSM-Res -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unidentifiedSubscriber | illegalSubscriber | illegalEquipment | subscriberBusyForMT-SMS | sm-DeliveryFailure | absentSubscriberSM} CODE local:44 } reportSM-DeliveryStatus OPERATION ::= { ARGUMENT ReportSM-DeliveryStatusArg RESULT ReportSM-DeliveryStatusRes -- optional ERRORS { dataMissing | unexpectedDataValue | unknownSubscriber | messageWaitingListFull} CODE local:47 } alertServiceCentre OPERATION ::= { ARGUMENT AlertServiceCentreArg RETURN RESULT TRUE ERRORS { systemFailure | dataMissing | unexpectedDataValue} CODE local:64 } informServiceCentre OPERATION ::= { ARGUMENT InformServiceCentreArg CODE local:63 } readyForSM OPERATION ::= { ARGUMENT ReadyForSM-Arg RESULT ReadyForSM-Res -- optional ERRORS { dataMissing | unexpectedDataValue | facilityNotSupported | unknownSubscriber} CODE local:66 } --Timer s

--Timer ml

--Timer s

--Timer s

--Timer m

1286

3GPP

11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190

1287 Release 7 1288 1289

323

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer ml

mt-ForwardSM-VGCS OPERATION ::= { ARGUMENT MT-ForwardSM-VGCS-Arg RESULT MT-ForwardSM-VGCS-Res -- optional ERRORS { systemFailure | unexpectedDataValue } CODE local:21 }

END

11191
11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224 11225 11226 11227 11228 11229 11230 11231 11232 11233 11234 11235 11236 11237 11238 11239 11240 11241 11242 11243 11244 11245 11246 11247 11248 11249 11250 11251 11252

17.6.6 Errors
MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} DEFINITIONS ::= BEGIN EXPORTS -- generic errors systemFailure, dataMissing, unexpectedDataValue, facilityNotSupported, incompatibleTerminal, resourceLimitation, -- identification and numbering errors unknownSubscriber, numberChanged, unknownMSC, unidentifiedSubscriber, unknownEquipment, -- subscription errors roamingNotAllowed, illegalSubscriber, illegalEquipment, bearerServiceNotProvisioned, teleserviceNotProvisioned, -- handover errors noHandoverNumberAvailable, subsequentHandoverFailure, targetCellOutsideGroupCallArea, -- operation and maintenance errors tracingBufferFull, -- call handling errors or-NotAllowed, noRoamingNumberAvailable, busySubscriber, noSubscriberReply, absentSubscriber, callBarred, forwardingViolation, forwardingFailed, cug-Reject, -- any time interrogation errors ati-NotAllowed, -- any time information handling errors atsi-NotAllowed, atm-NotAllowed, informationNotAvailable,

1290

3GPP

11253 11254 11255 11256 11257 11258 11259 11260 11261 11262 11263 11264 11265 11266 11267 11268 11269 11270 11271 11272 11273 11274 11275 11276 11277 11278 11279 11280 11281 11282 11283 11284 11285 11286 11287 11288 11289 11290 11291 11292 11293 11294 11295 11296 11297 11298 11299 11300 11301 11302 11303 11304 11305 11306 11307 11308 11309 11310 11311 11312 11313 11314 11315 11316 11317 11318 11319 11320 11321 11322 11323 11324 11325 11326 11327 11328 11329 11330 11331

1291 Release 7 1292 1293

324

3GPP TS 29.002 V7.5.0 (2006-09)

-- supplementary service errors illegalSS-Operation, ss-ErrorStatus, ss-NotAvailable, ss-SubscriptionViolation, ss-Incompatibility, unknownAlphabet, ussd-Busy, pw-RegistrationFailure, negativePW-Check, numberOfPW-AttemptsViolation, shortTermDenial, longTermDenial, -- short message service errors subscriberBusyForMT-SMS, sm-DeliveryFailure, messageWaitingListFull, absentSubscriberSM, -- Group Call errors noGroupCallNumberAvailable, ongoingGroupCall, -- location service errors unauthorizedRequestingNetwork, unauthorizedLCSClient, positionMethodFailure, unknownOrUnreachableLCSClient, -- Mobility Management errors mm-EventNotSupported

; IMPORTS ERROR FROM Remote-Operations-Information-Objects {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0) } SS-Status FROM MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, RoamingNotAllowedParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam, TracingBufferFullParam, NoRoamingNbParam, OR-NotAllowedParam, AbsentSubscriberParam, BusySubscriberParam, NoSubscriberReplyParam, CallBarredParam, ForwardingViolationParam, ForwardingFailedParam, CUG-RejectParam, ATI-NotAllowedParam, SubBusyForMT-SMS-Param, MessageWaitListFullParam, AbsentSubscriberSM-Param, ResourceLimitationParam, NoGroupCallNbParam, IncompatibleTerminalParam, ShortTermDenialParam,

1294

3GPP

11332 11333 11334 11335 11336 11337 11338 11339 11340 11341 11342 11343 11344 11345 11346 11347 11348 11349 11350 11351 11352 11353 11354 11355 11356 11357 11358 11359 11360 11361 11362 11363 11364 11365 11366 11367 11368 11369 11370 11371 11372 11373 11374 11375 11376 11377 11378 11379 11380 11381 11382 11383 11384 11385 11386 11387 11388 11389 11390 11391 11392 11393 11394 11395 11396 11397 11398 11399 11400 11401 11402 11403 11404 11405 11406 11407 11408 11409

1295 Release 7 1296 1297

325

3GPP TS 29.002 V7.5.0 (2006-09)

LongTermDenialParam, UnauthorizedRequestingNetwork-Param, UnauthorizedLCSClient-Param, PositionMethodFailure-Param, UnknownOrUnreachableLCSClient-Param, MM-EventNotSupported-Param, ATSI-NotAllowedParam, ATM-NotAllowedParam, IllegalSS-OperationParam, SS-NotAvailableParam, SS-SubscriptionViolationParam, InformationNotAvailableParam, TargetCellOutsideGCA-Param, OngoingGroupCallParam FROM MAP-ER-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version10 (10)} ; -- generic errors systemFailure ERROR ::= { PARAMETER SystemFailureParam -- optional CODE local:34 } dataMissing ERROR ::= { PARAMETER DataMissingParam -- optional -- DataMissingParam must not be used in version <3 CODE local:35 } unexpectedDataValue ERROR ::= { PARAMETER UnexpectedDataParam -- optional -- UnexpectedDataParam must not be used in version <3 CODE local:36 } facilityNotSupported ERROR ::= { PARAMETER FacilityNotSupParam -- optional -- FacilityNotSupParam must not be used in version <3 CODE local:21 } incompatibleTerminal ERROR ::= { PARAMETER IncompatibleTerminalParam -- optional CODE local:28 } resourceLimitation ERROR ::= { PARAMETER ResourceLimitationParam -- optional CODE local:51 } -- identification and numbering errors unknownSubscriber ERROR ::= { PARAMETER UnknownSubscriberParam -- optional -- UnknownSubscriberParam must not be used in version <3 CODE local:1 } numberChanged ERROR ::= { PARAMETER NumberChangedParam -- optional CODE local:44 } unknownMSC ERROR ::= { CODE local:3 }

1298

3GPP

11410 11411 11412 11413 11414 11415 11416 11417 11418 11419 11420 11421 11422 11423 11424 11425 11426 11427 11428 11429 11430 11431 11432 11433 11434 11435 11436 11437 11438 11439 11440 11441 11442 11443 11444 11445 11446 11447 11448 11449 11450 11451 11452 11453 11454 11455 11456 11457 11458 11459 11460 11461 11462 11463 11464 11465 11466 11467 11468 11469 11470 11471 11472 11473 11474 11475 11476 11477 11478 11479 11480 11481 11482 11483 11484

1299 Release 7 1300 1301

326

3GPP TS 29.002 V7.5.0 (2006-09)

unidentifiedSubscriber ERROR ::= { PARAMETER UnidentifiedSubParam -- optional -- UunidentifiedSubParam must not be used in version <3 CODE local:5 } unknownEquipment ERROR ::= { CODE local:7 }

-- subscription errors roamingNotAllowed ERROR ::= { PARAMETER RoamingNotAllowedParam CODE local:8 } illegalSubscriber ERROR ::= { PARAMETER IllegalSubscriberParam -- optional -- IllegalSubscriberParam must not be used in version <3 CODE local:9 } illegalEquipment ERROR ::= { PARAMETER IllegalEquipmentParam -- optional -- IllegalEquipmentParam must not be used in version <3 CODE local:12 } bearerServiceNotProvisioned ERROR ::= { PARAMETER BearerServNotProvParam -- optional -- BearerServNotProvParam must not be used in version <3 CODE local:10 } teleserviceNotProvisioned ERROR ::= { PARAMETER TeleservNotProvParam -- optional -- TeleservNotProvParam must not be used in version <3 CODE local:11 } -- handover errors noHandoverNumberAvailable CODE local:25 } subsequentHandoverFailure CODE local:26 } ERROR ::= { ERROR ::= {

targetCellOutsideGroupCallArea ERROR ::= { PARAMETER TargetCellOutsideGCA-Param -- optional CODE local:42 } -- operation and maintenance errors tracingBufferFull ERROR ::= { PARAMETER TracingBufferFullParam -- optional CODE local: 40 } -- call handling errors noRoamingNumberAvailable ERROR ::= { PARAMETER NoRoamingNbParam -- optional CODE local:39 }

1302

3GPP

11485 11486 11487 11488 11489 11490 11491 11492 11493 11494 11495 11496 11497 11498 11499 11500 11501 11502 11503 11504 11505 11506 11507 11508 11509 11510 11511 11512 11513 11514 11515 11516 11517 11518 11519 11520 11521 11522 11523 11524 11525 11526 11527 11528 11529 11530 11531 11532 11533 11534 11535 11536 11537 11538 11539 11540 11541 11542 11543 11544 11545 11546 11547 11548 11549 11550 11551 11552 11553 11554 11555 11556 11557 11558 11559 11560 11561

1303 Release 7 1304 1305

327

3GPP TS 29.002 V7.5.0 (2006-09)

absentSubscriber ERROR ::= { PARAMETER AbsentSubscriberParam -- optional -- AbsentSubscriberParam must not be used in version <3 CODE local:27 } busySubscriber ERROR ::= { PARAMETER BusySubscriberParam -- optional CODE local:45 } noSubscriberReply ERROR ::= { PARAMETER NoSubscriberReplyParam -- optional CODE local:46 } callBarred ERROR ::= { PARAMETER CallBarredParam -- optional CODE local:13 } forwardingViolation ERROR ::= { PARAMETER ForwardingViolationParam -- optional CODE local:14 } forwardingFailed ERROR ::= { PARAMETER ForwardingFailedParam -- optional CODE local:47 } cug-Reject ERROR ::= { PARAMETER CUG-RejectParam -- optional CODE local:15 } or-NotAllowed ERROR ::= { PARAMETER OR-NotAllowedParam -- optional CODE local:48 }

-- any time interrogation errors ati-NotAllowed ERROR ::= { PARAMETER ATI-NotAllowedParam -- optional CODE local:49 } -- any time information handling errors atsi-NotAllowed ERROR ::= { PARAMETER ATSI-NotAllowedParam -- optional CODE local:60 } atm-NotAllowed ERROR ::= { PARAMETER ATM-NotAllowedParam -- optional CODE local:61 } informationNotAvailable ERROR ::= { PARAMETER InformationNotAvailableParam -- optional CODE local:62 } -- supplementary service errors

1306

3GPP

11562 11563 11564 11565 11566 11567 11568 11569 11570 11571 11572 11573 11574 11575 11576 11577 11578 11579 11580 11581 11582 11583 11584 11585 11586 11587 11588 11589 11590 11591 11592 11593 11594 11595 11596 11597 11598 11599 11600 11601 11602 11603 11604 11605 11606 11607 11608 11609 11610 11611 11612 11613 11614 11615 11616 11617 11618 11619 11620 11621 11622 11623 11624 11625 11626 11627 11628 11629 11630 11631 11632 11633 11634 11635 11636

1307 Release 7 1308 1309

328

3GPP TS 29.002 V7.5.0 (2006-09)

illegalSS-Operation ERROR ::= { PARAMETER IllegalSS-OperationParam -- optional -- IllegalSS-OperationParam must not be used in version <3 CODE local:16 } ss-ErrorStatus ERROR ::= { PARAMETER SS-Status -- optional CODE local:17 } ss-NotAvailable ERROR ::= { PARAMETER SS-NotAvailableParam -- optional -- SS-NotAvailableParam must not be used in version <3 CODE local:18 } ss-SubscriptionViolation ERROR ::= { PARAMETER SS-SubscriptionViolationParam -- optional -- SS-SubscriptionViolationParam must not be used in version <3 CODE local:19 } ss-Incompatibility ERROR ::= { PARAMETER SS-IncompatibilityCause -- optional CODE local:20 } unknownAlphabet ERROR ::= { CODE local:71 } ussd-Busy ERROR ::= { CODE local:72 } pw-RegistrationFailure ERROR ::= { PARAMETER PW-RegistrationFailureCause CODE local:37 } negativePW-Check ERROR ::= { CODE local:38 } numberOfPW-AttemptsViolation CODE local:43 } shortTermDenial ERROR ::= { PARAMETER ShortTermDenialParam -- optional CODE local:29 } longTermDenial ERROR ::= { PARAMETER LongTermDenialParam -- optional CODE local:30 } ERROR ::= {

-- short message service errors subscriberBusyForMT-SMS ERROR ::= { PARAMETER SubBusyForMT-SMS-Param -- optional CODE local:31 } sm-DeliveryFailure ERROR ::= { PARAMETER SM-DeliveryFailureCause CODE local:32 }

1310

3GPP

11637 11638 11639 11640 11641 11642 11643 11644 11645 11646 11647 11648 11649 11650 11651 11652 11653 11654 11655 11656 11657 11658 11659 11660 11661 11662 11663 11664 11665 11666 11667 11668 11669 11670 11671 11672 11673 11674 11675 11676 11677 11678 11679 11680 11681 11682 11683 11684 11685 11686 11687 11688 11689 11690 11691 11692 11693 11694 11695 11696

1311 Release 7 1312 1313

329

3GPP TS 29.002 V7.5.0 (2006-09)

messageWaitingListFull ERROR ::= { PARAMETER MessageWaitListFullParam -- optional CODE local:33 } absentSubscriberSM ERROR ::= { PARAMETER AbsentSubscriberSM-Param -- optional CODE local:6 }

-- Group Call errors noGroupCallNumberAvailable ERROR ::= { PARAMETER NoGroupCallNbParam -- optional CODE local:50 } ongoingGroupCall ERROR ::= { PARAMETER OngoingGroupCallParam -- optional CODE local:22 } -- location service errors unauthorizedRequestingNetwork ERROR ::= { PARAMETER UnauthorizedRequestingNetwork-Param -- optional CODE local:52 } unauthorizedLCSClient ERROR ::= { PARAMETER UnauthorizedLCSClient-Param -- optional CODE local:53 } positionMethodFailure ERROR ::= { PARAMETER PositionMethodFailure-Param -- optional CODE local:54 } unknownOrUnreachableLCSClient ERROR ::= { PARAMETER UnknownOrUnreachableLCSClient-Param -- optional CODE local:58 } mm-EventNotSupported ERROR ::= { PARAMETER MM-EventNotSupported-Param -- optional CODE local:59 } END

11697
11698 11699 11700 11701 11702 11703 11704 11705 11706 11707 11708 11709 11710 11711

17.6.7 Group Call operations

MAP-Group-Call-Operations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Group-Call-Operations (22) version10 (10)} DEFINITIONS ::= BEGIN EXPORTS prepareGroupCall, sendGroupCallEndSignal,

1314

3GPP

11712 11713 11714 11715 11716 11717 11718 11719 11720 11721 11722 11723 11724 11725 11726 11727 11728 11729 11730 11731 11732 11733 11734 11735 11736 11737 11738 11739 11740 11741 11742 11743 11744 11745 11746 11747 11748 11749 11750 11751 11752 11753 11754 11755 11756 11757 11758 11759 11760 11761 11762 11763 11764 11765 11766 11767 11768 11769 11770 11771 11772 11773 11774 11775 11776 11777 11778 11779 11780 11781 11782 11783 11784 11785 11786 11787 11788 11789

1315 Release 7 1316 1317

330

3GPP TS 29.002 V7.5.0 (2006-09)

forwardGroupCallSignalling, processGroupCallSignalling, sendGroupCallInfo

IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} systemFailure, unexpectedDataValue, noGroupCallNumberAvailable, ongoingGroupCall, unknownSubscriber, teleserviceNotProvisioned, dataMissing FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} PrepareGroupCallArg, PrepareGroupCallRes, SendGroupCallEndSignalArg, SendGroupCallEndSignalRes, ForwardGroupCallSignallingArg, ProcessGroupCallSignallingArg, SendGroupCallInfoArg, SendGroupCallInfoRes FROM MAP-GR-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-GR-DataTypes (23) version10 (10)} ; prepareGroupCall OPERATION ::= { ARGUMENT PrepareGroupCallArg RESULT PrepareGroupCallRes ERRORS { systemFailure | noGroupCallNumberAvailable | unexpectedDataValue} CODE local:39 } sendGroupCallEndSignal OPERATION ::= { ARGUMENT SendGroupCallEndSignalArg RESULT SendGroupCallEndSignalRes CODE local:40 } processGroupCallSignalling OPERATION ::= { ARGUMENT ProcessGroupCallSignallingArg CODE local:41 } forwardGroupCallSignalling OPERATION ::= { ARGUMENT ForwardGroupCallSignallingArg CODE local:42 } sendGroupCallInfo OPERATION ::= { ARGUMENT SendGroupCallInfoArg RESULT SendGroupCallInfoRes ERRORS { systemFailure | ongoingGroupCall | unexpectedDataValue | dataMissing | teleserviceNotProvisioned | unknownSubscriber} CODE local:84 } --Timer m

--Timer l

--Timer s

--Timer s

--Timer m

1318

3GPP

11790 11791

1319 Release 7 1320 1321

END

331

3GPP TS 29.002 V7.5.0 (2006-09)

17.6.8 Location service operations

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67

MAP-LocationServiceOperations { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version10 (10)} DEFINITIONS ::= BEGIN EXPORTS provideSubscriberLocation, sendRoutingInfoForLCS, subscriberLocationReport ; IMPORTS OPERATION FROM Remote-Operations-Information-Objects { joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} systemFailure, dataMissing, unexpectedDataValue, facilityNotSupported, unknownSubscriber, absentSubscriber, unauthorizedRequestingNetwork, unauthorizedLCSClient, positionMethodFailure, resourceLimitation, unknownOrUnreachableLCSClient, unidentifiedSubscriber, illegalEquipment, illegalSubscriber FROM MAP-Errors { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version10 (10)} RoutingInfoForLCS-Arg, RoutingInfoForLCS-Res, ProvideSubscriberLocation-Arg, ProvideSubscriberLocation-Res, SubscriberLocationReport-Arg, SubscriberLocationReport-Res FROM MAP-LCS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LCS-DataTypes (25) version10 (10)} ; sendRoutingInfoForLCS OPERATION ::= { ARGUMENT RoutingInfoForLCS-Arg RESULT RoutingInfoForLCS-Res ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unknownSubscriber | absentSubscriber | unauthorizedRequestingNetwork } CODE local:85 } --Timer m

1322

3GPP

1323 Release 7 1324 1325

68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85

332

3GPP TS 29.002 V7.5.0 (2006-09)

--Timer ml

provideSubscriberLocation OPERATION ::= { ARGUMENT ProvideSubscriberLocation-Arg RESULT ProvideSubscriberLocation-Res ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unidentifiedSubscriber | illegalSubscriber | illegalEquipment | absentSubscriber | unauthorizedRequestingNetwork | unauthorizedLCSClient | positionMethodFailure } CODE local:83 } subscriberLocationReport OPERATION ::= { ARGUMENT SubscriberLocationReport-Arg RESULT SubscriberLocationReport-Res ERRORS { systemFailure | dataMissing | resourceLimitation | unexpectedDataValue | unknownSubscriber | unauthorizedRequestingNetwork | unknownOrUnreachableLCSClient} CODE local:86 }

86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 1

--Timer m

END

17.6.9 Void
2

3 4
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

17.7 MAP constants and data types

17.7.1 Mobile Service data types
MAP-MS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS -- location registration types UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationArg, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes, IST-SupportIndicator, SupportedLCS-CapabilitySets,

1326

3GPP

1327 Release 7 1328 1329

33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111

333

3GPP TS 29.002 V7.5.0 (2006-09)

-- gprs location registration types GSN-Address, -- handover types ForwardAccessSignalling-Arg, PrepareHO-Arg, PrepareHO-Res, PrepareSubsequentHO-Arg, PrepareSubsequentHO-Res, ProcessAccessSignalling-Arg, SendEndSignal-Arg, SendEndSignal-Res, -- authentication management types SendAuthenticationInfoArg, SendAuthenticationInfoRes, AuthenticationFailureReportArg, AuthenticationFailureReportRes, -- security management types Kc, Cksn, -- equipment management types CheckIMEI-Arg, CheckIMEI-Res, -- subscriber management types InsertSubscriberDataArg, InsertSubscriberDataRes, LSAIdentity, DeleteSubscriberDataArg, DeleteSubscriberDataRes, Ext-QoS-Subscribed, Ext2-QoS-Subscribed, SubscriberData, ODB-Data, SubscriberStatus, ZoneCodeList, maxNumOfZoneCodes, O-CSI, D-CSI, O-BcsmCamelTDPCriteriaList, T-BCSM-CAMEL-TDP-CriteriaList, SS-CSI, ServiceKey, DefaultCallHandling, CamelCapabilityHandling, BasicServiceCriteria, SupportedCamelPhases, OfferedCamel4CSIs, OfferedCamel4Functionalities, maxNumOfCamelTDPData, CUG-Index, CUG-Info, CUG-Interlock, InterCUG-Restrictions, IntraCUG-Options, NotificationToMSUser, QoS-Subscribed, IST-AlertTimerValue, T-CSI, T-BcsmTriggerDetectionPoint, APN, AdditionalInfo, -- fault recovery types ResetArg, RestoreDataArg, RestoreDataRes,

-- provide subscriber info types GeographicalInformation, MS-Classmark2, GPRSMSClass, -- subscriber information enquiry types ProvideSubscriberInfoArg, ProvideSubscriberInfoRes,

1330

3GPP

1331 Release 7 1332 1333

112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190

334

3GPP TS 29.002 V7.5.0 (2006-09)

SubscriberInfo, LocationInformation, LocationInformationGPRS, RAIdentity, SubscriberState, GPRSChargingID,

MNPInfoRes,

RouteingNumber, -- any time information enquiry types AnyTimeInterrogationArg, AnyTimeInterrogationRes, -- any time information handling types AnyTimeSubscriptionInterrogationArg, AnyTimeSubscriptionInterrogationRes, AnyTimeModificationArg, AnyTimeModificationRes, -- subscriber data modification notification types NoteSubscriberDataModifiedArg, NoteSubscriberDataModifiedRes, -- gprs location information retrieval types SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, -- failure reporting types FailureReportArg, FailureReportRes, -- gprs notification types NoteMsPresentForGprsArg, NoteMsPresentForGprsRes, -- Mobility Management types NoteMM-EventArg, NoteMM-EventRes, NumberPortabilityStatus, -- VGCS / VBS types types GroupId, AdditionalSubscriptions ; IMPORTS maxNumOfSS, SS-SubscriptionOption, SS-List, SS-ForBS-Code, Password FROM MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} SS-Code FROM MAP-SS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version10 (10)} Ext-BearerServiceCode FROM MAP-BS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version10 (10)} Ext-TeleserviceCode FROM MAP-TS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version10 (10)} AddressString, ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString, AccessNetworkSignalInfo, IMSI, IMEI, TMSI,

1334

3GPP

1335 Release 7 1336 1337

191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268

335

3GPP TS 29.002 V7.5.0 (2006-09)

HLR-List, LMSI, Identity, GlobalCellId, CellGlobalIdOrServiceAreaIdOrLAI, Ext-BasicServiceCode, NAEA-PreferredCI, EMLPP-Info, MC-SS-Info, SubscriberIdentity, AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, Ext-SS-Status, LCSServiceTypeID, ASCI-CallReference, TBCD-STRING, LAIFixedLength, PLMN-Id FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version10 (10)} TracePropagationList FROM MAP-OM-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version10 (10)} ; -- location registration types UpdateLocationArg ::= SEQUENCE { imsi msc-Number vlr-Number lmsi extensionContainer ... , vlr-Capability informPreviousNetworkEntity cs-LCS-NotSupportedByUE v-gmlc-Address add-info IMSI, [1] ISDN-AddressString, ISDN-AddressString, [10] LMSI ExtensionContainer [6] VLR-Capability [11] NULL [12] NULL [2] GSN-Address [13] ADD-Info

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

VLR-Capability ::= SEQUENCE{ supportedCamelPhases [0] SupportedCamelPhases extensionContainer ExtensionContainer ... , solsaSupportIndicator [2] NULL istSupportIndicator [1] IST-SupportIndicator superChargerSupportedInServingNetworkEntity [3] SuperChargerInfo longFTN-Supported [4] NULL supportedLCS-CapabilitySets [5] SupportedLCS-CapabilitySets offeredCamel4CSIs [6] OfferedCamel4CSIs supportedRAT-TypesIndicator [7] SupportedRAT-Types

SupportedRAT-Types::= BIT STRING { utran (0), geran (1)} (SIZE (2..8)) -- exception handling: bits 2 to 7 shall be ignored if received and not understood

SuperChargerInfo ::= CHOICE { sendSubscriberData subscriberDataStored

[0] NULL, [1] AgeIndicator }

1338

3GPP

1339 Release 7 1340 1341

269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337

336

3GPP TS 29.002 V7.5.0 (2006-09)

AgeIndicator ::= OCTET STRING (SIZE (1..6)) -- The internal structure of this parameter is implementation specific. IST-SupportIndicator ::= ENUMERATED { basicISTSupported (0), istCommandSupported (1), ...} -- exception handling: -- reception of values > 1 shall be mapped to ' istCommandSupported ' SupportedLCS-CapabilitySets ::= BIT STRING { lcsCapabilitySet1 (0), lcsCapabilitySet2 (1), lcsCapabilitySet3 (2), lcsCapabilitySet4 (3) , lcsCapabilitySet5 (4) } (SIZE (2..16)) -- Core network signalling capability set1 indicates LCS Release98 or Release99 version. -- Core network signalling capability set2 indicates LCS Release4. -- Core network signalling capability set3 indicates LCS Release5. -- Core network signalling capability set4 indicates LCS Release6. -- Core network signalling capability set5 indicates LCS Release7 or later version. -- A node shall mark in the BIT STRING all LCS capability sets it supports. -- If no bit is set then the sending node does not support LCS. -- If the parameter is not sent by an VLR then the VLR may support at most capability set1. -- If the parameter is not sent by an SGSN then no support for LCS is assumed. -- An SGSN is not allowed to indicate support of capability set1. -- Other bits than listed above shall be discarded. UpdateLocationRes ::= SEQUENCE { hlr-Number extensionContainer ..., add-Capability ADD-Info ::= SEQUENCE { imeisv skipSubscriberDataUpdate ...} CancelLocationArg ::= [3] SEQUENCE { identity cancellationType extensionContainer ...} ISDN-AddressString, ExtensionContainer NULL [0] IMEI, [1] NULL

OPTIONAL, OPTIONAL }

OPTIONAL,

Identity, CancellationType ExtensionContainer

OPTIONAL, OPTIONAL,

CancellationType ::= ENUMERATED { updateProcedure (0), subscriptionWithdraw (1), ...} -- The HLR shall not send values other than listed above CancelLocationRes ::= SEQUENCE { extensionContainer ...} PurgeMS-Arg ::= [3] SEQUENCE { imsi vlr-Number sgsn-Number extensionContainer ...} PurgeMS-Res ::= SEQUENCE { freezeTMSI freezeP-TMSI extensionContainer ...} ExtensionContainer OPTIONAL,

IMSI, [0] ISDN-AddressString [1] ISDN-AddressString ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

[0] NULL [1] NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

1342

3GPP

1343 Release 7 1344 1345

338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414

337

3GPP TS 29.002 V7.5.0 (2006-09)

SendIdentificationArg ::= SEQUENCE { tmsi TMSI, numberOfRequestedVectors NumberOfRequestedVectors OPTIONAL, -- within a dialogue numberOfRequestedVectors shall be present in -- the first service request and shall not be present in subsequent service requests. -- If received in a subsequent service request it shall be discarded. segmentationProhibited NULL OPTIONAL, extensionContainer ExtensionContainer OPTIONAL, ..., msc-Number ISDN-AddressString OPTIONAL, previous-LAI [0] LAIFixedLength OPTIONAL, hopCounter [1] HopCounter OPTIONAL } HopCounter ::= INTEGER (0..3) SendIdentificationRes ::= [3] SEQUENCE { imsi IMSI OPTIONAL, -- IMSI shall be present in the first (or only) service response of a dialogue. -- If multiple service requests are present in a dialogue then IMSI -- shall not be present in any service response other than the first one. authenticationSetList AuthenticationSetList OPTIONAL, currentSecurityContext [2]CurrentSecurityContext OPTIONAL, extensionContainer [3] ExtensionContainer OPTIONAL, ...}

-- authentication management types AuthenticationSetList ::= CHOICE { tripletList quintupletList TripletList ::= SEQUENCE SIZE (1..5) OF [0] TripletList, [1] QuintupletList } AuthenticationTriplet

QuintupletList ::= SEQUENCE SIZE (1..5) OF AuthenticationQuintuplet AuthenticationTriplet ::= SEQUENCE { rand sres kc ...} AuthenticationQuintuplet ::= SEQUENCE { rand xres ck ik autn ...} CurrentSecurityContext ::= CHOICE { gsm-SecurityContextData umts-SecurityContextData GSM-SecurityContextData ::= SEQUENCE { kc cksn ... } UMTS-SecurityContextData ::= SEQUENCE { ck ik ksi ... } RAND ::= OCTET STRING (SIZE (16)) SRES ::= OCTET STRING (SIZE (4)) Kc ::= OCTET STRING (SIZE (8)) XRES ::= OCTET STRING (SIZE (4..16)) CK ::= OCTET STRING (SIZE (16)) IK ::= OCTET STRING (SIZE (16)) RAND, SRES, Kc,

RAND, XRES, CK, IK, AUTN,

[0] GSM-SecurityContextData, [1] UMTS-SecurityContextData } Kc, Cksn,

CK, IK, KSI,

1346

3GPP

1347 Release 7 1348 1349

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

338

3GPP TS 29.002 V7.5.0 (2006-09)

AUTN ::= OCTET STRING (SIZE (16)) AUTS ::= OCTET STRING (SIZE (14)) Cksn ::= OCTET STRING (SIZE (1)) -- The internal structure is defined in 3GPP TS 24.008 KSI ::= OCTET STRING (SIZE (1)) -- The internal structure is defined in 3GPP TS 24.008 AuthenticationFailureReportArg ::= SEQUENCE { imsi IMSI, failureCause FailureCause, extensionContainer ExtensionContainer ... , re-attempt BOOLEAN accessType AccessType rand RAND vlr-Number [0] ISDN-AddressString sgsn-Number [1] ISDN-AddressString AccessType ::= ENUMERATED { call (0), emergencyCall (1), locationUpdating (2), supplementaryService (3), shortMessage (4), gprsAttach (5), routingAreaUpdating (6), serviceRequest (7), pdpContextActivation (8), pdpContextDeactivation (9), ..., gprsDetach (10)} -- exception handling: -- received values greater than 10 shall be ignored. AuthenticationFailureReportRes ::= SEQUENCE { extensionContainer ExtensionContainer ...} FailureCause ::= ENUMERATED { wrongUserResponse (0), wrongNetworkSignature (1)} -- gprs location registration types UpdateGprsLocationArg ::= SEQUENCE { imsi sgsn-Number sgsn-Address extensionContainer ... , sgsn-Capability informPreviousNetworkEntity ps-LCS-NotSupportedByUE v-gmlc-Address add-info IMSI, ISDN-AddressString, GSN-Address, ExtensionContainer [0] SGSN-Capability [1] NULL [2] NULL [3] GSN-Address [4] ADD-Info OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL, OPTIONAL , OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

SGSN-Capability ::= SEQUENCE{ solsaSupportIndicator NULL extensionContainer [1] ExtensionContainer ... , superChargerSupportedInServingNetworkEntity [2] SuperChargerInfo gprsEnhancementsSupportIndicator [3] NULL supportedCamelPhases [4] SupportedCamelPhases supportedLCS-CapabilitySets [5] SupportedLCS-CapabilitySets offeredCamel4CSIs [6] OfferedCamel4CSIs smsCallBarringSupportIndicator [7] NULL supportedRAT-TypesIndicator [8] SupportedRAT-Types GSN-Address ::= OCTET STRING (SIZE (5..17)) -- Octets are coded according to TS 3GPP TS 23.003 [17]

1350

3GPP

1351 Release 7 1352 1353

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

339

3GPP TS 29.002 V7.5.0 (2006-09)

UpdateGprsLocationRes ::= SEQUENCE { hlr-Number extensionContainer ..., add-Capability

ISDN-AddressString, ExtensionContainer NULL

OPTIONAL, OPTIONAL }

-- handover types ForwardAccessSignalling-Arg ::= [3] SEQUENCE { an-APDU AccessNetworkSignalInfo, integrityProtectionInfo [0] IntegrityProtectionInformation OPTIONAL, encryptionInfo [1] EncryptionInformation OPTIONAL, keyStatus [2] KeyStatus OPTIONAL, allowedGSM-Algorithms [4] AllowedGSM-Algorithms OPTIONAL, allowedUMTS-Algorithms [5] AllowedUMTS-Algorithms OPTIONAL, radioResourceInformation [6] RadioResourceInformation OPTIONAL, extensionContainer [3] ExtensionContainer OPTIONAL, ..., radioResourceList [7] RadioResourceList OPTIONAL, bssmap-ServiceHandover [9] BSSMAP-ServiceHandover OPTIONAL, ranap-ServiceHandover [8] RANAP-ServiceHandover OPTIONAL, bssmap-ServiceHandoverList [10] BSSMAP-ServiceHandoverList OPTIONAL, currentlyUsedCodec [11] Codec OPTIONAL, iuSupportedCodecsList [12] SupportedCodecsList OPTIONAL, rab-ConfigurationIndicator [13] NULL OPTIONAL, iuSelectedCodec [14] Codec OPTIONAL, alternativeChannelType [15] RadioResourceInformation OPTIONAL, tracePropagationList [17] TracePropagationList OPTIONAL } AllowedGSM-Algorithms ::= OCTET STRING (SIZE (1)) -- internal structure is coded as Algorithm identifier octet from -- Permitted Algorithms defined in 3GPP TS 48.008 -- A node shall mark all GSM algorithms that are allowed in MSC-B AllowedUMTS-Algorithms ::= SEQUENCE { integrityProtectionAlgorithms OPTIONAL, encryptionAlgorithms extensionContainer ...} [0] [1] [2] PermittedIntegrityProtectionAlgorithms PermittedEncryptionAlgorithms OPTIONAL, ExtensionContainer OPTIONAL,

PermittedIntegrityProtectionAlgorithms ::= OCTET STRING (SIZE (1..maxPermittedIntegrityProtectionAlgorithmsLength)) -- Octets contain a complete PermittedIntegrityProtectionAlgorithms data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413. -- Padding bits are included, if needed, in the least significant bits of the -- last octet of the octet string. maxPermittedIntegrityProtectionAlgorithmsLength INTEGER ::= 9 PermittedEncryptionAlgorithms ::= OCTET STRING (SIZE (1..maxPermittedEncryptionAlgorithmsLength)) -- Octets contain a complete PermittedEncryptionAlgorithms data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413 -- Padding bits are included, if needed, in the least significant bits of the -- last octet of the octet string. maxPermittedEncryptionAlgorithmsLength INTEGER ::= 9 KeyStatus ::= ENUMERATED { old (0), new (1), ...} -- exception handling: -- received values in range 2-31 shall be treated as "old" -- received values greater than 31 shall be treated as "new"

1354

3GPP

1355 Release 7 1356 1357

561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635

340

3GPP TS 29.002 V7.5.0 (2006-09)

PrepareHO-Arg ::= [3] SEQUENCE { targetCellId ho-NumberNotRequired targetRNCId an-APDU multipleBearerRequested imsi integrityProtectionInfo encryptionInfo radioResourceInformation allowedGSM-Algorithms allowedUMTS-Algorithms radioResourceList extensionContainer ... , rab-Id bssmap-ServiceHandover ranap-ServiceHandover bssmap-ServiceHandoverList asciCallReference geran-classmark iuCurrentlyUsedCodec iuSupportedCodecsList rab-ConfigurationIndicator uesbi-Iu imeisv alternativeChannelType tracePropagationList

[0] GlobalCellId OPTIONAL, NULL OPTIONAL, [1] RNCId OPTIONAL, [2] AccessNetworkSignalInfo OPTIONAL, [3] NULL OPTIONAL, [4] IMSI OPTIONAL, [5] IntegrityProtectionInformation OPTIONAL, [6] EncryptionInformation OPTIONAL, [7] RadioResourceInformation OPTIONAL, [9] AllowedGSM-Algorithms OPTIONAL, [10] AllowedUMTS-Algorithms OPTIONAL, [11] RadioResourceList OPTIONAL, [8] ExtensionContainer OPTIONAL, [12] [13] [14] [15] [20] [16] [17] [18] [19] [21] [22] [23] [25] RAB-Id BSSMAP-ServiceHandover RANAP-ServiceHandover BSSMAP-ServiceHandoverList ASCI-CallReference GERAN-Classmark Codec SupportedCodecsList NULL UESBI-Iu IMEI RadioResourceInformation TracePropagationList OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

BSSMAP-ServiceHandoverList ::= SEQUENCE SIZE (1.. maxNumOfServiceHandovers) OF BSSMAP-ServiceHandoverInfo BSSMAP-ServiceHandoverInfo ::= SEQUENCE { bssmap-ServiceHandover BSSMAP-ServiceHandover, rab-Id RAB-Id, -- RAB Identity is needed to relate the service handovers with the radio access bearers. ...} maxNumOfServiceHandovers INTEGER ::= 7

BSSMAP-ServiceHandover ::= OCTET STRING (SIZE (1)) -- Octets are coded according the Service Handover information element in -- 3GPP TS 48.008. RANAP-ServiceHandover ::= OCTET STRING (SIZE (1)) -- Octet contains a complete Service-Handover data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413 -- Padding bits are included in the least significant bits. RadioResourceList ::= SEQUENCE SIZE (1.. maxNumOfRadioResources) OF RadioResource RadioResource ::= SEQUENCE { radioResourceInformation RadioResourceInformation, rab-Id RAB-Id, -- RAB Identity is needed to relate the radio resources with the radio access bearers. ...} maxNumOfRadioResources INTEGER ::= 7 [0] ISDN-AddressString OPTIONAL, [1] RelocationNumberList OPTIONAL, [2] AccessNetworkSignalInfo OPTIONAL, [3] MulticallBearerInfo OPTIONAL, NULL OPTIONAL, [5] SelectedUMTS-Algorithms OPTIONAL, [6] ChosenRadioResourceInformation OPTIONAL, [4] ExtensionContainer OPTIONAL, [7] Codec [8] CodecList OPTIONAL, OPTIONAL }

PrepareHO-Res ::= [3] SEQUENCE { handoverNumber relocationNumberList an-APDU multicallBearerInfo multipleBearerNotSupported selectedUMTS-Algorithms chosenRadioResourceInformation extensionContainer ..., iuSelectedCodec iuAvailableCodecsList

1358

3GPP

1359 Release 7 1360 1361

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 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710

341

3GPP TS 29.002 V7.5.0 (2006-09)

SelectedUMTS-Algorithms ::= SEQUENCE { integrityProtectionAlgorithm encryptionAlgorithm extensionContainer ...}

[0] [1] [2]

ChosenIntegrityProtectionAlgorithm OPTIONAL, ChosenEncryptionAlgorithm OPTIONAL, ExtensionContainer OPTIONAL,

ChosenIntegrityProtectionAlgorithm ::= OCTET STRING (SIZE (1)) -- Octet contains a complete IntegrityProtectionAlgorithm data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413 -- Padding bits are included in the least significant bits. ChosenEncryptionAlgorithm ::= OCTET STRING (SIZE (1)) -- Octet contains a complete EncryptionAlgorithm data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413 -- Padding bits are included in the least significant bits. ChosenRadioResourceInformation ::= SEQUENCE { chosenChannelInfo [0] ChosenChannelInfo chosenSpeechVersion [1] ChosenSpeechVersion ...} OPTIONAL, OPTIONAL,

ChosenChannelInfo ::= OCTET STRING (SIZE (1)) -- Octets are coded according the Chosen Channel information element in 3GPP TS 48.008 ChosenSpeechVersion ::= OCTET STRING (SIZE (1)) -- Octets are coded according the Speech Version (chosen) information element in 3GPP TS -- 48.008 PrepareSubsequentHO-Arg ::= [3] SEQUENCE { targetCellId [0] targetMSC-Number [1] targetRNCId [2] an-APDU [3] selectedRab-Id [4] extensionContainer [5] ..., geran-classmark [6] rab-ConfigurationIndicator [7] GlobalCellId ISDN-AddressString, RNCId AccessNetworkSignalInfo RAB-Id ExtensionContainer GERAN-Classmark NULL OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

PrepareSubsequentHO-Res ::= [3] SEQUENCE { an-APDU AccessNetworkSignalInfo, extensionContainer [0] ExtensionContainer ...}

OPTIONAL,

ProcessAccessSignalling-Arg ::= [3] SEQUENCE { an-APDU AccessNetworkSignalInfo, selectedUMTS-Algorithms [1] SelectedUMTS-Algorithms OPTIONAL, selectedGSM-Algorithm [2] SelectedGSM-Algorithm OPTIONAL, chosenRadioResourceInformation [3] ChosenRadioResourceInformation OPTIONAL, selectedRab-Id [4] RAB-Id OPTIONAL, extensionContainer [0] ExtensionContainer OPTIONAL, ..., iUSelectedCodec [5] Codec OPTIONAL, iuAvailableCodecsList [6] CodecList OPTIONAL } SupportedCodecsList ::= SEQUENCE { utranCodecList geranCodecList extensionContainer ...} CodecList ::= SEQUENCE { codec1 codec2 codec3 codec4 codec5 codec6 codec7 codec8 extensionContainer ...} -- Codecs are sent in priority order [0] CodecList [1] CodecList [2] ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL,

[1] [2] [3] [4] [5] [6] [7] [8] [9]

Codec, Codec Codec Codec Codec Codec Codec Codec ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

where codec1 has highest priority

711

1362

3GPP

1363 Release 7 1364 1365

712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787

342

3GPP TS 29.002 V7.5.0 (2006-09)

Codec ::= OCTET STRING (SIZE (1..4)) -- The internal structure is defined as follows: -- octet 1 Coded as Codec Identification code in 3GPP TS 26.103 -- octets 2,3,4 Parameters for the Codec as defined in 3GPP TS -26.103, if available, length depending on the codec GERAN-Classmark ::= OCTET STRING (SIZE (2..87)) -- Octets are coded according the GERAN Classmark information element in 3GPP TS 48.008 SelectedGSM-Algorithm ::= OCTET STRING (SIZE (1)) -- internal structure is coded as Algorithm identifier octet from Chosen Encryption -- Algorithm defined in 3GPP TS 48.008 -- A node shall mark only the selected GSM algorithm SendEndSignal-Arg ::= [3] SEQUENCE { an-APDU extensionContainer ...} SendEndSignal-Res ::= SEQUENCE { extensionContainer ...} AccessNetworkSignalInfo, [0] ExtensionContainer

OPTIONAL,

[0]

ExtensionContainer

OPTIONAL,

RNCId ::= OCTET STRING (SIZE (7)) -- The internal structure is defined as follows: -- octet 1 bits 4321 Mobile Country Code 1st digit -bits 8765 Mobile Country Code 2nd digit -- octet 2 bits 4321 Mobile Country Code 3rd digit -bits 8765 Mobile Network Code 3rd digit -or filler (1111) for 2 digit MNCs -- octet 3 bits 4321 Mobile Network Code 1st digit -bits 8765 Mobile Network Code 2nd digit -- octets 4 and 5 Location Area Code according to 3GPP TS 24.008 -- octets 6 and 7 RNC Id value according to 3GPP TS 25.413 RelocationNumberList ::= SEQUENCE SIZE (1..maxNumOfRelocationNumber) OF RelocationNumber MulticallBearerInfo ::= INTEGER (1..maxNumOfRelocationNumber) RelocationNumber ::= SEQUENCE { handoverNumber ISDN-AddressString, rab-Id RAB-Id, -- RAB Identity is needed to relate the calls with the radio access bearers. ...} RAB-Id ::= INTEGER (1..maxNrOfRABs) maxNrOfRABs INTEGER ::= 255 maxNumOfRelocationNumber INTEGER ::= 7

RadioResourceInformation ::= OCTET STRING (SIZE (3..13)) -- Octets are coded according the Channel Type information element in 3GPP TS 48.008 IntegrityProtectionInformation ::= OCTET STRING (SIZE (18..maxNumOfIntegrityInfo)) -- Octets contain a complete IntegrityProtectionInformation data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413 -- Padding bits are included, if needed, in the least significant bits of the -- last octet of the octet string. maxNumOfIntegrityInfo INTEGER ::= 100 EncryptionInformation ::= OCTET STRING (SIZE (18..maxNumOfEncryptionInfo)) -- Octets contain a complete EncryptionInformation data type -- as defined in 3GPP TS 25.413, encoded according to the encoding scheme -- mandated by 3GPP TS 25.413 -- Padding bits are included, if needed, in the least significant bits of the -- last octet of the octet string. maxNumOfEncryptionInfo INTEGER ::= 100 -- authentication management types

1366

3GPP

1367 Release 7 1368 1369

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

343

3GPP TS 29.002 V7.5.0 (2006-09)

SendAuthenticationInfoArg ::= SEQUENCE { imsi numberOfRequestedVectors segmentationProhibited immediateResponsePreferred re-synchronisationInfo extensionContainer ..., requestingNodeType requestingPLMN-Id

[0] IMSI, NumberOfRequestedVectors, NULL [1] NULL Re-synchronisationInfo [2] ExtensionContainer [3] RequestingNodeType [4] PLMN-Id

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

NumberOfRequestedVectors ::= INTEGER (1..5) Re-synchronisationInfo ::= SEQUENCE { rand auts ...} RAND, AUTS,

SendAuthenticationInfoRes ::= [3] SEQUENCE { authenticationSetList AuthenticationSetList extensionContainer ExtensionContainer ...}

OPTIONAL, OPTIONAL,

RequestingNodeType ::= ENUMERATED { vlr (0), sgsn (1), ..., s-cscf (2), bsf (3), gan-aaa-server (4), wlan-aaa-server (5) } -- the values 2, 3, 4 and 5 shall not be used on the MAP-D or Gr interfaces -- exception handling: -- received values in the range (6-15) shall be treated as "vlr" -- received values greater than 15 shall be treated as "sgsn" -- equipment management types CheckIMEI-Arg ::= SEQUENCE { imei requestedEquipmentInfo extensionContainer ...} CheckIMEI-Res ::= SEQUENCE { equipmentStatus bmuef extensionContainer ...} IMEI, RequestedEquipmentInfo, ExtensionContainer

OPTIONAL,

EquipmentStatus UESBI-Iu [0] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

RequestedEquipmentInfo::= BIT STRING { equipmentStatus (0), bmuef (1)} (SIZE (2..8)) -- exception handling: reception of unknown bit assignments in the -- RequestedEquipmentInfo data type shall be discarded by the receiver UESBI-Iu ::= SEQUENCE { uesbi-IuA [0] UESBI-IuA uesbi-IuB [1] UESBI-IuB ...} UESBI-IuA -- See 3GPP TS 25.413 UESBI-IuB -- See 3GPP TS 25.413 EquipmentStatus ::= ENUMERATED { whiteListed (0), blackListed (1), greyListed (2)} -- subscriber management types ::= BIT STRING (SIZE(1..128)) ::= BIT STRING (SIZE(1..128)) OPTIONAL, OPTIONAL,

1370

3GPP

1371 Release 7 1372 1373

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

344

3GPP TS 29.002 V7.5.0 (2006-09)

InsertSubscriberDataArg ::= SEQUENCE { imsi [0] IMSI COMPONENTS OF SubscriberData, extensionContainer [14] ExtensionContainer ... , naea-PreferredCI [15] NAEA-PreferredCI -- naea-PreferredCI is included at the discretion of the HLR operator. gprsSubscriptionData [16] GPRSSubscriptionData roamingRestrictedInSgsnDueToUnsupportedFeature [23] networkAccessMode lsaInformation lmu-Indicator lcsInformation istAlertTimer superChargerSupportedInHLR mc-SS-Info cs-AllocationRetentionPriority sgsn-CAMEL-SubscriptionInfo chargingCharacteristics accessRestrictionData [24] [25] [21] [22] [26] [27] [28] [29] [17] [18] [19]

OPTIONAL, OPTIONAL, OPTIONAL,

OPTIONAL, NULL OPTIONAL, NetworkAccessMode OPTIONAL, LSAInformation OPTIONAL, NULL OPTIONAL, LCSInformation OPTIONAL, IST-AlertTimerValue OPTIONAL, AgeIndicator OPTIONAL, MC-SS-Info OPTIONAL, CS-AllocationRetentionPriority OPTIONAL, SGSN-CAMEL-SubscriptionInfo OPTIONAL, ChargingCharacteristics OPTIONAL, AccessRestrictionData OPTIONAL

-- If the Network Access Mode parameter is sent, it shall be present only in -- the first sequence if seqmentation is used

AccessRestrictionData ::= BIT STRING { utranNotAllowed (0), geranNotAllowed (1) } (SIZE (2..8)) -- exception handling: -- bits 2 to 7 shall be ignored if received and not understood CS-AllocationRetentionPriority ::= OCTET STRING (SIZE (1)) -- This data type encodes each priority level defined in TS 23.107 as the binary value -- of the priority level. IST-AlertTimerValue ::= INTEGER (15..255) LCSInformation ::= SEQUENCE { gmlc-List [0] GMLC-List OPTIONAL, lcs-PrivacyExceptionList [1] LCS-PrivacyExceptionList OPTIONAL, molr-List [2] MOLR-List OPTIONAL, ..., add-lcs-PrivacyExceptionList [3] LCS-PrivacyExceptionList OPTIONAL } -- add-lcs-PrivacyExceptionList may be sent only if lcs-PrivacyExceptionList is -- present and contains four instances of LCS-PrivacyClass. If the mentioned condition -- is not satisfied the receiving node shall discard add-lcs-PrivacyExceptionList. -- If an LCS-PrivacyClass is received both in lcs-PrivacyExceptionList and in -- add-lcs-PrivacyExceptionList with the same SS-Code, then the error unexpected -- data value shall be returned. GMLC-List ::= SEQUENCE SIZE (1..maxNumOfGMLC) OF ISDN-AddressString -- if segmentation is used, the complete GMLC-List shall be sent in one segment maxNumOfGMLC INTEGER ::= 5 (0), (1), (2), NetworkAccessMode

NetworkAccessMode ::= ENUMERATED { bothMSCAndSGSN onlyMSC onlySGSN ...} -- if unknown values are received in -- they shall be discarded.

GPRSDataList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF PDP-Context maxNumOfPDP-Contexts INTEGER ::= 50

1374

3GPP

1375 Release 7 1376 1377

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

345

3GPP TS 29.002 V7.5.0 (2006-09)

PDP-Context ::= SEQUENCE { pdp-ContextId ContextId, pdp-Type [16] PDP-Type, pdp-Address [17] PDP-Address OPTIONAL, qos-Subscribed [18] QoS-Subscribed, vplmnAddressAllowed [19] NULL OPTIONAL, apn [20] APN, extensionContainer [21] ExtensionContainer OPTIONAL, ... , ext-QoS-Subscribed [0] Ext-QoS-Subscribed OPTIONAL, pdp-ChargingCharacteristics [1] ChargingCharacteristics OPTIONAL, ext2-QoS-Subscribed [2] Ext2-QoS-Subscribed OPTIONAL -- ext2-QoS-Subscribed may be present only if ext-QoS-Subscribed is present. } ContextId ::= INTEGER (1..maxNumOfPDP-Contexts) GPRSSubscriptionData ::= SEQUENCE { completeDataListIncluded NULL OPTIONAL, -- If segmentation is used, completeDataListIncluded may only be present in the -- first segment of GPRSSubscriptionData. gprsDataList [1] GPRSDataList, extensionContainer [2] ExtensionContainer OPTIONAL, ... } SGSN-CAMEL-SubscriptionInfo ::= SEQUENCE gprs-CSI mo-sms-CSI extensionContainer ..., mt-sms-CSI mt-smsCAMELTDP-CriteriaList mg-csi } { [0] [1] [2] [3] [4] [5] GPRS-CSI SMS-CSI ExtensionContainer SMS-CSI MT-smsCAMELTDP-CriteriaList MG-CSI OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

GPRS-CSI ::= SEQUENCE { gprs-CamelTDPDataList [0] GPRS-CamelTDPDataList OPTIONAL, camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL, extensionContainer [2] ExtensionContainer OPTIONAL, notificationToCSE [3] NULL OPTIONAL, csi-Active [4] NULL OPTIONAL, ...} -notificationToCSE and csi-Active shall not be present when GPRS-CSI is sent to SGSN. -They may only be included in ATSI/ATM ack/NSDC message. -GPRS-CamelTDPData and camelCapabilityHandling shall be present in -the GPRS-CSI sequence. -If GPRS-CSI is segmented, gprs-CamelTDPDataList and camelCapabilityHandling shall be -present in the first segment GPRS-CamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF GPRS-CamelTDPData -GPRS-CamelTDPDataList shall not contain more than one instance of -GPRS-CamelTDPData containing the same value for gprs-TriggerDetectionPoint. GPRS-CamelTDPData ::= SEQUENCE { gprs-TriggerDetectionPoint serviceKey gsmSCF-Address defaultSessionHandling extensionContainer ... } [0] [1] [2] [3] [4] GPRS-TriggerDetectionPoint, ServiceKey, ISDN-AddressString, DefaultGPRS-Handling, ExtensionContainer

OPTIONAL,

DefaultGPRS-Handling ::= ENUMERATED { continueTransaction (0) , releaseTransaction (1) , ...} -- exception handling: -- reception of values in range 2-31 shall be treated as "continueTransaction" -- reception of values greater than 31 shall be treated as "releaseTransaction"

1378

3GPP

1379 Release 7 1380 1381

1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081

346

3GPP TS 29.002 V7.5.0 (2006-09)

GPRS-TriggerDetectionPoint ::= ENUMERATED { attach (1), attachChangeOfPosition (2), pdp-ContextEstablishment (11), pdp-ContextEstablishmentAcknowledgement (12), pdp-ContextChangeOfPosition (14), ... } -- exception handling: -- For GPRS-CamelTDPData sequences containing this parameter with any -- other value than the ones listed the receiver shall ignore the whole -- GPRS-CamelTDPDatasequence. APN ::= OCTET STRING (SIZE (2..63)) -- Octets are coded according to TS 3GPP TS 23.003 [17] PDP-Type ::= OCTET STRING (SIZE (2)) -- Octets are coded according to TS 3GPP TS 29.060 [105] PDP-Address ::= OCTET STRING (SIZE (1..16)) -- Octets are coded according to TS 3GPP TS 29.060 [105] -- The possible size values -- 1-7 octets X.25 address -- 4 octets IPv4 address -- 16 octets Ipv6 address are: type type type

QoS-Subscribed ::= OCTET STRING (SIZE (3)) -- Octets are coded according to TS 3GPP TS 24.008 [35] Quality of Service Octets -- 3-5. Ext-QoS-Subscribed ::= OCTET STRING (SIZE (1..9)) -- OCTET 1: -- Allocation/Retention Priority (This octet encodes each priority level defined in -23.107 as the binary value of the priority level, declaration in 29.060) -- Octets 2-9 are coded according to 3GPP TS 24.008 [35] Quality of Service Octets -- 6-13. Ext2-QoS-Subscribed ::= OCTET STRING (SIZE (1..3)) -- Octets 1-3 are coded according to 3GPP TS 24.008 [35] Quality of Service Octets 14-16. -- If Quality of Service information is structured with 14 octet length, then -- Octet 1 is coded according to 3GPP TS 24.008 [35] Quality of Service Octet 14. ChargingCharacteristics ::= OCTET STRING (SIZE (2)) -- Octets are coded according to 3GPP TS 32.215. LSAOnlyAccessIndicator ::= ENUMERATED { accessOutsideLSAsAllowed (0), accessOutsideLSAsRestricted (1)} LSADataList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF LSAData maxNumOfLSAs INTEGER ::= 20 [0] [1] [2] [3] LSAIdentity, LSAAttributes, NULL ExtensionContainer

LSAData ::= SEQUENCE { lsaIdentity lsaAttributes lsaActiveModeIndicator extensionContainer ...} LSAInformation ::= SEQUENCE { completeDataListIncluded

OPTIONAL, OPTIONAL,

NULL

OPTIONAL,

-- If segmentation is used, completeDataListIncluded may only be present in the -- first segment. lsaOnlyAccessIndicator [1] LSAOnlyAccessIndicator OPTIONAL, lsaDataList [2] LSADataList OPTIONAL, extensionContainer [3] ExtensionContainer OPTIONAL, ...} LSAIdentity ::= OCTET STRING (SIZE (3)) -- Octets are coded according to TS 3GPP TS 23.003 [17] LSAAttributes ::= OCTET STRING (SIZE (1)) -- Octets are coded according to TS 3GPP TS 48.008 [49]

1382

3GPP

1383 Release 7 1384 1385

1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 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 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159

347

3GPP TS 29.002 V7.5.0 (2006-09)

SubscriberData ::= SEQUENCE { msisdn [1] ISDN-AddressString category [2] Category subscriberStatus [3] SubscriberStatus bearerServiceList [4] BearerServiceList -- The exception handling for reception of unsupported / not allocated -- bearerServiceCodes is defined in section 8.8.1 teleserviceList [6] TeleserviceList -- The exception handling for reception of unsupported / not allocated -- teleserviceCodes is defined in section 8.8.1 provisionedSS [7] Ext-SS-InfoList odb-Data [8] ODB-Data roamingRestrictionDueToUnsupportedFeature [9] NULL regionalSubscriptionData [10] ZoneCodeList vbsSubscriptionData [11] VBSDataList vgcsSubscriptionData [12] VGCSDataList vlrCamelSubscriptionInfo [13] VlrCamelSubscriptionInfo } Category ::= OCTET STRING (SIZE (1)) -- The internal structure is defined in ITU-T Rec Q.763. SubscriberStatus ::= ENUMERATED { serviceGranted (0), operatorDeterminedBarring (1)} BearerServiceList ::= SEQUENCE SIZE (1..maxNumOfBearerServices) OF Ext-BearerServiceCode maxNumOfBearerServices INTEGER ::= 50

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

TeleserviceList ::= SEQUENCE SIZE (1..maxNumOfTeleservices) OF Ext-TeleserviceCode maxNumOfTeleservices INTEGER ::= 20 ODB-GeneralData, ODB-HPLMN-Data ExtensionContainer

ODB-Data ::= SEQUENCE { odb-GeneralData odb-HPLMN-Data extensionContainer ...}

OPTIONAL, OPTIONAL,

ODB-GeneralData ::= BIT STRING { allOG-CallsBarred (0), internationalOGCallsBarred (1), internationalOGCallsNotToHPLMN-CountryBarred (2), interzonalOGCallsBarred (6), interzonalOGCallsNotToHPLMN-CountryBarred (7), interzonalOGCallsAndInternationalOGCallsNotToHPLMN-CountryBarred (8), premiumRateInformationOGCallsBarred (3), premiumRateEntertainementOGCallsBarred (4), ss-AccessBarred (5), allECT-Barred (9), chargeableECT-Barred (10), internationalECT-Barred (11), interzonalECT-Barred (12), doublyChargeableECT-Barred (13), multipleECT-Barred (14), allPacketOrientedServicesBarred (15), roamerAccessToHPLMN-AP-Barred (16), roamerAccessToVPLMN-AP-Barred (17), roamingOutsidePLMNOG-CallsBarred (18), allIC-CallsBarred (19), roamingOutsidePLMNIC-CallsBarred (20), roamingOutsidePLMNICountryIC-CallsBarred (21), roamingOutsidePLMN-Barred (22), roamingOutsidePLMN-CountryBarred (23), registrationAllCF-Barred (24), registrationCFNotToHPLMN-Barred (25), registrationInterzonalCF-Barred (26), registrationInterzonalCFNotToHPLMN-Barred (27), registrationInternationalCF-Barred (28)} (SIZE (15..32)) -- exception handling: reception of unknown bit assignments in the -- ODB-GeneralData type shall be treated like unsupported ODB-GeneralData -- When the ODB-GeneralData type is removed from the HLR for a given subscriber, -- in NoteSubscriberDataModified operation sent toward the gsmSCF -- all bits shall be set to O.

1386

3GPP

1387 Release 7 1388 1389

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 1201 1202 1203 1204 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 1230 1231 1232

348

3GPP TS 29.002 V7.5.0 (2006-09)

ODB-HPLMN-Data ::= BIT STRING { plmn-SpecificBarringType1 (0), plmn-SpecificBarringType2 (1), plmn-SpecificBarringType3 (2), plmn-SpecificBarringType4 (3)} (SIZE (4..32)) -- exception handling: reception of unknown bit assignments in the -- ODB-HPLMN-Data type shall be treated like unsupported ODB-HPLMN-Data -- When the ODB-HPLMN-Data type is removed from the HLR for a given subscriber, -- in NoteSubscriberDataModified operation sent toward the gsmSCF -- all bits shall be set to O. Ext-SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF Ext-SS-Info Ext-SS-Info ::= CHOICE { forwardingInfo callBarringInfo cug-Info ss-Data emlpp-Info Ext-ForwInfo ::= SEQUENCE { ss-Code forwardingFeatureList extensionContainer ...} [0] [1] [2] [3] [4] Ext-ForwInfo, Ext-CallBarInfo, CUG-Info, Ext-SS-Data, EMLPP-Info}

SS-Code, Ext-ForwFeatureList, [0] ExtensionContainer

OPTIONAL,

Ext-ForwFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF Ext-ForwFeature Ext-ForwFeature ::= SEQUENCE { basicService Ext-BasicServiceCode OPTIONAL, ss-Status [4] Ext-SS-Status, forwardedToNumber [5] ISDN-AddressString OPTIONAL, -- When this data type is sent from an HLR which supports CAMEL Phase 2 -- to a VLR that supports CAMEL Phase 2 the VLR shall not check the -- format of the number forwardedToSubaddress [8] ISDN-SubaddressString OPTIONAL, forwardingOptions [6] Ext-ForwOptions OPTIONAL, noReplyConditionTime [7] Ext-NoRepCondTime OPTIONAL, extensionContainer [9] ExtensionContainer OPTIONAL, ..., longForwardedToNumber [10] FTN-AddressString OPTIONAL } Ext-ForwOptions ::= OCTET STRING (SIZE (1..5)) -- OCTET 1: ---------------bit 8: notification to forwarding party 0 no notification 1 notification bit 7: redirecting presentation 0 no presentation 1 presentation bit 6: notification to calling party 0 no notification 1 notification bit 5: 0 (unused) bits 00 01 10 11 43: forwarding reason ms not reachable ms busy no reply unconditional

-- bits 21: 00 (unused) -- OCTETS 2-5: reserved for future use. They shall be discarded if -- received and not understood.

1390

3GPP

1391 Release 7 1392 1393

1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298

349

3GPP TS 29.002 V7.5.0 (2006-09)

Ext-NoRepCondTime ::= INTEGER (1..100) -- Only values 5-30 are used. -- Values in the ranges 1-4 and 31-100 are reserved for future use -- If received: -values 1-4 shall be mapped on to value 5 -values 31-100 shall be mapped on to value 30 Ext-CallBarInfo ::= SEQUENCE { ss-Code callBarringFeatureList extensionContainer ...} SS-Code, Ext-CallBarFeatureList, ExtensionContainer

OPTIONAL,

Ext-CallBarFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF Ext-CallBarringFeature Ext-CallBarringFeature ::= SEQUENCE { basicService ss-Status extensionContainer ...} CUG-Info ::= SEQUENCE { cug-SubscriptionList cug-FeatureList extensionContainer ...} Ext-BasicServiceCode [4] Ext-SS-Status, ExtensionContainer OPTIONAL, OPTIONAL,

CUG-SubscriptionList, CUG-FeatureList [0] ExtensionContainer

OPTIONAL, OPTIONAL,

CUG-SubscriptionList ::= SEQUENCE SIZE (0..maxNumOfCUG) OF CUG-Subscription CUG-Subscription ::= SEQUENCE { cug-Index CUG-Index, cug-Interlock intraCUG-Options basicServiceGroupList extensionContainer ...}

CUG-Interlock, IntraCUG-Options, Ext-BasicServiceGroupList [0] ExtensionContainer

OPTIONAL, OPTIONAL,

CUG-Index ::= INTEGER (0..32767) -- The internal structure is defined in ETS 300 138. CUG-Interlock ::= OCTET STRING (SIZE (4)) IntraCUG-Options ::= ENUMERATED { noCUG-Restrictions (0), cugIC-CallBarred (1), cugOG-CallBarred (2)} maxNumOfCUG INTEGER ::= 10

CUG-FeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF CUG-Feature Ext-BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF Ext-BasicServiceCode maxNumOfExt-BasicServiceGroups CUG-Feature ::= SEQUENCE { basicService preferentialCUG-Indicator interCUG-Restrictions extensionContainer ...} INTEGER ::= 32 Ext-BasicServiceCode CUG-Index OPTIONAL, InterCUG-Restrictions, ExtensionContainer OPTIONAL, OPTIONAL,

1394

3GPP

1395 Release 7 1396 1397

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 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374

350

3GPP TS 29.002 V7.5.0 (2006-09)

InterCUG-Restrictions ::= OCTET STRING (SIZE (1)) -- bits 876543: 000000 (unused) -- Exception handling: -- bits 876543 shall be ignored if received and not understood -- bits 21 -00 CUG -01 CUG -10 CUG -11 CUG only with with with facilities outgoing access incoming access both outgoing and incoming access SS-Code, SS-SubscriptionOption Ext-BasicServiceGroupList [5] ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL,

Ext-SS-Data ::= SEQUENCE { ss-Code ss-Status [4] Ext-SS-Status, ss-SubscriptionOption basicServiceGroupList extensionContainer ...}

LCS-PrivacyExceptionList ::= SEQUENCE SIZE (1..maxNumOfPrivacyClass) OF LCS-PrivacyClass maxNumOfPrivacyClass INTEGER ::= 4

LCS-PrivacyClass ::= SEQUENCE { ss-Code SS-Code, ss-Status Ext-SS-Status, notificationToMSUser [0] NotificationToMSUser OPTIONAL, -- notificationToMSUser may be sent only for SS-codes callSessionRelated -- and callSessionUnrelated. If not received for SS-codes callSessionRelated -- and callSessionUnrelated, -- the default values according to 3GPP TS 23.271 shall be assumed. externalClientList [1] ExternalClientList OPTIONAL, -- externalClientList may be sent only for SS-code callSessionUnrelated to a -- visited node that does not support LCS Release 4 or later versions. -- externalClientList may be sent only for SS-codes callSessionUnrelated and -- callSessionRelated to a visited node that supports LCS Release 4 or later versions. plmnClientList [2] PLMNClientList OPTIONAL, -- plmnClientList may be sent only for SS-code plmnoperator. extensionContainer [3] ExtensionContainer OPTIONAL, ..., ext-externalClientList [4] Ext-ExternalClientList OPTIONAL, -- Ext-externalClientList may be sent only if the visited node supports LCS Release 4 or -- later versions, the user did specify more than 5 clients, and White Book SCCP is used. serviceTypeList [5] ServiceTypeList OPTIONAL -- serviceTypeList may be sent only for SS-code serviceType and if the visited node -- supports LCS Release 5 or later versions. --- if segmentation is used, the complete LCS-PrivacyClass shall be sent in one segment } ExternalClientList ::= SEQUENCE SIZE (0..maxNumOfExternalClient) OF ExternalClient maxNumOfExternalClient INTEGER ::= 5

PLMNClientList ::= SEQUENCE SIZE (1..maxNumOfPLMNClient) OF LCSClientInternalID maxNumOfPLMNClient INTEGER ::= 5

Ext-ExternalClientList ::= SEQUENCE SIZE (1..maxNumOfExt-ExternalClient) OF ExternalClient maxNumOfExt-ExternalClient INTEGER ::= 35

ExternalClient ::= SEQUENCE { clientIdentity LCSClientExternalID, gmlc-Restriction [0] GMLC-Restriction OPTIONAL, notificationToMSUser [1] NotificationToMSUser OPTIONAL, -- If notificationToMSUser is not received, the default value according to -- 3GPP TS 23.271 shall be assumed. extensionContainer [2] ExtensionContainer OPTIONAL, ... }

1398

3GPP

1399 Release 7 1400 1401

1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451

351

3GPP TS 29.002 V7.5.0 (2006-09)

GMLC-Restriction ::= ENUMERATED { gmlc-List (0), home-Country (1) , ... } -- exception handling: -- At reception of any other value than the ones listed the receiver shall ignore -- GMLC-Restriction. NotificationToMSUser ::= ENUMERATED { notifyLocationAllowed (0), notifyAndVerify-LocationAllowedIfNoResponse (1), notifyAndVerify-LocationNotAllowedIfNoResponse(2), ..., locationNotAllowed (3) } -- exception handling: -- At reception of any other value than the ones listed the receiver shall ignore -- NotificationToMSUser. ServiceTypeList ::= SEQUENCE SIZE (1..maxNumOfServiceType) OF ServiceType maxNumOfServiceType INTEGER ::= 32

ServiceType ::= SEQUENCE { serviceTypeIdentity LCSServiceTypeID, gmlc-Restriction [0] GMLC-Restriction OPTIONAL, notificationToMSUser [1] NotificationToMSUser OPTIONAL, -- If notificationToMSUser is not received, the default value according to -- 3GPP TS 23.271 shall be assumed. extensionContainer [2] ExtensionContainer OPTIONAL, ... } MOLR-List ::= SEQUENCE SIZE (1..maxNumOfMOLR-Class) OF MOLR-Class maxNumOfMOLR-Class INTEGER ::= 3 SS-Code, Ext-SS-Status, [0] ExtensionContainer

MOLR-Class ::= SEQUENCE { ss-Code ss-Status extensionContainer ...}

OPTIONAL,

ZoneCodeList ::= SEQUENCE SIZE (1..maxNumOfZoneCodes) OF ZoneCode ZoneCode ::= OCTET STRING (SIZE (2)) -- internal structure is defined in TS 3GPP TS 23.003 [17] maxNumOfZoneCodes INTEGER ::= 10 [1] [2] [3] [4] [5] [6] [7] TeleserviceList BearerServiceList SS-List ODB-GeneralData RegionalSubscriptionResponse SupportedCamelPhases ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

InsertSubscriberDataRes ::= SEQUENCE { teleserviceList bearerServiceList ss-List odb-GeneralData regionalSubscriptionResponse supportedCamelPhases extensionContainer ... , offeredCamel4CSIs

[8] OfferedCamel4CSIs

RegionalSubscriptionResponse ::= ENUMERATED { networkNode-AreaRestricted (0), tooManyZoneCodes (1), zoneCodesConflict (2), regionalSubscNotSupported (3)} DeleteSubscriberDataArg ::= SEQUENCE { imsi [0] IMSI, basicServiceList [1] BasicServiceList -- The exception handling for reception of unsupported/not allocated -- basicServiceCodes is defined in section 6.8.2 ss-List [2] SS-List roamingRestrictionDueToUnsupportedFeature [4] NULL regionalSubscriptionIdentifier [5] ZoneCode vbsGroupIndication [7] NULL

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

1402

3GPP

1403 Release 7 1404 1405

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

352

3GPP TS 29.002 V7.5.0 (2006-09)

vgcsGroupIndication [8] NULL OPTIONAL, camelSubscriptionInfoWithdraw [9] NULL OPTIONAL, extensionContainer [6] ExtensionContainer OPTIONAL, ..., gprsSubscriptionDataWithdraw [10] GPRSSubscriptionDataWithdraw roamingRestrictedInSgsnDueToUnsuppportedFeature [11] NULL lsaInformationWithdraw [12] LSAInformationWithdraw gmlc-ListWithdraw [13] NULL istInformationWithdraw [14] NULL specificCSI-Withdraw [15] SpecificCSI-Withdraw chargingCharacteristicsWithdraw [16] NULL

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

SpecificCSI-Withdraw ::= BIT STRING { o-csi (0), ss-csi (1), tif-csi (2), d-csi (3), vt-csi (4), mo-sms-csi (5), m-csi (6), gprs-csi (7), t-csi (8), mt-sms-csi (9), mg-csi (10), o-IM-CSI (11), d-IM-CSI (12), vt-IM-CSI (13) } (SIZE(8..32)) -- exception handling: -- bits 11 to 31 shall be ignored if received by a non-IP Multimedia Core Network entity. -- bits 0-10 and 14-31 shall be ignored if received by an IP Multimedia Core Network entity. -- bits 11-13 are only applicable in an IP Multimedia Core Network. -- Bit 8 and bits 11-13 are only applicable for the NoteSubscriberDataModified operation. GPRSSubscriptionDataWithdraw ::= CHOICE { allGPRSData NULL, contextIdList ContextIdList} ContextIdList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF ContextId LSAInformationWithdraw ::= CHOICE { allLSAData lsaIdentityList NULL, LSAIdentityList }

LSAIdentityList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF LSAIdentity BasicServiceList ::= SEQUENCE SIZE (1..maxNumOfBasicServices) OF Ext-BasicServiceCode maxNumOfBasicServices INTEGER ::= 70 [0] RegionalSubscriptionResponse ExtensionContainer OPTIONAL, OPTIONAL,

DeleteSubscriberDataRes ::= SEQUENCE { regionalSubscriptionResponse extensionContainer ...} VlrCamelSubscriptionInfo ::= SEQUENCE { o-CSI extensionContainer ..., ss-CSI o-BcsmCamelTDP-CriteriaList tif-CSI m-CSI mo-sms-CSI vt-CSI t-BCSM-CAMEL-TDP-CriteriaList d-CSI mt-sms-CSI mt-smsCAMELTDP-CriteriaList }

[0] O-CSI [1] ExtensionContainer [2] SS-CSI [4] O-BcsmCamelTDPCriteriaList [3] NULL [5] M-CSI [6] SMS-CSI [7] T-CSI [8] T-BCSM-CAMEL-TDP-CriteriaList [9] D-CSI [10] SMS-CSI [11] MT-smsCAMELTDP-CriteriaList

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

MT-smsCAMELTDP-CriteriaList ::= SEQUENCE SIZE (1.. maxNumOfCamelTDPData) OF MT-smsCAMELTDP-Criteria

1406

3GPP

1407 Release 7 1408 1409

1528 1529 1530 1531 1532 1533 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 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595

353

3GPP TS 29.002 V7.5.0 (2006-09)

MT-smsCAMELTDP-Criteria ::= SEQUENCE { sms-TriggerDetectionPoint tpdu-TypeCriterion ... }

SMS-TriggerDetectionPoint, [0] TPDU-TypeCriterion

OPTIONAL,

TPDU-TypeCriterion ::= SEQUENCE SIZE (1..maxNumOfTPDUTypes) OF MT-SMS-TPDU-Type maxNumOfTPDUTypes INTEGER ::= 5 MT-SMS-TPDU-Type ::= ENUMERATED { sms-DELIVER sms-SUBMIT-REPORT sms-STATUS-REPORT ... } ------(0), (1), (2),

exception handling: For TPDU-TypeCriterion sequences containing this parameter with any other value than the ones listed above the receiver shall ignore the whole TPDU-TypeCriterion sequence. In CAMEL phase 4, sms-SUBMIT-REPORT shall not be used and a received TPDU-TypeCriterion sequence containing sms-SUBMIT-REPORT shall be wholly ignored.

D-CSI ::= SEQUENCE { dp-AnalysedInfoCriteriaList [0] DP-AnalysedInfoCriteriaList OPTIONAL, camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL, extensionContainer [2] ExtensionContainer OPTIONAL, notificationToCSE [3] NULL OPTIONAL, csi-Active [4] NULL OPTIONAL, ...} -notificationToCSE and csi-Active shall not be present when D-CSI is sent to VLR/GMSC. -They may only be included in ATSI/ATM ack/NSDC message. -DP-AnalysedInfoCriteria and camelCapabilityHandling shall be present in -the D-CSI sequence. -If D-CSI is segmented, then the first segment shall contain dp-AnalysedInfoCriteriaList -and camelCapabilityHandling. Subsequent segments shall not contain -camelCapabilityHandling, but may contain dp-AnalysedInfoCriteriaList. DP-AnalysedInfoCriteriaList ::= SEQUENCE SIZE (1..maxNumOfDP-AnalysedInfoCriteria) OF DP-AnalysedInfoCriterium

maxNumOfDP-AnalysedInfoCriteria INTEGER ::= 10 DP-AnalysedInfoCriterium ::= SEQUENCE { dialledNumber serviceKey gsmSCF-Address defaultCallHandling extensionContainer ...} ISDN-AddressString, ServiceKey, ISDN-AddressString, DefaultCallHandling, ExtensionContainer

OPTIONAL,

SS-CSI ::= SEQUENCE { ss-CamelData SS-CamelData, extensionContainer ExtensionContainer OPTIONAL, ..., notificationToCSE [0] NULL OPTIONAL, csi-Active [1] NULL OPTIONAL -notificationToCSE and csi-Active shall not be present when SS-CSI is sent to VLR. -They may only be included in ATSI/ATM ack/NSDC message. } SS-CamelData ::= SEQUENCE { ss-EventList gsmSCF-Address extensionContainer ...} SS-EventList, ISDN-AddressString, [0] ExtensionContainer

OPTIONAL,

1410

3GPP

1411 Release 7 1412 1413

1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 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

354

3GPP TS 29.002 V7.5.0 (2006-09)

SS-EventList ::= SEQUENCE SIZE (1..maxNumOfCamelSSEvents) OF SS-Code -- Actions for the following SS-Code values are defined in CAMEL Phase 3: -- ect SS-Code ::= '00110001'B -- multiPTY SS-Code ::= '01010001'B -- cd SS-Code ::= '00100100'B -- ccbs SS-Code ::= '01000100'B -- all other SS codes shall be ignored -- When SS-CSI is sent to the VLR, it shall not contain a marking for ccbs. -- If the VLR receives SS-CSI containing a marking for ccbs, the VLR shall discard the -- ccbs marking in SS-CSI. maxNumOfCamelSSEvents INTEGER ::= 10 O-CSI ::= SEQUENCE { o-BcsmCamelTDPDataList O-BcsmCamelTDPDataList, extensionContainer ExtensionContainer OPTIONAL, ..., camelCapabilityHandling [0] CamelCapabilityHandling OPTIONAL, notificationToCSE [1] NULL OPTIONAL, csiActive [2] NULL OPTIONAL} -notificationtoCSE and csiActive shall not be present when O-CSI is sent to VLR/GMSC. -They may only be included in ATSI/ATM ack/NSDC message. -O-CSI shall not be segmented. O-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF O-BcsmCamelTDPData -- O-BcsmCamelTDPDataList shall not contain more than one instance of -- O-BcsmCamelTDPData containing the same value for o-BcsmTriggerDetectionPoint. -- For CAMEL Phase 2, this means that only one instance of O-BcsmCamelTDPData is allowed -- with o-BcsmTriggerDetectionPoint being equal to DP2. maxNumOfCamelTDPData INTEGER ::= 10 O-BcsmTriggerDetectionPoint, ServiceKey, [0] ISDN-AddressString, [1] DefaultCallHandling, [2] ExtensionContainer

O-BcsmCamelTDPData ::= SEQUENCE { o-BcsmTriggerDetectionPoint serviceKey gsmSCF-Address defaultCallHandling extensionContainer ... } ServiceKey ::= INTEGER (0..2147483647)

OPTIONAL,

O-BcsmTriggerDetectionPoint ::= ENUMERATED { collectedInfo (2), ..., routeSelectFailure (4) } -- exception handling: -- For O-BcsmCamelTDPData sequences containing this parameter with any -- other value than the ones listed the receiver shall ignore the whole -- O-BcsmCamelTDPDatasequence. -- For O-BcsmCamelTDP-Criteria sequences containing this parameter with any -- other value than the ones listed the receiver shall ignore the whole -- O-BcsmCamelTDP-Criteria sequence. O-BcsmCamelTDPCriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF O-BcsmCamelTDP-Criteria T-BCSM-CAMEL-TDP-CriteriaList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF T-BCSM-CAMEL-TDP-Criteria O-BcsmCamelTDP-Criteria ::= SEQUENCE { o-BcsmTriggerDetectionPoint destinationNumberCriteria basicServiceCriteria callTypeCriteria ..., o-CauseValueCriteria extensionContainer O-BcsmTriggerDetectionPoint, [0] DestinationNumberCriteria [1] BasicServiceCriteria [2] CallTypeCriteria [3] O-CauseValueCriteria [4] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

T-BCSM-CAMEL-TDP-Criteria ::= SEQUENCE { t-BCSM-TriggerDetectionPoint T-BcsmTriggerDetectionPoint, basicServiceCriteria [0] BasicServiceCriteria t-CauseValueCriteria [1] T-CauseValueCriteria ... }

OPTIONAL, OPTIONAL,

1414

3GPP

1415 Release 7 1416 1417

1673 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 1701 1702 1703 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 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744

355

3GPP TS 29.002 V7.5.0 (2006-09)

DestinationNumberCriteria ::= SEQUENCE { matchType [0] MatchType, destinationNumberList [1] DestinationNumberList OPTIONAL, destinationNumberLengthList [2] DestinationNumberLengthList OPTIONAL, -- one or both of destinationNumberList and destinationNumberLengthList -- shall be present ...} DestinationNumberList ::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumbers) OF ISDN-AddressString -- The receiving entity shall not check the format of a number in -- the dialled number list ::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumberLengths) OF INTEGER(1..maxNumOfISDN-AddressDigits)

DestinationNumberLengthList

BasicServiceCriteria ::= SEQUENCE SIZE(1..maxNumOfCamelBasicServiceCriteria) OF Ext-BasicServiceCode maxNumOfISDN-AddressDigits INTEGER ::= 15 INTEGER ::= 10 INTEGER ::= 3

maxNumOfCamelDestinationNumbers

maxNumOfCamelDestinationNumberLengths maxNumOfCamelBasicServiceCriteria CallTypeCriteria forwarded notForwarded

INTEGER ::= 5 (0), (1)} (0), (1)}

::= ENUMERATED {

MatchType ::= ENUMERATED { inhibiting enabling O-CauseValueCriteria CauseValue T-CauseValueCriteria CauseValue

::= SEQUENCE SIZE(1..maxNumOfCAMEL-O-CauseValueCriteria) OF ::= SEQUENCE SIZE(1..maxNumOfCAMEL-T-CauseValueCriteria) OF INTEGER ::= 5 INTEGER ::= 5

maxNumOfCAMEL-O-CauseValueCriteria maxNumOfCAMEL-T-CauseValueCriteria

CauseValue ::= OCTET STRING (SIZE(1)) -- Type extracted from Cause parameter in ITU-T Recommendation Q.763. -- For the use of cause value refer to ITU-T Recommendation Q.850. DefaultCallHandling ::= ENUMERATED { continueCall (0) , releaseCall (1) , ...} -- exception handling: -- reception of values in range 2-31 shall be treated as "continueCall" -- reception of values greater than 31 shall be treated as "releaseCall" CamelCapabilityHandling ::= INTEGER(1..16) -- value 1 = CAMEL phase 1, -- value 2 = CAMEL phase 2, -- value 3 = CAMEL Phase 3, -- value 4 = CAMEL phase 4: -- reception of values greater than 4 shall be treated as CAMEL phase 4. SupportedCamelPhases ::= BIT STRING { phase1 (0), phase2 (1), phase3 (2), phase4 (3)} (SIZE (1..16)) -- A node shall mark in the BIT STRING all CAMEL Phases it supports. -- Other values than listed above shall be discarded.

1418

3GPP

1419 Release 7 1420 1421

1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812

356

3GPP TS 29.002 V7.5.0 (2006-09)

OfferedCamel4CSIs ::= BIT STRING { o-csi (0), d-csi (1), vt-csi (2), t-csi (3), mt-sms-csi (4), mg-csi (5), psi-enhancements (6) } (SIZE (7..16)) -- A node supporting Camel phase 4 shall mark in the BIT STRING all Camel4 CSIs -- it offers. -- Other values than listed above shall be discarded. OfferedCamel4Functionalities ::= BIT STRING { initiateCallAttempt (0), splitLeg (1), moveLeg (2), disconnectLeg (3), entityReleased (4), dfc-WithArgument (5), playTone (6), dtmf-MidCall (7), chargingIndicator (8), alertingDP (9), locationAtAlerting (10), changeOfPositionDP (11), or-Interactions (12), warningToneEnhancements (13), cf-Enhancements (14), subscribedEnhancedDialledServices (15), servingNetworkEnhancedDialledServices (16), criteriaForChangeOfPositionDP (17), serviceChangeDP (18), collectInformation (19) } (SIZE (15..64)) -- A node supporting Camel phase 4 shall mark in the BIT STRING all CAMEL4 -- functionalities it offers. -- Other values than listed above shall be discarded. SMS-CSI ::= SEQUENCE { sms-CAMEL-TDP-DataList [0] SMS-CAMEL-TDP-DataList OPTIONAL, camelCapabilityHandling [1] CamelCapabilityHandling OPTIONAL, extensionContainer [2] ExtensionContainer OPTIONAL, notificationToCSE [3] NULL OPTIONAL, csi-Active [4] NULL OPTIONAL, ...} -notificationToCSE and csi-Active shall not be present -when MO-SMS-CSI or MT-SMS-CSI is sent to VLR or SGSN. -They may only be included in ATSI/ATM ack/NSDC message. -SMS-CAMEL-TDP-Data and camelCapabilityHandling shall be present in -the SMS-CSI sequence. -If SMS-CSI is segmented, sms-CAMEL-TDP-DataList and camelCapabilityHandling shall be -present in the first segment SMS-CAMEL-TDP-DataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF SMS-CAMEL-TDP-Data -SMS-CAMEL-TDP-DataList shall not contain more than one instance of -SMS-CAMEL-TDP-Data containing the same value for sms-TriggerDetectionPoint. SMS-CAMEL-TDP-Data ::= SEQUENCE { sms-TriggerDetectionPoint serviceKey gsmSCF-Address defaultSMS-Handling extensionContainer ... } [0] [1] [2] [3] [4] SMS-TriggerDetectionPoint, ServiceKey, ISDN-AddressString, DefaultSMS-Handling, ExtensionContainer

OPTIONAL,

1422

3GPP

1423 Release 7 1424 1425

1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869

357

3GPP TS 29.002 V7.5.0 (2006-09)

SMS-TriggerDetectionPoint ::= ENUMERATED { sms-CollectedInfo (1), ..., sms-DeliveryRequest (2) } -exception handling: -For SMS-CAMEL-TDP-Data and MT-smsCAMELTDP-Criteria sequences containing this -parameter with any other value than the ones listed the receiver shall ignore -the whole sequence. --If this parameter is received with any other value than sms-CollectedInfo -in an SMS-CAMEL-TDP-Data sequence contained in mo-sms-CSI, then the receiver shall -ignore the whole SMS-CAMEL-TDP-Data sequence. --If this parameter is received with any other value than sms-DeliveryRequest -in an SMS-CAMEL-TDP-Data sequence contained in mt-sms-CSI then the receiver shall -ignore the whole SMS-CAMEL-TDP-Data sequence. --If this parameter is received with any other value than sms-DeliveryRequest -in an MT-smsCAMELTDP-Criteria sequence then the receiver shall -ignore the whole MT-smsCAMELTDP-Criteria sequence. DefaultSMS-Handling ::= ENUMERATED { continueTransaction (0) , releaseTransaction (1) , ...} -exception handling: -reception of values in range 2-31 shall be treated as "continueTransaction" -reception of values greater than 31 shall be treated as "releaseTransaction" M-CSI ::= SEQUENCE { mobilityTriggers MobilityTriggers, serviceKey ServiceKey, gsmSCF-Address [0] ISDN-AddressString, extensionContainer [1] ExtensionContainer OPTIONAL, notificationToCSE [2] NULL OPTIONAL, csi-Active [3] NULL OPTIONAL, ...} -notificationToCSE and csi-Active shall not be present when M-CSI is sent to VLR. -They may only be included in ATSI/ATM ack/NSDC message. MG-CSI ::= SEQUENCE { mobilityTriggers MobilityTriggers, serviceKey ServiceKey, gsmSCF-Address [0] ISDN-AddressString, extensionContainer [1] ExtensionContainer OPTIONAL, notificationToCSE [2] NULL OPTIONAL, csi-Active [3] NULL OPTIONAL, ...} -notificationToCSE and csi-Active shall not be present when MG-CSI is sent to SGSN. -They may only be included in ATSI/ATM ack/NSDC message. MobilityTriggers MM-Code ::= SEQUENCE SIZE (1..maxNumOfMobilityTriggers) OF

maxNumOfMobilityTriggers INTEGER ::= 10

1426

3GPP

1427 Release 7 1428 1429

1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944

358

3GPP TS 29.002 V7.5.0 (2006-09)

MM-Code ::= OCTET STRING (SIZE (1)) -This type is used to indicate a Mobility Management event. -Actions for the following MM-Code values are defined in CAMEL Phase 4: --CS domain MM events: -Location-update-in-same-VLR MM-Code ::= '00000000'B -Location-update-to-other-VLR MM-Code ::= '00000001'B -IMSI-Attach MM-Code ::= '00000010'B -MS-initiated-IMSI-Detach MM-Code ::= '00000011'B -Network-initiated-IMSI-Detach MM-Code ::= '00000100'B --PS domain MM events: -Routeing-Area-update-in-same-SGSN MM-Code ::= '10000000'B -Routeing-Area-update-to-other-SGSN-update-from-new-SGSN -MM-Code ::= '10000001'B -Routeing-Area-update-to-other-SGSN-disconnect-by-detach -MM-Code ::= '10000010'B -GPRS-Attach MM-Code ::= '10000011'B -MS-initiated-GPRS-Detach MM-Code ::= '10000100'B -Network-initiated-GPRS-Detach MM-Code ::= '10000101'B -Network-initiated-transfer-to-MS-not-reachable-for-paging -MM-Code ::= '10000110'B --If the MSC receives any other MM-code than the ones listed above for the -CS domain, then the MSC shall ignore that MM-code. -If the SGSN receives any other MM-code than the ones listed above for the -PS domain, then the SGSN shall ignore that MM-code. T-CSI ::= SEQUENCE { t-BcsmCamelTDPDataList T-BcsmCamelTDPDataList, extensionContainer ExtensionContainer OPTIONAL, ..., camelCapabilityHandling [0] CamelCapabilityHandling OPTIONAL, notificationToCSE [1] NULL OPTIONAL, csi-Active [2] NULL OPTIONAL} -notificationToCSE and csi-Active shall not be present when VT-CSI/T-CSI is sent -to VLR/GMSC. -They may only be included in ATSI/ATM ack/NSDC message. -T-CSI shall not be segmented. T-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF T-BcsmCamelTDPData --- T-BcsmCamelTDPDataList shall not contain more than one instance of --- T-BcsmCamelTDPData containing the same value for t-BcsmTriggerDetectionPoint. --- For CAMEL Phase 2, this means that only one instance of T-BcsmCamelTDPData is allowed --- with t-BcsmTriggerDetectionPoint being equal to DP12. --- For CAMEL Phase 3, more TDPs are allowed. T-BcsmCamelTDPData ::= SEQUENCE { t-BcsmTriggerDetectionPoint serviceKey gsmSCF-Address defaultCallHandling extensionContainer ...} T-BcsmTriggerDetectionPoint, ServiceKey, [0] ISDN-AddressString, [1] DefaultCallHandling, [2] ExtensionContainer

OPTIONAL,

T-BcsmTriggerDetectionPoint ::= ENUMERATED { termAttemptAuthorized (12), ... , tBusy (13), tNoAnswer (14)} -- exception handling: -- For T-BcsmCamelTDPData sequences containing this parameter with any other -- value than the ones listed above, the receiver shall ignore the whole -- T-BcsmCamelTDPData sequence. -- gprs location information retrieval types SendRoutingInfoForGprsArg ::= SEQUENCE { imsi ggsn-Address ggsn-Number extensionContainer ...} [0] IMSI, [1] GSN-Address [2] ISDN-AddressString, [3] ExtensionContainer

OPTIONAL, OPTIONAL,

1430

3GPP

1431 Release 7 1432 1433

1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020

359

3GPP TS 29.002 V7.5.0 (2006-09)

SendRoutingInfoForGprsRes ::= SEQUENCE { sgsn-Address ggsn-Address mobileNotReachableReason extensionContainer ...}

[0] GSN-Address, [1] GSN-Address OPTIONAL, [2] AbsentSubscriberDiagnosticSM OPTIONAL, [3] ExtensionContainer OPTIONAL,

-- failure report types FailureReportArg ::= SEQUENCE { imsi ggsn-Number ggsn-Address extensionContainer ...} FailureReportRes ::= SEQUENCE { ggsn-Address extensionContainer ...} -- gprs notification types NoteMsPresentForGprsArg ::= SEQUENCE { imsi sgsn-Address ggsn-Address extensionContainer ...} NoteMsPresentForGprsRes ::= SEQUENCE { extensionContainer ...} -- fault recovery types ResetArg ::= SEQUENCE { hlr-Number hlr-List ...} RestoreDataArg ::= SEQUENCE { imsi lmsi extensionContainer ... , vlr-Capability RestoreDataRes ::= SEQUENCE { hlr-Number msNotReachable extensionContainer ...} ISDN-AddressString, HLR-List [0] [1] [2] [3] IMSI, GSN-Address, GSN-Address ExtensionContainer [0] [1] [2] [3] IMSI, ISDN-AddressString GSN-Address ExtensionContainer

, OPTIONAL, OPTIONAL,

[0] GSN-Address [1] ExtensionContainer

OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL,

[0] ExtensionContainer

OPTIONAL,

OPTIONAL,

IMSI, LMSI ExtensionContainer [6] VLR-Capability ISDN-AddressString, NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL }

OPTIONAL, OPTIONAL,

-- VBS/VGCS types VBSDataList ::= SEQUENCE SIZE (1..maxNumOfVBSGroupIds) OF VoiceBroadcastData VGCSDataList ::= SEQUENCE SIZE (1..maxNumOfVGCSGroupIds) OF VoiceGroupCallData maxNumOfVBSGroupIds maxNumOfVGCSGroupIds INTEGER ::= 50 INTEGER ::= 50 GroupId, ExtensionContainer AdditionalSubscriptions [0] AdditionalInfo

VoiceGroupCallData ::= SEQUENCE { groupId extensionContainer ..., additionalSubscriptions additionalInfo

OPTIONAL, OPTIONAL, OPTIONAL }

AdditionalInfo ::= BIT STRING (SIZE (1..136)) -Refers to Additional Info as specified in 3GPP TS 43.068

1434

3GPP

1435 Release 7 1436 1437

2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098

360

3GPP TS 29.002 V7.5.0 (2006-09)

AdditionalSubscriptions ::= BIT STRING { privilegedUplinkRequest (0), emergencyUplinkRequest (1), emergencyReset (2)} (SIZE (3..8)) -- Other bits than listed above shall be discarded. VoiceBroadcastData ::= SEQUENCE { groupid broadcastInitEntitlement extensionContainer ...} GroupId ----GroupId, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

::= TBCD-STRING (SIZE (3)) When Group-Id is less than six characters in length, the TBCD filler (1111) is used to fill unused half octets. Refers to the Group Identification as specified in 3GPP TS 23.003 and 3GPP TS 43.068/ 43.069

-- provide subscriber info types ProvideSubscriberInfoArg ::= SEQUENCE { imsi [0] IMSI, lmsi [1] LMSI requestedInfo extensionContainer ...} ProvideSubscriberInfoRes ::= SEQUENCE { subscriberInfo extensionContainer ...} SubscriberInfo ::= SEQUENCE { locationInformation subscriberState extensionContainer ... , locationInformationGPRS ps-SubscriberState imei ms-Classmark2 gprs-MS-Class mnpInfoRes ------

OPTIONAL, [2] RequestedInfo, [3] ExtensionContainer

OPTIONAL,

SubscriberInfo, ExtensionContainer

OPTIONAL,

[0] LocationInformation [1] SubscriberState [2] ExtensionContainer [3] [4] [5] [6] [7] [8] LocationInformationGPRS PS-SubscriberState IMEI MS-Classmark2 GPRSMSClass MNPInfoRes

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

If the HLR receives locationInformation, subscriberState or ms-Classmark2 from an SGSN it shall discard them. If the HLR receives locationInformationGPRS, ps-SubscriberState or gprs-MS-Class from a VLR it shall discard them. If the HLR receives parameters which it has not requested, it shall discard them. routeingNumber [0] RouteingNumber OPTIONAL, imsi [1] IMSI OPTIONAL, msisdn [2] ISDN-AddressString OPTIONAL, numberPortabilityStatus [3] NumberPortabilityStatus OPTIONAL, extensionContainer [4] ExtensionContainer OPTIONAL, ... } The IMSI parameter contains a generic IMSI, i.e. it is not tied necessarily to the Subscriber. MCC and MNC values in this IMSI shall point to the Subscription Network of the Subscriber. See 3GPP TS 23.066 [108].

MNPInfoRes ::= SEQUENCE {

----

RouteingNumber ::= TBCD-STRING (SIZE (1..5)) NumberPortabilityStatus ::= ENUMERATED { notKnownToBePorted (0), ownNumberPortedOut (1), foreignNumberPortedToForeignNetwork (2), ..., ownNumberNotPortedOut (4), foreignNumberPortedIn (5) } -exception handling: -- reception of other values than the ones listed the receiver shall ignore the -- whole NumberPortabilityStatus; -- ownNumberNotPortedOut or foreignNumberPortedIn may only be included in Any Time -- Interrogation message.

1438

3GPP

1439 Release 7 1440 1441

2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176

361

3GPP TS 29.002 V7.5.0 (2006-09)

MS-Classmark2 ::= OCTET STRING (SIZE (3)) -- This parameter carries the value part of the MS Classmark 2 IE defined in -- 3GPP TS 24.008 [35]. GPRSMSClass ::= SEQUENCE { mSNetworkCapability mSRadioAccessCapability } [0] MSNetworkCapability, [1] MSRadioAccessCapability

OPTIONAL

MSNetworkCapability ::= OCTET STRING (SIZE (1..8)) -- This parameter carries the value part of the MS Network Capability IE defined in -- 3GPP TS 24.008 [35]. MSRadioAccessCapability ::= OCTET STRING (SIZE (1..50)) -- This parameter carries the value part of the MS Radio Access Capability IE defined in -- 3GPP TS 24.008 [35]. RequestedInfo ::= SEQUENCE { locationInformation subscriberState extensionContainer ..., currentLocation requestedDomain imei ms-classmark mnpRequestedInfo -[0] NULL [1] NULL [2] ExtensionContainer [3] [4] [6] [5] [7] NULL DomainType NULL NULL NULL OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

currentLocation shall be absent if locationInformation is absent

DomainType ::= ENUMERATED { cs-Domain (0), ps-Domain (1), ...} -- exception handling: -- reception of values > 1 shall be mapped to 'cs-Domain' LocationInformation ::= SEQUENCE { ageOfLocationInformation AgeOfLocationInformation OPTIONAL, geographicalInformation [0] GeographicalInformation OPTIONAL, vlr-number [1] ISDN-AddressString OPTIONAL, locationNumber [2] LocationNumber OPTIONAL, cellGlobalIdOrServiceAreaIdOrLAI [3] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, extensionContainer [4] ExtensionContainer OPTIONAL, ... , selectedLSA-Id [5] LSAIdentity OPTIONAL, msc-Number [6] ISDN-AddressString OPTIONAL, geodeticInformation [7] GeodeticInformation OPTIONAL, currentLocationRetrieved [8] NULL OPTIONAL, sai-Present [9] NULL OPTIONAL } -- sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI parameter contains -- a Service Area Identity. -- currentLocationRetrieved shall be present -- if the location information were retrieved after a successfull paging. LocationInformationGPRS ::= SEQUENCE { cellGlobalIdOrServiceAreaIdOrLAI [0] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, routeingAreaIdentity [1] RAIdentity OPTIONAL, geographicalInformation [2] GeographicalInformation OPTIONAL, sgsn-Number [3] ISDN-AddressString OPTIONAL, selectedLSAIdentity [4] LSAIdentity OPTIONAL, extensionContainer [5] ExtensionContainer OPTIONAL, ..., sai-Present [6] NULL OPTIONAL, geodeticInformation [7] GeodeticInformation OPTIONAL, currentLocationRetrieved [8] NULL OPTIONAL, ageOfLocationInformation [9] AgeOfLocationInformation OPTIONAL } -- sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI parameter contains -- a Service Area Identity. -- currentLocationRetrieved shall be present if the location information -- was retrieved after successful paging. RAIdentity ::= OCTET STRING (SIZE (6)) -- Routing Area Identity is coded in accordance with 3GPP TS 29.060 [105]. -- It shall contain the value part defined in 3GPP TS 29.060 only. I.e. the 3GPP TS 29.060 -- type identifier octet shall not be included.

1442

3GPP

1443 Release 7 1444 1445

2177 2178 2179 2180 2181 2182 2183 2184 2185 2186

362

3GPP TS 29.002 V7.5.0 (2006-09)

GeographicalInformation ::= OCTET STRING (SIZE (8)) -Refers to geographical Information defined in 3GPP TS 23.032. -Only the description of an ellipsoid point with uncertainty circle -as specified in 3GPP TS 23.032 is allowed to be used -The internal structure according to 3GPP TS 23.032 is as follows: -Type of shape (ellipsoid point with uncertainty circle) -Degrees of Latitude -Degrees of Longitude -Uncertainty code GeodeticInformation ::= OCTET STRING (SIZE (10)) -Refers to Calling Geodetic Location defined in Q.763 (1999). -Only the description of an ellipsoid point with uncertainty circle -as specified in Q.763 (1999) is allowed to be used -The internal structure according to Q.763 (1999) is as follows: -Screening and presentation indicators -Type of shape (ellipsoid point with uncertainty circle) -Degrees of Latitude -Degrees of Longitude -Uncertainty code -Confidence

1 3 3 1

octet octets octets octet

1 1 3 3 1 1

octet octet octets octets octet octet

2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239

LocationNumber ::= OCTET STRING (SIZE (2..10)) -- the internal structure is defined in ITU-T Rec Q.763 SubscriberState ::= CHOICE { assumedIdle camelBusy netDetNotReachable notProvidedFromVLR PS-SubscriberState ::= CHOICE { notProvidedFromSGSN ps-Detached ps-AttachedNotReachableForPaging ps-AttachedReachableForPaging ps-PDP-ActiveNotReachableForPaging ps-PDP-ActiveReachableForPaging netDetNotReachable [0] NULL, [1] NULL, NotReachableReason, [2] NULL} [0] NULL, [1] NULL, [2] NULL, [3] NULL, [4] PDP-ContextInfoList, [5] PDP-ContextInfoList, NotReachableReason }

PDP-ContextInfoList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF PDP-ContextInfo PDP-ContextInfo ::= SEQUENCE { pdp-ContextIdentifier [0] ContextId, pdp-ContextActive [1] NULL pdp-Type [2] PDP-Type, pdp-Address [3] PDP-Address apn-Subscribed [4] APN apn-InUse [5] APN nsapi [6] NSAPI transactionId [7] TransactionId teid-ForGnAndGp [8] TEID teid-ForIu [9] TEID ggsn-Address [10] GSN-Address qos-Subscribed [11] Ext-QoS-Subscribed qos-Requested [12] Ext-QoS-Subscribed qos-Negotiated [13] Ext-QoS-Subscribed chargingId [14] GPRSChargingID chargingCharacteristics [15] ChargingCharacteristics rnc-Address [16] GSN-Address extensionContainer [17] ExtensionContainer ..., qos2-Subscribed [18] Ext2-QoS-Subscribed -- qos2-Subscribed may be present only if qos-Subscribed is present. qos2-Requested [19] Ext2-QoS-Subscribed -- qos2-Requested may be present only if qos-Requested is present. qos2-Negotiated [20] Ext2-QoS-Subscribed -- qos2-Negotiated may be present only if qos-Negotiated is present. } NSAPI ::= INTEGER (0..15) -This type is used to indicate the Network layer Service Access Point

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

1446

3GPP

1447 Release 7 1448 1449

2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316

363

3GPP TS 29.002 V7.5.0 (2006-09)

TransactionId ::= OCTET STRING (SIZE (1..2)) -This type carries the value part of the transaction identifier which is used in the -session management messages on the access interface. The encoding is defined in -3GPP TS 24.008 TEID ---::= OCTET STRING (SIZE (4)) This type carries the value part of the Tunnel Endpoint Identifier which is used to distinguish between different tunnels between the same pair of entities which communicate using the GPRS Tunnelling Protocol The encoding is defined in 3GPP TS 29.060.

GPRSChargingID ::= OCTET STRING (SIZE (4)) -The Charging ID is a unique four octet value generated by the GGSN when -a PDP Context is activated. A Charging ID is generated for each activated context. -The encoding is defined in 3GPP TS 29.060. NotReachableReason ::= ENUMERATED { msPurged (0), imsiDetached (1), restrictedArea (2), notRegistered (3)} -- any time interrogation info types AnyTimeInterrogationArg ::= SEQUENCE { subscriberIdentity requestedInfo gsmSCF-Address extensionContainer ...} AnyTimeInterrogationRes ::= SEQUENCE { subscriberInfo extensionContainer ...} -- any time information handling types AnyTimeSubscriptionInterrogationArg ::= SEQUENCE { subscriberIdentity [0] SubscriberIdentity, requestedSubscriptionInfo [1] RequestedSubscriptionInfo, gsmSCF-Address [2] ISDN-AddressString, extensionContainer [3] ExtensionContainer longFTN-Supported [4] NULL ...} AnyTimeSubscriptionInterrogationRes ::= SEQUENCE { callForwardingData [1] CallForwardingData callBarringData [2] CallBarringData odb-Info [3] ODB-Info camel-SubscriptionInfo [4] CAMEL-SubscriptionInfo supportedVLR-CAMEL-Phases [5] SupportedCamelPhases supportedSGSN-CAMEL-Phases [6] SupportedCamelPhases extensionContainer [7] ExtensionContainer ... , offeredCamel4CSIsInVLR [8] OfferedCamel4CSIs offeredCamel4CSIsInSGSN [9] OfferedCamel4CSIs msisdn-BS-List [10] MSISDN-BS-List [0] [1] [3] [2] SubscriberIdentity, RequestedInfo, ISDN-AddressString, ExtensionContainer

OPTIONAL,

SubscriberInfo, ExtensionContainer

OPTIONAL,

OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

RequestedSubscriptionInfo ::= SEQUENCE { requestedSS-Info [1] SS-ForBS-Code OPTIONAL, odb [2] NULL OPTIONAL, requestedCAMEL-SubscriptionInfo [3] RequestedCAMEL-SubscriptionInfo OPTIONAL, supportedVLR-CAMEL-Phases [4] NULL OPTIONAL, supportedSGSN-CAMEL-Phases [5] NULL OPTIONAL, extensionContainer [6] ExtensionContainer OPTIONAL, ..., additionalRequestedCAMEL-SubscriptionInfo [7] AdditionalRequestedCAMEL-SubscriptionInfo OPTIONAL, msisdn-BS-List [8] NULL OPTIONAL } MSISDN-BS-List ::= SEQUENCE SIZE (1..maxNumOfMSISDN) OF MSISDN-BS maxNumOfMSISDN INTEGER ::= 50

1450

3GPP

1451 Release 7 1452 1453

2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391

364

3GPP TS 29.002 V7.5.0 (2006-09)

MSISDN-BS ::= SEQUENCE { msisdn basicServiceList extensionContainer ...}

[0] [1]

ISDN-AddressString, BasicServiceList ExtensionContainer

OPTIONAL, OPTIONAL,

RequestedCAMEL-SubscriptionInfo ::= ENUMERATED { o-CSI (0), t-CSI (1), vt-CSI (2), tif-CSI (3), gprs-CSI (4), mo-sms-CSI (5), ss-CSI (6), m-CSI (7), d-csi (8)} AdditionalRequestedCAMEL-SubscriptionInfo ::= ENUMERATED { mt-sms-CSI (0), mg-csi (1), o-IM-CSI (2), d-IM-CSI (3), vt-IM-CSI (4), ...} -exception handling: unknown values shall be discarded by the receiver. CallForwardingData ::= SEQUENCE { forwardingFeatureList notificationToCSE extensionContainer ...} CallBarringData ::= SEQUENCE { callBarringFeatureList password wrongPasswordAttemptsCounter notificationToCSE extensionContainer ...} Ext-ForwFeatureList, NULL [0] ExtensionContainer

OPTIONAL, OPTIONAL,

Ext-CallBarFeatureList, Password WrongPasswordAttemptsCounter NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

WrongPasswordAttemptsCounter ::= INTEGER (0..4) ODB-Info ::= SEQUENCE { odb-Data notificationToCSE extensionContainer ...} CAMEL-SubscriptionInfo ::= SEQUENCE { o-CSI o-BcsmCamelTDP-CriteriaList d-CSI t-CSI t-BCSM-CAMEL-TDP-CriteriaList vt-CSI vt-BCSM-CAMEL-TDP-CriteriaList tif-CSI tif-CSI-NotificationToCSE gprs-CSI mo-sms-CSI ss-CSI m-CSI extensionContainer ..., specificCSIDeletedList mt-sms-CSI mt-smsCAMELTDP-CriteriaList mg-csi o-IM-CSI o-IM-BcsmCamelTDP-CriteriaList d-IM-CSI vt-IM-CSI vt-IM-BCSM-CAMEL-TDP-CriteriaList } ODB-Data, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]

O-CSI O-BcsmCamelTDPCriteriaList D-CSI T-CSI T-BCSM-CAMEL-TDP-CriteriaList T-CSI T-BCSM-CAMEL-TDP-CriteriaList NULL NULL GPRS-CSI SMS-CSI SS-CSI M-CSI ExtensionContainer SpecificCSI-Withdraw SMS-CSI MT-smsCAMELTDP-CriteriaList MG-CSI O-CSI O-BcsmCamelTDPCriteriaList D-CSI T-CSI T-BCSM-CAMEL-TDP-CriteriaList

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

1454

3GPP

1455 Release 7 1456 1457

2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469

365

3GPP TS 29.002 V7.5.0 (2006-09)

AnyTimeModificationArg ::= SEQUENCE { subscriberIdentity gsmSCF-Address modificationRequestFor-CF-Info modificationRequestFor-CB-Info modificationRequestFor-CSI extensionContainer longFTN-Supported ..., modificationRequestFor-ODB-data AnyTimeModificationRes ::= SEQUENCE { ss-InfoFor-CSE camel-SubscriptionInfo extensionContainer ..., odb-Info

[0] [1] [2] [3] [4] [5] [6] [7] [0] [1] [2] [3]

SubscriberIdentity, ISDN-AddressString, ModificationRequestFor-CF-Info OPTIONAL, ModificationRequestFor-CB-Info OPTIONAL, ModificationRequestFor-CSI OPTIONAL, ExtensionContainer OPTIONAL, NULL OPTIONAL, ModificationRequestFor-ODB-data OPTIONAL } Ext-SS-InfoFor-CSE CAMEL-SubscriptionInfo ExtensionContainer ODB-Info SS-Code, Ext-BasicServiceCode Ext-SS-Status AddressString ISDN-SubaddressString Ext-NoRepCondTime ModificationInstruction ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

ModificationRequestFor-CF-Info ::= SEQUENCE { ss-Code [0] basicService [1] ss-Status [2] forwardedToNumber [3] forwardedToSubaddress [4] noReplyConditionTime [5] modifyNotificationToCSE [6] extensionContainer [7] ...} ModificationRequestFor-CB-Info ::= SEQUENCE { ss-Code [0] basicService [1] ss-Status [2] password [3] wrongPasswordAttemptsCounter [4] modifyNotificationToCSE [5] extensionContainer [6] ...}

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

SS-Code, Ext-BasicServiceCode Ext-SS-Status Password WrongPasswordAttemptsCounter ModificationInstruction ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

ModificationRequestFor-ODB-data ::= SEQUENCE { odb-data [0] ODB-Data modifyNotificationToCSE [1] ModificationInstruction extensionContainer [2] ExtensionContainer ...}

OPTIONAL, OPTIONAL, OPTIONAL,

ModificationRequestFor-CSI ::= SEQUENCE { requestedCamel-SubscriptionInfo [0] RequestedCAMEL-SubscriptionInfo, modifyNotificationToCSE [1] ModificationInstruction OPTIONAL, modifyCSI-State [2] ModificationInstruction OPTIONAL, extensionContainer [3] ExtensionContainer OPTIONAL, ..., additionalRequestedCAMEL-SubscriptionInfo [4] AdditionalRequestedCAMEL-SubscriptionInfo OPTIONAL } -- requestedCamel-SubscriptionInfo shall be discarded if -- additionalRequestedCAMEL-SubscriptionInfo is received ModificationInstruction ::= ENUMERATED { deactivate activate (0), (1)}

-- subscriber data modification notification types NoteSubscriberDataModifiedArg ::= SEQUENCE { imsi IMSI, msisdn ISDN-AddressString, forwardingInfoFor-CSE [0] Ext-ForwardingInfoFor-CSE callBarringInfoFor-CSE [1] Ext-CallBarringInfoFor-CSE odb-Info [2] ODB-Info camel-SubscriptionInfo [3] CAMEL-SubscriptionInfo allInformationSent [4] NULL extensionContainer ExtensionContainer ...} NoteSubscriberDataModifiedRes ::= SEQUENCE { extensionContainer ExtensionContainer ...}

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

OPTIONAL,

1458

3GPP

1459 Release 7 1460 1461

2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510

366

3GPP TS 29.002 V7.5.0 (2006-09)

-- mobility management event notificatioon info types NoteMM-EventArg::= SEQUENCE { serviceKey eventMet imsi msisdn locationInformation supportedCAMELPhases extensionContainer ..., locationInformationGPRS offeredCamel4Functionalities } NoteMM-EventRes ::= SEQUENCE { extensionContainer ...} Ext-SS-InfoFor-CSE ::= CHOICE { forwardingInfoFor-CSE callBarringInfoFor-CSE } Ext-ForwardingInfoFor-CSE ::= SEQUENCE { ss-Code forwardingFeatureList notificationToCSE extensionContainer ...} ServiceKey, [0] MM-Code, [1] IMSI, [2] ISDN-AddressString, [3] LocationInformation [5] SupportedCamelPhases [6] ExtensionContainer [7] LocationInformationGPRS [8] OfferedCamel4Functionalities

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

ExtensionContainer

OPTIONAL,

[0] Ext-ForwardingInfoFor-CSE, [1] Ext-CallBarringInfoFor-CSE

[0] [1] [2] [3]

SS-Code, Ext-ForwFeatureList, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

Ext-CallBarringInfoFor-CSE ::= SEQUENCE { ss-Code [0] callBarringFeatureList [1] password [2] wrongPasswordAttemptsCounter [3] notificationToCSE [4] extensionContainer [5] ...} END

SS-Code, Ext-CallBarFeatureList, Password WrongPasswordAttemptsCounter NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

2511
2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544

17.7.2 Operation and maintenance data types

MAP-OM-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS ActivateTraceModeArg, ActivateTraceModeRes, DeactivateTraceModeArg, DeactivateTraceModeRes, TracePropagationList ; IMPORTS AddressString, IMSI FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ;

1462

3GPP

1463 Release 7 1464 1465

2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617

367

3GPP TS 29.002 V7.5.0 (2006-09)

ActivateTraceModeArg ::= SEQUENCE { imsi traceReference traceType omc-Id extensionContainer ..., traceReference2 traceDepthList traceNE-TypeList traceInterfaceList traceEventList }

[0] [1] [2] [3] [4] [5] [6] [7] [8] [9]

IMSI TraceReference, TraceType, AddressString ExtensionContainer TraceReference2 TraceDepthList TraceNE-TypeList TraceInterfaceList TraceEventList

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

TraceReference ::= OCTET STRING (SIZE (1..2)) TraceReference2 ::= OCTET STRING (SIZE (3)) TraceRecordingSessionReference ::= OCTET STRING (SIZE (2)) TraceType ::= INTEGER (0..255) -- Trace types are fully defined in TraceDepthList ::= SEQUENCE { msc-s-TraceDepth mgw-TraceDepth sgsn-TraceDepth ggsn-TraceDepth rnc-TraceDepth bmsc-TraceDepth ...}

3GPP TS 52.008. [61] [0] [1] [2] [3] [4] [5] TraceDepth TraceDepth TraceDepth TraceDepth TraceDepth TraceDepth OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

TraceDepth ::= ENUMERATED { minimum (0), medium (1), maximum (2), ...} -- The value medium is applicable only for RNC. For other network elements, if value medium -- is received, value minimum shall be applied. TraceNE-TypeList ::= BIT STRING { msc-s (0), mgw (1), sgsn (2), ggsn (3), rnc (4), bm-sc (5)} (SIZE (6..16)) -- Other bits than listed above shall be discarded. TraceInterfaceList ::= SEQUENCE { msc-s-List mgw-List sgsn-List ggsn-List rnc-List bmsc-List ...} [0] [1] [2] [3] [4] [5] MSC-S-InterfaceList MGW-InterfaceList SGSN-InterfaceList GGSN-InterfaceList RNC-InterfaceList BMSC-InterfaceList OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

MSC-S-InterfaceList ::= BIT STRING { a (0), iu (1), mc (2), map-g (3), map-b (4), map-e (5), map-f (6), cap (7), map-d (8), map-c (9)} (SIZE (10..16)) -- Other bits than listed above shall be discarded.

1466

3GPP

1467 Release 7 1468 1469

2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688

368

3GPP TS 29.002 V7.5.0 (2006-09)

MGW-InterfaceList ::= BIT STRING { mc (0), nb-up (1), iu-up (2)} (SIZE (3..8)) -- Other bits than listed above shall be discarded. SGSN-InterfaceList ::= BIT STRING { gb (0), iu (1), gn (2), map-gr (3), map-gd (4), map-gf (5), gs (6), ge (7)} (SIZE (8..16)) -- Other bits than listed above shall be discarded. GGSN-InterfaceList ::= BIT STRING { gn (0), gi (1), gmb (2)} (SIZE (3..8)) -- Other bits than listed above shall be discarded. RNC-InterfaceList ::= BIT STRING { iu (0), iur (1), iub (2), uu (3)} (SIZE (4..8)) -- Other bits than listed above shall be discarded. BMSC-InterfaceList ::= BIT STRING { gmb (0)} (SIZE (1..8)) -- Other bits than listed above shall be discarded. TraceEventList ::= SEQUENCE { msc-s-List mgw-List sgsn-List ggsn-List bmsc-List ...} [0] [1] [2] [3] [4] MSC-S-EventList MGW-EventList SGSN-EventList GGSN-EventList BMSC-EventList OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

MSC-S-EventList ::= BIT STRING { mo-mtCall (0), mo-mt-sms (1), lu-imsiAttach-imsiDetach (2), handovers (3), ss (4)} (SIZE (5..16)) -- Other bits than listed above shall be discarded. MGW-EventList ::= BIT STRING { context (0)} (SIZE (1..8)) -- Other bits than listed above shall be discarded. SGSN-EventList ::= BIT STRING { pdpContext (0), mo-mt-sms (1), rau-gprsAttach-gprsDetach (2), mbmsContext (3)} (SIZE (4..16)) -- Other bits than listed above shall be discarded. GGSN-EventList ::= BIT STRING { pdpContext (0), mbmsContext (1)} (SIZE (2..8)) -- Other bits than listed above shall be discarded. BMSC-EventList ::= BIT STRING { mbmsMulticastServiceActivation (0)} (SIZE (1..8)) -- Other bits than listed above shall be discarded.

1470

3GPP

1471 Release 7 1472 1473

2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722

369

3GPP TS 29.002 V7.5.0 (2006-09)

TracePropagationList ::= SEQUENCE { traceReference traceType traceReference2 traceRecordingSessionReference rnc-TraceDepth rnc-InterfaceList msc-s-TraceDepth msc-s-InterfaceList msc-s-EventList mgw-TraceDepth mgw-InterfaceList mgw-EventList ...} ActivateTraceModeRes ::= SEQUENCE { extensionContainer ..., traceSupportIndicator } DeactivateTraceModeArg ::= SEQUENCE { imsi traceReference extensionContainer ..., traceReference2 } DeactivateTraceModeRes ::= SEQUENCE { extensionContainer ...}

[0] TraceReference OPTIONAL, [1] TraceType OPTIONAL, [2] TraceReference2 OPTIONAL, [3] TraceRecordingSessionReference OPTIONAL, [4] TraceDepth OPTIONAL, [5] RNC-InterfaceList OPTIONAL, [6] TraceDepth OPTIONAL, [7] MSC-S-InterfaceList OPTIONAL, [8] MSC-S-EventList OPTIONAL, [9] TraceDepth OPTIONAL, [10] MGW-InterfaceList OPTIONAL, [11] MGW-EventList OPTIONAL,

[0] ExtensionContainer [1] NULL

OPTIONAL, OPTIONAL

[0] IMSI [1] TraceReference, [2] ExtensionContainer [3] TraceReference2

OPTIONAL, OPTIONAL, OPTIONAL

[0] ExtensionContainer

OPTIONAL,

END

2723
2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764

17.7.3 Call handling data types

MAP-CH-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CH-DataTypes (13) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg, ResumeCallHandlingRes, NumberOfForwarding, SuppressionOfAnnouncement, CallReferenceNumber, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes, IST-AlertArg, IST-AlertRes, IST-CommandArg, IST-CommandRes, UU-Data, ReleaseResourcesArg, ReleaseResourcesRes ; IMPORTS SubscriberInfo, SupportedCamelPhases, OfferedCamel4CSIs,

1474

3GPP

1475 Release 7 1476 1477

2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813

370

3GPP TS 29.002 V7.5.0 (2006-09)

CUG-Interlock, O-CSI, D-CSI, O-BcsmCamelTDPCriteriaList, T-BCSM-CAMEL-TDP-CriteriaList, IST-SupportIndicator, IST-AlertTimerValue, T-CSI, NumberPortabilityStatus FROM MAP-MS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version10 (10)} ForwardingOptions, SS-List, CCBS-Feature FROM MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString, ExternalSignalInfo, Ext-ExternalSignalInfo, IMSI, LMSI, Ext-BasicServiceCode, AlertingPattern, NAEA-PreferredCI FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ; CUG-CheckInfo ::= SEQUENCE { cug-Interlock cug-OutgoingAccess extensionContainer ...} NumberOfForwarding ::= INTEGER (1..5)

CUG-Interlock, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

1478

3GPP

1479 Release 7 1480 1481

2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870

371

3GPP TS 29.002 V7.5.0 (2006-09)

SendRoutingInfoArg ::= SEQUENCE { msisdn cug-CheckInfo numberOfForwarding interrogationType or-Interrogation or-Capability gmsc-OrGsmSCF-Address callReferenceNumber forwardingReason basicServiceGroup networkSignalInfo camelInfo suppressionOfAnnouncement extensionContainer ..., alertingPattern ccbs-Call supportedCCBS-Phase additionalSignalInfo istSupportIndicator pre-pagingSupported callDiversionTreatmentIndicator longFTN-Supported suppress-VT-CSI suppressIncomingCallBarring gsmSCF-InitiatedCall basicServiceGroup2 networkSignalInfo2 } SuppressionOfAnnouncement ::= NULL InterrogationType ::= ENUMERATED { basicCall (0), forwarding (1)} OR-Phase ::= INTEGER (1..127)

[0] ISDN-AddressString, [1] CUG-CheckInfo [2] NumberOfForwarding [3] InterrogationType, [4] NULL [5] OR-Phase [6] ISDN-AddressString, [7] CallReferenceNumber [8] ForwardingReason [9] Ext-BasicServiceCode [10] ExternalSignalInfo [11] CamelInfo [12] SuppressionOfAnnouncement [13] ExtensionContainer [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26]

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

AlertingPattern OPTIONAL, NULL OPTIONAL, SupportedCCBS-Phase OPTIONAL, Ext-ExternalSignalInfo OPTIONAL, IST-SupportIndicator OPTIONAL, NULL OPTIONAL, CallDiversionTreatmentIndicator OPTIONAL, NULL OPTIONAL, NULL OPTIONAL, NULL OPTIONAL, NULL OPTIONAL, Ext-BasicServiceCode OPTIONAL, ExternalSignalInfo OPTIONAL

CallReferenceNumber ::= OCTET STRING (SIZE (1..8)) ForwardingReason ::= ENUMERATED { notReachable (0), busy (1), noReply (2)} SupportedCCBS-Phase ::= INTEGER (1..127) -- exception handling: -- Only value 1 is used. -- Values in the ranges 2-127 are reserved for future use. -- If received values 2-127 shall be mapped on to value 1. CallDiversionTreatmentIndicator ::= OCTET STRING (SIZE(1)) -callDiversionAllowed (xxxx xx01) -callDiversionNotAllowed (xxxx xx10) -network default is call diversion allowed

1482

3GPP

1483 Release 7 1484 1485

2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942

372

3GPP TS 29.002 V7.5.0 (2006-09)

SendRoutingInfoRes ::= [3] SEQUENCE { imsi [9] IMSI -- IMSI must be present if SendRoutingInfoRes is not segmented. -- If the TC-Result-NL segmentation option is taken the IMSI must be -- present in one segmented transmission of SendRoutingInfoRes. extendedRoutingInfo ExtendedRoutingInfo cug-CheckInfo [3] CUG-CheckInfo cugSubscriptionFlag [6] NULL subscriberInfo [7] SubscriberInfo ss-List [1] SS-List basicService [5] Ext-BasicServiceCode forwardingInterrogationRequired [4] NULL vmsc-Address [2] ISDN-AddressString extensionContainer [0] ExtensionContainer ... , naea-PreferredCI [10] NAEA-PreferredCI -- naea-PreferredCI is included at the discretion of the HLR operator. ccbs-Indicators [11] CCBS-Indicators msisdn [12] ISDN-AddressString numberPortabilityStatus [13] NumberPortabilityStatus istAlertTimer [14] IST-AlertTimerValue supportedCamelPhasesInVMSC [15] SupportedCamelPhases offeredCamel4CSIsInVMSC [16] OfferedCamel4CSIs routingInfo2 [17] RoutingInfo ss-List2 [18] SS-List basicService2 [19] Ext-BasicServiceCode allowedServices [20] AllowedServices unavailabilityCause [21] UnavailabilityCause releaseResourcesSupported [22] NULL gsm-BearerCapability [23] ExternalSignalInfo } AllowedServices ::= BIT STRING { firstServiceAllowed (0), secondServiceAllowed (1) } (SIZE (2..8)) -firstService is the service indicated in the networkSignalInfo -secondService is the service indicated in the networkSignalInfo2 -Other bits than listed above shall be discarded

OPTIONAL,

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

UnavailabilityCause ::= ENUMERATED { bearerServiceNotProvisioned (1), teleserviceNotProvisioned (2), absentSubscriber (3), busySubscriber (4), callBarred (5), cug-Reject (6), ...} -exception handling: -Reception of other values than the ones listed shall result in the service -being unavailable for that call. CCBS-Indicators ::= SEQUENCE { ccbs-Possible keepCCBS-CallIndicator extensionContainer ...} RoutingInfo ::= CHOICE { roamingNumber forwardingData [0] [1] [2] NULL NULL ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL,

ISDN-AddressString, ForwardingData} OPTIONAL,

ForwardingData ::= SEQUENCE { forwardedToNumber [5] ISDN-AddressString -- When this datatype is sent from an HLR which supports CAMEL Phase 2 -- to a GMSC which supports CAMEL Phase 2 the GMSC shall not check the -- format of the number forwardedToSubaddress [4] ISDN-SubaddressString forwardingOptions [6] ForwardingOptions extensionContainer [7] ExtensionContainer ..., longForwardedToNumber [8] FTN-AddressString

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL}

1486

3GPP

1487 Release 7 1488 1489

2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018

373

3GPP TS 29.002 V7.5.0 (2006-09)

ProvideRoamingNumberArg ::= SEQUENCE { imsi [0] IMSI, msc-Number [1] ISDN-AddressString, msisdn [2] ISDN-AddressString lmsi [4] LMSI gsm-BearerCapability [5] ExternalSignalInfo networkSignalInfo [6] ExternalSignalInfo suppressionOfAnnouncement [7] SuppressionOfAnnouncement gmsc-Address [8] ISDN-AddressString callReferenceNumber [9] CallReferenceNumber or-Interrogation [10] NULL extensionContainer [11] ExtensionContainer ... , alertingPattern [12] AlertingPattern ccbs-Call [13] NULL supportedCamelPhasesInInterrogatingNode [15] SupportedCamelPhases additionalSignalInfo [14] Ext-ExternalSignalInfo orNotSupportedInGMSC [16] NULL pre-pagingSupported [17] NULL longFTN-Supported [18] NULL suppress-VT-CSI [19] NULL offeredCamel4CSIsInInterrogatingNode [20] OfferedCamel4CSIs } ProvideRoamingNumberRes ::= SEQUENCE { roamingNumber extensionContainer ..., releaseResourcesSupported ResumeCallHandlingArg ::= SEQUENCE { callReferenceNumber basicServiceGroup forwardingData imsi cug-CheckInfo o-CSI extensionContainer ccbs-Possible msisdn uu-Data allInformationSent ..., d-csi o-BcsmCamelTDPCriteriaList basicServiceGroup2 } UU-Data ::= SEQUENCE { uuIndicator uui uusCFInteraction extensionContainer ...} ISDN-AddressString, ExtensionContainer NULL [0] CallReferenceNumber [1] Ext-BasicServiceCode [2] ForwardingData [3] IMSI [4] CUG-CheckInfo [5] O-CSI [7] ExtensionContainer [8] NULL [9] ISDN-AddressString [10] UU-Data [11] NULL [12] D-CSI [13] O-BcsmCamelTDPCriteriaList [14] Ext-BasicServiceCode

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

[0] [1] [2] [3]

UUIndicator UUI NULL ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

UUIndicator ::= OCTET STRING (SIZE (1)) -- Octets are coded according to ETS 300 356 UUI ::= OCTET STRING (SIZE (1..131)) -- Octets are coded according to ETS 300 356 ExtensionContainer OPTIONAL,

ResumeCallHandlingRes ::= SEQUENCE { extensionContainer ...} CamelInfo ::= SEQUENCE { supportedCamelPhases suppress-T-CSI extensionContainer ... , offeredCamel4CSIs ExtendedRoutingInfo ::= CHOICE { routingInfo camelRoutingInfo

SupportedCamelPhases, NULL ExtensionContainer [0] OfferedCamel4CSIs RoutingInfo, [8] CamelRoutingInfo}

OPTIONAL, OPTIONAL, OPTIONAL }

1490

3GPP

1491 Release 7 1492 1493

3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089

374

3GPP TS 29.002 V7.5.0 (2006-09)

CamelRoutingInfo ::= SEQUENCE { forwardingData gmscCamelSubscriptionInfo extensionContainer ...}

ForwardingData [0] GmscCamelSubscriptionInfo, [1] ExtensionContainer

OPTIONAL, OPTIONAL,

GmscCamelSubscriptionInfo ::= SEQUENCE { t-CSI [0] T-CSI OPTIONAL, o-CSI [1] O-CSI OPTIONAL, extensionContainer [2] ExtensionContainer ..., o-BcsmCamelTDP-CriteriaList [3] O-BcsmCamelTDPCriteriaList t-BCSM-CAMEL-TDP-CriteriaList [4] T-BCSM-CAMEL-TDP-CriteriaList d-csi [5] D-CSI SetReportingStateArg ::= SEQUENCE { imsi lmsi ccbs-Monitoring extensionContainer ...} ReportingState ::= ENUMERATED { stopMonitoring startMonitoring ...} -- exception handling: -- reception of values 2-10 shall be -- reception of values > 10 shall be SetReportingStateRes ::= SEQUENCE{ ccbs-SubscriberStatus extensionContainer ...} [0] [1] [2] [3] IMSI LMSI ReportingState ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL} OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

(0), (1), mapped to 'stopMonitoring' mapped to 'startMonitoring' [0] [1] CCBS-SubscriberStatus ExtensionContainer OPTIONAL, OPTIONAL,

CCBS-SubscriberStatus ::= ENUMERATED { ccbsNotIdle (0), ccbsIdle (1), ccbsNotReachable (2), ...} -- exception handling: -- reception of values 3-10 shall be mapped to 'ccbsNotIdle' -- reception of values 11-20 shall be mapped to 'ccbsIdle' -- reception of values > 20 shall be mapped to 'ccbsNotReachable' StatusReportArg ::= SEQUENCE{ imsi eventReportData callReportdata extensionContainer ...} EventReportData ::= SEQUENCE{ ccbs-SubscriberStatus extensionContainer ...} CallReportData ::= SEQUENCE{ monitoringMode callOutcome extensionContainer ...} [0] [1] [2] [3] IMSI, EventReportData CallReportData ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

[0] [1]

CCBS-SubscriberStatus ExtensionContainer

OPTIONAL, OPTIONAL,

[0] [1] [2]

MonitoringMode CallOutcome ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

MonitoringMode ::= ENUMERATED { a-side (0), b-side (1), ...} -exception handling: -- reception of values 2-10 shall be mapped 'a-side' -- reception of values > 10 shall be mapped to 'b-side'

1494

3GPP

1495 Release 7 1496 1497

3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166

375

3GPP TS 29.002 V7.5.0 (2006-09)

CallOutcome ::= ENUMERATED { success (0), failure (1), busy (2), ...} -exception handling: -- reception of values 3-10 shall be mapped to 'success' -- reception of values 11-20 shall be mapped to 'failure' -- reception of values > 20 shall be mapped to 'busy' StatusReportRes ::= SEQUENCE { extensionContainer ...} RemoteUserFreeArg ::= SEQUENCE{ imsi callInfo ccbs-Feature translatedB-Number replaceB-Number alertingPattern extensionContainer ...} RemoteUserFreeRes ::= SEQUENCE{ ruf-Outcome extensionContainer ...} [0] ExtensionContainer OPTIONAL,

[0] [1] [2] [3] [4] [5] [6]

IMSI, ExternalSignalInfo, CCBS-Feature, ISDN-AddressString, NULL AlertingPattern ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL,

[0] [1]

RUF-Outcome, ExtensionContainer

OPTIONAL,

RUF-Outcome ::= ENUMERATED{ accepted (0), rejected (1), noResponseFromFreeMS (2), -- T4 Expiry noResponseFromBusyMS (3), -- T10 Expiry udubFromFreeMS (4), udubFromBusyMS (5), ...} -- exception handling: -- reception of values 6-20 shall be mapped to 'accepted' -- reception of values 21-30 shall be mapped to 'rejected' -- reception of values 31-40 shall be mapped to 'noResponseFromFreeMS' -- reception of values 41-50 shall be mapped to 'noResponseFromBusyMS' -- reception of values 51-60 shall be mapped to 'udubFromFreeMS' -- reception of values > 60 shall be mapped to 'udubFromBusyMS' IST-AlertArg ::= SEQUENCE{ imsi extensionContainer ...} IST-AlertRes ::= SEQUENCE{ istAlertTimer istInformationWithdraw callTerminationIndicator extensionContainer ...} IST-CommandArg ::= SEQUENCE{ imsi extensionContainer ...} IST-CommandRes ::= SEQUENCE{ extensionContainer ...} CallTerminationIndicator ::= ENUMERATED { terminateCallActivityReferred terminateAllCallActivities ...} -- exception handling: -- reception of values 2-10 shall be -- reception of values > 10 shall be [0] [1] IMSI, ExtensionContainer

OPTIONAL,

[0] [1] [2] [3]

IST-AlertTimerValue NULL CallTerminationIndicator ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

[0] [1]

IMSI, ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

(0), (1), mapped to ' terminateCallActivityReferred ' mapped to ' terminateAllCallActivities '

-- In MSCs not supporting linkage of all call activities, any value received shall -- be interpreted as ' terminateCallActivityReferred '

1498

3GPP

1499 Release 7 1500 1501

3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177

376

3GPP TS 29.002 V7.5.0 (2006-09)

ReleaseResourcesArg ::= SEQUENCE{ msrn extensionContainer ...} ReleaseResourcesRes ::= SEQUENCE{ extensionContainer ...}

ISDN-AddressString, ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

END

3178
3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242

17.7.4 Supplementary service data types

MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RegisterSS-Arg, SS-Info, SS-Status, SS-SubscriptionOption, SS-ForBS-Code, InterrogateSS-Res, USSD-Arg, USSD-Res, USSD-DataCodingScheme, USSD-String, Password, GuidanceInfo, SS-List, SS-InfoList, OverrideCategory, CliRestrictionOption, NoReplyConditionTime, ForwardingOptions, maxNumOfSS, SS-Data, SS-InvocationNotificationArg, SS-InvocationNotificationRes, CCBS-Feature, RegisterCC-EntryArg, RegisterCC-EntryRes, EraseCC-EntryArg, EraseCC-EntryRes ; IMPORTS AddressString, ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString, IMSI, BasicServiceCode, AlertingPattern, EMLPP-Priority, MaxMC-Bearers, MC-Bearers, ExternalSignalInfo FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} SS-Code

1502

3GPP

1503 Release 7 1504 1505

3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300

377

3GPP TS 29.002 V7.5.0 (2006-09)

FROM MAP-SS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version10 (10)} ; RegisterSS-Arg ::= SEQUENCE { ss-Code basicService forwardedToNumber forwardedToSubaddress noReplyConditionTime ..., defaultPriority nbrUser longFTN-Supported NoReplyConditionTime ::= INTEGER (5..30) SS-Info ::= CHOICE { forwardingInfo callBarringInfo ss-Data ForwardingInfo ::= SEQUENCE { ss-Code forwardingFeatureList ...} [0] ForwardingInfo, [1] CallBarringInfo, [3] SS-Data} SS-Code ForwardingFeatureList, OPTIONAL,

SS-Code, BasicServiceCode [4] AddressString [6] ISDN-SubaddressString [5] NoReplyConditionTime [7] EMLPP-Priority [8] MC-Bearers [9] NULL

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

ForwardingFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF ForwardingFeature ForwardingFeature ::= SEQUENCE { basicService ss-Status forwardedToNumber forwardedToSubaddress forwardingOptions noReplyConditionTime ..., longForwardedToNumber SS-Status ::= OCTET STRING (SIZE (1)) -- bits 8765: 0000 (unused) -- bits 4321: Used to convey the "P bit","R bit","A bit" and "Q bit", -representing supplementary service state information -as defined in TS 3GPP TS 23.011 [22] -- bit 4: "Q bit" -- bit 3: "P bit" -- bit 2: "R bit" -- bit 1: "A bit" BasicServiceCode [4] SS-Status [5] ISDN-AddressString [8] ISDN-SubaddressString [6] ForwardingOptions [7] NoReplyConditionTime [9] FTN-AddressString OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

1506

3GPP

1507 Release 7 1508 1509

3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377

378

3GPP TS 29.002 V7.5.0 (2006-09)

ForwardingOptions ::= OCTET STRING (SIZE (1)) -- bit 8: notification to forwarding party -0 no notification -1 notification -- bit 7: redirecting presentation -0 no presentation -1 presentation -- bit 6: notification to calling party -0 no notification -1 notification -- bit 5: 0 (unused) -- bits 43: forwarding reason -00 ms not reachable -01 ms busy -10 no reply -11 unconditional when used in a SRI Result, -or call deflection when used in a RCH Argument -- bits 21: 00 (unused) CallBarringInfo ::= SEQUENCE { ss-Code callBarringFeatureList ...} SS-Code CallBarringFeatureList, OPTIONAL,

CallBarringFeatureList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF CallBarringFeature CallBarringFeature ::= SEQUENCE { basicService ss-Status [4] SS-Status ...} SS-Data ::= SEQUENCE { ss-Code ss-Status ss-SubscriptionOption basicServiceGroupList ..., defaultPriority nbrUser } SS-SubscriptionOption ::= CHOICE { cliRestrictionOption overrideCategory CliRestrictionOption ::= ENUMERATED { permanent (0), temporaryDefaultRestricted (1), temporaryDefaultAllowed (2)} OverrideCategory ::= ENUMERATED { overrideEnabled (0), overrideDisabled (1)} SS-ForBS-Code ::= SEQUENCE { ss-Code basicService ..., longFTN-Supported GenericServiceInfo ::= SEQUENCE { ss-Status SS-Status, cliRestrictionOption ..., maximumEntitledPriority defaultPriority ccbs-FeatureList nbrSB nbrUser nbrSN SS-Code, BasicServiceCode [4] NULL BasicServiceCode OPTIONAL, OPTIONAL,

SS-Code [4] SS-Status SS-SubscriptionOption BasicServiceGroupList EMLPP-Priority [5] MC-Bearers

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

[2] CliRestrictionOption, [1] OverrideCategory}

OPTIONAL, OPTIONAL }

CliRestrictionOption [0] [1] [2] [3] [4] [5] EMLPP-Priority EMLPP-Priority CCBS-FeatureList MaxMC-Bearers MC-Bearers MC-Bearers

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

1510

3GPP

1511 Release 7 1512 1513

3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445

379

3GPP TS 29.002 V7.5.0 (2006-09)

CCBS-FeatureList ::= SEQUENCE SIZE (1..maxNumOfCCBS-Requests) OF CCBS-Feature maxNumOfCCBS-Requests INTEGER ::= 5 [0] [1] [2] [3] CCBS-Index ISDN-AddressString ISDN-SubaddressString BasicServiceCode OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

CCBS-Feature ::= SEQUENCE { ccbs-Index b-subscriberNumber b-subscriberSubaddress basicServiceGroup ...} CCBS-Index

::= INTEGER (1..maxNumOfCCBS-Requests) [0] SS-Status, [2] BasicServiceGroupList, [3] ForwardingFeatureList, [4] GenericServiceInfo } USSD-DataCodingScheme, USSD-String, AlertingPattern [0] ISDN-AddressString USSD-DataCodingScheme, USSD-String, OPTIONAL, OPTIONAL }

InterrogateSS-Res ::= CHOICE { ss-Status basicServiceGroupList forwardingFeatureList genericServiceInfo USSD-Arg ::= SEQUENCE { ussd-DataCodingScheme ussd-String ... , alertingPattern msisdn USSD-Res ::= SEQUENCE { ussd-DataCodingScheme ussd-String ...}

USSD-DataCodingScheme ::= OCTET STRING (SIZE (1)) -- The structure of the USSD-DataCodingScheme is defined by -- the Cell Broadcast Data Coding Scheme as described in -- TS 3GPP TS 23.038 [25] USSD-String ::= OCTET STRING (SIZE (1..maxUSSD-StringLength)) -- The structure of the contents of the USSD-String is dependent -- on the USSD-DataCodingScheme as described in TS 3GPP TS 23.038 [25]. maxUSSD-StringLength INTEGER ::= 160

Password ::= NumericString (FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9")) (SIZE (4)) GuidanceInfo ::= ENUMERATED { enterPW (0), enterNewPW (1), enterNewPW-Again (2)} -- How this information is really delivered to the subscriber -- (display, announcement, ...) is not part of this -- specification. SS-List ::= SEQUENCE SIZE (1..maxNumOfSS) OF SS-Code maxNumOfSS INTEGER ::= 30

SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF SS-Info BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfBasicServiceGroups) OF BasicServiceCode maxNumOfBasicServiceGroups INTEGER ::= 13

1514

3GPP

1515 Release 7 1516 1517

3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515

380

3GPP TS 29.002 V7.5.0 (2006-09)

SS-InvocationNotificationArg ::= SEQUENCE { imsi [0] IMSI, msisdn [1] ISDN-AddressString, ss-Event [2] SS-Code, -- The following SS-Code values are allowed : -- ect SS-Code ::= '00110001'B -- multiPTY SS-Code ::= '01010001'B -- cd SS-Code ::= '00100100'B -- ccbs SS-Code ::= '01000100'B ss-EventSpecification [3] SS-EventSpecification extensionContainer [4] ExtensionContainer ..., b-subscriberNumber [5] ISDN-AddressString ccbs-RequestState [6] CCBS-RequestState } CCBS-RequestState ::= ENUMERATED { request (0), recall (1), active (2), completed (3), suspended (4), frozen (5), deleted (6) } SS-InvocationNotificationRes ::= SEQUENCE { extensionContainer ExtensionContainer ... } SS-EventSpecification ::= SEQUENCE SIZE (1..maxEventSpecification) OF AddressString maxEventSpecification INTEGER ::= 2 [0] [1] SS-Code, CCBS-Data

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

OPTIONAL,

RegisterCC-EntryArg ::= SEQUENCE { ss-Code ccbs-Data ...} CCBS-Data ::= SEQUENCE { ccbs-Feature translatedB-Number serviceIndicator callInfo networkSignalInfo ...}

OPTIONAL,

[0] [1] [2] [3] [4]

CCBS-Feature, ISDN-AddressString, ServiceIndicator ExternalSignalInfo, ExternalSignalInfo,

OPTIONAL,

ServiceIndicator ::= BIT STRING { clir-invoked (0), camel-invoked (1)} (SIZE(2..32)) -- exception handling: -- bits 2 to 31 shall be ignored if received and not understood RegisterCC-EntryRes ::= SEQUENCE { ccbs-Feature ...} EraseCC-EntryArg ::= SEQUENCE { ss-Code ccbs-Index ...} EraseCC-EntryRes ::= SEQUENCE { ss-Code ss-Status ...} END [0] CCBS-Feature OPTIONAL,

[0] [1]

SS-Code, CCBS-Index

OPTIONAL,

[0] SS-Code, [1] SS-Status

OPTIONAL,

3516
3517 3518 3519 3520

17.7.5 Supplementary service codes

MAP-SS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version10 (10)}

1518

3GPP

1519 Release 7 1520 1521

3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587

381

3GPP TS 29.002 V7.5.0 (2006-09)

DEFINITIONS ::= BEGIN SS-Code --------::= OCTET STRING (SIZE (1)) This type is used to represent the code identifying a single supplementary service, a group of supplementary services, or all supplementary services. The services and abbreviations used are defined in TS 3GPP TS 22.004 [5]. The internal structure is defined as follows: bits 87654321: group (bits 8765), and specific service (bits 4321)

allSS SS-Code ::= '00000000'B -- reserved for possible future use -- all SS allLineIdentificationSS SS-Code ::= -- reserved for possible future use -- all line identification SS clip SS-Code ::= -- calling line identification presentation clir SS-Code ::= -- calling line identification restriction colp SS-Code ::= -- connected line identification presentation colr SS-Code ::= -- connected line identification restriction mci SS-Code ::= -- reserved for possible future use -- malicious call identification allNameIdentificationSS -- all name identification SS cnap -- calling name presentation '00010000'B '00010001'B '00010010'B '00010011'B '00010100'B '00010101'B

SS-Code ::= '00011000'B SS-Code ::= '00011001'B

-- SS-Codes '00011010'B to '00011111'B are reserved for future -- NameIdentification Supplementary Service use. allForwardingSS SS-Code ::= '00100000'B -- all forwarding SS cfu SS-Code ::= '00100001'B -- call forwarding unconditional allCondForwardingSS SS-Code ::= '00101000'B -- all conditional forwarding SS cfb SS-Code ::= '00101001'B -- call forwarding on mobile subscriber busy cfnry SS-Code ::= '00101010'B -- call forwarding on no reply cfnrc SS-Code ::= '00101011'B -- call forwarding on mobile subscriber not reachable cd SS-Code ::= '00100100'B -- call deflection allCallOfferingSS SS-Code ::= '00110000'B -- reserved for possible future use -- all call offering SS includes also all forwarding SS ect SS-Code ::= '00110001'B -- explicit call transfer mah SS-Code ::= '00110010'B -- reserved for possible future use -- mobile access hunting

1522

3GPP

1523 Release 7 1524 1525

3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651

382

3GPP TS 29.002 V7.5.0 (2006-09)

allCallCompletionSS SS-Code ::= '01000000'B -- reserved for possible future use -- all Call completion SS cw SS-Code ::= '01000001'B -- call waiting hold SS-Code ::= '01000010'B -- call hold ccbs-A SS-Code ::= '01000011'B -- completion of call to busy subscribers, originating side ccbs-B SS-Code ::= '01000100'B -- completion of call to busy subscribers, destination side -- this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData mc SS-Code ::= '01000101'B -- multicall allMultiPartySS SS-Code ::= '01010000'B -- reserved for possible future use -- all multiparty SS multiPTY SS-Code ::= '01010001'B -- multiparty allCommunityOfInterest-SS SS-Code ::= '01100000'B -- reserved for possible future use -- all community of interest SS cug SS-Code ::= '01100001'B -- closed user group allChargingSS SS-Code ::= '01110000'B -- reserved for possible future use -- all charging SS aoci SS-Code ::= '01110001'B -- advice of charge information aocc SS-Code ::= '01110010'B -- advice of charge charging allAdditionalInfoTransferSS SS-Code -- reserved for possible future use -- all additional information transfer SS uus1 SS-Code -- UUS1 user-to-user signalling uus2 SS-Code -- UUS2 user-to-user signalling uus3 SS-Code -- UUS3 user-to-user signalling ::= '10000000'B ::= '10000001'B ::= '10000010'B ::= '10000011'B

allBarringSS SS-Code ::= '10010000'B -- all barring SS barringOfOutgoingCalls SS-Code ::= '10010001'B -- barring of outgoing calls baoc SS-Code ::= '10010010'B -- barring of all outgoing calls boic SS-Code ::= '10010011'B -- barring of outgoing international calls boicExHC SS-Code ::= '10010100'B -- barring of outgoing international calls except those directed -- to the home PLMN Country barringOfIncomingCalls SS-Code ::= '10011001'B -- barring of incoming calls baic SS-Code ::= '10011010'B -- barring of all incoming calls bicRoam SS-Code ::= '10011011'B -- barring of incoming calls when roaming outside home PLMN -- Country

1526

3GPP

1527 Release 7 1528 1529

3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699

383
SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code SS-Code ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= '11110000'B '11110001'B '11110010'B '11110011'B '11110100'B '11110101'B '11110110'B '11110111'B '11111000'B '11111001'B '11111010'B '11111011'B '11111100'B '11111101'B '11111110'B '11111111'B

3GPP TS 29.002 V7.5.0 (2006-09)

allPLMN-specificSS plmn-specificSS-1 plmn-specificSS-2 plmn-specificSS-3 plmn-specificSS-4 plmn-specificSS-5 plmn-specificSS-6 plmn-specificSS-7 plmn-specificSS-8 plmn-specificSS-9 plmn-specificSS-A plmn-specificSS-B plmn-specificSS-C plmn-specificSS-D plmn-specificSS-E plmn-specificSS-F

allCallPrioritySS SS-Code ::= '10100000'B -- reserved for possible future use -- all call priority SS emlpp SS-Code ::= '10100001'B -- enhanced Multilevel Precedence Pre-emption (EMLPP) service allLCSPrivacyException SS-Code ::= '10110000'B -- all LCS Privacy Exception Classes universal SS-Code ::= '10110001'B -- allow location by any LCS client callSessionRelated SS-Code ::= '10110010'B -- allow location by any value added LCS client to which a call/session -- is established from the target MS callSessionUnrelated SS-Code ::= '10110011'B -- allow location by designated external value added LCS clients plmnoperator SS-Code ::= '10110100'B -- allow location by designated PLMN operator LCS clients serviceType SS-Code ::= '10110101'B -- allow location by LCS clients of a designated LCS service type allMOLR-SS SS-Code ::= '11000000'B -- all Mobile Originating Location Request Classes basicSelfLocation SS-Code ::= '11000001'B -- allow an MS to request its own location autonomousSelfLocation SS-Code ::= '11000010'B -- allow an MS to perform self location without interaction -- with the PLMN for a predetermined period of time transferToThirdParty SS-Code ::= '11000011'B -- allow an MS to request transfer of its location to another LCS client END

3700
3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727

17.7.6 Short message data types

MAP-SM-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RoutingInfoForSM-Arg, RoutingInfoForSM-Res, MO-ForwardSM-Arg, MO-ForwardSM-Res, MT-ForwardSM-Arg, MT-ForwardSM-Res, ReportSM-DeliveryStatusArg, ReportSM-DeliveryStatusRes, AlertServiceCentreArg, InformServiceCentreArg, ReadyForSM-Arg, ReadyForSM-Res, SM-DeliveryOutcome, AlertReason,

1530

3GPP

1531 Release 7 1532 1533

3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799

384

3GPP TS 29.002 V7.5.0 (2006-09)

Additional-Number, MT-ForwardSM-VGCS-Arg, MT-ForwardSM-VGCS-Res

IMPORTS AddressString, ISDN-AddressString, SignalInfo, IMSI, LMSI, ASCI-CallReference FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ; RoutingInfoForSM-Arg ::= SEQUENCE { msisdn [0] ISDN-AddressString, sm-RP-PRI [1] BOOLEAN, serviceCentreAddress [2] AddressString, extensionContainer [6] ExtensionContainer ... , gprsSupportIndicator [7] NULL -- gprsSupportIndicator is set only if the SMS-GMSC supports -- receiving of two numbers from the HLR sm-RP-MTI [8] SM-RP-MTI sm-RP-SMEA [9] SM-RP-SMEA SM-RP-MTI ::= INTEGER (0..10) -- 0 SMS Deliver -- 1 SMS Status Report -- other values are reserved for future use and shall be discarded if -- received SM-RP-SMEA ::= OCTET STRING (SIZE (1..12)) -- this parameter contains an address field which is encoded -- as defined in 3GPP TS 23.040. An address field contains 3 elements : -address-length -type-of-address -address-value RoutingInfoForSM-Res ::= SEQUENCE { imsi locationInfoWithLMSI extensionContainer ...} LocationInfoWithLMSI ::= SEQUENCE { networkNode-Number lmsi extensionContainer ..., gprsNodeIndicator -- gprsNodeIndicator is set only if -- Network Node Number additional-Number -- NetworkNode-number can be either } IMSI, [0] LocationInfoWithLMSI, [4] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

OPTIONAL,

[1] ISDN-AddressString, LMSI ExtensionContainer [5] NULL the SGSN number is sent as the [6] Additional-Number msc-number or sgsn-number

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

1534

3GPP

1535 Release 7 1536 1537

3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873

385

3GPP TS 29.002 V7.5.0 (2006-09)

Additional-Number ::= CHOICE { msc-Number [0] ISDN-AddressString, sgsn-Number [1] ISDN-AddressString} -- additional-number can be either msc-number or sgsn-number -- if received networkNode-number is msc-number then the -- additional number is sgsn-number -- if received networkNode-number is sgsn-number then the -- additional number is msc-number MO-ForwardSM-Arg ::= SEQUENCE { sm-RP-DA sm-RP-OA sm-RP-UI extensionContainer ... , imsi MO-ForwardSM-Res ::= SEQUENCE { sm-RP-UI extensionContainer ...} MT-ForwardSM-Arg ::= SEQUENCE { sm-RP-DA sm-RP-OA sm-RP-UI moreMessagesToSend extensionContainer ...} MT-ForwardSM-Res ::= SEQUENCE { sm-RP-UI extensionContainer ...} SM-RP-DA ::= CHOICE { imsi lmsi serviceCentreAddressDA noSM-RP-DA SM-RP-OA ::= CHOICE { msisdn serviceCentreAddressOA noSM-RP-OA SM-RP-DA, SM-RP-OA, SignalInfo, ExtensionContainer IMSI SignalInfo ExtensionContainer

OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL,

SM-RP-DA, SM-RP-OA, SignalInfo, NULL ExtensionContainer

OPTIONAL, OPTIONAL,

SignalInfo ExtensionContainer

OPTIONAL, OPTIONAL,

[0] [1] [4] [5]

IMSI, LMSI, AddressString, NULL}

[2] ISDN-AddressString, [4] AddressString, [5] NULL}

ReportSM-DeliveryStatusArg ::= SEQUENCE { msisdn ISDN-AddressString, serviceCentreAddress AddressString, sm-DeliveryOutcome SM-DeliveryOutcome, absentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM

OPTIONAL, extensionContainer [1] ExtensionContainer OPTIONAL, ..., gprsSupportIndicator [2] NULL OPTIONAL, -- gprsSupportIndicator is set only if the SMS-GMSC supports -- handling of two delivery outcomes deliveryOutcomeIndicator [3] NULL OPTIONAL, -- DeliveryOutcomeIndicator is set when the SM-DeliveryOutcome -- is for GPRS additionalSM-DeliveryOutcome [4] SM-DeliveryOutcome OPTIONAL, -- If received, additionalSM-DeliveryOutcome is for GPRS -- If DeliveryOutcomeIndicator is set, then AdditionalSM-DeliveryOutcome shall be absent additionalAbsentSubscriberDiagnosticSM [5] AbsentSubscriberDiagnosticSM OPTIONAL -- If received additionalAbsentSubscriberDiagnosticSM is for GPRS -- If DeliveryOutcomeIndicator is set, then AdditionalAbsentSubscriberDiagnosticSM -- shall be absent }

SM-DeliveryOutcome ::= ENUMERATED { memoryCapacityExceeded (0), absentSubscriber (1), successfulTransfer (2)}

1538

3GPP

1539 Release 7 1540 1541

3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943

386

3GPP TS 29.002 V7.5.0 (2006-09)

ReportSM-DeliveryStatusRes ::= SEQUENCE { storedMSISDN ISDN-AddressString extensionContainer ExtensionContainer ...} AlertServiceCentreArg ::= SEQUENCE { msisdn serviceCentreAddress ...} ISDN-AddressString, AddressString,

OPTIONAL, OPTIONAL,

InformServiceCentreArg ::= SEQUENCE { storedMSISDN ISDN-AddressString OPTIONAL, mw-Status MW-Status OPTIONAL, extensionContainer ExtensionContainer OPTIONAL, ... , absentSubscriberDiagnosticSM AbsentSubscriberDiagnosticSM OPTIONAL, additionalAbsentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM OPTIONAL } -- additionalAbsentSubscriberDiagnosticSM may be present only if -- absentSubscriberDiagnosticSM is present. -- if included, additionalAbsentSubscriberDiagnosticSM is for GPRS and -- absentSubscriberDiagnosticSM is for non-GPRS MW-Status ::= BIT STRING { sc-AddressNotIncluded (0), mnrf-Set (1), mcef-Set (2) , mnrg-Set (3)} (SIZE (6..16)) -- exception handling: -- bits 4 to 15 shall be ignored if received and not understood ReadyForSM-Arg ::= SEQUENCE { imsi [0] IMSI, alertReason AlertReason, alertReasonIndicator NULL -- alertReasonIndicator is set only when the alertReason -- sent to HLR is for GPRS extensionContainer ExtensionContainer ...} ReadyForSM-Res ::= SEQUENCE { extensionContainer ...} AlertReason ::= ENUMERATED { ms-Present (0), memoryAvailable (1)} MT-ForwardSM-VGCS-Arg ::= SEQUENCE { asciCallReference sm-RP-OA sm-RP-UI extensionContainer ...} MT-ForwardSM-VGCS-Res ::= SEQUENCE { sm-RP-UI dispatcherList ongoingCall extensionContainer ...} ASCI-CallReference, SM-RP-OA, SignalInfo, ExtensionContainer ExtensionContainer

OPTIONAL, OPTIONAL,

OPTIONAL,

OPTIONAL,

[0] SignalInfo [1] DispatcherList NULL [2] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

DispatcherList ::= SEQUENCE SIZE (1..maxNumOfDispatchers) OF ISDN-AddressString maxNumOfDispatchers INTEGER ::= 5

END

3944
3945 3946 3947 3948

17.7.7 Error data types

MAP-ER-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version10 (10)}

1542

3GPP

1543 Release 7 1544 1545

3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027

387

3GPP TS 29.002 V7.5.0 (2006-09)

DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RoamingNotAllowedParam, CallBarredParam, CUG-RejectParam, SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, OR-NotAllowedParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam, TracingBufferFullParam, NoRoamingNbParam, AbsentSubscriberParam, BusySubscriberParam, NoSubscriberReplyParam, ForwardingViolationParam, ForwardingFailedParam, ATI-NotAllowedParam, SubBusyForMT-SMS-Param, MessageWaitListFullParam, AbsentSubscriberSM-Param, AbsentSubscriberDiagnosticSM, ResourceLimitationParam, NoGroupCallNbParam, IncompatibleTerminalParam, ShortTermDenialParam, LongTermDenialParam, UnauthorizedRequestingNetwork-Param, UnauthorizedLCSClient-Param, PositionMethodFailure-Param, UnknownOrUnreachableLCSClient-Param, MM-EventNotSupported-Param, ATSI-NotAllowedParam, ATM-NotAllowedParam, IllegalSS-OperationParam, SS-NotAvailableParam, SS-SubscriptionViolationParam, InformationNotAvailableParam, TargetCellOutsideGCA-Param, OngoingGroupCallParam ; IMPORTS SS-Status FROM MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} SignalInfo, BasicServiceCode, NetworkResource, AdditionalNetworkResource FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} SS-Code FROM MAP-SS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version10 (10)}

1546

3GPP

1547 Release 7 1548 1549

4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099

388

3GPP TS 29.002 V7.5.0 (2006-09)

ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ; RoamingNotAllowedParam ::= SEQUENCE { roamingNotAllowedCause extensionContainer ..., additionalRoamingNotAllowedCause --RoamingNotAllowedCause, ExtensionContainer

OPTIONAL,

[0] AdditionalRoamingNotAllowedCause OPTIONAL }

if the additionalRoamingNotallowedCause is received by the MSC/VLR or SGSN then the roamingNotAllowedCause shall be discarded.

AdditionalRoamingNotAllowedCause ::= ENUMERATED { supportedRAT-TypesNotAllowed (0), ...} RoamingNotAllowedCause ::= ENUMERATED { plmnRoamingNotAllowed (0), operatorDeterminedBarring (3)} CallBarredParam ::= CHOICE { callBarringCause CallBarringCause, -- call BarringCause must not be used in version 3 and higher extensibleCallBarredParam ExtensibleCallBarredParam -- extensibleCallBarredParam must not be used in version <3 } CallBarringCause ::= ENUMERATED { barringServiceActive (0), operatorBarring (1)} ExtensibleCallBarredParam ::= SEQUENCE { callBarringCause extensionContainer ... , unauthorisedMessageOriginator CUG-RejectParam ::= SEQUENCE { cug-RejectCause extensionContainer ...} CallBarringCause ExtensionContainer [1] NULL CUG-RejectCause ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL,

CUG-RejectCause ::= ENUMERATED { incomingCallsBarredWithinCUG (0), subscriberNotMemberOfCUG (1), requestedBasicServiceViolatesCUG-Constraints calledPartySS-InteractionViolation (7)} SS-IncompatibilityCause ::= SEQUENCE { ss-Code basicService ss-Status ...}

(5),

[1] SS-Code BasicServiceCode [4] SS-Status

OPTIONAL, OPTIONAL, OPTIONAL,

PW-RegistrationFailureCause ::= ENUMERATED { undetermined (0), invalidFormat (1), newPasswordsMismatch (2)} SM-EnumeratedDeliveryFailureCause ::= ENUMERATED { memoryCapacityExceeded (0), equipmentProtocolError (1), equipmentNotSM-Equipped (2), unknownServiceCentre (3), sc-Congestion (4), invalidSME-Address (5), subscriberNotSC-Subscriber (6)}

1550

3GPP

1551 Release 7 1552 1553

4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175

389

3GPP TS 29.002 V7.5.0 (2006-09)

SM-DeliveryFailureCause ::= SEQUENCE { sm-EnumeratedDeliveryFailureCause diagnosticInfo extensionContainer ...}

SM-EnumeratedDeliveryFailureCause, SignalInfo OPTIONAL, ExtensionContainer OPTIONAL,

AbsentSubscriberSM-Param ::= SEQUENCE { absentSubscriberDiagnosticSM AbsentSubscriberDiagnosticSM OPTIONAL, -- AbsentSubscriberDiagnosticSM can be either for non-GPRS -- or for GPRS extensionContainer ExtensionContainer OPTIONAL, ..., additionalAbsentSubscriberDiagnosticSM [0] AbsentSubscriberDiagnosticSM OPTIONAL } -- if received, additionalAbsentSubscriberDiagnosticSM -- is for GPRS and absentSubscriberDiagnosticSM is -- for non-GPRS AbsentSubscriberDiagnosticSM ::= INTEGER (0..255) -- AbsentSubscriberDiagnosticSM values are defined in 3GPP TS 23.040 SystemFailureParam ::= CHOICE { networkResource NetworkResource, -- networkResource must not be used in version 3 extensibleSystemFailureParam ExtensibleSystemFailureParam -- extensibleSystemFailureParam must not be used in version <3 } ExtensibleSystemFailureParam ::= SEQUENCE { networkResource NetworkResource extensionContainer ExtensionContainer ..., additionalNetworkResource [0] AdditionalNetworkResource DataMissingParam ::= SEQUENCE { extensionContainer ...} UnexpectedDataParam ::= SEQUENCE { extensionContainer ...} ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL } OPTIONAL,

ExtensionContainer

OPTIONAL,

FacilityNotSupParam ::= SEQUENCE { extensionContainer ExtensionContainer ..., shapeOfLocationEstimateNotSupported [0] NULL neededLcsCapabilityNotSupportedInServingNode [1] NULL OR-NotAllowedParam ::= SEQUENCE { extensionContainer ...} UnknownSubscriberParam ::= SEQUENCE { extensionContainer ..., unknownSubscriberDiagnostic ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL } OPTIONAL,

ExtensionContainer UnknownSubscriberDiagnostic

OPTIONAL, OPTIONAL}

UnknownSubscriberDiagnostic ::= ENUMERATED { imsiUnknown (0), gprsSubscriptionUnknown (1), ..., npdbMismatch (2)} -- if unknown values are received in -- UnknownSubscriberDiagnostic they shall be discarded NumberChangedParam ::= SEQUENCE { extensionContainer ...} UnidentifiedSubParam ::= SEQUENCE { extensionContainer ...} IllegalSubscriberParam ::= SEQUENCE { extensionContainer ...} ExtensionContainer OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

1554

3GPP

1555 Release 7 1556 1557

4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251

390

3GPP TS 29.002 V7.5.0 (2006-09)

IllegalEquipmentParam ::= SEQUENCE { extensionContainer ...} BearerServNotProvParam ::= SEQUENCE { extensionContainer ...} TeleservNotProvParam ::= SEQUENCE { extensionContainer ...} TracingBufferFullParam ::= SEQUENCE { extensionContainer ...} NoRoamingNbParam ::= SEQUENCE { extensionContainer ...} AbsentSubscriberParam ::= SEQUENCE { extensionContainer ..., absentSubscriberReason

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer [0] AbsentSubscriberReason

OPTIONAL, OPTIONAL}

AbsentSubscriberReason ::= ENUMERATED { imsiDetach (0), restrictedArea (1), noPageResponse (2), ... , purgedMS (3)} -- exception handling: at reception of other values than the ones listed the -- AbsentSubscriberReason shall be ignored. -- The AbsentSubscriberReason: purgedMS is defined for the Super-Charger feature -- (see TS 23.116). If this value is received in a Provide Roaming Number response -- it shall be mapped to the AbsentSubscriberReason: imsiDetach in the Send Routeing -- Information response BusySubscriberParam ::= SEQUENCE { extensionContainer ..., ccbs-Possible ccbs-Busy NoSubscriberReplyParam ::= SEQUENCE { extensionContainer ...} ForwardingViolationParam ::= SEQUENCE { extensionContainer ...} ForwardingFailedParam ::= SEQUENCE { extensionContainer ...} ATI-NotAllowedParam ::= SEQUENCE { extensionContainer ...} ATSI-NotAllowedParam ::= SEQUENCE { extensionContainer ...} ATM-NotAllowedParam ::= SEQUENCE { extensionContainer ...} IllegalSS-OperationParam ::= SEQUENCE { extensionContainer ...} SS-NotAvailableParam ::= SEQUENCE { extensionContainer ...} ExtensionContainer [0] NULL [1] NULL ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL} OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

1558

3GPP

1559 Release 7 1560 1561

4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315

391

3GPP TS 29.002 V7.5.0 (2006-09)

SS-SubscriptionViolationParam ::= SEQUENCE { extensionContainer ExtensionContainer ...} InformationNotAvailableParam ::= SEQUENCE { extensionContainer ExtensionContainer ...} SubBusyForMT-SMS-Param ::= SEQUENCE { extensionContainer ExtensionContainer ... , gprsConnectionSuspended NULL -- If GprsConnectionSuspended is not understood it shall -- be discarded MessageWaitListFullParam ::= SEQUENCE { extensionContainer ...} ResourceLimitationParam ::= SEQUENCE { extensionContainer ...} NoGroupCallNbParam ::= SEQUENCE { extensionContainer ...} IncompatibleTerminalParam ::= SEQUENCE { extensionContainer ...} ShortTermDenialParam ::= SEQUENCE { ...} LongTermDenialParam ::= SEQUENCE { ...} UnauthorizedRequestingNetwork-Param ::= SEQUENCE { extensionContainer ExtensionContainer ...} ExtensionContainer

OPTIONAL,

OPTIONAL,

OPTIONAL, OPTIONAL }

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

ExtensionContainer

OPTIONAL,

OPTIONAL,

UnauthorizedLCSClient-Param ::= SEQUENCE { unauthorizedLCSClient-Diagnostic [0] UnauthorizedLCSClient-Diagnostic extensionContainer [1] ExtensionContainer ... } UnauthorizedLCSClient-Diagnostic ::= ENUMERATED { noAdditionalInformation (0), clientNotInMSPrivacyExceptionList (1), callToClientNotSetup (2), privacyOverrideNotApplicable (3), disallowedByLocalRegulatoryRequirements (4), ..., unauthorizedPrivacyClass (5), unauthorizedCallSessionUnrelatedExternalClient (6), unauthorizedCallSessionRelatedExternalClient (7) } -exception handling: -any unrecognized value shall be ignored PositionMethodFailure-Param ::= SEQUENCE { positionMethodFailure-Diagnostic [0] PositionMethodFailure-Diagnostic extensionContainer [1] ExtensionContainer ... }

OPTIONAL, OPTIONAL,

OPTIONAL, OPTIONAL,

1562

3GPP

1563 Release 7 1564 1565

4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347

392

3GPP TS 29.002 V7.5.0 (2006-09)

PositionMethodFailure-Diagnostic ::= ENUMERATED { congestion (0), insufficientResources (1), insufficientMeasurementData (2), inconsistentMeasurementData (3), locationProcedureNotCompleted (4), locationProcedureNotSupportedByTargetMS (5), qoSNotAttainable (6), positionMethodNotAvailableInNetwork (7), positionMethodNotAvailableInLocationArea (8), ... } -exception handling: -any unrecognized value shall be ignored UnknownOrUnreachableLCSClient-Param ::= SEQUENCE { extensionContainer ExtensionContainer ...} MM-EventNotSupported-Param ::= SEQUENCE { extensionContainer ExtensionContainer ...} TargetCellOutsideGCA-Param ::= SEQUENCE { extensionContainer ExtensionContainer ...} OngoingGroupCallParam ::= SEQUENCE { extensionContainer ...} ExtensionContainer OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

END

4348
4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390

17.7.8 Common data types

MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS -- general data types and values AddressString, ISDN-AddressString, maxISDN-AddressLength, FTN-AddressString, ISDN-SubaddressString, ExternalSignalInfo, Ext-ExternalSignalInfo, AccessNetworkSignalInfo, SignalInfo, maxSignalInfoLength, AlertingPattern, TBCD-STRING, -- data types for numbering and identification IMSI, TMSI, Identity, SubscriberId, IMEI, HLR-List, LMSI, GlobalCellId, NetworkResource, AdditionalNetworkResource, NAEA-PreferredCI, NAEA-CIC, ASCI-CallReference,

1566

3GPP

1567 Release 7 1568 1569

4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452

393

3GPP TS 29.002 V7.5.0 (2006-09)

SubscriberIdentity, PLMN-Id, -- data types for CAMEL CellGlobalIdOrServiceAreaIdOrLAI, CellGlobalIdOrServiceAreaIdFixedLength, LAIFixedLength, -- data types for subscriber management BasicServiceCode, Ext-BasicServiceCode, EMLPP-Info, EMLPP-Priority, MC-SS-Info, MaxMC-Bearers, MC-Bearers, Ext-SS-Status, -- data types for geographic location AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, LCSServiceTypeID

IMPORTS TeleserviceCode, Ext-TeleserviceCode FROM MAP-TS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version10 (10)} BearerServiceCode, Ext-BearerServiceCode FROM MAP-BS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version10 (10)} SS-Code FROM MAP-SS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ; -- general data types TBCD-STRING ::= OCTET STRING -- This type (Telephony Binary Coded Decimal String) is used to -- represent several digits from 0 through 9, *, #, a, b, c, two -- digits per octet, each digit encoded 0000 to 1001 (0 to 9), -- 1010 (*), 1011 (#), 1100 (a), 1101 (b) or 1110 (c); 1111 used -- as filler when there is an odd number of digits. -- bits 8765 of octet n encoding digit 2n -- bits 4321 of octet n encoding digit 2(n-1) +1

1570

3GPP

1571 Release 7 1572 1573

4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510

394

3GPP TS 29.002 V7.5.0 (2006-09)

AddressString ::= OCTET STRING (SIZE (1..maxAddressLength)) -- This type is used to represent a number for addressing -- purposes. It is composed of -a) one octet for nature of address, and numbering plan -indicator. -b) digits of an address encoded as TBCD-String. -- a) --The first octet includes a one bit extension indicator, a 3 bits nature of address indicator and a 4 bits numbering plan indicator, encoded as follows: (no extension)

-- bit 8: 1

-- bits 765: nature of address indicator -000 unknown -001 international number -010 national significant number -011 network specific number -100 subscriber number -101 reserved -110 abbreviated number -111 reserved for extension -- bits 4321: numbering plan indicator -0000 unknown -0001 ISDN/Telephony Numbering Plan (Rec ITU-T E.164) -0010 spare -0011 data numbering plan (ITU-T Rec X.121) -0100 telex numbering plan (ITU-T Rec F.69) -0101 spare -0110 land mobile numbering plan (ITU-T Rec E.212) -0111 spare -1000 national numbering plan -1001 private numbering plan -1111 reserved for extension -all other values are reserved. The following octets representing digits of an address encoded as a TBCD-STRING. INTEGER ::= 20

-- b) --

maxAddressLength

ISDN-AddressString ::= AddressString (SIZE (1..maxISDN-AddressLength)) -- This type is used to represent ISDN numbers. maxISDN-AddressLength INTEGER ::= 9

FTN-AddressString ::= AddressString (SIZE (1..maxFTN-AddressLength)) -- This type is used to represent forwarded-to numbers. -- For long forwarded-to numbers (longer than 15 digits) NPI shall be unknown; -- if NAI = international the first digits represent the country code (CC) -- and the network destination code (NDC) as for E.164. maxFTN-AddressLength INTEGER ::= 15

1574

3GPP

1575 Release 7 1576 1577

4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584

395

3GPP TS 29.002 V7.5.0 (2006-09)

ISDN-SubaddressString ::= OCTET STRING (SIZE (1..maxISDN-SubaddressLength)) -- This type is used to represent ISDN subaddresses. -- It is composed of -a) one octet for type of subaddress and odd/even indicator. -b) 20 octets for subaddress information. ------------------------a) The first octet includes a one bit extension indicator, a 3 bits type of subaddress and a one bit odd/even indicator, encoded as follows: (no extension) of subaddress (X.213/ISO 8348 AD2) Specified values are reserved

bit 8: 1

bits 765: type 000 NSAP 010 User All other

bit 4: odd/even indicator 0 even number of address signals 1 odd number of address signals The odd/even indicator is used when the type of subaddress is "user specified" and the coding is BCD. bits 321: 000 (unused) b) Subaddress information. The NSAP X.213/ISO8348AD2 address shall be formatted as specified by octet 4 which contains the Authority and Format Identifier (AFI). The encoding is made according to the "preferred binary encoding" as defined in X.213/ISO834AD2. For the definition of this type of subaddress, see ITU-T Rec I.334. For User-specific subaddress, this field is encoded according to the user specification, subject to a maximum length of 20 octets. When interworking with X.25 networks BCD coding should be applied. INTEGER ::= 21

maxISDN-SubaddressLength

ExternalSignalInfo ::= SEQUENCE { protocolId ProtocolId, signalInfo SignalInfo, -- Information about the internal structure is given in -- clause 7.6.9. extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 ...} SignalInfo ::= OCTET STRING (SIZE (1..maxSignalInfoLength))

OPTIONAL,

maxSignalInfoLength INTEGER ::= 200 -- This NamedValue represents the theoretical maximum number of octets which is -- available to carry a single instance of the SignalInfo data type, -- without requiring segmentation to cope with the network layer service. -- However, the actual maximum size available for an instance of the data -- type may be lower, especially when other information elements -- have to be included in the same component. ProtocolId ::= ENUMERATED { gsm-0408 (1), gsm-0806 (2), gsm-BSSMAP (3), -- Value 3 is reserved and must not be used ets-300102-1 (4)} Ext-ExternalSignalInfo ::= SEQUENCE { ext-ProtocolId Ext-ProtocolId, signalInfo SignalInfo, -- Information about the internal structure is given in -- clause 7.6.9.10 extensionContainer ExtensionContainer ...}

OPTIONAL,

1578

3GPP

1579 Release 7 1580 1581

4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661

396

3GPP TS 29.002 V7.5.0 (2006-09)

Ext-ProtocolId ::= ENUMERATED { ets-300356 (1), ... } -- exception handling: -- For Ext-ExternalSignalInfo sequences containing this parameter with any -- other value than the ones listed the receiver shall ignore the whole -- Ext-ExternalSignalInfo sequence. AccessNetworkSignalInfo ::= SEQUENCE { accessNetworkProtocolId AccessNetworkProtocolId, signalInfo LongSignalInfo, -- Information about the internal structure is given in clause 7.6.9.1 extensionContainer ...} ExtensionContainer OPTIONAL,

LongSignalInfo ::= OCTET STRING (SIZE (1..maxLongSignalInfoLength)) maxLongSignalInfoLength INTEGER ::= 2560 -- This Named Value represents the maximum number of octets which is available -- to carry a single instance of the LongSignalInfo data type using -- White Book SCCP with the maximum number of segments. -- It takes account of the octets used by the lower layers of the protocol, and -- other information elements which may be included in the same component. AccessNetworkProtocolId ::= ENUMERATED { ts3G-48006 (1), ts3G-25413 (2), ...} -- exception handling: -- For AccessNetworkSignalInfo sequences containing this parameter with any -- other value than the ones listed the receiver shall ignore the whole -- AccessNetworkSignalInfo sequence. AlertingPattern ::= OCTET STRING (SIZE (1) ) -- This type is used to represent Alerting Pattern -------bits 8765 : 0000 (unused) bits 43 : type of Pattern 00 level 01 category 10 category all other values are reserved. bits 21 : type of alerting

alertingLevel-0 AlertingPattern ::= '00000000'B alertingLevel-1 AlertingPattern ::= '00000001'B alertingLevel-2 AlertingPattern ::= '00000010'B -- all other values of Alerting level are reserved -- Alerting Levels are defined in GSM 02.07 alertingCategory-1 AlertingPattern ::= '00000100'B alertingCategory-2 AlertingPattern ::= '00000101'B alertingCategory-3 AlertingPattern ::= '00000110'B alertingCategory-4 AlertingPattern ::= '00000111'B alertingCategory-5 AlertingPattern ::= '00001000'B -- all other values of Alerting Category are reserved -- Alerting categories are defined in GSM 02.07 -- data types for numbering and identification IMSI ::= TBCD-STRING (SIZE (3..8)) -- digits of MCC, MNC, MSIN are concatenated in this order. Identity ::= CHOICE { imsi imsi-WithLMSI IMSI, IMSI-WithLMSI}

IMSI-WithLMSI ::= SEQUENCE { imsi IMSI, lmsi LMSI, -- a special value 00000000 indicates that the LMSI is not in use ...}

1582

3GPP

1583 Release 7 1584 1585

4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737

397

3GPP TS 29.002 V7.5.0 (2006-09)

ASCI-CallReference ::= TBCD-STRING (SIZE (1..8)) -- digits of VGCS/VBC-area,Group-ID are concatenated in this order. TMSI ::= OCTET STRING (SIZE (1..4)) SubscriberId ::= CHOICE { imsi tmsi IMEI ::= -----[0] IMSI, [1] TMSI}

TBCD-STRING (SIZE (8)) Refers to International Mobile Station Equipment Identity and Software Version Number (SVN) defined in TS 3GPP TS 23.003 [17]. If the SVN is not present the last octet shall contain the digit 0 and a filler. If present the SVN shall be included in the last octet.

HLR-Id ::= IMSI -- leading digits of IMSI, i.e. (MCC, MNC, leading digits of -- MSIN) forming HLR Id defined in TS 3GPP TS 23.003 [17]. HLR-List ::= SEQUENCE SIZE (1..maxNumOfHLR-Id) OF HLR-Id maxNumOfHLR-Id INTEGER ::= 50

LMSI ::= OCTET STRING (SIZE (4)) GlobalCellId ::= OCTET STRING (SIZE (5..7)) -- Refers to Cell Global Identification defined in TS 3GPP TS 23.003 [17]. -- The internal structure is defined as follows: -- octet 1 bits 4321 Mobile Country Code 1st digit -bits 8765 Mobile Country Code 2nd digit -- octet 2 bits 4321 Mobile Country Code 3rd digit -bits 8765 Mobile Network Code 3rd digit -or filler (1111) for 2 digit MNCs -- octet 3 bits 4321 Mobile Network Code 1st digit -bits 8765 Mobile Network Code 2nd digit -- octets 4 and 5 Location Area Code according to TS 3GPP TS 24.008 [35] -- octets 6 and 7 Cell Identity (CI) according to TS 3GPP TS 24.008 [35] NetworkResource ::= ENUMERATED { plmn (0), hlr (1), vlr (2), pvlr (3), controllingMSC (4), vmsc (5), eir (6), rss (7)} AdditionalNetworkResource ::= ENUMERATED { sgsn (0), ggsn (1), gmlc (2), gsmSCF (3), nplr (4), auc (5), ...} -- if unknown value is received in AdditionalNetworkResource -- it shall be ignored. NAEA-PreferredCI ::= SEQUENCE { naea-PreferredCIC extensionContainer ...}

[0] NAEA-CIC, [1] ExtensionContainer

OPTIONAL,

NAEA-CIC ::= OCTET STRING (SIZE (3)) -- The internal structure is defined by the Carrier Identification -- parameter in ANSI T1.113.3. Carrier codes between 000 and 999 may -- be encoded as 3 digits using 000 to 999 or as 4 digits using -- 0000 to 0999. Carrier codes between 1000 and 9999 are encoded -- using 4 digits.

1586

3GPP

1587 Release 7 1588 1589

4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786

398

3GPP TS 29.002 V7.5.0 (2006-09)

SubscriberIdentity ::= CHOICE { imsi msisdn } LCSClientExternalID ::= SEQUENCE { externalAddress extensionContainer ... }

[0] IMSI, [1] ISDN-AddressString

[0] ISDN-AddressString [1] ExtensionContainer

OPTIONAL, OPTIONAL,

LCSClientInternalID ::= ENUMERATED { broadcastService (0), o-andM-HPLMN (1), o-andM-VPLMN (2), anonymousLocation (3), targetMSsubscribedService (4), ... } -- for a CAMEL phase 3 PLMN operator client, the value targetMSsubscribedService shall be used LCSServiceTypeID ::= INTEGER (0..127) -- the integer values 0-63 are reserved for Standard LCS service types -- the integer values 64-127 are reserved for Non Standard LCS service types -- Standard LCS Service Types emergencyServices LCSServiceTypeID ::= emergencyAlertServices LCSServiceTypeID ::= personTracking LCSServiceTypeID ::= fleetManagement LCSServiceTypeID ::= assetManagement LCSServiceTypeID ::= trafficCongestionReporting LCSServiceTypeID ::= roadsideAssistance LCSServiceTypeID ::= routingToNearestCommercialEnterprise LCSServiceTypeID ::= navigation LCSServiceTypeID ::= --this service type is reserved for use in previous releases citySightseeing LCSServiceTypeID ::= localizedAdvertising LCSServiceTypeID ::= mobileYellowPages LCSServiceTypeID ::= trafficAndPublicTransportationInfo LCSServiceTypeID ::= weather LCSServiceTypeID ::= assetAndServiceFinding LCSServiceTypeID ::= gaming LCSServiceTypeID ::= findYourFriend LCSServiceTypeID ::= dating LCSServiceTypeID ::= chatting LCSServiceTypeID ::= routeFinding LCSServiceTypeID ::= whereAmI LCSServiceTypeID ::= 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

-- The values of LCSServiceTypeID are defined according to 3GPP TS 22.071.

1590

3GPP

1591 Release 7 1592 1593

4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864

399

3GPP TS 29.002 V7.5.0 (2006-09)

-- Non Standard LCS Service Types serv64 serv65 serv66 serv67 serv68 serv69 serv70 serv71 serv72 serv73 serv74 serv75 serv76 serv77 serv78 serv79 serv80 serv81 serv82 serv83 serv84 serv85 serv86 serv87 serv88 serv89 serv90 serv91 serv92 serv93 serv94 serv95 serv96 serv97 serv98 serv99 serv100 serv101 serv102 serv103 serv104 serv105 serv106 serv107 serv108 serv109 serv110 serv111 serv112 serv113 serv114 serv115 serv116 serv117 serv118 serv119 serv120 serv121 serv122 serv123 serv124 serv125 serv126 serv127 PLMN-Id --------::= OCTET STRING (SIZE (3)) The internal structure is defined octet 1 bits 4321 bits 8765 octet 2 bits 4321 bits 8765 octet 3 bits 4321 bits 8765

LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID LCSServiceTypeID

::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::=

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

as follows: Mobile Country Code 1st digit Mobile Country Code 2nd digit Mobile Country Code 3rd digit Mobile Network Code 3rd digit or filler (1111) for 2 digit MNCs Mobile Network Code 1st digit Mobile Network Code 2nd digit

-- data types for CAMEL

1594

3GPP

1595 Release 7 1596 1597

4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941

400

3GPP TS 29.002 V7.5.0 (2006-09)

CellGlobalIdOrServiceAreaIdOrLAI ::= CHOICE { cellGlobalIdOrServiceAreaIdFixedLength [0] CellGlobalIdOrServiceAreaIdFixedLength, laiFixedLength [1] LAIFixedLength} CellGlobalIdOrServiceAreaIdFixedLength ::= OCTET STRING (SIZE (7)) -- Refers to Cell Global Identification or Service Are Identification -- defined in 3GPP TS 23.003. -- The internal structure is defined as follows: -- octet 1 bits 4321 Mobile Country Code 1st digit -bits 8765 Mobile Country Code 2nd digit -- octet 2 bits 4321 Mobile Country Code 3rd digit -bits 8765 Mobile Network Code 3rd digit -or filler (1111) for 2 digit MNCs -- octet 3 bits 4321 Mobile Network Code 1st digit -bits 8765 Mobile Network Code 2nd digit -- octets 4 and 5 Location Area Code according to 3GPP TS 24.008 -- octets 6 and 7 Cell Identity (CI) value or -Service Area Code (SAC) value -according to 3GPP TS 23.003 LAIFixedLength ::= OCTET STRING (SIZE (5)) -- Refers to Location Area Identification defined in TS 3GPP TS 23.003 [17]. -- The internal structure is defined as follows: -- octet 1 bits 4321 Mobile Country Code 1st digit -bits 8765 Mobile Country Code 2nd digit -- octet 2 bits 4321 Mobile Country Code 3rd digit -bits 8765 Mobile Network Code 3rd digit -or filler (1111) for 2 digit MNCs -- octet 3 bits 4321 Mobile Network Code 1st digit -bits 8765 Mobile Network Code 2nd digit -- octets 4 and 5 Location Area Code according to TS 3GPP TS 24.008 [35]

-- data types for subscriber management BasicServiceCode ::= CHOICE { bearerService teleservice Ext-BasicServiceCode ::= CHOICE { ext-BearerService ext-Teleservice EMLPP-Info ::= SEQUENCE { maximumentitledPriority defaultPriority extensionContainer ...} [2] BearerServiceCode, [3] TeleserviceCode} [2] Ext-BearerServiceCode, [3] Ext-TeleserviceCode} EMLPP-Priority, EMLPP-Priority, ExtensionContainer

OPTIONAL,

EMLPP-Priority ::= INTEGER (0..15) -- The mapping from the values A,B,0,1,2,3,4 to the integer-value is -- specified as follows where A is the highest and 4 is the lowest -- priority level -- the integer values 7-15 are spare and shall be mapped to value 4 priorityLevelA priorityLevelB priorityLevel0 priorityLevel1 priorityLevel2 priorityLevel3 priorityLevel4 MC-SS-Info ::= SEQUENCE { ss-Code ss-Status nbrSB nbrUser extensionContainer ...} EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority [0] [1] [2] [3] [4] ::= ::= ::= ::= ::= ::= ::= 6 5 0 1 2 3 4

SS-Code, Ext-SS-Status, MaxMC-Bearers, MC-Bearers, ExtensionContainer

OPTIONAL,

MaxMC-Bearers ::= INTEGER (2..maxNumOfMC-Bearers) MC-Bearers ::= INTEGER (1..maxNumOfMC-Bearers) maxNumOfMC-Bearers INTEGER ::= 7

1598

3GPP

1599 Release 7 1600 1601

4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974

401

3GPP TS 29.002 V7.5.0 (2006-09)

Ext-SS-Status ::= OCTET STRING (SIZE (1..5)) -- OCTET 1: --- bits 8765: 0000 (unused) -- bits 4321: Used to convey the "P bit","R bit","A bit" and "Q bit", -representing supplementary service state information -as defined in TS 3GPP TS 23.011 [22] -- bit 4: "Q bit" -- bit 3: "P bit" -- bit 2: "R bit" -- bit 1: "A bit" -- OCTETS 2-5: reserved for future use. They shall be discarded if -- received and not understood. -- data types for geographic location AgeOfLocationInformation ::= INTEGER (0..32767) -- the value represents the elapsed time in minutes since the last -- network contact of the mobile station (i.e. the actuality of the -- location information). -- value 0 indicates that the MS is currently in contact with the -network -- value 32767 indicates that the location information is at least -32767 minutes old

END

4975
4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013

17.7.9 Teleservice Codes

MAP-TS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version10 (10)} DEFINITIONS ::= BEGIN TeleserviceCode ::= OCTET STRING (SIZE (1)) -- This type is used to represent the code identifying a single -- teleservice, a group of teleservices, or all teleservices. The -- services are defined in TS GSM 22.003 [4]. -- The internal structure is defined as follows: -- bits 87654321: group (bits 8765) and specific service -- (bits 4321) Ext-TeleserviceCode ::= OCTET STRING (SIZE (1..5)) -- This type is used to represent the code identifying a single -- teleservice, a group of teleservices, or all teleservices. The -- services are defined in TS GSM 22.003 [4]. -- The internal structure is defined as follows: -- OCTET 1: -- bits 87654321: group (bits 8765) and specific service -- (bits 4321) -- OCTETS 2-5: reserved for -- Ext-TeleserviceCode shall -- treated according to the -- operation that uses this future use. If received the be exception handling defined for the type.

-- Ext-TeleserviceCode includes all values defined for TeleserviceCode. allTeleservices TeleserviceCode ::= '00000000'B

1602

3GPP

1603 Release 7 1604 1605

5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062

402

3GPP TS 29.002 V7.5.0 (2006-09)

allSpeechTransmissionServices telephony emergencyCalls allShortMessageServices shortMessageMT-PP shortMessageMO-PP allFacsimileTransmissionServices facsimileGroup3AndAlterSpeech automaticFacsimileGroup3 facsimileGroup4

TeleserviceCode ::= '00010000'B TeleserviceCode ::= '00010001'B TeleserviceCode ::= '00010010'B TeleserviceCode ::= '00100000'B TeleserviceCode ::= '00100001'B TeleserviceCode ::= '00100010'B TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode ::= ::= ::= ::= '01100000'B '01100001'B '01100010'B '01100011'B

-- The following non-hierarchical Compound Teleservice Groups -- are defined in TS 3GPP TS 22.030: allDataTeleservices TeleserviceCode ::= '01110000'B -- covers Teleservice Groups 'allFacsimileTransmissionServices' -- and 'allShortMessageServices' allTeleservices-ExeptSMS TeleserviceCode ::= '10000000'B -- covers Teleservice Groups 'allSpeechTransmissionServices' and -- 'allFacsimileTransmissionServices' --- Compound Teleservice Group Codes are only used in call -- independent supplementary service operations, i.e. they -- are not used in InsertSubscriberData or in -- DeleteSubscriberData messages. allVoiceGroupCallServices voiceGroupCall voiceBroadcastCall allPLMN-specificTS plmn-specificTS-1 plmn-specificTS-2 plmn-specificTS-3 plmn-specificTS-4 plmn-specificTS-5 plmn-specificTS-6 plmn-specificTS-7 plmn-specificTS-8 plmn-specificTS-9 plmn-specificTS-A plmn-specificTS-B plmn-specificTS-C plmn-specificTS-D plmn-specificTS-E plmn-specificTS-F END TeleserviceCode ::= '10010000'B TeleserviceCode ::= '10010001'B TeleserviceCode ::= '10010010'B TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode TeleserviceCode ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= '11010000'B '11010001'B '11010010'B '11010011'B '11010100'B '11010101'B '11010110'B '11010111'B '11011000'B '11011001'B '11011010'B '11011011'B '11011100'B '11011101'B '11011110'B '11011111'B

5063
5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087

17.7.10 Bearer Service Codes

MAP-BS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version10 (10)} DEFINITIONS ::= BEGIN BearerServiceCode ::= OCTET STRING (SIZE (1)) -- This type is used to represent the code identifying a single -- bearer service, a group of bearer services, or all bearer -- services. The services are defined in TS 3GPP TS 22.002 [3]. -- The internal structure is defined as follows: --- plmn-specific bearer services: -- bits 87654321: defined by the HPLMN operator ----rest of bearer services: bit 8: 0 (unused) bits 7654321: group (bits 7654), and rate, if applicable (bits 321)

1606

3GPP

1607 Release 7 1608 1609

5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151

403

3GPP TS 29.002 V7.5.0 (2006-09)

Ext-BearerServiceCode ::= OCTET STRING (SIZE (1..5)) -- This type is used to represent the code identifying a single -- bearer service, a group of bearer services, or all bearer -- services. The services are defined in TS 3GPP TS 22.002 [3]. -- The internal structure is defined as follows: --- OCTET 1: -- plmn-specific bearer services: -- bits 87654321: defined by the HPLMN operator --- rest of bearer services: -- bit 8: 0 (unused) -- bits 7654321: group (bits 7654), and rate, if applicable -- (bits 321) -- OCTETS 2-5: reserved for -- Ext-TeleserviceCode shall -- treated according to the -- operation that uses this future use. If received the be exception handling defined for the type.

-- Ext-BearerServiceCode includes all values defined for BearerServiceCode. allBearerServices allDataCDA-Services dataCDA-300bps dataCDA-1200bps dataCDA-1200-75bps dataCDA-2400bps dataCDA-4800bps dataCDA-9600bps general-dataCDA allDataCDS-Services dataCDS-1200bps dataCDS-2400bps dataCDS-4800bps dataCDS-9600bps general-dataCDS allPadAccessCA-Services padAccessCA-300bps padAccessCA-1200bps padAccessCA-1200-75bps padAccessCA-2400bps padAccessCA-4800bps padAccessCA-9600bps general-padAccessCA allDataPDS-Services dataPDS-2400bps dataPDS-4800bps dataPDS-9600bps general-dataPDS allAlternateSpeech-DataCDA allAlternateSpeech-DataCDS allSpeechFollowedByDataCDA allSpeechFollowedByDataCDS BearerServiceCode ::= '00000000'B BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= '00010000'B '00010001'B '00010010'B '00010011'B '00010100'B '00010101'B '00010110'B '00010111'B '00011000'B '00011010'B '00011100'B '00011101'B '00011110'B '00011111'B '00100000'B '00100001'B '00100010'B '00100011'B '00100100'B '00100101'B '00100110'B '00100111'B '00101000'B '00101100'B '00101101'B '00101110'B '00101111'B

BearerServiceCode ::= '00110000'B BearerServiceCode ::= '00111000'B BearerServiceCode ::= '01000000'B BearerServiceCode ::= '01001000'B

1610

3GPP

1611 Release 7 1612 1613

5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189

404

3GPP TS 29.002 V7.5.0 (2006-09)

-- The following non-hierarchical Compound Bearer Service -- Groups are defined in TS 3GPP TS 22.030: allDataCircuitAsynchronous BearerServiceCode ::= '01010000'B -- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and -- "allSpeechFollowedByDataCDA" allAsynchronousServices BearerServiceCode ::= '01100000'B -- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA", -- "allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services" allDataCircuitSynchronous BearerServiceCode ::= '01011000'B -- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and -- "allSpeechFollowedByDataCDS" allSynchronousServices BearerServiceCode ::= '01101000'B -- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS", -- "allSpeechFollowedByDataCDS" and "allDataPDS-Services" --- Compound Bearer Service Group Codes are only used in call -- independent supplementary service operations, i.e. they -- are not used in InsertSubscriberData or in -- DeleteSubscriberData messages. allPLMN-specificBS plmn-specificBS-1 plmn-specificBS-2 plmn-specificBS-3 plmn-specificBS-4 plmn-specificBS-5 plmn-specificBS-6 plmn-specificBS-7 plmn-specificBS-8 plmn-specificBS-9 plmn-specificBS-A plmn-specificBS-B plmn-specificBS-C plmn-specificBS-D plmn-specificBS-E plmn-specificBS-F BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode BearerServiceCode ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= ::= '11010000'B '11010001'B '11010010'B '11010011'B '11010100'B '11010101'B '11010110'B '11010111'B '11011000'B '11011001'B '11011010'B '11011011'B '11011100'B '11011101'B '11011110'B '11011111'B

END

5190
5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225

17.7.11 Extension data types

MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS PrivateExtension, ExtensionContainer, SLR-ArgExtensionContainer; -- IOC for private MAP extensions MAP-EXTENSION ::= CLASS { &ExtensionType OPTIONAL, &extensionId OBJECT IDENTIFIER } -- The length of the Object Identifier shall not exceed 16 octets and the -- number of components of the Object Identifier shall not exceed 16 -- data types ExtensionContainer ::= SEQUENCE { privateExtensionList pcs-Extensions ...} [0]PrivateExtensionList [1]PCS-Extensions OPTIONAL, OPTIONAL,

1614

3GPP

1615 Release 7 1616 1617 5226 SLR-ArgExtensionContainer ::= SEQUENCE {

5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256

405

3GPP TS 29.002 V7.5.0 (2006-09)

privateExtensionList slr-Arg-PCS-Extensions ...}

[0]PrivateExtensionList [1]SLR-Arg-PCS-Extensions

OPTIONAL, OPTIONAL,

PrivateExtensionList ::= SEQUENCE SIZE (1..maxNumOfPrivateExtensions) OF PrivateExtension PrivateExtension ::= SEQUENCE { extId extType maxNumOfPrivateExtensions INTEGER ::= 10 MAP-EXTENSION.&extensionId ({ExtensionSet}), MAP-EXTENSION.&ExtensionType ({ExtensionSet}{@extId})

OPTIONAL}

ExtensionSet MAP-EXTENSION ::= {... -- ExtensionSet is the set of all defined private extensions } -- Unsupported private extensions shall be discarded if received. PCS-Extensions ::= SEQUENCE { ...}

SLR-Arg-PCS-Extensions ::= SEQUENCE {

..., na-ESRK-Request [0] NULL OPTIONAL }

END

5257
5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300

17.7.12 Group Call data types

MAP-GR-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-GR-DataTypes (23) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS PrepareGroupCallArg, PrepareGroupCallRes, SendGroupCallEndSignalArg, SendGroupCallEndSignalRes, ForwardGroupCallSignallingArg, ProcessGroupCallSignallingArg, SendGroupCallInfoArg, SendGroupCallInfoRes ; IMPORTS ISDN-AddressString, IMSI, TMSI, EMLPP-Priority, ASCI-CallReference, SignalInfo, GlobalCellId FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} Ext-TeleserviceCode FROM MAP-TS-Code { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version10 (10)} Kc, AdditionalInfo, GroupId,

1618

3GPP

1619 Release 7 1620 1621

5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371

406

3GPP TS 29.002 V7.5.0 (2006-09)

AdditionalSubscriptions, Cksn FROM MAP-MS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version10 (10)} ExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} ; PrepareGroupCallArg ::= SEQUENCE { teleservice Ext-TeleserviceCode, asciCallReference ASCI-CallReference, codec-Info CODEC-Info, cipheringAlgorithm CipheringAlgorithm, groupKeyNumber-Vk-Id [0] GroupKeyNumber OPTIONAL, groupKey [1] Kc OPTIONAL, -- this parameter shall not be sent and shall be discarded if received priority [2] EMLPP-Priority OPTIONAL, uplinkFree [3] NULL OPTIONAL, extensionContainer [4] ExtensionContainer OPTIONAL, ..., vstk [5] VSTK OPTIONAL, vstk-rand [6] VSTK-RAND OPTIONAL } VSTK ::= OCTET STRING (SIZE (16)) VSTK-RAND ::= OCTET STRING (SIZE (5)) -- The 36 bit value is carried in bit 7 of octet 1 to bit 4 of octet 5 -- bits 3, 2, 1, and 0 of octet 5 are padded with zeros. PrepareGroupCallRes ::= SEQUENCE { groupCallNumber extensionContainer ...} SendGroupCallEndSignalArg ::= SEQUENCE { imsi extensionContainer ..., talkerPriority additionalInfo TalkerPriority ::= ENUMERATED { normal (0), privileged (1), emergency (2)} SendGroupCallEndSignalRes ::= SEQUENCE { extensionContainer ...} ExtensionContainer OPTIONAL, ISDN-AddressString, ExtensionContainer

OPTIONAL,

IMSI ExtensionContainer [0]TalkerPriority [1]AdditionalInfo

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

ForwardGroupCallSignallingArg ::= SEQUENCE { imsi IMSI uplinkRequestAck [0] NULL uplinkReleaseIndication [1] NULL uplinkRejectCommand [2] NULL uplinkSeizedCommand [3] NULL uplinkReleaseCommand [4] NULL extensionContainer ExtensionContainer ..., stateAttributes [5] StateAttributes talkerPriority [6] TalkerPriority additionalInfo [7] AdditionalInfo emergencyModeResetCommandFlag [8] NULL sm-RP-UI [9] SignalInfo }

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

1622

3GPP

1623 Release 7 1624 1625

5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443

407

3GPP TS 29.002 V7.5.0 (2006-09)

ProcessGroupCallSignallingArg ::= SEQUENCE { uplinkRequest [0] NULL uplinkReleaseIndication [1] NULL releaseGroupCall [2] NULL extensionContainer ExtensionContainer ..., talkerPriority [3] TalkerPriority additionalInfo [4] AdditionalInfo emergencyModeResetCommandFlag [5] NULL GroupKeyNumber ::= INTEGER (0..15)

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

CODEC-Info ::= OCTET STRING (SIZE (5..10)) -- Refers to channel type -- coded according to 3GPP TS 48.008 [49] and including Element identifier and Length CipheringAlgorithm ::= OCTET STRING (SIZE (1)) -- Refers to 'permitted algorithms' in 'encryption information' -- coded according to 3GPP TS 48.008 [49]: ----------Bits 8765 0000 0000 0000 0000 0001 0010 0100 1000 8-1 4321 0001 0010 0100 1000 0000 0000 0000 0000

No encryption GSM A5/1 GSM A5/2 GSM A5/3 GSM A5/4 GSM A5/5 GSM A5/6 GSM A5/7 [5] [6] [7] [8] NULL NULL NULL NULL OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

StateAttributes ::= SEQUENCE { downlinkAttached uplinkAttached dualCommunication callOriginator

-- Refers to 3GPP TS 44.068 for definitions of StateAttributes fields. SendGroupCallInfoArg ::= SEQUENCE { requestedInfo groupId cellId imsi tmsi additionalInfo talkerPriority cksn extensionContainer ... }

RequestedInfo, GroupId, [0] GlobalCellId [1] IMSI [2] TMSI [3] AdditionalInfo [4] TalkerPriority [5] Cksn [6] ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

RequestedInfo ::= ENUMERATED { anchorMSC-AddressAndASCI-CallReference (0), imsiAndAdditionalInfoAndAdditionalSubscription (1), ... } -exception handling: -an unrecognized value shall be rejected by the receiver with a return error cause of -unexpected data value SendGroupCallInfoRes ::= SEQUENCE { anchorMSC-Address asciCallReference imsi additionalInfo additionalSubscriptions kc extensionContainer ... } END [0] [1] [2] [3] [4] [5] [6] ISDN-AddressString ASCI-CallReference IMSI AdditionalInfo AdditionalSubscriptions Kc ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,

5444

17.7.13 Location service data types

1626

3GPP

1627 Release 7 1628 1629

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78

408

3GPP TS 29.002 V7.5.0 (2006-09)

MAP-LCS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LCS-DataTypes (25) version10 (10)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RoutingInfoForLCS-Arg, RoutingInfoForLCS-Res, ProvideSubscriberLocation-Arg, ProvideSubscriberLocation-Res, SubscriberLocationReport-Arg, SubscriberLocationReport-Res, LocationType, DeferredLocationEventType, LCSClientName, LCS-QoS, Horizontal-Accuracy, ResponseTime, Ext-GeographicalInformation, VelocityEstimate, SupportedGADShapes, Add-GeographicalInformation, LCSRequestorID, LCS-ReferenceNumber, LCSCodeword, AreaEventInfo, ReportingPLMNList, PeriodicLDRInfo, SequenceNumber ; IMPORTS AddressString, ISDN-AddressString, IMEI, IMSI, LMSI, SubscriberIdentity, AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, LCSServiceTypeID, CellGlobalIdOrServiceAreaIdOrLAI, PLMN-Id FROM MAP-CommonDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version10 (10)} ExtensionContainer, SLR-ArgExtensionContainer FROM MAP-ExtensionDataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version10 (10)} USSD-DataCodingScheme, USSD-String FROM MAP-SS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version10 (10)} APN, GSN-Address, SupportedLCS-CapabilitySets FROM MAP-MS-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version10 (10)} Additional-Number FROM MAP-SM-DataTypes { itu-t identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version10 (10)} ;

1630

3GPP

1631 Release 7 1632 1633

79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152

409

3GPP TS 29.002 V7.5.0 (2006-09)

RoutingInfoForLCS-Arg ::= SEQUENCE { mlcNumber targetMS extensionContainer ...} RoutingInfoForLCS-Res ::= SEQUENCE { targetMS lcsLocationInfo extensionContainer ..., v-gmlc-Address h-gmlc-Address ppr-Address additional-v-gmlc-Address LCSLocationInfo ::= SEQUENCE { networkNode-Number -- NetworkNode-number can be either lmsi extensionContainer ... , gprsNodeIndicator -- gprsNodeIndicator is set only if additional-Number supportedLCS-CapabilitySets additional-LCS-CapabilitySets }

[0] ISDN-AddressString, [1] SubscriberIdentity, [2] ExtensionContainer

OPTIONAL,

[0] SubscriberIdentity, [1] LCSLocationInfo, [2] ExtensionContainer [3] [4] [5] [6] GSN-Address GSN-Address GSN-Address GSN-Address

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

ISDN-AddressString, msc-number or sgsn-number [0] LMSI [1] ExtensionContainer

OPTIONAL, OPTIONAL,

[2] NULL OPTIONAL, the SGSN number is sent as the Network Node Number [3] Additional-Number OPTIONAL, [4] SupportedLCS-CapabilitySets OPTIONAL, [5] SupportedLCS-CapabilitySets OPTIONAL

ProvideSubscriberLocation-Arg ::= SEQUENCE { locationType LocationType, mlc-Number ISDN-AddressString, lcs-ClientID [0] LCS-ClientID privacyOverride [1] NULL imsi [2] IMSI msisdn [3] ISDN-AddressString lmsi [4] LMSI imei [5] IMEI lcs-Priority [6] LCS-Priority lcs-QoS [7] LCS-QoS extensionContainer [8] ExtensionContainer ... , supportedGADShapes [9] SupportedGADShapes lcs-ReferenceNumber [10] LCS-ReferenceNumber lcsServiceTypeID [11] LCSServiceTypeID lcsCodeword [12] LCSCodeword lcs-PrivacyCheck [13] LCS-PrivacyCheck areaEventInfo [14] AreaEventInfo h-gmlc-Address [15] GSN-Address mo-lrShortCircuitIndicator [16] NULL periodicLDRInfo [17] PeriodicLDRInfo reportingPLMNList [18] ReportingPLMNList

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

-- one of imsi or msisdn is mandatory -- If a location estimate type indicates activate deferred location or cancel deferred -- location, a lcs-Reference number shall be included. LocationType ::= SEQUENCE { locationEstimateType ..., deferredLocationEventType [0] LocationEstimateType, [1] DeferredLocationEventType OPTIONAL }

LocationEstimateType ::= ENUMERATED { currentLocation (0), currentOrLastKnownLocation (1), initialLocation (2), ..., activateDeferredLocation (3), cancelDeferredLocation (4) , notificationVerificationOnly (5) } -exception handling: -a ProvideSubscriberLocation-Arg containing an unrecognized LocationEstimateType -shall be rejected by the receiver with a return error cause of unexpected data value

1634

3GPP

1635 Release 7 1636 1637

153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224

410

3GPP TS 29.002 V7.5.0 (2006-09)

DeferredLocationEventType ::= BIT STRING { msAvailable (0) , enteringIntoArea (1), leavingFromArea (2), beingInsideArea (3) , periodicLDR (4) } (SIZE (1..16)) -- beingInsideArea is always treated as oneTimeEvent regardless of the possible value -- of occurrenceInfo inside areaEventInfo. -- exception handling: -- a ProvideSubscriberLocation-Arg containing other values than listed above in -- DeferredLocationEventType shall be rejected by the receiver with a return error cause of -- unexpected data value. LCS-ClientID ::= SEQUENCE { lcsClientType lcsClientExternalID lcsClientDialedByMS lcsClientInternalID lcsClientName ..., lcsAPN lcsRequestorID [0] [1] [2] [3] [4] LCSClientType, LCSClientExternalID AddressString LCSClientInternalID LCSClientName

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

[5] APN [6] LCSRequestorID

LCSClientType ::= ENUMERATED { emergencyServices (0), valueAddedServices (1), plmnOperatorServices (2), lawfulInterceptServices (3), ... } -exception handling: -unrecognized values may be ignored if the LCS client uses the privacy override -otherwise, an unrecognized value shall be treated as unexpected data by a receiver -a return error shall then be returned if received in a MAP invoke LCSClientName ::= SEQUENCE { dataCodingScheme nameString ..., lcs-FormatIndicator [0] USSD-DataCodingScheme, [2] NameString, [3] LCS-FormatIndicator OPTIONAL }

-- The USSD-DataCodingScheme shall indicate use of the default alphabet through the -- following encoding -bit 7 6 5 4 3 2 1 0 -0 0 0 0 1 1 1 1 NameString ::= USSD-String (SIZE (1..maxNameStringLength)) maxNameStringLength INTEGER ::= 63 [0] USSD-DataCodingScheme, [1] RequestorIDString, [2] LCS-FormatIndicator OPTIONAL }

LCSRequestorID ::= SEQUENCE { dataCodingScheme requestorIDString ..., lcs-FormatIndicator

RequestorIDString ::= USSD-String (SIZE (1..maxRequestorIDStringLength)) maxRequestorIDStringLength INTEGER ::= 63 (0), (1), (2), (3), (4),

LCS-FormatIndicator ::= ENUMERATED { logicalName e-mailAddress msisdn url sipUrl ... } LCS-Priority ::= OCTET STRING (SIZE (1)) -- 0 = highest priority -- 1 = normal priority -- all other values treated as 1

1638

3GPP

1639 Release 7 1640 1641

225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296

411

3GPP TS 29.002 V7.5.0 (2006-09)

LCS-QoS ::= SEQUENCE { horizontal-accuracy verticalCoordinateRequest vertical-accuracy responseTime extensionContainer ..., velocityRequest }

[0] [1] [2] [3] [4]

Horizontal-Accuracy NULL Vertical-Accuracy ResponseTime ExtensionContainer

OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL

[5] NULL

Horizontal-Accuracy ::= OCTET STRING (SIZE (1)) -- bit 8 = 0 -- bits 7-1 = 7 bit Uncertainty Code defined in 3GPP TS 23.032. The horizontal location -- error should be less than the error indicated by the uncertainty code with 67% -- confidence. Vertical-Accuracy ::= OCTET STRING (SIZE (1)) -- bit 8 = 0 -- bits 7-1 = 7 bit Vertical Uncertainty Code defined in 3GPP TS 23.032. -- The vertical location error should be less than the error indicated -- by the uncertainty code with 67% confidence. ResponseTime ::= SEQUENCE { responseTimeCategory ResponseTimeCategory, ...} -note: an expandable SEQUENCE simplifies later addition of a numeric response time. ResponseTimeCategory ::= ENUMERATED { lowdelay (0), delaytolerant (1), ... } -exception handling: -an unrecognized value shall be treated the same as value 1 (delaytolerant) SupportedGADShapes ::= BIT STRING { ellipsoidPoint (0), ellipsoidPointWithUncertaintyCircle (1), ellipsoidPointWithUncertaintyEllipse (2), polygon (3), ellipsoidPointWithAltitude (4), ellipsoidPointWithAltitudeAndUncertaintyElipsoid (5), ellipsoidArc (6) } (SIZE (7..16)) -- A node shall mark in the BIT STRING all Shapes defined in 3GPP TS 23.032 it supports. -- exception handling: bits 7 to 15 shall be ignored if received. LCS-ReferenceNumber::= OCTET STRING (SIZE(1)) LCSCodeword ::= SEQUENCE { dataCodingScheme lcsCodewordString ...} [0] USSD-DataCodingScheme, [1] LCSCodewordString,

LCSCodewordString ::= USSD-String (SIZE (1..maxLCSCodewordStringLength)) maxLCSCodewordStringLength INTEGER ::= 20 [0] PrivacyCheckRelatedAction, [1] PrivacyCheckRelatedAction

LCS-PrivacyCheck ::= SEQUENCE { callSessionUnrelated callSessionRelated ...}

OPTIONAL,

PrivacyCheckRelatedAction ::= ENUMERATED { allowedWithoutNotification (0), allowedWithNotification (1), allowedIfNoResponse (2), restrictedIfNoResponse (3), notAllowed (4), ...} -exception handling: -a ProvideSubscriberLocation-Arg containing an unrecognized PrivacyCheckRelatedAction -shall be rejected by the receiver with a return error cause of unexpected data value

1642

3GPP

1643 Release 7 1644 1645

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

412

3GPP TS 29.002 V7.5.0 (2006-09)

AreaEventInfo ::= SEQUENCE { areaDefinition occurrenceInfo intervalTime ...} AreaDefinition ::= SEQUENCE { areaList ...}

[0] [1] [2]

AreaDefinition, OccurrenceInfo IntervalTime

OPTIONAL, OPTIONAL,

[0]

AreaList,

AreaList ::= SEQUENCE SIZE (1..maxNumOfAreas) OF Area maxNumOfAreas INTEGER ::= 10 [0] [1] AreaType, AreaIdentification,

Area ::= SEQUENCE { areaType areaIdentification ...} AreaType ::= ENUMERATED { countryCode plmnId locationAreaId routingAreaId cellGlobalId ..., utranCellId AreaIdentification ::= OCTET STRING (SIZE -- The internal structure is defined -- octet 1 bits 4321 -bits 8765 -- octet 2 bits 4321 -bits 8765 --- octet 3 bits 4321 -bits 8765 -- octets 4 and 5 --- octet 6 -- octets 6 and 7 -- octets 4 until 7 OccurrenceInfo ::= ENUMERATED { oneTimeEvent multipleTimeEvent ...}

(0), (1), (2), (3), (4), (5) } (2..7)) as follows: Mobile Country Code 1st digit Mobile Country Code 2nd digit Mobile Country Code 3rd digit Mobile Network Code 3rd digit if 3 digit MNC included or filler (1111) Mobile Network Code 1st digit Mobile Network Code 2nd digit Location Area Code (LAC) for Local Area Id, Routing Area Id and Cell Global Id Routing Area Code (RAC) for Routing Area Id Cell Identity (CI) for Cell Global Id Utran Cell Identity (UC-Id) for Utran Cell Id (0), (1),

IntervalTime ::= INTEGER (1..32767) -- minimum interval time between area reports in seconds PeriodicLDRInfo ::= SEQUENCE { reportingAmount ReportingAmount, reportingInterval ReportingInterval, ...} -- reportingInterval x reportingAmount shall not exceed 8639999 (99 days, 23 hours, -- 59 minutes and 59 seconds) for compatibility with OMA MLP and RLP ReportingAmount ::= INTEGER (1..maxReportingAmount) maxReportingAmount INTEGER ::= 8639999 ReportingInterval ::= INTEGER (1..maxReportingInterval) -- ReportingInterval is in seconds maxReportingInterval INTEGER ::= 8639999 ReportingPLMNList::= SEQUENCE { plmn-ListPrioritized plmn-List ...}

[0] NULL [1] PLMNList,

OPTIONAL,

1646

3GPP

1647 Release 7 1648 1649

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

413

3GPP TS 29.002 V7.5.0 (2006-09)

PLMNList::= SEQUENCE SIZE (1..maxNumOfReportingPLMN) OF ReportingPLMN maxNumOfReportingPLMN INTEGER ::= 20 ReportingPLMN::= SEQUENCE { plmn-Id ran-Technology ran-PeriodicLocationSupport ...} RAN-Technology ::= ENUMERATED { gsm (0), umts (1), ...} ProvideSubscriberLocation-Res ::= SEQUENCE { locationEstimate Ext-GeographicalInformation, ageOfLocationEstimate [0] AgeOfLocationInformation OPTIONAL, extensionContainer [1] ExtensionContainer OPTIONAL, ... , add-LocationEstimate [2] Add-GeographicalInformation OPTIONAL, deferredmt-lrResponseIndicator [3] NULL OPTIONAL, geranPositioningData [4] PositioningDataInformation OPTIONAL, utranPositioningData [5] UtranPositioningDataInfo OPTIONAL, cellIdOrSai [6] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, sai-Present [7] NULL OPTIONAL, accuracyFulfilmentIndicator [8] AccuracyFulfilmentIndicator OPTIONAL, velocityEstimate [9] VelocityEstimate OPTIONAL, mo-lrShortCircuitIndicator [10] NULL OPTIONAL } ----------if deferredmt-lrResponseIndicator is set, locationEstimate is ignored. the add-LocationEstimate parameter shall not be sent to a node that did not indicate the geographic shapes supported in the ProvideSubscriberLocation-Arg The locationEstimate and the add-locationEstimate parameters shall not be sent if the supportedGADShapes parameter has been received in ProvideSubscriberLocation-Arg and the shape encoded in locationEstimate or add-LocationEstimate is not marked as supported in supportedGADShapes. In such a case ProvideSubscriberLocation shall be rejected with error FacilityNotSupported with additional indication shapeOfLocationEstimateNotSupported. sai-Present indicates that the cellIdOrSai parameter contains a Service Area Identity.

[0] PLMN-Id, [1] RAN-Technology [2] NULL

OPTIONAL, OPTIONAL,

AccuracyFulfilmentIndicator ::= ENUMERATED { requestedAccuracyFulfilled (0), requestedAccuracyNotFulfilled (1), ... }

1650

3GPP

1651 Release 7 1652 1653

417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476

414

3GPP TS 29.002 V7.5.0 (2006-09)

Ext-GeographicalInformation ::= OCTET STRING (SIZE (1..maxExt-GeographicalInformation)) -- Refers to geographical Information defined in 3GPP TS 23.032. -- This is composed of 1 or more octets with an internal structure according to -- 3GPP TS 23.032 -- Octet 1: Type of shape, only the following shapes in 3GPP TS 23.032 are allowed: -(a) Ellipsoid point with uncertainty circle -(b) Ellipsoid point with uncertainty ellipse -(c) Ellipsoid point with altitude and uncertainty ellipsoid -(d) Ellipsoid Arc -(e) Ellipsoid Point -- Any other value in octet 1 shall be treated as invalid -- Octets 2 to 8 for case (a) Ellipsoid point with uncertainty circle -Degrees of Latitude 3 octets -Degrees of Longitude 3 octets -Uncertainty code 1 octet -- Octets 2 to 11 for case (b) Ellipsoid point with uncertainty ellipse: -Degrees of Latitude 3 octets -Degrees of Longitude 3 octets -Uncertainty semi-major axis 1 octet -Uncertainty semi-minor axis 1 octet -Angle of major axis 1 octet -Confidence 1 octet -- Octets 2 to 14 for case (c) Ellipsoid point with altitude and uncertainty ellipsoid -Degrees of Latitude 3 octets -Degrees of Longitude 3 octets -Altitude 2 octets -Uncertainty semi-major axis 1 octet -Uncertainty semi-minor axis 1 octet -Angle of major axis 1 octet -Uncertainty altitude 1 octet -Confidence 1 octet -- Octets 2 to 13 for case (d) Ellipsoid Arc -Degrees of Latitude 3 octets -Degrees of Longitude 3 octets -Inner radius 2 octets -Uncertainty radius 1 octet -Offset angle 1 octet -Included angle 1 octet -Confidence 1 octet -- Octets 2 to 7 for case (e) Ellipsoid Point -Degrees of Latitude 3 octets -Degrees of Longitude 3 octets ------------An Ext-GeographicalInformation parameter comprising more than one octet and containing any other shape or an incorrect number of octets or coding according to 3GPP TS 23.032 shall be treated as invalid data by a receiver. An Ext-GeographicalInformation parameter comprising one octet shall be discarded by the receiver if an Add-GeographicalInformation parameter is received in the same message. An Ext-GeographicalInformation parameter comprising one octet shall be treated as invalid data by the receiver if an Add-GeographicalInformation parameter is not received in the same message.

maxExt-GeographicalInformation INTEGER ::= 20 -- the maximum length allows for further shapes in 3GPP TS 23.032 to be included in later -- versions of 3GPP TS 29.002

1654

3GPP

1655 Release 7 1656 1657

477 478 479 480 481 482 483 484 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

415

3GPP TS 29.002 V7.5.0 (2006-09)

VelocityEstimate ::= OCTET STRING (SIZE (4..7)) -- Refers to Velocity description defined in 3GPP TS 23.032. -- This is composed of 4 or more octets with an internal structure according to -- 3GPP TS 23.032 -- Octet 1: Type of velocity, only the following types in 3GPP TS 23.032 are allowed: -(a) Horizontal Velocity -(b) Horizontal with Vertical Velocity -(c) Horizontal Velocity with Uncertainty -(d) Horizontal with Vertical Velocity and Uncertainty -- For types Horizontal with Vertical Velocity and Horizontal with Vertical Velocity -- and Uncertainty, the direction of the Vertical Speed is also included in Octet 1 -- Any other value in octet 1 shall be treated as invalid -- Octets 2 to 4 for case (a) Horizontal velocity: -Bearing 1 octet -Horizontal Speed 2 octets -- Octets 2 to 5 for case (b) Horizontal with Vertical Velocity: -Bearing 1 octet -Horizontal Speed 2 octets -Vertical Speed 1 octet -- Octets 2 to 5 for case (c) Horizontal velocity with Uncertainty: -Bearing 1 octet -Horizontal Speed 2 octets -Uncertainty Speed 1 octet -- Octets 2 to 7 for case (d) Horizontal with Vertical Velocity and Uncertainty: -Bearing 1 octet -Horizontal Speed 2 octets -Vertical Speed 1 octet -Horizontal Uncertainty Speed 1 octet -Vertical Uncertainty Speed 1 octet PositioningDataInformation ::= OCTET STRING (SIZE (2..maxPositioningDataInformation)) -- Refers to the Positioning Data defined in 3GPP TS 49.031. -- This is composed of 2 or more octets with an internal structure according to -- 3GPP TS 49.031. maxPositioningDataInformation INTEGER ::= 10 -UtranPositioningDataInfo ::= OCTET STRING (SIZE (3..maxUtranPositioningDataInfo)) -- Refers to the Position Data defined in 3GPP TS 25.413. -- This is composed of the positioningDataDiscriminator and the positioningDataSet -- included in positionData as defined in 3GPP TS 25.413. maxUtranPositioningDataInfo INTEGER ::= 11 -Add-GeographicalInformation ::= OCTET STRING (SIZE (1..maxAdd-GeographicalInformation)) -- Refers to geographical Information defined in 3GPP TS 23.032. -- This is composed of 1 or more octets with an internal structure according to -- 3GPP TS 23.032 -- Octet 1: Type of shape, all the shapes defined in 3GPP TS 23.032 are allowed: -- Octets 2 to n (where n is the total number of octets necessary to encode the shape -- according to 3GPP TS 23.032) are used to encode the shape itself in accordance with the -- encoding defined in 3GPP TS 23.032 --- An Add-GeographicalInformation parameter, whether valid or invalid, received -- together with a valid Ext-GeographicalInformation parameter in the same message -- shall be discarded. --- An Add-GeographicalInformation parameter containing any shape not defined in -- 3GPP TS 23.032 or an incorrect number of octets or coding according to -- 3GPP TS 23.032 shall be treated as invalid data by a receiver if not received -- together with a valid Ext-GeographicalInformation parameter in the same message. maxAdd-GeographicalInformation INTEGER ::= 91 -- the maximum length allows support for all the shapes currently defined in 3GPP TS 23.032

1658

3GPP

1659 Release 7 1660 1661

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 599 600 601 602 603 604 605 606 607 608 609 610 611 612

416

3GPP TS 29.002 V7.5.0 (2006-09)

SubscriberLocationReport-Arg ::= SEQUENCE { lcs-Event LCS-Event, lcs-ClientID LCS-ClientID, lcsLocationInfo LCSLocationInfo, msisdn [0] ISDN-AddressString OPTIONAL, imsi [1] IMSI OPTIONAL, imei [2] IMEI OPTIONAL, na-ESRD [3] ISDN-AddressString OPTIONAL, na-ESRK [4] ISDN-AddressString OPTIONAL, locationEstimate [5] Ext-GeographicalInformation OPTIONAL, ageOfLocationEstimate [6] AgeOfLocationInformation OPTIONAL, slr-ArgExtensionContainer [7] SLR-ArgExtensionContainer OPTIONAL, ... , add-LocationEstimate [8] Add-GeographicalInformation OPTIONAL, deferredmt-lrData [9] Deferredmt-lrData OPTIONAL, lcs-ReferenceNumber [10] LCS-ReferenceNumber OPTIONAL, geranPositioningData [11] PositioningDataInformation OPTIONAL, utranPositioningData [12] UtranPositioningDataInfo OPTIONAL, cellIdOrSai [13] CellGlobalIdOrServiceAreaIdOrLAI OPTIONAL, h-gmlc-Address [14] GSN-Address OPTIONAL, lcsServiceTypeID [15] LCSServiceTypeID OPTIONAL, sai-Present [17] NULL OPTIONAL, pseudonymIndicator [18] NULL OPTIONAL, velocityEstimate [19] VelocityEstimate OPTIONAL, accuracyFulfilmentIndicator [20] AccuracyFulfilmentIndicator OPTIONAL, sequenceNumber [21] SequenceNumber OPTIONAL, periodicLDRInfo [22] PeriodicLDRInfo OPTIONAL, mo-lrShortCircuitIndicator [23] NULL OPTIONAL } ---------------one of msisdn or imsi is mandatory a location estimate that is valid for the locationEstimate parameter should be transferred in this parameter in preference to the add-LocationEstimate. the deferredmt-lrData parameter shall be included if and only if the lcs-Event indicates a deferredmt-lrResponse. if the lcs-Event indicates a deferredmt-lrResponse then the locationEstimate and the add-locationEstimate parameters shall not be sent if the supportedGADShapes parameter had been received in ProvideSubscriberLocation-Arg and the shape encoded in locationEstimate or add-LocationEstimate was not marked as supported in supportedGADShapes. In such a case terminationCause in deferredmt-lrData shall be present with value shapeOfLocationEstimateNotSupported. If a lcs event indicates deferred mt-lr response, the lcs-Reference number shall be included. sai-Present indicates that the cellIdOrSai parameter contains a Service Area Identity.

Deferredmt-lrData ::= SEQUENCE { deferredLocationEventType DeferredLocationEventType, terminationCause [0] TerminationCause OPTIONAL, lcsLocationInfo [1] LCSLocationInfo OPTIONAL, ...} -- lcsLocationInfo may be included only if a terminationCause is present -- indicating mt-lrRestart. LCS-Event ::= ENUMERATED { emergencyCallOrigination (0), emergencyCallRelease (1), mo-lr (2), ..., deferredmt-lrResponse (3) , deferredmo-lrTTTPInitiation (4) } -deferredmt-lrResponse is applicable to the delivery of a location estimate -for an LDR initiated earlier by either the network (via an MT-LR activate deferred -location) or the UE (via a deferred MO-LR TTTP initiation) -exception handling: -a SubscriberLocationReport-Arg containing an unrecognized LCS-Event -shall be rejected by a receiver with a return error cause of unexpected data value

1662

3GPP

1663 Release 7 1664 1665

613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651

417

3GPP TS 29.002 V7.5.0 (2006-09)

TerminationCause ::= ENUMERATED { normal (0), errorundefined (1), internalTimeout (2), congestion (3), mt-lrRestart (4), privacyViolation (5), ..., shapeOfLocationEstimateNotSupported (6) , subscriberTermination (7), uETermination (8), networkTermination (9) } -- mt-lrRestart shall be used to trigger the GMLC to restart the location procedure, -- either because the sending node knows that the terminal has moved under coverage -- of another MSC or SGSN (e.g. Send Identification received), or because the subscriber -- has been deregistered due to a Cancel Location received from HLR. --- exception handling -- an unrecognized value shall be treated the same as value 1 (errorundefined) SequenceNumber ::= INTEGER (1..maxReportingAmount) SubscriberLocationReport-Res ::= SEQUENCE { extensionContainer ExtensionContainer ..., na-ESRK [0] ISDN-AddressString na-ESRD [1] ISDN-AddressString h-gmlc-Address [2] GSN-Address mo-lrShortCircuitIndicator [3] NULL reportingPLMNList [4] ReportingPLMNList lcs-ReferenceNumber [5] LCS-ReferenceNumber OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }

-- na-ESRK and na-ESRD are mutually exclusive --- exception handling -- receipt of both na-ESRK and na-ESRD shall be treated the same as a return error END

17.7.14 Void

1666

3GPP

1667

652

653 654

18

General on MAP user procedures

18.1 Introduction

655 Clauses 18 to 25 describe the use of MAP services for GSM signalling procedures. GSM signalling procedures may 656 involve one or several interfaces running one or several application protocols. The present document addresses only the 657 signalling procedures which require at least the use of one MAP service. 658 659 660 661 662

When a signalling procedure takes place in the network, an application process invocation is created in each system component involved. Part of the application process invocation acts as a MAP user and handles one or several MAP dialogues. For each dialogue it employs an instance of the MAP service provider. It may also use other communication services to exchange information on other interfaces, but detailed description of these aspects is outside the scope of the present document.

663 664
665 666 667 668 669 670 671 672 673 674 675 676

18.2 Common aspects of user procedure descriptions

18.2.1 General conventions
For each signalling procedure the present document provides a brief textual overview accompanied by a flow diagram which represent the functional interactions between system components. Functional interactions are labelled using the MAP service name when the interaction results from a service request or by this service name followed by the symbol "ack" when this interaction results from a service response. For each of the system components involved, the present document also provides a detailed textual description of the application process behaviour as well as an SDL diagram. SDL diagrams describe the sequence of events, as seen by the MAP-User, which occurs at MAP service provider boundaries as well as external events which occur at other interfaces and which impact on the previous sequence. External events do not necessarily correspond to the messages of other protocols used in the system component. The MAP-user procedures are described as if a set of interworking functions (IWF) between the MAP-user and the other protocol entities was implemented (see figure 18.2/1). Such interworking functions are assumed to perform either an identity mapping or some processing or translation as required to eliminate information irrelevant to the MAP-user.

677 The mapping of service primitives on to protocol elements is described in clauses 14 to 17. 678 GSM signalling procedures are built from one or more sub-procedures (e.g. authentication, ciphering, ...). 679 Sub-procedures from which signalling procedures are built are represented using SDL MACRO descriptions. 680 In case of any discrepancy between the textual descriptions and the SDL descriptions, the latter take precedence.

681

18.2.2 Naming conventions

682 Events related to MAP are represented by MAP service primitives. The signal names used in the SDL diagrams are 683 derived from the service primitive names defined in clauses 7 to 12, with some lexical transformations for readability 684 and parsability purposes (blanks between words are replaced by underscores, the first letter of each word is capitalised). 685 Events received and sent on other interfaces are named by appending the message or signal name to a symbol 686 representing the interface type, with some lexical transformations for readability and parsability purposes (blanks 687 between words are replaced by underscores, the first letter of each word is capitalised). 688 The following symbols are used to represent the interface types: 689 690 691

"I": "A": "Gb":

For interfaces to the fixed network. "I" stands for ISUP interface. For interfaces between the MSC and the BSS (i.e. A-interfaces); For interfaces between the SGSN and the BSS (i.e. Gb-interfaces);

1668

1669

692 693 694 695

"OM": "SC": "HO_CA": "US":

For network management interfaces (communication with OMC, MML interface, ...); For interfaces to a Service Centre; For internal interfaces to the Handover Control Application. For a local USSD application.

696 These naming conventions can be summarised by the following BNF description: 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

<Event_Name> <MAP_Primitive>

::= <MAP_Primitive> | <External_Event> ::= <MAP_Open> | <MAP_Close> | <MAP_U_Abort> | <MAP_P_Abort> | <MAP_Specific> | <MAP_Notice>

<MAP_Open> <MAP_Close> <MAP_U_Abort> <MAP_P_Abort> <MAP_Notice> <MAP_Specific> <MAP_Req> <MAP_Ind> <MAP_Rsp> <MAP_Cnf> <External_Event> <Interface_Type> <External_Signal> <Service_Name> <Lexical_Unit>

::= MAP_Open_Req | MAP_Open_Ind | MAP_Open_Rsp | MAP_Open_Cnf ::= MAP_Close_Req | MAP_Close_Ind ::= MAP_U_Abort_Req | MAP_U_Abort_Ind ::= MAP_P_Abort_Ind ::= MAP_Notice_Ind ::= <MAP_Req> | <MAP_Ind> | <MAP_Rsp> | <MAP_Cnf> ::= MAP_<Service_Name>_Req ::= MAP_<Service_Name>_Ind ::= MAP_<Service_Name>_Rsp ::= MAP_<Service_Name>_Cnf ::= <Interface_Type>_<External_Signal> ::= I | A | Gb | OM | SC | HO AC | US ::= <Lexical_Unit> ::= <Lexical_Unit> ::= <Lexical_Component> | <Lexical_Unit>_ <Lexical_Component>

<Lexical_Component> ::= <Upper_Case_Letter><Letter_Or_Digit_List> <Letter_Or_Digit_List> ::= <Letter_Or_Digit> | <Letter_Or_Digit_List><Letter_Or_Digit> <Letter_Or_Digit> <Letter> <Upper_Case_Letter> ::= <Letter> | <Digit> ::= <Lower_Case_Letter> | <Upper_Case_Letter> ::= A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z

<Lower_Case_Letter> ::= a|b|c|d|e|f|g|h|i|j|k|l|m|n|o|p|q|r|s|t|u|v|w|x|y|z <Digit> ::= 1|2|3|4|5|6|7|8|9|0 Figure 18.2/1: Interfaces applicable to the MAP-User

723 724 18.2.3.1

18.2.3 Convention on primitives parameters

Open service

1670

1671

725 When the originating and destination reference parameters shall be included in the MAP-OPEN request primitive, their 726 value are indicated as a comment to the signal which represents this primitive.

727 18.2.3.2

Close service

728 When a pre-arranged released is requested, a comment is attached to the signal which represents the MAP-CLOSE 729 request primitive. In the absence of comment, a normal release is assumed.

730

18.2.4 Version handling at dialogue establishment

731 Unless explicitly indicated in subsequent clauses, the following principles regarding version handling procedures at 732 dialogue establishment are applied by the MAP-user.

733 18.2.4.1

Behaviour at the initiating side

734 When a MAP user signalling procedure has to be executed, the MAP-user issues a MAP-OPEN request primitive with 735 an appropriate application-context-name. If several names are supported (i.e. several versions) a suitable one is selected 736 using the procedures described in clause 5. 737 738 739 740 741 742

If version n is selected (where 1 < n <= highest existing version) and a MAP-OPEN Confirm primitive is received in response to the MAP-OPEN request with a result parameter set to "refused" and a diagnostic parameter indicating "application context not supported" or "potential version incompatibility problem", the MAP-User issues a new MAPOPEN request primitive with the equivalent version y context (where 1 <= y < n). This is informally represented in the SDL diagrams by task symbols indicating 'Perform Vr procedure".

743 18.2.4.2

Behaviour at the responding side

744 On receipt of a MAP-OPEN indication primitive, the MAP-User analyses the application-context-name and executes 745 the procedure associated with the requested version context. For example,if it refers to a version one context, the 746 associated V1 procedure is executed; if it refers to a version two context, the associated V2 procedure is executed;etc.

747

18.2.5 Abort Handling

748 Unless explicitly indicated in subsequent clauses, the following principles are applied by the MAP-user regarding abort 749 handling procedures: 750 On receipt of a MAP-P-ABORT indication or MAP-U-ABORT Indication primitive from any MAP-provider 751 invocation, the MAP-User issues a MAP-U-ABORT Request primitive to each MAP-provider invocation associated 752 with the same user procedure. 753 If applicable a decision is made to decide if the affected user procedure has to be retried or not.

754

18.2.6 SDL conventions

755 The MAP SDLs make use of a number of SDL concepts and conventions, where not all of them may be widely known. 756 Therefore, this clause outlines the use of a few concepts and conventions to improve understanding of the MAP SDLs. 757 758 759 760

The MAP User SDLs make use of SDL Processes, Procedures and Macros. Processes are independent from each other even if one process starts another one: The actions of both of them have no ordering in time. SDL Procedures and Macros are just used to ease writing of the specification: They contain parts of a behaviour used in several places, and the corresponding Procedure/Macro definition has to be expanded at the position of the Procedure/Macro call.

761 All Processes are started at system initialisation and live forever, unless process creation/termination is indicated 762 explicitly (i.e. a process is created by some other process). 763 The direction of Input/Output Signals in the SDL graphs is used to indicate the entity to which/from which 764 communication is directed. If a process A communicates in parallel with processes B and C, all Inputs/Outputs to/from 765 B are directed to one side, whereas communication with C is directed to the other side. However, there has been no

1672

1673

766 formal convention used that communication to a certain entity (e.g. a HLR) will always be directed to a certain side 767 (e.g. right). 768 769 770 771

In each state all those Input Signals are listed, which result in an action and/or state change. If an Input Signal is not listed in a state, receipt of this input should lead to an implicit consumption without any action or state change (according to the SDL rules). This implicit consumption is mainly used for receipt of the MAP DELIMITER indication and for receipt of a MAP CLOSE indication, except for a premature MAP CLOSE.

772
773 774 775 776 777 778 779 780 781 782 783 784 785

18.3 Interaction between MAP Provider and MAP Users

Each MAP User is defined by at least one SDL process. On the dialogue initiating side, the MAP User will create a new instance of a MAP Provider implicit by issuing a MAP-OPEN request. This instance corresponds to a TC Dialogue and lives as long as the dialogue exists (see also clause 14.3). There is a fixed relation between MAP User and this Provider instance, i.e. all MAP service primitives from the MAP User for this dialogue are sent to this instance and all TC components received by this MAP Provider are mapped onto service primitives sent to this MAP User. On the receiving side a MAP Provider instance is created implicit by receipt of a TC BEGIN indication. The corresponding MAP User is determined by the Application Context name included in this primitive, i.e. each Application Context is associated with one and only one MAP User. An instance of this User will be created implicitly by receiving a MAP-OPEN indication. Note that in some cases there exist several SDL Processes for one MAP User (Application Context), e.g. the processes Register_SS_HLR, Erase_SS_HLR, Activate_SS_HLR, Deactivate_SS_HLR, Interrogate_SS_HLR, and Register_Password for the AC Network_Functional_SS_Handling. In these cases, a coordinator process is introduced acting as a MAP User, which in turn starts a sub-process depending on the first MAP service primitive received.

1674

1675

786 787

19

Mobility procedures
19.1 Location management Procedures

788 The signalling procedures in this subclause support: 789 790 791 792 793 794 795 796 797 798

Interworking between the VLR and the HLR and between the VLR and the previous VLR (PVLR) when a nonGPRS subscriber performs a location update to a new VLR service area; Interworking between the SGSN, the HLR and the VLR when a subscriber with both GPRS and non-GPRS subscriptions performs a routeing area update in an SGSN and the Gs interface is implemented; Interworking between the SGSN and the VLR when a GPRS subscriber performs a routeing area update to a new SGSN service area; Interworking between the HLR and the VLR and between the HLR and the SGSN to delete a subscriber record from the VLR or the SGSN; Interworking between the VLR and the HLR and between the SGSN and the HLR to report to the HLR that a subscriber record has been purged from the VLR or the SGSN.

799 The MAP co-ordinating process in the HLR to handle a dialogue opened with the network location updating context is 800 shown in figure 19.1/1. The MAP process invokes a macro not defined in this clause; the definition of this macro can be 801 found as follows: 802

Receive_Open_Ind

see clause 25.1.1.

1676

1677

process Location_Management_Coordinator_HLR
Process in the HLR to handle a dialogue opening request using the application context netLocUpContext

LMC_HLR1(1)
Signals to/from the left are to/fromthe VLR; signals to/from the right are to/fromthe child process

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK

Error

Null

Null

Wait_For_ Service_ Primitive

MAP_UPDATE_ LOCATION_ind

MAP_RESTORE_ DATA_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Update_ Location_HLR

Figure 19.1.1/13

Restore_ Data_HLR

Figure 19.3.1/2

MAP_ CLOSE_req

MAP_UPDATE_ LOCATION_ind

MAP_RESTORE_ DATA_ind

Null

Relay_Info

MAP_U_ABORT_req, MAP_P_ABORT_req, MAP_CLOSE_req

MAP_U_ABORT_ind, MAP_CLOSE_ind

Null

Relay_Info

Null

Relay_Info

803
804

Figure 19.1/1: Process Location_Management_Coordinator_HLR

805 806 19.1.1.1

19.1.1 Location updating

General

807 The stage 2 specification for GPRS is in 3GPP TS 23.060 [104]. The interworking between the MAP signalling 808 procedures and the GPRS procedures in the SGSN and the HLR is shown by the transfer of signals between these 809 procedures.
1678

1679

810 The message flow for successful inter-VLR location updating when the IMSI can be retrieved from the PVLR is shown 811 in figure 19.1.1/2. 812 The message flow for successful inter-VLR location updating when the IMSI cannot be retrieved from the PVLR is 813 shown in figure 19.1.1/3. 814 The message flow for successful GPRS Attach/RA update procedure (Gs interface not installed) is shown in figure 815 19.1.1/4. 816 The message flow for successful GPRS Attach/RA update procedure combined with a successful VLR location 817 updating (Gs interface installed) is shown in figure 19.1.1/5.
MSC/ VLR 1

MS

PVLR

HLR

2 3 4 5 6 7 8 9 10 11

12

818
819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838

PVLR = Previous VLR 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) A_LU_REQUEST (Note 1) MAP_SEND_IDENTIFICATION_req/ind MAP_SEND_IDENTIFICATION_rsp/cnf MAP_UPDATE_LOCATION_req/ind MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf MAP_ACTIVATE_TRACE_MODE_req/ind (Note 2) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 2) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_LOCATION_rsp/cnf A_LU_CONFIRM (Note 1)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: Services printed in italics are optional.

839 840

Figure 19.1.1/2: Message flow for location updating to a new VLR area, when the IMSI can be retrieved from the previous VLR

1680

1681

841
MSC/ VLR 1 2 3

MS

PVLR

HLR

4 5 6 7 8 9 10 11

12

842
843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862

PVLR = Previous VLR 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) A_LU_REQUEST (Note 1) A_IDENTITY_REQUEST (Note 1) A_IDENTITY_RESPONSE (Note 1) MAP_UPDATE_LOCATION_req/ind MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf MAP_ACTIVATE_TRACE_MODE_req/ind (Note 2) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 2) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_LOCATION_rsp/cnf A_LU_CONFIRM (Note 1)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: Services printed in italics are optional.

863 864

Figure 19.1.1/3: Message flow for location updating to a new VLR area, when the IMSI cannot be retrieved from the previous VLR

1682

1683

MS

SGSN 1

PSGSN

HLR

2 3 4 5 6 7 8 9

10

865
866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887

PSGSN = Previous SGSN 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) Gb_ATTACH_REQUEST or RA_UPDATE_REQUEST (Note 1, note 2) MAP_UPDATE_GPRS_LOCATION_req/ind MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf MAP_ACTIVATE_TRACE_MODE_req/ind (Note 3) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 3) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_GPRS_LOCATION_rsp/cnf Gb_ATTACH_ACCEPT or RA_UPDATE_ACCEPT (Note 1)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. The services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For security functions (authentication, ciphering, IMEI check) triggering refer to 3GPP TS 23.060 [104]. The MAP signalling invoked for these functions is described in clause 25 of the present document. NOTE 3: Services printed in italics are optional. NOTE 4: Refer to 3GPP TS 23.060 [104] for termination of the procedure and triggering of the signalling on the interface between the BSS and the SGSN.

888

Figure 19.1.1/4: Message flow for GPRS location updating (Gs interface not installed)

1684

1685

MS

SGSN 1

VLR

PSGSN

HLR

2 3 4 5 6 7 8 9 10

11 12 13 14

16 17

15

18

889
890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18)

Gb_ATTACH_REQUEST or RA_UPDATE_REQUEST (Note 1, note 2) MAP_UPDATE_GPRS_LOCATION_req/ind MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf MAP_ACTIVATE_TRACE_MODE_req/ind (Note 3) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 3) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_GPRS_LOCATION_rsp/cnf Gs_LOCATION_UPDATE_REQUEST (Note 4) MAP_UPDATE_LOCATION_req/ind (Note 5) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_LOCATION_rsp/cnf Gs_LOCATION_UPDATE_ACCEPT (Note 4) Gb_ATTACH_ACCEPT or RA_UPDATE_ACCEPT (Note 1) Gb_TMSI_REALLOCATION_COMPLETE (Note 1) Gs_TMSI_REALLOCATION_COMPLETE (Note 4)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35]. The services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For security functions (authentication, ciphering, IMEI check) triggering refer to 3GPP TS 23.060 [104]. MAP processes invoked for those procedures are described in subclause 25.5. NOTE 3: Services printed in italics are optional.

1686

1687

924

916 917 918 919 920 921 922 923

NOTE 5: For details of the procedure on the path between the SGSN and the VLR, see 3GPP TS 29.018 [106]. The services shown in chain lines indicate the trigger provided by the signalling on the path between the SGSN and the VLR, and the signalling triggered on the path between the SGSN and the VLR. NOTE 4: Refer to 3GPP TS 23.060 [104] for termination of the procedure and triggering of the signalling on the interface between the BSS and the SGSN. NOTE 5: For simplicity, the Location Cancellation procedure towards the previous VLR and optional tracing activation towards the new VLR are not shown in this figure.

Figure 19.1.1/5: Message flow for GPRS location updating (Gs interface installed)

925 19.1.1.2

Procedures in the VLR

926 The MAP process in the VLR for location updating for a non-GPRS subscriber is shown in figure 19.1.1/6. The MAP 927 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 928 929

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

930 The MAP process in the VLR to retrieve the IMSI of a subscriber from the previous VLR (PVLR) is shown in figure 931 19.1.1/7. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as 932 follows: 933 934

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

935 The process in the VLR for location updating for a GPRS subscriber when the Gs interface is installed is shown in 936 figure 19.1.1/8. 937 The macro GPRS_Location_Update_Completion_VLR is shown in figure 19.1.1/9. The macro invokes a process not 938 defined in this clause; the definition of this process can be found as follows: 939

Subscriber_Present_VLR

see subclause 25.10.1.

940 The macro GPRS_Update_HLR_VLR is shown in figure 19.1.1/10. The macro invokes macros not defined in this 941 clause; the definitions of these macros can be found as follows: 942 943 944 945

Receive_Open_Cnf Check_Confirmation Insert_Subs_Data_VLR Activate_Tracing_VLR

see subclause 25.1.2; see subclause 25.2.2; see subclause 25.7.1; see subclause 25.9.4.

946 19.1.1.3

Procedure in the PVLR

947 The MAP process in the PVLR to handle a request for the IMSI of a subscriber from the new VLR is shown in figure 948 19.1.1/11. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as 949 follows: 950

Receive_Open_Ind

see subclause 25.1.1.

951 19.1.1.4

Procedure in the SGSN

952 The MAP process in the SGSN for location updating for a GPRS subscriber is shown in figure 19.1.1/12. The MAP 953 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 954 955 956

Receive_Open_Cnf Check_Confirmation Insert_Subs_Data_SGSN

see subclause 25.1.2; see subclause 25.2.2; see subclause 25.7.2;

1688

1689

957

Activate_Tracing_SGSN

see subclause 25.9.5.

958 Sheet 2: The procedure Check_User_Error_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 959 3GPP TS 23.116 [110].

960 19.1.1.5

Procedures in the HLR

961 The MAP process in the HLR to handle a location updating request from a VLR is shown in figure 19.1.1/13. The MAP 962 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 963

Check_Confirmation

see subclause 25.2.2.

964 The MAP process in the HLR to handle a location updating request from an SGSN is shown in figure 19.1.1/14. The 965 MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 966 967 968 969

Receive_Open_Ind Check_Indication Check_Confirmation

see subclause 25.1.1; see subclause 25.2.1; see subclause 25.2.2;

Control_Tracing_With_SGSN_HLR see subclause 25.9.7.

970 Sheet 2: The procedure Super_Charged_Cancel_Location_HLR is specific to Super-Charger; it is specified in 971 3GPP TS 23.116 [110]. If the HLR does not support the Super-Charger functionality, processing continues from the 972 "No" exit of the test "Result=Pass?". 973 Sheet 2: The procedure Super_Charged_Location_Updating_HLR is specific to Super-Charger; it is specified in 974 3GPP TS 23.116 [110]. If the HLR does not support the Super-Charger functionality, processing continues from the 975 "No" exit of the test "Result=Pass?". 976 Sheet 2: If the HLR supports the Administrative Restriction of Subscribers Access feature and roaming is allowed in 977 the VPLMN then the HLR may check the "Supported RAT Types" received from the VLR against the access restriction 978 parameters. If this check fails then the decision box "Roaming allowed in this PLMN" shall take the exit "No". 979 The MAP process in the HLR to notify Short Message Service Centres that a subscriber is now reachable is shown in 980 figure 19.1.1/15. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found 981 as follows: 982

Alert_Service_Centre_HLR

see subclause 25.10.3.

1690

1691

process Update_Location_VLR
Process in the VLR to handle a location updating dialogue with the HLR when the Gs interface is not used

UL_VLR1(2)
Signals to/from the l eft are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/fromthe HLR

Null

Update Location

MAP_OPEN_req MAP_UPDATE_LOCATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error Set negative response: System failure

Vr Perform MAP Vr dialogue

OK Wait_For_ HLR_Response

Update Location negative response

MAP_ ACTIVATE_ TRACE_ MODE_ind

MAP_INSERT_ SUBSCRIBER_ DATA_ind

Null

Result

Activate Trace Mode

Insert Subscriber Data

Unknown Subscriber Set negative response: Unknown subscriber

Roam ing not allowed Set negative response: Roam ing not allowed

Procedure error Set negative response: Procedure error

Aborted Set negative response: Aborted

HLR num ber Wait_For_HLR_ Or_Application_ Response

Update Location negative response

Update Location ack

Null

Null

983
984

Figure 19.1.1/6 (sheet 1 of 2): Process Update_Location_VLR

1692

1693

process Update_Location_VLR
Process in the VLR to handle a location updating dialogue with the HLR when the Gs interface is not used Wait_For_HLR_ Or_Application_ Response

UL_VLR2(2)

Activate Trace Mode ack

Activate Trace Mode negative response

Insert Subscriber Data ack

Insert Subscriber Data negative response

MAP_INSERT_ SUBSCRIBER_ DATA_ind

MAP_ FORWARD_ CHECK_SS_ ind

Set User Error

Set User Error

MAP_ ACTIVATE_ TRACE_ MODE_rsp

MAP_INSERT_ SUBSCRIBER_ DATA_rsp

Insert Subscriber Data

Forward Check SS

Signals to/from the l eft are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/fromthe HLR

Wait_For_HLR_ Or_Application_ Response

Wait_For_HLR_Response, Wait_For_HLR_Or_Application_Response

MAP_UPDATE_ LOCATION_ cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK Set negative response: System failure

Set negative response

Update Location negative response

Update Location ack

Update Location negative response

Null

Null

Null

985
986

Figure 19.1.1/6 (sheet 2 of 2): Process Update_Location_VLR

1694

1695

process Send_Identification_VLR
Process in the VLR to request IMSI and authentication information from the previous VLR

SI_VLR1(2)
Signals to/from the l eft are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/fromthe PVLR Null

Send Identifi cation

MAP_OPEN_req MAP_SEND_IDENTIFICATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error Set negative response: System failure

Vr Perform MAP Vr dialogue

OK Wait_For_ PVLR_Response

No IMSI received? Yes MAP_SEND_IDENTIFICATION_cnf

Send Identifi cation negative response

Send Identifi cation ack

Check_ Confirmation

OK Wait_For_ Dialogue_ End

User Error, Provider Error, Data Error

Null

Null

MAP_ DELIMITER_ ind

MAP_ CLOSE_ ind

No IMSI received? Yes

MAP_SEND_IDENTIFICATION_req MAP_DELIMITER_req

Send Identifi cation ack

Send Identification negative response

Send Identifi cation ack

Wait_For_ PVLR_Response

Null

Null

Null

987
988

Figure 19.1.1/7 (sheet 1 of 2): Process Send_Identification_VLR

1696

1697

process Send_Identification_VLR
Process in the VLR to request IMSI and authentication information from the previous VLR Wait_For_ PVLR_Response

SI_VLR2(2)
Signals to/from the l eft are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/fromthe PVLR MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Abort

MAP_ NOTICE_ ind

Null

MAP_ CLOSE_ req

No IMSI received? Yes

Send Identifi cation negative response

Send Identifi cation ack

Null

Null

989
990

Figure 19.1.1/7 (sheet 2 of 2): Process Send_Identification_VLR

1698

1699

process GPRS_Update_Location_Area_VLR
Process in the VLR to handle an Update Location Area request received over the Gs interface

GULA_VLR1(2)
Signals to/from the l eft are to/fromthe SGSN

Null

Gs_GPRS_LOCATION_UPDATING_ind

Yes Subscriber known? No Location Information Confirmed in HLR:=False

Confirmed by Radio Contact:= True

Update LAI

No VLR-SGSN association exists? Yes Create association Update association

Yes HLR update required? No GPRS_Location_ Update_ Completion_VLR

Update register

Null

991
992

Figure 19.1.1/8 (sheet 1 of 2): Process GPRS_Update_Location_Area_VLR

1700

1701

process GPRS_Update_Location_Area_VLR
Process in the VLR to handle an Update Location Area request received over the Gs interface 1

GULA_VLR2(2)
Signals to/from the left are to/from the SGSN

GPRS_Update_ HLR_VLR Unknown_Subscriber, Roaming_Not_Allowed Delete subscriber record

OK GPRS_Location_ Update_ Completion_VLR

Procedure_Error

Update register

Set User Error

See 3GPP TS 29.018

Null

Gs_GPRS_LOCATION_UPDATING_rsp

Null

993
994

Figure 19.1.1/8 (sheet 2 of 2): Process GPRS_Update_Location_Area_VLR

1702

1703

macrodefinition GPRS_Location_Update_Completion_VLR
Macro in the VLR to complete the local handl ing of an Update Location Area request received over the Gs interface No Roaming allowed in target LA? Yes

GLUC_VLR1(1)
Signals to/from the left are to/fromthe SGSN

LA not allowed:= True

LA not allowed:=False IM detached:=False SI

Set User Error

See 3GPP TS 29.018

Subscriber_ Present_VLR

No Gs_GPRS_LOCATION_ UPDATING_rsp TMSI reallocation required? Yes

Allocate TMSI

Set result

Set TMSI parameter

Gs_GPRS_LOCATION_ UPDATING_rsp

Start TM SI reallocation timer

Gs_GPRS_LOCATION_UPDATING_rsp

Wait_For_ TMSI_Allocation_ Confirm

GS_GPRS_TMSI_REALLOCATION_COMPLETE_ind

TMSI reallocation timer expired

Internal

Freeze old TMSI

995
996

Figure 19.1.1/9: Macro GPRS_Location_Update_Completion_VLR

1704

1705

macrodefinition GPRS_Update_HLR_VLR
Macro in the VLR to handle a location updating dialogue with the HLR when the Gs interface is used No

GUHLR_VLR1(2)
Signals to/from the right are to/fromthe HLR

HLR address known? Yes

MAP_OPEN_req MAP_UPDATE_LOCATION_req MAP_DELIMITER_req

Roaming_Not_ Allowed

Receive_ Open_Cnf

Error Procedure_ Error

Vr Perform MAP_Vr dialogue

OK Wait_For_ HLR_Response

Result? Procedure error, Aborted

Unknown subscriber Procedure_ Error Unknown_ Subscriber

Roam not allowed ing Roaming_ Not_Allowed

HLR number

OK

Wait_For_ HLR_Response

Insert_Subs_ Data_VLR

Activate_ Tracing_VLR

MAP_FORWARD_ CHECK_SS_ INDICATION_ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Wait_For_ HLR_Response

Wait_For_ HLR_Response

Wait_For_ HLR_Response

MAP_ CLOSE_ req

Subscriber data confirmed by HLR:=False; Location information confirm in HLR:=False ed

Procedure_ Error

997
998

Figure 19.1.1/10 (sheet 1 of 2): Macro GPRS_Update_HLR_VLR

1706

1707

macrodefinition GPRS_Update_HLR_VLR
Macro in the VLR to handle a location updating dialogue with the HLR when the Gs interface is used Wait_For_ HLR_Response

GUHLR_VLR2(2)
Signals to/from the right are to/fromthe HLR

MAP_UPDATE_LOCATION_cnf

Check_ Confirmation Provider Error, Data Error

OK

User Error

Subscriber data confirmed by HLR:=True; Location information confirm in HLR:=True ed

Subscriber data confirmed by HLR:=False; Location information confirm in HLR:=False ed

OK

Procedure_ Error

User error

Unknown subscriber

Roam not allowed ing

Else

Unknown_ Subscriber

Roaming_ Not_Allowed

Subscriber data confirmed by HLR:=False; Location information confirm in HLR:=False ed

Procedure_ Error

999
1000

Figure 19.1.1/10 (sheet 2 of 2): Macro GPRS_Update_HLR_VLR

1708

1709

process Send_Identification_PVLR
Process in the PVLR to handle a request for IMSI and authenticati on information from the new VLR

SI_PVLR1(2)
Signals to/from the l eft are to/fromthe new VLR; signals to/from the right are to/fromthe location managem application ent process in the PVLR (see 3GPP TS 23.012)

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Primitive

Error

Null

Null

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

MAP_SEND_IDENTIFICATION_ind

MAP_ CLOSE_ req

Send Identifi cation

Null

Wait_For_ Application_ Response

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Send Identifi cation negative response

MAP_ CLOSE_ req

Set User Error

Abort

MAP_SEND_IDENTIFICATION_rsp MAP_CLOSE_req

Null

Null

1001
1002

Figure 19.1.1/11 (sheet 1 of 2): Process Send_Identification_PVLR

1710

1711

process Send_Identification_PVLR
Process in the PVLR to handle a request for IMSI and authenticati on information from the new VLR Wait_For_ Application_ Response

SI_PVLR2(2)
Signals to/from the l eft are to/fromthe new VLR; signals to/from the right are to/fromthe location managem application ent process in the PVLR (see 3GPP TS 23.012)

Send Identification ack

MAP_SEND_IDENTIFICATION_rsp

No More authenti cation sets to send? Yes

No Segmentation allowed? Yes

MAP_ CLOSE_ req

MAP_ DELIMITER_ req

Null

Wait_For_ Next_ Request

MAP_SEND_IDENTIFICATION_ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ CLOSE_ req

Abort

Null

1003
1004

Figure 19.1.1/11 (sheet 2 of 2): Process Send_Identification_PVLR

1712

1713

process Update_GPRS_Location_SGSN
Process in the SGSN to handle a location updating dialogue with the HLR

UGL_SGSN1(2)
Signals to/from the left are to/fromthe GPRS mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/fromthe HLR

Null

Update Location

HLR address known? Yes

No

MAP_OPEN_req MAP_UPDATE_GPRS_LOCATION_req MAP_DELIMITER_req

Set negative response: Unknown HLR

Receive_ Open_Cnf

Update Location negative response

Vr, Error Set negative response: Procedure error

OK

Wait_For_ HLR_Response

Null

Update Location negative response

Abort

Insert_Subs_ Data_SGSN

Activate_ Tracing_SGSN

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Null

MAP_U_ ABORT_ req

Wait_For_ HLR_Response

Wait_For_ HLR_Response

MAP_ CLOSE_ req

Null

Set negative response: Procedure error

Update Location negative response

Null

1005
1006

Figure 19.1.1/12 (sheet 1 of 2): Process Update_GPRS_Location_SGSN

1714

1715

process Update_GPRS_Location_SGSN
Process in the SGSN to handle a location updating dialogue with the HLR Wait_For_ HLR_Response

UGL_SGSN2(2)
Signals to/from the left are to/fromthe GPRS mobility management application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/fromthe HLR MAP_UPDATE_GPRS_LOCATION_cnf

Check_ Confirmation

User Error Check_User_ Error_In_Serving_ Network_Entity

OK

Provider Error, Data Error

See 3GPP TS 23.116

Set negative response

Set result

Set negative response: Procedure error

Update Location negative response

Update Location ack

Update Location negative response

Null

Null

Null

1007
1008

Figure 19.1.1/12 (sheet 2 of 2): Process Update_GPRS_Location_SGSN

1716

1717

process Update_Location_HLR
Process in the HLR to handle an Update Location request from a VLR

UL_HLR1(3)
Signals to/from the left are to/fromthe VLR; signals to/from the right are to/fromthe location managem application ent process in the HLR (see 3GPP TS 23.012)

Null

MAP_UPDATE_LOCATION_ind

Update Location

Wait_For_ Application_ Response

Update Location ack

Update Location negative response

Activate Trace Mode

Insert Subscriber Data

Set Result

Set User Error

MAP_ACTIVATE_TRACE_M ODE_req MAP_DELIMITER_req

MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Wait_For_ ATM_Cnf

Wait_For_ ISD_Cnf_Or_ Application_ Response

MAP_UPDATE_LOCATION_rsp MAP_CLOSE_req

1009
1010

Figure 19.1.1/13 (sheet 1 of 3): Process Update_Location_HLR

1718

1719

process Update_Location_HLR
Process in the HLR to handle an Update Location request from a VLR Wait_For_ ATM_Cnf

UL_HLR2(3)
Signals to/from the l eft are to/fromthe VLR; signals to/from the right are to/fromthe location managem application ent process in the HLR (see 3GPP TS 23.012)

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ACTIVATE_TRACE_M ODE_cnf

Abort

MAP_ CLOSE_ req

Check_ Confirmation

Provider Error Set negative response: System failure

Data Error Set negative response: System failure

User Error

OK

Set negative response

Activate Trace Mode negative response

Activate Trace Mode negative response

Activate Trace Mode ack

Wait_For_ Application_ Response

Wait_For_ ISD_Cnf_Or_ Application_ Response

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Insert Subscriber Data

Abort

Set negative response: System failure

Insert Subscriber Data negative response

MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Wait_For_ ISD_Cnf_Or_ Application_ Response

1011
1012

Figure 19.1.1/13 (sheet 2 of 3): Process Update_Location_HLR

1720

1721

process Update_Location_HLR
Process in the HLR to handle an Update Location request from a VLR Wait_For_ ISD_Cnf_Or_ Application_ Response

UL_HLR3(3)
Signals to/from the l eft are to/fromthe VLR; signals to/from the right are to/fromthe location managem application ent process in the HLR (see 3GPP TS 23.012)

Update Location ack

Update Location negative response

MAP_INSERT_SUBSCRIBER_DATA_cnf

Set Result

Set User Error

Check_ Confirmation

OK

User Error

Data Error Set negative response: System failure

Provider Error Set negative response: System failure

Set negative response

MAP_UPDATE_LOCATION_rsp MAP_CLOSE_req

Insert Subscriber Data ack

Insert Subscriber Data negative response

Insert Subscriber Data negative response

Wait_For_ ISD_Cnf_Or_ Application_ Response

1013
1014

Figure 19.1.1/13 (sheet 3 of 3): Process Update_Location_HLR

1722

1723

process Update_GPRS_Location_HLR
Process in the HLR to handle an Update GPRS Location request from an SGSN

UGL_HLR1(2)
Signals to/from the left are to/fromthe SGSN; signals to/from the right are to/fromthe GPRS mobility management application process in the HLR (see 3GPP TS 23.060)

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Primitive

Vr, Error

Null

MAP_P_ ABORT_ ind

MAP_UPDATE_GPRS_LOCATION_ind

MAP_ NOTICE_ ind

Null

Check_ Indication

MAP_ CLOSE_ req

Error MAP_UPDATE_GPRS_LOCATION_rsp MAP_CLOSE_req

OK No Subscriber known? Yes Set diagnostic: IMSI unknown Network Access Mode? Else Non-GPRS only Null

Null

Set diagnostic: GPRS subscription unknown

Subscriber tracing active in SGSN:= False

Set User Error: Unknown subscriber

MAP_UPDATE_GPRS_LOCATION_rsp MAP_CLOSE_req

Null

1015
1016

Figure 19.1.1/14 (sheet 1 of 2): Process Update_GPRS_Location_HLR

1724

1725

process Update_GPRS_Location_HLR
Process in the HLR to handle an Update GPRS Location request from an SGSN No New SGSN? Yes Super_Charged_ Cancel_ Location_HLR 1

UGL_HLR2(2)

See 3GPP TS 23.116

Yes Result= Pass? No Cancel _GPRS_ Location_ Child_HLR

No Roaming allowed in this PLMN? Yes

Delete Routeing Info

Update Routeing Info; MS Purged for GPRS:=False

Set User Error: Roam not ing allowed

Control_Tracing_ With_SGSN_HLR

OK MAP_UPDATE_GPRS_LOCATION_rsp MAP_CLOSE_req Super_Charged_ Location_ Updating_HLR

Error

See 3GPP TS 23.116

Null

Yes Null Result= Pass? No Insert_GPRS_ Subs_Data_ Framed_HLR

OK Subscriber_ Present_HLR

Error Set User Error: System failure

Aborted

Null

MAP_UPDATE_GPRS_LOCATION_rsp MAP_CLOSE_req

Null

1017
1018

Figure 19.1.1/14 (sheet 2 of 2): Process Update_GPRS_Location_HLR

1726

1727

process Subscriber_Present_HLR
Process in the HLR to alert SMS service centres if required as part of the location updating process for a GPRS or non-GPRS subscriber

SP_HLR1(1)

No Message waiting data set? Yes

Alert_ Service_Centre_ HLR

1019
1020

Figure 19.1.1/15: Process Subscriber_Present_HLR

1728

1729

1021 1022 19.1.2.1

19.1.2 Location Cancellation

General

1023 Location cancellation is used to delete a subscriber record from the serving node (VLR or SGSN). The procedure is 1024 invoked: 1025 1026 1027 1028 1029

because the subscriber has registered with a new serving node, or because the HPLMN operator has decided to delete the subscriber record from the serving node, e.g. because the subscription has been withdrawn, or because roaming restrictions have been imposed. Location cancellation can be used to force location updating including updating of subscriber data in the serving node at the next subscriber access.

1030 The message flow for location cancellation for a non-GPRS subscriber is shown in figure 19.1.2/1. 1031 The message flow for location cancellation for a GPRS subscriber is shown in figure 19.1.2/2.

VLR 1

HLR

PVLR

2 3

1032
1033 1034 1035 1036 1037 1038 1039

1) 2) 3) NOTE:

MAP_UPDATE_LOCATION_req/ind MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf The service shown in dotted lines indicates the trigger provided by other MAP signalling.

1040

Figure 19.1.2/1: Message flow for Location Cancellation (non-GPRS)

SGSN 1

HLR

PSGSN

2 3

1041
1042 1043 1044 1045 1046 1047 1048

1) 2) 3) NOTE:

MAP_UPDATE_GPRS_LOCATION_req/ind MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf The service shown in dotted lines indicates the trigger provided by other MAP signalling.

1049

Figure 19.1.2/2: Message flow for Location Cancellation (GPRS)

1050 19.1.2.2

Procedure in the HLR

1051 The MAP process in the HLR to cancel the location information in a VLR is shown in figure 19.1.2/3. The MAP 1052 process invokes macros not defined in this clause; the definitions of these macros can be found as follows:
1730

1731

1053 1054

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1055 The MAP process in the HLR to cancel the location information in a VLR as an independent process invoked from 1056 another process is shown in figure 19.1.2/4. 1057 The MAP process in the HLR to cancel the location information in an SGSN is shown in figure 19.1.2/5. The MAP 1058 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 1059 1060

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1061 The MAP process in the HLR to cancel the location information in an SGSN as an independent process invoked from 1062 another process is shown in figure 19.1.2/6.

1063 19.1.2.3

Procedure in the VLR

1064 The MAP process in the VLR to handle a location cancellation request is shown in figure 19.1.2/7. The MAP process 1065 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1066

Receive_Open_Ind

see subclause 25.1.1.

1067 19.1.2.4

Procedure in the SGSN

1068 The MAP process in the SGSN to handle a location cancellation request is shown in figure 19.1.2/8. The MAP process 1069 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1070

Receive_Open_Ind

see subclause 25.1.1.

1732

1733

1071

process Cancel_Location_HLR
Process in the HLR to cancel the information stor ed in a VLR

CL_HLR1(1)
Signals to/from the left are to/fromthe VLR; signals to/from the right are to/fromthe location managem application ent process in the HLR (see 3GPP TS 23.012) or the process Cancel_Location_ Child_HLR Null

Cancel Location

MAP_OPEN_req MAP_CANCEL_LOCATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK Wait_For_ VLR_Response

Error

Null

MAP_P_ ABORT_ ind

MAP_ CANCEL_ LOCATION_ cnf

MAP_ NOTICE_ ind

Abort

Check_ Confirmation Provider Error, Data Error Set negative response: System failure

MAP_ CLOSE_ req

OK

User Error Set negative response Set negative response: System failure

Null

Cancel Location negative response

Cancel Location ack

Cancel Location negative response

Cancel Location negative response

Null

Null

Null

Null

1072
1073

Figure 19.1.2/3: Process Cancel_Location_HLR

1734

1735

process Cancel_Location_Child_HLR
Child process in the HLR to cancel the information stor ed in a VLR

CLC_HLR1(1)
Signals to/from the l eft are to/fromthe process Cancel_Location_HLR

Cancel Location

Wait_For_ VLR_Response

Cancel Location negative response

Cancel Location ack

1074
1075

Figure 19.1.2/4: Process Cancel_Location_Child_HLR

1736

1737

process Cancel_GPRS_Location_HLR
Process in the HLR to cancel the information stor ed in an SGSN Wait_For_ Repeat_Attempt_ Timer_Expiry

CGL_HLR1(1)
Signals to/from the left are to/fromthe VLR; signals to/from the right are to/fromthe GPRS mobility management application process in the HLR (see 3GPP TS 23.060) or the process Cancel_GPRS_ Location_Child_HLR unless marked otherwise

Null

Internal

Repeat attempt timer expired

Cancel GPRS Location

MAP_OPEN_req MAP_CANCEL_GPRS_LOCATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ VLR_Response

Vr, Error Set negative response: System failure

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

MAP_ CANCEL_ LOCATION_ cnf

Cancel GPRS Location negative response

MAP_ CLOSE_ req

Check_ Confirmation

Null

Provider Error, Data Error Yes Repeat attempt? No

OK

User Error Yes Repeat attempt? No

Start Repeat attempt timer

Set negative response: System failure

Set negative response

Start Repeat attempt timer

Wait_For_ Repeat_Attempt_ Timer_Expiry

Cancel GPRS Location negative response

Cancel GPRS Location ack

Cancel GPRS Location negative response

Wait_For_ Repeat_Attempt_ Timer_Expiry

Null

Null

Null

1076
1077

Figure 19.1.2/5: Process Cancel_GPRS_Location_HLR

1738

1739

process Cancel_GPRS_Location_Child_HLR
Child process in the HLR to cancel the information stor ed in an SGSN

CGLC_HLR1(1)
Signals to/from the left are to/fromthe process Cancel_GPRS_Location_HLR

Cancel GPRS Location

Wait_For_ SGSN_Response

Cancel GPRS Location negative response

Cancel GPRS Location ack

1078
1079

Figure 19.1.2/6: Process Cancel_GPRS_Location_Child_HLR

1740

1741

process Cancel_Location_VLR
Process in the VLR to handle a Cancel Location request

CL_VLR1(1)
Signals to/from the left are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/fromthe HLR

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Primitive

Error

Null

Null

MAP_ NOTICE_ ind

MAP_CANCEL_LOCATION_ind

MAP_P_ ABORT_ ind

MAP_ CLOSE_ req

Cancel Location

Null

Null

Wait_For_ Application_ Response

Cancel Location ack

Cancel Location negative response

Set Result

Set User Error

MAP_CANCEL_LOCATION_rsp MAP_CLOSE_req

Null

1080
1081

Figure 19.1.2/7: Process Cancel_Location_VLR

1742

1743

process Cancel_Location_SGSN
Process in the SGSN to handle a Cancel Location request

CGL_SGSN1(1)
Signals to/from the right are to/fromthe HLR

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Primitive

Vr, Error

Null

MAP_ NOTICE_ ind

MAP_CANCEL_LOCATION_ind

MAP_P_ ABORT_ ind

MAP_ CLOSE_ req

Check_ Indication

Null

Error

OK No

Null

Subscriber registered? Yes

Delete subscriber record

Release P-TMSI

MAP_CANCEL_LOCATION_rsp MAP_CLOSE_req

Null

1082
1083

Figure 19.1.2/8: Process Cancel_Location_SGSN

1744

1745

1084 1085 1086 19.1.4.1

19.1.3 Void 19.1.4 MS Purging

General

1087 O&M procedures in the VLR or SGSN can trigger MS purging either because of administrative action or because the 1088 MS has been inactive for an extended period. The O&M process in the VLR or in the SGSN should ensure that during 1089 the MS purging procedure any other attempt to access the MS record is blocked, to maintain consistency of data. 1090 The message flow for a VLR to report MS purging to the HLR is shown in figure 19.1.4/1. 1091 The message flow for an SGSN to report MS purging to the HLR is shown in figure 19.1.4/2.

VLR 1 2

HLR

1092
1093 1094 1095 1096

1) 2)

MAP_PURGE_MS_req/ind MAP_PURGE_MS_rsp/cnf

1097
1098

Figure 19.1.4/1: Message flow for MS purging (non-GPRS)

SGSN 1 2

HLR

1099
1100 1101 1102 1103

1) 2)

MAP_PURGE_MS_req/ind MAP_PURGE_MS_rsp/cnf

1104

Figure 19.1.4/2: Message flow for MS purging (GPRS)

1105 19.1.4.2

Procedure in the VLR

1106 The MAP process in the VLR to report MS purging to the HLR is shown in figure 19.1.4/3. The MAP process invokes 1107 macros not defined in this clause; the definitions of these macros can be found as follows: 1108 1109

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1110 19.1.4.3

Procedure in the SGSN

1111 The MAP process in the SGSN to report MS purging to the HLR is shown in figure 19.1.4/4. The MAP process invokes 1112 macros not defined in this clause; the definitions of these macros can be found as follows:

1746

1747

1113 1114

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1115 Sheet 1: The procedure Purge_MS_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3GPP 1116 TS 23.116 [110]. If the HLR does not support the Super-Charger functionality, processing continues from the "No" exit 1117 of the test "Result=Pass?".

1118 19.1.4.4

Procedure in the HLR

1119 The MAP process in the HLR to handle a notification from a VLR or an SGSN that an MS record has been purged is 1120 shown in figure 19.1.4/5. The MAP process invokes macros not defined in this clause; the definitions of these macros 1121 can be found as follows: 1122 1123

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

1124 If the notification was received from a VLR, the MAP process communicates with the location management application 1125 process specified in 3GPP TS 23.012 [23]; if the notification was received from an SGSN, the MAP process 1126 communicates with the GPRS mobility management application process specified in 3GPP TS 23.060 [104].

1748

1749

1127

process Purge_MS_VLR
Process in the VLR to report purging to the HLR

PMS_VLR1(1)
Signals to/from the l eft are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012); signals to/from the right are to/fromthe HLR

Null

Purge MS

MAP_OPEN_req MAP_PURGE_MS_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK Wait_For_ HLR_Response

Error

Null

MAP_ PURGE_MS_ cnf

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error, Data Error Set negative response: System failure

MAP_ CLOSE_ req

OK

User Error Set negative response

Set negative response: System failure

Purge MS ack

Purge MS negative response

Purge MS negative response

Null

Null

Null

1128
1129

Figure 19.1.4/3: Process Purge_MS_VLR

1750

1751

process Purge_MS_SGSN
Process in the SGSN to report purging to the HLR

PMS_SGSN1(2)
Signals to/from the left are to/fromthe O&M application in the SGSN; signals to/from the right are to/fromthe HLR

Null

OM_PURGE_ MS_ind

Purge_M S_In Serving_Network_ Entity

See3GPP TS 23.116

Yes Result= Pass? No MAP_OPEN_req MAP_PURGE_MS_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Error

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

MAP_ CLOSE_ req

Set User Error: System failure

OM_PURGE_ MS_rsp

Null

1130
1131

Figure 19.1.4/4 (sheet 1 of 2): Process Purge_MS_SGSN

1752

1753

process Purge_MS_SGSN
Process in the SGSN to report purging to the HLR Wait_For_ HLR_Response

PMS_SGSN2(2)
Signals to/from the left are to/fromthe O&M application in the SGSN; signals to/from the right are to/fromthe HLR

MAP_ PURGE_MS_ cnf

Check_ Confirmation Provider Error, Data Error

OK Delete subscriber data

User Error

Set User Error

Set User Error: System failure

No Freeze P-TMSI? Yes

Freeze P-TMSI

Set Result

OM_PURGE_ MS_rsp

Null

1132
1133

Figure 19.1.4/4 (sheet 2 of 2): Process Purge_MS_SGSN

1754

1755

process Purge_MS_HLR
Process in the HLR to handle a notifi cation from the VLR or the SGSN that an MS has been purged

PMS_HLR1(1)
Signals to/from the left are to/fromthe VLR; signals to/from the right are to/fromthe location managem application ent process in the HLR (see 3GPP TS 23.012) or the GPRS location m anagement application process in the HLR (see 3GPP TS 23.060)

Null

Receive_ Open_Ind

Vr

OK Wait_For_ Service_ Primitive

V1, Error

Perform MAP Vr dialogue

Null

Null

MAP_P_ ABORT_ ind

MAP_PURGE_MS_ind

MAP_ NOTICE_ ind

Null

Purge MS

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Null

Purge MS ack

Purge MS negative response

Set Result

Set User Error

MAP_PURGE_MS_rsp MAP_CLOSE_req

Null

1134
1135

Figure 19.1.4/5: Process Purge_MS_HLR

1756

1757

1136 1137

19.2 Handover procedures

19.2.1 General

1138 In this subclause, the term "Inter-MSC handover" is used to denote handover or relocation between different MSCs. 1139 The interfaces involved for Inter-MSC handover are shown in figure 19.2/1. There are two Inter-MSC handover 1140 procedures: 1141 1142 1143 1144 1145 1146 1147 1148 1149

1) Basic Inter-MSC handover: The call is handed over from the controlling MSC(MSCA) to another MSC(MSCB) (figure 19.2/1a). Figure 19.2/2 shows the message flow for a successful handover from MSC-A to MSCB, including a request for handover number allocation from MSC-B to VLR-B. 2) Subsequent Inter-MSC handover: After the call has been handed over from MSC-A to MSC-B, a further handover either to MSC-A (figure 19.2/1a) or to a third MSC (MSC-B') (figure 19.2/1b) may be necessary in order to continue the call. Figure 19.2/3 shows the message flow for a successful subsequent handover to MSC-B'. For a successful subsequent handover to MSC-A, the messages to and from MSC-B' and VLR-B' are omitted..

MSC-A

MSC-B E B

VLR-B

1150
1151 1152

a) Basic handover procedure MSC-A to MSC-B and subsequent handover procedure MSC-B to MSC-A.

MSC-A E

MSC-B B

VLR-B

MSC-B'

VLR-B' B

1153
1154 1155

b) Subsequent handover procedure MSC-B to MSC-B'. Figure 19.2/1: Interface structure for handover

1758

1759

MSC-A

MSC-B 1

VLR-B

2 3

5 6 7 8 9 10

1156
1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) NOTE:

MAP_PREPARE_HANDOVER_req/ind MAP_ALLOCATE_HANDOVER_NUMBER_req/ind MAP_SEND_HANDOVER_REPORT_req/ind MAP_PREPARE_HANDOVER_rsp/cnf MAP_SEND_HANDOVER_REPORT_rsp/cnf (Note) MAP_PROCESS_ACCESS_SIGNALLING_req/ind MAP_SEND_END_SIGNAL_req/ind MAP_FORWARD_ACCESS_SIGNALLING_req/ind MAP_PROCESS_ACCESS_SIGNALLING_req/ind MAP_SEND_END_SIGNAL_rsp/cnf This can be sent at any time after the connection between MSC-A and MSC-B is established.

1171

Figure 19.2/2: Example of a successful basic handover procedure to MSC-B

1760

1761

MSC-A

MSC-B 1

VLR-B

MSC-B'

VLR-B'

2 3

5 6 7 8 9

10 11

12

13 14 15 16 17

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

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17)

MAP_PREPARE_HANDOVER_req/ind MAP_ALLOCATE_HANDOVER_NUMBER_req/ind MAP_SEND_HANDOVER_REPORT_req/ind MAP_PREPARE_HANDOVER_rsp/cnf MAP_SEND_HANDOVER_REPORT_rsp/cnf (Note 1) MAP_PROCESS_ACCESS_SIGNALLING_req/ind MAP_SEND_END_SIGNAL_req/ind MAP_PREPARE_SUBSEQUENT_HANDOVER_req/ind MAP_PREPARE_HANDOVER_req/ind MAP_ALLOCATE_HANDOVER_NUMBER_req/ind MAP_SEND_HANDOVER_REPORT_req/ind MAP_PREPARE_HANDOVER_rsp/cnf MAP_SEND_HANDOVER_REPORT_rsp/cnf (Note 2) MAP_PREPARE_SUBSEQUENT_HANDOVER_rsp/cnf MAP_PROCESS_ACCESS_SIGNALLING_req/ind MAP_SEND_END_SIGNAL_req/ind MAP_SEND_END_SIGNAL_rsp/cnf (Note 3)

NOTE 1: This can be sent at any time after the connection between MSC-A and MSC-B is established. NOTE 2: This can be sent at any time after the connection between MSC-A and MSC-B' is established. NOTE 3: At this stage, the subsequent handover is complete. Any further interworking between MSC-A and MSC-B' is the same as the interworking between MSC-A and MSC-B after basic handover

1197

Figure 19.2/3: Example of a successful subsequent handover to a third MSC

1762

1763

1198 The MAP signalling procedures for inter-MSC handover support the allocation of a handover number or one or more 1199 relocation numbers and the transfer of encapsulated BSSAP or RANAP messages. 1200 The minimum application context version for the MAP handover application context shall be: 1201 1202 1203 1204 1205

version 3 for inter-MSC UTRAN to UTRAN handover; version 3 for inter-MSC intersystem handover from GSM BSS to UTRAN; version 2 for inter-MSC intersystem handover from UTRAN to GSM BSS. If the MAP handover application context version 2 is used, subsequent handover to UTRAN is not possible.

NOTE:

1206 The minimum application context version for the MAP handover application context should be version 2 for inter-MSC 1207 handover from GSM BSS to GSM BSS. 1208 1209 1210 1211 1212 1213 1214 1215

NOTE:

If the MAP handover application context version 2 or lower is used, subsequent handover to UTRAN is not possible.

The BSSAP or RANAP messages encapsulated in MAP messages are processed by the Handover Control Application in each MSC. The information in the encapsulated BSSAP or RANAP messages is passed from the Handover Control Application to the MAP process at the sending end; the notation used in the SDL diagrams for the MAP processes is "HO_CA_MESSAGE_ind(Message transfer)". The information in the encapsulated BSSAP or RANAP messages is passed from the MAP process to the Handover Control Application at the sending end; the notation used in the SDL diagrams for the MAP processes is "HO_CA_MESSAGE_req(Message transfer)".

1216 For details of the interworking between the A-interface and MAP procedures or the Iu-interface and MAP procedures, 1217 see 3GPP TS 23.009 [21] and 3GPP TS 29.010 [58].

1218

19.2.2 Procedure in MSC-A

1219 This subclause describes the inter-MSC handover procedure in MSC-A; it covers basic inter-MSC handover to another 1220 MSC (MSC-B) and subsequent inter-MSC handover to a third MSC (MSC-B') or back to the controlling MSC 1221 (MSC-A). 1222 The MAP process in MSC-A to handle inter-MSC handover is shown in figure 19.2/4. The MAP process invokes 1223 macros not defined in this clause; the definitions of these macros can be found as follows: 1224 1225 1226

Receive_Open_Cnf Check_Indication Check_Confirmation

see subclause 25.1.2; see subclause 25.2.1. see subclause 25.2.2.

1227 Communication between the MAP handover process and the Handover Control application is represented by the 1228 HO_CA_MESSAGE service. For a detailed description of the interworking between the Handover Control applications 1229 in different MSCs for the inter-MSC handover procedure, see 3GPP TS 23.009 [21].

1230 19.2.2.1

Basic handover

1231 The handling in MSC-A for basic inter-MSC handover is shown in sheets 1 to 6 of figure 19.2/4. 1232 Sheet 1: The MAP_PREPARE_HANDOVER request may contain: 1233 1234 1235 1236 1237 1238

an indication that handover number allocation is not required; the target Cell ID, for compatibility for handover to GSM; the target RNC ID, for SRNS relocation or inter-system handover from GSM to UMTS; the IMSI; UMTS encryption information and UMTS integrity protection information, which are necessary for inter-system handover from GSM to UMTS;

1764

1765

1239

GSM radio resource information (channel type).

1240 The conditions for the presence of these parameters and the processing in MSC-B (3G_MSC-B) are described in detail 1241 in 3GPP TS 29.010 [58] and 3GPP TS 23.009 [21]. 1242 Sheet 2: The MAP_PREPARE_HANDOVER confirmation contains one of: 1243 1244 1245 1246

no handover number, if the MAP_PREPARE_HANDOVER request included an indication that handover number allocation is not required; a handover number; one or more relocation numbers.

1247 Sheet 2: The MAP_PREPARE_HANDOVER confirmation contains BSSAP or RANAP signalling information, which 1248 is passed to the Handover Control application in MSC-A. 1249 Sheet 2: If the MAP_PREPARE_HANDOVER confirmation contains an indication that MSC-B does not support 1250 multiple bearers, the Handover Control application in MSC-A may request handover of one bearer to the same cell in 1251 MSC-B. 1252 Sheet 5: If the original MAP_PREPARE_HANDOVER request included a parameter indicating that handover number 1253 allocation is not required, the Handover Control application in MSC-A may request a handover number (or one or more 1254 relocation numbers); this triggers a further MAP_PREPARE_HANDOVER request towards MSC-B

1255 19.2.2.2
1256 1257 1258 1259

Handling of access signalling

The Handover Control application in MSC-A may forward access signalling to any of the MS, RNS-B or BSS-B using the MAP_FORWARD_ACCESS_SIGNALLING service; any of the MS, RNS-B or BSS-B may forward access signalling to the Handover Control application in MSC-A using the MAP_PROCESS_ACCESS_SIGNALLING service. These are non-confirmed services.

1260 19.2.2.3
1261 1262 1263 1264

Subsequent handover

The handling in MSC-A for subsequent inter-MSC handover is shown in sheets 7 & 8 of figure 19.2/4. If the Handover Control Application determines that the call is to be handed over to a third MSC (MSC-B') it triggers another instance of the MAP process to handle the basic handover to MSC-B', and reports the result of the subsequent handover to the instance of the MAP process which handles the dialogue with MSC-B.

1265 Sheet 8: While the MAP process in MSC-A is waiting for the completion of subsequent handover, it relays access 1266 signalling between the Handover Control application and the MS, RNS-B or BSS-B as described in subclause 19.2.2.2.

1267

19.2.3 Procedure in MSC-B

1268 This subclause describes the handover or relocation procedure in MSC-B; it covers basic handover or relocation from 1269 the controlling MSC (MSC-A) and subsequent handover or relocation. 1270 The MAP process in MSC-B to handle handover or relocation is shown in figure 19.2/5. The MAP process invokes 1271 macros not defined in this clause; the definitions of these macros can be found as follows: 1272 1273 1274 1275

Receive_Open_Ind Receive_Open_Cnf Check_Indication Check_Confirmation

see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.1. see subclause 25.2.2.

1276 Communication between the MAP handover process and the Handover Control application is represented by the 1277 HO_CA_MESSAGE service. For a detailed description of the interworking between the Handover Control applications 1278 in different MSCs for the inter-MSC handover procedure, see 3GPP TS 23.009 [21]. 1279 The ordering of allocation of handover number and radio resources shown in the SDL diagrams is not mandatory.

1766

1767

1280 19.2.3.1

Basic handover

1281 The handling in MSC-B for basic inter-MSC handover is shown in sheets 1 to 7 of figure 19.2/5. 1282 1283 1284 1285

Sheet 2: If the MAP_PREPARE_HANDOVER indication included a parameter requesting multiple bearers but MSC-B does not support multiple bearers, MSC-B sends a MAP_PREPARE_HANDOVER response indicating that multiple bearers are not supported, and waits for a possible MAP_PREPARE_HANDOVER indication requesting handover of a single bearer.

1286 Sheet 6: If the original MAP_PREPARE_HANDOVER indication included a parameter indicating that handover 1287 number allocation is not required, MSC-A may send a further MAP_PREPARE_HANDOVER request to request the 1288 allocation of a handover number (or one or more relocation numbers).

1289 19.2.3.2
1290 1291 1292 1293 1294

Handling of access signalling

The Handover Control application in MSC-A may forward access signalling to any of the MS, RNS-B or BSS-B using the MAP_FORWARD_ACCESS_SIGNALLING service; any of the MS, RNS-B or BSS-B may forward access signalling to the Handover Control application in MSC-A using the MAP_PROCESS_ACCESS_SIGNALLING service. These are non-confirmed services. Signals to or from any of the MS, RNS-B or BSS-B are routed through the Handover Control application in MSC-B.

1295 19.2.3.3

Subsequent handover

1296 The handling in MSC-B for subsequent inter-MSC handover is shown in sheet 8 of figure 19.2/5. 1297 While the MAP process in MSC-B is waiting for the completion of subsequent handover, it relays access signalling 1298 between MSC-A and the MS, RNS-B or BSS-B through the Handover Control application as described in subclause 1299 19.2.3.2.

1300

19.2.4 Macro Receive_Error_From_HO_CA

1301 This macro is used by the handover processes in MSC-A and MSC-B to receive errors from the Handover Control 1302 Application at any state of a handover process.

1303

19.2.5 Procedure in VLR-B

1304 The process in VLR-B to handle a request for a handover number is shown in figure 19.2/7. The process invokes 1305 macros not defined in this clause; the definitions of these macros can be found as follows: 1306 1307

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

1768

1769

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC)

HO_MSCA1(8)
Signals to/from the l eft are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

Null

HO_CA_MESSAGE_i nd (Handover Request)

MAP_OPEN_req MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error HO_CA_MESSAGE_req (M Error) AP

OK

Vr Perform MAP Vr dialogue

Null

Wait_For_ Prepare_ Handover_Result

Null

HO_CA_MESSAGE_i nd (Call Release)

MAP_ CLOSE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ req

HO_CA_MESSAGE_req (Connection Closed)

MAP_CLOSE_ req

Null

Null

HO_CA_MESSAGE_req (M Error) AP

Null

1308
1309

Figure 19.2/4 (sheet 1 of 8): Process HO_MSC_A

1770

1771

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) Wait_For_ Prepare_ Handover_Result

HO_MSCA2(8)
Signals to/from the l eft are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

MAP_ PREPARE_ HANDOVER_ cnf

Check_ Confirmation

OK

Provider Error MAP_U_ ABORT_ req

User Error, Data Error

HO_CA_MESSAGE_req (Prepare Handover Result)

HO_CA_MESSAGE_req (M Error) AP

No Multiple bearer not supported indication received? Yes Null

Wait_For_HO_ Completion_ On_MSC_B

Wait_For_ Resend

HO_CA_MESSAGE_i nd (Handover Request)

HO_CA_MESSAGE_i nd (Error)

Receive_ Error_From _ HO_CA

MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req

MAP_U_ ABORT_ req

Error Wait_For_HO_ Completion_ On_MSC_B

Null Wait_For_ Prepare_ Handover_Result

Null

Null

1310
1311

Figure 19.2/4 (sheet 2 of 8): Process HO_MSC_A

1772

1773

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) Wait_For_HO_ Completion_ On_MSCB

HO_MSCA3(8)
Signals to/from the l eft are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

HO_CA_MESSAGE_i nd (M essage Transfer)

MAP_SEND END_SIGNAL_ ind

MAP_PROCESS_ ACCESS_ SIGNALLING_ind

MAP_FORWARD_ACCESS_SIGNALLING_req MAP_DELIMITER_req

Check_ Indication

Check_ Indication

OK Wait_For_HO_ Completion_ On_MSC_B HO_CA_MESSAGE_req (Handover Com plete)

Error HO_CA_MESSAGE_req (M Error) AP

Error MS_On_ MSCB MAP_U_ ABORT_ req Wait_For_HO_ Completion_ On_MSC_B

OK HO_CA_MESSAGE_req (M essage Transfer)

Null

Wait_For_HO_ Completion_ On_MSC_B

Wait_For_HO_ Completion_ On_MSC_B

MAP_ CLOSE_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ ind

HO_CA_MESSAGE_req (Connection Closed)

HO_CA_MESSAGE_req (M Error) AP

HO_CA_MESSAGE_req (M Error) AP

Null

Null

Wait_For_HO_ Completion_ On_MSC_B

1312
1313

Figure 19.2/4 (sheet 3 of 8): Process HO_MSC_A

1774

1775

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) MS_On_ MSC_B

HO_MSCA4(8)
Signals to/from the l eft are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

HO_CA_MESSAGE_i nd (M essage Transfer)

Receive_ Error_From _ HO_CA

MAP_PROCESS_ACCESS_ SIGNALLING_ind

Error

Null

MAP_FORWARD_ACCESS_SIGNALLING_req MAP_DELIMITER_req

MS_On_ MSC_B

Null

Check_ Indication

Error MS_On_ MSC_B

OK HO_CA_MESSAGE_req (M essage Transfer)

MS_On_ MSC_B

MS_On_ MSC_B

MS_On_ MSC_B

MAP_ CLOSE_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ ind

HO_CA_MESSAGE_req (Connection Closed)

HO_CA_MESSAGE_req (M Error) AP

HO_CA_MESSAGE_req (M Error) AP

Null

Null

MS_On_ MSC_B

1314
1315

Figure 19.2/4 (sheet 4 of 8): Process HO_MSC_A

1776

1777

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) MS_On_ MSC_B

HO_MSCA5(8)
Signals to/from the l eft are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

HO_CA_MESSAGE_i nd (Call Release)

HO_CA_MESSAGE_i nd (HO Num Requi red) ber

MAP_SEND_END_SIGNAL_rsp MAP_CLOSE_req

MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req

Null

Wait_For_HO_ Number_From _ MSC_B

MAP_ PREPARE_ HANDOVER_cnf

Check_ Confirmation

OK Yes Handover number received? No

User Error, Data Error HO_CA_MESSAGE_req (M Error) AP

Provider Error HO_CA_MESSAGE_req (M Error) AP

Set HO-number: present

Set HO-number: not present

MS_On_ MSC_B

Null

HO_CA_MESSAGE_req (Routing information)

MS_On_ MSC_B

1316
1317

Figure 19.2/4 (sheet 5 of 8): Process HO_MSC_A

1778

1779

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) Wait_For_HO_ Number_From _ MSC_B

HO_MSCA6(8)
Signals to/from the left are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

MAP_ CLOSE_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ ind

HO_CA_MESSAGE_req (Connection Closed)

HO_CA_MESSAGE_req (M Error) AP

HO_CA_MESSAGE_req (M Error) AP

Null

Null

Wait_For_HO_ Number_From _ MSC_B

Wait_For_HO_ Number_From _ MSC_B

Receive_ Error_From _ HO_CA

Null

Error Wait_For_HO_ Number_From _ MSC_B

Null

1318
1319

Figure 19.2/4 (sheet 6 of 8): Process HO_MSC_A

1780

1781

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) MS_On_ MSC_B

HO_MSCA7(8)
Signals to/from the left are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

MAP_PREPARE_SUBSEQUENT_HANDOVER_ind

Check_ Indication

OK No MSC known? Yes Set User Error: Unknown M SC

Error

HO_CA_MESSAGE_req (Handover Request)

MAP_PREPARE_SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req

Wait_For_ Subsequent_ Handover

MS_On_ MSC_B

HO_CA_MESSAGE_i nd (Subsequent Handover Accepted)

HO_CA_MESSAGE_i nd (Subsequent Handover Failure)

Set User Error: Subsequent Handover Failure

MAP_PREPARE_SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req

MAP_PREPARE_SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req

Wait_For_ Subsequent_ Handover_ Completion

MS_On_ MSC_B

HO_CA_MESSAGE_i nd (Subsequent Handover Com plete)

MAP_SEND_END_SIGNAL_rsp MAP_CLOSE_req

Null

1320
1321

Figure 19.2/4 (sheet 7 of 8): Process HO_MSC_A

1782

1783

process Handover_MSC_A
Process in M SC-A (the Anchor MSC) to handle inter-MSC handover to MSC-B (the Relay MSC) and subsequent handover back to M SC-A or to MSC-B' (the new Relay MSC) Wait_For_Subsequent_Handover, Wait_For_Subsequent_Handover_Completion

HO_MSCA8(8)
Signals to/from the l eft are to/fromthe Handover Control Application in MSC-A; signals to/from the right are to/fromMSC-B

HO_CA_MESSAGE_i nd (M essage Transfer)

MAP_PROCESS_ACCESS_SIGNALLING_ind

Receive_ Error_From _ HO_CA

Null

Error

MAP_FORWARD_ACCESS_SIGNALLING_req MAP_DELIMITER_req

Check_ Indication

Null

MS_On_ MSC_B

Error

OK HO_CA_MESSAGE_req (M essage Transfer)

Wait_For_ Handover_ Indication

Wait_For_Subsequent_Handover, Wait_For_Subsequent_Handover_Completion

MAP_ CLOSE_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ ind

HO_CA_MESSAGE_req (Connection Closed)

HO_CA_MESSAGE_req (M Error) AP

HO_CA_MESSAGE_req (M Error) AP

Null

Null

1322
1323

Figure 19.2/4 (sheet 8 of 8): Process HO_MSC_A

1784

1785

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC)

HO_MSCB1(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B

Null

Receive_ Open_Ind

Error

OK Wait_For_ Service_ Indication

Vr Perform MAP Vr dialogue

Null

MAP_ NOTICE_ ind

MAP_PREPARE_HANDOVER_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ CLOSE_ req

Check_ Indication

OK No Null VBS or VGCS? Yes

Error

MAP_PREPARE_HANDOVER_rsp MAP_CLOSE_req

Yes New cell in Group Call area? No

Set User Error: Target cell outside Group Call area

Handover number allocation required? Yes

No

MAP_PREPARE_HANDOVER_rsp MAP_CLOSE_req

HO_CA_MESSAGE_req (Handover Request)

Null

Wait_For_ Channel

Null

1324
1325

Figure 19.2/5 (sheet 1 of 8): Process HO_MSC_B

1786

1787

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) 1

HO_MSCB2(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B unless marked otherwise No

Multiple bearer requested? Yes

Multiple bearer supported?

No

Yes MAP_OPEN_req MAP_ALLOCATE_HANDOVER_NUMBER_req MAP_DELIMITER_req

MAP_PREPARE_HANDOVER_rsp MAP_DELIMITER_req

To VLR-B Wait_For_ Service_ Indication Receive_ Open_Cnf

Vr, Error

OK Wait_For_ Handover_ Number

MAP_ALLOCATE_HANDOVER_NUMBER_cnf

MAP_SEND_HANDOVER_REPORT_ind

From VLR-B Check_ Indication

From VLR-B

Error Set User Error: No Handover Number available Set User Error: System failure

OK HO_CA_MESSAGE_req (Handover Num ber allocated)

MAP_PREPARE_HANDOVER_rsp MAP_CLOSE_req

Null

Wait_For_ Channel

1326
1327

Figure 19.2/5 (sheet 2 of 8): Process HO_MSC_B

1788

1789

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) Wait_For_ Channel

HO_MSCB3(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B

MAP_ NOTICE_ ind

HO_CA_MESSAGE_i nd (Handover Request ack)

Receive_ Error_From _ HO_CA

Error MAP_ CLOSE_ req No SCCP segmentation required? Yes MAP_U_ ABORT_ req

Null

HO_CA_MESSAGE_i nd (M Error) AP

MAP DELIMITER_ req

Null

Null

Null

MAP_PREPARE_HANDOVER_rsp MAP_DELIMITER_req

Wait_For_ Connection

Wait_For_Assignment, Wait_For_Channel, Wait_For_Connection, MS_On_MSC_B

MAP_U_ABORT_ind MAP_P_ABORT_ind

MAP_ CLOSE_ ind

HO_CA_MESSAGE_i nd (M Error) AP

HO_CA_MESSAGE_i nd (Connection Closed)

Null

Null

1328
1329

Figure 19.2/5 (sheet 3 of 8): Process HO_MSC_B

1790

1791

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) Wait_For_ Connection

HO_MSCB4(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B unless marked otherwise

HO_CA_MESSAGE_i nd (M essage Transfer)

HO_CA_MESSAGE_i nd (Release Handover Num ber)

HO_CA_MESSAGE_i nd (Handover Com plete)

MAP_PROCESS_ ACCESS_SIGNALLING_req MAP_DELIMITER_req

Set result

MAP_SEND_END_SIGNAL_req MAP_DELIMITER_req

Wait_For_ Connection

MAP_SEND_HANDOVER_ REPORT_rsp MAP_CLOSE_req

MS_On_ MSC_B

To VLR-B Wait_For_ Connection

Wait_For_ Connection

MAP_ NOTICE_ ind

Receive_ Error_From _ HO_CA

Error MAP_ CLOSE_ req MAP_U_ ABORT_ req

Null

HO_CA_MESSAGE_i nd (M Error) AP

Null

Null

Null

1330
1331

Figure 19.2/5 (sheet 4 of 8): Process HO_MSC_B

1792

1793

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) MS_On_ MSC_B

HO_MSCB5(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B

MAP_SEND_END_SIGNAL_cnf

MAP_FORWARD_ACCESS_ SIGNALLING_ind

HO_CA_MESSAGE_i nd (M essage Transfer)

HO_CA_MESSAGE_i nd (Connection Closed)

Check_ Indication

MAP_PROCESS_ACCESS_ SIGNALLING_req MAP_DELIMITER_req

Error

OK HO_CA_MESSAGE_req (M essage Transfer)

Null

MS_On_ MSC_B

MS_On_ MSC_B

MS_On_ MSC_B

MS_On_ MSC_B

MAP_ NOTICE_ ind

Receive_ Error_From _ HO_CA

Error HO_CA_MESSAGE_ind (M Error) AP MS_On_ MSC_B

Null

Null

MS_On_ MSC_B

1332
1333

Figure 19.2/5 (sheet 5 of 8): Process HO_MSC_B

1794

1795

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) MS_On_ MSC_B

HO_MSCB6(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B unless marked otherwise

MAP_PREPARE_HANDOVER_ind

Check_ Indication

Error Yes

OK

HO Number Not Required parameter present? No

Yes Handover number already used? No

Set User Error: Unexpected data value

MAP_OPEN_req MAP_ALLOCATE_HANDOVER_NUMBER_req MAP_DELIMITER_req

To VLR-B Receive_ Open_Cnf

Vr, Error Set User Error: No Handover Number available

OK Wait_For_ Handover_Number_ Allocation

MAP_PREPARE_HANDOVER_rsp MAP_DELIMITER_req

MS_On_ MSC_B

1334
1335

Figure 19.2/5 (sheet 6 of 8): Process HO_MSC_B

1796

1797

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) Wait_For_ Handover_Number_ Allocation

HO_MSCB7(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B unless marked otherwise

MAP_ALLOCATE_HANDOVER_NUMBER_cnf

MAP_SEND_HANDOVER_REPORT_ind

From VLR-B Check_ Indication

From VLR-B

Error Set User Error: No Handover Number available

OK HO_CA_MESSAGE_req (Handover Num ber allocated)

Set User Error: System failure

MAP_PREPARE_HANDOVER_rsp MAP_DELIMITER_req

Wait_For_ Assignm ent

MS_On_ MSC_B

MAP_ NOTICE_ ind

HO_CA_MESSAGE_i nd (Handover Request ack)

Receive_ Error_From _ HO_CA

Error No HO_CA_MESSAGE_i nd (M Error) AP Yes SCCP segmentation required?

Null

Wait_For_ Assignm ent

Null

Wait_For_ Assignm ent

MAP DELIMITER_ req

MAP_PREPARE_HANDOVER_rsp MAP_DELIMITER_req

MS_On_ MSC_B

1336
1337

Figure 19.2/5 (sheet 7 of 8): Process HO_MSC_B

1798

1799

process Handover_MSC_B
Process in M SC-B (the Relay MSC) to handle inter-MSC handover from MSC-A (the Anchor MSC) MS_On_ MSC_B

HO_MSCB8(8)
Signals to/from the l eft are to/fromMSC-A; signals to/from the right are to/fromthe Handover Control Application in MSC-B

HO_CA_MESSAGE_i nd (Handover Required)

MAP_PREPARE_SUBSEQUENT_HANDOVER_req MAP_DELIMITER_req

Wait_For_Perform_ Subsequent_ Handover_Result

MAP_FORWARD_ACCESS_ SIGNALLING_ind

MAP_PREPARE_SUBSEQUENT_ HANDOVER_cnf

Check_ Indication

HO_CA_MESSAGE_req (Message Transfer)

Error

OK MAP_PROCESS_ACCESS_ SIGNALLING_req MAP_DELIMITER_req

HO_CA_MESSAGE_req (M essage Transfer)

Wait_For_Perform_ Subsequent_ Handover_Result

Wait_For_Perform_ Subsequent_ Handover_Result

Check_ Confirmation

Wait_For_Perform_ Subsequent_ Handover_Result

OK

User Error, Data Error HO_CA_MESSAGE_req (HO-Prepared) HO_CA_MESSAGE_req (Subsequent Handover Failure)

Provider Error HO_CA_MESSAGE_req (Connection closed)

MS_On_ MSC_B

MS_On_ MSC_B

Null

1338
1339

Figure 19.2/5 (sheet 8 of 8): Process HO_MSC_B

1800

1801

macrodefinition Receive_Error_From_HO_CA
Macro in the MSC to handle an error indication from the Handover Control Application

REF_HOCA1(1)
Signals to/from the left are to/fromthe local Handover Control Application; signals to/from the right are to/fromthe distant MSC

HO_CA_MESSAGE_i nd (Error Indication)

Error indication?

Keep dialogue

Close dialogue

MAP_NOTICE previously received?

No MAP_ DELIMITER_ req MAP_U_ ABORT_ req MAP_ CLOSE_ req

Yes

Error

Null

Null

1340
1341

Figure 19.2/6: Macro Receive_error_from_HO_CA

1802

1803

process Handover_VLR_B
Process in VLR-B (the VLR of the Relay M SC) to handle inter-MSC handover from MSC-A to MSC-B

HO_VLRB1(1)
Signals to/from the l eft are to/fromMSC-B; signals from the right are from the handover control application in VLR-B

Null

Receive_ Open_Ind

OK

Vr, Error

MAP_ALLOCATE_HANDOVER_NUMBER_ind

Null

Check_ Indication

Error No

OK Handover number available? Set User Error: No Handover num available ber Yes Allocate Handover number

MAP_ALLOCATE_HANDOVER_NUMBER_rsp MAP_CLOSE_req

MAP_SEND_HANDOVER_REPORT_req MAP_DELIMITER_req

Null

Wait_For_ Handover_ Report

MAP_SEND_HANDOVER_REPORT_cnf

MAP_U_ ABORT_ ind

Local Abort

Release Handover number

MAP_U_ ABORT_ req

Null

1342
1343

Figure 19.2/7: Process HO_VLR_B

1804

1805

1344

19.3 Fault recovery procedures

1345 When a location register has restarted after a fault, the fault recovery procedures ensure that the subscriber data in the 1346 VLR or in the SGSN become consistent with the subscriber data that are stored in the HLR for the MS concerned and 1347 that the location information in the HLR , the VLR and the SGSN reflect accurately the current location of the MS. 1348 The stage 2 specification of fault recovery procedures in location registers is 3GPP TS 23.007 [19].

1349

19.3.1 VLR fault recovery procedures

1350 19.3.1.1 General

1351 1352 1353 1354 1355 1356 1357

Restoration of an IMSI record in a VLR can be triggered by a location registration request from the MS or by a request from the HLR for a roaming number to route a mobile terminated call to the MS. If the restoration is triggered by a location registration request from the MS, the VLR performs the location updating procedure described in 3GPP TS 23.012 [23] and subclause 19.1.1 of the present document. If the restoration is triggered by a request for a roaming number, the VLR provides the roaming number and triggers an independent dialogue to restore the subscriber data as described in 3GPP TS 23.018 [97]. The message flow for data restoration triggered by a request for a roaming number is shown in figure 19.3.1/1.

VLR 1 2 3 4 5 6 7 8 9 10

HLR

1358
1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1806

1) 2) 3) 4) 5) 6) 7) 8) 9) 10)

MAP_PROVIDE_ROAMING_NUMBER_req/ind MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf MAP_SEND_AUTHENTICATION_INFO_req/ind (Note 1, note 2) MAP_SEND_AUTHENTICATION_INFO_rsp/cnf (Note 1, note 2) MAP_RESTORE_DATA_req/ind MAP_ACTIVATE_TRACE_MODE_req/ind (Note 1, note 3) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 1, note 3) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_RESTORE_DATA_rsp/cnf

NOTE 1: Services printed in italics are optional. NOTE 2: If authentication is required.

1807

1375

1373 1374

NOTE 3: If subscriber tracing is active in the HLR.

Figure 19.3/1: Message flow for VLR restoration at mobile terminated call set-up

1376 19.3.1.2

Procedure in the VLR

1377 The procedure in the VLR to handle a dialogue for subscriber data restoration is defined in subclause 21.2.6 of the 1378 present document.

1379 19.3.1.3

Procedure in the HLR

1380 The MAP process in the HLR to handle a request for data restoration in the VLR is shown in figure 19.3.1/2. The MAP 1381 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 1382 1383

Check_Indication Control_Tracing_With_VLR_HLR

see subclause 25.2.1; see subclause 25.9.6.

1808

1809

1384

process Restore_Data_HLR
Process in the HLR to handle a request from the VLR to restore subscriber data

RD_HLR1(1)
Signals to/from the l eft are to/fromthe VLR

Null

MAP_ RESTORE_ DATA_ind

Check_ Indication

Error No

OK IMSI known? Yes Set User Error: Unknown subscriber No LMSI received? Yes

Update LMSI

Subscriber tracing active in VLR:=False

Control_ Tracing_ With_VLR_HLR

No MNRF set? Yes

Error

OK Insert_ Subs_Data_ Framed_HLR

Set: M NRF

Error Set User Error: System failure

Aborted

OK Set: HLR num ber

MAP_RESTORE_DATA_rsp MAP_CLOSE_req

MAP_RESTORE_DATA_rsp MAP_CLOSE_req

1385
1386

Figure 19.3.1/2: Process Restore_Data_HLR

1810

1811

1387 1388 19.3.2.1

19.3.2 HLR fault recovery procedures

General

1389 For the HLR, periodic back-up of data to non-volatile memory is mandatory. 1390 Data that have been changed after the last back-up and before the restart of the HLR cannot be recovered by reload from 1391 the non-volatile memory. Therefore, a restoration procedure is triggered for each IMSI record that has been affected by 1392 the HLR fault at the first authenticated radio contact with the MS concerned. 1393 1394 1395 1396

As an implementation option, a notification can be forwarded to the MS to alert the subscriber to check the parameters for supplementary services that allow subscriber controlled input (MAP_FORWARD_CHECK_SS_INDICATION service). If the VLR receives this notification from the HLR it shall forward the notification to the MS. If the Gsinterface is implemented the VLR shall not forward this notification.

1397 The message flow for HLR restoration for a non-GPRS subscriber is shown in figure 19.3.2/1. 1398 The message flow for HLR restoration for a GPRS subscriber is shown in figure 19.3.2/2.

MSC

VLR 1 2

HLR

3 4 5 6 7 8 9

10

1399
1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414

1) 2) 3) 4) 5) 6) 7) 8) 9) 10)

MAP_RESET_req/ind MAP_PROCESS_ACCESS_REQUEST_req/ind MAP_UPDATE_LOCATION_req/ind MAP_ACTIVATE_TRACE_MODE_req/ind (Note 1, Note 2) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 1, Note 2) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_LOCATION_rsp/cnf MAP_FORWARD_CHECK_SS_INDICATION_req/ind (Note 1) MAP_FORWARD_CHECK_SS_INDICATION_req/ind (Note 1)

NOTE 1: Services printed in italics are optional. NOTE 2: If subscriber tracing is active in the HLR.

1415

Figure 19.3.2/1: Message flow for HLR restoration (non-GPRS)

1416

1812

1813

SGSN 1 2 3 4 5 6 7

HLR

1417
1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429

1) 2) 3) 4) 5) 6) 7)

MAP_RESET_req/ind MAP_UPDATE_GPRS_LOCATION_req/ind MAP_ACTIVATE_TRACE_MODE_req/ind (Note 1, Note 2) MAP_ACTIVATE_TRACE_MODE_rsp/cnf (Note 1, Note 2) MAP_INSERT_SUBSCRIBER_DATA_req/ind MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf MAP_UPDATE_GPRS_LOCATION_rsp/cnf

NOTE 1: Services printed in italics are optional. NOTE 2: If subscriber tracing is active in the HLR.

1430

Figure 19.3.2/2: Message flow for HLR restoration (GPRS)

1431 19.3.2.2

Procedure in the HLR

1432 The MAP process in the HLR to notify the relevant serving nodes that the HLR has restarted is shown in figure 1433 19.3.2/3. 1434 The SGSN address list includes one instance of the address of each SGSN in which (according to the HLR data 1435 retrieved from the non-volatile memory) there is at least one subscriber registered who is affected by the HLR restart. 1436 The VLR address list includes one instance of the address of each VLR in which (according to the HLR data retrieved 1437 from the non-volatile memory) there is at least one subscriber registered who is affected by the HLR restart. 1438 The MAP process in the HLR to notify a VLR that the HLR has restarted is shown in figure 19.3.2/4. The MAP process 1439 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1440

Receive_Open_Cnf

see subclause 25.1.2.

1441 The MAP process in the HLR to notify an SGSN that the HLR has restarted is shown in figure 19.3.2/5. The MAP 1442 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1443

Receive_Open_Cnf

see subclause 25.1.2.

1444 19.3.2.3

Procedure in the VLR

1445 The MAP process in the VLR to handle a notification that an HLR has restarted is shown in figure 19.3.2/6. The MAP 1446 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1447

Receive_Open_Ind

see subclause 25.1.1.

1814

1815

1448 The VLR uses the HLR number or the HLR identity list included in the MAP_RESET indication to identify the IMSI 1449 records which are affected by the HLR restart.

1450 19.3.2.4

Procedure in the SGSN

1451 The MAP process in the SGSN to handle a notification that an HLR has restarted is shown in figure 19.3.2/6. The MAP 1452 process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1453

Receive_Open_Ind

see subclause 25.1.1.

1454 The SGSN uses the HLR number or the HLR identity list included in the MAP_RESET indication to identify the IMSI 1455 records which are affected by the HLR restart.

1816

1817

process Restart_HLR
Process in the HLR to notify the relevant serving nodes after an HLR restart

R_HLR1(1)
Signals from the right are from the O&M application in the HLR

Null

OM_ RESTART_ind

Reload data from backup

Subscriber tracing active in SGSN:=False

For each GPRS subscriber affected by the HLR restart

Subscriber tracing active in VLR:=False

For each non-GPRS subscriber affected by the HLR restart

MS purged for GPRS:=False

For each GPRS subscriber affected by the HLR restart

MS purged:= False

For each non-GPRS subscriber affected by the HLR restart

Read SGSN address list

Read VLR address list

Send_Reset_ To_SGSN_HLR

Send_Reset_ To_VLR_HLR

No

All SGSNs notified? Yes

No

All VLRs notified? Yes

Forward Check SS indication supported?

Null

No

Yes Check SS required:=True For each non-GPRS subscriber affected by the HLR restart

1456
1457

Figure 19.3.2/3: Process Restart_HLR

1818

1819

process Send_Reset_To_VLR_HLR
Process in the HLR to send a Reset m essage to a VLR

SR_VLR_HLR1(1)
Signals to the left are to the VLR

MAP_OPEN_req MAP_RESET_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK MAP_ CLOSE_ req

Error

Release method= Prearranged End

1458
1459

Figure 19.3.2/4: Process Send_Reset_To_VLR_HLR

1820

1821

process Send_Reset_To_VLR_HLR
Process in the HLR to send a Reset m essage to a VLR

SR_VLR_HLR1(1)
Signals to the left are to the VLR

MAP_OPEN_req MAP_RESET_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK MAP_ CLOSE_ req

Error

Release method:= Prearranged End

1460
1461

Figure 19.3.2/5: Process Send_Reset_To_SGSN_HLR

1822

1823

process Receive_Reset_VLR
Process in the VLR to handle a Reset message from the HLR

RR_VLR1(1)
Signals to/from the right are to/fromthe HLR

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Primitive

Error

Null

Null

MAP_P_ ABORT_ ind

MAP_ RESET_ ind

Null

MAP_ CLOSE_ req

Release method:= Prearranged End

Identify IMSI records

Location information confirmed in HLR:=False

For each identified IMSI record

Subscriber tracing active:= False

For each identified IMSI record

Null

1462
1463

Figure 19.3.2/6: Process Receive_Reset_VLR

1824

1825

process Receive_Reset_SGSN
Process in the SGSN to handle a Reset message from the HLR

RR_SGSN1(1)
Signals to/from the right are to/fromthe HLR

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Primitive

Error

Null

Null

MAP_P_ ABORT_ ind

MAP_ RESET_ ind

Null

MAP_ CLOSE_ req

Release method:= Prearranged End

Identify IMSI records

Location information confirmed in HLR:=False

For each identified IMSI record

Subscriber tracing active:= False

For each identified IMSI record

Null

1464
1465

Figure 19.3.2/7: Process Receive_Reset_SGSN

1826

1827

1466 1467

19.4 Mobility Management event notification procedure

19.4.1 General

1468 The Mobility Management event notification procedure is used to notify a gsmSCF about the successful completion of a 1469 Mobility Management event. 1470 The message flow for Mobility Management event notification is shown in figure 19.4/1.
VLR or SGSN

gsmSCF 1

1471
1472 1473 1474 1475

1) 2)

MAP_REPORT_MM_EVENT_req/ind MAP_REPORT_MM_EVENT_rsp/cnf

1476

Figure 19.5/1: Message flow for Mobility Management event notification

1477

19.4.2 Procedure in the VLR or SGSN

1478 The MAP process in the VLR or the SGSN to report a Mobility Management event to the gsmSCF is shown in figure 1479 19.4/2.The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as 1480 follows: 1481 1482

Receive_Open_Cnf Check_Confirmation:

see subclause 25.1.2; see subclause 25.2.2.

1483

19.4.3 Procedure in the gsmSCF

1484 The MAP process in the gsmSCF to handle the report of a Mobility Management event is shown in figure 19.4/3.The 1485 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1486

Receive_Open_Ind

see subclause 25.1.1;

1828

1829

process Notify_MM_Event_VLR_Or_SGSN
Process in the VLR or SGSN to notify the gsmSCF of a mobility managem event ent

NMME_VLR_SGSN1(1)
Signals to/from the l eft are to/fromthe location managem application ent process in the VLR (see 3GPP TS 23.012) or the GPRS m obility managem application ent process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/fromthe gsm SCF

Null

Send MM event notification

MAP_OPEN_req MAP_REPORT_MM_EVENT_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ gsmSCF_ Response

Vr, Error

Abort

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ REPORT_MM_ EVENT_cnf

Null

MAP_ CLOSE_ req Provider Error, Data Error Set negative response: System failure Set negative response: System failure

Check_ Confirmation

User Error Set negative response

OK

Send M event M notification negative response

Send M event M notification ack

Null

Null

1487
1488

Figure 19.4/2: Process Notify_MM_Event_VLR_Or_SGSN

1830

1831

process Notify_MM_Event_gsmSCF
Process in the gsmSCF to handle the notification of a mobility management event

NMME_SCF1(1)
Signals to/from the left are to/fromthe VLR or SGSN; signals to/from the right are to/fromthe service logic application process in the gsmSCF

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Primitive

Vr, Error

Null

MAP_P_ ABORT_ ind

MAP_REPORT_MM_EVENT_ind

MAP_ NOTICE_ ind

Null

Report MM Event

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Null

Report MM Event ack

Report MM Event negative response

Set Result

Set User Error

MAP_REPORT_MM_EVENT_rsp MAP_CLOSE_req

Null

1489
1490

Figure 19.4/3: Process Notify_MM_Event_gsmSCF

1832

1833

1491 1492

19.4 HLR Insert Subscriber Data macros

19.5.1 Macro Insert_Subs_Data_Framed_HLR

1493 This macro is used to transfer subscriber data to the VLR as part of an existing dialogue for location updating or data 1494 restoration. The macro invokes a macro and a process not defined in this clause; the definitions of the macro and the 1495 process can be found as follows: 1496 1497

Wait_For_Insert_Subs_Data_Cnf Send_Insert_Subs_Data_HLR:

see subclause 25.7.5; see subclause 25.7.7.

1498 The HLR may wait for each MAP_INSERT_SUBSCRIBER_DATA request to be acknowledged before it sends the 1499 next request, or it may handle the requests and the confirmations in parallel. 1500 1501 1502 1503 1504

If the VLR has indicated that it does not support a service or feature (e.g. Closed User Group or Advice Of Charge Charging Level) which the HLR operator regards as essential for the subscriber, the macro Wait_for_Insert_Subs_Data_Cnf takes the Replace_Service exit; the HLR sets the Roaming Restriction Due To Unsupported Feature flag to roaming restricted and sends Roaming Restriction Due To Unsupported Feature in a subsequent MAP_INSERT_SUBSCRIBER_DATA request.

1505 If the HLR operator does not regard the unsupported service or feature as essential for the subscriber but the macro 1506 Wait_for_Insert_Subs_Data_Cnf takes the Replace_Service exit, the HLR sends the data for a replacement service in a 1507 subsequent MAP_INSERT_SUBSCRIBER_DATA request. 1508 1509 1510 1511 1512 1513 1514 1515

If subscriber data for CAMEL Phase 2 or later services are sent to a VLR which does not support the appropriate phase of CAMEL, the service behaviour may be unpredictable or incorrect. The HLR should therefore ensure that at the conclusion of a stand alone Insert Subscriber data procedure the data in the VLR do not require a capability that the VLR does not have. Possible mechanisms to ensure this are described in 3GPP TS 23.078 [98]. The HLR should send a Forwarded-to number which is not in E.164 international format to the VLR only when the HLR has ascertained that the VLR supports CAMEL Phase 2 or later. Thus, the ISD message containing the Forwarded-to number which is not in E.164 international format shall be sent to the VLR only if the HLR previously received confirmation from the VLR at Location Update that CAMEL Phase 2 or later is supported.

1516

19.5.2 Macro Insert_GPRS_Subs_Data_Framed_HLR

1517 This macro is used to transfer subscriber data to the SGSN as part of an existing dialogue for location updating. The 1518 macro invokes a macro and a process not defined in this clause; the definitions of the macro and the process can be 1519 found as follows: 1520 1521

Wait_For_Insert_GPRS_Subs_Data_Cnf see subclause 25.7.5; Send_Insert_Subs_Data_HLR: see subclause 25.7.7.

1522 The HLR may wait for each MAP_INSERT_SUBSCRIBER_DATA request to be acknowledged before it sends the 1523 next request, or it may handle the requests and the confirmations in parallel. 1524 1525 1526 1527

If the SGSN has indicated that it does not support a service or feature which the HLR operator regards as essential for the subscriber, the macro Wait_for_Insert_GPRS_Subs_Data_Cnf takes the Replace_Service exit; the HLR sets the Roaming Restricted In SGSN Due To Unsupported Feature flag to roaming restricted and sends Roaming Restricted In SGSN Due To Unsupported Feature in a subsequent MAP_INSERT_SUBSCRIBER_DATA request.

1528 If the HLR operator does not regard the unsupported service or feature as essential for the subscriber but the macro 1529 Wait_for_Insert_GPRS_Subs_Data_Cnf takes the Replace_Service exit, the HLR sends the data for a replacement 1530 service in a subsequent MAP_INSERT_SUBSCRIBER_DATA request.

1834

1835

macrodefinition Insert_Subs_Data_Framed_HLR
Macro in the HLR to transfer subscriber data to the VLR in an existing dialogue

ISDF_HLR1(1)
Signals to the left are to the VLR

MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Count:=1

No All data inserted? Yes 1

Wait_For_ Insert_Subs_ Data_Cnf

Send_Insert_ Subs_Data_HLR

OK

Replace_Service Set replacement services(s)

Error

Abort Count:= Count+1

Count:= Count-1

Count:= Count-1

Yes Count>0? No 1 Error Aborted

No Network node area restricted received OR Roaming Restriction due to Unsupported Feature? Yes

MSC Area restricted:= Not restricted

MSC Area restricted:= Restricted

OK

1531
1532

Figure 19.5/1: Macro Insert_Subs_Data_Framed_HLR

1836

1837

macrodefinition Insert_GPRS_Subs_Data_Framed_HLR
Macro in the HLR to transfer subscriber data to the SGSN in an existing dialogue

IGSDF_HLR1(1)
Signals to the left are to the VLR

MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Count:=1

No All data inserted? Yes 1

Wait_For_ Insert_GPRS_ Subs_Data_Cnf

Send_Insert_ Subs_Data_HLR

OK

Replace_Service Set replacement services(s)

Error

Abort Count:= Count+1

Count:= Count-1

Count:= Count-1

Yes Count>0? No 1 Error Aborted

No Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature? Yes

SGSN Area restricted:= Not restricted

SGSN Area restricted:= Restricted

OK

1533
1534

Figure 19.5/2: Macro Insert_GPRS_Subs_Data_Framed_HLR

1838

1839

1535 1536

20

Operation and maintenance procedures

20.1 General

1537 The Operation and Maintenance procedures are used to support operation and maintenance of the network. 1538 The following procedures exist for operation and maintenance purposes: 1539 1540 1541

i) Tracing procedures; ii) Subscriber Data Management procedures; iii) Subscriber Identity procedure.

1542 The following application contexts refer to complex MAP Users consisting of several processes: 1543 1544

subscriberDataManagementContext; tracingContext.

1545 Each of these two application contexts needs a co-ordinating process in the VLR or in the SGSN as described in the 1546 following subclauses.

1547

20.1.1 Tracing Co-ordinator for the VLR

1548 The Tracing Co-ordinator process in the VLR is shown the figure 20.1/1. The MAP process invokes a macro not 1549 defined in this clause; the definition of this macro can be found as follows: 1550

Receive_Open_Ind

see subclause 25.1.1.

1551

20.1.2 Tracing Co-ordinator for the SGSN

1552 The Tracing Co-ordinator process in the SGSN is shown in figure 20.1/2. The MAP process invokes a macro not 1553 defined in this clause; the definition of this macro can be found as follows: 1554

Receive_Open_Ind

see subclause 25.1.1.

1555

20.1.3 Subscriber Data Management Co-ordinator for the VLR

1556 The Subscriber Data Management Co-ordinator process in the VLR is shown in figure 20.1/3. The MAP process 1557 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1558

Receive_Open_Ind

see subclause 25.1.1.

1559

20.1.4 Subscriber Data Management Co-ordinator for the SGSN

1560 The Subscriber Data Management Co-ordinator process in the SGSN is shown in figure 20.1/4. The MAP process 1561 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1562

Receive_Open_Ind

see subclause 25.1.1.

1840

1841

process Co_Tracing_VLR
Co-or dinating pr ocess in the VLR to handle a dialogue opening request using the application context tr acingContext

Co_Tr_VLR1(1)
Signals to/from the left are to/from the child process; signals to/fr om the right are to/from the HLR

Null

Receive_ Open_Ind

Figure 25.1/1

Vr Per for m MAP Vr dialogue

OK

Error

Null

Null

Wait_For_ Service_ Primitive

MAP_ACTIVATE_ TRACE_MODE_ind

MAP_DEACT IVATE_ TRACE_MODE_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

ATM_Stand_ Alone_VLR

Figure 20.2/10

DTM_Stand_ Alone_VLR

Figure 20.2/14

MAP_ CLOSE_r eq

MAP_ACTIVATE_ TRACE_MODE_ind

MAP_DEACT IVATE_ TRACE_MODE_ind

Null

Relay_Info

MAP_U_ABORT_req, MAP_CLOSE_r eq

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

Null

Relay_Info

Null

Relay_Info

1563
1564

Figure 20.1/1: Process Co_Tracing_VLR

1842

1843

process Co_Tracing_SGSN
Co-or dinating pr ocess in the SGSN to handle a dialogue opening request using the application context tr acingContext

Co_Tr_SGSN1(1)
Signals to/from the left are to/from the child process; signals to/fr om the right are to/from the HLR

Null

Receive_ Open_Ind

Figure 25.1/1

Vr Per for m MAP Vr dialogue

OK

Error

Null

Null

Wait_For_ Service_ Primitive

MAP_ACTIVATE_ TRACE_MODE_ind

MAP_DEACT IVATE_ TRACE_MODE_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

ATM_Stand_ Alone_SGSN

Figure 20.2/11

DTM_Stand_ Alone_SGSN

Figure 20.2/15

MAP_ CLOSE_r eq

MAP_ACTIVATE_ TRACE_MODE_ind

MAP_DEACT IVATE_ TRACE_MODE_ind

Null

Relay_Info

MAP_U_ABORT_req, MAP_CLOSE_r eq

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

Null

Relay_Info

Null

Relay_Info

1565
1566

Figure 20.1/2: Process Co_Tracing_SGSN

1844

1845

process Co_SDM_VLR
Co-or dinating pr ocess in the VLR to handle a dialogue opening request using the application context subscriberDataMngtContext

Co_SDM_VLR1(1)
Signals to/from the left are to/from the child process; signals to/fr om the right are to/from the HLR

Null

Receive_ Open_Ind

Figure 25.1/1

Vr Per for m MAP Vr dialogue

OK

Error

Null

Null

Wait_For_ Service_ Primitive

MAP_INSERT _ SUBSCRIBER_ DATA_ind

MAP_DELETE_ SUBSCRIBER_ DATA_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

Ins_Subs_Data_ Stand_Alone_VLR

Figure 20.3/9

Delete_Subs_ Data_VLR

Figure 20.3/10

MAP_ CLOSE_r eq

MAP_INSERT _ SUBSCRIBER_ DATA_ind

MAP_DELETE_ SUBSCRIBER_ DATA_ind

Null

Relay_Info

MAP_U_ABORT_req, MAP_CLOSE_r eq

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

Null

Relay_Info

Null

Relay_Info

1567
1568

Figure 20.1/3: Process Co_SDM_VLR

1846

1847

process Co_SDM_SGSN
Co-or dinating pr ocess in the SGSN to handle a dialogue opening request using the application context subscriberDataMngtContext

Co_SDM_SGSN1(1)
Signals to/from the left ar e to/from the child process; signals to/fr om the right ar e to/from the HLR

Null

Receive_ Open_Ind

Figure 25.1/1

OK

Vr, Error

Null

Wait_For_ Service_ Primitive

MAP_INSERT _ SUBSCRIBER_ DATA_ind

MAP_DELETE_ SUBSCRIBER_ DATA_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

Ins_Subs_Data_ Stand_Alone_SGSN

Figure 20.3/11

Delete_Subs_ Data_SGSN

Figure 20.3/12

MAP_ CLOSE_r eq

MAP_INSERT _ SUBSCRIBER_ DATA_ind

MAP_DELETE_ SUBSCRIBER_ DATA_ind

Null

Relay_Info

MAP_U_ABORT_req, MAP_CLOSE_r eq

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

Null

Relay_Info

Null

Relay_Info

1569
1570

Figure 20.1/4: Process Co_SDM_SGSN

1848

1849

1571

20.2 Tracing procedures

i) Subscriber tracing management procedures; ii) Subscriber tracing procedures; iii) Event tracing procedures. The subscriber tracing management procedures are used to manage the status and the type of the tracing. The subscriber tracing activation procedure is used at location updating or data restoration when the trace mode of a subscriber is set active in the HLR or, as a stand alone procedure, when the subscriber is already registered and the trace mode becomes active in the HLR. The procedures to activate tracing in the VLR are shown in figures 20.2/1 and 20.2/3. The procedures to activate tracing in the SGSN are shown in figures 20.2/2 and 20.2/4.

1572 Three types of tracing procedures exist: 1573 1574 1575 1576 1577 1578 1579 1580

VLR

HLR 1

OMC

2 3

1581
1582 1583 1584 1585 1586 1587

1) 2) 3) 4)

Subscriber Tracing Activation MAP_ACTIVATE_TRACE_MODE_req/ind MAP_ACTIVATE_TRACE_MODE_rsp/cnf Subscriber Tracing Activation Accepted

1588

Figure 20.2/1: Stand-alone subscriber tracing activation procedure for non-GPRS

1589

SGSN

HLR 1

OMC

2 3

1590
1591 1592 1593 1594 1595 1596

1) 2) 3) 4)

Subscriber Tracing Activation MAP_ACTIVATE_TRACE_MODE_req/ind MAP_ACTIVATE_TRACE_MODE_rsp/cnf Subscriber Tracing Activation Accepted

1597 1598

Figure 20.2/2: Stand-alone subscriber tracing activation procedure for GPRS

1850

1851

VLR 1 2 3 4

HLR

1599
1600 1601 1602 1603 1604 1605

1) 2) 3) 4)

MAP_UPDATE_LOCATION or MAP_RESTORE_DATA_req/ind MAP_ACTIVATE_TRACE_MODE_req/ind MAP_ACTIVATE_TRACE_MODE_rsp/cnf MAP_UPDATE_LOCATION_rsp/cnf or MAP_RESTORE_DATA_rsp/cnf

1606 1607

Figure 20.2/3: Subscriber tracing activation procedure at location updating or data restoration

SGSN 1 2 3 4

HLR

1608
1609 1610 1611 1612 1613 1614

1) 2) 3) 4)

MAP_UPDATE_GPRS_LOCATION_req/ind MAP_ACTIVATE_TRACE_MODE_req/ind MAP_ACTIVATE_TRACE_MODE_rsp/cnf MAP_UPDATE_GPRS_LOCATION_rsp/cnf

1615

Figure 20.2/4: Subscriber tracing activation procedure at GPRS location updating

1616 The MAP_ACTIVATE_TRACE_MODE request includes the IMSI, trace reference, trace type and identity of the 1617 OMC. 1618 The subscriber tracing deactivation procedure is used when tracing of a subscriber in the VLR or in the SGSN is no 1619 longer required. The procedures are shown in figures 20.2/5 and 20.2/6.

1852

1853

VLR

HLR 1

OMC

2 3

1620
1621 1622 1623 1624 1625 1626

1) 2) 3) 4)

Subscriber Tracing Deactivation MAP_DEACTIVATE_TRACE_MODE_req/ind MAP_DEACTIVATE_TRACE_MODE_rsp/cnf Subscriber Tracing Deactivation Accepted

1627

Figure 20.2/5: Subscriber tracing deactivation procedure for non-GPRS

SGSN

HLR 1

OMC

2 3

1628
1629 1630 1631 1632 1633 1634

1) 2) 3) 4)

Subscriber Tracing Deactivation MAP_DEACTIVATE_TRACE_MODE_req/ind MAP_DEACTIVATE_TRACE_MODE_rsp/cnf Subscriber Tracing Deactivation Accepted

1635

Figure 20.2/6: Subscriber tracing deactivation procedure for GPRS

1636 The subscriber tracing procedures are used when the VLR detects any subscriber related activity for which the trace 1637 mode is activated, e.g. the VLR receives a MAP_PROCESS_ACCESS_REQUEST indication. The procedure is shown 1638 in figure 20.2/7.

MSC 1 2

VLR

OMC

1639
1640 1641 1642 1643 1644

1) 2) 3)

MAP_PROCESS_ACCESS_REQUEST_req/ind MAP_TRACE_SUBSCRIBER_ACTIVITY_req/ind Subscriber tracing information

1645

Figure 20.2/7: Subscriber tracing procedure in the serving MSC

1854

1855

1646 1647 20.2.1.1

20.2.1 Subscriber tracing activation procedure

Procedures in the HLR

1648 A subscriber tracing activation request from the OMC starts the appropriate process in the HLR: 1649 ATM_With_VLR_HLR if tracing is required in the MSC/VLR, ATM_With_SGSN_HLR if tracing is required in the 1650 SGSN. 1651 The process in the HLR to activate tracing in the VLR is shown in figure 20.2/8. The MAP process invokes macros not 1652 defined in this clause; the definitions of these macros can be found as follows: 1653 1654

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1655 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the 1656 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are 1657 operator options. 1658 The process in the HLR to activate tracing in the SGSN is shown in figure 20.2/9. The MAP process invokes macros 1659 not defined in this clause; the definitions of these macros can be found as follows: 1660 1661

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1662 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the 1663 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are 1664 operator options.

1665 20.2.1.2

Procedure in the VLR

1666 The process in the VLR to activate tracing in a stand-alone dialogue is shown in figure 20.2/10. The MAP process 1667 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1668

Check_Indication

see subclause 25.2.1.

1669 20.2.1.3

Procedure in the SGSN

1670 The process in the SGSN to activate tracing in a stand-alone dialogue is shown in figure 20.2/11. The MAP process 1671 invokes a macro not defined in this clause; the definition of this macro can be found as follows: 1672

Check_Indication

see subclause 25.2.1.

1673 1674 20.2.2.1

20.2.2 Subscriber tracing deactivation procedure

Procedures in the HLR

1675 A subscriber tracing deactivation request from the OMC starts the appropriate process in the HLR: 1676 DTM_HLR_With_VLR if tracing is no longer required in the MSC/VLR, DTM_HLR_With_SGSN if tracing is no 1677 longer required in the SGSN. 1678 The process in the HLR to deactivate tracing in the VLR is shown in figure 20.2/12. The MAP process invokes macros 1679 not defined in this clause; the definitions of these macros can be found as follows: 1680 1681

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1682 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the 1683 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are 1684 operator options.

1856

1857

1685 The process in the HLR to deactivate tracing in the SGSN is shown in figure 20.2/13. The MAP process invokes macros 1686 not defined in this clause; the definitions of these macros can be found as follows: 1687 1688

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1689 Sheet 1: If the Repeat attempt counter has reached its limit, the test "Repeat Attempt" takes the "No" exit; otherwise the 1690 test takes the "Yes" exit. The number of repeat attempts and the interval between successive repeat attempts are 1691 operator options.

1692 20.2.2.2

Procedure in the VLR

1693 The process in the VLR to deactivate tracing is shown in figure 20.2/14. The MAP process invokes a macro not defined 1694 in this clause; the definition of this macro can be found as follows: 1695

Check_Indication

see subclause 25.2.1.

1696 20.2.2.3

Procedure in the SGSN

1697 The process in the SGSN to deactivate tracing is shown in figure 20.2/15. The MAP process invokes a macro not 1698 defined in this clause; the definition of this macro can be found as follows: 1699

Check_Indication

see subclause 25.2.1.

1858

1859

process ATM_W ith_VLR_HLR

Process in the HLR to activate trace mode in the VLR using a stand-alone dialogue

ATM_VLR_HLR1(2)
Signals to/from the left ar e to/from the VLR; signals to/fr om the right ar e to/from the OMC

Null

OM_Subscriber _ Tracing_ Activation_ ind Yes No Subscriber known? Yes

Repeat attempt? No

Subscriber tracing active in VLR:=False

Subscriber tracing active in HLR False

True

Set User Err or : Tracing already active

Set User Err or : Unknown Subscriber

Set: Subscriber Tracing Activation Failure

Repeat attempt counter:= Repeat attempt counter+1

Subscriber tracing active in HLR:=True

OM_Subscriber_ Tracing_ Activation_ rsp

Start repeat attempt timer

Yes Subscriber deregistered? No

Null

Wait_For_ Timer_Expir y

Subscriber in home PLMN area? Yes

No

Internal

Repeat attempt timer expired

Repeat attempt counter:=0

Subscriber tracing active in VLR:=False

MAP_OPEN_req MAP_ACTIVATE_TRACE_MODE_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error

OK

Vr Perform MAP Vr dialogue OM_Subscriber _ Tracing_ Activation_ rsp

Wait_For_ ATM_Result

Null

Null

1700
1701

Figure 20.2/8 (sheet 1 of 2): Process ATM_With_VLR_HLR

1860

1861

process ATM_With_VLR_HLR
Process in the HLR to activate trace mode in the VLR using a stand-alone dialogue Wait_For_ ATM_Result

ATM_VLR_HLR2(2)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the OMC

MAP_ACTIVATE_TRACE_M ODE_cnf

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

MAP_ CLOSE_req

OK Subscriber tracing active in VLR:=True

User Error, Provider Error, Data Error 1

OM_Subscriber_ Tracing_ Activation_ rsp

Null

1702
1703

Figure 20.2/8 (sheet 2 of 2): Process ATM_With_VLR_HLR

1862

1863

process ATM_W ith_SGSN_HLR

Process in the HLR to activate trace mode in the SGSN using a stand-alone dialogue

ATM_SGSN_HLR1(2)
Signals to/from the left ar e to/from the SGSN; signals to/fr om the right ar e to/from the OMC

Null

OM_GPRS_ Subscriber_ Tracing_ Activation_ind Yes No

Repeat attempt? No

GPRS subscriber known? Yes

Subscriber tracing active in SGSN:=False

Subscriber tracing active in HLR False

True

Set User Err or : Tracing already active

Set User Err or : Unknown Subscriber

Set: Subscriber Tracing Activation Failure

Repeat attempt counter:= Repeat attempt counter+1

Subscriber tracing active in HLR:=True

OM_GPRS_ Subscr iber_ Tracing_ Activation_rsp

Start repeat attempt timer

Yes Subscriber deregistered? No

Null

Wait_For_ Timer_Expir y

Subscriber in home PLMN area? Yes

No

Internal

Repeat attempt timer expired

Repeat attempt counter:=0

Subscriber tracing active in SGSN:=F alse

MAP_OPEN_req MAP_ACTIVATE_TRACE_MODE_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error

OK

Vr Perform MAP Vr dialogue OM_GPRS_ Subscriber_ Tracing_ Activation_rsp

Wait_For_ ATM_Result

Null

Null

1704
1705

Figure 20.2/9 (sheet 1 of 2): Process ATM_with_SGSN_HLR

1864

1865

process ATM_With_SGSN_HLR
Process in the HLR to activate trace mode in the SGSN using a stand-alone dialogue Wait_For_ ATM_Result

ATM_SGSN_HLR2(2)
Signals to/from the left are to/from the SGSN; signals to/from the right are to/from the OMC

MAP_ACTIVATE_TRACE_M ODE_cnf

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

MAP_ CLOSE_req

OK Subscriber tracing active in SGSN:=True

User Error, Provider Error, Data Error 1

OM_GPRS_ Subscriber_ Tracing_ Activation_rsp

Null

1706
1707

Figure 20.2/9 (sheet 2 of 2): Process ATM_with_SGSN_HLR

1866

1867

process ATM_Stand_Alone_VLR
Process in the VLR to activate trace mode in a stand-alone-dialogue

ATM_SA_VLR1(1)
Signals to/from the right are to/from the HLR

Null

MAP_ACTIVATE_TRACE_M ODE_ind

Check_ Indication

Error

OK No Subscriber known? Yes

Tracing supported?

No

Yes Tracing buffer full? No Yes

Set User Error: Facility not supported

Subscriber tracing active:= True

Set User Error: Tracing buffer full

Set User Error: Unidentified subscriber

MAP_ACTIVATE_TRACE_M ODE_rsp MAP_CLOSE_req

1708
1709

Figure 20.2/10: Process ATM_Standalone_VLR

1868

1869

process ATM_Stand_Alone_SGSN
Process in the SGSN to activate trace mode in a stand-alone-dialogue

ATM_SA_SGSN1(1)
Signals to/from the right are to/from the HLR

Null

MAP_ACTIVATE_TRACE_M ODE_ind

Check_ Indication

Error

OK No Subscriber known? Yes

Tracing supported?

No

Yes Tracing buffer full? No Yes

Set User Error: Facility not supported

Subscriber tracing active:= True

Set User Error: Tracing buffer full

Set User Error: Unidentified subscriber

MAP_ACTIVATE_TRACE_M ODE_rsp MAP_CLOSE_req

1710
1711

Figure 20.2/11: Process ATM_Standalone_SGSN

1870

1871

process DTM_With_VLR_HLR
Process in the HLR to deactivate trace mode in the VLR using a stand-alone dialogue

DTM_VLR_HLR1(2)
Signals to/from the left ar e to/from the VLR; signals to/fr om the right ar e to/from the OMC

Null

Yes Repeat attempt? No Subscriber tracing active in VLR:=True

OM_Subscriber _ Tracing_ Deactivation_ ind No Subscriber known? Yes Set User Err or : Unknown Subscriber False

Set: Subscriber Tracing Deactivation Failure

Repeat attempt counter:= Repeat attempt counter+1

Subscriber tracing active in HLR True

OM_Subscriber_ Tracing_ Deactivation_ rsp

Start repeat attempt timer

Subscriber tracing active in HLR:=False

Null

Wait_For_ Timer_Expir y

Subscriber tracing active in VLR True

False

Internal

Repeat attempt timer expired

Repeat attempt counter:=0

MAP_OPEN_req MAP_DEACTIVAT E_TRACE_MODE_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error

OK

Vr Perform MAP Vr dialogue OM_Subscriber _ Tracing_ Deactivation_ rsp

Wait_For_ DTM_Result

Null

Null

1712
1713

Figure 20.2/12 (sheet 1 of 2): Process DTM_with_VLR_HLR

1872

1873

process DTM_With_VLR_HLR
Process in the HLR to deactivate trace m ode in the VLR using a stand-alone dialogue Wait_For_ DTM_Result

DTM_VLR_HLR2(2)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the OMC

MAP_DEACTIVATE_TRACE_MODE_cnf

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

MAP_ CLOSE_req

OK Subscriber tracing active in VLR:=False

User Error, Provider Error, Data Error 1

OM_Subscriber_ Tracing_ Deactivation_ rsp

Null

1714
1715

Figure 20.2/12 (sheet 2 of 2): Process DTM_with_VLR_HLR

1874

1875

process DTM_With_SGSN_HLR
Process in the HLR to deactivate trace mode in the VLR using a stand-alone dialogue

DTM_SGSN_HLR1(2)
Signals to/from the left ar e to/from the OMC; signals to/fr om the right ar e to/from the SGSN

Null

Yes Repeat attempt? No Subscriber tracing active in SGSN:=True

OM_GPRS_ Subscriber_ Tracing_ Deactivation_ind No Subscriber known? Yes Set User Err or : Unknown Subscriber False

Set: Subscriber Tracing Deactivation Failure

Repeat attempt counter:= Repeat attempt counter+1

Subscriber tracing active in HLR True

OM_GPRS_ Subscr iber_ Tracing_ Deactivation_rsp

Start repeat attempt timer

Subscriber tracing active in HLR:=False

Null

Wait_For_ Timer_Expir y

Subscriber tracing active in SGSN True

False

Internal

Repeat attempt timer expired

Repeat attempt counter:=0

MAP_OPEN_req MAP_DEACTIVAT E_TRACE_MODE_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error

OK

Vr Perform MAP Vr dialogue OM_GPRS_ Subscriber_ Tracing_ Deactivation_r sp

Wait_For_ DTM_Result

Null

Null

1716
1717

Figure 20.2/13 (sheet 1 of 2): Process DTM_with_SGSN_HLR

1876

1877

process DTM_With_SGSN_HLR
Process in the HLR to deactivate trace m ode in the VLR using a stand-alone dialogue Wait_For_ DTM_Result

DTM_SGSN_HLR2(2)
Signals to/from the left are to/from the SGSN; signals to/from the right are to/from the OMC

MAP_DEACTIVATE_TRACE_MODE_cnf

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

MAP_ CLOSE_req

OK Subscriber tracing active in SGSN:=False

User Error, Provider Error, Data Error 1

OM_GPRS_ Subscriber_ Tracing_ Deactivation_rsp

Null

1718
1719

Figure 20.2/13 (sheet 2 of 2): Process DTM_with_SGSN_HLR

1878

1879

process DTM_Stand_Alone_VLR
Process in the VLR to deactivate trace m ode in a stand-alone-dialogue

DTM_SA_VLR1(1)
Signals to/from the right are to/from the HLR

Null

MAP_DEACTIVATE_TRACE_MODE_ind

Check_ Indication

Error

OK No Subscriber known? Yes

Tracing supported?

No Set User Error: Facility not supported

Yes Subscriber tracing active:= False Set User Error: Unidentified subscriber

MAP_DEACTIVATE_TRACE_MODE_rsp MAP_CLOSE_req

1720
1721

Figure 20.2/14: Process DTM_Standalone_VLR

1880

1881

process DTM_Stand_Alone_SGSN
Process in the SGSN to deactivate trace m ode in a stand-alone-dialogue

DTM_SA_SGSN1(1)
Signals to/from the right are to/from the HLR

Null

MAP_DEACTIVATE_TRACE_MODE_ind

Check_ Indication

Error

OK No Subscriber known? Yes

Tracing supported?

No Set User Error: Facility not supported

Yes Subscriber tracing active:= False Set User Error: Unidentified subscriber

MAP_DEACTIVATE_TRACE_MODE_rsp MAP_CLOSE_req

1722
1723

Figure 20.2/15: Process DTM_Standalone_SGSN

1882

1883

1724

20.3 Subscriber data management procedures

1) Subscriber Deletion; 2) Subscriber Data Modification.

1725 Two types of subscriber data management procedures exist: 1726 1727

1728 The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.3/1 , 1729 20.3/2, 20.3/3 and 20.3/4).

VLR

HLR 1

OMC

2 3

1730
1731 1732 1733 1734 1735 1736

1) 2) 3) 4)

Delete Subscriber MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf Subscriber Deleted

1737

Figure 20.3/1: Subscriber deletion procedure for non-GPRS

1738 In the subscriber deletion procedure for a non-GPRS subscriber the subscriber data are removed from the VLR and the 1739 HLR. The HLR uses the MAP_CANCEL_LOCATION service.

SGSN

HLR 1

OMC

2 3

1740
1741 1742 1743 1744 1745 1746

1) 2) 3) 4)

Delete GPRS Subscriber MAP_CANCEL_LOCATION_req/ind MAP_CANCEL_LOCATION_rsp/cnf GPRS Subscriber Deleted

1747

Figure 20.3/2: Subscriber deletion procedure for GPRS

1748 In the subscriber deletion procedure for a GPRS subscriber the subscriber data are removed from the SGSN and the 1749 HLR. The HLR uses the MAP_CANCEL_LOCATION service.

1884

1885

VLR

HLR 1

OMC

2 3

1750
1751 1752 1753 1754 1755 1756 1757 1758

1) 2) 3) 4)

Modify Subscriber Data MAP_CANCEL_LOCATION_req/ind, MAP_INSERT_SUBSCRIBER_DATA_req/ind or MAP_DELETE_SUBSCRIBER_DATA_req/ind MAP_CANCEL_LOCATION_rsp/cnf, MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf or MAP_DELETE_SUBSCRIBER_DATA_rsp/cnf Subscriber Data Modified

1759
1760 1761 1762 1763 1764 1765 1766 1767

Figure 20.3/3: Subscriber data modification procedure for non-GPRS

1) 2) 3) 4) Modify Subscriber Data MAP_CANCEL_LOCATION_req/ind, MAP_INSERT_SUBSCRIBER_DATA_req/ind or MAP_DELETE_SUBSCRIBER_DATA_req/ind MAP_CANCEL_LOCATION_rsp/cnf, MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf or MAP_DELETE_SUBSCRIBER_DATA_rsp/cnf Subscriber Data Modified

1768

Figure 20.3/4: Subscriber data modification procedure for GPRS

1769 In the subscriber data modification procedure the subscriber data are modified in the HLR and when necessary also in 1770 the VLR or in the SGSN. The HLR initiates one of the MAP_INSERT_SUBSCRIBER_DATA, 1771 MAP_DELETE_SUBSCRIBER_DATA or MAP_CANCEL_LOCATION services depending on the modified data.

1772 1773 20.3.1.1

20.3.1 Subscriber deletion procedure

Procedure in the HLR

1774 The subscriber deletion process in the HLR is shown in figure 20.3/5. The MAP process invokes processes not defined 1775 in this clause; the definitions of these processes can be found as follows: 1776 1777

Cancel_GPRS_Location_Child_HLR Cancel_Location_Child_HLR

see subclause 19.1.2.2; see subclause 19.1.2.2.

1778 20.3.1.2

Procedure in the VLR

1779 The subscriber deletion procedure in the VLR is described in subclause 19.1.2.3 of the present document.

1780 20.3.1.3

Procedure in the SGSN

1781 The subscriber deletion procedure in the SGSN is described in subclause 19.1. 2.4 of the present document.

1886

1887

1782 1783 20.3.2.1

20.3.2 Subscriber data modification procedure

Procedure in the HLR

1784 The OMC can modify the subscriber data in several different ways. The modifications can be categorised in the 1785 following groups: 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799

1) data shall be modified in the HLR; no effect in the VLR; 2) data shall be modified in both the HLR and the VLR; 3) withdrawal of a basic service or a supplementary service requiring change to VLR data; 4) modification affects the roaming permission for the subscriber and the subscriber record shall be removed from the VLR data base; 5) withdrawal of non-GPRS Subscription caused by a change of Network Access Mode; 6) data shall be modified in the HLR; no effect in the SGSN; 7) data shall be modified in both the HLR and the SGSN; 8) withdrawal of GPRS subscription data or a basic service or a supplementary service requiring change to SGSN data; 9) modification affects the roaming permission for the subscriber and the subscriber record shall be removed from the SGSN data base; 10)withdrawal of GPRS Subscription caused by a change of Network Access Mode; 11)authentication algorithm or authentication key of the subscriber is modified.

1800 In cases 2 and 7 the HLR uses the MAP_INSERT_SUBSCRIBER_DATA service. 1801 In cases 3 and 8 the HLR uses the MAP_DELETE_SUBSCRIBER_DATA service. 1802 In cases 4, 5, 9, 10 and 11 the HLR uses the MAP_CANCEL_LOCATION service. 1803 If the deletion of subscriber data fails, the HLR may repeat the request; the number of repeat attempts and the time in 1804 between are HLR operator options, depending on the error returned by the VLR or the SGSN. 1805 The subscriber data modification process in the HLR is shown in figure 20.3/6. The MAP process invokes processes not 1806 defined in this clause; the definitions of these processes can be found as follows: 1807 1808 1809 1810

Insert_Subs_Data_Stand_Alone_HLR Cancel_Location_Child_HLR Insert_GPRS_Subs_Data_Stand_Alone_HLR Cancel_GPRS_Location_Child_HLR

see subclause 25.7.3; see subclause 19.1.2.2; see subclause 25.7.4; see subclause 19.1.2.2.

1811 The macro Delete_Subscriber_Data_HLR is shown in figure 20.3/7. The macro invokes macros not defined in this 1812 clause; the definitions of these macros can be found as follows: 1813 1814

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1815 The macro Delete_GPRS_Subscriber_Data_HLR is shown in figure 20.3/8. The macro invokes macros not defined in 1816 this clause; the definitions of these macros can be found as follows: 1817 1818

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1888

1889

1819 20.3.2.2

Procedures in the VLR

1820 The process in the VLR to update subscriber data in a stand-alone dialogue is shown in figure 20.3/9. The MAP process 1821 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 1822 1823

Check_Indication Insert_Subs_Data_VLR

see subclause 25.2.1; see subclause 25.7.1.

1824 The process in the VLR to delete subscriber data is shown in figure 20.3/10. The MAP process invokes a macro not 1825 defined in this clause; the definition of this macro can be found as follows: 1826

Check_Indication

see subclause 25.2.1.

1827 20.3.2.3

Procedures in the SGSN

1828 The process in the SGSN to update subscriber data in a stand-alone dialogue is shown in figure 20.3/11. The MAP 1829 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 1830 1831

Check_Indication Insert_Subs_Data_SGSN

see subclause 25.2.1; see subclause 25.7.2.

1832 The process in the SGSN to delete subscriber data is shown in figure 20.3/12. The MAP process invokes a macro not 1833 defined in this clause; the definition of this macro can be found as follows: 1834

Check_Indication

see subclause 25.2.1.

1890

1891

process Delete_Subscriber_HLR
Process in the HLR to delete a subscriber record from the SGSN and the VLR

Del_Sub_HLR1(1)
Signals to/from the right are to/from the OMC

Null

OM_Delete_ Subscriber_ ind

No Subscriber known? Yes

No Subscriber registered in an SGSN? Yes

Set User Error: Unknown subscriber

Cancel_GPRS_ Location_ Child_HLR

No Subscriber registered in a VLR? Yes

Cancel_ Location_ Child_HLR

Delete subscriber data from HLR

OM_Delete_ Subscriber_ rsp

Null

1835
1836

Figure 20.3/5: Process Delete_Subscriber_HLR

1892

1893

process Modify_Data_HLR
Process in the HLR to modify subscriber data in the SGSN and/or VLR

Mod_Dat_HLR1(2)
Signals to/from the right are to/from the OMC

Null

No Repeat operation? Yes

OM_Modify_ Subscriber_ Data_ind

No 2 Star t r epeat timer Subscriber known? Yes

Wait_For_ Timer_Expiry

OM_Modify_ Subscriber_ Data_rsp

Set User Err or : Unknown subscriber

Internal

Repeat timer expired

Modify subscriber data in HLR database

OM_Modify_ Subscriber_ Data_rsp

Yes

Subscriber registered in a VLR? No

Null

Type of modification

No effect in VLR

Data to be modified in VLR

Data to be deleted fr om VLR

Subscriber record to be deleted from VLR

Insert_Subs_ Data_Stand_ Alone_HLR

Delete_ Subscriber _ Data_HLR

Cancel_ Location_ Child_HLR

OK

Error

1837
1838

Figure 20.3/6 (sheet 1 of 2): Process Modify_Data_HLR

1894

1895

process Modify_Data_HLR
Process in the HLR to modify subscriber data in the SGSN and/or VLR 3

Mod_Dat_HLR2(2)

No Repeat operation? Yes

Null

Start repeat timer

Wait_For_ Timer_Expiry

Internal

Repeat timer expired

Yes

Subscriber registered in an SGSN? No

Type of modification

Null

No effect in SGSN

Data to be modified in SGSN

Data to be deleted from SGSN

Subscriber record to be deleted from SGSN

Insert_GPRS_ Subs_Data_ Stand_Alone_HLR

Delete_ Subscriber_ Data_HLR

Cancel_GPRS_ Location_ Child_HLR

OK

Error

Null

Null

Null

Null

1839
1840

Figure 20.3/6 (sheet 2 of 2): Process Modify_Data_HLR

1896

1897

macrodefinition Delete_Subscriber_Data_HLR
Macr o in the HLR to delete specific subscriber data from a VLR

DSD_HLR1(1)
Signals to/from the left are to/from the VLR

MAP_OPEN_req MAP_DELET E_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Per for m MAP Vr dialogue

OK Wait_For_ VLR_Response

Error

Error

No Successful result? Yes

MAP_DELETE_ SUBSCRIBER_ DATA_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

OK

Error

Check_ Confirmation

User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK

Error

Error

No Network Node Area Restr icted received OR Roaming Restriction Due To Unsuppor ted Feature Yes

MSC Area Restricted:= False

MSC Area Restricted:= True

OK

1841
1842

Figure 20.3/7: Macro Delete_Subscriber_Data_HLR

1898

1899

macrodefinition Delete_GPRS_Subscriber_Data_HLR
Macr o in the HLR to delete specific subscriber data from an SGSN

DGCSD_HLR(1)
Signals to/from the left are to/from the SGSN

MAP_OPEN_req MAP_DELET E_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ SGSN_Response

Vr, Error

Error

MAP_DELETE_ SUBSCRIBER_ DATA_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK

Error

Error

No Network Node Area Restr icted received OR Roaming Restricted in SGSN Due To Unsupported Feature Yes

SGSN Area Restricted:= False

SGSN Area Restricted:= True

OK

1843
1844

Figure 20.3/8: Macro Delete_GPRS_Subscriber_Data_HLR

1900

1901

process Ins_Subs_Data_Stand_Alone_VLR
Process in the VLR to handle Insert Subscriber Data requests in a stand-alone dialogue

ISD_SA_VLR1(2)
Signals to/from the right are to/from the HLR

Null

MAP_INSERT_ SUBSCRIBER_ DATA_ind

Check_ Indication

OK No IMSI known? Yes

Error

No

Update subscriber data for supported services & features

Yes

All received services & features supported?

Set parameters for unsupported services & features

Update subscriber data

Subscriber data confirmed by HLR:=False

Yes

MSC area restricted due to regional subscripti on? No

Set User Error: Unidentified Subscriber

Set network node area restricted

MAP_INSERT_SUBSCRIBER_DATA_rsp MAP_DELIMITER_req

Wait_For_ Service_ Indication

1845
1846

Figure 20.3/9 (sheet 1 of 2): Process Ins_Subs_Data_Stand_Alone_VLR

1902

1903

process Ins_Subs_Data_Stand_Alone_VLR
Process in the VLR to handle Insert Subscriber Data requests in a stand-alone dialogue Wait_For_ Service_ Indication

ISD_SA_VLR2(2)
Signals to/from the right are to/from the HLR

Insert_Subs_ Data_VLR

MAP_ CLOSE_ ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

Wait_For_ Service_ Indication

Store subscriber data in VLR

MAP_ CLOSE_ req

Subscriber data confirmed by HLR:=True

Subscriber data confirmed by HLR:=False

1847
1848

Figure 20.3/9 (sheet 2 of 2): Process Ins_Subs_Data_Stand_Alone_VLR

1904

1905

process Delete_Subs_Data_VLR
Process in the VLR to handle Delete Subscriber Data requests

DSD_VLR1(1)
Signals to/from the right are to/from the HLR

Null

MAP_DELETE_ SUBSCRIBER_ DATA_ind

Check_ Indication

OK No IMSI known? Yes

Error

Delete subscriber data from VLR

No Deletion successful? Yes

Yes

MSC area restricted due to regional subscripti on? No

Set network node area restricted

Subscriber data confirmed by HLR:=False

Subscriber data confirmed by HLR:=True

Set User Error: Unknown subscriber

Subscriber data confirmed by HLR:=Fal se

MAP_U_ ABORT_ req

MAP_DELETE_SUBSCRIBER_DATA_rsp MAP_CLOSE_req

1849
1850

Figure 20.3/10: Process Delete_Subs_Data_VLR

1906

1907

process Ins_Subs_Data_Stand_Alone_SGSN
Process in the SGSN to handle Insert Subscriber Data requests in a stand-alone dialogue

ISD_SA_SGSN1(2)
Signals to/from the right are to/from the HLR

Null

MAP_INSERT_ SUBSCRIBER_ DATA_ind

Check_ Indication

OK No IMSI known? Yes

Error

No

Update subscriber data for supported services & features

Yes

All received services & features supported?

Set parameters for unsupported services & features

Update subscriber data

Subscriber data confirmed by HLR:=False

Yes

SGSN area restricted due to regional subscripti on? No

Set User Error: Unidentified Subscriber

Set network node area restricted

MAP_INSERT_SUBSCRIBER_DATA_rsp MAP_DELIMITER_req

Wait_For_ Service_ Indication

1851
1852

Figure 20.3/11 (sheet 1 of 2): Process Ins_Subs_Data_Stand_Alone_SGSN

1908

1909

process Ins_Subs_Data_Stand_Alone_SGSN
Process in the SGSN to handle Inser t Subscriber Data r equests in a stand- alone dialogue Wait_For_ Service_ Indication

ISD_SA_SGSN2(2)
Signals to/from the right are to/from the HLR

Insert_Subs_ Data_SGSN

MAP_ CLOSE_ ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

Wait_For_ Ser vice_ Indication

Stor e subscriber data in SGSN

MAP_ CLOSE_ req

Subscriber data confir med by HLR:=True

Subscriber data confir med by HLR:=False

1853
1854

Figure 20.3/11 (sheet 2 of 2): Process Ins_Subs_Data_Stand_Alone_SGSN

1910

1911

process Delete_Subs_Data_SGSN
Process in the SGSN to handle Delete Subscriber Data requests

DSD_SGSN1(1)
Signals to/from the right are to/from the HLR

Null

MAP_DELETE_ SUBSCRIBER_ DATA_ind

Check_ Indication

OK No IMSI known? Yes

Error

Delete subscriber data from SGSN

No Deletion successful? Yes

Yes

SGSN area restricted due to regional subscripti on? No

Set network node area restricted

Subscriber data confirmed by HLR:=False

Subscriber data confirmed by HLR:=True

Set User Error: Unknown subscriber

Subscriber data confirmed by HLR:=Fal se

MAP_U_ ABORT_ req

MAP_DELETE_SUBSCRIBER_DATA_rsp MAP_CLOSE_req

1855
1856

Figure 20.3/12: Process Delete_Subs_Data_SGSN

1912

1913

1857

20.4 Subscriber Identity procedure

1858 In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in 1859 figure 20.4/1.

OMC 1

VLR

HLR

2 3

1860
1861 1862 1863 1864 1865

1) 2) 3) 4)

Identity request MAP_SEND_IMSI_req/ind MAP_SEND_IMSI_rsp/cnf Identity confirm

1866

Figure 20.4/1: The subscriber identity procedure

1867

20.4.1 Procedure in the VLR

1868 The subscriber identity process in the VLR is shown in figure 20.4/2. The MAP process invokes macros not defined in 1869 this clause; the definitions of these macros can be found as follows: 1870 1871

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1872

20.4.2 Procedure in the HLR

1873 The subscriber identity process in the HLR is shown in figure 20.4/3. The MAP process invokes macros not defined in 1874 this clause; the definitions of these macros can be found as follows: 1875 1876

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

1914

1915

1877

process Send_IMSI_VLR
Process in the VLR to request the IMSI of a subscriber from the HLR

SI_VLR1(1)
Signals to/from the left are to.from the OMC; signals to/from the right are to/from the HLR

Null

OM_Subscriber_Identity_ind

MAP_OPEN_req MAP_SEND_IMSI_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Yes Vr=V1? No

Error

OK Wait_For_ HLR_Response

Perform MAP Vr dialogue

Set User Error

MAP_SEND_ IMSI_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

Null

Check_ Confirmation

MAP_ CLOSE_ req

OK

User Error, Provider Error, Data Error Set User Error

OM_Subscriber_Identity_rsp

Null

1878
1879

Figure 20.4/2: Process Send_IMSI_VLR

1916

1917

process Send_IMSI_HLR
Process in the HLR to handle a request from the VLR for the IMSI of a subscriber

SI_HLR1(1)
Signals to/from the left are to/from the VLR

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr Perform MAP Vr dialogue

Error

Null

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

MAP_SEND_ IMSI_ind

Null

Null

MAP_ CLOSE_ req

Check_ Indication

OK No Null Subscriber known? Yes

Error

Fetch IMSI

Set User Error: Unknown subscriber

MAP_SEND_IMSI_rsp MAP_CLOSE_req

Null

1880
1881

Figure 20.4/3: Process Send_IMSI_HLR

1918

1919

1882 1883

21

Call handling procedures

21.1 General

1884 The MAP call handling procedures are used: 1885 1886 1887 1888 1889 1890 1891 1892

to retrieve routeing information to handle a mobile terminating call; to transfer control of a call back to the GMSC if the call is to be forwarded; to retrieve and transfer information between anchor MSC and relay MSC for inter MSC group calls / broadcast calls; to handle the reporting of MS status for call completion services; to handle the notification of remote user free for CCBS; to handle the alerting and termination of ongoing call activities for a specific subscriber; to handle early release of no longer needed resources.

1893 The procedures to handle a mobile originating call and a mobile terminating call after the call has arrived at the 1894 destination MSC do not require any signalling over a MAP interface. These procedures are specified in 3GPP TS 1895 23.018 [97]. 1896 1897 1898 1899 1900

The stage 2 specification for the retrieval of routeing information to handle a mobile terminating call is in 3GPP TS 23.018 [97]; modifications to this procedure for CAMEL are specified in 3GPP TS 23.078 [98], for optimal routeing of a basic mobile-to-mobile call in 3GPP TS 23.079 [99] and for CCBS in 3GPP TS 23.093 [107]. The interworking between the MAP signalling procedures and the call handling procedures for each entity (GMSC, HLR and VLR) is shown by the transfer of signals between these procedures.

1901 The stage 2 specification for the transfer of control of a call back to the GMSC if the call is to be forwarded is in 3GPP 1902 TS 23.079 [99]. The interworking between the MAP signalling procedures and the call handling procedures for each 1903 entity (VMSC and GMSC) is shown by the transfer of signals between these procedures. 1904 The stage 2 specifications for inter MSC group calls / broadcast calls are in 3GPP TS 43.068 [100] and 3GPP TS 1905 43.069 [101]. The interworking between the MAP signalling procedures and the group call /broadcast call procedures 1906 for each entity (Anchor MSC and Relay MSC) is shown by the transfer of signals between these procedures. 1907 The interworking between the call handling procedures and signalling protocols other than MAP are shown in 3GPP TS 1908 23.018, 3GPP TS 23.078 and 3GPP TS 23.079 [99]. 1909 The stage 2 specification for the handling of reporting of MS status for call completion services and notification of 1910 remote user free for CCBS is in 3GPP TS 23.093 [107].

1911 1912
1913 1914 1915 1916

21.2 Retrieval of routing information

21.2.1 General
The message flows for successful retrieval of routeing information for a mobile terminating call are shown in figure 21.2/1 (mobile terminating call which has not been optimally routed) and 21.2/2 (mobile-to-mobile call which has been optimally routed). The message flow for successful retrieval of routeing information for a gsmSCF initiated call is shown in figure 21.2/3.

1920

1921

PSTN/ ISDN

GMSC 1

HLR

VLR

3 4

MSC

5 6

7 8 11 12 13 14

10

1917
1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 12)

I_IAM (Note 1) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 2) MAP_PROVIDE_SUBSCRIBER_INFO_req/ind (Note 3, Note 4) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf (Note 4) MAP_SEND_ROUTING_INFORMATION_rsp/cnf (Note 4) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 4) MAP_PROVIDE_ROAMING_NUMBER_req/ind MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf MAP_SEND_ROUTING_INFORMATION_rsp/cnf I_IAM (Note 1) MAP_RESTORE_DATA_req/ind (Note 4) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 4) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 4) MAP_RESTORE_DATA_rsp/cnf (Note 4)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations and ETSI specification: - Q.721-725 - Telephone User Part (TUP); - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. NOTE 2: This service may also be used by an ISDN exchange for obtaining routing information from the HLR. NOTE 3: As a network operator option, the HLR sends MAP_PROVIDE_SUBSCRIBER_INFORMATION to the VLR. For further details on the CAMEL procedures refer to 3GPP TS 23.078 [98]. NOTE 4: Services printed in italics are optional.

1945

Figure 21.2/1: Message flow for retrieval of routeing information (non-optimally routed call)

1922

1923

VMSC

GMSC 1

HLR

VLR

3 4 5 6 9 10 11 12

MSC

1946
1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12)

I_IAM (Note 1) MAP_SEND_ROUTING_INFORMATION_req/ind MAP_PROVIDE_SUBSCRIBER_INFO_req/ind (Note 2) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf (Note 2) MAP_PROVIDE_ROAMING_NUMBER_req/ind (Note 2) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf (Note 2) MAP_SEND_ROUTING_INFORMATION_rsp/cnf I_IAM (Note 1) MAP_RESTORE_DATA_req/ind (Note 3) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3) MAP_RESTORE_DATA_rsp/cnf (Note 3)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations & ETSI specification: - Q.721-725 - Telephone User Part (TUP); - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. NOTE 2: For Optimal Routeing phase 1, only one of the information flows for Provide Subscriber Info and Provide Roaming Number is used. NOTE 3: Services printed in italics are optional.

1971 1972

Figure 21.2/2: Message flow for retrieval of routeing information (optimally routed call)

1924

1925

gsmSCF 1

HLR

VLR

2 3

4 5 7 8 9 10

1973
1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986

1) 2) 3) 4) 5) 6) 7) 8) 9) 10)

MAP_SEND_ROUTING_INFORMATION_req/ind MAP_SEND_ROUTING_INFORMATION_rsp/cnf (Note 1) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 1) MAP_PROVIDE_ROAMING_NUMBER_req/ind MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf MAP_SEND_ROUTING_INFORMATION_rsp/cnf MAP_RESTORE_DATA_req/ind (Note 1) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 1) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 1) MAP_RESTORE_DATA_rsp/cnf (Note 1)

NOTE 1: Services printed in italics are optional.

1987

Figure 21.2/3: Message flow for retrieval of routeing information for a gsmSCF initiated call

1988 The following MAP services are used to retrieve routing information: 1989 1990 1991 1992

MAP_SEND_ROUTING_INFORMATION MAP_PROVIDE_ROAMING_NUMBER MAP_PROVIDE_SUBSCRIBER_INFO MAP_RESTORE_DATA

see subclause 10.1; see subclause 10.2; see subclause 8.11.2; see subclause 8.10.3.

1993

21.2.2 Procedure in the GMSC

1994 The MAP process in the GMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.2/6. 1995 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 1996 1997

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

1998 Sheet 1: if the MAP_SEND_ROUTING_INFORMATION request included the OR Interrogation parameter, the test 1999 "OR interrogation?" takes the "Yes" exit; otherwise the test takes the "No" exit.

1926

1927

2000

21.2.9 Process in the gsmSCF

2001 For the purposes of retrieving routeing information from the HLR, the gsmSCF takes the role of the GMSC and 2002 follows the process specified in subclause 21.2.2.

2003

21.2.4 Procedure in the HLR

2004 The MAP process in the HLR to retrieve routeing information for a mobile terminating call is shown in figure 21.2/7. 2005 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2006 2007 2008

Receive_Open_Ind Receive_Open_Cnf Check_Confirmation

see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.2.

2009 Sheet 3: if the MAP_PROVIDE_ROAMING_NUMBER request included the OR Interrogation parameter, the test "OR 2010 interrogation?" takes the "Yes" exit; otherwise the test takes the "No" exit.

2011

21.2.5 Procedure in the VLR to provide a roaming number

2012 The MAP process in the VLR to provide a roaming number for a mobile terminating call is shown in figure 21.2/8. The 2013 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2014

Receive_Open_Ind

see subclause 25.1.1;

2015

21.2.6 Procedure in the VLR to restore subscriber data

2016 The MAP process in the HLR to restore subscriber data is shown in figure 21.2/9. The MAP process invokes macros 2017 not defined in this clause; the definitions of these macros can be found as follows: 2018 2019 2020 2021

Receive_Open_Cnf Check_Confirmation Insert_Subs_Data_VLR Activate_Tracing_VLR

see subclause 25.1.2; see subclause 25.2.2; see subclause 25.7.1; see subclause 25.9.4.

2022

21.2.7 Procedure in the VLR to provide subscriber information

2023 The MAP process in the VLR to provide subscriber information for a mobile terminating call subject to CAMEL 2024 invocation is shown in figure 21.2/9. The MAP process invokes a macro not defined in this clause; the definition of this 2025 macro can be found as follows: 2026

Receive_Open_Ind

see subclause 25.1.1;

1928

1929

process SRI_GMSC
Process in the GMSC to retrieve routeing information for an MT call

SRI_GMSC1(2)
Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.018); signals to/from the right are to/from the HLR

Idle

Send Routeing Info

MAP_OPEN_req MAP_SEND_ROUTING_INFORMATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr OR interrogation? Yes

Error

Abort No

MAP_SEND_ROUTING_INFORMATION_cnf

Set negative response: OR not allowed

Perform MAP Vr dialogue

Idle

Check_ Confirmation Provider Error, User Error, Data Error Send Routeing Info negative response

Send Routeing Info negative response

OK

Send Routeing Info ack

Idle

Idle

Idle

Idle

2027
2028

Figure 21.2/6 (sheet 1 of 2): Process SRI_GMSC

1930

1931

process SRI_GMSC
Process in the GMSC to retrieve routeing information for an MT call Wait_For_ HLR_Response

SRI_GMSC2(2)
Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.018); signals to/from the right are to/from the HLR

Abort

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Idle

MAP_ CLOSE_ req

Set negative response: System Failure

Send Routeing Info negative response

Idle

2029
2030

Figure 21.2/6 (sheet 2 of 2): Process SRI_GMSC

1932

1933

process SRI_HLR
Process in the HLR to handle a request for routeing information for an MT call

SRI_HLR1(3)
Signals to/from the left are to/from the GMSC; signals to/fr om the right are to/from the VLR unless mar ked otherwise

Idle

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Indication

Error

Idle

Idle

MAP_P_ ABORT_ ind

MAP_SEND_ROUTIN G_INFORMATION_ind

MAP_ NOTICE_ ind

Idle

Send Routeing Info

To HLR call handling application process

MAP_ CLOSE_ req

Wait_For_ Call_Handling_ Response

Idle

Send Routeing Info ack

From HLR call handling application process

Send Routeing Info negative response

From HLR call handling application process

Set result

Set err or

MAP_SEND_ROUTIN G_INFORMATION_rsp MAP_CLOSE_req

Idle

2031
2032

Figure 21.2/7 (sheet 1 of 3): Process SRI_HLR

1934

1935

process SRI_HLR
Process in the HLR to handle a request for routeing information for an MT call Wait_For_ Call_Handling_ Response

SRI_HLR2(3)
Signals to/fr om the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise From HLR call handling application process

Provide Subscr iber Info

MAP_OPEN_req MAP_PROVIDE_SUBSCRIBER_INFO_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK

Vr, Err or Set negative response: System failure

Provide Subscr iber Info negative response

To HLR call handling application process

Wait_For_ PSI_Response

Wait_For_ Call_Handling_ Response

MAP_PROVIDE_SUBSCRIBER_INF O_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ CLOSE_ req

Check_ Confirmation Pr ovider Error, User Error, Data Error To HLR call handling application pr ocess Provide Subscriber Info negative response To HLR call handling application pr ocess

Set negative response: System Failure

OK Provide Subscriber Info ack

Provide Subscr iber Info negative response

To HLR call handling application process

Wait_For_ Call_Handling_ Response

2033
2034

Figure 21.2/7 (sheet 2 of 3): Process SRI_HLR

1936

1937

process SRI_HLR
Process in the HLR to handle a request for routeing information for an MT call Wait_For_ Call_Handling_ Response

SRI_HLR3(3)
Signals to/fr om the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise From HLR call handling application pr ocess

Provide Roaming Number

MAP_OPEN_req MAP_PROVIDE_ROAMING_NUMBER_req MAP_DELIMITER_req

Receive_ Open_Cnf

Er ror Set negative response: System failure

OK

Vr Yes OR interrogation? No

Provide Roaming Number negative response

To HLR call handling application pr ocess

Perform MAP Vr dialogue

Set negative response: OR not allowed

Wait_For_ Call_Handling_ Response

MAP Vr dialogue result

To HLR call handling application process

Provide Roaming Number negative response

To HLR call handling application pr ocess

Wait_For_ PRN_Response

Wait_For_ Call_Handling_ Response

Wait_For_ Call_Handling_ Response

MAP_PROVIDE_ROAMING_NUMBER_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Check_ Confirmation

MAP_ CLOSE_ req

OK

Pr ovider Error, User Error, Data Error

Set negative response: System Failure

Provide Roaming Number ack

To HLR call handling application pr ocess

Provide Roaming Number negative response

To HLR call handling application pr ocess

Provide Roaming Number negative response

To HLR call handling application process

Wait_For_ Call_Handling_ Response

2035
2036

Figure 21.2/7 (sheet 3 of 3): Process SRI_HLR

1938

1939

process PRN_VLR
Process in the VLR to handle a request for a roaming number

PRN_VLR1(1)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the VLR (see 3GPP TS 23.018)

Idle

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Indication

Error

Idle

Idle

MAP_P_ ABORT_ ind

MAP_PROVIDE_ROAMING_NUMBER_ind

MAP_ NOTICE_ ind

Idle

Provide Roaming Number

MAP_ CLOSE_ req

Wait_For_ Roaming_ Number

Idle

Provide Roaming Number ack

Provide Roaming Number negative r esponse

Set result

Set err or

MAP_PROVIDE_ROAMING_NUMBER_rsp MAP_CLOSE_req

Idle

2037
2038

Figure 21.2/8: Process PRN_VLR

1940

1941

process Restore_Data_VLR
Process in the VLR to request restoration of subscriber data

RD_VLR1(1)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the VLR (see 3GPP TS 23.018) Idle

Restore Data

MAP_OPEN_req MAP_RESTORE_DATA_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK Wait_For_ HLR_Response Restore Data negative response

Error

Idle

Insert_ Subs_Data_ VLR

Activate_ Tracing_ VLR

MAP_RESTORE_DATA_cnf

Idle

Wait_For_ HLR_Response

Check_ Confirmation User Error, Provider Error, Data Error Restore Data negative response

OK MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind MAP_ NOTICE_ ind Restore Data ack

MAP_ CLOSE_ req Idle

Restore Data negative response

Idle

2039
2040

Figure 21.2/9: Process Restore_Data_VLR

1942

1943

process PSI_VLR
Process in the VLR to handle a request for subscriber information

PSI_VLR1(1)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the VLR (see 3GPP TS 23.018)

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Err or

Idle

MAP_P_ ABORT_ ind

MAP_PROVIDE_SUBSCRIBER_INFO_ind

MAP_ NOTICE_ ind

Idle

Provide Subscriber Info

MAP_ CLOSE_ req

Wait_For_ Subscriber _ Info

Idle

Provide Subscriber Info ack

Provide Subscriber Info negative r esponse

Set result

Set err or

MAP_PROVIDE_SUBSCRIBER_INFO_rsp MAP_CLOSE_req

Idle

2041
2042

Figure 21.2/10: Process PSI_VLR

1944

1945

2043 2044

21.3 Transfer of call handling

21.3.1 General

2045 The message flow for successful transfer of call handling to forward a call is shown in figure 21.3/1.
ForwardedTo Local Exchange

GMSC 1 2 3

HLR

VMSC

4 5 6

2046
2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062

1) 2) 3) 4) 5) 6)

MAP_RESUME_CALL_HANDLING_req/ind MAP_SEND_ROUTING_INFORMATION_req/ind (Note 2) MAP_SEND_ROUTING_INFORMATION_rsp/cnf (Note 2) MAP_RESUME_CALL_HANDLING_rsp/cnf I_REL (Note 1) I_IAM (Note 1)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations & ETSI specification: - Q.721-725 - Telephone User Part (TUP); - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. NOTE 2: Services printed in italics are optional.

2063

Figure 21.3/1: Message flow for transfer of call handling If the HLR indicated in the response to the original request for routeing information that forwarding interrogation is required, the GMSC executes the Send Routeing Information procedure with the HLR to obtain forwarding information; otherwise the GMSC uses the forwarding data which were sent in the MAP_RESUME_CALL_HANDLING req/ind.

2064 2065 2066 2067

2068

21.3.2 Process in the VMSC

2069 The MAP process in the VMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.3/2. 2070 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2071 2072

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2073 If the capacity of a message signal unit in the lower layers of the protocol is enough to carry all the information which 2074 has to be sent to the GMSC, the test "Segmentation needed?" takes the "No" exit; otherwise the test takes the "Yes" 2075 exit.

1946

1947

2076

21.3.3 Process in the GMSC

2077 The MAP process in the GMSC to handle a request for the GMSC to resume call handling is shown in figure 21.3/3. 2078 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2079

Receive_Open_Ind

see subclause 25.1.1;

2080 If the parameter All Information Sent was present in the MAP_RESUME_CALL_HANDLING indication, the test "All 2081 Information Sent" takes the "Yes" exit; otherwise the test takes the "No" exit.

1948

1949

process RCH_VMSC
Process in the VMSC to request the GMSC to r esume call handling

RCH_VMSC1(1)
Signals to/fr om the left are to/from the GMSC; signals to/from the right are to/from the application process in the VMSC (see 3GPP TS 23.079) Idle

Resume Call Handling

Yes Segmentation needed? No Set: All Information Sent Segmentation needed? No Set: All Information Sent

Yes

MAP_RESUME_CALL_HANDLING_req MAP_DELIMITER_req

MAP_OPEN_req MAP_RESUME_CALL_HANDLING_req MAP_DELIMITER_req

Wait_For_ GMSC Response

Receive_ Open_Cnf

OK Wait_For_ GMSC Response

Vr, Err or Resume Call Handling negative response

MAP_RESUME_CALL_HANDLING_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_CLOSE_ind

Idle

Check_ Confirmation

MAP_ CLOSE_ req

OK All information sent? No Resume C all Handling ack Yes

Pr ovider Error, User Error, Data Error

Set negative response: System failure

Resume C all Handling negative response

Resume C all Handling negative response

Idle

Idle

Idle

2082
2083

Figure 21.3/2: Process RCH_VMSC

1950

1951

process RCH_GMSC
Process in the GMSC to handle a request to resume call handling

RCH_GMSC1(1)
Signals to/from the left ar e to/from the application pr ocess in the GMSC (see 3GPP TS 23.079); signals to/fr om the right ar e to/from the VMSC; Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Err or

Idle

MAP_P_ ABORT_ ind

MAP_RESUME_CALL_HANDLING_ind

MAP_ NOTICE_ ind

Idle

All Information Sent? Yes Assemble received data

No

MAP_ CLOSE_ req

Stor e received data

Idle

Resume Call Handling

MAP_RESUME_CALL_HANDLING_rsp MAP_DELIMITER_req

Wait_For_ Call_Handling_ Response

Wait_For_ Ser vice_ Indication

Resume Call Handling ack

Resume Call Handling negative response

Set Result

Set Error

MAP_RESUME_CALL_HANDLING_rsp MAP_CLOSE_req

Idle

2084
2085

Figure 21.3/3: Process RCH_GMSC

1952

1953

2086 2087

21.4 Inter MSC Group Call Procedures

21.4.1 General

2088 The message flow for successful inter MSC group call / broadcast call set-up is shown in figure 21.4/1.
PSTN/ ISDN Anchor MSC 1 Relay MSC

2 3 4 5 6 8 9 10

11

12

2089
2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12)

I_IAM (Note 1) MAP_PREPARE_GROUP_CALL_req/ind MAP_PREPARE_GROUP_CALL_rsp/cnf I_IAM (Note 1) MAP_SEND_GROUP_CALL_END_SIGNAL_req/ind I_ACM (Note 1) I_ACM (Note 1) MAP_FORWARD_GROUP_CALL_SIGNALLING_req/ind (Note 2) MAP_PROCESS_GROUP_CALL_SIGNALLING_req/ind (Note 2) MAP_SEND_GROUP_CALL_END_SIGNAL_rsp/cnf I_REL (Note 3) I_REL (Note 3)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations and ETSI specification: - Q.721-725 - Telephone User Part (TUP); - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. NOTE 2: The MAP_FORWARD_GROUP_CALL_SIGNALLING and MAP_PROCESS_GROUP_CALL_SIGNALLING services are not applicable for voice broadcast calls. NOTE 3: The call can be released from the PSTN/ISDN or the Relay MSC

2114

Figure 21.4/1: Message flow for inter MSC group call / broadcast call

2115

21.4.2 Process in the Anchor MSC

1954

1955

2116 The MAP process in the Anchor MSC to retrieve and transfer information from / to the Relay MSC for VBS and VGCS 2117 calls is shown in figure 21.4/2. The MAP process invokes macros not defined in this clause; the definitions of these 2118 macros can be found as follows: 2119 2120 2121

Receive_Open_Cnf Check_Indication Check_Confirmation

see subclause 25.1.2; see subclause 25.2.1; see subclause 25.2.2.

2122

21.4.3 Process in the Relay MSC

2123 The MAP process in the Relay MSC to receive and transfer information from / to the Anchor MSC for VBS and VGCS 2124 calls is shown in figure 21.4/3. The MAP process invokes macros not defined in this clause; the definitions of these 2125 macros can be found as follows: 2126 2127

Receive_Open_Ind Check_Indication

see subclause 25.1.2; see subclause 25.2.1.

1956

1957

process ASCI_Anchor_MSC
Process in the Anchor MSC for ASCI call handling

AA_MSC1(2)
Signals to/from the left are to/from the ASCI call handling process in the anchor MSC; signals to/from the right are to/from the Relay MSC

Idle

Prepare Group Call

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_OPEN_req MAP_PREPARE_GROUP_CALL_req MAP_DELIMITER_req

MAP_ CLOSE_ req

Receive_ Open_Cnf

Abort

Vr , Error

OK Wait_For_ Gr oup_Call_ Number

Abort

Idle

Idle

MAP_PREPARE_GROUP_CALL_cnf

Check_ Confirmation User Error, Data Error Prepare Group Call negative response

OK Prepare Group Call ack

Provider Error Prepare Group Call negative response

Wait_For_ Call_ Completion

Idle

MAP_U_ ABORT_ req

Idle

2128
2129

Figure 21.4/2 (sheet 1 of 2): Process ASCI_Anchor_MSC

1958

1959

process ASCI_Anchor_MSC
Process in the Anchor MSC for ASCI call handling Wait_For_ Call_ Completion

AA_MSC2(2)
Signals to/fr om the left are to/from the ASCI call handling process in the anchor MSC; signals to/from the right are to/from the Relay MSC

MAP_SEND_GROUP_CALL_END_SIGNAL_ind

Check_ Indication

Error

OK Send Group Call End Signal

Abort

MAP_U_ ABORT_req

Uplink_ Management

Idle

Forward Group C all Signalling

MAP_PROCESS_GROUP_CALL_SIGNALLING_ind

MAP_FORWAR D_GROUP_CALL_SIGNALLING_req MAP_DELIMITER_req

Check_ Indication

Er ror Uplink_ Management Uplink_ Management

OK Process Group C all Signalling

Abort

Send Group Call End Signal ack

MAP_U_ ABORT_req

Uplink_ Management

MAP_SEND_GROUP_CALL_END_SIGNAL_rsp MAP_CLOSE_req

Idle

Idle

2130
2131

Figure 21.4/2 (sheet 2 of 2): Process ASCI_Anchor_MSC

1960

1961

process ASCI_Relay_MSC
Process in the Relay MSC for ASCI call handling

AR_MSC1(2)
Signals to/from the left are to/from the Relay MSC; signals to/from the right are to/from the ASCI call handling process in the relay MSC Idle

Receive_ Open_Ind

Vr, Error

OK Wait_For_ Service_ Indication

Idle

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

MAP_PREPARE_GROUP_CALL_ind

Idle

MAP_ CLOSE_ req

Check_ Indication

Error MAP_U_ ABORT_ req

OK

Idle

Prepare Group Call

Idle

Wait_For_ Gr oup_Call_ Number

Prepare Group Call ack

Prepare Group Call negative response

Set result

Set error

MAP_PREPARE_GROUP_CALL_rsp MAP_DELIMITER_req

MAP_PREPARE_GROUP_CALL_rsp MAP_CLOSE_req

Wait_For_ End_Signal

Idle

2132
2133

Figure 21.4/3 (sheet 1 of 2): Process ASCI_Relay_MSC

1962

1963

process ASCI_Relay_MSC
Process in the Relay MSC for ASCI call handling Wait_For_ End_Signal

AR_MSC2(2)
Signals to/fr om the left are to/from the Relay MSC; signals to/from the right are to/from the ASCI call handling process in the relay MSC

Send Group Call End Signal

MAP_SEND_GROUP_CALL_END_SIGNAL_req MAP_DELIMITER_req

Uplink_ Management

MAP_FORWAR D_GROUP_CALL_SIGNALLING_ind

Process Group C all Signalling

Check_ Indication

MAP_PROCESS_GROUP_CALL_SIGNALLING_r eq MAP_DELIMITER_req

Er ror Forward Group C all Signalling

OK Uplink_ Management

Abort

MAP_U_ ABORT_ req

Uplink_ Management

Idle

Wait_For_Group_Call_Number, Wait_For_End_Signal, Uplink_Management

Uplink_ Management

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_SEND_GROUP_CALL_END_SIGNAL_cnf

No VGCS? MAP_ CLOSE_ req Yes

Send Group Call End Signal ack Abort

Idle

Idle

2134
2135

Figure 21.4/3 (sheet 2 of 2): Process ASCI_Relay_MSC

1964

1965

2136 2137

21.4AInter MSC Group Call Info Retrieval

21.4A.1 General

2138 The message flow for successful inter MSC group call info retrieval is shown in figure 21.4A/1.

MSC

MSC

MAP Send Group Call Info req/ind

MAP Send Group Call Info rsp/cnf

2139
2140

Figure 21.4A/1: Message flow for inter MSC group call info retrieval

2141

21.4A.2 Process in the MSC

2142 The MAP process in the MSC to retrieve and group call information is shown in figure 21.4A/2. The MAP process 2143 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2144 2145 2146

Receive_Open_Cnf Check_Confirmation Receive_Open_Ind

see subclause 25.1.2; see subclause 25.2.2. see subclause 25.1.2;

1966

1967

process Group_Call_Info_Retrieval_MSC
process in the MSC to send and receive Group Call Info Retrieval messages

GCIR_MSC(2)

Signals to/from the left are to/from the application process in the MSC; signals to/from the right are to/from the distant MSC

Idle

Send Group_ Call_Info

MAP_OPEN_req, MAP_SEND_GROUP_CALL_INFO_req, MAP_DELIMITER_req

Receive_ Open_Cnf OK Wait_For_ Distant_MSC_ Response Vr, Error Send_Group_Call_ Info negative response

MAP_SEND_GROUP_ CALL_INFO_cnf

MAP_NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Idle

Check_ Confirmation User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK Send_Group_ Call_Info_ ack

Send_Group_Call_ Info negative response

Idle

2147
2148

Figure 21.4A/2 (sheet 1 of 2): Process Group_Call_Info_Retrieval_MSC

1968

1969

process Group_Call_Info_Retrieval_MSC
process in the MSC to send and receive Group Call Info Retrieval messages

GCRI_MSC(2)
Signals to/from the left are to/from the application process in the MSC; signals to/from the right are to/from the distant MSC

Idle

Receive_ Open_ind OK Vr, Error

Wait_For_ Service_ Indication

Idle

MAP_P_ ABORT_ind

MAP_SEND_ GROUP_CALL_ INFO_ind

MAP_ NOTICE_ ind

Idle

Send_Group_ Call_info

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Idle

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Send_Group_ Call_Info_ ack

Send_Group_ Call_Info_ negative response

Set User Error

MAP_SEND_GROUP_CALL_INFO_rsp MAP_CLOSE_req

Idle

2149
2150

Figure 21.4A/2 (sheet 2 of 2): Process Group_Call_Info_Retrieval_MSC

1970

1971

2151 2152 2153 2154

21.5 Void 21.6 CCBS: monitoring and reporting the status of the subscriber
21.6.1 Reporting co-ordinator process in the VLR

2155 The MAP co-ordinating process in the VLR to handle a dialogue opened with the reporting application context is shown 2156 in figure 21.6/6. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found 2157 as follows: 2158 2159

Receive_Open_Ind

see subclause 25.1.1.

2160

21.6.2 Setting the reporting state stand-alone

2161 The message flow for setting the reporting state in a stand-alone dialogue is shown in figure 21.6/1.

VLR 1 2

HLR

2162
2163 2164 2165 2166

1) 2)

MAP_SET_REPORTING_STATE_req/ind MAP_SET_REPORTING_STATE_rsp/cnf

2167

Figure 21.6/1: Message flow for setting the reporting state stand-alone dialogue

2168 21.6.2.1

Process in the HLR

2169 The MAP process in the HLR to set the reporting state in the VLR in a stand-alone dialogue is shown in figure 21.6/7. 2170 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2171 2172

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2173 The result of a request to stop reporting is not reported to the CCBS application in the HLR.

2174 21.6.2.2

Process in the VLR

2175 The MAP process in the VLR to set the reporting state is shown in figure 21.6/8. 2176 The macro Set_Reporting_State_VLR is shown in figure 21.6/9.

2177

21.6.3 Status Reporting

2178 The message flows for reporting the status of a subscriber are shown in figures 21.6/2 and 21.6/3.
1972

1973

VLR 1 2

HLR

2179
2180 2181 2182 2183

1) 2)

MAP_STATUS_REPORT_req/ind MAP_STATUS_REPORT_rsp/cnf

2184

Figure 21.6/2: Message flow for status reporting, when monitoring continues in the VLR

VLR 1 2 3 4

HLR

2185
2186 2187 2188 2189 2190 2191

1) 2) 3) 4)

MAP_STATUS_REPORT_req/ind MAP_STATUS_REPORT_rsp/cnf MAP_SET_REPORTING_STATE_req/ind MAP_SET_REPORTING_STATE_rsp/cnf

2192

Figure 21.6/3: Message flow for status reporting, when monitoring stops

2193 The MAP_SET_REPORTING_STATE request is used to stop monitoring in the VLR. If the HLR requires the VLR to 2194 continue monitoring, it closes the dialogue without sending a MAP_SET_REPORTING_STATE request.

2195 21.6.3.1

Process in the VLR

2196 The MAP process in the VLR to send a status report to the HLR is shown in figure 21.6/10. The MAP process invokes 2197 macros not defined in this clause; the definitions of these macros can be found as follows: 2198 2199

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2200 This process can be used to report: 2201 2202

an event, such as the user becoming free, or the result of a CCBS call attempt

2203 to the HLR

1974

1975

2204 21.6.3.2

Process in the HLR

2205 The MAP process in the HLR to handle a status report is shown in figure 21.6/11. The MAP process invokes a macro 2206 not defined in this clause; the definition of this macro can be found as follows: 2207

Receive_Open_Ind

see subclause 25.1.1;

2208 It is an implementation option whether to send the MAP_DELIMITER request before invoking the macro 2209 Set_Reporting_State_HLR. 2210 The macro Receive_Status_Report_HLR is shown in figure 21.6/12. 2211 The macro Set_Reporting_State_HLR is shown in figure 21.6/13. The macro invokes a macro not defined in this 2212 clause; the definition of this macro can be found as follows: 2213

Check_Confirmation

see subclause 25.2.2.

2214

21.6.4 CCBS: Remote User Free

2215 The message flows for handling remote user free are shown in figures 21.6/4 and 21.6/5.

VLR 1 2

HLR

2216
2217 2218 2219 2220

1) 2)

MAP_REMOTE_USER_FREE_req/ind MAP_REMOTE_USER_FREE_rsp/cnf

2221

Figure 21.6/4: Remote User Free: recall not accepted

VLR 1 2 3 4

HLR

2222
2223 2224 2225 2226 2227 2228 1976

1) 2) 3) 4)

MAP_REMOTE_USER_FREE_req/ind MAP_REMOTE_USER_FREE_rsp/cnf MAP_STATUS_REPORT_req/ind MAP_STATUS_REPORT_rsp/cnf

1977

2229

Figure 21.6/5: Remote User Free: recall accepted

2230 21.6.4.1

Process in the HLR

2231 The MAP process in the HLR to handle Remote User Free is shown in figure 21.6/14. The MAP process invokes 2232 macros not defined in this clause; the definitions of these macros can be found as follows: 2233 2234

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2235 21.6.3.2

Process in the VLR

2236 The MAP process in the VLR to handle Remote User Free is shown in figure 21.6/15. The MAP process invokes a 2237 macro not defined in this clause; the definition of this macro can be found as follows: 2238

Check_Confirmation

see subclause 25.2.2.

1978

1979

process Reporting_Coord_VLR
Co-or dinating pr ocess in the VLR to handle a dialogue opened with the AC ReportingContext

Rep_Co_VLR1(1)
Signals to/from the left ar e to/from the HLR; signals to/fr om the right ar e to/from the child process

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Err or

Idle

MAP_ REMOTE_ USER_FREE_ ind

MAP_SET_ REPORTING_ STATE_ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Remote_User _ Free_VLR

Set_Repor ting_ State_VLR

MAP_ CLOSE_ req

MAP_ REMOTE_ USER_FREE_ ind

MAP_SET_ REPORTING_ STATE_ind

Idle

Relay_ Information

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

Idle

Relay_ Information

Idle

Relay_ Information

2239
2240

Figure 21.6/6: Process Reporting_Coord_VLR

1980

1981

process Set_Reporting_State_Stand_Alone_HLR
Process in the HLR to set the reporting state in the VLR using a separate dialogue

SRS_SA_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093)

Idle

Start reporting

Stop reporting

Set required reporting state: Start

Set required reporting state: Stop

MAP_OPEN_req MAP_SET_REPORTING_STATE_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK No Wait_For_ VLR_Response

Vr, Error

Required reporting state=Start? Yes

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_SET_ REPORTING_ STATE_cnf

Start reporting negative response

MAP_ CLOSE_ req

User Error, Provider Error, Data Error

Check_ Confirmation

Idle

OK No Required reporti ng state=Start? Yes Yes No Required reporti ng state=Start?

Start reporting negative response

Start reporting ack

Idle

Idle

2241
2242

Figure 21.6/7: Process Set_Reporting_State_Stand_Alone_HLR

1982

1983

process Set_Reporting_State_VLR
Process in the VLR to handle a r equerst from the HLR to set the reporting state for a subscriber

SRS_VLR1(1)
Signals to/from the right are to/from the HLR

Idle

Receive_Set_ Repor ting_ State_VLR

MAP_ CLOSE_ req

2243
2244

Figure 21.6/8: Process Set_Reporting_State_VLR

1984

1985

macrodefinition Receive_Set_Reporting_State_VLR
Macro in the VLR to handle a request from the HLR to set the reporting state for a subscriber

RSRS_VLR1(1)
Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR

MAP_SET_ REPORTING_ STATE_ind

No Required reporti ng state=Start? Yes

Stop Reporting

Start Reporting

Wait_For_ Application_ Response

Start Reporting ack

Start Reporting negative response

Set User Error

MAP_SET_ REPORTING_ STATE_rsp

2245
2246

Figure 21.6/9: Macro Receive_Set_Reporting_State_VLR

1986

1987

process Send_Status_Report_VLR
Process in the VLR to send a status report to the H LR

SSR_VLR1(2)
Signals to/fr om the left ar e to/from the CC BS application pr ocess in the VLR (see 3GPP TS 23.093); signals to/from the right ar e to/from the HLR Idle

Event Report

CC BS Call Report

Build MAP message

Build MAP message

Include call report data

MAP_OPEN_req MAP_STATUS_REPOR T_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Err or

MAP_STATUS_ REPORT_ cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Check_ Confirmation

User Error, Pr ovider Error, Data Error

MAP_ CLOSE_ req

OK No CCBS call repor t data present? Yes Yes No CCBS call repor t data pr esent?

Event Report ack

CC BS Call Report ack

Event Report negative response

CCBS Call Repor t negative r esponse

Wait_For_ Set_Reporting_ State

Idle

2247
2248

Figure 21.6/10 (sheet 1 of 2): Process Send_Status_Report_VLR

1988

1989

process Send_Status_Report_VLR
Process in the VLR to send a status report to the HLR Wait_For_ Set_Reporting_ State

SSR_VLR2(2)
Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR

Receive_Set_ Reporting_ State_VLR

MAP_ CLOSE_ ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ CLOSE_ req

Continue Monitoring

MAP_ CLOSE_ req

Idle

Idle

Idle

Idle

2249
2250

Figure 21.6/10 (sheet 2 of 2): Process Send_Status_Report_VLR

1990

1991

process Status_Report_HLR
Process in the HLR to handle a status report from the VLR

SR_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application proccess in the HLR (see 3GPP TS 23.093

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_P_ ABORT_ ind

Receive_ Status_ Report_HLR

MAP_ NOTICE_ ind

Idle

Wait_For_ Application_ Response

MAP_ CLOSE_ req

Continue Monitoring

Stop Reporting

Idle

MAP_ CLOSE_ req

Set required reporting state: Stop

Idle

MAP_ DELIMITER_ req

Set_Reporting_ State_HLR

OK, Error, Aborted

Idle

2251
2252

Figure 21.6/11: Process Status Report_HLR

1992

1993

macrodefinition Receive_Status_Report_HLR
Macro in the HLR to receive a status report from the VLR

RSR_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application proccess in the HLR (see 3GPP TS 23.093

MAP_ STATUS_ REPORT_ind

Yes CCBS call report data present? No

CCBS Call Report

Event Report

Wait_For_ Application_ Response

CCBS Call Report ack

CCBS Call Report negative response

Event Report ack

Event Report negative response

Set User Error

Set User Error

MAP_ STATUS_ REPORT_rsp

2253
2254

Figure 21.6/12: Macro Receive_Status_Report_HLR

1994

1995

macrodefinition Set_Reporting_State_HLR
Macr o in the HLR to instr uct the VLR to set the reporting state for a subscriber

SRS_HLR1(1)
Signals to/from the left are to/from the VLR

MAP_SET_REPORTING_STATE_req MAP_DELIMITER_req

Wait_For_ VLR_Response

MAP_SET_ REPORTING_ STATE_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK

OK

Error

Aborted

2255
2256

Figure 21.6/13: Macro Set_Reporting_State_HLR

1996

1997

process Remote_User_Free_HLR
Process in the HLR to send a Remote User Free notification to the VLR

RUF_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application proccess in the HLR (see 3GPP TS 23.093) Idle

CCBS RUF

MAP_OPEN_req MAP_REMOTE_USER_FREE_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ VLR_Response

Vr, Error

MAP_ REMOTE_ USER_ FREE_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK

CCBS RUF ack

Wait_For_ Status_Report

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Receive_ Status_Report_ HLR

Abort

Set negative response: System fai lure

MAP_ CLOSE_ req

CCBS RUF negative resonse

Idle

Idle

Idle

2257
2258

Figure 21.6/14: Process Remote_User_Free_HLR

1998

1999

process Remote_User_Free_VLR
Process in the VLR to handle a Remote User Free notification from the HLR

RUF_VLR1(2)
Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR

Idle

MAP_REMOTE_ USER_FREE_ ind

CCBS RUF

Wait_For_ Application_ Response

CCBS RUF ack (Recall accepted)

CCBS RUF ack (Recall unsuccessful)

CCBS RUF negative response

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

Set User Error

MAP_REMOTE_USER_FREE_rsp MAP_DELIMITER_req

MAP_REMOTE_USER_FREE_rsp MAP_CLOSE_req

Wait_For_ Call_Report

2259
2260

Figure 21.6/15 (sheet 1 of 2): Process Remote_User_Free_VLR

2000

2001

process Remote_User_Free_VLR
Process in the VLR to handle a Remote User Free notification from the HLR Wait_For_ Call_Report

RUF_VLR2(2)
Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR

CCBS Call Report

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_STATUS_REPORT_req MAP_DELIMITER_req

MAP_ CLOSE_ req

Wait_For_ HLR_Response

MAP_STATUS_ REPORT_ cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK CCBS Call Report negative response

CCBS Call Report ack

2261
2262

Figure 21.6/15 (sheet 2 of 2): Process Remote_User_Free_VLR

2002

2003

2263 2264 2265 2266

21.7 Void 21.8 Void 21.9 Immediate Service Termination (IST)

21.9.1 IST Alert

2267 The Immediate Service Termination Alert procedure is used to keep track of the call activities performed by subscribers 2268 who are marked as being subject to IST monitoring and, possibly, to terminate the call activities for which the alert was 2269 sent, or all the call activities related to the subscriber for whom the alert was sent. 2270 The message flow for alerting is shown in figure 21.9/1; the MSC may be a Visited MSC or a Gateway MSC.

MSC 1 2

HLR

2271
2272 2273 2274 2275

1) 2)

MAP_IST_ALERT_req/ind MAP_IST_ALERT_rsp/cnf

2276

Figure 21.9/1: Message flow for IST Alert

2277 21.9.1.1

Procedure in the MSC

2278 The MAP process in the MSC (Visited MSC or Gateway MSC) is shown in figure 21.9/3. The MAP process invokes 2279 macros not defined in this clause; the definitions of these macros can be found as follows: 2280 2281

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2282 21.9.1.2

Procedure in the HLR

2283 The MAP process in the HLR is shown in figure 21.9/4. The MAP process invokes a macro not defined in this clause; 2284 the definition of this macro can be found as follows: 2285

Receive_Open_Ind

see subclause 25.1.1;

2286

21.9.2 IST Command

2287 The Immediate Service Termination Command procedure is used to terminate the call activities related to a subscriber. 2288 The message flow for the IST Command procedure is shown in figure 21.9/2; the MSC may be a Visited MSC or a 2289 Gateway MSC.

2004

2005

MSC 1 2

HLR

2290
2291 2292 2293 2294

1) 2)

MAP_IST_COMMAND_req/ind MAP_IST_COMMAND_rsp/cnf

2295

Figure 21.9/2: Message flow for IST Command

2296 21.9.2.1

Procedure in the HLR

2297 The MAP process in the HLR is shown in figure 21.9/5. The MAP process invokes macros not defined in this clause; 2298 the definitions of these macros can be found as follows: 2299 2300

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2301 21.9.2.2

Procedure in the MSC

2302 The MAP process in the MSC is shown in figure 21.9.6. The MAP process invokes a macro not defined in this clause; 2303 the definition of this macro can be found as follows: 2304

Receive_Open_Ind

see subclause 25.1.1.

2006

2007

process IST_Alert_MSC
Process in the MSC to send an IST alert to the HLR

ISTA_MSC1(1)
Signals to/from the left are to/from the call handling application process in the MSC; signals to/fr om the right are to/from the HLR

Idle

IST Alert

MAP_OPEN_req MAP_IST_ALERT_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Err or IST Alert negative response

MAP_IST_ ALERT_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Idle

Check_ Confirmation

User Error, Provider Err or , Data Error

MAP_ CLOSE_ req

OK IST Alert ack IST Alert negative response

Idle

Idle

2305
2306

Figure 21.9/3: Process IST_Alert_MSC

2008

2009

process IST_Alert_HLR
Process in the HLR to handle an IST Aler t fr om the MSC

ISTA_HLR(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the IST application process in the HLR

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_P_ ABORT_ ind

MAP_IST_ ALERT_ind

MAP_ NOTICE_ ind

Idle

IST Alert

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Idle

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

IST Alert ack

IST Alert negative response

Set User Error

MAP_IST_ALERT_rsp MAP_CLOSE_r eq

Idle

Idle

2307
2308

Figure 21.9/4: Process IST_Alert_HLR

2010

2011

process IST_Com mand_HLR

Process in the HLR to send an IST command to the MSC

ISTC_HLR1(1)
Signals to/from the left are to/from the MSC; signals to/fr om the right are to/from the IST application process in the HLR

Idle

IST Command

MAP_OPEN_req MAP_IST_COMMAND_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ MSC_Response

Vr, Err or IST Command negative response

MAP_IST_ COMMAND_ cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Idle

Check_ Confirmation

User Error, Provider Err or , Data Error

MAP_ CLOSE_ req

OK IST Command ack IST Command negative response

Idle

Idle

2309
2310

Figure 21.9/5: Process IST_Command_HLR

2012

2013

process IST_Command_MSC
Process in the M to handle SC an IST Com mand from the HLR

ISTC_MSC1(1)
Signals to/from the left are to/from the call handling application process in the MSC; signals to/from the right are to/from the HLR

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_P_ ABORT_ ind

MAP_IST_ COMM AND_ ind

MAP_ NOTICE_ ind

Idle

IST Command

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Idle

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

IST Command ack

IST Command negative response

Set User Error

MAP_IST_COMM AND_rsp MAP_CLOSE_req

Idle

Idle

2311
2312

Figure 21.9/6: Process IST_Command_MSC

2014

2015

2313 2314

21.10 Resource Management

21.10.1 General

2315 The message flow for successful release of resources is shown in figure 21.10/1.

GMSC

HLR

VMSC/ VLR

1 4

3 5

6 7

2316
2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333

1) 2) 3) 4) 5) 6) 7)

I_IAM (Note 1) MAP_SEND_ROUTING_INFORMATION_req/ind MAP_PROVIDE_ROAMING_NUMBER_req/ind I_REL (Note 1) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf MAP_SEND_ROUTING_INFORMATION_rsp/cnf MAP_RELEASE_RESOURCES (Note 2)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations & ETSI specification: - Q.721-725 - Telephone User Part (TUP); - ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. NOTE 2: Services printed in italics are optional.

2334

Figure 21.10/1: Message flow for early release of resources

2335

21.3.2 Process in the GMSC

2336 The MAP process in the GMSC to release resources is shown in figure 21.10/2. The MAP process invokes macros not 2337 defined in this clause; the definitions of these macros can be found as follows: 2338 2339

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

2340

21.3.3 Process in the VMSC

2341 The MAP process in the VMSC to handle a request for the GMSC to release resources is shown in figure 21.10/3. The 2342 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2343

Receive_Open_Ind

see subclause 25.1.1;

2016

2017

process Release_Resources_GMSC
Process in the GMSC to request the VMSC to release resosources Signals to/from the left are to/from the application process in the GMSC (see 3GPP TS 23.018); signals to/from the right are to/from the VMSC; Idle

1(1)

Release Resources

MAP_OPEN_req MAPRELEASE_RESOURCES_req MAP_DELIMITER_req

Receive_ Open_cnf

OK Wait_For_ VMSC_ Response

Vr, Error

Idle

MAP_ NOTICE_ ind

MAP_RELEASE_ RESOURCES_cnf

MAP_P_ABORT_ind, MAP_CLOSE_req

MAP_ CLOSE_ req

Idle

2344
2345

Figure 21.10/2: Process Release Resources_GMSC

2018

2019

process Release_Resources_VMSC
Process in the VMSC to handle a request to release resources Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the application process in the VMSC (see 3GPP TS 23.018) Idle

1(1)

Receive_ Open_ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_P_ ABORT_ ind

MAP_RELEASE_RESOURCES_ind

MAP_ NOTICE_ ind

Idle

Release Resources

MAP_ CLOSE_ req

Wait-For_ Call_Handling_ Response

Idle

Release Resources Ack

Release Resources negative response

Set Error

MAP_RELEASE_RESOURCES_rsp MAP_CLOSE_req

Idle

2346
2347

Figure 21.10/3: Process Release Resources_VMSC

2020

2021

2348 2349 2350

22

Supplementary services procedures

22.1 Supplementary service co-ordinator processes
22.1.1 Supplementary service co-ordinator process for the MSC

2351 The co-ordinator process in the MSC to handle a CM connection request with CM service type Supplementary service 2352 activation is shown in figure 22.1/1. The process invokes a macro not defined in this clause; the definition of this macro 2353 can be found as follows: 2354

Process_Access_Request_MSC

see subclause 25.4.1.

2355 2356 2357

22.1.2 Void 22.1.3 Functional supplementary service co-ordinator process for the HLR

2358 The MAP co-ordinator process in the HLR to handle a dialogue opened with the networkFunctionalSS application 2359 context is shown in figure 22.1/3. The MAP process invokes a macro not defined in this clause; the definition of this 2360 macro can be found as follows: 2361

Receive_Open_Ind

see subclause 25.1.1.

2362 2363

22.1.4 Call completion supplementary service co-ordinator process for the HLR

2364 The MAP co-ordinator process in the HLR to handle a dialogue opened with the callCompletion application context is 2365 shown in figure 22.1/4. The MAP process invokes a macro not defined in this clause; the definition of this macro can be 2366 found as follows: 2367

Receive_Open_Ind

see subclause 25.1.1.

2022

2023

process SS_Coordinator_MSC
Supplem entary service co-ordinating process in the MSC

SSC_MSC1(2)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the child process unless shown otherwise

Null

A_CM_ SERV_REQ

CM Service type= Supplementary service activation

Process_ Access_ Request_MSC

OK Wait_For_ Service_ Indication

Error

Null

A_ REGISTER_ SS_ind

A_ ERASE_ SS_ind

A_ ACTIVATE_ SS_ind

A_ DEACTIVATE_ SS_ind

A_ INTERROGATE_ SS_ind

A_ REGISTER_ PASSWORD_ ind

From interworking function; see 3GPP TS 29.011

Register_ SS_MSC

Erase_ SS_MSC

Activate_ SS_MSC

Deactivate_ SS_MSC

Interrogate_ SS_MSC

Register_ Password_MSC

A_ REGISTER_ SS_ind

A_ ERASE_ SS_ind

A_ ACTIVATE_ SS_ind

A_ DEACTIVATE_ SS_ind

A_ INTERROGATE_ SS_ind

A_ REGISTER_ PASSWORD_ ind

Relay_Info

2368
2369

Figure 22.1/1 (sheet 1 of 2): Process SS_Coordinator_MSC

2024

2025

process SS_Coordinator_MSC
Supplementary service co-ordinating pr ocess in the MSC Wait_For_ Service_ Indication

SSC_MSC2(2)
Signals to/from the left are to/from the MS; signals to/fr om the right are to/from the child process

A_CM_ SERV_ RELEASE_ ind

A_PROCESS_ UNSTRUCTURED_ SS_REQUEST_ ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ ABORT_ req

Application procedure cancellation

MS_Init_ USSD_MSC

A_CM_ RELEASE_ COMPLETE_ req

A_PROCESS_ UNSTRUCTURED_ SS_REQUEST_ ind

A_CM_ RELEASE_ req

Null

Relay_Info

Null

A_REL

A_REL

A_REL

A_REL

Null

Relay_Info

Null

Relay_Info

2370
2371 2372

Figure 22.1/1 (sheet 2 of 2): Process SS_Coordinator_MSC Figure 22.1/2 void

2026

2027

process SS_Coordinator_HLR
Supplem entary service co-ordinating process in the HLR

SSC_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the child process Null

Receive_ Open_Ind Error OK Null Wait_For_ Service_ Indication Perform MAP Vr dialogue Vr

MAP_ REGISTER_ SS_ind

MAP_ ERASE_ SS_ind

MAP_ ACTIVATE_ SS_ind

MAP_ DEACTIVATE_ SS_ind

MAP_ INTERROGATE_ SS_ind

MAP_ REGISTER_ PASSWORD_ ind

Null

Register_ SS_HLR

Erase_ SS_HLR

Activate_ SS_HLR

Deactivate_ SS_HLR

Interrogate_ SS_HLR

Register_ Password_HLR

MAP_ REGISTER_ SS_ind

MAP_ ERASE_ SS_ind

MAP_ ACTIVATE_ SS_ind

MAP_ DEACTIVATE_ SS_ind

MAP_ INTERROGATE_ SS_ind

MAP_ REGISTER_ PASSWORD_ ind

Relay_Info

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ABORT_req, MAP_CLOSE_req

Null

Relay_Info

Null

Relay_Info

Wait_For_ Service_ Indication

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ CLOSE_ req

Null

2373
2374

Figure 22.1/3: Process SS_Coordinator_HLR

2028

2029

process CC_Coordinator_HLR
Call Completion co-ordinating process in the HLR

CCC_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the child process

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Null

MAP_ REGISTER_ CC_ENTRY_ ind

MAP_ ERASE_ CC_ENTRY_ ind

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Register_CC_ Entry_HLR

Erase_CC_ Entry_HLR

MAP_ CLOSE_ req

MAP_ REGISTER_ CC_ENTRY_ ind

MAP_ ERASE_ CC_ENTRY_ ind

Null

Relay_Info

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ABORT_req, MAP_CLOSE_req

Null

Relay_Info

Null

Relay_Info

2375
2376

Figure 22.1/4: Process CC_Coordinator_HLR

2030

2031

2377 2378

22.2 Registration procedure

22.2.1 General

2379 The registration procedure is used to register data related to a supplementary service in the HLR. The registration 2380 procedure is a fully transparent communication between the MS and the HLR, except that some services may be 2381 invoked as a result of the procedure, as described in the clauses below. 2382 The registration procedure is shown in figure 22.2.1/1. 2383 The following services may be used: 2384 2385 2386 2387 2388 2389 2390 2391 2392

MAP_PROCESS_ACCESS_REQUEST

(see clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (see clauses 9 and 25); MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_READY_FOR_SM MAP_INSERT_SUBSCRIBER_DATA (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25); (see clauses 8 and 25);

2393 The following service is certainly used: 2394

MAP_REGISTER_SS
MS MSC

(defined in clause 11).

VLR HLR

1 3

2 4

5 6 9 10

2395
2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2032

1) 2) 3) 4) 5) 6) 7) 8) 9) 10)

A_CM_SERV_REQ (Note 1) MAP_PROCESS_ACCESS_REQUEST (Note 2) A_REGISTER_SS (Note 1) MAP_REGISTER_SS_req/ind MAP_REGISTER_SS_req/ind MAP_REGISTER_SS_rsp/cnf MAP_REGISTER_SS_rsp/cnf A_REGISTER_SS ack (Note 1) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3)

2033

2414

2408 2409 2410 2411 2412 2413

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For details of the Process Access Request procedure, refer to subclause 25.4 in the present document. NOTE 3: Services printed in italics are optional.

Figure 22.2.1/1: Message flow for supplementary service registration

2415

22.2.2 Procedure in the MSC

2416 The A_REGISTER_SS service indication received by the MAP process in the MSC contains the SS-Code and any 2417 parameters that are related to the supplementary service. 2418 The MAP user transfers the received information to the VLR in the MAP_REGISTER_SS request without checking the 2419 contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59]. 2420 The information in the MAP_REGISTER_SS confirm from the VLR is relayed to the MS in the A_REGISTER_SS 2421 response message as described in 3GPP TS 24.08x, 3GPP TS 24.08x and 3GPP TS 29.011. 2422 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2423 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 2424 The registration process in the MSC is shown in figure 22.2.2/1.

2425

22.2.3 Procedure in the VLR

Receive_Open_Ind Receive_Open_Cnf Check_Confirmation Process_Access_Request_VLR see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.2; see subclause 25.4.2.

2426 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2427 2428 2429 2430

2431 The MAP process in the VLR transfers the information received in the MAP_REGISTER_SS indication to the HLR in 2432 the MAP_REGISTER_SS request without checking the contents. The MAP_OPEN request includes the IMSI of the 2433 subscriber as the destination reference and the VLR number as the originating reference. 2434 If the MAP_REGISTER_SS confirm is properly formed and contains a result or a user error, the MAP process in the 2435 VLR shall transfer the information contained in this primitive to the MSC in the MAP_REGISTER_SS response. 2436 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2437 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 2438 The registration process in the VLR is shown in figure 22.2.3/1.

2439

22.2.4 Procedure in the HLR

2440 The MAP process invokes a macro and a process not defined in this clause; the definitions of the macro and process can 2441 be found as follows: 2442 2443

Check_Indication Insert_Subs_Data_Stand_Alone_HLR

see subclause 25.2.1; see subclause 25.7.3.

2444 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x2445 series of technical specifications. This handling may lead to a successful result, a partially successful result or an error 2446 being returned. 2447 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2448 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]):

2034

2035

2449 The registration process in the HLR is shown in figure 22.2.4/1.

2036

2037

process Register_SS_MSC
Process in the MSC to handle a r equest to r egister data for a supplementary service

RSS_MSC1(1)
Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/fr om the right are to/from the VLR

Null

A_CM_ SERV_ RELEASE_ ind

A_ REGISTER_ SS_ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ ABORT_ req

Application procedure cancellation

MAP_REGISTER_SS_req MAP_DELIMITER_req

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ RELEASE_ req

Wait_For_ Register _ SS_Confirm

A_CM_ SERV_ RELEASE_ ind

MAP_REGISTER_SS_cnf

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ ABORT_ req

Application procedure cancellation

A_CM_ RELEASE_ COMPLETE_ req

A_REGISTER _SS_rsp A_CM_RELEASE_req

A_CM_ RELEASE_ req

2450
2451

Figure 22.2.2/1: Process Register_SS_MSC

2038

2039

process Register_SS_VLR
Process in the VLR to handle a r equest to r egister data for a supplementary service

RSS_VLR1(2)
Signals to/from the left are to/from the MSC; signals to/fr om the right are to/from the HLR

Null

Receive_ Open_Ind

OK Wait_For_ PAR

Vr, Err or

Null

MAP_U_ABORT_ind, MAP_CLOSE_ind

Process_ Access_ Request_VLR

OK Wait_For_ Register _ SS_Request

Error

Null

Null

MAP_ REGISTER_ SS_ind

MAP_OPEN_req MAP_REGISTER_SS_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error MAP_U_ ABORT_ req

OK

Vr Per for m MAP Vr dialogue

Null

Wait_For_ Register _ SS_Confirm

Null

2452
2453

Figure 22.2.3/1 (sheet 1 of 2): Process Register_SS_VLR

2040

2041

process Register_SS_VLR
Process in the VLR to handle a request to register data for a supplem entary service Wait_For_ Register_ SS_Confirm

RSS_VLR2(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ REGISTER_ SS_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

Check_ Confirmation

MAP_ CLOSE_ req

OK, User Error, Data Error

Provider Error MAP_U_ ABORT_ req MAP_U_ ABORT_ req

Null

MAP_REGISTER_SS_rsp MAP_CLOSE_req

Null

Null

Null

2454
2455

Figure 22.2.3/1 (sheet 2 of 2): Process Register_SS_VLR

2042

2043

process Register_SS_HLR
Process in the HLR to handle a r equest to r egister data for a supplementary service

RSS_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the process SS_REQUEST_WITH_ BS_GROUP (see 3GPP TS 23.011)

Null

MAP_ REGISTER_ SS_ind

Check_ Indication

Error Yes

OK Operator Determined Barring of SS management? No Set User Error: Call barred Call barr ing cause= Oper ator barr ing

SS request

MAP_REGISTER_SS_rsp MAP_CLOSE_r eq

Wait_For_ Application_ Response

acknowledge

par tial acceptance

error

MAP_ NOTICE_ ind

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

Set Result

Set User Error

MAP_U_ ABORT_ req

MAP_REGISTER_SS_rsp MAP_CLOSE_r eq

No Update of subs data required in VLR? Yes

Insert_Subs_Data_ Stand_Alone_ HLR

2456
2457

Figure 22.2.4/1: Process Register_SS_HLR

2044

2045

2458 2459

22.3 Erasure procedure

22.3.1 General

2460 The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a 2461 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of 2462 the procedure, as described in the clauses below. 2463 The erasure procedure is shown in figure 22.3.1/1. 2464 The following services may be used: 2465 2466 2467 2468 2469 2470 2471 2472 2473

MAP_PROCESS_ACCESS_REQUEST

(see clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (see clauses 9 and 25); MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_READY_FOR_SM MAP_INSERT_SUBSCRIBER_DATA (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25); (see clauses 8 and 25);

2474 The following service is certainly used: 2475

MAP_ERASE_SS
MS MSC

(defined in clause 11).

VLR HLR

1 3

2 4

5 6 9 10

2476
2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2046

1) 2) 3) 4) 5) 6) 7) 8) 9) 10)

A_CM_SERV_REQ (Note 1) MAP_PROCESS_ACCESS_REQUEST (Note 2) A_ERASE_SS (Note 1) MAP_ERASE_SS_req/ind MAP_ERASE_SS_req/ind MAP_ERASE_SS_rsp/cnf MAP_ERASE_SS_rsp/cnf A_ERASE_SS ack (Note 1) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3)

2047

2495

2489 2490 2491 2492 2493 2494

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For details of the Process Access Request procedure, refer to subclause 25.4 in the present document. NOTE 3: Services printed in italics are optional.

Figure 22.3.1/1: Message flow for supplementary service erasure

2496

22.3.2 Procedure in the MSC

2497 The MSC procedure for erasure is identical to that specified for registration in subclause 22.2.2. The text and diagrams 2498 in subclause 22.2.2 apply with all references to registration changed to erasure.

2499

22.3.3 Procedure in the VLR

2500 The VLR procedure for erasure is identical to that specified for registration in subclause 22.2.3. The text and diagrams 2501 in subclause 22.2.3 apply with all references to registration changed to erasure.

2502

22.3.4 Procedure in the HLR

2503 The HLR procedure for erasure is identical to that specified for registration in subclause 22.2.4. The text and diagrams 2504 in subclause 22.2.4 apply with all references to registration changed to erasure.

2505 2506

22.4 Activation procedure

22.4.1 General

2507 The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully 2508 transparent communication between the MS and the HLR, except that some services may be invoked as a result of the 2509 procedure, as described in the clauses below. 2510 The activation procedure is shown in figure 22.4.1/1. 2511 The following services may be used: 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521

MAP_PROCESS_ACCESS_REQUEST

(see clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (see clauses 9 and 25); MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_READY_FOR_SM MAP_GET_PASSWORD MAP_INSERT_SUBSCRIBER_DATA (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25); (defined in clause 11); (see clauses 8 and 25);

2522 The following service is certainly used: 2523

MAP_ACTIVATE_SS

(defined in clause 11).

2048

2049

MS

MSC

VLR

HLR

1 3

2 4

5 6

8 9

10

11 12 15 16

14

13

2524
2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16)

A_CM_SERV_REQ (Note 1) MAP_PROCESS_ACCESS_REQUEST (Note 2) A_ACTIVATE_SS (Note 1) MAP_ACTIVATE_SS_req/ind MAP_ACTIVATE_SS_req/ind MAP_GET_PASSWORD_req/ind (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) A_GET_PASSWORD (Note 1, Note 3) A_GET_PASSWORD ack (Note 1, Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_ACTIVATE_SS_rsp/cnf MAP_ACTIVATE_SS_rsp/cnf A_ACTIVATE_SS ack (Note 1) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For details of the Process Access Request procedure, refer to subclause 25.4 of this document. NOTE 3: Services printed in italics are optional.

2549

Figure 22.4.1/1: Message flow for supplementary service activation

2550

22.4.2 Procedure in the MSC

2551 The A_ACTIVATE_SS service indication received by the MAP user in the MSC contains the SS-Code and any 2552 parameters related to the supplementary service. 2553 The MSC transfers the received information to the VLR in the MAP_ACTIVATE_SS request without checking the 2554 contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59]. 2555 The information in the MAP_ACTIVATE_SS confirm from the VLR is relayed to the MS in the A_ACTIVATE_SS 2556 response message, as described in TS 24.08x, 3GPP TS 24.08x and 3GPP TS 29.011. 2557 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2558 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]).
2050

2051

2559 The activation process in the MSC is shown in figure 22.4.2/1.

2560

22.4.3 Procedure in the VLR

Receive_Open_Ind Receive_Open_Cnf Check_Confirmation Process_Access_Request_VLR see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.2; see subclause 25.4.2.

2561 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2562 2563 2564 2565

2566 The MAP process in the VLR transfers the information received in the MAP_ACTIVATE_SS indication to the HLR in 2567 the MAP_ACTIVATE_SS request without checking the contents. The MAP_OPEN request includes the IMSI of the 2568 subscriber as the destination reference and the VLR number as the originating reference. 2569 If the MAP_REGISTER_SS confirm is properly formed and contains a result or a user error, the MAP process in the 2570 VLR shall transfer the information contained in this primitive to the MSC in the MAP_ACTIVATE_SS response. 2571 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2572 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 2573 The activation process in the VLR is shown in figure 22.4.3/1.

2574

22.4.4 Procedure in the HLR

2575 The MAP process invokes a macro and a process not defined in this clause; the definitions of the macro and process can 2576 be found as follows: 2577 2578

Check_Indication Insert_Subs_Data_Stand_Alone_HLR

see subclause 25.2.1; see subclause 25.7.3.

2579 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x2580 series of technical specifications. This handling may lead to a successful result, a partially successful result or an error 2581 being returned. 2582 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2583 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]): 2584 The activation process in the HLR is shown in figure 22.4.4/1.

2052

2053

process Activate_SS_MSC
Process in the M to handle SC a request to activate a supplem entary service

ASS_MSC1(1)
Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the VLR

Null

A_CM_ SERV_ RELEASE_ ind

A_ ACTIVATE_ SS_ind

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

Application procedure cancellation

MAP_ACTIVATE_SS_req MAP_DELIMITER_req

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ RELEASE_ req

Wait_For_ Activate_ SS_Confirm

A_CM_ SERV_ RELEASE_ ind

MAP_ACTIVATE_SS_cnf

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

Application procedure cancellation

A_ACTIVATE_SS_rsp A_CM _RELEASE_req

A_CM_ RELEASE_ COMPLETE_ req Null

Get_Password_ MSC

A_CM_ RELEASE_ req

OK

Wait_For_ SS_Confirm

2585
2586

Figure 22.4.2/1: Process Activate_SS_MSC

2054

2055

process Activate_SS_VLR
Process in the VLR to handle a r equest to activate a supplementary service

ASS_VLR1(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR

Null

Receive_ Open_Ind

OK Wait_For_ PAR

Vr, Err or

Null

MAP_U_ABORT_ind, MAP_CLOSE_ind

Process_ Access_ Request_VLR

OK Wait_For_ Activate_ SS_Request

Error

Null

Null

MAP_ ACTIVATE_ SS_ind

MAP_OPEN_req MAP_ACTIVATE_SS_r eq MAP_DELIMITER_req

Receive_ Open_Cnf

Error MAP_U_ ABORT_ req

OK

Vr Per for m MAP Vr dialogue

Null

Wait_For_ Activate_ SS_Confirm

Null

2587
2588

Figure 22.4.3/1 (sheet 1 of 2): Process Activate_SS_VLR

2056

2057

process Activate_SS_VLR
Process in the VLR to handle a request to activate a supplem entary service Wait_For_ Activate_ SS_Confirm

ASS_VLR2(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ ACTIVATE_ SS_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

Check_ Confirmation

MAP_ CLOSE_ req

OK, User Error, Data Error

Provider Error MAP_U_ ABORT_ req MAP_U_ ABORT_ req

Null

MAP_ACTIVATE_SS_rsp MAP_CLOSE_req

Null

Null

Null

Wait_For_ Activate_ SS_Confirm

Get_Password_ VLR

OK Wait_For_ Activate_ SS_Confirm

Null

Null

2589
2590

Figure 22.4.3/1 (sheet 2 of 2): Process Activate_SS_VLR

2058

2059

process Activate_SS_HLR
Process in the HLR to handle a request to activate a supplem entary service

ASS_HLR1(2)
Signals to/from the left are to/fromthe VLR; signals to/from the right are to/fromthe process SS_REQUEST_WITH_ BS_GROUP (see 3GPP TS 23.011)

Null

MAP_ ACTIVATE_ SS_ind

Check_ Indication

Error Yes

OK

Operator Determined Barring of SS management? No

Set User Error: Call barred

Call barring cause= Operator barring

SS request

MAP_ACTIVATE_SS_rsp MAP_CLOSE_req

Wait_For_ Application_ Response

acknowledge

partial acceptance

error

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

Set Result

Set User Error

MAP_U_ ABORT_ req

MAP_ACTIVATE_SS_rsp MAP_CLOSE_req

No Update of subs data required in VLR? Yes Insert_Subs_Data_ Stand_Alone_ HLR

2591
2592

Figure 22.4.4/1 (sheet 1 of 2): Process Activate_SS_HLR

2060

2061

process Activate_SS_HLR
Process in the HLR to handle a r equest to activate a supplementary service Wait_For_ Application_ Response

ASS_HLR2(2)

SS Get Password

MAP_GET_PASSWORD_r eq MAP_DELIMITER_req

Wait_For_ Password

MAP_ NOTICE_ ind

MAP_GET_ PASSWOR D_ cnf

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ CLOSE_ req

Check_ Confirmation

OK, U ser Error SS Get Password_ Ack

Provider Error, Data Er ror

Wait_For_ Application_ Response

2593
2594

Figure 22.4.4/1 (sheet 2 of 2): Process Activate_SS_HLR

2062

2063

2595 2596

22.5 Deactivation procedure

22.5.1 General

2597 The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a 2598 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of 2599 the procedure, as described in the clauses below. 2600 The deactivation procedure is shown in figure 22.5.1/1. 2601 The following services may be used: 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611

MAP_PROCESS_ACCESS_REQUEST

(see clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (see clauses 9 and 25); MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_READY_FOR_SM MAP_GET_PASSWORD MAP_INSERT_SUBSCRIBER_DATA (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25); (defined in clause 11); (see clauses 8 and 25);

2612 The following service is certainly used: 2613

MAP_DEACTIVATE_SS
MS MSC

(defined in clause 11).

VLR HLR

1 3

2 4

5 6

8 9

10

11 12 15 16

14

13

2614
2615 2616

1)

A_CM_SERV_REQ (Note 1)

2064

2065

2639

2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638

2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16)

MAP_PROCESS_ACCESS_REQUEST (Note 2) A_DEACTIVATE_SS (Note 1) MAP_DEACTIVATE_SS_req/ind MAP_DEACTIVATE_SS_req/ind MAP_GET_PASSWORD_req/ind (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) A_GET_PASSWORD (Note 1, Note 3) A_GET_PASSWORD ack (Note 1, Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_DEACTIVATE_SS_rsp/cnf MAP_DEACTIVATE_SS_rsp/cnf A_DEACTIVATE_SS ack (Note 1) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For details of the Process Access Request procedure, refer to subclause 25.4 in the present document. NOTE 3: Services printed in italics are optional.

Figure 22.5.1/1: Message flow for supplementary service deactivation

2640

22.5.2 Procedure in the MSC

2641 The MSC procedure for deactivation is identical to that specified for activation in subclause 22.4.2. The text and 2642 diagrams in subclause 22.4.2 apply with all references to activation changed to deactivation.

2643

22.5.3 Procedures in the VLR

2644 The VLR procedure for deactivation is identical to that specified for activation in subclause 22.4.3. The text and 2645 diagrams in subclause 22.4.3 apply with all references to activation changed to deactivation.

2646

22.5.4 Procedures in the HLR

2647 The HLR procedure for deactivation is identical to that specified for activation in subclause 22.4.4. The text and 2648 diagrams in subclause 22.4.4 apply with all references to activation changed to deactivation.

2649 2650

22.6 Interrogation procedure

22.6.1 General

2651 The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the 2652 HLR. It is the VLR which decides whether an interrogation request should be forwarded to the HLR or not. Some non2653 supplementary service related services may be invoked as a result of the procedure, as described in the clauses below. 2654 The interrogation procedure is shown in figure 22.6.1/1. 2655 The following services may be used: 2656 2657 2658 2659 2660 2661

MAP_PROCESS_ACCESS_REQUEST

(see clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (see clauses 9 and 25); MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25);

2066

2067

2662 2663

MAP_CHECK_IMEI MAP_READY_FOR_SM

(see clauses 8 and 25); (see clauses 12 and 25);

2664 The following service is certainly used: 2665

MAP_INTERROGATE_SS
MS MSC

(defined in clause 11).

VLR HLR

1 3

2 4

5 6

2666
2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682

1) 2) 3) 4) 5) 6) 7) 8)

A_CM_SERV_REQ (Note 1) MAP_PROCESS_ACCESS_REQUEST (Note 2) A_INTERROGATE_SS (Note 1) MAP_INTERROGATE_SS_req/ind MAP_INTERROGATE_SS_req/ind MAP_INTERROGATE_SS_rsp/cnf MAP_INTERROGATE_SS_rsp/cnf A_INTERROGATE_SS ack (Note 1)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path. NOTE 2: For details of the Process Access Request procedure, refer to subclause 25.4 in the present document. NOTE 3: Services printed in italics are optional.

2683

Figure 22.6.1/1: Message flow for supplementary service interrogation

2684

22.6.2 Procedure in the MSC

2685 The MSC procedures for interrogation are identical to those specified for registration in subclause 22.2.2. The text and 2686 diagrams in subclause 22.2.2 apply with all references to registration changed to interrogation.

2687

22.6.3 Procedures in the VLR

Receive_Open_Ind Receive_Open_Cnf Check_Confirmation Process_Access_Request_VLR see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.2; see subclause 25.4.2.

2688 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2689 2690 2691 2692

2693 The interrogation is answered either by the VLR or by the HLR, depending on the service interrogated. 2694

1) Interrogation to be handled by the VLR

2068

2069

2695 The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x2696 series of technical specifications. This handling may lead to a successful result, a partially successful result or an error 2697 being returned. 2698 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2699 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 2700 2701 2702 2703 2704

2) Interrogation to be handled by the HLR If the interrogation is to be handled by the HLR, the MAP process in the VLR transfers the information received in the MAP_INTERROGATE_SS indication to the HLR in the MAP_INTERROGATE_SS request without checking the contents of the service indication. The MAP_OPEN request includes the IMSI of the subscriber as the destination reference and the VLR number as the originating reference.

2705 If the MAP_INTERROGATE_SS confirm is properly formed and contains a result or a user error, the MAP process in 2706 the VLR shall transfer the information contained in this primitive to the MSC in the MAP_INTERROGATE_SS 2707 response. 2708 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2709 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 2710 The Interrogation process in the VLR is shown in figure 22.6.3/1.

2711

22.6.4 Procedure in the HLR

Check_Indication see subclause 25.2.1.

2712 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2713

2714 The HLR acts as follows: 2715 The interrogation is answered either by the VLR or by the HLR, depending on the service interrogated. 2716 2717 2718 2719 2720 2721 2722

1) Interrogation to be handled by the VLR If the interrogation procedure should have been answered by the VLR, then the HLR assumes that the VLR does not support the interrogated supplementary service, and returns the SS Not Available error to the VLR. 2) Interrogation to be handled by HLR The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x-series of technical specifications. This handling may lead to either a successful result or an error being returned.

2723 For call independent SS operations, each message shall contain only a single component. Messages which contain more 2724 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 2725 The Interrogation process in the HLR is shown in figure 22.6.4/1.

2070

2071

process Interrogate_SS_VLR
Processs in the VLR to handle a request to i nterrogate data for a supplem entary service

ISS_VLR1(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the process SS_REQUEST_WITH_ BS_GROUP (see 3GPP TS 23.011) Null

Receive_ Open_Ind

OK Wait_For_ PAR

Vr, Error

Null

MAP_U_ABORT_ind, MAP_CLOSE_ind

Process_ Access_ Request_VLR

OK Wait_For_ Interrogate_ SS_Request

Error

Null

Null

MAP_ INTERROGATE_ SS_ind

Yes Operator Determined Barring of SS management? No No Set User Error: Call barred Call barring cause= Operator barring SS known? Yes No MAP_INTERROGATE_SS_rsp MAP_CLOSE_req Yes Handle interrogation in VLR?

Null

SS request

Wait_For_ Application_ Response

2726
2727

Figure 22.6.3/1 (sheet 1 of 2): Process Interrogate_SS_VLR

2072

2073

process Interrogate_SS_VLR
Processs in the VLR to handle a request to i nterrogate data for a supplem entary service 1

ISS_VLR2(2)
In the upper subtree, signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR MAP_OPEN_req MAP_REGISTER_SS_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error MAP_U_ ABORT_ req

Vr Perform MAP Vr dialogue

OK Wait_For_ Interrogate_ SS_Confirm

Null

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ INTERROGATE_ SS_cnf

MAP_P_ABORT_i nd, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

MAP_U_ ABORT_ req

Check_ Confirmation

MAP_ CLOSE_ req

OK, User Error, Data Error

Provider Error MAP_U_ ABORT_ req MAP_U_ ABORT_ req

Null

MAP_INTERROGATE_SS_rsp MAP_CLOSE_req

Null

Null

Null

Wait_For_ Application_ Response

acknow ledge

partial acceptance

error

In the lower subtree, signals to/from the left are to/from the MSC; signals to/from the right are to/from the process SS_REQUEST_WITH_ BS_GROUP (see 3GPP TS 23.011)

Set Result

Set User Error

MAP_INTERROGATE_SS_rsp MAP_CLOSE_req

Null

2728
2729

Figure 22.6.3/1 (sheet 2 of 2): Process Interrogate_SS_VLR

2074

2075

process Interrogate_SS_HLR
Process in the HLR to handle a r equest to interrogate data for a supplementary service

ISS_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/fr om the right are to/from the process SS_REQUEST_WITH_ BS_GROUP (see 3GPP TS 23.011)

Null

MAP_ INT ERROGATE_ SS_ind

Check_ Indication

Error Yes

OK Operator Determined Barring of SS management? No Set User Error: Call bar red Call barr ing cause= Oper ator barr ing No SS supported in HLR? Set User Error: Unexpected data value Yes Interrogation should be handled in VLR? Set User Error: SS not available SS request No Yes

Wait_For_ Application_ Response

acknowledge

error

MAP_ NOTICE_ ind

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

Set Result

Set User Error

MAP_U_ ABORT_ req

MAP_INTERROGATE_SS_rsp MAP_CLO SE_r eq

MAP_INTERROGATE_SS_r sp MAP_CLOSE_r eq

2730
2731

Figure 22.6.4/1: Process Interrogate_SS_HLR

2076

2077

2732
2733 2734

22.7 Void
Figure 22.7.2/1 void Figure 22.7.3/1 void

2078

2079

2735 2736

22.8 Password registration procedure

22.8.1 General

2737 The password registration procedure is used to register a password in the HLR. The password registration procedure is a 2738 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of 2739 the procedure, as described below. 2740 The password registration procedure is shown in figure 22.8.1/1. 2741 The following services may be used: 2742 2743 2744 2745 2746 2747 2748 2749

MAP_PROCESS_ACCESS_REQUEST MAP_TRACE_SUBSCRIBER_ACTIVITY MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_READY_FOR_SM

(see clauses 8 and 25); (see clauses 9 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25);

2750 The following services are certainly used: 2751 2752

MAP_REGISTER_PASSWORD MAP_GET_PASSWORD

(defined in clause 11); (defined in clause 11).

2080

2081

MS

MSC

VLR

HLR

1 3

2 4

5 6

8 9

10

11 12

14 15

13

16

17 18

20 21

19

22

23 24

26

25

2753
2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2082

1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18) 19) 20) 21) 22) 23) 24) 25) 26)

A_CM_SERV_REQ (Note 1) MAP_PROCESS_ACCESS_REQUEST (Note 2) A_REGISTER_PASSWORD (Note 1) MAP_REGISTER_PASSWORD_req/ind MAP_REGISTER_PASSWORD_req/ind MAP_GET_PASSWORD_req/ind (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) A_GET_PASSWORD (Note 1, Note 3) A_GET_PASSWORD ack (Note 1, Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) A_GET_PASSWORD (Note 1, Note 3) A_GET_PASSWORD ack (Note 1, Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) MAP_GET_PASSWORD_req/ind (Note 3) A_GET_PASSWORD (Note 1, Note 3) A_GET_PASSWORD ack (Note 1, Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_GET_PASSWORD_rsp/cnf (Note 3) MAP_REGISTER_PASSWORD_rsp/cnf MAP_REGISTER_PASSWORD_rsp/cnf A_REGISTER_PASSWORD (Note 1)

2083

2788

2782 2783 2784 2785 2786 2787

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines are triggers/ triggered signalling on the radio path. NOTE 2: For details of the Process Access Request procedure, refer to subclause 25.4 in the present document. NOTE 3: The use of each of the three MAP_GET_PASSWORD operations is described in subclause 22.8.4.

Figure 22.8.1/1: Message flow for supplementary service password registration

2789

22.8.2 Procedure in the MSC

2790 The password registration procedure in the MSC is identical to that for activation specified in subclause 22.4.2. All the 2791 text and diagrams in subclause 22.4.2 apply with all references to activation changed to password registration.

2792

22.8.3 Procedure in the VLR

2793 The password registration procedure in the VLR is identical to that for activation specified in subclause 22.4.3. All the 2794 text and diagrams in subclause 22.4.3 apply with all references to activation changed to password registration.

2795

22.8.4 Procedure in the HLR

Check_Indication see subclause 25.2.1.

2796 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2797

2798 The HLR shall process the MAP_REGISTER_PASSWORD indication as specified in 3GPP TS 23.011 [22]. During 2799 the handling of password registration, the password procedure is initiated (as specified in 3GPP TS 23.011 [22]) This 2800 involves the sending of MAP_GET_PASSWORD requests to the VLR. 2801 The password registration process in the HLR is shown in figure 22.8.4/1.

2084

2085

process Register_Password_HLR
Process in the HLR to handle a request to register a password for a supplementary service

RP_HLR1(2)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the application process PW1/PW2/PW3/PW4 (see 3GPP TS 23.011)

Null

MAP_ REGISTER_ PASSWORD_ ind

Check_ Indication

Error Yes

OK Operator Determined Barring of SS management? No

Set User Error: Call barred

Call barring cause= Operator barring

register passwor d

MAP_REGISTER_SS_rsp MAP_CLOSE_req

Wait_For_ Application_ Response

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

2802
2803

Figure 22.8.4/1 (sheet 1 of 2): Process Register_PW_HLR

2086

2087

process Register_Password_HLR
Process in the HLR to handle a request to register a password for a supplementary service Wait_For_ Application_ Response

RP_HLR2(2)

password changed

error

get password

get new passwor d

get new password again

Set User Error

MAP_GET_PASSWORD_req MAP_DELIMITER_req

MAP_REGISTER_PASSWORD_rsp MAP_CLOSE_req

Wait_For_ Password

MAP_GET_ PASSWORD_ cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Check_ Confirmation OK, User Error SS Get Password_ Ack

MAP_U_ ABORT_ req

Data Error Set User Error: System failure

Provider Error

MAP_REGISTER_PASSWORD_rsp MAP_CLOSE_req

Wait_For_ Application_ Response

2804
2805

Figure 22.8.4/1 (sheet 2 of 2): Process Register_PW_HLR

2088

2089

2806 2807

22.9 Mobile Initiated USSD procedure

22.9.1 General

2808 The procedure supports supplementary service signalling procedures which allow PLMN specific services to be 2809 introduced. 2810 The message flow for the procedure can be found in 3GPP TS 23.090 [34]. 2811 The following services may be used: 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821

MAP_PROCESS_ACCESS_REQUEST MAP_TRACE_SUBSCRIBER_ACTIVITY MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_READY_FOR_SM MAP_UNSTRUCTURED_SS_REQUEST MAP_UNSTRUCTURED_SS_NOTIFY

(see clauses 8 and 25); (see clauses 9 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25); (defined in clause 11); (defined in clause 11).

2822 The following service is certainly used: 2823

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST (defined in clause 11).

2824

22.9.2 Procedure in the MSC

Check_Confirmation see subclause 25.2.2.

2825 The process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2826

2827 The A_PROCESS_UNSTRUCTURED_SS_REQUEST from the MS contains information input by the user; the 2828 message may be fed to an application contained locally in the MSC or to the VLR. The rules for determining this are 2829 specified in 3GPP TS 23.090 [34]. 2830

1) Message Destined for the VLR

2831 If the message is destined for the VLR then the MSC shall transfer the message to the VLR using the mapping specified 2832 in detail in 3GPP TS 29.011 [59]. 2833

2) Message Destined for the Local Application

2834 If the message is destined for the local USSD application then the MSC shall transfer the information contained in the 2835 message to the application. 2836 The process in the MSC is shown in figure 22.9.2/1.

2837

22.9.3 Procedure in the VLR

Receive_Open_Cnf Check_Confirmation see subclause 25.1.2; see subclause 25.2.2;

2838 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2839 2840
2090

2091

2841

Process_Access_Request_VLR

see subclause 25.4.2.

2842 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST from the MSC contains information input by the user; the 2843 message may be fed to an application contained locally in the VLR or to the HLR. The rules for determining this are 2844 specified in 3GPP TS 23.090 [34]. 2845

1) Message Destined for the HLR

2846 If the message is destined for the HLR then the VLR shall transfer the message transparently to the HLR. 2847

2) Message Destined for the Local Application

2848 If the message is destined for the local USSD application then the VLR shall transfer the information contained in the 2849 message to the application. 2850 The process in the VLR is shown in figure 22.9.3/1.

2851

22.9.4 Procedure in the HLR

Receive_Open_Ind Receive_Open_Cnf Check_Confirmation see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.2.

2852 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2853 2854 2855

2856 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST from the VLR contains information input by the user. If the 2857 alphabet used for the message is understood then the message shall be fed to an application contained locally in the 2858 HLR or to the gsmSCF or to a secondary HLR where the USSD application is located. 2859

1) Message Destined for the Local Application

2860 If the message is destined for the local USSD application then the HLR shall transfer the information contained in the 2861 message to the local application. 2862

2) Message Destined for the gsmSCF or the secondary HLR

2863 If the message is destined for the gsmSCF or the secondary HLR then the primary HLR shall transfer the message 2864 transparently to the next node. 2865 The process in the primary HLR is shown in figure 22.9.4/1.

2866

22.9.5 Procedures in the gsmSCF/secondary HLR

Receive_Open_Ind see subclause 25.1.1.

2867 The MAP process invokes a macro not defined in this clause; the definition of this macros can be found as follows: 2868

2869 The process in the gsmSCF or secondary HLR is shown in figure 22.9.5/1.

2092

2093

process MS_Init_USSD_MSC
Process in the M to handle an SC MS initiated USSD transaction

MI_USSD_MSC1(3)
Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the VLR

Wait_For_ Service_Indication

A_PROCESS_UNSTRUCTURED_SS_REQUEST_ind

Yes Handle in MSC? (See 3GPP TS 23.090) No

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req MAP_DELIMITER_req

Wait_For_ PUSSR_ Confirm

MAP_UNSTRUCTURED_SS_ NOTIFY_ind

MAP_UNSTRUCTURED_SS_ REQUEST_ind

A_UNSTRUCTURED_SS_ NOTIFY_r eq

A_UNSTRUCTURED_SS_ REQUEST_req

Wait_For_ USSN_ Confirm

Wait_For_ USSR_ Confirm

A_UNSTRUCTURED_SS_ NOTIFY_cnf

A_UNSTRUCTURED_SS_ REQUEST_cnf

MAP_UNSTRUCTURED_SS_ NOTIFY_r sp MAP_DELIMITER_req

MAP_UNSTRUCTURED_SS_ REQUEST_rsp MAP_DELIMITER_req

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

2870
2871

Figure 22.9.2/1 (sheet 1 of 3): Process MS_Init_USSD_MSC

2094

2095

process MS_Init_USSD_MSC
Process in the MSC to handle an MS initiated USSD transaction Wait_For_ PUSSR_ Confirm

MI_USSD_MSC2(3)
Signals to/from the left ar e to/from the SS co-ordinating process in the MSC; signals to/fr om the right ar e to/from the VLR

MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_cnf

Check_ Confirmation

OK, U ser Er ror, Data Er ror A_PROCESS_U NSTRUCTURED_ SS_REQUEST_rsp A_CM_RELEASE_req

Provider Err or A_CM_ RELEASE_ req

Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm

A_CM_ SERV_ RELEASE_ ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ ABORT_ req

Application pr ocedure cancellation

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ RELEASE_ req

2872
2873

Figure 22.9.2/1 (sheet 2 of 3): Process MS_Init_USSD_MSC

2096

2097

process MS_Init_USSD_MSC
Process in the M to handle an SC MS initiated USSD transaction 1

MI_USSD_MSC3(3)
Signals to/from the left are to/from the SS co-ordinating process in the MSC; signals to/from the right are to/from the USSD application process in the MSC unless shown otherwise

Process Unstructured SS Request

MAP_ CLOSE_ req

To VLR

Wait_For_ Application_ Response

Unstructured SS Notify

Unstructured SS Request

Process Unstructured SS Request ack, Process Unstructured SS Request negative response

A_UNSTRUCTURED_SS_ NOTIFY_r eq

A_UNSTRUCTURED_SS_ REQUEST_req

A_PROCESS_UNSTRUCTURED_ SS_REQUEST_rsp A_CM _RELEASE_req

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

A_UNSTRUCTURED_SS_ NOTIFY_cnf

A_UNSTRUCTURED_SS_ REQUEST_cnf

Unstructured SS Notify ack

Unstructured SS Request ack

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

A_CM_ SERV_ RELEASE_ ind

Abort

Abort

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ SERV_ RELEASE_ req

2874
2875

Figure 22.9.2/1 (sheet 3 of 3): Process MS_Init_USSD_MSC

2098

2099

process MS_Init_USSD_VLR
Process in the VLR to handle an MS initiated USSD transaction

MI_USSD_VLR1(4)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR Null

Receive_ Open_Ind

OK

Vr, Error

Wait_For_ PAR

Null

MAP_U_ABORT_ind, MAP_CLOSE_ind

Process_ Access_ Request_VLR

OK Null Wait_For_ PUSSR_ Request Null

Error

MAP_ CLOSE_ ind

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind

Yes Null No Yes Set User Error: Call barred Call barring cause= Operator barring No MAP_PROCESS_ UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_req MAP_OPEN_req MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req MAP_DELIMITER_req Handle in VLR? (See 3GPP TS 23.090) Operator Determined Barring of SS management?

Null

Receive_ Open_Cnf

Vr MAP_U_ ABORT_ req

Error Set User Error: System failure

OK Wait_For_ PUSSR_ Confirm

Null

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp MAP_CLOSE_req

Null

2876
2877

Figure 22.9.3/1 (sheet 1 of 4): Process MS_Init_USSD_VLR

2100

2101

process MS_Init_USSD_VLR
Process in the VLR to handle an MS initiated USSD transaction Wait_For_ PUSSR_ Confirm

MI_USSD_VLR2(4)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR

MAP_PROCESS_ UNSTRUCTURED_ SS_REQUEST_cnf

Check_ Confirmation

Provider Error MAP_U_ ABORT_ req

OK, User Error, Data Error MAP_PROCESS_ UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_req

Null

Null

Wait_For_ PUSSR_ Confirm

MAP_UNSTRUCTURED_SS_ NOTIFY_ind

MAP_UNSTRUCTURED_SS_ REQUEST_i nd

MAP_UNSTRUCTURED_SS_ NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_SS_ REQUEST_req MAP_DELIMITER_req

Wait_For_ USSN_ Confirm

Wait_For_ USSR_ Confirm

MAP_UNSTRUCTURED_SS_ NOTIFY_cnf

MAP_UNSTRUCTURED_SS_ REQUEST_cnf

MAP_UNSTRUCTURED_SS_ NOTIFY_rsp MAP_DELIMITER_req

MAP_UNSTRUCTURED_SS_ REQUEST_rsp MAP_DELIMITER_req

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

2878
2879

Figure 22.9.3/1 (sheet 2 of 4): Process MS_Init_USSD_VLR

2102

2103

process MS_Init_USSD_VLR
Process in the VLR to handle an MS initiated USSD transaction

MI_USSD_VLR3(4)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR Wait_For_PUSSR_Confirm , Wait_For_USSN_Confirm, Wait_For_USSR_Confirm,

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_U_ ABORT_ req

MAP_ CLOSE_ req

Null

MAP_U_ ABORT_ req

Null

2880
2881

Figure 22.9.3/1 (sheet 3 of 4): Process_MS_Init_USSD_VLR

2104

2105

process MS_Init_USSD_VLR
Process in the VLR to handle an MS initiated USSD transaction 1

MIUSSD_VLR4(4)
Signals to/from the left ar e to/from the MSC; signals to/fr om the right ar e to/from the USSD application pr ocess in the VLR

Process Unstructured SS Request

Wait_For_ Application_ Response

Unstructured SS Notify

Unstructured SS Request

Process Unstructured SS Request ack, Process Unstructured SS Request negative response

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_req

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

Null

MAP_UNSTRUCTURED_SS_ NOT IFY_cnf

MAP_UNSTRUCTURED_SS_ REQUEST_cnf

Unstructured SS Notify ack

Unstructured SS Request ack

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

Wait_For_Application_Response, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

MAP_U_ABORT_ind, MAP_CLOSE_ind

Abort

Abort

MAP_U_ ABORT_ req

Null

Null

2882
2883 2884

Figure 22.9.3/1 (sheet 4 of 4): Process_MS_Init_USSD_VLR Figure 22.9.3/2 void

2106

2107

process MS_Init_USSD_HLR
Process in the HLR to handle an MS initiated USSD transaction

MI_USSD_HLR1(4)
Signals to/from the left ar e to/from the VLR; signals to/fr om the right ar e to/from the next node (gsmSCF or secondary HLR)

Null

Receive_ Open_Ind

Vr Per for m MAP Vr dialogue

Er ror

OK Wait_For_ Service_ Indication

Null

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind

Yes Oper ator Determined Barring of SS management? No Yes Alphabet supported? No Set User Error: Call barred Call barring cause= Oper ator barr ing Set User Error : Unknown alphabet Yes Handle in HLR? (See 3GPP TS 23.090) No

MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_r eq

MAP_OPEN_req MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_req MAP_DELIMITER_req

Null

Receive_ Open_Cnf

Vr MAP_U_ ABORT_ req

Error Set User Err or : System failure

OK Wait_For_ PUSSR_ Confirm

Null

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_rsp MAP_CLOSE_r eq

Null

2885
2886

Figure 22.9.4/1 (sheet 1 of 4): Process MS_Init_USSD_HLR

2108

2109

process MS_Init_USSD_HLR
Process in the HLR to handle an MS initiated USSD transaction Wait_For_ PUSSR_ Confirm

MI_USSD_HLR2(4)
Signals to/from the left ar e to/from the VLR; signals to/fr om the right ar e to/from the next node (gsmSCF or secondary HLR)

MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_cnf

Check_ Confirmation

Provider Err or MAP_U_ ABORT_ req

OK, U ser Er ror, Data Error MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_r sp MAP_CLOSE_r eq

Null

Null

Wait_For_ PUSSR_ Confirm

MAP_UNSTRUCTURED_SS_ NOTIFY_ind

MAP_UNSTRUCTURED_SS_ REQUEST_ind

MAP_UNSTRUCTURED_SS_ NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_SS_ REQUEST_req MAP_DELIMITER_req

Wait_For_ USSN_ Confirm

Wait_For_ USSR_ Confirm

MAP_UNSTRUCTURED_SS_ NOTIFY_cnf

MAP_UNSTRUCTURED_SS_ REQUEST_cnf

MAP_UNSTRUCTURED_SS_ NOTIFY_rsp MAP_DELIMITER_req

MAP_UNSTRUCTURED_SS_ REQUEST_rsp MAP_DELIMITER_req

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

2887
2888

Figure 22.9.4/1 (sheet 2 of 4): Process MS_Init_USSD_HLR

2110

2111

process MS_Init_USSD_HLR
Process in the HLR to handle an MS initiated USSD transaction Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm,

MI_USSD_HLR3(4)
Signals to/from the left are to/from the VLR; signals to/fr om the right are to/from the next node (gsmSCF or secondary HLR)

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ CLOSE_ req

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

MAP_U_ ABORT_ req

Null

Null

2889
2890

Figure 22.9.4/1 (sheet 3 of 4): Process MS_Init_USSD_HLR

2112

2113

process MS_Init_USSD_HLR
Process in the HLR to handle an MS initiated USSD transaction 1

MI_USSD_HLR4(4)
Signals to/from the left are to/from the VLR; signals to/fr om the right are to/from the USSD application process in the HLR

Process Unstructured SS Request

Wait_For_ Application_ Response

Unstructured SS Notify

Unstructured SS Request

Process Unstructured SS Request ack, Process Unstructured SS Request negative response

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_req

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

Null

MAP_UNSTRUCTURED_SS_ NOTIFY_cnf

MAP_UNSTRUCTURED_SS_ REQUEST_cnf

Unstructured SS Notify ack

Unstructured SS Request ack

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Abort

MAP_ CLOSE_ req

Abort

MAP_U_ ABORT_ req

Null

Null

2891
2892

Figure 22.9.4/1 (sheet 4 of 4): Process MS_Init_USSD_HLR

2114

2115

process MS_INIT_USSD_gsmSCF_Secondary_HLR
Process in the gsmSCF or secondary HLR to handle an MS initiated USSD transaction

MI_USSD_SCF1(2)
Signals to/from the left are to/from the HLR; signals to/fr om the right are to/from the USSD application process

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

Error

OK Wait_For_ Service_ Indication

Null

MAP_PROCESS_UNSTRUCTURED_SS_REQUEST_ind

Process Unstructured SS Request

Wait_For_ Application_ Response

Unstructured SS Notify

Unstructured SS Request

Process Unstructured SS Request ack, Process Unstructured SS Request negative response

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

MAP_PROCESS_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_req

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

Null

MAP_UNSTRUCTURED_SS_ NOT IFY_cnf

MAP_UNSTRUCTURED_SS_ REQUEST_cnf

Unstructured SS Notify ack

Unstructured SS Request ack

Wait_For_ PUSSR_ Confirm

Wait_For_ PUSSR_ Confirm

2893
2894

Figure 22.9.5/1 (sheet 1 of 2): Process MS_Init_USSD_gsmSCF_Secondary_HLR

2116

2117

process MS_INIT_USSD_gsmSCF_Secondary_HLR
Process in the gsmSCF or secondary HLR to handle an MS initiated USSD transaction Wait_For_PUSSR_Confirm, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

MI_USSD_SCF2(2)
Signals to/from the left are to/from the HLR; signals to/fr om the right are to/from the USSD application process

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Abort

MAP_ CLOSE_ req

Abort

MAP_U_ ABORT_ req

Null

Null

2895
2896

Figure 22.9.5/1 (sheet 2 of 2): Process MS_Init_USSD_gsmSCF_Secondary_HLR

2118

2119

2897 2898

22.10 Network initiated USSD procedure

22.10.1 General

2899 The procedure supports supplementary service signalling procedures which allow PLMN specific services to be 2900 introduced. 2901 The message flow for the procedure can be found in 3GPP TS 23.090 [34]. 2902 The following services may be used: 2903 2904 2905 2906 2907 2908 2909

MAP_PAGE MAP_SEARCH_FOR_MOBILE_SUBSCRIBER MAP_PROCESS_ACCESS_REQUEST MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_FORWARD_NEW_TMSI MAP_READY_FOR_SM

(see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 8 and 25); (see clauses 12 and 25).

2910 At least one of the following services will certainly be used, and both may be used: 2911 2912

MAP_UNSTRUCTURED_SS_REQUEST MAP_UNSTRUCTURED_SS_NOTIFY

(defined in clause 11); (defined in clause 11).

2913

22.10.2 Procedure in the MSC

Receive_Open_Ind Receive_Open_Cnf Page_MSC Search_For_MS_MSC Process_Access_Request_MSC see subclause 25.1.1; see subclause 25.1.2; see subclause 25.3.1; see subclause 25.3.2; see subclause 25.4.1.

2914 The process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2915 2916 2917 2918 2919

2920 The process in the MSC is shown in figure 22.10.2/1.

2921

22.10.3 Procedure in the VLR

Receive_Open_Ind Receive_Open_Cnf Check_Indication Check_Confirmation see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.1; see subclause 25.2.2.

2922 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2923 2924 2925 2926

2927 The process in the VLR is shown in figure 22.10.3/1. 2928 MSC Initiated USSD

2120

2121

2929 If a USSD application in the MSC wishes to use the network initiated USSD procedure, and a connection to the MS 2930 does not exist then the MSC opens a dialogue with the VLR. This dialogue leads to the VLR performing page or search 2931 using the macro Start_USSD_VLR. 2932 Macro Start_USSD_VLR 2933 The macro invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2934 2935

Check_Confirmation Process_Access_Request_VLR

see subclause 25.2.1; see subclause 25.4.2.

2936 The macro is shown in figure 22.10.3/2.

2937

22.10.4 Procedure in the HLR

Receive_Open_Ind Receive_Open_Cnf Check_Indication Check_Confirmation see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.1; see subclause 25.2.2.

2938 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2939 2940 2941 2942

2943 The process in the primary HLR is shown in figures 22.10.4/1 and 22.10.4/2.

2944

22.10.5 Procedure in the gsmSCF or secondary HLR

Receive_Open_Cnf Check_Confirmation see subclause 25.1.2; see subclause 25.2.2.

2945 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2946 2947

2948 The procedure in the gsmSCF or secondary HLR is shown in figure 22.10.5/1.

2122

2123

process NW_Init_USSD_MSC
Process in the M to handle a SC network initiated USSD transaction Null

NI_USSD_MSC3(4)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise

Start USSD

From the USSD application in the MSC

MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ Paging_ Comm and_ Local

Vr, Error

Page_MSC

Search_For_ MS_MSC

MAP_U_ABORT_ind, MAP_CLOSE_i nd

Null MAP_ CLOSE_ req

Error

OK

OK MAP_ CLOSE_ req

Error

Null

Process_ Access_ Request_MSC

OK MAP_ CLOSE_ req

Error

Abort

To the USSD application in the MSC

Wait_For_ USSD_ Instruction

Null

2949
2950

Figure 22.10.2/1 (sheet 1 of 4): Process NW_Init_USSD_MSC

2124

2125

process NW _Init_USSD_MSC
Process in the MSC to handle a network initiated USSD transaction Wait_For_ USSD_ Indication

NI_USSD_MSC2(4)
Signals to/from the left are to/from the MS; signals to/fr om the right are to/from the VLR

MAP_UNSTRUCTURED_SS_ NOTIFY_ind

MAP_UNSTRUCTURED_SS_ REQUEST_ind

A_UNSTRUCTURED_SS_ NOTIFY_req

A_UNSTRUCTURED_SS_ REQUEST_r eq

Wait_For_ USSN_ Confirm

Wait_For_ USSR_ Confirm

A_UNSTRUCTURED_SS_ NOTIFY_cnf

A_UNSTRUCTURED_SS_ REQUEST_cnf

MAP_UNSTRUCTURED_SS_ NOTIFY_rsp MAP_DELIMITER_req

MAP_UNSTRUCTURED_SS_ REQUEST_r sp MAP_DELIMITER_req

Wait_For_ USSD_ Indication

Wait_For_ USSD_ Indication

Wait_For_USSN_Confirm, Wait_For_USSR_Confirm

A_CM_ SERV_ RELEASE_ ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ ABORT_ req

Application pr ocedure cancellation

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ RELEASE_ req

Null

Null

2951
2952

Figure 22.10.2/1 (sheet 2 of 4): Process NW_Init_USSD_MSC

2126

2127

process NW_Init_USSD_MSC
Process in the M to handle a SC network initiated USSD transaction Null

NI_USSD_MSC3(4)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise

Start USSD

From the USSD application in the MSC

MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ Paging_ Comm and_ Local

Vr, Error

Page_MSC

Search_For_ MS_MSC

MAP_U_ABORT_ind, MAP_CLOSE_i nd

Null MAP_ CLOSE_ req

Error

OK

OK MAP_ CLOSE_ req

Error

Null

Process_ Access_ Request_MSC

OK MAP_ CLOSE_ req

Error

Abort

To the USSD application in the MSC

Wait_For_ USSD_ Instruction

Null

2953
2954

Figure 22.10.2/1 (sheet 3 of 4): Process NW_Init_USSD_MSC

2128

2129

process NW _Init_USSD_MSC
Process in the MSC to handle a network initiated USSD transaction Wait_For_ USSD_ Instruction

NI_USSD_MSC4(4)
Signals to/from the left are to/from the MS; signals to/fr om the right are to/from the USSD application in the MSC

Unstructured SS Notify

Unstructured SS Request

A_UNSTRUCTURED_SS_ NOTIFY_req

A_UNSTRUCTURED_SS_ REQUEST_req

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

A_UNSTRUCTURED_SS_ NOTIFY_cnf

A_UNSTRUCTURED_SS_ REQUEST_cnf

Unstructured SS Notify ack

Unstructured SS Request ack

Wait_For_ USSD_ Instruction

Wait_For_ USSD_ Instruction

Wait_For_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

A_CM_ SERV_ RELEASE_ ind

USSD release

Abort

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ SERV_ RELEASE_ req

Null

Null

2955
2956

Figure 22.10.2/1 (sheet 4 of 4): Process NW_Init_USSD_MSC

2130

2131

process NW _Init_USSD_VLR
Process in the VLR to handle a network initiated USSD transaction

NI_USSD_VLR1(5)
Signals to/from the left are to/from the MSC; signals to/fr om the right are to/from the HLR Null

Receive_ Open_Ind

From HLR

OK Wait_For_ USSD_ Indication

Vr, Err or

Null

MAP_UNSTRUCTURED_ SS_NOTIFY_ind

MAP_UNSTRUCTURED_ SS_REQUEST_ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Check_ Indication

Check_ Indication

MAP_ CLOSE_ req

Er ror MAP_UNSTRUCTURED_ SS_NOTIFY_rsp MAP_CLOSE_r eq

OK

Error MAP_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_r eq

OK

Null

Null

Null

MAP_OPEN_req MAP_DELIMITER_req

MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf Vr, Err or OK Star t_USSD_ VLR Null

Receive_ Open_Cnf Vr, Err or OK Start_USSD_ VLR Null

OK MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

Error

OK MAP_UNSTRUCTURED_ SS_REQUEST_r eq MAP_DELIMITER_req

Error

Set User Error

Set User Error

Wait_For_ USSN_ Confirm

MAP_UNSTRUCTU RED_ SS_NOTIFY_rsp MAP_CLOSE_req

Wait_For_ USSR_ Confirm

MAP_UNSTRUCTU RED_ SS_REQUEST_rsp MAP_CLOSE_req

Null

Null

2957
2958

Figure 22.10.3/1 (sheet 1 of 5): Process NW_Init_USSD_VLR

2132

2133

process NW _Init_USSD_VLR
Process in the VLR to handle a network initiated USSD transaction Wait_For_ Next_USSD_ Indication

NI_USSD_VLR2(5)
Signals to/from the left are to/from the MSC; signals to/fr om the right are to/from the HLR

MAP_ CLOSE_ ind

MAP_UNSTRUCTURED_ SS_NOTIFY_ind

MAP_UNSTRUCTURED_ SS_REQUEST_ind

MAP_ CLOSE_ req

Check_ Indication

Check_ Indication

Error MAP_UNSTRUCTURED_ SS_NOTIFY_rsp MAP_CLOSE_r eq

OK

Error MAP_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_r eq

OK

Null

MAP_ CLOSE_ req

MAP_ CLOSE_ req

Null

Null

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_r eq MAP_DELIMITER_req

Wait_For_ USSN_ Confirm

Wait_For_ USSR_ Confirm

MAP_UNSTRUCTURED_ SS_NOTIFY_cnf

MAP_UNSTRUCTURED_ SS_REQUEST_cnf

MAP_UNSTRUCTURED_ SS_NOTIFY_rsp MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_r sp MAP_DELIMITER_req

Wait_For_ Next_USSD_ Indication

Wait_For_ Next_USSD_ Indication

2959
2960

Figure 22.10.3/1 (sheet 2 of 5): Process NW_Init_USSD_VLR

2134

2135

process NW _Init_USSD_VLR
Process in the VLR to handle a network initiated USSD transaction

In the upper subtrees, signals to/from the left ar e to/from the VLR; signals to/from the right ar e to/from the HLR

NI_USSD_VLR3(5)
Wait_For_Next_USSD_Indication, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm

Wait_For_USSN_Confirm, Wait_For_USSR_Confirm

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_P_ABORT _ind, MAP_U_ABORT_ind

MAP_ CLOSE_ ind

MAP_U_ ABORT_ req

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

Null

MAP_U_ ABORT_ req

Null

Null In the lower subtrees, signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD application in the VLR

Null

Wait_For_USSD_Instruction, Wait_For_USSN_Confirm, Wait_For_USSR_Confirm

Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

Receive_ Open_Ind

From MSC

Abort

MAP_U_ABORT_ind, MAP_CLOSE_ind

OK Start_USSD_ VLR

Vr, Error MAP_U_ ABORT_ req

Abort

OK, Err or

Null

Null

Null

Null

2961
2962

Figure 22.10.3/1 (sheet 3 of 5): Process NW_Init_USSD_VLR

2136

2137

process NW _Init_USSD_VLR
Process in the VLR to handle a network initiated USSD transaction Null

NI_USSD_VLR4(5)
Signals to/from the left are to/from the MSC; signals to/fr om the right are to/from the USSD application in the VLR

Start USSD

MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ USSD_ Instruction

Vr, Error

Abort

Unstructured SS Notify

Unstructured SS Request

Null

Start_USSD_ VLR

Start_USSD_ VLR

OK MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

Error Set negative response

OK MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

Error Set negative response

Wait_For_ USSN_ Confirm_ Local

Unstructured SS Notify negative response

Wait_For_ USSR_ Confirm_ Local

Unstructured SS Request negative response

Null

Null

2963
2964

Figure 22.10.3/1 (sheet 4 of 5): Process NW_Init_USSD_VLR

2138

2139

process NW _Init_USSD_VLR
Process in the VLR to handle a network initiated USSD transaction Wait_For_ Next_USSD_ Instruction

NI_USSD_VLR5(5)
Signals to/from the left are to/from the MSC; signals to/fr om the right are to/from the USSD application in the VLR

USSD release

Unstructured SS Notify

Unstructured SS Request

MAP_ CLOSE_ req

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

Null

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

MAP_UNSTRUCTURED_ SS_NOTIFY_cnf

MAP_UNSTRUCTURED_ SS_REQUEST_cnf

Check_ Confirmation User Error, Data Error, Provider Error Set negative response User Error, Data Error, Provider Err or Set negative response

Check_ Confirmation

OK

OK

Set ack

Set ack

Unstructured SS Notify negative response

Unstructured SS Notify ack

Unstructured SS Request negative response

Unstructured SS Request ack

Wait_For_ Next_USSD_ Instruction

Wait_For_ Next_USSD_ Instruction

2965
2966

Figure 22.10.3/1 (sheet 5 of 5): Process NW_Init_USSD_VLR

2140

2141

macrodefinition Start_USSD_VLR
Macr o in the VLR to page the MS to start a network initiated USSD transaction

S_USSD_VLR1(2)
Signals to/from the left are to/from the MSC

No Subscriber data confirmed by HLR? Yes

Yes IMSI detached? No

No Roaming allowed in current location area? Yes

No Set User Error: System Failure Set User Error: Absent Subscriber LAI known? Yes

No Er ror Yes Confirmed by Radio Contact?

MAP_SEARCH_FOR_MS_req MAP_DELIMITER_req

MAP_PAGE_r eq MAP_DELIMITER_req

Wait_For_ Access_Request

2967
2968

Figure 22.10.3/2 (sheet 1 of 2): Macro Start_USSD_VLR

2142

2143

macrodefinition Start_USSD_VLR
Macr o in the VLR to page the MS to start a network initiated USSD transaction

S_USSD_VLR2(2)
Signals to/from the left are to/from the MSC

Wait_For_ Access_Request

MAP_U_ ABORT_ ind

Process_Access_ Request_VLR

MAP_PAGE_ cnf

MAP_SEARCH_ FOR_MS_cnf

OK

Error Check_ Confirmation User Error OK Yes Absent subscriber? No Update LAI Error

Er ror

OK

Error

Provider Error , Data Error

Set User Error : Absent subscriber

Set User Err or : System failure

Confirmed by Radio Contact:= Confirmed

MAP_ CLOSE_ req

Wait_For_ Access_Request

Error

2969
2970

Figure 22.10.3/2 (sheet 2 of 2): Macro Start_USSD_VLR

2144

2145

process NW _Init_USSD_HLR
Process in the HLR to handle a networ k initiated USSD transaction

NI_USSD_HLR1(5)
Signals to/from the left are to/from the VLR; signals to/fr om the r ight are to/from the next node (gsmSCF or secondary HLR)

Null

Receive_ Open_Ind

From gsmSCF or secondar y HLR

OK Wait_For_ USSD_ Indication

Vr, Error

Null

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_UNSTRUCTURED_ SS_REQUEST_ind

MAP_ CLOSE_ req

Null

Check_ Indication

OK MAP_UNSTRUCTURED_ SS_NOTIFY_ind Start_ USSD_HLR Error OK Check_ Indication MAP_U_ ABORT_ req Abort

Error

Null

MAP_UNSTRUCTURED_ SS_REQUEST_r sp MAP_CLOSE_req

OK Star t_ USSD_HLR Error OK MAP_U_ ABORT_ req Abort

Error

Null

Null

MAP_UNSTRUCTURED_ SS_NOTIFY_rsp MAP_CLOSE_r eq

Null

Null

2971
2972

Figure 22.10.4/1 (sheet 1 of 5): Process NW_Init_USSD_HLR

2146

2147

process NW _Init_USSD_HLR
Process in the HLR to handle a network initiated USSD transaction 1 2

NI_USSD_HLR2(5)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the next node (gsmSCF or secondary HLR)

MAP_OPEN_req MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_OPEN_req MAP_UNSTRUCTURED_ SS_REQUEST_r eq MAP_DELIMITER_req

Receive_ Open_Cnf

Receive_ Open_Cnf

OK MAP_U_ ABORT_ req

Vr, Error

OK MAP_U_ ABORT_ req

Vr, Err or

Wait_For_ USSN_ Confirm

Null

Wait_For_ USSR_ Confirm

Null

Wait_For_USSN_Confirm, Wait_For_USSR_Confirm

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ NOTICE_ ind

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ CLOSE_ req

MAP_ CLOSE_ req

Set User Error: System failure

MAP_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_r eq

MAP_U_ ABORT_ req

Null

Null

2973
2974

Figure 22.10.4/1 (sheet 2 of 5): Process NW_Init_USSD_HLR

2148

2149

process NW _Init_USSD_HLR
Process in the HLR to handle a network initiated USSD transaction Wait_For_ Next_USSD_ Indication

NI_USSD_HLR3(5)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the next node (gsmSCF or secondary HLR)

MAP_ CLOSE_ ind

MAP_UNSTRUCTURED_ SS_NOTIFY_ind

MAP_UNSTRUCTURED_ SS_REQUEST_ind

MAP_ CLOSE_ req

Check_ Indication

Check_ Indication

Error MAP_UNSTRUCTURED_ SS_NOTIFY_rsp MAP_CLOSE_r eq

OK

Error MAP_UNSTRUCTURED_ SS_REQUEST_rsp MAP_CLOSE_r eq

OK

Null

MAP_ CLOSE_ req

MAP_ CLOSE_ req

Null

Null

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_r eq MAP_DELIMITER_req

Wait_For_ USSN_ Confirm

Wait_For_ USSR_ Confirm

MAP_UNSTRUCTURED_ SS_NOTIFY_cnf

MAP_UNSTRUCTURED_ SS_REQUEST_cnf

MAP_UNSTRUCTURED_ SS_NOTIFY_rsp MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_r sp MAP_DELIMITER_req

Wait_For_ Next_USSD_ Indication

Wait_For_ Next_USSD_ Indication

2975
2976

Figure 22.10.4/1 (sheet 3 of 5): Process NW_Init_USSD_HLR

2150

2151

process NW _Init_USSD_HLR
Process in the HLR to handle a network initiated USSD transaction Null

NI_USSD_HLR4(5)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD application in the HLR

Unstructured SS Notify

Unstructured SS Request

No MS reachable? Yes MAP_OPEN_req MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req Set Negative response: MS not reachable MS reachable? Yes

No

MAP_OPEN_req MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

Set Negative response: MS not reachable

Receive_ Open_Cnf

Unstructured SS Notify negative response Vr, Error

Receive_ Open_Cnf

Unstructured SS Notify negative response Vr, Error

OK

OK

Abort

Null

Abort

Null

Wait_For_ USSN_ Confirm_ Local

Null

Wait_For_ USSR_ Confirm_ Local

Null

Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Abort

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

Abort

Null

Null

2977
2978

Figure 22.10.4/1 (sheet 4 of 5): Process NW_Init_USSD_HLR

2152

2153

process NW _Init_USSD_HLR
Process in the HLR to handle a network initiated USSD transaction Wait_For_ Next_USSD_ Instruction

NI_USSD_HLR5(5)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD application in the HLR

USSD release

Unstructured SS Notify

Unstructured SS Request

MAP_ CLOSE_ req

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

Null

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

MAP_UNSTRUCTURED_ SS_NOTIFY_cnf

MAP_UNSTRUCTURED_ SS_REQUEST_cnf

Check_ Confirmation User Error, Data Error, Provider Err or Set negative response User Error, Data Error, Provider Err or Set negative response

Check_ Confirmation

OK

OK

Set ack

Set ack

Unstructured SS Notify negative response

Unstructured SS Notify ack

Unstructured SS Request negative response

Unstructured SS Request ack

Wait_For_ Next_USSD_ Instruction

Wait_For_ Next_USSD_ Instruction

2979
2980

Figure 22.10.4/1 (sheet 5 of 5): Process NW_Init_USSD_HLR

2154

2155

macrodefinition Start_USSD_HLR
Macr o in the HLR to check the reachability of the subscr iber for a network initiated USSD transaction

S_USSD_HLR1(1)

No Subscriber known? Yes

No Location known? Yes Abort

Yes MS purged? No

Yes MSC area restricted? No

Yes Roaming restriction due to unsupported feature?

Set User Error : Absent subscriber

Error

OK

2981
2982

Figure 22.10.4/2: Macro Start_USSD_HLR

2156

2157

process NI_USSD_gsmSCF_Secondary_HLR
Process in the gsmSCF or secondary HLR to handle a network initiated USSD transaction

NI_USSD_SCF1(2)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD application process

Null

Unstructured SS Notify

Unstructured SS Request

MAP_OPEN_req MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_OPEN_req MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

Receive_ Open_Cnf

Receive_ Open_Cnf

OK

Vr, Error

OK

Vr, Error

Abort

Abort

Wait_For_ USSN_ Confirm_ Local

Null

Wait_For_ USSR_ Confirm_ Local

Null

Wait_For_Next_USSD_Instruction, Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

Wait_For_USSN_Confirm_Local, Wait_For_USSR_Confirm_Local

MAP_P_ABORT _ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Abort

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

Abort

Null

Null

2983
2984

Figure 22.10.5/1 (sheet 1 of 2): Process NW_Init_USSD_gsmSCF_secondary_HLR

2158

2159

process NI_USSD_gsmSCF_Secondary_HLR
Process in the gsmSCF or secondary HLR to handle a network initiated USSD transaction Wait_For_ Next_USSD_ Instruction

NI_USSD_SCF2(2)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD application process

USSD release

Unstructured SS Notify

Unstructured SS Request

MAP_ CLOSE_ req

MAP_UNSTRUCTURED_ SS_NOTIFY_req MAP_DELIMITER_req

MAP_UNSTRUCTURED_ SS_REQUEST_req MAP_DELIMITER_req

Null

Wait_For_ USSN_ Confirm_ Local

Wait_For_ USSR_ Confirm_ Local

MAP_UNSTRUCTURED_ SS_NOTIFY_cnf

MAP_UNSTRUCTURED_ SS_REQUEST_cnf

Check_ Confirmation User Error, Data Error, Provider Err or Set negative response User Error, Data Error, Provider Err or Set negative response

Check_ Confirmation

OK

OK

Set ack

Set ack

Unstructured SS Notify negative response

Unstructured SS Notify ack

Unstructured SS Request negative response

Unstructured SS Request ack

Wait_For_ Next_USSD_ Instruction

Wait_For_ Next_USSD_ Instruction

2985
2986

Figure 22.10.5/1 (sheet 2 of 2): Process NW_Init_USSD_gsmSCF_Secondary_HLR

2160

2161

2987

22.11 Common macros for clause 22

2988 The following macros are used for the description of more than one of the supplementary service processes described in 2989 clause 22.

2990

22.11.1 SS Password handling macros

2991 Macro Get_Password_MSC 2992 This macro is used by the MSC to relay a request for password from the VLR to the MS, and to relay a response from 2993 the MS back to the VLR. The macro is shown in figure 22.11.1/1. 2994 Macro Get_Password_VLR 2995 This macro is used by the VLR to relay a request for password from the HLR to the MSC, and to relay a response from 2996 the MSC back to the HLR. The macro invokes a macro not defined in this clause; the definition of this macro can be 2997 found as follows: 2998

Check_Indication

see subclause 25.2.1.

2999 The macro is shown in figure 22.11.1/2.

3000

22.11.2 Void

2162

2163

macrodefinition Get_Password_MSC
Macro in the MSC to relay a password request and response

Get_Pwd_MSC1(1)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

MAP_GET_ PASSWORD_ ind

A_GET_ PASSWORD_ req

Wait_For_ Password

A_CM_ SERV_ RELEASE_ ind

A_GET_ PASSWORD_ cnf

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

Application procedure cancellation

MAP_GET_PASSWORD_rsp MAP_DELIMITER_req

A_CM_ RELEASE_ COMPLETE_ req

A_CM_ RELEASE_ req

Null

OK

Null

3001
3002

Figure 22.11.1/1: Macro Get_Password_MSC

2164

2165

macrodefinition Get_Password_VLR
Macro in the VLR to relay a password request and response

Get_Pwd_VLR1(1)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR

MAP_GET_ PASSWORD_ ind

Check_ Indication

Error MAP_U_ ABORT_ req

OK

MAP_GET_PASSWORD_req MAP_DELIMITER_req

MAP_U_ ABORT_ req

Wait_For_ Password

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_GET_ PASSWORD_ cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

MAP_GET_PASSWORD_rsp MAP_DELIMITER_req

MAP_ CLOSE_ req

Null

Null

OK

Null

3003
3004 3005 3006 3007 3008

Figure 22.11.1/2: Macro Get_Password_VLR Figure 22.11.2/1 void Figure 22.11.2/2 void Figure 22.11.2/3 void Figure 22.11.2/4 void

2166

2167

3009

Figure 22.11.2/5 void

2168

2169

3010 3011 3012

22.12 Supplementary Service Invocation Notification procedure

22.12.1 General

3013 The Supplementary Service Invocation Notification procedure is used to notify a gsmSCF about the invocation of a 3014 GSM Supplementary Service. 3015 The supplementary service invocation notification procedure is shown in figure 22.12.1/1. 3016 The following service is certainly used: 3017

MAP_SS_INVOCATION_NOTIFY

(defined in clause 11).

MSC

gsmSCF

3018
3019 3020 3021

1) 2)

MAP_SS_INVOCATION_NOTIFY_req/ind MAP_SS_INVOCATION_NOTIFY_rsp/cnf

3022

Figure 22.12.1/1: Message flow for supplementary service invocation notification

3023

22.12.2 Procedure in the MSC

Receive_Open_Cnf Check_Confirmation see subclause 25.1.2; see subclause 25.2.2.

3024 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3025 3026

3027 The supplementary service invocation notification process in the MSC is shown in figure 22.12.2/1.

3028

22.12.3 Procedure in the gsmSCF

Receive_Open_Ind see subclause 25.1.1.

3029 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 3030

3031 The supplementary service invocation notification process in thegsmSCF is shown in figure 22.12.3/1.

2170

2171

process Notify_SS_Invocation_MSC
Process in the M to notify the gsmSCF SC that a supplementary service has been invoked

NSSI_MSC1(1)
Signals to/from the left are to/from the SS handling application process in the MSC; signals to/from the right are to/from the gsmSCF

Null

Note SS invocation

MAP_OPEN_req MAP_SS_INVOCATION_NOTIFY_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Error

OK Wait_For_ gsmSCF_ Response

Abort

Null

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ind

MAP_SS_INVOCATION_NOTIFY_cnf

MAP_ CLOSE_ req

Check_ Confirmation Provider Error, Data Error Set Negative response: System failure

OK Set Negative response: System failure

User Error

Note SS invocation negative response

Note SS invocation ack

Note SS invocation negative response

Null

Null

Null

3032
3033

Figure 22.12.2/1: Process Notify_SS_Invocation_MSC

2172

2173

process Note_SS_Invocation_gsmSCF
Process in the gsmSCF to handle a notification of supplementary service invocation

NSSI_SCF1(1)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the application process in the gsmSCF

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Null

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

MAP_SS_INVOCATION_NOTIFY_ind

MAP_ CLOSE_ req

Note SS invocation

Wait_For_ Application_ Response Null

Note SS invocation ack

Note SS invocation negative response

Set Result

Set User Error

MAP_SS_INVOCATION_NOTIFY_rsp MAP_CLOSE_req

Null

3034
3035

Figure 22.12.3/1: Process Note_SS_Invocation_gsmSCF

2174

2175

3036 3037

22.13 Activation of a CCBS request

22.13.1 General

3038 The message flow to activate a CCBS request is shown in figure 22.13.1/1. 3039 The following service is certainly used: 3040

MAP_REGISTER_CC_ENTRY

(defined in clause 11).

VLR

HLR

3041
3042 3043 3044 3045

1) 2)

MAP_REGISTER_CC_ENTRY_req/ind MAP_REGISTER_CC_ENTRY_rsp/cnf

3046

Figure 22.13.1/1: Message flow to activate a CCBS request

3047

22.13.2 Procedure in the VLR

3048 The MAP process in the VLR to activate a CCBS request is shown in figure 22.13.2/1. The MAP process invokes 3049 macros not defined in this clause; the definitions of these macros can be found as follows: 3050 3051

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3052

22.13.3 Procedure in the HLR

3053 The MAP process in the HLR to activate a CCBS request is shown in figure 22.13.2/1.

2176

2177

process Register_CC_Entry_VLR
Process in the VLR to request registration of a Call Completion entry in the HLR

RCCE_VLR1(1)
Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR

Null

CCBS request

MAP_OPEN_req MAP_REGISTER_CC_ENTRY_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Error

OK Wait_For_ Response_ From_HLR

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

MAP_REGISTER_CC_ENTRY_cnf

MAP CLOSE_ req Provider Error, Data Error Set Negative response: System failure Set Negative response: System failure

Check_ Confirmation

User Error

OK

Set Negative response

CCBS request negative response

CCBS request negative response

CCBS request negative response

CCBS request ack

Null

Null

Null

Null

3054
3055

Figure 22.13.2/1: Process Register_CC_Entry_VLR

2178

2179

process Register_CC_Entry_HLR
Process in the HLR to handle a request to register a Call Completion entry

RCCE_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093)

Null

MAP_REGISTER_CC_ENTRY_ind

CCBS request

Wait_For_ Application_ Response

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

CCBS request negative response

CCBS request ack

MAP_ CLOSE_ req

Ser User Error

Set Result

Abort

MAP_REGISTER_CC_ENTRY_rsp MAP_CLOSE_req

3056
3057

Figure 22.13.3/1: Process Register_CC_Entry_HLR

2180

2181

3058 3059

22.14 Deactivation of a CCBS request

22.14.1 General

3060 The message flow to deactivate a CCBS request is shown in figure 22.14.1/1. 3061 The following service is certainly used: 3062

MAP_ERASE_CC_ENTRY

(defined in clause 11).

VLR

HLR

3063
3064 3065 3066 3067

1) 2)

MAP_ERASE_CC_ENTRY_req/ind MAP_ERASE_CC_ENTRY_rsp/cnf

3068

Figure 22.14.1/1: Message flow to deactivate a CCBS request

3069

22.14.2 Procedure in the VLR

3070 The MAP process in the VLR to deactivate a CCBS request is shown in figure 22.14.2/1. The MAP process invokes 3071 macros not defined in this clause; the definitions of these macros can be found as follows: 3072 3073

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3074

22.14.3 Procedure in the HLR

3075 The MAP process in the HLR to deactivate a CCBS request is shown in figure 22.14.2/1.

2182

2183

process Erase_CC_Entry_VLR
Process in the VLR to request erasure of a Call Completion entry in the HLR

ECCE_VLR1(1)
Signals to/from the left are to/from the CCBS application process in the VLR (see 3GPP TS 23.093); signals to/from the right are to/from the HLR

Null

Deactivate CCBS

MAP_OPEN_req MAP_ERASE_CC_ENTRY_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Error

OK Wait_For_ Response_ From_HLR

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

MAP_ERASE_CC_ENTRY_cnf

MAP CLOSE_ req Provider Error, Data Error Set Negative response: System failure Set Negative response: System failure

Check_ Confirmation

User Error

OK

Set Negative response

Deactivate CCBS negative response

Deactivate CCBS negative response

Deactivate CCBS negative response

Deactivate CCBS ack

Null

Null

Null

Null

3076
3077

Figure 22.14.2/1: Process Erase_CC_Entry_VLR

2184

2185

process Erase_CC_Entry_HLR
Process in the HLR to handle a request to erase a Call Completion entry

ECCE_HLR1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the CCBS application process in the HLR (see 3GPP TS 23.093)

Null

MAP_ERASE_CC_ENTRY_ind

Deactivate CCBS

Wait_For_ Application_ Response

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Deactivate CCBS negative response

Deactivate CCBS ack

MAP_ CLOSE_ req

Ser User Error

Set Result

Abort

MAP_ERASE_CC_ENTRY_rsp MAP_CLOSE_req

3078
3079

Figure 22.14.3/1: Process Erase_CC_Entry_HLR

2186

2187

3080 3081

23

Short message service procedures

23.1 General

3082 The short message service procedures are used to control both mobile originated and mobile terminated short message 3083 transfer. 3084 Four procedures exist for short message services: 3085 3086 3087 3088

mobile originated short message service transfer; mobile terminated short message service transfer; short message alert procedure; short message delivery status report procedure.

3089 The following application context refers to a complex MAP user consisting of several processes: 3090

shortMessageGatewayContext.

3091 This application context needs a co-ordinating process in the HLR. Additionally a co-ordinating process needed for the 3092 mobile originated situation in the MSC, because the A_CM_SERV_REQ message does not distinguish between mobile 3093 originated short message transfer and the short message alert procedures. 3094 3095 3096

NOTE:

the A_CM_SERV_REQ message is not used for SMS over GPRS. The modelling is based on the assumption that the SGSN will trigger the appropriate process, according to whether an RP_MO_DATA or an RP_SM_MEMORY_AVAILABLE is received over the LLC layer.

3097 3098

23.1.1 Mobile originated short message service Co-ordinator for the MSC

3099 The process starts when the MSC receives an A_CM_SERV_REQ message (see 3GPP TS 24.008 [35]), with a CM 3100 service type indicating short message service, from the A-interface. The process invokes a macro not defined in this 3101 clause; the definition of this macro can be found as follows: 3102

Process_Access_Request_MSC

see subclause 25.4.1.

3103 If the macro Process_Access_Request_MSC takes the "OK" exit (which means that the MSC has sent an 3104 A_CM_SERVICE_ACCEPT to the MS), , the MS initiates mobile originated short message transfer or sends an 3105 indication that it has memory available for more short messages. 3106 The SMS Co-ordinator process in the MSC is shown in figure 23.1/1.

3107

23.1.2 Short message Gateway Co-ordinator for the HLR

3108 The process starts when the HLR receives a MAP_OPEN indication using when the application context 3109 shortMessageGatewayContext. The MAP process invokes a macro not defined in this clause; the definition of this 3110 macro can be found as follows: 3111

Receive_Open_Ind

see subclause 25.1.1.

3112 The SM Gateway Co-ordinator process in the HLR is shown in figure 23.1/2. 3113 If the Receive_Open_Ind macro takes the Vr exit then HLR shall perform the MAP dialogue as specified for the 3114 appropriate application context version. Depending on the subscriber data, handling at the MAP user application level 3115 may be performed as specified in subclauses 23.3.2 and 23.5.2 of the present document:

2188

2189

process Co_SMS_MSC
Co-ordinating process in the MSC for m obile ori ginated SMS activity

Co_SMS_MSC1(2)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise

Null

A_CM_ SERVICE_ REQUEST

Process_ Access_ Request_MSC

Error

OK Wait_For_ Service_ Primitive

Null

A_MM_ RELEASE_ ind

A_RP_MO_ DATA

A_RP_SM_ MEMORY_ AVAILABLE

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_req

MO_SM_ MSC

SM _Alert_ MSC

A_RP_MO_ DATA

To offspring

A_RP_SM_ MEMORY_ AVAILABLE

To offspring

Null

Relay_Info

Null

3116
3117

Figure 23.1/1 (sheet 1 of 2): Process Co_SMS_MSC

2190

2191

process Co_SMS_MSC
Co-ordinating process in the MSC for m obile ori ginated SMS activity Relay_Info

Co_SMS_MSC2(2)
In the upper subtree, signals to/from the left are to/from the MS; signals to/from the right are to/from the child process

A_MM_ RELEASE_ ind

A_DISC_ind

A_*

Null

Null

Relay_Info

Relay_Info

In the lower subtree, signals to/from the left are to/from the VLR; signals to/from the right are to/from the child process

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_U_ABORT_ind, MAP_CLOSE_i nd

Null

Relay_Info

Null

Relay_Info

3118
3119

Figure 23.1/1 (sheet 2 of 2): Process Co_SMS_MSC

2192

2193

process Co_SM_GW_HLR
Co-ordinating process in the HLR for SMS activity using the shortMsgGatewayContext

Co_SM_GW_HLR1(1)
Signals to/from the left are to/from the SM S-GM SC; signals to/from the right are to/from the child process

Null

Receive_ Open_Ind

Figure 25.1/1

Error

OK

Vr Perform Vr dialogue

Null

Wait_For_ Service_ Primitive

Null

MAP_SEND_ ROUTING_ INFO_FOR_ SM _ind

MAP_REPORT_SM DELIVERY_STATUS_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_i nd, MAP_CLOSE_i nd

MTSM_HLR

Report_SM_ Delivery_ Status_HLR

MAP_ CLOSE_req

MAP_SEND_ ROUTING_ INFO_FOR_ SM _ind

MAP_REPORT_SM DELIVERY_STATUS_ind

Null

Relay_Info

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

Null

Relay_Info

Null

Relay_Info

3120
3121

Figure 23.1/2: Process Co_SM_Gateway_HLR

2194

2195

3122 3123

23.2 The mobile originated short message transfer procedure

3124 The mobile originated short message service procedure is used to forward a short message from a mobile subscriber to a 3125 Service Centre. The message flow for the mobile originated short message service procedure is shown in figure 23.2/1.
MS Serving MSC or SGSN 1 3 4 4a 4b 5 7 8 6 2 VLR Interworking MSC SC

3126
3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3150 3151 3152

1) 2) 3) 4) 4a) 4b) 5) 6) 7) 8) (*) (**)

Short Message (3GPP TS 24.011 [37]). MAP_SEND_INFO_FOR_MO_SMS (*). MAP_SEND_INFO_FOR_MO_SMS_ACK (*). TCAP BEGIN (**) TCAP CONTINUE (**) MAP_MO_FORWARD_SHORT_MESSAGE. Short message (3GPP TS 23.040). Short message Acknowledgement (3GPP TS 23.040). MAP_MO_FORWARD_SHORT_MESSAGE_ACK. Short Message Acknowledgement (3GPP TS 24.011 [37]). Messages 2) and 3) are not used by the SGSN. If a) the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MO_FORWARD_SHORT_MESSAGE request in a single TC message and b) the Interworking MSC operator and the serving node (MSC or SGSN) operator agreed not to use the TCAP handshake countermeasure against SMS fraud for messages exchanged between their networks (see 3GPP TS 33.204 [34a]) then the TCAP handshake may be omitted.

3153

Figure 23.2/1: Mobile originated short message transfer

3154 In addition the following MAP services are used: 3155 3156

MAP_PROCESS_ACCESS_REQUEST MAP_AUTHENTICATE

(see subclause 8.3); (*) (see subclause 8.5); (*)

2196

2197

3157 3158 3159 3160 3161 3162 3163

MAP_SET_CIPHERING_MODE MAP_PROVIDE_IMSI MAP_CHECK_IMEI MAP_FORWARD_NEW_TMSI MAP_TRACE_SUBSCRIBER_ACTIVITY MAP_READY_FOR_SM (*) These services are not used by the SGSN.

(see subclause 8.6); (*) (see subclause 8.9); (*) (see subclause 8.7); (see subclause 8.9); (*) (see subclause 9.1); (*) (see subclause 12.4).

3164

23.2.1 Procedure in the serving MSC

3165 Any CAMEL-specific handling defined in this subclause is omitted if the MSC does not support CAMEL control of 3166 MO SMS, or if the subscriber does not have a subscription for CAMEL control of MO SMS. 3167 The process starts when the MSC receives a short message from the MS. The process invokes macros not defined in 3168 this clause; the definitions of these macros can be found as follows: 3169 3170 3171

Receive_Open_Cnf Check_Indication Check_Confirmation

see subclause 25.1.2; see subclause 25.2.1; see subclause 25.2.2.

3172 Sheet 1: If the MSC is integrated with the SMS-IWMSC, it communicates directly with the Short Message Service 3173 Centre (SMSC) using one of the protocols described in 3GPP TS 23.039 [25a]; otherwise it communicates with the 3174 SMS-IWMSC using MAP. 3175 Sheet 3: If the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the 3176 MAP_OPEN request and the content of the MAP_MO_FORWARD_SHORT_MESSAGE request in a single TC 3177 message, the test "Message segmentation needed" takes the "No" exit; otherwise the test takes the "Yes" exit. 3178 Sheet 3:The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between 3179 the serving MSC's operator and the SMS-IWMSC's operator (see 3GPP TS 33.204 [34a]). 3180 The mobile originated short message service process in the MSC is shown in figure 23.2/2.

3181

23.2.2 Procedure in the VLR

3182 Any CAMEL-specific handling defined in this subclause is omitted if the VLR does not support CAMEL control of 3183 MO SMS. 3184 The process starts when the VLR receives a dialogue opening request followed by a 3185 MAP_PROCESS_ACCESS_REQUEST including a CM service type Short Message Service. The process invokes 3186 macros not defined in this clause; the definitions of these macros can be found as follows: 3187 3188 3189

Receive_Open_Ind Check_Indication Process_Access_Request_VLR

see subclause 25.1.1; see subclause 25.2.1; see subclause 25.4.2.

3190 The mobile originated short message transfer process in the VLR is shown in figure 23.2/3.

2198

2199

3191

23.2.3 Procedure in the SGSN

3192 Any CAMEL-specific handling defined in this subclause is omitted if the SGSN does not support CAMEL control of 3193 MO SMS, or if the subscriber does not have a subscription for CAMEL control of MO SMS. 3194 The process starts when the SGSN receives a short message received from the MS over the Gb interface. The MAP 3195 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3196 3197

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3198 Sheet 2: If the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the 3199 MAP_OPEN request and the content of the MAP_MO_FORWARD_SHORT_MESSAGE request in a single TC 3200 message, the test "Message segmentation needed" takes the "No" exit; otherwise the test takes the "Yes" exit. 3201 Sheet 2:The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between 3202 the serving SGSN's operator and the SMS-IWMSC's operator (see 3GPP TS 33.204 [34a]). 3203 The mobile originated short message service process in the SGSN is shown in figure 23.2/4.

3204

23.2.4 Procedure in the SMS Interworking MSC (SMS-IWMSC)

3205 This procedure applies only when the SMS-IWMSC is not integrated with the serving MSC or SGSN. 3206 The process starts when the SMS-IWMSC receives a dialogue opening request with the application context 3207 shortMsgMO-RelayContext. The MAP process invokes macros not defined in this clause; the definitions of these 3208 macros can be found as follows: 3209 3210

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

3211 Sheet 1:The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between 3212 the SMS-IWMSC's operator and the serving node's operator (see 3GPP TS 33.204 [34a]). 3213 The mobile originated short message service transfer process in the SMS-IWMSC is shown in figure 23.2/5.

2200

2201

process MO_SM_MSC
Process in the M to handle MO SC short message submission

MO_SM_MSC1(4)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise

Null

A_RP_MO_DATA_ind

MAP_SEND_INFO_FOR_MO_SMS_req MAP_DELIMITER_req

Wait_For_ VLR_Response

MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_SEND_INFO_FOR_MO_SMS_cnf

Check_ Confirmation

OK CAMEL_O_ SM S_ FAILURE Yes See 3GPP TS 23.078 MSC= IWMSC? No

User Error

Data Error CAMEL_O_ SM S_ FAILURE See 3GPP TS 23.078

Set RP_ERROR: Network out of order

SC_RP_MO_ DATA_req

CAMEL_O_ SM S_ FAILURE To SMSC

See 3GPP TS 23.078

Set RP_ERROR

Set RP_ERROR: Network out of order

A_RP_ ERROR_ req

A_RP_ ERROR_ req

Wait_For_ Confirm_ From_SC

3214
3215

Figure 23.2/2 (sheet 1 of 4): Process MO_SM_MSC

2202

2203

process MO_SM_MSC
Process in the M to handle MO SC short message submission Wait_For_ VLR_Response

MO_SM_MSC2(4)
Signals to/from the left are to/from the MS; Signals to/from the right are to/from the VLR

MAP_CONTINUE_CAMEL_SMS_HANDLING_ind

Check_ Indication

OK CAMEL_ O_SMS_ INIT

Error

See 3GPP TS 23.078

Result?

SM S_Aborted

Release_SM S Set RP_ERROR according to gsmSCF instructions

Redirect_SMS Modify data according to gsmSCF instructions

Continue Set RP_ERROR: Network out of order

A_RP_ ERROR_ req

A_RP_ ERROR_ req

MAP_U_ ABORT_ req

MAP_U_ ABORT_ req

MAP_SEND_INFO_FOR_MO_SMS_req MAP_DELIMITER_req

MAP_U_ ABORT_ req

Wait_For_ VLR_Response

3216
3217

Figure 23.2/2 (sheet 2 of 4): Process MO_SM_MSC

2204

2205

process MO_SM_MSC
Process in the MSC to handle MO short message submission 1

MO_SM_MSC3(4)
Signals to/from the left are to/from the MS; Signals to/from the right are to/from the IWMSC Yes

No no TCAP Handshake required yes

Message segmentation needed?

MAP_OPEN_req MAP_DELIMITER_req MAP_OPEN_req MAP_MO_FORWARD_SHORT_MESSAGE_req MAP_DELIMITER_req

Receive_ Open_Cnf

Receive_ Open_Cnf

OK

Vr Perform MAP Vr dialogue

Error

Error

Vr Perform MAP Vr dialogue

OK

CAMEL_O_ SMS_ FAILURE

See 3GPP TS 23.078

Set RP_ERROR: Network out of order

MAP_MO_FORWARD_ SHORT_MESSAGE_req MAP_DELIMITER_req

A_RP_ ERROR_req

Wait_For_ MO_SMS_ Result

Wait_For_ MO_SMS_ Result

MAP_MO_FORWARD_SHORT_MESSAGE_cnf

No Check_ Confirmation Provider Error, User Error, Data Error CAMEL_O_ SMS_ FAILURE Submission successful?

Yes

OK CAMEL_O_ SMS_ SUBMITTED See 3GPP TS 23.078

See 3GPP TS 23.078

CAMEL_O_ SMS_ SUBMITTED

See 3GPP TS 23.078

Set RP_ERROR

A_RP_ ACK_req

A_RP_ ERROR_req

A_RP_ ACK_req

3218
3219

Figure 23.2/2 (sheet 3 of 4): Process MO_SM_MSC

2206

2207

process MO_SM_MSC
Process in the M to handle MO SC short message submission Wait_For_ Confirm_ From_SC

MO_SM_MSC4(4)
In the upper subtree, signals to/from the left are to/from the MS; Signals to/from the right are to/from the SM SC SC_RP_ ACK_ind

SC_RP_ ERROR_ind

SC_ABORT_ ind

CAMEL_O_ SM S_FAILURE

See 3GPP TS 23.078

CAMEL_O_ SM S_FAILURE

See 3GPP TS 23.078

CAMEL_O_ SM S_ SUBMITTED

See 3GPP TS 23.078

Set RP_ERROR

Set RP_ERROR: Network out of order

A_RP_ ERROR_ req

A_RP_ACK_ ind

Wait_For_ MO_SMS_ RESULT

In the lower subtree, signals to/from the left are to/from the MS; Signals to/from the right are to/from the IWMSC

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ CLOSE_ req

CAMEL_O_ SM S_FAILURE

See 3GPP TS 23.078

Set RP_ERROR: Network out of order

A_RP_ ERROR_ req

3220
3221

Figure 23.2/2 (sheet 4 of 4): Process MO_SM_MSC

2208

2209

process MO_SM_VLR
Process in the VLR to handle a request for inform ation to handle MO short message submission

MO_SM_VLR1(2)
Signals to/from the left are to/from the MSC

Null

Receive_ Open_Ind

Vr, Error

OK Wait_For_ Service_ Primitive

Process_ Access_ Request_VLR

Error

OK Wait_For_ Info_Request

Null

3222
3223

Figure 23.2/3 (sheet 1 of 2): Process MOSM_VLR

2210

2211

process MO_SM_VLR
Process in the VLR to handle a request for inform ation to handle MO short message submission Wait_For_ Info_Request

MO_SM_VLR2(2)
Signals to/from the left are to/from the MSC

MAP_U_ ABORT_ req

MAP_SEND_INFO_FOR_MO_SMS_ind

Null

Check_ Indication

OK No MO SM S provisioned?

Error

Set User Error: Teleservice not provi sioned

Yes Operator barring? No BAOC

Yes SS barring? No BAOC

Set User Error: Call barred (Operator barring)

Set User Error: Call barred (barring service active)

CAMEL_ MO_SMS_VLR

See 3GPP TS 23.078

Fail Result? Pass Yes Operator barring? No Yes SS barring? Set User Error: Call barred (Operator barring) Set User Error: Call barred (barring service active) No BOIC or BOIC-exHC BOIC or BOIC-exHC etc

Null

MAP_SEND_INFO_FOR_MO_SMS_rsp MAP_CLOSE_req

Null

3224
3225

Figure 23.2/3 (sheet 2 of 2): Process MO_SM_VLR

2212

2213

process MO_SM_SGSN
Process in the SGSN to handle submission of a short message

MO_SM_SGSN1(3)
Signals to/from the left are to/from the UE; signals to/from the right are to/from the HLR

Null

Gb_RP_ MO_DATA_ ind

No CAMEL_O_ SM S_FAILURE See 3GPP TS 23.078 MO SM S provisioned? Yes Yes Operator barring? No 2 Yes SS barring? No Set RP_ERROR: Operator determ ined barring Set RP_ERROR: Call barred CAMEL_O_ SM S_INIT See 3GPP TS 23.078 BAOC BAOC

Gb_RP_ ERROR_ req

Result?

SM S_Aborted

Release_SM S

Redirect_SMS Modify data according to gsmSCF instructions Yes

Continue

Operator barring? No 1

BOIC or BOIC-exHC etc

Set RP_ERROR according to gsmSCF instructions

Yes BOIC or BOIC-exHC SS barring? No CAMEL_O_ SM S_FAILURE See 3GPP TS 23.078

Set RP_ERROR: Requested facility not subscribed

Gb_RP_ ERROR_ req

Gb_RP_ ERROR_ req

Null

Null

Null

3226
3227

Figure 23.2/4 (sheet 1 of 3): Process MO_SM_SGSN

2214

2215

process MO_SM_SGSN
Process in the SGSN to handle submission of a short message No 3

MO_SM_SGSN2(3)
Signals to/from the left are to/from the UE; signals to/from the right are to/from the HLR

Message segmentation needed?

Yes

no

TCAP Handshake required

yes MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf

MAP_OPEN_req MAP_MO_FORWARD_SHORT_MESSAGE_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK

Vr Perform MAP_Vr dialogue

Error

Error

Vr Perform MAP_Vr dialogue

OK

CAMEL_O_ SMS_ FAILURE

See 3GPP TS 23.078

Set RP_ERROR: Network out of order

MAP_MO_FORWARD_ SHORT_MESSAGE_req MAP_DELIMITER_req

Gb_RP_ ERROR_req

Wait_For_ MO_SMS_ Result

Null

Wait_For_ MO_SMS_ Result

MAP_MO_FORWARD_SHORT_MESSAGE_cnf

No Check_ Confirmation Provider Error, User Error, Data Error CAMEL_O_ SMS_ FAILURE Submission successful?

Yes

OK CAMEL_O_ SMS_ SUBMITTED See 3GPP TS 23.078

See 3GPP TS 23.078

CAMEL_O_ SMS_ SUBMITTED

See 3GPP TS 23.078

Set RP_ERROR

Gb_RP_ ACK_req

Gb_RP_ ERROR_req

Gb_RP_ ACK_req

Null

Null

Null

3228
3229

Figure 23.2/4 (sheet 2 of 3): Process MO_SM_SGSN

2216

2217

process MO_SM_SGSN
Process in the SGSN to handle submission of a short message Wait_For_ MO_SMS_ Result

MO_SM_SGSN3(3)
Signals to/from the left are to/from the UE; signals to/from the right are to/from the HLR

MAP_NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_i nd

MAP_CLOSE_ req

CAMEL_O_ SM S_ FAILURE

See 3GPP TS 23.078

Set RP_ERROR: Network out of order

Gb_RP_ ERROR_req

Null

3230
3231

Figure 23.2/4 (sheet 3 of 3): Process MO_SM_SGSN

2218

2219

process MO_SM_IWMSC
Process in the MSC to handle MO short message submission

MO_SM_IWMSC1(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the SMSC Null

Receive_ Open_Ind Vr Perform MAP Vr dialogue OK Null Error

Null no

TCAP Handshake required yes

Wait_For_ Service_ Primitive

Wait_For_ DELIMITER

MAP_ DELIMITER_ ind

MAP_ DELIMITER_ ind

MAP_MO_FORW ARD_ SHORT_MESSAGE_ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ DELIMITER_ req

MAP_ DELIMITER_ req

Set Error System Failure

MAP_ CLOSE_ req

Wait_For_ Service_ Primitive

Wait_For_ Service_ Primitive

MAP_MO_ FORW ARD_ SM_rsp

Null

MAP_ CLOSE_ req

Null

3232
3233 3234

Figure 23.2/5 (sheet 1 of 2): Process MO_SM_IWMSC

2220

2221

process MO_SM_IWMSC
Process in the MSC to handle MO short message submission

MO_SM_IWMSC2(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the SMSC

Wait_For_ Service_ Primitive

MAP_MO_FORW ARD_ SHORT_MESSAGE_ind

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Indication OK Error SC known? No Yes SC_RP_ MO_DATA_ req Set User Error: SM delivery failure Set error parameter: Unknown service centre 1

MAP_ CLOSE_ req

Null

Wait_For_ Confirm_ From_SC

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

SC_RP_ ACK_ind

SC_RP_ ERROR_ind

MAP_ CLOSE_ req

Set User Error: SM delivery failure

Set error parameter: according to service centre error value

SC_ ABORT_ req

MAP_MO_FORW ARD_ SHORT_MESSAGE_rsp

Null

Null

3235
3236

Figure 23.2/5 (sheet 2 of 2): Process MO_SM_IWMSC

2222

2223

3237 3238

23.3 The mobile terminated short message transfer procedure

3239 The mobile terminated short message transfer procedure is used for forwarding a short message or several short 3240 messages from a Service Centre to a mobile subscriber. The message flow for the mobile terminated short message 3241 procedure for a single short message transfer is shown in figure 23.3/1.
MS Serving MSC or SGSN VLR HLR Gateway MSC SC

2 3

4a 4b 5 5a 5b 7 8 11 12 6 9 10 13

14

3242
3243

Figure 23.3/1: Mobile terminated short message service procedures

2224

2225

3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3272 3273 3274 3275 3276 3277

1) 2) 3) 4) 4a) 4b) 5) 5a) 5b) 6) 7) 8) 9) 10) 11) 12) 13) 14) (*) (**) (***)

Short Message (3GPP TS 23.040). MAP_SEND_ROUTING_INFO_FOR_SM. MAP_SEND_ROUTING_INFO_FOR_SM_ACK. TCAP BEGIN (***) TCAP CONTINUE (***) MAP_MT_FORWARD_SHORT_MESSAGE. MAP_SEND_INFO_FOR_MT_SMS (*). MAP_CONTINUE_CAMEL_SMS_HANDLING (*)(**) MAP_SEND_INFO_FOR_MT_SMS (*)(**) MAP_PAGE/MAP_SEARCH_FOR_MOBILE_SUBSCRIBER (*). Page (3GPP TS 24.008 [35]). Page response (3GPP TS 24.008 [35]). MAP_PROCESS_ACCESS_REQUEST_ACK and MAP_SEARCH_FOR_MOBILE_SUBSCRIBER_ACK (*). MAP_SEND_INFO_FOR_MT_SMS_ACK (*). Short Message (3GPP TS 24.011 [37]). Short Message Acknowledgement (3GPP TS 24.011 [37]). MAP_MT_FORWARD_SHORT_MESSAGE_ACK. Short Message Acknowledgement (3GPP TS 23.040). Messages 5), 5a), 5b), 6), 9), and 10) are not used by the SGSN. These messages are used only for a subscriber provisioned with MT-SMS-CSI in the VLR. If a) - the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MT_FORWARD_SHORT_MESSAGE request in a single TC message, and b) the SMS Gateway MSC operator and the serving node (MSC or SGSN) operator agreed not to use the TCAP handshake countermeasure against SMS fraud for messages exchanged between their networks (see 3GPP TS 33.204 [34a]) then the TCAP handshake may be omitted.

3278

2226

2227

3279 The message flow for the mobile terminated short message procedure for multiple short message transfer is shown in 3280 figure 23.3/2.
MS Serving MSC or SGSN VLR HLR Gateway MSC SC

2 3

4a 4b 5 5a 5b 7 8 11 12 6 9 10 13

14 15

17 18

16 19

20

3281
3282
3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 2228

Figure 23.3/2: Mobile terminated short message procedure for multiple short message transfer
1) 2) 3) 4) 4a 4b) 5) 5a) 5b) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) Short Message (3GPP TS 23.040). MAP_SEND_ROUTING_INFO_FOR_SM. MAP_SEND_ROUTING_INFO_FOR_SM_ACK. TCAP BEGIN (***) TCAP CONTINUE (***) MAP_MT_FORWARD_SHORT_MESSAGE (note 1). MAP_SEND_INFO_FOR_MT_SMS (*). MAP_CONTINUE_CAMEL_SMS_HANDLING (*)(**) MAP_SEND_INFO_FOR_MT_SMS (*)(**) MAP_PAGE/MAP_SEARCH_FOR_MOBILE_SUBSCRIBER (*). Page (3GPP TS 48.008 [49]). Page response (3GPP TS 24.008 [35]). MAP_PROCESS_ACCESS_REQUEST_ACK and MAP_SEARCH_FOR_MOBILE_SUBSCRIBER_ACK (*). MAP_SEND_INFO_FOR_MT_SMS_ACK (*). Short Message (3GPP TS 24.011 [37]). Short Message Acknowledgement (3GPP TS 24.011 [37]). MAP_MT_FORWARD_SHORT_MESSAGE_ACK. Short Message Acknowledgement (3GPP TS 23.040). Short Message (3GPP TS 23.040).

2229

3324 In the multiple short message transfer the service MAP_MT_FORWARD_SHORT_MESSAGE can be used several 3325 times. However, the short message transfer is always acknowledged to the Service Centre before the next short message 3326 is sent. 3327 In addition the following MAP services are used: 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339

3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323

16) 17) 18) 19) 20) (*) (**) (***)

MAP_MT_FORWARD_SHORT_MESSAGE (note 2). Short Message (3GPP TS 24.011 [37]). Short Message Acknowledgement (3GPP TS 24.011 [37]). MAP_MT_FORWARD_SHORT_MESSAGE_ACK. Short Message Acknowledgement (3GPP TS 23.040). Messages 5), 5a), 5b) 6), 9), and 10) are not used by the SGSN. These messages are used only for a subscriber provisioned with MT-SMS-CSI in the VLR. If a) the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MT_FORWARD_SHORT_MESSAGE request in a single TC message, and b) the SMS Gateway MSC operator and the serving node (MSC or SGSN) operator agreed not to use the TCAP handshake countermeasure against SMS fraud for messages exchanged between their networks (see 3GPP TS 33.204 [34a]) then the TCAP handshake may be omitted.

NOTE 1: The More Messages To Send flag is TRUE. NOTE 2: The More Messages To Send flag is FALSE.

MAP_PROCESS_ACCESS_REQUEST MAP_PAGE MAP_SEARCH_FOR_MS MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI MAP_FORWARD_NEW_TMSI MAP_REPORT_SM_DELIVERY_STATUS MAP_INFORM_SERVICE_CENTRE MAP_TRACE_SUBSCRIBER_ACTIVITY MAP_READY_FOR_SM (*) These services are not used by the SGSN.

(see subclause 8.3); (*) (see subclause 8.2); (*) (see subclause 8.2); (*) (see subclause 8.5); (*) (see subclause 8.6); (*) (see subclause 8.7); (see subclause 8.9); (*) (see subclause 12.3); (see subclause 12.6); (see subclause 9.1); (*) (see subclause 12.4).

3340

23.3.1 Procedure in the SMS-GMSC

3341 Any CAMEL-specific handling described in this subclause is omitted if the SMS-GMSC does not support CAMEL. 3342 CAMEL-specific handling is invoked only if the SMS-GMSC is integrated with the VMSC. 3343 The process starts when the SMS-GMSC receives an SC_RP_MT_DATA indication from a Service Centre. The MAP 3344 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3345 3346 3347 3348 3349 3350
2230

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

Process MT_SM_GMSC sheet 1: If the MAP_SEND_ROUTING_INFO_FOR_SM confirmation included an LMSI, it may be included in the sm-RP-DA information field of the first MAP_MT_FORWARD_SHORT_MESSAGE request sent to the serving MSC. In this case, the IMSI shall be included in the Destination Reference of the MAP_OPEN request. The SMS-GMSC shall not send an LMSI to an SGSN. If the SMS-GMSC does not send an LMSI to the

2231

3351 serving node, the sm-RP-DA information field in the first MAP_MT_FORWARD_SHORT_MESSAGE request sent to 3352 the serving MSC or SGSN shall contain the IMSI, and the Destination Reference in the MAP_OPEN request shall not 3353 be present. The parameter SM_RP_OA shall contain the Service Centre address. 3354 3355 3356 3357

Process MT_SM_GMSC sheet 1: The indication of which number belongs to the SGSN and which to the MSC, received from the HLR in the MAP_SEND_ROUTING_INFO_FOR_SM confirm (see subclause 23.3.2) will enable the SMS-GMSC to map the causes received from one or both serving nodes into the appropriate causes for non GPRS, GPRS or both, and send them to the SC and the HLR.

3358 Process MT_SM_GMSC sheet 2: The SMS-GMSC maps "Unexpected data value" and "System failure" MAP errors 3359 from the serving node to a "System failure" RP_ERROR error cause. The mapping between other MAP error causes 3360 and the RP_ERROR error cause is given in 3GPP TS 23.040 [26] and 3GPP TS 24.011 [37]. 3361 Process MT_SM_GMSC sheet 2: If the SMS-GMSC receives both MSC and SGSN numbers from the HLR as routeing 3362 information, it may choose which serving node to use for the first delivery attempt. 3363 Process MT_SM_GMSC sheet 2: If the SMS-GMSC makes two delivery attempts, it may report the result of each 3364 delivery attempt to the HLR according to the conditions described below. 3365 Procedure MT_SM_Delivery_Attempt_GMSC sheet 1: if the macro MT_SM_Transfer_MSC takes the Error exit, the 3366 SMS-GMSC maps the MAP User Error to the corresponding SC_RP error, as defined in 3GPP TS 23.040 [26]. 3367 Procedure MT_SM_Delivery_Attempt_GMSC sheet 3: The decision box "TCAP Handshake required" takes the "yes" 3368 or "no" exit depending on agreements between the GMSC's operator and the serving node's operator (see 3GPP TS 3369 33.204 [34a]).

Procedure MT_SM_Delivery_Attempt_GMSC sheet 1, sheet 2, sheet 4, sheet 5: The SMS-GMSC invokes the macro Report_SM_Delivery_Stat_GMSC if:
3370 3371 3372 3373 3374 3375 3376 3377 3378 3379

the reason received from the serving node for failure to deliver the message is absent subscriber_SM, unidentified subscriber or SM delivery failure with error cause "MS memory capacity exceeded", and the SC address is not yet included in the MWD set, or the reason received from the serving node for failure to deliver the message is absent subscriber_SM, unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded, and the corresponding flag in the HLR (as indicated in the information received in the MAP_INFORM_ SERVICE_CENTRE) is not set, or the reason received from the serving node (MSC or SGSN) for failure to deliver the message is absent subscriber_SM and the absent subscriber diagnostic is different from the absent subscriber diagnostic received in the MAP_INFORM_ SERVICE_CENTRE.

Procedure MT_SM_Delivery_Attempt_GMSC sheet 1, sheet 2, sheet 4, sheet 5: If absent subscriber diagnostic information (see 3GPP TS 23.040 [26]) is included with the absent subscriber_SM error indication then the SMSGMSC relays this information to the HLR using the MAP_REPORT_SM_DELIVERY_STATUS service.
3380 Procedure MT_SM_Delivery_Attempt_GMSC sheet 1, sheet 4: The More Messages To Send flag is set to TRUE or 3381 FALSE according to the information received from the Service Centre. 3382 3383 3384 3385

Procedure MT_SM_Delivery_Attempt_GMSC sheet 3: If the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MT_FORWARD_SHORT_MESSAGE request in a single TC message, the test "Message segmentation needed" takes the "No" exit; otherwise the test takes the "Yes" exit.

3386 The mobile terminated short message transfer process in the SMS-GMSC is shown in figure 23.3/3. The procedure 3387 MT_SM_Delivery_Attempt_GMSC is shown in figure 23.3/4. The macro MT_SM_Transfer_MSC is shown in 3388 figure 23.3/7.

2232

2233

3389

23.3.2 Procedure in the HLR

3390 The process starts when the HLR receives a MAP_SEND_ROUTING_INFO_FOR_SM indication from the SMS3391 GMSC. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as 3392 follows: 3393 3394 3395 3396 3397 3398 3399 3400

Check_Indication

see subclause 25.2.1.

Sheet 3: If the SMS-GMSC does not support GPRS functionality, it uses the protocol defined in the Release 96 version of this specification. The parameter "msc-Number" in "RoutingInfoForSM-Res" in the Release 96 version of the protocol definition corresponds to the parameter "networkNode-Number" in "RoutingInfoForSM-Res" in the Release 97 (and later) version of the protocol definition; therefore if the HLR populates the parameter "networkNode-Number" with the SGSN number, the Release 96 SMS-GMSC will interpret the SGSN number as an MSC number. If the HLR populates the "gprsNodeIndicator" parameter in the MAP_SEND_ROUTING_INFO_FOR_SM response, a Release 96 SMS-GMSC will silently discard the parameter.

3401 Sheet 5: If the HLR received a LMSI from the VLR at location updating, it shall include the LMSI in the 3402 MAP_SEND_ROUTING_INFO_FOR_SM response only if the MAP_SEND_ROUTING_INFO_FOR_SM response 3403 also includes the MSC number. 3404 The mobile terminated short message transfer process in the HLR is shown in figure 23.3/5.

3405

23.3.3 Procedure in the Serving MSC

3406 Any CAMEL-specific handling defined in this subclause is omitted if the MSC does not support CAMEL control of 3407 MT SMS, or if the subscriber does not have a subscription for CAMEL control of MT SMS. 3408 The process starts when the MSC receives a dialogue opening request with the application context shortMsgMT3409 RelayContext. The MAP process invokes macros not defined in this clause; the definitions of these macros can be 3410 found as follows: 3411 3412

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

3413 The mobile terminated short message transfer process in the serving MSC is shown in figure 23.3/6 3414 Procedure MT_SM_VMSC sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit 3415 depending on agreements between the Serving MSC's operator and the SMS Gateway MSC's operator (see 3GPP TS 3416 33.204 [34a]). 3417 The macro MT_SM_Transfer_MSC may be invoked either in a stand-alone serving MSC or in a serving MSC which is 3418 integrated with the SMS-GMSC. It is used to transfer the first MT short message of a possible sequence of messages. 3419 The macro invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3420 3421 3422 3423 3424

Check_Confirmation Page_MSC Search_for_MS_MSC Process_Access_Request_MSC

see subclause 25.2.2. see subclause 25.3.1; see subclause 25.3.2; see subclause 25.4.1;

Trace_Subscriber_Activity_MSC see subclause 25.9.1.

3425 The macro MT_SM_Transfer_MSC is shown in figure 23.3/7. The macro Check_Subscr_Identity_For_MT_SMS is 3426 shown in figure 23.3/8.

2234

2235

3427

23.3.4 Procedure in the VLR

3428 Any CAMEL-specific handling defined in this subclause is omitted if the VLR does not support CAMEL control of MT 3429 SMS. 3430 The process starts when the VLR receives a dialogue opening request from the MSC. The process invokes macros not 3431 defined in this clause; the definitions of these macros can be found as follows: 3432 3433 3434 3435

Receive_Open_Ind Check_Indication Check_Confirmation Process_Access_Request_VLR

see subclause 25.1.1; see subclause 25.2.1; see subclause 25.2.2; see subclause 25.4.2.

3436 The mobile terminated short message transfer process in the VLR is shown in figure 23.3/9.

3437

23.3.5 Procedure in the SGSN

3438 Any CAMEL-specific handling defined in this subclause is omitted if the SGSN does not support CAMEL control of 3439 MT SMS, or if the subscriber does not have a subscription for CAMEL control of MT SMS. 3440 The process starts when the SGSN receives a dialogue opening request with the application context shortMsgMT3441 RelayContext. The MAP process invokes macros not defined in this clause; the definitions of these macros can be 3442 found as follows: 3443 3444

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

3445 The mobile terminated short message transfer process in the SGSN is shown in figure 23.3/10. 3446 Procedure MT_SM_SGSN sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit 3447 depending on agreements between the Serving SGSN's operator and the SMS Gateway MSC's operator (see 3GPP TS 3448 33.204 [34a]). 3449 The macro MT_SM_Transfer_SGSN is used to transfer the first MT short message of a possible sequence of messages. 3450 It is shown in figure 23.3/11. 3451 The macro Check_Subscr_Identity_For_MT_SMS is shown in figure 23.3/8. The page and search procedures are 3452 shown in figures 23.3/12 and 23.3/13.

2236

2237

Process MT_SM_GMSC
Process in the SMS-GMSC to handle delivery of an MT short message

MT_SM_GMSC1(2)
Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the HLR

Null

SC_RP_MT_ DATA_ind

MAP_OPEN_req MAP_SEND_ROUTING_INFO_FOR_SM_req MAP_DELIMITER_req

Receive_ Open_Cnf

V1 Perform_ MAP_V1_ Dialogue

OK Wait_For_ Routeing_Info

Error

SC_ABORT_ ind

MAP_SEND_ ROUTING_ INFO_FOR_ SM _cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_U_ ABORT_req

MAP_CLOSE_ req

Null

Check_ Confirmation

OK LMSI included in routing i nfo? Yes Set destination reference: not included No

User Error

Provider Error, Data Error

Set RP_CAUSE: System Failure

Set destination reference: IMSI

Set RP_CAUSE

SC_RP_ ERROR_req

Set SM_RP_DA: LMSI

Set SM_RP_DA: IMSI

Null

Wait_For_ INFORM_SC

3453
3454

Figure 23.3/3 (sheet 1 of 2): Process MT_SM_GMSC

2238

2239

Process MT_SM_GMSC
Process in the SMS-GMSC to handle delivery of an MT short message Wait_For_ INFORM_SC

MT_SM_GMSC2(2)
Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the HLR

MAP_ CLOSE_ ind

MAP_INFORM_ SERVICE_ Centre_ind

MAP_ NOTICE_ ind

SC_ABORT_ ind

Check_ Indication

MAP_ CLOSE_ req

MAP_U_ ABORT_req

OK No Error from HLR? Yes

Error

Null

Set RP_IMSI; Set RP_M SISDN Routing info recei ved? Yes SC_RP_ ERROR_req No

MT_SM_ Delivery_ Attempt_ GMSC Fail Result? Pass, Abort No Second routing address provided? Yes MT_SM_ Delivery_ Attempt_ GMSC

Null

Null

3455
3456

Figure 23.3/3 (sheet 2 of 2): Process MT_SM_GMSC

2240

2241

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcom e Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the BSS No Serving node =GM SC? Yes

MTSMDA1(8)

MT_SM_ Transfer_MSC

Abort 2 False Camel Handling True CAMEL_ T_SM S_ FAILURE False

OK

Release SMS

Error

False Camel Handling True CAMEL_ T_SM S_ DELIVERED Camel Handling True CAMEL_ T_SM S_ FAILURE

See TS 23.078

See TS 23.078

See TS 23.078

Yes Result:= Fail

More messages to send? No

Else Error? Unidentified Subscriber Absent Subscriber, MS Mem ory Capacity Exceeded

SC_RP_ ACK_req

Wait_For_More_ Messages_ Local_Delivery

Set UE: Absent Subscriber

SC_RP_MT_ DATA_ind

MWD already set? Yes False No

No

Camel Handling True CAMEL_ T_SM S_ INIT

MCEF or MNRF set in HLR? Yes Report_SM_ Delivery_ Stat_GMSC OK, Error

Yes

Failure cause= indication from HLR? No Report_SM_ Delivery_ Stat_GMSC OK, Error Set RP_ERROR

See TS 23.078

Release_SM S Result? Continue SC_ABORT_ req A_RP_MT_ DATA_req SC_RP_ ACK_req SC_RP_ ERROR_req

Result:= Abort

Result:= Pass

Result:= Fail

Wait_For_ Subsequent_ A_SM_CONFIRM

3457
3458

Figure 23.3/4 (sheet 1 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2242

2243

3459

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcom e Wait_For_ Subsequent_ A_SM_CONFIRM

MTSMDA2(8)

Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the BSS

A_RP_ ERROR_ind

A_RP_ ACK_ind

False Camel Handling True

False Camel Handling True

CAMEL_ T_SM S_ FAILURE

See TS 23.078

CAMEL_ T_SM S_ DELIVERED

See TS 23.078

Else Error? MS Memory Capacity Exceeded MWD already set? Yes No 2

Yes

Failure cause= indication from HLR? No

Report_SM_ Delivery_ Stat_GMSC OK, Error

SC_ABORT_ req

Result:= Abort

3460
3461

Figure 23.3/4 (sheet 2 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2244

2245

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome 1

MTSMDA3(8)
Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN)

No

Message segmenting needed?

Yes

No

TCAP Handshake required

Yes

MAP_OPEN_req MAP_MT_FORWARD_SHORT_MESSAGE_req MAP_DELIMITER_req

MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf

Receive_ Open_Cnf

Error Set RP_ERROR: System Failure

Vr Perform MAP Vr Dialogue

OK

Error Set RP_ERROR: System Failure

Vr Perform MAP Vr Dialogue

OK MAP_MT_FORWARD_ SHORT_MESSAGE_req MAP_DELIMITER_req

SC_RP_ ERROR_req No Successful delivery? Yes

SC_RP_ ERROR_req No Successful delivery? Yes

Result:= Fail

Result:= Pass

Result:= Fail

Result:= Pass

Wait_For_ First_MT_ SMS_Confirm

Wait_For_ First_MT_ SMS_Confirm

3462
3463

Figure 23.3/4 (sheet 3 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2246

2247

3464

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcom e Wait_For_ First_M T_ SM S_Confirm

MTSMDA4(8)
Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise

MAP_MT_FORWARD_SHORT_MESSAGE_cnf

Check_ Confirmation

OK Yes More messages to send? No No Else MCEF or MNRF set in HLR? Yes Report_SM_ Delivery_ Stat_GMSC OK, Error

User Error

Provider Error, Data Error Error?

Unidentified Subscriber Set UE: Absent Subscriber

Absent Subscriber, MS Memory Capacity Exceeded

Set RP_ERROR MWD already set? Yes No

SC_RP_ ACK_req

SC_RP_ ACK_req Yes Failure cause from VMSC=indication from HLR? No

SC_RP_ ERROR_req

Wait_For_More_ Messages_ Remote_Delivery

Result:= Pass

Result:= Fail

SC_RP_MT_ DATA_ind

Report_SM_ Delivery_ Stat_GMSC OK, Error

MAP_MT_FORWARD_ SHORT_MESSAGE_req MAP_DELIMITER_req

Set RP_ERROR

Wait_For_ Subsequent_ MT_SMS_ Confirm

SC_RP_ ERROR_req

Result:= Fail

3465
3466

Figure 23.3/4 (sheet 4 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2248

2249

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcom e Wait_For_ Subsequent_ MT_SMS_ Confirm

MTSMDA5(8)
Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN)

MAP_MT_FORWARD_SHORT_MESSAGE_cnf

Check_ Confirmation Provider Error, Data Error

OK Else 3

User Error

Error? MS Memory Capacity Exceeded MWD already set? Yes No

SC_ABORT_ req

Result:= Abort

Yes

Failure cause from VMSC=indication from HLR? No

Report_SM_ Delivery_ Stat_GMSC OK, Error

SC_ABORT_ req

Result:= Abort

3467
3468

Figure 23.3/4 (sheet 5 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2250

2251

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcome

MTSMDA6(8)

Wait_For_Fir st_A_SM_CONFIRM, Wait_For_Subsequent_A_SM_CONFIRM

Signals to/fr om the left ar e to/from the short message service centre; signals to/fr om the right ar e to/from the serving node (VMSC or SGSN) unless shown otherwise

SC_ABORT_ ind

False Camel Handling True CAMEL_ T_SMS_ FAILURE

See TS 23.078

A_ABORT_req

To BSS

Result:= Abort

Wait_For_ First_A_SM_ CONFIRM

Wait_For_ Subsequent_ A_SM_CONFIRM

A_ABORT_ ind

From BSS

A_ABORT_ ind

From BSS

False Camel Handling True CAMEL_ T_SMS_ FAILURE

False Camel Handling True CAMEL_ T_SMS_ FAILURE

See TS 23.078

See TS 23.078

Set RP_ERROR: System Failur e

SC_RP_ ERROR_req

SC_ ABORT_req

Result:= Fail

Result:= Abort

3469
3470

Figure 23.3/4 (sheet 6 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2252

2253

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcom e Wait_For_First_MT_SMS_Confirm, Wait_For_Subsequent_MT_SMS_Confirm

MTSMDA7(8)

Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise

SC_ABORT_ ind

MAP_U_ ABORT_ind

Result:= Abort

Wait_For_ First_M T_ SM S_Confirm

Wait_For_ Subsequent_ MT_SMS_ Confirm

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ind

MAP_ CLOSE_req

MAP_ CLOSE_req

Set RP_ERROR: System Failure

SC_RP_ ERROR_req

SC_ ABORT_req

Result:= Fail

Result:= Abort

3471
3472

Figure 23.3/4 (sheet 7 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2254

2255

Procedure MT_SM_Delivery_Attempt_GMSC
Procedure in the SMS-GMSC to attempt MT SM delivery and report the outcom e Wait_For_More_ Messages_ Local_Delivery

MTSMDA8(8)
Signals to/from the left are to/from the short message service centre; signals to/from the right are to/from the serving node (VMSC or SGSN) unless shown otherwise

SC_ABORT_ ind

A_ABORT_ ind

From BSS

False Camel Handling True CAMEL_ T_SM S_ FAILURE

False Camel Handling True CAMEL_ T_SM S_ FAILURE

See TS 23.078

See TS 23.078

A_ABORT_req

To BSS

SC_ ABORT_req

Result:= Abort

Result:= Abort

Wait_For_More_ Messages_ Remote_Delivery

SC_ABORT_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ NOTICE_ind

MAP_ CLOSE_req

MAP_U_ ABORT_ind

SC_ ABORT_req

Result:= Abort

Result:= Abort

3473
3474

Figure 23.3/4 (sheet 8 of 8): Procedure MT_SM_Delivery_Attempt_GMSC

2256

2257

process MT_SM_HLR
Process in the HLR ro provide routeing information for MT SM S

MT_SM_HLR1(5)
Signals to/from the left are to/from the SM S-GM SC

Null

MAP_SEND_ROUTING_INFO_FOR_SM_ind

Check_ Indication

Error MAP_SEND_ROUTING_INFO_FOR_SM_rsp MAP_CLOSE_req

OK No Subscriber known? Yes Set User Error: Unknown subscriber

No MT SMS provi sioned? Set User Error: Teleservice not provisioned

Yes SM filtering by HPLM N? No Set User Error: Call barred Network access mode? Set Barring cause: Unauthorised message originator

Non-GPRS

GPRS

Non-GPRS & GPRS

3475
3476

Figure 23.3/5 (sheet 1 of 5): Process MT_SM_HLR

2258

2259

process MT_SM_HLR
Process in the HLR ro provide routeing information for MT SM S 2 NAM=Non-GPRS

MT_SM_HLR2(5)

MS reachable in MSC? Yes

No

No

MSC supports MT SMS? Yes

Set User Error: Facility not supported Yes

Operator barring? No Set User Error: Call barred Set Barring cause: Operator barring Yes SS barring? No

Set User Error: Call barred

Set Barring cause: Barring service active

Yes MNRF set? No Set MNRF

Retrieve routeing information

False SM -RP priority? True

11

Retrieve routeing information

Set MW status

Set User Error: Absent subscriber

10

3477
3478

Figure 23.3/5 (sheet 2 of 5): Process MT_SM_HLR

2260

2261

process MT_SM_HLR
Process in the HLR ro provide routeing information for MT SM S 3 NAM=GPRS

MT_SM_HLR3(5)

MS reachable in SGSN? Yes

No

No

SGSN supports MT SMS? Yes

Set User Error: Facility not supported Yes

Operator barring? No Set User Error: Call barred Set Barring cause: Operator barring Yes SS barring? No

Set User Error: Call barred

Set Barring cause: Barring service active

Yes MNRG set? No Set MNRG

Retrieve routeing information

False SM -RP priority? True

11

Retrieve routeing information

Set MW status

Set User Error: Absent subscriber

10

3479
3480

Figure 23.3/5 (sheet 3 of 5): Process MT_SM_HLR

2262

2263

process MT_SM_HLR
Process in the HLR ro provide routeing information for MT SM S 4 NAM=Non-GPRS & GPRS

MT_SM_HLR4(5)

SM S-GM SC supports GPRS? Yes No MS reachable in MSC?

No

MSC Yes

Preferred delivery node

SGSN

MS reachable in SGSN? No

Yes

Yes

MS reachable in SGSN? No

No 7 No SGSN supports MT SMS? Yes

MSC supports MT SMS? Yes SGSN supports MT SMS? Yes Yes Operator barring? No 5

Set User Error: Facility not supported

No Set User Error: Call barred Set Barring cause: Operator barring

Set MNRF; Set MNRG SS barring? No

Yes

Set User Error: Call barred Yes MNRF set? Yes MNRG set? No Yes MNRG set? False SM -RP priority? Set User Error: Absent subscriber True Set MSC address; Set SGSN address True SM -RP priority? False Set SGSN address SM -RP priority? True Set MSC address; Set SGSN address False No No

Set Barring cause: Barring service active

Set MSC address

Set MSC address; Set SGSN address

Retrieve routeing information 9 Set MW status 11

10

3481
3482

Figure 23.3/5 (sheet 4 of 5): Process MT_SM_HLR

2264

2265

process MT_SM_HLR
Process in the HLR ro provide routeing information for MT SM S

MT_SM_HLR5(5)
Signals to the left are to the SMS-GMSC

10

11

MAP_SEND_ROUTING_ INFO_FOR_SM _rsp

MAP_SEND_ROUTING_ INFO_FOR_SM _rsp

MAP_SEND_ROUTING_ INFO_FOR_SM_rsp

SC address in MWD list? No

Yes

Yes

SC address in MWD list? No

Yes MCEF set? No

Update MWD list

MWD update failed? Yes

No

MWD status:= SC address not included

MWD status:= SC address included

MWD status:= SC address not included

Yes Set MW status

MSISDN= MSISDN Alert? No

MSISDN= MSISDN Alert? No

Yes Set MSISDN Alert

Set MSISDN Alert

MAP_INFORM _SERVICE_ CENTRE_req

MAP_INFORM_SERVICE_CENTRE_req MAP_CLOSE_req

MAP_ CLOSE_ req

3483
3484

Figure 23.3/5 (sheet 5 of 5): Process MT_SM_HLR

2266

2267

Process MT_SM_VMSC
The mobile terminated short message service process in the VMSC

MT_SM_VMSC1(4)
Signals to/from the left are to/from the SMS-GMSC

Null

Receive_ Open_Ind

Figure 25.1/1

Vr Perform MAP Vr Dialogue Yes

OK Destination Reference received No

Error

Null

Store Destination Reference

Null

No

TCAP Handshake required Yes

Wait_For_ Service_ Primitive

Wait_For_ DELIMITER

MAP_ DELIMITER_ ind

MAP_MT_ FORW _SM_ ind

MAP_ DELIMITER_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ DELIMITER_ req

Set Error System Failure

MAP_ DELIMITER_ req

MAP_ CLOSE_ req

Wait_For_ Service_ Primitive

MAP_MT_ FORW _SM_ rsp

Wait_For_ Service_ Primitive

Null

MAP_ CLOSE_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ CLOSE_ req

Null

Null

3485
3486

Figure 23.3/6 (sheet 1 of 4): Procedure MT_SM_VMSC

2268

2269

Process MT_SM_VMSC
The mobile term inated short m essage service process in the VMSC Wait_For_ Service_ Primitive

MT_SM_VMSC2(4)
Signals to/from the left are to/from the SM S-GM SC

MAP_MT_FORWARD_SHORT_MESSAGE_ind

Check_ Indication

Figure 25.2/1

OK MT_SM_ Transfer _MSC

Error

Figure 23.3/4

OK

Abort

Error

Release SMS

False CAMEL Handling True CAMEL Handling True

False CAMEL Handling True

False

CAMEL_ T_SM S_ DELIVERED

See TS 23.078

CAMEL_ T_SM S_ FAILURE

See TS 23.078

CAMEL_ T_SM S_ FAILURE

See TS 23.078

Null

More messages to send? Yes

No

MAP_MT_FORWARD_SHORT_MESSAGE_rsp MAP_DELIMITER_req

MAP_MT_FORWARD_SHORT_M ESSAGE_rsp MAP_CLOSE_req

Wait_For_ More_ Messages

Null

3487
3488

Figure 23.3/6 (sheet 2 of 4): Procedure MT_SM_VMSC

2270

2271

Process MT_SM_VMSC
The mobile term inated short m essage service process in the VMSC

Wait_For_ More_ Messages

MT_SM_VMSC3(4)

Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS Check_ Indication

MAP_MT_FORWARD_SHORT_MESSAGE_ind

Error

OK False CAMEL Handling True CAMEL_ T_SM S_ INIT

See TS 23.078

Release_SM S Result? Set Error according to gsmSCF instructions

Continue

A_RP_ MT_DATA_ req

Wait_For_ Subsequent_ A_SM_CONFIRM

A_RP_ ERROR_ind

A_RP_ ACK_ind

False Set User Error CAMEL Handling True False CAMEL Handling True CAMEL_ T_SM S_ FAILURE No More messages to send? Yes CAMEL_ T_SM S_ DELIVERED

See TS 23.078

See TS 23.078

MAP_MT_FORWARD_SHORT_MESSAGE_rsp MAP_CLOSE_req

MAP_MT_FORWARD_SHORT_M ESSAGE_rsp MAP_DELIMITER_req

Null

Wait_For_ More_ Messages

3489
3490

Figure 23.3/6 (sheet 3 of 4): Procedure MT_SM_VMSC

2272

2273

Process MT_SM_VMSC
The mobil e term inated short m essage service process in the VMSC Wait_For_ More_ Messages

MT_SM_VMSC4(4)
Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS

MAP_U_ABORT_ind MAP_P_ABORT_ind

MAP_ NOTICE_ ind

A_MM_ RELEASE

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

A_ABORT_ req

A_ABORT_ req

Null

Wait_For_ Subsequent_ A_SM_CONFIRM

MAP_U_ABORT_ind MAP_P_ABORT_ind

MAP_ NOTICE_ ind

A_MM_ RELEASE

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

A_ABORT_ req

A_ABORT_ req

False CAMEL Handling True CAMEL_ T_SM S_ FAILURE

See TS 23.078

Null

3491
3492

Figure 23.3/6 (sheet 4 of 4): Procedure MT_SM_VMSC

2274

2275

Macrodefinition MT_SM_Transfer_MSC
The mobile term inated short m essage transfer macro in the M SC

MT_SM_Xfer_MSC1(4)

Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

MSC supports MT SMS?

Yes Check_Subscr_ Identity_for_ MT_SMS

No Set User Error: Facility Not Supported

OK MAP_OPEN_req MAP_SEND_INFO_FOR_MT_SMS_req MAP_DELIMITER_req

Error

Error

Receive_ Open_ Cnf

Figure 25.1/2

OK CAMEL Handling:= False

Vr, Error Set User Error: System Failure

Wait_For_ Page

Error

Page_MSC

Figure 25.3/1

Search_for_ MS_MSC

Figure 25.3/2

MAP_SEND_ INFO_FOR_ MT_SMS_cnf

Null

Error

OK

OK

Null

Error

Set User Error: System Failure

Set User Error: System Failure

Set User Error

Error

Wait_For_ VLR_Response

Error

Wait_For_ VLR_Response

Error

No

MS supports SM S?

Yes

Set User Error: SM Delivery Failure

Delivery failure cause:= Equipment not SM equipped

Process_ Access_ Request_MSC

Figure 25.4/1

Error MAP_U_ ABORT_req

OK

A_ABORT_ req

Set User Error: System Failure

Error

Wait_For_ VLR_Response

3493
3494

Figure 23.3/7 (sheet 1 of 4): Macro MT_SM_Transfer_MSC

2276

2277

Macrodefinition MT_SM_Transfer_MSC
The mobile term inated short m essage transfer macro in the M SC Wait_For_ Page

MT_SM_Xfer_MSC2(4)
Signals to/from the right are to/from the VLR

MAP_CONTINUE_CAMEL_SMS_HANDLING_ind

CAMEL Handling:= True

CAMEL_ T_SM S_ INIT

See TS 23.078

Release_SM S Result? Continue

Set Suppress MT-SMS-CSI

MAP_U_ ABORT_ req

MAP_SEND_INFO_FOR_MT_SMS_req

Release SM S

Wait_For_ Page

3495
3496

Figure 23.3/7 (sheet 2 of 4): Macro MT_SM_Transfer_MSC

2278

2279

Macrodefinition MT_SM_Transfer_MSC
The mobil e term inated short m essage transfer macro in the M SC Wait_For_ VLR_Response

MT_SM_Xfer_MSC3(4)

Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

Figure 25.9/1

Trace_ Subcriber_ Activity_MSC

MAP_SEND_INFO_FOR_MT_SMS_cnf

Wait_For_ VLR_Response

Check_ Confirmation

OK A_RP_ MT_DATA_ req

Provider Error, Data Error Set User Error: System Failure

User Error For Absent Subscriber, User Error includes diagnostic indication

Set User Error

Wait_For_ First_A_SM _ CONFIRM

Error

A_RP_ ACK_ind

A_RP_ ERROR_ ind

Set User Error

OK

Error

3497
3498

Figure 23.3/7 (sheet 3 of 4): Macro MT_SM_Transfer_MSC

2280

2281

Macrodefinition MT_SM_Transfer_MSC
The mobile term inated short m essage transfer macro in the M SC Wait_For_Page, Wait_For_VLR_Response, Wait_For_First_A_SM_CONFIRM

MT_SM_Xfer_MSC4(4)
In the upper subtree: Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

A_MM_ RELEASE_ ind

MAP_U_ABORT_ind MAP_CLOSE_i nd

MAP_U_ ABORT_ req

A_ ABORT_ Req

Set User Error: System Failure

Error

Wait_For_Page, Wait_For_VLR_Response, Wait_For_First_A_SM_CONFIRM

In the lower subtree: Signals to/from the left are to/from the MS; signals to/from the right are to/from the SM S-GM SC unless marked otherwise

MAP_ NOTICE_ ind

MAP_U_ABORT_ind MAP_P_ABORT_ind MAP_CLOSE_i nd

MAP_ CLOSE_ req

MAP_U_ ABORT_ Req

To VLR

A_ ABORT_ Req

Abort

3499
3500

Figure 23.3/7 (sheet 4 of 4): Macro MT_SM_Transfer_MSC

2282

2283

macrodefinition Check_Subscr_Identity_for_MT_SMS
Macro to check the identity of a subscriber for MT SMS; invoked in the VMSC and the SGSN

CSIFMTSMS1(1)

No Destination reference present? Yes

No SM _RP_DA= IMSI? Yes

No SM _RP_DA= LMSI? Yes

Destination reference:= Not included

Destination reference:= IMSI

SM _RP_DA:= IMSI

Set User Error: Unexpected data value

SM _RP_DA:= LMSI

OK

Error

OK

3501
3502

Figure 23.3/8: Macro Check_Subscr_Identity_For_MT_SMS

2284

2285

process MT_SM_VLR
Process in the VLR to handle a request for inform ation to handle MT short message delivery

MT_SM_VLR1(3)
Signals to/from the left are to/from the MSC

Null

Receive_ Open_Ind

OK Wait_For_ Service_ Primitive

Vr, Error

Null

MAP_SEND_INFO_FOR_MT_SMS_ind

Check_ Indication OK No Subscriber known? Yes

Error

No Confirmed by HLR? Yes

Set User Error: Unidentified subscriber

MAP_SEND_INFO_FOR_MT_SM S_rsp MAP_CLOSE_req

Null

3503
3504

Figure 23.3/9 (sheet 1 of 3): Process MT_SM_VLR

2286

2287

process MT_SM_VLR
Process in the VLR to handle a request for inform ation to handle MT short message delivery 1

MT_SM_VLR2(3)
Signals to/from the left are to/from the MSC

Yes IM detached? SI No

No Roaming in LA allowed? Yes

CAMEL_MT_ SM S_VLR

See 3GPP TS 23.078

Set User Error: Absent subscriber

Set diagnostic: IMSI detached

Fail Result? Pass Set MNRF

No Null LAI known? Yes

MAP_SEND_INFO_ FOR_MT_SMS_rsp MAP_CLOSE_req

No Confirmed by radio contact? Yes Null

MAP_SEARCH_FOR_MS_req MAP_DELIMITER_req

MAP_PAGE_req MAP_DELIMITER_req

Wait_For_ Access_ Request

3505
3506

Figure 23.3/9 (sheet 2 of 3): Process MT_SM_VLR

2288

2289

process MT_SM_VLR
Process in the VLR to handle a request for inform ation to handle MT short message delivery Wait_For_ Access_ Request

MT_SM_VLR3(3)
Signals to/from the left are to/from the MSC

Process_ Access_ Request_VLR

MAP_U_ ABORT_ ind

MAP_ PAGE_cnf

MAP_SEARCH_FOR_MS_cnf

Error

OK Set subscriber data Check_ Confirmation

Null

Null

User Error User error= absent subscriber? Yes No

OK

Provider Error, Data Error

Update LAI

Set diagnostic: No response to paging

Ser User Error: Absent subscriber

Set User Error

Confirmed by Radio Contact:= Confirmed

Null

Set MNRF

Wait_For_ Access_ Request

MAP_SEND_INFO_FOR_MT_SMS_rsp MAP_CLOSE_req

Null

3507
3508

Figure 23.3/9 (sheet 3 of 3): Process MT_SM_VLR

2290

2291

Process MT_SM_SGSN
The mobile terminated short message service process in the SGSN

MT_SM_SGSN1(4)
Signals to/from the left are to/from the SMS-GMSC

Null

Receive_ Open_Ind

Figure 25.1/1

Vr Perform MAP Vr Dialogue See the relevant version of GSM 09.02 or TS 29.002 Yes

OK Destination Reference received

Error

Null

Store Destination Reference

Null

No

No

TCAP Handshake required Yes

Wait_For_ Service_ Primitive

Wait_For_ DELIMITER

MAP_ DELIMITER _ind

MAP_MT_ FORW _SW_ ind

MAP_ DELIMITER _ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE _ind

MAP_ DELIMITER _req

Set Error System Failure

MAP_ DELIMITER _req

MAP_ CLOSE _req

Wait_For_ Service_ Primitive

MAP_MT_ FORW _SM_ rsp

Wait_For_ Service_ Primitive

Null

MAP_ CLOSE_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE _ind

MAP_ CLOSE _req

Null

Null

3509
3510

Figure 23.3/10 (sheet 1 of 4): Process MT_SM_SGSN

2292

2293

Process MT_SM_SGSN
The mobile term inated short m essage service process in the SGSN Wait_For_ Service_ Primitive

MT_SM_SGSN2(4)
Signals to/from the left are to/from the SM S-GM SC

MAP_MT_FORWARD_SHORT_MESSAGE_ind

Check_ Indication

Figure 25.2/1

OK MT_SM_ Transfer _SGSN

Error

Figure 23.3/4

OK False CAMEL Handling True CAMEL Handling True

Abort False

Error False CAMEL Handling True

Release SMS

CAMEL_ T_SM S_ DELIVERED

See TS 23.078

CAMEL_ T_SM S_ FAILURE

See TS 23.078

CAMEL_ T_SM S_ FAILURE

See TS 23.078

Null

More messages to send? Yes

No

MAP_MT_FORWARD_SHORT_MESSAGE_rsp MAP_DELIMITER_req

MAP_MT_FORWARD_SHORT_M ESSAGE_rsp MAP_CLOSE_req

Wait_For_ More_ Messages

Null

3511
3512

Figure 23.3/10 (sheet 2 of 4): Process MT_SM_ SGSN

2294

2295

Process MT_SM_SGSN
The mobil e term inated short m essage service process in the SGSN

Wait_For_ More_ Messages

MT_SM_SGSN3(4)
Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS MAP_MT_FORWARD_SHORT_MESSAGE_ind

Check_ Indication

Figure 25.2/1

Error

OK False CAMEL Handling True CAMEL_ T_SM S_ INIT

See TS 23.078

Release_SM S Result? Set Error according to gsmSCF instructions

Continue

Gb_RP_ MT_DATA_ req

Wait_For_ Subsequent_ Gb_SM_CONFIRM

Gb_RP_ ERROR_ind

Gb_RP_ ACK_ind

False Set User Error CAMEL Handling True False CAMEL Handling True CAMEL_ T_SM S_ FAILURE No More messages to send? Yes MAP_MT_FORWARD_SHORT_MESSAGE_rsp MAP_CLOSE_req MAP_MT_FORWARD_SHORT_MESSAGE_rsp MAP_DELIMITER_req CAMEL_ T_SM S_ DELIVERED

See TS 23.078

See TS 23.078

Null

Wait_For_ More_ Messages

3513
3514

Figure 23.3/10 (sheet 3 of 4): Process MT_SM_ SGSN

2296

2297

Process MT_SM_SGSN
The mobil e term inated short m essage service process in the SGSN Wait_For_ More_ Messages

MT_SM_SGSN4(4)
Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS

MAP_U_ABORT_ind MAP_P_ABORT_ind

MAP_ NOTICE_ ind

Gb_LLC_ RELEASE_ ind

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

Gb_LLC_ RELEASE_ req

Gb_LLC_ RELEASE_ req

NULL

Wait_For_ Subsequent_ Gb_SM_CONFIRM

MAP_U_ABORT_ind MAP_P_ABORT_ind

MAP_ NOTICE_ ind

Gb_LLC_ RELEASE_ ind

MAP_ CLOSE_ req

MAP_U_ ABORT_ req

Gb_LLC_ RELEASE_ req

Gb_LLC_ RELEASE_ req

False CAMEL Handling True CAMEL_ T_SM S_ FAILURE

See TS 23.078

NULL

3515
3516

Figure 23.3/10 (sheet 4 of 4): Process MT_SM_ SGSN

2298

2299

Macrodefinition MT_SM_Transfer_SGSN
The mobile term inated short m essage transfer macro in the SGSN

MT_SM_Xfer_SGSN1(3)

SGSN supports MT SMS?

Yes Check_Subscr_ Identity_for_ MT_SMS

No Set User Error: Facility Not Supported

OK No Subscriber known? Yes No Confirmed by HLR? Yes Yes GPRS detached flag=Detached? No RA Not Allowed flag=Not allowed? No Set User Error: Absent subscriber Yes Set User Error: Unidentified Subscriber

Error

See TS 23.078

CAMEL_MT_ SM S_SGSN

Diagnostic= GPRS detached

Continue Result? CAMEL Handling CAMEL Handling:= False CAMEL Handling:= True Set MNRG

See TS 23.078

CAMEL_T_ SM S_INIT

Release_SM S Result? Continue Set User Error according to gsmSCF instructions

Release SMS

3517
3518

Figure 23.3/11 (sheet 1 of 3): Macro MT_SM_TRANSFER_SGSN

2300

2301

Macrodefinition MT_SM_Transfer_SGSN
The mobile term inated short m essage transfer macro in the SGSN 1

MT_SM_Xfer_SGSN2(3)

Signals to/from the right are to/from the MS

Confirmed by radio contact

Not confirmed

Confirmed No RAI known? Yes

Page_SMS_ SGSN

Search_SMS_ SGSN

Fail Result Pass

Pass Result Fail 2

Else 2 Error Absent Subscriber

No

MS supports SMS? Yes

Set User Error

Set User Error: Absent Subscriber

Diagnostic=No response to paging

Gb_LLC_ RELEASE_ req

Gb_RP_ MT_DATA_ req

Set MNRG

Wait_For_ First_ Gb_SM _Confirm

Error

Gb_RP_ACK_ ind

Gb_RP_ ERROR_ind

Set User Error: SM delivery failure

Delivery failure cause:= Equipment not SM equipped

Set User Error

Error

OK

Error

3519
3520

Figure 23.3/11 (sheet 2 of 3): Macro MT_SM_TRANSFER_SGSN

2302

2303

Macrodefinition MT_SM_Transfer_SGSN
The mobile term inated short m essage transfer macro in the SGSN Wait_For_ First_ Gb_SM _Confirm

MT_SM_Xfer_SGSN3(3)
Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MS

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

Gb_LLC_ RELEASE_ ind

MAP_ CLOSE_req

Gb_LLC_ RELEASE_ req

Set User Error: System fai lure

Abort

Error

3521
3522

Figure 23.3/11 (sheet 3 of 3): Macro MT_SM_TRANSFER_SGSN

2304

2305

Procedure Page_SMS_SGSN
Procedure in the SGSN to page an MS for M SMS delivery T

Page_SMS_SGSN1(1)
Signals to/from the right are to/from the MS

MS connection exists? No

Yes

In specified routeing area

Gb_PAGE_ REQUEST

Result:= Pass

Wait_For_ Page_Response

Gb_PAGE_ RESPONSE

Gb_NO_PAGE_ RESPONSE

Error:= Absent subscriber

Result:= Pass

Result:= Fail

3523
3524

Figure 23.3/12 (sheet 1 of 1): Procedure Page_SMS_SGSN

2306

2307

Procedure Search_SMS_SGSN
Procedure in the SGSN to search for an MS for MT SMS delivery

Search_SMS_SGSN1(1)
Signals to/from the right are to/from the MS

MS connection exists? No

Yes

In all routeing areas

Gb_PAGE_ REQUEST

Result:= Pass

Wait_For_ Search_Response

Gb_PAGE_ RESPONSE

Gb_NO_PAGE_ RESPONSE

Update LAI

Error:= Absent subscriber

Result:= Pass

Result:= Fail

3525
3526

Figure 23.3/13 (sheet 1 of 1): Procedure Search_SMS_SGSN

2308

2309

3527

23.4 The Short Message Alert procedure

3528 The Short Message Alert procedure is used to alert the Service Centre when the mobile subscriber is active after a short 3529 message transfer has failed because the mobile subscriber is not reachable, or when the MS has indicated that it has 3530 memory capacity to accept a short message. 3531 The message flow for the Short Message Alert procedure for the case when the mobile subscriber was not reachable is 3532 shown in figure 23.4/1.
MS Serving MSC or SGSN 1 2 4 VLR HLR Interworking MSC SC

5 5 5 7 7 7

6 6 6

3533
3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548

1) 2) 3)

CM Service Request (**), Page response or Location Updating (3GPP TS 24.008 [35]). MAP_PROCESS_ACCESS_REQUEST / MAP_UPDATE_LOCATION_AREA (**). MAP_READY_FOR_SM (Mobile Present) / MAP_UPDATE_LOCATION / Supplementary Service Control Request (*). 4) MAP_READY_FOR_SM_ACK (*). 5) MAP_ALERT_SERVICE_CENTRE (notes 1 and 2). 6) Alert Service Centre (3GPP TS 23.040). 7) MAP_ALERT_SERVICE_CENTRE_ACK. NOTE 1: To all Service Centres in the Message Waiting List. NOTE 2: The HLR initiates the MAP_ALERT_SERVICE_CENTRE service only if the MS Memory Capacity Exceeded flag is clear. (*) For GPRS, messages 3) and 4) are sent/received by the SGSN. (**) These messages are not used by the SGSN.

3549

Figure 23.4/1: Short message alert procedure (Mobile is present)

3550 The message flow for the Short Message Alert procedure for the case where the MS indicates that it has memory 3551 capacity to accept one or more short messages is shown in figure 23.4/2.

2310

2311

MS

Serving MSC or SGSN 1 2

VLR

HLR

Interworking MSC

SC

3 4

7 7 7 9 9 9

8 8 8

3552
3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566

1) 2) 3) 4) 5) 6) 7) 8) 9) NOTE: (*) (**)

SM memory capacity available ( 3GPP TS 24.011 [37]). MAP_READY_FOR_SM (Memory Available) (*). MAP_READY_FOR_SM (Memory Available) (**). MAP_READY_FOR_SM_ACK (**). MAP_READY_FOR_SM_ACK (*). SM memory capacity available (Acknowledge) (3GPP TS 24.011 [37]). MAP_ALERT_SERVICE_CENTRE (note). Alert Service Centre (3GPP TS 23.040). MAP_ALERT_SERVICE_CENTRE_ACK. To all Service Centres in the Message Waiting List. Messages 2) and 5) are not used by the SGSN. For GPRS, messages 3) and 4) are sent/received by the SGSN.

3567

Figure 23.4/2: Short message alert procedure (MS memory capacity available)

3568 In addition the following MAP services are used in the MS memory available case: 3569 3570 3571 3572 3573 3574 3575 3576

MAP_PROCESS_ACCESS_REQUEST MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_PROVIDE_IMSI MAP_CHECK_IMEI MAP_FORWARD_NEW_TMSI MAP_TRACE_SUBSCRIBER_ACTIVITY (*) These services are not used by the SGSN.

(see subclause 8.3); (*) (see subclause 8.5); (*) (see subclause 8.6); (*) (see subclause 8.9); (*) (see subclause 8.7); (see subclause 8.9); (*) (see subclause 9.1). (*)

3577 The Short Message Alert procedure when the MS indicates successful transfer after polling is shown in figure 23.4/3.

2312

2313

Gateway MSC 1 2

HLR

Interworking MSC

SC

3 3 3 5 5 5

4 4 4

3578
3579 3580 3581 3582 3583 3584 3585 3586

1) 2) 3) 4) 5) NOTE:

MAP_REPORT_SM_DELIVERY_STATUS (Successful Transfer). MAP_REPORT_SM_DELIVERY_STATUS_ACK. MAP_ALERT_SERVICE_CENTRE (note). Alert Service Centre (3GPP TS 23.040). MAP_ALERT_SERVICE_CENTRE_ACK. To all Service Centres in the Message Waiting List.

3587

Figure 23.4/3: Short message alert procedure (Successful transfer after polling)

3588 3589

23.4.1 Procedure in the Serving MSC the MS has memory available

3590 The process starts when the MSC receives a notification from the MS that it has memory available. The process invokes 3591 a macro not defined in this clause; the definition of this macro can be found as follows: 3592

Check_Confirmation

see subclause 25.2.2.

3593 The short message alert process in the MSC for the MS memory capacity available case is shown in figure 23.4/4.

3594 3595 23.4.2.1

3596 3597 3598 3599 3600 3601

23.4.2 Procedures in the VLR

The Mobile Subscriber is present

If the VLR successfully handles a MAP_PROCESS_ACCESS_REQUEST indication or a MAP_UPDATE_LOCATION_AREA indication while the MS Not Reachable Flag (MNRF) is set, the VLR sends a MAP_READY_FOR_SM request to the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for non GPRS. If authentication fails during the handling of a MAP_PROCESS_ACCESS_REQUEST indication or a MAP_UPDATE_LOCATION_AREA indication, the VLR shall not send a MAP_READY_FOR_SM request to the HLR. The process in the VLR is described in detail in subclause 25.10.1.

3602 23.4.2.2

The MS has memory available

3603 The process starts when the VLR receives dialogue opening request followed by a 3604 MAP_PROCESS_ACCESS_REQUEST indication including a CM service type Short Message Service. The MAP 3605 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3606

Receive_Open_Ind

see subclause 25.1.1;

2314

2315

3607 3608 3609

Receive_Open_Cnf Check_Indication Check_Confirmation

see subclause 25.1.2; see subclause 25.2.1; see subclause 25.2.2.

3610 The short message alert process in the VLR for the MS memory capacity available case is shown in figure 23.4/5.

3611 3612 23.4.3.1

3613 3614 3615 3616 3617

23.4.3 Procedures in the SGSN

The Mobile Subscriber is present

If the SGSN successfully handles a Page response, Attach request or Routing Area Update request message (3GPP TS 24.008 [35]), while the MS Not Reachable for GPRS (MNRG) flag is set, the SGSN sends a MAP_READY_FOR_SM request to the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. If authentication fails during the handling of a Page response, Attach request or Routing Area Update request, the SGSN shall not send a MAP_READY_FOR_SM request to the HLR

3618 The process in the SGSN is described in detail in subclause 25.10.23.

3619 23.4.3.2

The Mobile Equipment has memory available

3620 The process starts when the SGSN receives an RP_SM_MEMORY_AVAILABLE indication from the MS. The MAP 3621 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3622 3623

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3624 The short message alert procedure in the SGSN for the MS memory capacity available case is shown in figure 23.4/6.

3625

23.4.4 Procedure in the HLR

3626 The process starts when the HLR receives a dialogue opening request using the application context mwdMngtContext. 3627 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3628 3629 3630

Receive_Open_Ind Check_Indication Alert_Service_Centre_HLR

see subclause 25.1.1; see subclause 25.2.1; see subclause 25.10.3.

3631 Sheet 1: If the dialogue opening request is from an SGSN, version 2 and version 1 of the application context are not 3632 applicable. 3633 The short message alert process in the HLR is shown in figure 23.4/7.

3634

23.4.5 Procedure in the SMS Interworking MSC

3635 The process starts when the SMS-IWMSC receives a dialogue opening request using the application context 3636 shortMsgAlertContext. The MAP process invokes macros not defined in this clause; the definitions of these macros can 3637 be found as follows: 3638 3639

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

3640 The short message alert process in the SMS-IWMSC is shown in figure 23.4/8.

2316

2317

process SM_Alert_MSC
Process in the M to forward SC a notification that the MS has m emory available to store short m essages

SMA_MSC1(1)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

Null

A_RP_SM _MEMORY_AVAILABLE_ind

MAP_READY_FOR_SM_req MAP_DELIMITER_req

Wait_For_ VLR_Response

A_MM_ Release_ ind

MAP_READY_ FOR_SM_cnf

MAP_U_ABORT_ind, MAP_CLOSE_i nd

Check_ Confirmation User Error, Provider Error, Data Error Set RP_ERROR Set RP_ERROR: Network out of order

OK

MAP_U_ ABORT_ req

A_RP_ ACK_ req

A_RP_ ERROR_ req

A_RP_ ERROR_ req

3641
3642

Figure 23.4/4: Procedure SM_Alert_MSC

2318

2319

process SM_Alert_VLR
Process in the VLR to forward a notification that the MS has m emory available to store short m essages

SMA_VLR1(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR; Null

Receive_ Open_Ind

Error, Vr

OK Wait_For_ Service_ Primitive

Process_ Access_ Request_VLR

Error

OK Wait_For_ Ready_ For_SM

Null

MAP_READY_FOR_SM_ind

Check_ Indication OK Error Set Ready for SM Reason: Memory available for non-GPRS

MAP_OPEN_req MAP_READY_FOR_SM_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error Set User Error: System Failure

V1 Set User Error: Facility not supported

Vr

OK

Perform MAP Vr dialogue

Wait_For_ HLR_Response

MAP_READY_FOR_SM_rsp MAP_CLOSE_req

Null

Null

3643
3644

Figure 23.4/5 (sheet 1 of 2): Procedure SM_Alert_VLR

2320

2321

process SM_Alert_VLR
Process in the VLR to forward a notification that the MS has m emory available to store short m essages Wait_For_ HLR_Response

SMA_VLR2(2)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR;

MAP_READY_FOR_SM_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_i nd, MAP_CLOSE_i nd

Check_ Confirmation User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK

Set User Error

Set User Error: System fai lure

MAP_READY_FOR_SM_rsp MAP_CLOSE_req

Null

3645
3646

Figure 23.4/5 (sheet 2 of 2): Procedure SM_Alert_VLR

2322

2323

process SM_Alert_SGSN
Process in the SGSN to forward a notification that the MS has m emory available to store short m essages

SMA_SGSN1(2)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the HLR

Null

Gb_RP_SM_MEM ORY_AVAILABLE_ind

Set Ready for SM Reason: Memory available for GPRS

MAP_OPEN_req MAP_READY_FOR_SM_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error Set RP_ERROR: Network out of order

Vr Set RP_ERROR: Facility not supportedr

OK

Wait_For_ HLR_Response

Gb_RP_ ERROR_ req

Null

3647
3648

Figure 23.4/6 (sheet 1 of 2): Process SM_Alert_SGSN

2324

2325

process SM_Alert_SGSN
Process in the SGSN to forward a notification that the MS has m emory available to store short m essages Wait_For_ HLR_Response

SMA_SGSN2(2)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the HLR

Gb_LLC_ RELEASE_ ind

MAP_READY_FOR_SM_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_U_ ABORT_ req

Check_ Confirmation User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK

Set RP_ERROR

Set RP_ERROR: Network out of order

Gb_RP_ ACK_ req

Gb_RP_ ERROR_ req

Gb_RP_ ERROR_ req

Null

Null

Null

Null

3649
3650

Figure 23.4/6 (sheet 2 of 2): Process SM_Alert_SGSN

2326

2327

process SM_Alert_HLR
Process in the HLR to handle a notification that the MS is ready to receive short messages

SMA_HLR1(2)
Signals to/from the left are to/from the VLR or the SGSN; signals to/from the right are from the SMS-GMSC

Null

Receive_ Open_Ind

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Primitive

Error

Null

Null

MAP_ READY_ FOR_SM_ind

MAP_P_ ABORT_ind

MAP_ NOTICE_ ind

MAP_REPORT_SM_ DELIVERY_STATUS_ind

Check_ Indication

Null

MAP_ CLOSE_ req

Report_SM_ Delivery_ Stat_HLR

Error

OK

Error No Null

OK Delivery Result= Success? Yes

MNRF or MNRG supported AND MCEF supported AND MWD supported?

Alert_ Pending

Stop Race tim er

No Set User Error: Facility not supported

Yes Yes Subscriber known? No Null

Set User Error: Unknown subscriber

MAP_READY_FOR_SM_rsp MAP_CLOSE_req

No

MCEF set OR MNRF set OR MNRG set Yes

MAP_READY_FOR_SM_rsp MAP_CLOSE_req

Start Race timer

Null

Alert_ Pending

3651
3652

Figure 23.4/7 (sheet 1 of 2): Process SM_Alert_HLR

2328

2329

process SM_Alert_HLR
Process in the HLR to handle a notification that the MS is ready to receive short messages 1

SMA_HLR2(2)

Ready for SM Reason

Mem available ory for GPRS

Subscriber present for GPRS

Subscriber present for non-GPRS

Mem available ory for non-GPRS

Clear MNRG; Clear MCEF

Clear MNRG

Clear MNRF

Clear MNRF; Clear MCEF

Yes MCEF set? No Alert_ Service_ Centre_HLR Alert_ Service_ Centre_HLR

Yes MCEF set? No Alert_ Service_ Centre_HLR Alert_ Service_ Centre_HLR

Null

Alert_ Pending

Race timer expired

Internal

Receive_ Open_Ind

Error

OK

Vr Perform MAP Vr dialogue

Null

Null

Wait_For_ Service_ Primitive

Null

3653
3654 3655

Figure 23.4/7 (sheet 2 of 2): Process SM_Alert_HLR

2330

2331

process Alert_SC_IWMSC
Process in the SMS Interworking MSC to relay an alert to the SMSC

ASC_IWMSC1(1)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the SM SC

Null

Receive_ Open_Ind

Error

OK Wait_For_ Service_ Primitive

Vr Perform MAP Vr dialogue

Null

MAP_ NOTICE_ ind

MAP_ALERT_SERVICE_CENTRE_ind

Null

MAP_ CLOSE_ ind

Check_ Indication

Error

OK

Null

SC_RP_ALERT_SC_req

MAP_ALERT_SERVICE_CENTRE_rsp MAP_CLOSE_req

Null

3656
3657

Figure 23.4/8: Process Alert_SC_IWMSC

2332

2333

3658

23.5 The SM delivery status report procedure

to set the Service Centre address into the message waiting list in the HLR after short message delivery has failed because the subscriber is absent or unidentified or the memory capacity is exceeded. The procedure sets: the Memory Capacity Exceeded Flag (MCEF) in the HLR if the MS memory does not have room for more messages; and/or the MS Not Reachable Flag for non-GPRS if there is no record for the subscriber in the VLR or the subscriber does not respond to paging for delivery via the MSC; and/or the MS Not Reachable for GPRS (MNRG) flag if there is no record for the subscriber in the SGSN unidentified or the subscriber does not respond to paging for delivery via the SGSN.

3659 The SM delivery status report procedure is used: 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669

to report to the HLRthat delivery has succeeded. The conditions for report of a successful delivery are described in subclause 23.3.1.

3670 The message flow for the SM delivery status report procedure is shown in figure 23.5/1.

Visited MSC or SGSN

HLR

Gateway MSC 1

SC

2 3
3671
3672 3673 3674 3675 3676 3677 3678

1) 2) 3) 4)

MAP_MT_FORWARD_SHORT_MESSAGE_ACK/_NACK (Absent subscriber_SM, unidentified subscriber or memory capacity exceeded). MAP_REPORT_SM_DELIVERY_STATUS. MAP_REPORT_SM_DELIVERY_STATUS_ACK. Short Message Negative Acknowledgement (3GPP TS 23.040).

3679

Figure 23.5/1: Short message delivery status report procedure

3680

23.5.1 Procedure in the SMS-GMSC

The conditions for the GMSC to invoke the short message delivery status report procedure are specified in subclause 23.3.1.

3681 The short message delivery status report macro in the SMS-GMSC is shown in figure 23.5/2.

3682

23.5.2 Procedure in the HLR

3683 When the HLR receives a MAP_REPORT_SM_DELIVERY_STATUS indication, it acts as described in 3684 subclause 23.6, macro Report_SM_Delivery_Stat_HLR. 3685 The short message delivery status report process in the HLR is shown in figure 23.5/3.

2334

2335

macrodefinition Report_SM_Delivery_Stat_GMSC
Macro to report the result of an MT short message delivery attem pt

RSMDS_GMSC1(1)
Signals to/from the right are to/from the HLR

MAP_OPEN_req MAP_REPORT_SM _DELIVERY_STATUS_req MAP_DELIMITER_req

Receive_ Open_Cnf

V1 Success Delivery resul t? Failure Absent Subscriber

Vr

OK Wait_For_ HLR_Response

Error

Error

Other

Delivery failure reason?

MAP_REPORT_SM _DELIVERY_STATUS_cnf

Perform MAP Vr dialogue

Check_ Confirmation Provider Error, User Error, Data Error Error

OK

Error

OK

OK

Wait_For_ HLR_Response

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ CLOSE_ req

Error

3686
3687

Figure 23.5/2: Macro Report_SM_Delivery_Stat_GMSC

2336

2337

process SM_Delivery_Status_Report_HLR
Process in the HLR to handle an SM delivery status report from the SMS-GMSC

SMDSR_HLR1(1)
Signals to/from the left are to/from the SM S-GM SC

Null

MAP_REPORT_SM _DELIVERY_STATUS_ind

Report_SM_ Delivery_ Stat_HLR OK, Error

3688
3689

Figure 23.5/3: Process SM_Delivery_Status_Report_HLR

2338

2339

3690

2340

2341

3691

23.6 The macro Report_SM_Delivery_Stat_HLR

3692 This macro is invoked when the HLR receives a MAP_REPORT_SM_DELIVERY_STATUS indication from the 3693 SMS-GMSC. The macro invokes macros not defined in this clause; the definitions of these macros can be found as 3694 follows: 3695 3696

Check_Indication Alert_Service_Centre_HLR

see subclause 25.2.1; see subclause 25.10.3.

3697 Sheet 1: If the MAP_REPORT_SM_DELIVERY_STATUS indication did not include the GPRS support indicator, the 3698 HLR deduces the domain for which the delivery report applies as follows: 3699 3700 3701 3702 3703 3704

if the subscriber is a GPRS-only subscriber, the report applies for GPRS; if the subscriber is a non-GPRS-only subscriber, the report applies for non-GPRS; if the subscriber is a GPRS and non-GPRS subscriber and the subscription option for MT SMS delivery when the SMS-GMSC does not support GPRS is set to "Delivery via the SGSN", the report applies for GPRS; if the subscriber is a GPRS and non-GPRS subscriber and the subscription option for MT SMS delivery when the SMS-GMSC does not support GPRS is set to "Delivery via the MSC", the report applies for non-GPRS;

3705 The short message delivery status report macro in the HLR is shown in figure 23.6/1.

2342

2343

m acrodefinition Report_SM_Delivery_Stat_HLR
Macr o in the HLR to handle an SM delivery status report fr om the SMS-GMSC

RSMDS_HLR1(2)
Signals to/from the left ar e to/from the SMS-GMSC

Check_ Indication

Error No

OK Subscriber known? Yes Delivery failure Deliver y result? Successful transfer for non-GPRS Update MWD list Clear MNRF: Clear MCEF Clear MNRG: Clear MCEF Successful transfer for GPRS

Set User Error: Unknown Subscriber

Yes

MWD update failed? No

MAP_REPORT_SM_ DELIVERY_STATUS_rsp MAP_CLOSE_r eq

Set User Error: MWD list full

Alert_Service_ Centr e_HLR

MAP_REPORT_SM_ DELIVERY_STATUS_rsp MAP_CLOSE_req

Delivery Result:= Failure

Deliver y Result:= Success

Er ror

OK

3706
3707

Figure 23.6/1 (sheet 1 of 2): Macro Report_SM_Delivery_Stat_HLR

2344

2345

macrodefinition Report_SM_Delivery_Stat_HLR
Macr o in the HLR to handle an SM delivery status report fr om the SMS-GMSC 1

RSMDS_HLR2(2)
Signals to/from the left are to/from the SMS-GMSC

MSISDN= MSISDNAlert No

Yes

Set MSISDNAlert

Delivery failure cause?

MS memor y capacity exceeded for non-GPRS

MS memor y capacity exceeded for GPRS

Absent Subscriber for non- GPRS

Absent Subscriber for GPRS

Absent Subscriber for non- GPRS & GPRS

Set MCEF; Clear MNRF

Set MCEF; Clear MNRG

Set MNRF

Set MNRG

Set MNRF; Set MNRG

No

Reason for absence available? Yes

MN RR:= Reason for absence

Check_Absent_ Subscriber SM_ In_HLR

See 3GPP TS 23.116

MAP_REPORT_SM_DELIVERY_ STATUS_rsp MAP_Close_req

OK

3708
3709

Figure 23.6/1 (sheet 2 of 2): Macro Report_SM_Delivery_Stat_HLR

2346

2347

3710 3711

23.7 The mobile terminated short message transfer procedure for VGCS

3712 The mobile terminated short message transfer for VGCS procedure is used for forwarding a short message from a 3713 Service Centre to the group call anchor MSC. The message flow for the mobile terminated short message transfer 3714 procedure for VGCS is shown in figure 23.7/1.
Anchor MSC GCR Gateway MSC SC

1 2 3

4 5 6 7 8

3715
3716

Figure 23.7/1: Mobile terminated short message for VGCS service procedures

2348

2349

3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3732 3733 3734 3735 3736 3737

1) 2) 3) 4) 5) 6) 7) 8) (*)

Short Message (3GPP TS 23.040). TCAP BEGIN (*) TCAP CONTINUE (*) MAP_MT_FORWARD_SM_FOR_VGCS. GCR_SMS_INTERROGATION (3GPP TS 43.068). GCR_SMS_INTERROGATION_ACK (3GPP TS 43.068). MAP_MT_FORWARD_SM_FOR_VGCS_ACK. Short Message Acknowledgement (3GPP TS 23.040). If a) - the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MT_FORWARD_SM_FOR_VGCS request in a single TC message, and b) the SMS Gateway MSC operator and the serving node (Anchor-MSC) operator agreed not to use the TCAP handshake countermeasure against SMS fraud for messages exchanged between their networks (see 3GPP TS 33.204 [34a]) then the TCAP handshake may be omitted.

3738

3739

23.7.1 Procedure in the SMS-GMSC

3740 The process starts when the SMS-GMSC receives an SC_RP_MT_DATA indication from a Service Centre. The MAP 3741 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3742 3743

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3744 The mobile terminated short message transfer for VGCS process in the SMS-GMSC is shown in figure 23.7/2.

3745

23.7.2 Procedure in the Anchor MSC

3746 The process starts when the MSC receives a dialogue opening request with the application context shortMsgMT-Relay3747 VGCS-Context. The MAP process invokes macros not defined in this clause; the definitions of these macros can be 3748 found as follows: 3749

Receive_Open_Ind

see subclause 25.1.1;

3750 The mobile terminated short message transfer for VGCS process in the Anchor MSC is shown in figure 23.7/3 3751 Procedure MT_SM_VGCS_GMSC sheet 1: The decision box "TCAP Handshake required" takes the "yes" or "no" exit 3752 depending on agreements between the Serving MSC's operator and the SMS Gateway MSC's operator (see 3GPP TS 3753 33.204 [34a]).

2350

2351

process MT_SM_VGCS_GMSC
Process in the SMS-GMSC to handle delivery of an MT short message to a VGCS call

1(2)
Signals to/from the left are to/from the short message service centre, signals to/from the right are to/from the Group Call Anchor MSC

Null

SC_RP_MT_ DATA_ind

including a Group Call Reference Number

Message segmenting needed? no

yes

no

TCAP Handshake required

yes

MAP_OPEN_req MAP_MT_FORWARD_SM_VGCS_req MAP_DELIMITER_req

MAP_OPEN_req MAP_DELIMITER_req

Receive_ Open_Cnf

Receive_ Open_Cnf

Error, Vr

OK

Error, Vr

OK

Set RP_ERROR: System Failure

Set RP_ERROR: System Failure

MAP_MT_FORWARD_SM_VGCS_req MAP_DELIMITER_req

SC_RP_ ERROR_req

SC_RP_ ERROR_req

NULL

Wait_For_ Confirm

NULL

Wait_For_ Confirm

3754
3755

Figure 23.7/2 (sheet 1 of 2): Process MT_SM_VGCS_GMSC

2352

2353

process MT_SM_VGCS_GMSC
Process in the SMS-GMSC to handle delivery of an MT short message to a VGCS call Wait_For_ Confirm Signals to/from the left are to/from the short message service centre, signals to/from the right are to/from the Group Call Anchor MSC

2(2)

MAP_FORWARD_ SM_VGCS_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

MAP_ CLOSE_req

OK

User Error, Provider Error, Data Error

SET RP_ERROR

SC_RP_ ACK_req

SC_RP_ ERROR_req

NULL

3756
3757

Figure 23.7/2 (sheet 2 of 2): Process MT_SM_VGCS_GMSC

2354

2355

process MT_SM_VGCS_Anchor_MSC
Process in the Group Call Anchor MSC to handle delivery of an MT short message to a VGCS call Signals to/from the left are to/from the SMS GMSC; signals to/from the right are to/from the the application process in the Anchor MSC

1(2)

IDLE

Receive_ Open_ind

Error, Vr

OK

yes IDLE

Message protected by MAPsec no

no

TCAP Handshake required yes

Wait_For_ Service_ Primitive

Wait_For_ DELIMITER

MAP_MT_FORWARD_ SM_VGCS_ind

MAP_ DELIMITER_ ind

MAP_U_ABORT_ind MAP_P_ABORT_ind MAP_CLOSE_ind

MAP_ NOTICE_ ind

Set Error System Failure

MAP_ DELIMITER_ req

MAP_ CLOSE_ req

MAP_MT_FORWARD_ SM_VGCS_rsp

Wait_For_ Service_ Primitive

IDLE

MAP_ CLOSE_ req

IDLE

3758
3759

Figure 23.7/3 (sheet 1 of 2): Process MT_SM_VGCS_Anchor MSC

2356

2357

process MT_SM_VGCS_Anchor_MSC
Process in the Group Call Anchor MSC to handle delivery of an MT short message to a VGCS call Signals to/from the left are to/from the SMS GMSC; signals to/from the right are to/from the the application process in the Anchor MSC

2(2)

Wait_For_ Service_ Primitive

MAP_ DELIMITER_ ind

MAP_MT_FORWARD_ SM_VGCS_ind

MAP_U_ABORT_ind MAP_P_ABORT_ind MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_ DELIMITER_ req

MAP_ CLOSE_ req

Wait_For_ Service_ Primitive

see 3GPP TS 43.068

MT_Forward_SM_ VGCS

IDLE

Wait_For_ Response

positive response

negative response

set result

set error

MAP_MT_FORWARD_SM_VGCS_rsp MAP_CLOSE_req

IDLE

3760
3761

Figure 23.7/3 (sheet 2 of 2): Process MT_SM_VGCS_Anchor MSC

3762

24

GPRS process description

3763 The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures. 3764 The stage 2 specification for General Packet Radio Service (GPRS) is in 3GPP TS 23.060 [104].

2358

2359

3765 3766 3767

24.1 Procedure for retrieval of routeing information for GPRS

24.1.1 Process in the GGSN

3768 The MAP process in the GGSN to request routeing information for a network requested PDP context activation is 3769 shown in figure 24.1/2. The MAP process invokes macros not defined in this clause; the definition of these macros can 3770 be found as follows: 3771 3772

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3773

24.1.2 Process in the HLR

3774 The MAP process in the HLR to provide routing information for a network-requested PDP context activation is shown 3775 in figure 24.1/1. The MAP process invokes macros not defined in this clause; the definitions of these macros can be 3776 found as follows: 3777 3778

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

2360

2361

process SRI_GPRS_GGSN
Process in the GGSN to retrieve routeing information to establish a network-requested PDP context

SRI_GPRS_GGSN1(1)
Signals to/from the left are to/from the application process in the GGSN; signals to/from the right are to/from the HLR

Idle

Send Routing Info for GPRS

MAP_OPEN_req MAP_SEND_ROUTIN G_INFO_FOR_GPRS_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Per for m MAP Vr dialogue

Er ror

OK Wait_For_ Routeing_Info

Idle

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_SEND_ROUTIN G_INFO_FOR_GPRS_cnf

MAP_ CLOSE_ req

Check_ Confirmation

Set negative response: System failure

Provider Err or, Data Error

User Error

OK

Send Routing Info for GPRS negative r esponse

Send Routing Info for GPRS ack

Idle

Idle

3779
3780

Figure 24.1/1: Process SRI_GPRS_GGSN

2362

2363

process SRI_GPRS_HLR
Process in the HLR to provide routeing information to establish a network-requested PDP context

SRI_GPRS_HLR1(1)
Signals to/from the left ar e to/from the GGSN; signals to/fr om the right ar e to/from the GPRS application pr ocess in the HLR

Idle

Receive_ Open_Ind

OK Wait_For_ Ser vice_ Indication

Error

Vr Perform MAP Vr dialogue

Idle

MAP_SEND_ROUTING_INFO_FOR_GPRS_ind

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

Idle

Check_ Indication

MAP_ CLOSE_ req

Error

OK Send Routing Info for GPRS

Idle

Wait_For_ Routing_ Info

Send Routing Info for GPRS ack

Send Routing Info for GPRS negative response

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Set Routing info

Set User Error

MAP_ CLOSE_ req

MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp MAP_CLOSE_req

Idle

Idle

3781
3782

Figure 24.1/2: Process SRI_GPRS_HLR

2364

2365

3783 3784 3785

24.2 Procedure for reporting failure to establish a network requested PDP context
24.2.1 Process in the GGSN

3786 The MAP process in the GGSN to report the failure to establish a network requested PDP context is shown in figure 3787 24.2/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as 3788 follows: 3789 3790

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3791

24.2.2 Process in the HLR

3792 The MAP process in the HLR to handle a notification from the GGSN that a network requested PDP context could not 3793 be established is shown in figure 24.2/2. The MAP process invokes macros not defined in this clause; the definitions of 3794 these macros can be found as follows: 3795 3796

Receive_Open_Ind Check Indication

see subclause 25.1.1; see subclause 25.2.1.

2366

2367

process Failure_Report_GGSN
Process in the GGSN to report a failure to establish a networkrequested PDP context

FR_GGSN1(1)
Signals to/from the left are to/from the application process in the GGSN; signals to/from the right are to/from the HLR

Idle

Failure report

MAP_OPEN_req MAP_FAILURE_REPORT_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Error

OK Wait_For_ HLR_Response

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

MAP_FAILURE_REPORT_cnf

MAP_ CLOSE_ req

Check_ Confirmation

Set negative response: System failure

Provider Error, Data Error

User Error

OK

Failure report negative response

Failure report ack

Idle

Idle

3797
3798

Figure 24.2/1: Process Failure_Report_GGSN

2368

2369

process Failure_Report_HLR
Process in the HLR to handle a failure report from the GGSN

FR_HLR1(1)
Signals to/from the left are to/from the GGSN; signals to/from the right are to/from the GPRS application process in the HLR

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_FAILURE_REPORT_ind

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

Check_ Indication

MAP_ CLOSE_ req

Error

OK

Failure report

Idle

Wait_For_ Application_ Response

Failure report ack

Failure report negative response

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Set User Error

MAP_ CLOSE_ req

MAP_FAILURE_REPORT_rsp MAP_CLOSE_req

Idle

Idle

3799
3800

Figure 24.2/2: Process Failure_Report_HLR

2370

2371

3801 3802 3803

24.3 Procedure for reporting that an MS has become reachable for GPRS
24.3.1 Process in the HLR

3804 The MAP process in the HLR to report that an MS is reachable for GPRS is shown in figure 24.3/1. The MAP process 3805 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3806 3807

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3808

24.3.2 Process in the GGSN for Note Ms Present For Gprs

3809 The MAP process in the GGSN to handle a notification that the subscriber is present for GPRS again is shown in figure 3810 24.3/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as 3811 follows: 3812 3813

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

2372

2373

process Note_MS_Present_for_GPRS_HLR
Process in the HLR to report to the GGSN that an MS is reachable for GPRS

NMP_GPRS_HLR1(1)
Signals to/from the left ar e to/from the GGSN; signals to/fr om the right ar e to/from the GPRS application pr ocess in the HLR

Idle

Note MS pr esent for GPRS

MAP_OPEN_req MAP_NOTE_MS_PRESENT_FOR_GPRS_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Err or

OK Wait_For_ GGSN_Response

MAP_U_ABORT_ind, MAP_P_ABORT _ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

MAP_NOTE_MS_PRESENT_FOR_GPRS_cnf

MAP_ CLOSE_ req

Check_ Confirmation

Set negative response: System failure

Provider Err or , Data Error

User Error

OK

Note MS present for GPRS negative r esponse

Note MS present for GPRS ack

Idle

Idle

3814
3815

Figure 24.3/1: Process Note_MS_Present_For_GPRS_HLR

2374

2375

process Note_MS_Present_For_GPRS_GGSN
Process in the GGSN to handle a notification that the M is S reachable for GPRS

NMP_GPRS_GGSN1(1)
Signals to/from the left are to/from the application process in the GGSN; signals to/from the right are to/from the HLR

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_NOTE_MS_PRESENT_FOR_GPRS_ind

MAP_P_ ABORT_ ind

MAP_ NOTICE_ ind

Check_ Indication

MAP_ CLOSE_ req

Error

OK Note MS present for GPRS

Idle

Wait_For_ Application_ Response

Note MS present for GPRS ack

Note M present S for GPRS negative response

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Set Routing info

Set User Error

MAP_ CLOSE_ req

MAP_NOTE_MS_PRESENT_FOR_GPRS_rsp MAP_CLOSE_req

Idle

Idle

3816
3817

Figure 24.3/2: Process Note_MS_Present_For_GPRS_GGSN

2376

2377

3818 3819

24A

CSE interrogation and control of subscriber data

24A.1General

3820 The MAP procedures for interrogation and control of subscriber data are used to allow the CSE: 3821 3822 3823 3824 3825

to retrieve subscriber data from the HLR; to modify subscriber data in the HLR; to receive notification from the HLR when there is a change in subscriber data; to request information about the location of a subscriber from the HLR or the GMLC; to request information about the state of a subscriber from the HLR.

3826 The following application context refers to a complex MAP user consisting of several processes:
3827

anyTimeInfoHandlingContext

3828 This application context needs a co-ordinating process in the HLR. 3829 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 3830

Receive_Open_Ind

see subclause 25.1.1;

3831 The Any Time Info Handling Co-ordinator process in the HLR is shown in figure 24A.1/1.

2378

2379

process Co_ATIH_HLR
Co-ordinating process in the HLR to handle a dial ogue opening request using the application context anyTimeInfoHandlingContext

Co_ATIH_HLR1(1)
Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the child process

Null

Receive_ Open_Ind

Figure 25.1/1

OK Wait_For_ Service_ Primitive

Vr, Error

Null

MAP_ANY_TIM E_ SUBSCRIPTION_ INTERROGATION_ind

MAP_ANY_TIM E_ MODIFICATION_ind

MAP_ NOTICE_ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

ATSI_HLR

ATM_HLR

MAP_ CLOSE_req

MAP_ANY_TIM E_ SUBSCRIPTION_ INTERROGATION_ind

MAP_ANY_TIM E_ MODIFICATION_ind

Null

Relay_Info

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_U_ABORT_req, MAP_CLOSE_req

Null

Relay_Info

Null

Relay_Info

3832
3833

Figure 24A.1/1: Process Co_ATIH_HLR

2380

2381

3834 3835

24A.2Any Time Subscription Interrogation procedure

24A.2.1 General

3836 The message flow for successful retrieval of subscription information related to an any time subscription interrogation 3837 from the CAMEL server are shown in figure 24A.1/1. In an IP Multimedia Core Network, an IM-SSF can take on the 3838 role of a gsmSCF for this procedure (see 3GPP TS 23.278 [125]).

gsmSCF

HLR

MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION

MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION ack

3839
3840

Figure 24A.2/1: Message flow for any time subscription interrogation

3841 The following MAP service is used to retrieve requested information: 3842

MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION

see subclause 8.11.3.

3843

24A.2.2 Process in the gsmSCF

3844 The MAP process in the gsmSCF to obtain subscription information in response to a request from the application 3845 process in the gsmSCF is shown in figure 24A.2/2. The MAP process invokes macros not defined in this clause; the 3846 definitions of these macros can be found as follows: 3847 3848

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2

3849

24A.2.3 Process in the HLR

3850 The MAP process in the HLR to provide subscription information in response to an interrogation from the CAMEL 3851 server is shown in figure 24A.2/3. The MAP process invokes a macro not defined in this clause; the definition of this 3852 macro can be found as follows: 3853

Check_Indication

see subclause 25.2.2

3854 If the MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION service response cannot be carried in a single TC3855 Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by 3856 a TC-Result-L component in a TC-END message.

2382

2383

process ATSI_gsmSCF
Process in the gsmSCF to retrieve subscripti on information from the HLR

ATSI_SCF1(1)
Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the HLR

Idle

Any time subscription interrogation request

MAP_OPEN_req MAP_ANY_TIM E_SUBSCRIPTION_INTERROGATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_ Response

Vr, Error

MAP_ANY_TIM E_SUBSCRIPTION_INTERROGATION_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Check_ Confirmation Provider Error, Data Error

MAP_ CLOSE_ req

OK

User Error

Set negative response: System failure

Any time subscription interrogation ack

Any time subscripti on interrogation negative response

Any tim subscription e interrogation negative response

Idle

Idle

Idle

3857
3858

Figure 24A.2/2: Process ATSI_gsmSCF

2384

2385

process ATSI_HLR
Process in the HLR to handle a request from the gsm SCF for subscripti on information

ATSI_HLR1(1)
Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the subscriber data managem ent application in the HLR

Wait_For_ Service_ Indication

MAP_ANY_TIM E_SUBSCRIPTION_INTERROGATION_ind

Check_ Indication

OK

Error

Any Time Subscription Interrogation request

Wait_For_ Application_ Response

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Any Time Subscription Interrogation ack

Any Time Subscription Interrogation error

Set result

Set User Error

MAP_ CLOSE_ req

MAP_ANY_TIM E_SUBSCRIPTION_INTERROGATION_rsp MAP_CLOSE_req

3859
3860

Figure 24A.2/3: Process ATSI_HLR

2386

2387

3861 3862

24A.3Any Time Modification procedure

24A.3.1 General

3863 The message flow for successful modification of subscription information related to an any time modification request 3864 from the CAMEL server is shown in figure 24A.3/1

gsmSCF

HLR

MAP_ANY_TIME_MODIFICATION

MAP_ANY_TIME_MODIFICATION ack

3865
3866

Figure 24A.3/1: Message flow for any time modification

3867 The following MAP service is used to modify subscription information: 3868

MAP_ANY_TIME_MODIFICATION

see subclause 8.11.4.

3869

24A.3.2 Process in the gsmSCF

3870 The MAP process in the gsmSCF to modify subscription information in response to a request from the application 3871 process in the gsmSCF is shown in figure 24A.3/2. The MAP process invokes macros not defined in this clause; the 3872 definitions of these macros can be found as follows: 3873 3874

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2

3875

24A.3.3 Process in the HLR

3876 The MAP process in the HLR to modify subscriber information in response to a modification request from the CAMEL 3877 server is shown in figure 24A.3/3. The MAP process invokes a macro and a process not defined in this clause; the 3878 definitions of these can be found as follows: 3879 3880

Check_Indication Insert_Subs_Data_Stand_Alone_HLR

see subclause 25.2.2; see subclause 25.7.3;

3881 If the macro takes the OK exit, the MAP process waits for a service indication. 3882 If the MAP_ANY_TIME_MODIFICATION service response cannot be carried in a single TC-Result component, it is 3883 carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L 3884 component in a TC-END message. 3885 If the serving node (VLR or SGSN) is to be updated after the modification, the MAP process creates an instance of the 3886 appropriate process (Insert_Subs_Data_Stand_Alone_HLR for VLR update, 3887 Insert_GPRS_Subs_Data_Stand_Alone_HLR for SGSN update).

2388

2389

process ATM_gsmSCF
Process in the gsmSCF to modify subscripti on information in the HLR

ATM_SCF1(1)
Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the HLR

Idle

Any time modification request

MAP_OPEN_req MAP_ANY_TIM E_MODIFICATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_ Response

Vr, Error

MAP_ANY_TIM E_MODIFICATION_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Check_ Confirmation Provider Error, Data Error

MAP_ CLOSE_ req

OK

User Error

Set negative response: System failure

Any time modification ack

Any time modification negative response

Any tim m e odification negative response

Idle

Idle

Idle

3888
3889

Figure 24A.3/2: Process ATM_gsmSCF

2390

2391

process ATM_HLR
Process in the HLR to handle a request from the gsm SCF to modify subscription information

ATM_HLR1(1)
Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the subscriber data managem ent application in the HLR Wait_For_ Service_ Indication

MAP_ANY_TIM E_MODIFICATION_ind

Check_ Indication

OK Any Time Modification request

Error

Wait_For_ Application_ Response

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Any Time Modification ack

Any Time Modification error

Set result

Set User Error

MAP_ CLOSE_ req

MAP_ANY_TIM E_MODIFICATION_rsp MAP_CLOSE_req

No

VLR/SGSN update required? Yes Insert_ Subs_Data_ Stand_Alone_HLR Insert_GPRS_Subs_Data_ Stand_Alone_HLR for SGSN update

3890
3891

Figure 24A.3/3: Process ATM_HLR

2392

2393

3892 3893

24A.4Subscriber Data Modification Notification procedure

24A.4.1 General

3894 The Subscriber Data Modification Notification procedure is used to notify a gsmSCF about the modification of 3895 subscriber data. In an IP Multimedia Core Network, an IM-SSF can take on the role of a gsmSCF for this procedure. 3896 The stage 2 specification for Subscriber Data Modification Notification is in 3GPP TS 23.078 [98] and 3GPP TS 3897 23.278 [125]. The interworking between the MAP signalling procedures and the Subscriber Data Modification 3898 Notification procedures for each entity (HLR, gsmSCF) is shown by the transfer of signals between these processes. 3899 The following services are used:

HLR

gsmSCF

MAP_NOTE_SUBSCRIBER_DATA_MODIFIED

MAP_NOTE_SUBSCRIBER_DATA_MODIFIED ack

3900
3901

Figure 24A.4/1: Message flow for subscriber data modification notification

3902 The following MAP service is used to send the notification to the gsmSCF: 3903

MAP_NOTE_SUBSCRIBER_DATA_MODIFIED

see subclause 8.11.5.

3904

24A.4.2 Process in the HLR

3905 The MAP process in the HLR to send modified data to the gsmSCF is shown in figure 24A.4/2. The MAP process 3906 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3907 3908

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3909 If the required information cannot be carried in a single MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service 3910 request, the HLR segments the information into two or more requests. The "All Information Sent" parameter is omitted 3911 from each request except the last. 3912 Sheet 2: If the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service request contained the "All Information Sent" 3913 parameter, the test "All information sent" takes the "Yes" exit.

3914

24A.4.3 Process in the gsmSCF

3915 The MAP process in the gsmSCF to handle a notification to the gsmSCF of change of subscriber data is shown in figure 3916 24A.4/3. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as 3917 follows: 3918 3919

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1

2394

2395

3920 If the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service indication contained the "All Information Sent" 3921 parameter, the test "All information sent" takes the "Yes" exit. 3922 3923 3924 3925

If the test "All information sent" takes the "No" exit, the MAP process stores the data received in the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service indication. If the test "All information sent" takes the "Yes" exit, the MAP process assembles the data received in all the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service indications received in the dialogue and sends the assembled data to the application process in the gsmSCF.

2396

2397

process NSDC_HLR
Process in the HLR to notify the gsmSCF that subscriber data have changed

NSDC_HLR1(2)
Signals to/from the left are to/from the application process in the HLR (see 3GPP TS 23.078 or 3GPP TS 23.278); Signals to/from the right are to/from the gsmSCF

Idle

Notify Subscriber Data change

Yes Segmentation required? No

Set: All Information Sent

MAP_OPEN_req MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK

Vr, Error Set negative response: System failure

Notify Subscriber Data Change negative response

Wait_For_ gsmSCF_ Response

Idle

3926
3927

Figure 24A.4/2 (sheet 1 of 2): Process NSDC_HLR

2398

2399

process NSDC_HLR
Process in the HLR to notify the gsmSCF that subscriber data have changed Wait_For_ gsmSCF_ Response

Signals to/from the left are to/from the application process in the HLR (see 3GPP TS 23.078 or 3GPP TS 23.278); Signals to/from the right are to/from the gsm SCF

NSDC_HLR2(2)

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_cnf

MAP_ CLOSE_ req

User Error, Provider Error, Data Error

Check_ Confirmation OK

Notify Subscriber Data Change negative response

Yes Idle No All information sent?

Yes Notify Subscriber Data Change response No Segmentation required?

Idle

Set: All Information Sent

MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_req MAP_DELIMITER_req

Wait_For_ gsmSCF_ Response

3928
3929

Figure 24A.4/2 (sheet 2 of 2): Process NSDC_HLR

2400

2401

process NSDC_gsmSCF
Process in the gsmSCF to handle a notification of change of subscriber data

NSDC_SCF1(1)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the application process in the gsmSCF Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Error

Idle

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

MAP_NOTE_SUBSCRIBER_DATA_MODIFIED_ind

MAP_ CLOSE_ req

Check_ Indication

Error MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_rsp MAP_CLOSE_req

OK All information sent? No Store recei ved data Assemble received data Yes

Idle

Idle

MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_rsp MAP_DELIMITER_req

Notify Subscriber Data Change

Wait_For_ Service_ Indication

Wait_For Application_ Response

MAP_ NOTICE_ ind

Notify Subscriber Data Change negative response

Notify Subscriber Data Change response

MAP_ CLOSE_ req

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Set User Error

MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_rsp MAP_CLOSE_req

Idle

Idle

3930
3931

Figure 24A.4/3: Process NSDC_gsmSCF

2402

2403

3932 3933

24A.5Any Time Interrogation procedure

24A.5.1 General

3934 The message flows for successful retrieval of subscriber information related to an any time interrogation from the 3935 CAMEL server are shown in figure 24A.5/1 for interrogation directed to an HLR and figure 24A.5/2 for interrogation 3936 directed to a GMLC.
SGSN or VLR 2 3

gsmSCF 1

HLR

3937
3938 3939 3940 3941 3942 3943

1) 2) 3) 4)

MAP_ANY_TIME_INTERROGATION_req/ind MAP_PROVIDE_SUBSCRIBER_INFO_req/ind MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf MAP_ANY_TIME_INTERROGATION_rsp/cnf

3944

Figure 24A.5/1: Message flow for any time interrogation (gsmSCF to HLR)

3945 The following MAP services are used to retrieve information about the status and/or location of a subscriber: 3946 3947

MAP_ANY_TIME_INTERROGATION see subclause 8.11.1; MAP_PROVIDE_SUBSCRIBER_INFO see subclause 8.11.2.

3948 The HLR sends the MAP_PROVIDE_SUBSCRIBER_INFO request to the SGSN or the VLR, according to the domain 3949 for which the gsmSCF requested the information.

gsmSCF

GMLC 1

3950
3951 3952 3953 3954

1) 2)

MAP_ANY_TIME_INTERROGATION_req/ind MAP_ANY_TIME_INTERROGATION_rsp/cnf

3955

Figure 24A.5/2: Message flow for any time interrogation (gsmSCF to GMLC)

3956 The following MAP service is used to retrieve location information from a GMLC: 3957

MAP_ANY_TIME_INTERROGATION see subclause 8.11.1;

3958 In addition, the GMLC may use MAP Services specific to Location Services.

2404

2405

3959

24A.5.2 Procedures in the gsmSCF

3960 The process in the gsmSCF to request information about the location and/or state of a subscriber from the HLR is 3961 shown in figure 24A.5/3. The MAP process invokes macros not defined in this clause; the definitions of these macros 3962 can be found as follows: 3963 3964

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3965 The process in the gsmSCF to request location information from the GMLC is shown in figure 24A.5/4. The MAP 3966 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3967 3968

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

3969 24A.5.3

Procedure in the HLR

3970 The MAP process in the HLR to provide subscriber information in response to an interrogation from the CAMEL server 3971 is shown in figure 24A.5/5. The MAP process invokes macros not defined in this clause; the definitions of these macros 3972 can be found as follows: 3973 3974 3975

Receive_Open_Ind Receive_Open_Cnf Check_Confirmation

see subclause 25.1.1; see subclause 25.1.2; see subclause 25.2.2.

3976

24A.5.4 Procedure in the GMLC

3977 The MAP process in the GMLC to provide location information in response to a request from the gsmSCF is shown in 3978 figure 24A.5/6. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found 3979 as follows: 3980

Receive_Open_Ind

see subclause 25.1.1.

2406

2407

process ATI_To_HLR_gsmSCF
Process in the gsmSCF to request subscriber location and/or state from the HLR

ATI2HLR_SCF1(1)
Signals to/from the left are to/from the application process in the gsmSCF; signals to/from the right are to/from the HLR

Idle

Any Time Interrogation

MAP_OPEN_req MAP_ANY_TIM E_INTERROGATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Error

OK Wait_For_ HLR_Response

Abort

Idle

MAP_ANY_TIM E_INTERROGATION_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

Check_ Confirmation

User Error, Provider Error, Data Error

MAP_ CLOSE_ req

OK Any Time Interrogation ack Set negative response: system failure

Idle

Any Time Interrogation negative response

Idle

3981
3982

Figure 24A.5/3: Process ATI_To_HLR_gsmSCF

2408

2409

process ATI_To_GMLC_gsmSCF
Process in the gsmSCF to request subscriber location fr om the GMLC

ATI2GMLC_SCF1(1)
Signals to/from the left ar e to/from the application pr ocess in the gsmSCF; signals to/fr om the right ar e to/from the GMLC

Idle

Obtain Subscriber Location

MAP_OPEN_req MAP_ANY_TIME_INTERROGATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr, Err or

OK Wait_For_ GMLC_Response

Abort

Idle

MAP_ANY_T IME_INTERROGATION_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

User Error, Provider Error , Data Error

MAP_ CLOSE_ req

OK Obtain Subscriber Location ack Set negative response: system failure

Idle

Obtain Subscriber Location negative r esponse

Idle

3983
3984

Figure 24A.5/4: Process ATI_To_GMLC_gsmSCF

2410

2411

process ATI_HLR
Process in the HLR to handle an Any Time Interrogation request

ATI_HLR1(2)
Signals to/from the left are to/from the gsmSCF; signals to/fr om the right are to/from the application process in the HLR (see 3GPP TS 23.078)

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Err or

Idle

MAP_P_ ABORT_ ind

MAP_ANY_TIME_INTERROGATION_ind

MAP_ NOTICE_ ind

Idle

Any Time Interr ogation request

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Idle

Any Time Interr ogation ack

Any Time Interrogation negative response

Set result

Set error

MAP_ANY_TIME_INTERROGATION_rsp MAP_CLOSE_req

Idle

3985
3986

Figure 24A.5/5 (sheet 1 of 2): Process ATI_HLR

2412

2413

process ATI_HLR
Process in the HLR to handle an Any Time Interrogation request Wait_For_ Application_ Response

ATI_HLR2(2)
Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the application process in the HLR (see 3GPP TS 23.078) unless marked otherwise

Provide Subscriber Info

To VLR or SGSN

MAP_OPEN_req MAP_PROVIDE_SUBSCRIBER_INFO_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK

Vr, Error Provide Subscriber Info negative response

Wait_For_ PSI_Response

Wait_For_ Application_ Response

MAP_PROVIDE_SUBSCRIBER_INFO_cnf

MAP_ NOTICE_ ind

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation

User Error, Provider Err or , Data Error

MAP_ CLOSE_ req

OK Provide Subscriber Info ack Provide Subscriber Info negative response

Wait_For_ Application_ Response

Wait_For_ Application_ Response

3987
3988

Figure 24A.5/5 (sheet 2 of 2): Process ATI_HLR

2414

2415

process ATI_GMLC
Process in the HLR to handle an Any Time Interrogation request

ATI_GMLC1(1)
Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the application process in the GMLC (see 3GPP TS 23.078)

Idle

Receive_ Open_Ind

OK Wait_For_ Service_ Indication

Vr, Err or

Idle

MAP_P_ ABORT_ ind

MAP_ANY_TIME_INTERROGATION_ind

MAP_ NOTICE_ ind

Idle

Any Time Interr ogation request

MAP_ CLOSE_ req

Wait_For_ Application_ Response

Idle

Any Time Interr ogation ack

Any Time Interrogation negative response

Set result

Set error

MAP_ANY_TIME_INTERROGATION_rsp MAP_CLOSE_req

Idle

3989
3990

Figure 24A.5/6: Process ATI_GMLC

2416

2417

3991 3992 3993

24B

Location Services process description

24B.1Routeing information retrieval procedure for LCS
24B.1.1 General

3994 The message flow for successful retrieval of routeing information related to location services is shown in figure 3995 24B.1/1.

GMLC MAP_SEND_ROUTING_INFO_FOR_LCS

HLR

MAP_SEND_ROUTING_INFO_FOR_LCS_ACK

3996
3997

Figure 24B.1/1: Message flow for retrieval of routeing information for LCS

3998 The following MAP service is used to retrieve routeing information: 3999

MAP_SEND_ROUTING_INFO_FOR_LCS

see subclause 13A.1.

4000

24B.1.2 Process in the GMLC

4001 The MAP process in the GMLC to request routeing information for LCS is shown in figure 24B.1/2. The MAP process 4002 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4003 4004

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

4005 24B.1.3 Process in the HLR

4006 The MAP process in the HLR to handle a request for routeing information for LCS is shown in figure 24B.1/3. The 4007 MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4008 4009

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

2418

2419

4010
process SRI_LCS_GMLC
Process in the GMLC to retrieve routeing information for a location services enquiry

SRI_LCS_GMLC1(1)
Signals to/from the left are to/from the application process in the GMLC; signals to/from the right are to/from the HLR

Idle

Send routing info for LCS

MAP_OPEN_req MAP_SEND_ROUTING_INFO_FOR_LCS_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Error

MAP_SEND_ROUTING_INFO_FOR_LCS_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error, Data Error Set negative response: System fai lure

MAP_ CLOSE_ req

OK

User Error

Set negative response: System fai lure

Send routing info for LCS ack

Send routing info for LCS negative response

Send routing info for LCS negative response

Send routing info for LCS negative response

Idle

Idle

Idle

Idle

4011
4012

Figure 24B.1/2: Process SRI_LCS_GMLC

2420

2421

process SRI_LCS_HLR
Process in the HLR to provide routeing information for a location services enquiry

SRI_LCS_HLR1(1)
Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the HLR

Idle

Receive_ Open_Ind

OK Wait_For Service_ Indication

Vr, Error

Idle

MAP_SEND_ROUTING_INFO_FOR_LCS_ind

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

Check_ Indication

MAP_ CLOSE_ req

Error

OK

Send routing info for LCS

Idle

Wait_For_ Routeing_ Info

Send routing info for LCS ack

Send routing info for LCS negative response

Set Result

Set User Error

MAP_SEND_ROUTING_INFO_FOR_LCS_rsp MAP_CLOSE_req

Idle

4013
4014

Figure 24B.1/3: Process SRI_LCS_HLR

2422

2423

4015 4016

24B.2Provide Subscriber Location procedure

24B.2.1 General

4017 The message flow for successful retrieval of the location information of a target MS related to location services is 4018 shown in figure 24B.1/1.

GMLC MAP_PROVIDE_SUBSCRIBER_LOCATION

MSC/ SGSN

MAP_PROVIDE_SUBSCRIBER_LOCATION_ACK

4019
4020

Figure 24B.2/1: Message flow for retrieval of location information

4021 The following MAP service is used to retrieve location information: 4022

MAP_PROVIDE_SUBSCRIBER_LOCATION

see subclause 13A.2.

4023

24B.2.2 Process in the GMLC

4024 The MAP process in the GMLC to request location information from an MSC or an SGSN is shown in figure 24B.2/2. 4025 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4026 4027

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

4028

24B.2.3 Process in the MSC

4029 The MAP process in the MSC to handle a request for location information from a GMLC is shown in figure 24B.2/3. 4030 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4031 4032

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

4033

24B.2.4 Process in the SGSN

4034 The MAP process in the SGSN to handle a request for location information from a GMLC is shown in figure 24B.2/4. 4035 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4036 4037

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

2424

2425

process PSL_GMLC
Process in the GMLC to retrieve the location of a target MS from the MSC or the SGSN

PSL_GMLC1(1)
Signals to/from the left are to/from the application process in the GMLC; signals to/from the right are to/from the MSC or the SGSN

Idle

Provide subscriber location

MAP_OPEN_req MAP_PROVIDE_SUBSCRIBER_LOCATION_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ Serving_Node_ Response

Vr, Error

MAP_PROVIDE_SUBSCRIBER_LOCATION_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error, Data Error Set negative response: System failure

MAP_ CLOSE_ req

OK

User Error

Set negative response: System failure

Provide subscriber location ack

Provide subscriber location negative response

Provide subscriber location negative response

Idle

Idle

Idle

4038
4039

Figure 24B.2/2: Process PSL_GMLC

2426

2427

process PSL_MSC
Process in the M to retrieve SC the location of a target MS

PSL_MSC1(1)
Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the MSC

Idle

Receive_ Open_Ind

OK Wait_For Service_ Indication

Vr, Error

Idle

MAP_PROVIDE_SUBSCRIBER_LOCATION_ind

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

Check_ Indication

MAP_ CLOSE_ req

Error Provide subscriber location

OK

Idle

Wait_For_ Location_ Info

Provide subscriber location ack

Provide subscriber location negative response

Set Result

Set User Error

MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp MAP_CLOSE_req

Idle

4040
4041

Figure 24B.2/3: Process PSL_MSC

2428

2429

process PSL_SGSN
Process in the SGSN to retrieve the location of a target MS

PSL_SGSN1(1)
Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the SGSN

Idle

Receive_ Open_Ind

OK Wait_For Service_ Indication

Vr, Error

Idle

MAP_PROVIDE_SUBSCRIBER_LOCATION_ind

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

Check_ Indication

MAP_ CLOSE_ req

Error Provide subscriber location

OK

Idle

Wait_For_ Location_ Info

Provide subscriber location ack

Provide subscriber location negative response

Set Result

Set User Error

MAP_PROVIDE_SUBSCRIBER_LOCATION_rsp MAP_CLOSE_req

Idle

4042
4043

Figure 24B.2/4: Process PSL_SGSN

2430

2431

4044 4045

24B.3Subscriber Location Report procedure

24B.3.1 General

4046 The message flow for successful report of the location information of a target MS related to location services is shown 4047 in figure 24B.3/1.

GMLC MAP_SUBSCRIBER_LOCATION_REPORT

MSC/ SGSN

MAP_SUBSCRIBER_LOCATION_REPORT_ACK

4048
4049

Figure 24B.3/1: Message flow for report of the location information

4050 The following MAP services are used to report location information: 4051

MAP_SUBSCRIBER_LOCATION_REPORT

see subclause 13A.3.

4052

24B.3.2 Process in the MSC

4053 The MAP process in the MSC to send a subscriber location report to the GMLC is shown in figure 24B.3/2. The MAP 4054 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4055 4056

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

4057

24B.3.3 Process in the SGSN

4058 The MAP process in the SGSN to send a subscriber location report to the GMLC is shown in figure 24B.3/3. The MAP 4059 process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4060 4061

Receive_Open_Cnf Check_Confirmation

see subclause 25.1.2; see subclause 25.2.2.

4062

24B.3.4 Process in the GMLC

4063 The MAP process in the GMLC to handle a subscriber location report is shown in figure 24B.3/4. The MAP process 4064 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 4065 4066

Receive_Open_Ind Check_Indication

see subclause 25.1.1; see subclause 25.2.1.

2432

2433

process SLR_MSC
Process in the M to report SC the location of an MS to the GMLC

SLR_MSC1(1)
Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the MSC

Idle

Subscriber location report

MAP_OPEN_req MAP_SUBSCRIBER_LOCATION_REPORT_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ GMLC_Response

Vr, Error

MAP_SUBSCRIBER_LOCATION_REPORT_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error, Data Error Set negative response: System failure

MAP_ CLOSE_ req

OK

User Error

Set negative response: System failure

Subscriber location report ack

Subscriber location report negative response

Subscriber location report negative response

Idle

Idle

Idle

4067
4068

Figure 24B.3/2: Process SLR_MSC

2434

2435

process SLR_SGSN
Process in the SGSN to report the location of an MS to the GMLC

SLR_SGSN1(1)
Signals to/from the left are to/from the GMLC; signals to/from the right are to/from the application process in the MSC

Idle

Subscriber location report

MAP_OPEN_req MAP_SUBSCRIBER_LOCATION_REPORT_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ GMLC_Response

Vr, Error

MAP_SUBSCRIBER_LOCATION_REPORT_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error, Data Error Set negative response: System failure

MAP_ CLOSE_ req

OK

User Error

Set negative response: System failure

Subscriber location report ack

Subscriber location report negative response

Subscriber location report negative response

Idle

Idle

Idle

4069
4070

Figure 24B.3/3: Process SLR_SGSN

2436

2437

process SLR_GMLC
Process in the GMLC to receive a subscriber location report from the M or the SGSN SC

SLR_GMLC1(1)
Signals to/from the left are to/from the application process in the GMLC; signals to/from the right are to/from the MSC or the SGSN Idle

Receive_ Open_Ind

OK Wait_For Service_ Indication

Vr, Error

Idle

MAP_SUBSCRIBER_LOCATION_REPORT_ind

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

Check_ Indication

MAP_ CLOSE_ req

Error

OK Subscriber location report

Idle

Wait_For_ Location_ Info

Subscriber location report ack

Subscriber location report negative response

Set Result

Set User Error

MAP_SUBSCRIBER_LOCATION_REPORT_rsp MAP_CLOSE_req

Idle

4071
4072

Figure 24B.3/4: Process SLR_GMLC

2438

2439

4073 4074 4075

25

General macro description

25.1 MAP_OPEN handling macros
25.1.1 Macro Receive_Open_Ind

4076 This macro is used by a MAP service-user procedure when a peer entity requests opening of a dialogue.

4077

25.1.2 Macro Receive_Open_Cnf

4078 This macro is used by a user procedure after it has requested opening of a dialogue towards a peer entity.

2440

2441

macrodefinition Receive_Open_Ind
Macro to handle a MAP_OPEN indication

Rec_Open_Ind1(2)
Signals to/from the left are to/from the rem ote peer entity

MAP_ OPEN_ ind

Yes Version 1 AC? No No MAP_ OPEN info present? Yes Reference:= Destination reference

Vr

Check_ Reference

Figure 25.1/3

OK Reference:= Or iginating reference

Error Refuse-reason:= Invalid destination reference

Check_ Reference

Figure 25.1/3

OK No Destination reference check required? Yes Yes Destination reference known? No Refuse-reason:= Invalid destination reference

Error Refuse-reason:= Invalid originating reference

4079
4080

Figure 25.1/1 (sheet 1 of 2): Macro Receive_Open_Ind

2442

2443

macrodefinition Receive_Open_Ind
Macro to handle a MAP_OPEN indication

Rec_Open_Ind2(2)
Signals to/from the left are to/from the rem ote peer entity

Result:= Dialogue refused

Result:= Dialogue accepted

AC nam e:= Highest versi on supported

AC nam e:= Received AC nam e

MAP_ OPEN_ rsp

MAP_ OPEN_ rsp

Yes

Received AC version (Vr)= the one defined in this version of 3GPP TS 29.002? No

Error

OK

Vr

4081
4082

Figure 25.1/1 (sheet 2 of 2): Macro Receive_Open_Ind

2444

2445

macrodefinition Receive_Open_Cnf
Macro to handle a MAP_OPEN confirm

Rec_Open_Cnf1(1)
Signals to/from the right are to/from the rem ote peer entity

Wait_For_ Open_Cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind

MAP_ OPEN_ cnf

MAP_ CLOSE_ req

Dialogue accepted Result?

Dialogue refused

AC not supported Error Error OK Refuse reason?

Else

Potential version incompatibility Yes Received AC version (Vr) lower than the one defined in this version of 3GPP TS 29.002?

Vr:=V1

No

Vr

Error

Vr

Error

4083
4084

Figure 25.1/2: Macro Receive_Open_Cnf

2446

2447

macrodefinition Check_Reference
Macro to check a received destination reference or originating reference

Check_Ref1(1)

No Reference present? Yes

Yes Reference allowed for this AC? No

Yes Reference required for this AC? No

No Data type correct? Yes

OK

Error

Error

OK

4085
4086

Figure 25.1/3: Macro Check_Reference

2448

2449

4087 4088 4089

25.2 Macros to check the content of indication and confirmation primitives

25.2.1 Macro Check_Indication

4090 This macro checks that an indication includes all the parameters required by the application, no more and no less, and 4091 that the parameters are all within the correct range. It does not handle syntax checking; that is part of the function of the 4092 MAP protocol machine.

4093

25.2.2 Macro Check_Confirmation

4094 This macro checks whether a confirmation contains an error or a result, and if it contains a result whether the result is 4095 correctly formed.

2450

2451

macrodefinition Check_Indication
Macro to check the content of a MAP specifi c service indication

Check_Ind1(1)

Yes Data missing? No

Yes Unexpected data? No

Yes Unexpected value? No

Set User Error: Unexpected data value

Set User Error: Data missing

OK

Error

Error

4096
4097

Figure 25.2/1: Macro Check_Indication

2452

2453

macrodefinition Check_Confirmation
Macro to check the content of a MAP specifi c service confirm ation

Check_Cnf1(1)
Signals to/from the right are to/from the rem ote peer entity

Yes Provider error? No

Yes User error? No

MAP_ CLOSE_ req

Yes Data missing? No Provider Error

Yes Unexpected data? No User Error

Yes Unexpected value? No

OK

Data Error

4098
4099

Figure 25.2/2: Macro Check_Confirmation

2454

2455

4100 4101

25.3 The page and search macros

25.3.1 Macro PAGE_MSC

4102 This macro is called if an unstructured SS notification, a network-initiated unstructured SS request or a mobile 4103 terminating short message is to be delivered to the MS and the current location area identity of the MS is known in the 4104 VLR. 4105 If an MM-connection over the radio link already exists for the given IMSI, the MSC sets the access connection status 4106 according to the characteristics of the existing connection (i.e. RR-connection established, ciphering mode on/off, MM4107 connection existing and authenticated or not). 4108 If the MSC pages the MS and the VLR provided the TMSI, the MSC uses it to identify the MS at the radio interface; 4109 otherwise the MSC uses the IMSI. The MSC also uses the IMSI to determine the page group (see 3GPP TS 24.008 4110 [35]). 4111 4112 4113 4114

If the MS responds with a channel request containing an establishment cause which is not "answer to paging" the MSC sends a MAP_PAGE response primitive with user error Busy Subscriber. This gives priority to the mobile originating request. Alternatively, as an implementation option, the MSC may treat this as a response to paging, which gives priority to the mobile terminating request.

4115 If the paging is for MT SMS delivery and the VLR aborts the transaction before the MSC receives a response from the 4116 MS, the MSC aborts the transaction with the SMS-GMSC.

4117

25.3.2 Macro Search_For_MS_MSC

4118 This macro is called if an unstructured SS notification, a network-initiated unstructured SS request or a mobile 4119 terminating short message is to be delivered to the MS and the current location area identity of the MS is not known in 4120 VLR. 4121 4122 4123 4124

If an MM-connection over the radio link already exists for the given IMSI, the MSC returns a MAP_SEARCH_FOR_MS response containing the IMSI and current location area identification of the called MS to the VLR and sets the access connection status according to the characteristics of the existing connection (i.e. RRconnection established, ciphering mode on/off, MM-connection existing and authenticated or not).

4125 If the MSC pages the MS, the MSC uses the IMSI to identify the subscriber and the page group (see 3GPP TS 24.008 4126 [35]). 4127 4128 4129 4130

If the MS responds with a channel request containing an establishment cause which is not "answer to paging" the MSC sends a MAP_SEARCH_FOR_MS response with user error Busy Subscriber. This gives priority to the mobile originating request. Alternatively, as an implementation option, the MSC may treat this as a response to paging, which gives priority to the mobile terminating request.

4131 If the paging is for MT SMS delivery and the VLR aborts the transaction before the MSC receives a response from the 4132 MS, the MSC aborts the transaction with the SMS-GMSC.

2456

2457

macrodefinition Page_MSC
Macro in the MSC to page an MS for network initiated SS activity or SMS delivery

Page_MSC1(1)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise

MAP_ PAGE_ind

Check_ Indication

OK No LAI known? Yes

Error

Transaction still exists? Yes

No Set User Error: Unknown LAI 1

Yes MS connection exists? No Set User Error: System fai lure

In specified location area

A_Page_ Request

Set access connection status

MAP_PAGE_rsp MAP_DELIMITER_req

Wait_For_ Page_Response

OK

Error

A_Page_ Response

A_No_Page_ Response

A_CM_ Service_ Request

MAP_U_ ABORT_ ind

From SMS-GMSC

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

Set access connection status

Set User Error: Absent Subscriber

Set User Error: Busy Subscriber

MAP_U_ ABORT_ req

To SMS-GMSC

MAP_U_ ABORT_ req

OK

Null

Null

4133
4134

Figure 25.3/1: Macro Page_MSC

2458

2459

macrodefinition Search_For_MS_MSC
Macro in the MSC to search for an MS (i.e. page in all location areas) for network initiated SS activity or SMS delivery

Search_MSC1(1)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless m arked otherwise

MAP_SEARCH_ FOR_MS_ ind

Check_ Indication

OK Transaction still exists? Yes Yes

Error

Yes MS connection exists? No Set User Error: System fai lure

In all location areas

A_Page_ Request

MAP_SEARCH_FOR_MS_rsp MAP_DELIMITER_req

Wait_For_ Search_ Response

Error

A_Page_ Response

A_No_Page_ Response

A_CM_ Service_ Request

MAP_U_ ABORT_ ind

M AP_U_ABORT_ind, M AP_P_ABORT_ind, M AP_CLOSE_ind

From SMS-GMSC MAP_SEARCH_FOR_MS_rsp MAP_DELIMITER_req

Set access connection status; Set LAI

Set User Error: Absent Subscriber

Set User Error: Busy Subscriber

MAP_U_ ABORT_ req

To SMS-GMSC

MAP_U_ ABORT_ req

OK

Null

Null

4135
4136

Figure 25.3/2: Macro Search_for_MS_MSC

2460

2461

4137

25.4 Macros for handling an Access Request

4138 These macros are invoked when a MS accesses the network, e.g. to submit an MO short message or when responding to 4139 paging. The macros handle identification and authentication of the mobile subscriber as well as invocation of security 4140 related features (see 3GPP TS 42.009 [6]).

4141

25.4.1 Macro Process_Access_Request_MSC

the received subscriber identification (IMSI, TMSI); the CM service type, indicating the type of request; the status of the access connection, i.e. whether a connection to this MS already exists and if so, whether it is already authenticated and ciphered; the current location area id of the MS; and the CKSN received from the MS.

4142 Sheet 1: The MAP_PROCESS_ACCESS_REQUEST request includes the following parameters: 4143 4144 4145 4146 4147 4148

4149 Sheet 2, sheet 3: If the MSC receives an A_SETUP indication while it is waiting for further instructions from the VLR 4150 or for the acknowledgment of TMSI reallocation from the MS, the MSC saves the setup request for processing after 4151 control has returned from the macro Process_Access_Request_MSC to the calling process. 4152 Sheet 3: When the MSC is waiting for a possible instruction to allocate a new TMSI, a MAP_DELIMITER indication 4153 indicates that TMSI reallocation is not required. 4154 Sheet 3: If the MS sends a TMSI reallocation failure in response to the TMSI reallocation command, the MSC takes the 4155 OK exit; the VLR treats the lack of response as a provider error (see macro Process_Access_Request_VLR).

4156
4157 4158 4159 4160

25.4.2 Macro Process_Access_Request_VLR

Sheet 3: If the MSC does not send a positive response to the MAP_FORWARD_NEW_TMSI request, this is treated as a MAP_FORWARD_NEW_TMSI confirmation containing a provider error. The Macro takes the Error exit. If TMSI reallocation does not succeed, the old TMSI is frozen, to prevent it from being reallocated. In this case, both old and new TMSIs are regarded as valid.

4161

25.4.3 Macro Obtain_Identity_VLR

4162 This macro is invoked by the macro Process_Access_Request_VLR if the subscriber's identity is not known in the 4163 VLR. 4164 It is an operator option to allow or prevent retrieval of the IMSI without encryption.

4165

25.4.4 Process Update_Location_Child_VLR

4166 This process is started when the subscriber successfully accesses the network, e.g. for mobile originated short message 4167 submission, response to paging or supplementary services handling. 4168 The procedure Notify_gsmSCF is specified in 3GPP TS 23.078.

2462

2463

macrodefinition Process_Access_Request_MSC
Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity

Proc_Acc_Req_MSC1(3)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

Yes

VLR dialogue exists?

No

MAP_PROCESS_ACCESS_REQUEST_req MAP_DELIMITER_REQ

MAP_OPEN_REQ MAP_PROCESS_ACCESS_REQUEST_req MAP_DELIMITER_REQ

Receive_ Open_Cnf

OK Wait_For_ PAR_Result

Vr, Error

Error

Trace_ Subscriber_ Activity_MSC

Obtain_ IMSI_MSC

Obtain_ IMEI_MSC

MAP_PROCESS_ACCESS_REQUEST_cnf

OK Wait_For_ PAR_Result Wait_For_ PAR_Result

Error

Error

OK Wait_For_ PAR_Result Check_ Confirmation User error, Data error

Error

OK True Ciphering required False

Map error to Reject cause

Yes CM service type= Page response? No

A_CM _ SERVICE_ REJECT_req

A_CIPHER_ MODE_ COMM AND_ req

A_CM_ SERVICE_ ACCEPT_req

Error

Wait_For_ TMSI_ Reallocation

4169
4170

Figure 25.4/1 (sheet 1 of 3): Macro Process_Access_Request_MSC

2464

2465

macrodefinition Process_Access_Request_MSC
Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity Wait_For_ PAR_Result

Proc_Acc_Req_MSC2(3)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

A_CM_ SERVICE_ ABORT_ind

MAP_SET_ CIPHERING_ MODE_ind

Authenticate_ MSC

Check_ IMEI_MSC

MAP_U_ABORT_ind, MAP_CLOSE_i nd

OK MAP_U_ ABORT_ req Ciphering Required:= True Wait_For_ PAR_Result

Error

Error

OK Wait_For_ PAR_Result A_CM_ SERVICE_ REJECT_req

Error

Error

Wait_For_ PAR_Result

Error

Wait_For_ TMSI_ Reallocation

A_CM_ SERVICE_ ABORT_ind

A_SETUP_ind

Authenticate_ MSC

Check_ IMEI_MSC

MAP_U_ABORT_ind, MAP_CLOSE_i nd

OK MAP_U_ ABORT_ req

Error

Error

OK A_CM_ SERVICE_ REJECT_req

Wait_For_ PAR_Result

Error

Wait_For_ PAR_Result

Error

Error

4171
4172

Figure 25.4/1 (sheet 2 of 3): Macro Process_Access_Request_MSC

2466

2467

macrodefinition Process_Access_Request_MSC
Macro in the MSC to handle a request from the MS for access for SMS transfer or SS activity Wait_For_ TMSI_ Reallocation

Proc_Acc_Req_MSC3(3)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

MAP_ DELIMITER_ ind

MAP_FORWARD_NEW_TMSI_ind

A_TM SI_ REALLOC_ CMD_req

OK

Wait_For TMSI_Ack

A_CM_ SERVICE_ ABORT_ind

A_TM SI REALLOC_ COMPLETE_ ind

A_TM SI REALLOC_ FAILURE_ ind

A_SETUP_ind

MAP_U_ABORT_ind, MAP_CLOSE_i nd

OK

MAP_U_ ABORT_ req

MAP_FORWARD_NEW_TMSI_rsp MAP_DELIMITER_req

A_CM_ SERVICE_ REJECT_req

Error

OK

Error

4173
4174

Figure 25.4/1 (sheet 3 of 3): Macro Process_Access_Request_MSC

2468

2469

macrodefinition Process_Access_Request_VLR
Macro in the VLR to handle a request from the MS for access for SMS transfer or SS activity

Proc_Acc_Req_VLR1(3)
Signals to/from the left are to/from the MSC

MAP_PROCESS_ACCESS_REQUEST_ind

Check_Indication

OK No Identity known? Yes

Error

Obtain_ Identity_ VLR

OK Yes Identity= IMEI? No Error

Aborted

Error

No Set User Error: System Failure Authentication required? Yes

Authenticate_ VLR Unknown_Subscriber, Unidentified_Subscriber Set User Error: Unidentified subscriber

OK

Procedure_Error

Illegal_Subscriber

Aborted

Set User Error: System failure

Set User Error: Illegal subscriber

Error

MAP_PROCESS_ACCESS_REQUEST_rsp MAP_CLOSE_req

Error

4175
4176

Figure 25.4/2 (sheet 1 of 3): Macro Process_Access_Request_VLR

2470

2471

macrodefinition Process_Access_Request_VLR
Macro in the VLR to handle a request from the MS for access for SMS transfer or SS activity 2

Proc_Acc_Req_VLR2(3)
Signals to/from the l eft are to/fromthe MSC

Confirmed by radio contact:=True

Yes Location info confirmed in HLR? No Update_ Location_ Child_VLR

No Subscriber data confirmed by HLR? Yes No Roaming allowed in current LA? Yes Set User Error: Unidentified subscriber Set User Error: Roam not ing allowed in this LA

IMSI detached:= False

No 1 Yes Mobile Not Reachable Flag set?

Subscriber_ Present_VLR

No Tracing required? Yes Trace_ Subscriber_ Activity_VLR

No Ciphering required? Yes

MAP_SET_CIPHERING_MODE_req MAP_DELIMITER_req

4177
4178

Figure 25.4/2 (sheet 2 of 3): Macro Process_Access_Request_VLR

2472

2473

macrodefinition Process_Access_Request_VLR
Macro in the VLR to handle a request from the MS for access for SMS transfer or SS activity 3

Proc_Acc_Req_VLR3(3)
Signals to/from the left are to/from the MSC

No IMEI check required? Yes

Check_IMEI_ VLR

Error IMSI detached:= True

Aborted

OK Identity:= IMSI

Error

Set User Error: Illegal equimbent

MAP_PROCESS_ACCESS_REQUEST_rsp MAP_DELIMITER_req

Yes 1 TMSI reallocation required? No 4 OK No IMEI check required? Yes MAP_FORWARD_NEW_TMSI_req MAP_DELIMITER_req

Check_IMEI_ VLR Freeze old TMSI Error IMSI detached:= True Aborted OK Identity:= IMSI Wait_For_ TMSI_Ack

Error

Set User Error: Illegal equimbent

MAP_PROCESS_ACCESS_REQUEST_rsp MAP_DELIMITER_req

MAP_FORWARD_NEW_TMSI_cnf

OK

Check_ Confirmation

Provider Error

User Error, Data Error

OK

Unfreeze old TMSI

Error

OK

OK

4179
4180

Figure 25.4/2 (sheet 3 of 3): Macro Process_Access_Request_VLR

2474

2475

macrodefinition Obtain_Identity_VLR
Macro in the VLR to obtain a useable identity of the MS

Obt_ID_VLR1(1)

Yes Identity= IMSI? No

No Retrieval of IMSI allowed? Yes

Obtain_ IMSI_VLR

Error No

OK IMSI known? Yes

Aborted

Set User Error: Unidentified subscriber

Error

OK

Aborted

4181
4182

Figure 25.4/3: Macro Obtain_Identity_VLR

2476

2477

process Update_Location_Child_VLR
Child process in the VLR to update the location information in the HLR

ULC_VLR1(2)
Signals to/from the right are to/fromthe HLR

HLR address known? Yes

No

MAP_OPEN_req MAP_UPDATE_LOCATION_req MAP_DELIMITER_req

Delete subscriber record

Receive_ Open_Cnf

Vr Perform MAP_Vr dialogue

Error

OK Wait_For_ HLR_Response

Result

OK Set Event met: Location update to other VLR

Procedure Error, Aborted

Unknown Subscriber, Roam Not Allowed ing Delete subscriber record

Notify_gsm SCF

See 3GPP TS 23.078

Wait_For_ HLR_Response

Activate_ Tracing_VLR

Insert_Subs_ Data_VLR

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

Wait_For_ HLR_Response

Wait_For_ HLR_Response

MAP_ CLOSE_ req

Subscriber data confirmed by HLR:=False Location information confirm in HLR:=False ed

4183
4184

Figure 25.4/4 (sheet 1 of 2): Process Update_Location_Child_VLR

2478

2479

process Update_Location_Child_VLR
Child process in the VLR to update the location information in the HLR Wait_For_ HLR_Response

ULC_VLR2(2)
Signals from the right are from the HLR

MAP_UPDATE_LOCATION_cnf

Check_ Confirmation Provider Error, Data Error

OK

User Error

Subscriber data confirmed by HLR:=True; Location information confirm in HLR:=True ed

Subscriber data confirmed by HLR:=False; Location information confirm in HLR:=False ed

Set Event met: Location update to other VLR

Else Notify_gsm SCF See 3GPP TS 23.078 User error Roam Not Allowed, ing Unknown Subscriber

Delete subscriber record

Subscriber data confirmed by HLR:=False; Location information confirm in HLR:=False ed

4185
4186

Figure 25.4/4 (sheet 2 of 2): Process Update_Location_Child_VLR

2480

2481

4187

25.5 Authentication macros and processes

25.5.1 Macro Authenticate_MSC

4188 The following macros are used in the network in order to enable authentication of a mobile subscriber.

4189

4190 This macro is used by the MSC to relay a request for authentication transparently from the VLR to the MS, wait for a 4191 response from the MS and relay the response from the MS back to the VLR.

4192

25.5.2 Macro Authenticate_VLR

4193 This macro is used by the VLR to control the authentication of a subscriber. 4194 Sheet 1: The test "Received SRES=Expected SRES" indicates: 4195 4196 4197 4198

a comparison of the Signed RESult received from the MS with the Signed RESult received from the HLR, if GSM authentication is used (see 3GPP TS 43.020 [24]), or a comparison of the RESult received from the MS with the expected RESult received from the HLR, if UMTS authentication is used (see 3GPP TS 33.102).

4199

25.5.3 Macro Obtain_Authent_Params_VLR

4200 This macro is used by the VLR to request authentication vectors from the HLR. 4201 Sheet 1, sheet 2, sheet 3: It is an operator option whether to allow the re-use of old authentication triplets. 4202 Sheet 2, sheet 3: Old UMTS quintuplets shall not be re-used. 4203 Sheet 2: if the VLR requests more authentication vectors in the same dialogue, the subsequent 4204 MAP_SEND_AUTHENTIFICATION_INFO request has no parameters.

4205

25.5.4 Process Obtain_Authentication_Sets_VLR

4206 This process is initiated by the VLR to fetch authentication vectors from a subscriber's HLR independently of any other 4207 processing.

4208

25.5.6 Process Obtain_Authent_Sets_SGSN

4209 The procedure for authentication when the serving node is an SGSN is described in 3GPP TS 23.060 [104] and 3GPP 4210 TS 24.008 [35]. 4211 This Process is used by the SGSN to request authentication vectors from the HLR. 4212 Sheet 1, sheet 2: It is an operator option whether to allow the re-use of old authentication triplets. 4213 Sheet 2: Old UMTS quintuplets shall not be re-used.

4214

25.5.6 Process Obtain_Authent_Sets_HLR

4215 This process is used to provide authentication vectors (triplets or quintuplets) in response to a request from a VLR or an 4216 SGSN. 4217 Upon receipt of an authentication information request for a UMTS subscriber, the HLR shall return authentication 4218 quintuplets. If the user is a GSM subscriber, the HLR shall return authentication triplets.

2482

2483

4219 4220 25.5.7.1

25.5.7 Authentication Failure Reporting

General

4221 The Authentication Failure Report procedure is used to notify an HLR about the occurrence of an authentication failure 4222 in the SGSN or VLR. 4223 The message flows for this procedure are shown in figures 25.5/7& 25.5/8.

VLR MAP_AUTHENTICATION_FAILURE_REPORT

HLR

MAP_AUTHENTICATION_FAILURE_REPORT_ACK

4224
4225

Figure 25.5/7: Message Flow for Authentication Failure Report VLR to HLR

SGSN MAP_AUTHENTICATION_FAILURE_REPORT

HLR

MAP_AUTHENTICATION_FAILURE_REPORT_ACK

4226
4227

Figure 25.5/8: Message Flow for Authentication Failure Report SGSN to HLR

4228 25.5.7.2 4229 25.5.7.3 4230 25.5.7.4

Process in the VLR Process in the SGSN Process in the HLR

2484

2485

macrodefinition Authenticate_MSC
Macro in the MSC to relay the signalling for authentication between the M and the VLR S

Auth_MSC1(1)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

MAP_AUTHENTCATE_ind

Check_ Indication

OK

Error

A_AUTHENTICATE_req

MAP_AUTHENTCATE_rsp MAP_DELIMITER_req

Wait_For_ MS_Response

OK

A_AUTHENTICATE_cnf

A_CM_ SERVICE_ ABORT_ind

MAP_U_ABORT_ind, MAP_CLOSE_i nd

No Error? Yes

Set User Error

MAP_AUTHENTCATE_rsp MAP_DELIMITER_req

MAP_U_ ABORT_ req

OK

Error

Error

4231
4232

Figure 25.5/1: Macro Authenticate_MSC

2486

2487

macrodefinition Authenticate_VLR
Macro in the VLR to authenticate an MS 2

Auth_VLR1(2)
Signals to/from the left are to/from the MSC

Yes Authentication vectors available? No

Obtain_Authent_ Params_VLR

Null

OK MAP_ AUTHENTICATE_req MAP_DELIMITER_req

Unknown_Subscriber

Procedure_Error

Null

Unknown_ Subscriber

Procedure_ Error

Wait_For Response_ From_MSC

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_AUTHENTICATE_cnf

User Error, Provider Error, Data Error

Check_ Confirmation

OK No Received SRES= Expected SRES? Yes

No More authentication vectors required? Yes

No More authentication vectors required? Yes

Obtain_Authent_ Sets_VLR

Obtain_Authent_ Sets_VLR

Null

OK

4233
4234

Figure 25.5/2 (sheet 1 of 2): Macro Authenticate_VLR

2488

2489

macrodefinition Authenticate_VLR
Macro in the VLR to authenticate an MS 1

Auth_VLR2(2)

Yes Identity= IMSI? No

Retry with IMSI? Yes

No

Obtain_ IMSI_VLR

Aborted

Error Procedure_ Error

OK IMSI known? Yes Yes

Null

Unidentified_ subscriber

IMSI matches TMSI? No

Identity:= IMSI

Illegal_ Subscriber

4235
4236

Figure 25.5/2 (sheet 2 of 2): Macro Authenticate_VLR

2490

2491

macrodefinition Obtain_Authent_Params_VLR
Macro in the VLR to obtain authentication parameters from the HLR

Obt_Auth_Par_VLR1(3)
Signals to/from the right are to/from the HLR

MAP_OPEN_req MAP_SEND_AUTHENTICATION_INFO_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ Authentication_ Info

Vr Perform MAP Vr dialogue

Error

Procedure_ Error

Yes Successful resul t? No

No Em pty resul t? Yes

No Error=Unknown subscriber? Yes

Re-use old triplets? No

Yes

Unknown_ Subscriber

Procedure_ Error

OK

4237
4238

Figure 25.5/3 (sheet 1 of 3): Macro Obtain_Authent_Params_VLR

2492

2493

macrodefinition Obtain_Authent_Params_VLR
Macro in the VLR to obtain authentication parameters from the HLR Wait_For_ Authentication_ Info

Obt_Auth_Par_VLR2(3)
Signals to/from the right are to/from the HLR

MAP_SEND_AUTHENTICATION_INFO_cnf

Check_ Confirmation

OK

User Error

Provider Error MAP_ CLOSE_ req No

Data Error

Unknown subscriber ? Yes Re-use old vectors? No Yes

Wait_For_ Close_Or_ Delimiter

Unknown_ Subscriber

Procedure_ Error

OK

MAP_ CLOSE_ ind

MAP_ DELIMITER_ ind

No

Authentication vectors received? Yes

More vectors required? No

Yes

MAP_ CLOSE_ req

MAP_SEND_AUTHENTICATION_INFO_req MAP_DELIMITER_req

OK

OK

Wait_For_ Authentication_ Info

4239
4240

Figure 25.5/3 (sheet 2 of 3): Macro Obtain_Authent_Params_VLR

2494

2495

macrodefinition Obtain_Authent_Params_VLR
Macro in the VLR to obtain authentication parameters from the HLR Wait_For_ Authentication_ Info

Obt_Auth_Par_VLR3(3)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the HLR

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

MAP_U_ ABORT_ req

MAP_ CLOSE_ req

Yes

Re-use old vectors? No

Null

OK

Procedure_ Error

4241
4242

Figure 25.5/3 (sheet 3 of 3): Macro Obtain_Authent_Params_VLR

2496

2497

process Obtain_Authent_Sets_VLR
Process in the VLR to obtain authentication sets from the HLR

Obt_Auth_Sets_VLR1(1)

Obtain_Authent_ Params_VLR OK, Null, Unknown_Subscriber, Procedure_Error

4243
4244

Figure 25.5/4: Process Obtain_Authent_Sets_VLR

2498

2499

process Obtain_Authent_Sets_SGSN
Process in the SGSN to obtain authentication sets from the HLR

Obt_Auth_Sets_SGSN1(2)
Signals to/from the left are to/from the application process in the SGSN; signals to/from the right are to/from the HLR

Idle

Authentication parameter request

Yes Unknown HLR? No Set negative response: Unknown HLR MAP_OPEN_req MAP_SEND_AUTHENTICATION_INFO_req MAP_DELIMITER_req

Authentication parameter negative response OK Wait_For_ Authentication_ Info

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

Error

Idle

Yes Successful resul t? No Em pty resul t? No Error=Unknown subscriber? Yes Yes 1 No

No

Re-use old triplets?

Yes

Authentication parameter negative response

Authentication parameter ack

Idle

Idle

4245
4246

Figure 25.5/5 (sheet 1 of 2): Process Obtain_Authent_Sets_SGSN

2500

2501

process Obtain_Authent_Sets_SGSN
Process in the SGSN to obtain authentication sets from the HLR Wait_For_ Authentication_ Info

Obt_Auth_Sets_SGSN2(2)
Signals to/from the left are to/from the application process in the SGSN; signals to/from the right are to/from the HLR

MAP_SEND_AUTHENTICATION_INFO_cnf

Check_ Confirmation

OK

User Error No Unknown subscriber ? Yes No

Provider Error, Data Error

Re-use old vectors? Yes

Authentication parameter negative response

Authentication parameter ack

Wait_For_ Close_Or_ Delimiter

Idle

Idle

MAP_ CLOSE_ ind

MAP_ DELIMITER_ ind

No

Authentication vectors received? Yes

More vectors required? No

Yes

MAP_ CLOSE_ req

MAP_SEND_AUTHENTICATION_INFO_req MAP_DELIMITER_req

Authentication parameter ack

Wait_For_ Authentication_ Info

Idle

4247
4248

Figure 25.5/5 (sheet 2 of 2): Process Obtain_Authent_Sets_SGSN

2502

2503

process Obtain_Authent_Sets_HLR
Process in the HLR to handle a request from the VLR for authentication sets

Obt_Auth_Sets_HLR1(2)
Signals to/from the left are to/from the VLR or the SGSN

Null

Receive_ Open_Ind

Error

Vr Perform MAP Vr dialogue

OK Wait_For_ Service_ Primitive

MAP_ NOTICE_ ind

MAP_SEND_AUTHENTICATION_INFO_ind

Check_ Indication

OK MAP_ CLOSE_ req

Error

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_CLOSE_req

Null

Null

Null

Null

4249
4250

Figure 25.5/6 (sheet 1 of 2): Process Obtain_Authent_Sets_HLR

2504

2505

process Obtain_Authent_Sets_HLR
Process in the HLR to handle a request from the VLR for authentication sets 1

Obt_Auth_Sets_HLR2(2)
Signals to/from the left are to/from the VLR or the SGSN

Requesting node type present? No

Yes

Requesting node type=SGSN AND Network access mode= Non-GPRS only No

Yes

Set Diagnostic: GPRS subscription unknown Yes

Requesting node type=VLR AND Network access mode= GPRS only No

Set User Error: Unknown subscriber

Check_ Avail able_ Vectors

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_CLOSE_req

Segmentation allowed and supported and needed? Yes

No Null

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_CLOSE_req

Obtain_Vectors_ From_AuC

To be stored for later use; see 3GPP TS 33.102 (UMTS) or 3GPP TS 43.020 (GSM)

Null

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_DELIMITER_req

Wait_For_ Service_ Primitive

4251
4252

Figure 25.5/6 (sheet 2 of 2): Process Obtain_Authent_Sets_HLR

2506

2507

process Obtain_Authent_Sets_HLR
Process in the HLR to handle a request from the VLR for authentication sets 1

Obt_Auth_Sets_HLR2(2)
Signals to/from the left are to/from the VLR or the SGSN

Requesting node type present? No

Yes

Requesting node type=SGSN AND Network access mode= Non-GPRS only No

Yes

Set Diagnostic: GPRS subscription unknown Yes

Requesting node type=VLR AND Network access mode= GPRS only No

Set User Error: Unknown subscriber

Check_ Avail able_ Vectors

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_CLOSE_req

Segmentation allowed and supported and needed? Yes

No Null

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_CLOSE_req

Obtain_Vectors_ From_AuC

To be stored for later use; see 3GPP TS 33.102 (UMTS) or 3GPP TS 43.020 (GSM)

Null

MAP_SEND_AUTHENTICATION_INFO_rsp MAP_DELIMITER_req

Wait_For_ Service_ Primitive

4253
4254

Figure 25.5/7: Procedure Check_Available_Vectors

2508

2509

process Report_Authentication_Failure_VLR
Process in the VLR to send an authentication failure report to the HLR

Rep_Auth_Fail_VLR1(1)
Signals to/from the left are to/from the application process in the VLR; signals to/from the right are to/from the HLR

Idle

Authentication failure report

MAP_OPEN_req MAP_AUTHENTICATION_FAILURE_REPORT_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Error

Idle

MAP_ NOTICE_ ind

MAP_AUTHENTICATION_FAILURE_REPORT_cnf, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ CLOSE_ req

Idle

Idle

4255
4256

Figure 25.5/9: Process Report_Authentication_Failure_VLR

2510

2511

process Report_Authentication_Failure_SGSN
Process in the SGSN to send an authentication failure report to the HLR

Rep_Auth_Fail_SGSN1(1)
Signals to/from the left are to/from the applicati on process in the SGSN; signals to/from the right are to/from the HLR

Idle

Authentication failure report

MAP_OPEN_req MAP_AUTHENTICATION_FAILURE_REPORT_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Error

Idle

MAP_ NOTICE_ ind

MAP_AUTHENTICATION_FAILURE_REPORT_cnf, MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ CLOSE_ req

Idle

Idle

4257
4258

Figure 25.5/10: Process Report_Authentication_Failure_SGSN

2512

2513

process Note_Authentication_Failure_HLR
Process in the HLR to handle an authentication failure report from the VLR or SGSN

Note_Auth_Fail_HLR1(1)
Signals to/from the left are to/from the VLR or SGSN; signals to/from the right are to/from the applicati on process in the HLR

Idle

Receive_ Open_Ind

OK

Vr, Error

Wait_For_ Report

Idle

MAP_AUTHENTICATION_FAILURE_REPORT_ind

MAP_ NOTICE_ ind

MAP_P_ ABORT_ ind

Check_ Indication

MAP_ CLOSE_ req

OK No Subscriber known? Yes

Error

Idle

Authentication failure report

Set User Error: Unknown Subscriber

MAP_AUTHENTICATION_FAILURE_REPORT_rsp MAP_CLOSE_req

Idle

4259
4260

Figure 25.5/11: Process Note_Authentication_Failure_HLR

2514

2515

4261

25.6 IMEI Handling Macros

4262 The following macros are used in the network in order to enable handling and checking of the mobile equipment 4263 identity.

4264

25.6.1 Macro Check_IMEI_MSC

4265 This macro is used by the MSC to receive a request from the VLR, relay it to the EIR, and pass the result from the EIR 4266 back to the VLR. 4267 Sheet 1: If the dialogue with the EIR drops back to a previous protocol version and the EIR returned an error, the MSC 4268 relays the error to the VLR in the MAP_CHECK_IMEI response. If the dialogue with the EIR failed, or the EIR 4269 returned a badly formed result, the MSC sends a System Failure error to the VLR in the MAP_CHECK_IMEI response.

4270

25.6.2 Macro Check_IMEI_VLR

4271 This macro is used by the VLR to control the check of a mobile equipment's IMEI. It may also be used to request the 4272 BMUEF from the EIR.

4273

25.6.3 Process Check_IMEI_SGSN

4274 This process is used by the SGSN to control the check of a mobile equipment's IMEI. It may also be used to request the 4275 BMUEF from the EIR.

4276

25.6.4 Process Check_IMEI_EIR

4277 This process is used by the EIR to obtain the status of a mobile equipment, upon request from the MSC or from the 4278 SGSN. It may also be used to obtain the BMUEF.

4279

25.6.5 Macro Obtain_IMEI_MSC

4280 This macro is used by the MSC to respond to a request from the VLR to provide the IMEI.

4281

25.6.6 Macro Obtain_IMEI_VLR

4282 This macro is used by the VLR to obtain the IMEI from the MSC.

2516

2517

macrodefinition Check_IMEI_MSC
Macro in the MSC to check the IMEI of the MS, and report the result to the VLR

Chk_IMEI_MSC1(2)
Wait_For_IMEI

Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless marked otherwise No

MAP_ CHECK_ IMEI_ind

A_IDENTITY_ RESPONSE_ ind

Yes BM UEF requested? 1

No IMEI available?

Yes

No IMEISV available?

Yes

A_IDENTITY_ REQUEST_ req

Requested identity=IMEI

A_IDENTITY_ REQUEST_ req

Requested identity=IMEISV

Wait_For_IMEI

Wait_For_IMEI

To EIR

MAP_OPEN_req MAP_CHECK_IMEI_req MAP_DELIMITER_req

Wait_For_ EIR_Response

Receive_ Open_Cnf

Error MAP_ CHECK_ IMEI_cnf No From EIR

Vr Requested Info includes Equipment Status? Yes

OK Wait_For_ EIR_Response

Check_ Confirmation Provider Error, Data Error

Perform MAP Vr dialogue

User Error

OK Add IMEI to service response to VLR

Yes Set User Error: System failure Successful result? No

MAP_CHECK_IMEI_rsp MAP_DELIMITER_req

Set User Error: System fai lure

Set User Error

Add IMEI to service response to VLR

OK

MAP_CHECK_IMEI_rsp MAP_DELIMITER_req

OK

4283
4284

Figure 25.6/1 (sheet 1 of 2): Macro Check_IMEI_MSC

2518

2519

macrodefinition Check_IMEI_MSC
Macro in the MSC to check the IMEI of the MS, and report the result to the VLR Wait_For_ EIR_Response

Chk_IMEI_MSC2(2)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR unless m arked otherwise

A_CM_ RELEASE_ ind

MAP_U_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

From EIR

MAP_U_ ABORT_ req

To EIR

MAP_U_ ABORT_ req

To EIR

MAP_ CLOSE_ req

To EIR

MAP_U_ ABORT_ req

A_DISC_ req

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind from EIR

Error

A_CLEAR_ CMD_req

Set User Error: System failure

Error

MAP_CHECK_IMEI_rsp MAP_DELIMITER_req

OK

4285
4286

Figure 25.6/1 (sheet 2 of 2): Macro Check_IMEI_MSC

2520

2521

macrodefinition Check_IMEI_VLR
Macro in the VLR to instruct the MSC to check the IMEI of the MS and handle the report of the result

Chk_IMEI_VLR1(1)
Signals to/from the left are to/from the MSC; signals to/from the right are to/from the OMC

MAP_CHECK_IMEI_req MAP_DELIMITER_req

Wait_For_ Check_IMEI_ REesul t

MAP_ CHECK_ IMEI_cnf

MAP_U_ABORT_rind, MAP_CLOSE_ind

O&M notification required? Yes

No Aborted

OM_ALARM_ req

No Service granted? Yes

OK

Error

4287
4288

Figure 25.6/2: Macro Check_IMEI_VLR

2522

2523

process Check_IMEI_SGSN
Process in the SGSN to check the IMEI of an MS

Chk_IMEI_SGSN1(2)
Signals to/from the left are to/from the application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the EIR Idle

Check IMEI

No BM UEF requested?

Yes

No IMEI available?

Yes

Yes IMEISV available?

No

MAP_OPEN_req MAP_CHECK_IMEI_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error No

Vr Requested Info includes Equipment status? Yes

OK Wait_For_ EIR_Response

Perform MAP Vr dialogue

Provider Error, Data Error Result?

Success

User Error

Set negative response: System fai lure

Check IMEI ack

Idle

4289
4290

Figure 25.6/3 (sheet 1 of 2): Process Check_IMEI_SGSN

2524

2525

process Check_IMEI_SGSN
Process in the SGSN to check the IMEI of an MS Wait_For_ EIR_Response

Chk_IMEI_SGSN2(2)
Signals to/from the left are to/from the application process in the SGSN (see 3GPP TS 23.060); signals to/from the right are to/from the EIR

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ CHECK_ IMEI_cnf

MAP_ NOTICE_ ind

Set negative response: System fai lure

MAP_ CLOSE_ req

Check_ Confirmation

Provider Error, Data Error

User Error

OK O&M notification required? Yes No Set negative response: System fai lure

To OMC

OM_ALARM_ req

No Service granted? Yes

Check IMEI ack

Check IMEI negative response

Idle

Idle

4291
4292

Figure 25.6/3 (sheet 2 of 2): Process Check_IMEI_SGSN

2526

2527

process Check_IMEI_EIR
Process in the EIR to check the IMEI of an MS

Chk_IMEI_EIR1(1)
Signals to/from the left are to/from the MSC or the SGSN

Idle

Receive_ Open_Ind

OK Wait_For Service_ Primitive

Error

Vr Perform MAP Vr dialogue

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ CHECK_ IMEI_ind

Idle

MAP_ CLOSE_ req

Check_ Indication

Equipm ent status requested? Yes

No

Error

OK Yes IMEI known? No Set User Error: Unknown Equipm ent

Equipm ent status supported?

Idle

Yes

No

Set equipment status

No MAP_CHECK_IMEI_rsp MAP_CLOSE_req BM UEF requested? Yes

Idle

BM UEF supported?

Yes

No

Set BMUEF

MAP_CHECK_IMEI_rsp MAP_CLOSE_req

Idle

4293
4294

Figure 25.6/4: Process Check_IMEI_EIR

2528

2529

macrodefinition Obtain_IMEI_MSC
Macro in the MSC to obtain the IM EI from the MS

Obt_IMEI_MSC1(1)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

MAP_ OBTAIN_ IMEI_ind

Yes IMEI available? No

A_IDENTITY_ REQUEST_ req

Requested identity=IMEI

Wait_For_IMEI

A_IDENTITY_ RESPONSE_ ind

A_CM_ RELEASE_ ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

Set IM EI

Set User Error: System failure

Error

MAP_OBTAIN_IMEI_rsp MAP_DELIMITER_req

OK

4295
4296

Figure 25.6/5: Macro Obtain_IMEI_MSC

2530

2531

macrodefinition Obtain_IMEI_VLR
Macro in the VLR to instruct the MSC to obtain the IM of the MS EI and handle the report of the result

Obt_IMEI_VLR1(1)
Signals to/from the left are to/from the MSC

MAP_OBTAIN_IMEI_req MAP_DELIMITER_req

Wait_For_IMEI

MAP_ OBTAIN_ IMEI_cnf

MAP_U_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation User Error, Provider Error, Data Error

OK

OK

Error

Aborted

4297
4298

Figure 25.6/6: Macro Obtain_IMEI_VLR

2532

2533

4299 4300

25.7 Insert Subscriber Data macros and processes

25.7.1 Macro Insert_Subs_Data_VLR

4301 This macro is used by any procedure in the VLR that triggers the reception of subscriber data (e.g. Update Location or 4302 Restore Data).

4303

25.7.2 Macro Insert_Subs_Data_SGSN

4304 This macro is used by any procedure that triggers the reception of subscriber data (e.g. Update GPRS Location ).

4305

25.7.3 Process Insert_Subs_Data_Stand_Alone_HLR

4306 This process is used by HLR to transfer subscriber data to the VLR in a stand alone mode, i.e. in a separate dialogue. 4307 This is done whenever a change of subscriber data is performed either by the operator or by the subscriber and this 4308 change has to be reported to the VLR. 4309 Sheet 1: The HLR may wait for each MAP_INSERT_SUBSCRIBER_DATA request to be acknowledged before it 4310 sends the next request, or it may handle the requests and the confirmations in parallel. 4311 4312 4313 4314 4315

Sheet 1, sheet 2: If the VLR has indicated that it does not support a service or feature (e.g. Closed User Group or Advice Of Charge Charging Level) which the HLR operator regards as essential for the subscriber, the macro Wait_for_Insert_Subs_Data_Cnf takes the Replace_Service exit; the HLR sets the Roaming Restriction Due To Unsupported Feature flag to roaming restricted and sends Roaming Restriction Due To Unsupported Feature in a subsequent MAP_INSERT_SUBSCRIBER_DATA request.

4316 Sheet 1, sheet 2: If the HLR operator does not regard the unsupported service or feature as essential for the subscriber 4317 but the macro Wait_for_Insert_Subs_Data_Cnf takes the Replace_Service exit, the HLR sends the data for a 4318 replacement service in a subsequent MAP_INSERT_SUBSCRIBER_DATA request. 4319 Sheet 2: It is an operator option whether to repeat the download of subscriber data if the VLR returns an error response. 4320 The number of repeat attempts and the interval between them is also an operator option, depending on the error 4321 response from the VLR. 4322 4323 4324 4325 4326 4327 4328 4329

If subscriber data for CAMEL Phase 2 or later services are sent to a VLR which does not support the appropriate phase of CAMEL, the service behaviour may be unpredictable or incorrect. The HLR should therefore ensure that at the conclusion of a stand alone Insert Subscriber data procedure the data in the VLR do not require a capability that the VLR does not have. Possible mechanisms to ensure this are described in 3GPP TS 23.078 [98]. The HLR should send a Forwarded-to number which is not in E.164 international format to the VLR only when the HLR has ascertained that the VLR supports CAMEL Phase 2 or later. Thus, the ISD message containing the Forwarded-to number which is not in E.164 international format shall be sent to the VLR only if the HLR previously received confirmation from the VLR at Location Update that CAMEL Phase 2 or later is supported.

4330

25.7.4 Process Insert_GPRS_Subs_Data_Stand_Alone_HLR

4331 This process is used by the HLR to transfer subscriber data from the HLR to the SGSN in a stand alone mode, i.e. in a 4332 separate dialogue. This is done whenever a change of subscriber data is performed either by the operator or by the 4333 subscriber and this change has to be reported to the SGSN. 4334 Sheet 1: The HLR may wait for each MAP_INSERT_SUBSCRIBER_DATA request to be acknowledged before it 4335 sends the next request, or it may handle the requests and the confirmations in parallel. 4336 4337 4338 4339

Sheet 1, sheet 2: If the SGSN has indicated that it does not support a service or feature which the HLR operator regards as essential for the subscriber, the macro Wait_for_Insert_GPRS_Subs_Data_Cnf takes the Replace_Service exit; the HLR sets the Roaming Restricted In SGSN Due To Unsupported Feature flag to roaming restricted and sends Roaming Restricted In SGSN Due To Unsupported Feature in a subsequent MAP_INSERT_SUBSCRIBER_DATA request.

2534

2535

4340 Sheet 1, sheet 2: If the HLR operator does not regard the unsupported service or feature as essential for the subscriber 4341 but the macro Wait_for_Insert_GPRS_Subs_Data_Cnf takes the Replace_Service exit, the HLR sends the data for a 4342 replacement service in a subsequent MAP_INSERT_SUBSCRIBER_DATA request. 4343 Sheet 2: It is an operator option whether to repeat the download of subscriber data if the SGSN returns an error 4344 response. The number of repeat attempts and the interval between them is also an operator option, depending on the 4345 error response from the SGSN.

4346

25.7.5 Macro Wait_for_Insert_Subs_Data_Cnf

4347 This macro is used by any process or macro that describes the handling in the HLR of the transfer of subscriber data to 4348 the VLR (e.g. Update Location or Restore Data).

4349

25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf

4350 This macro is used by any process or macro that describes the handling in the HLR of the transfer of subscriber data to 4351 the SGSN (e.g. Update GPRS Location).

4352

25.7.7 Process Send_Insert_Subs_Data_HLR

4353 This process is used by any process or macro in the HLR where a MAP_INSERT_SUBSCRIBER_DATA request is 4354 sent to the VLR or to the SGSN.

2536

2537

macrodefinition Insert_Subs_Data_VLR
Macro in the VLR to handle an Insert Subscriber Data request from the HLR

Ins_Sub_Dat_VLR1(1)
Signals to/from the right are to/from the HLR

MAP_INSERT_SUBSCRIBER_DATA_ind

Check_ Indication

OK All received services & features supported? No

Error

Yes

Update subscriber data

Update subscriber data for supported services & features

Set parameters for unsupported services & features

MSC area restricted due to regional subscription?

No

Yes

Set network node area restricted

MAP_INSERT_SUBSCRIBER_DATA_rsp MAP_DELIMITER_req

4355
4356

Figure 25.7/1: Macro Insert_Subs_Data_VLR

2538

2539

macrodefinition Insert_Subs_Data_SGSN
Macro in the VLR to handle an Insert Subscriber Data request from the HLR

Ins_Sub_Dat_SGSN1(1)
Signals to/from the right are to/from the HLR

MAP_INSERT_SUBSCRIBER_DATA_ind

Check_ Indication

OK All received services & features supported? No

Error

Yes

Update subscriber data

Update subscriber data for supported services & features

Set parameters for unsupported services & features

SGSN area restricted due to regional subscription?

No

Yes

Set network node area restricted

MAP_INSERT_SUBSCRIBER_DATA_rsp MAP_DELIMITER_req

4357
4358

Figure 25.7/2: Macro Insert_Subs_Data_SGSN

2540

2541

process Insert_Subs_Data_Stand_Alone_HLR
Process in the HLR to open a dialogue and transfer subscriber data to the VLR 5

ISD_SA_HLR1(2)
Signals to/from the left are to/from the VLR

MAP_OPEN_req MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK Wait_For_ Insert_ Subs_Data_Cnf

Error

Abort Error MAP_U_ ABORT_ req

OK

Replace_Service Set replacement service(s)

No

All data inserted? Yes

Count:=0

Send_Insert_ Subs_Data_HLR

Count:= Count+1

No

All data inserted? Yes

4359
4360

Figure 25.7/3 (sheet 1 of 2): Process Insert_Subs_Data_Stand_Alone_HLR

2542

2543

process Insert_Subs_Data_Stand_Alone_HLR
Process in the HLR to open a dialogue and transfer subscriber data to the VLR 2

ISD_SA_HLR2(2)
Signals to/from the left are to/from the VLR

Wait_For_ Insert_ Subs_Data_Cnf

Replace_Service Count:= Count-1

OK Count:= Count-1

Error MAP_U_ ABORT_ req

Abort

Set replacement service(s)

No Count>0? Yes 1

No 4 2 Yes Network node area restricted received OR Roaming Restriction due to Unsupported Feature?

MSC Area restricted:= Not restricted

MSC Area restricted:= Restricted

MAP_ CLOSE_ req

Repeat update of VLR? Yes Start repetition timer

No

Wait_For_ Repetition_ Timer_Expiry

Repetition timer expired

Internal

4361
4362

Figure 25.7/3 (sheet 2 of 2): Process Insert_Subs_Data_Stand_Alone_HLR

2544

2545

process Insert_GPRS_Subs_Data_Stand_Alone_HLR
Process in the HLR to open a dialogue and transfer subscriber data to the SGSN 5

IGSD_SA_HLR1(2)
Signals to/from the left are to/from the SGSN

MAP_OPEN_req MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ Insert_GPRS_ Subs_Data_Cnf

Vr, Error

Abort Error MAP_U_ ABORT_ req

OK

Replace_Service Set replacement service(s)

No

All data inserted? Yes

Count:=0

Send_Insert_ Subs_Data_HLR

Count:= Count+1

No

All data inserted? Yes

4363
4364

Figure 25.7/4 (sheet 1 of 2): Process Insert_GPRS_Subs_Data_Stand_Alone_HLR

2546

2547

process Insert_GPRS_Subs_Data_Stand_Alone_HLR
Process in the HLR to open a dialogue and transfer subscriber data to the SGSN 2

IGSD_SA_HLR2(2)
Signals to/from the left are to/from the SGSN

Wait_For_ Insert_GPRS_ Subs_Data_Cnf

Replace_Service Count:= Count-1

OK Count:= Count-1

Error MAP_U_ ABORT_ req

Abort

Set replacement service(s)

No Count>0? Yes 1

No 4 2 Yes Network node area restricted received OR Roaming Restricted in SGSN due to Unsupported Feature?

SGSN Area restricted:= Not restricted

SGSN Area restricted:= Restricted

MAP_ CLOSE_ req

Repeat update of SGSN? Yes Start repetition timer

No

Wait_For_ Repetition_ Timer_Expiry

Repetition timer expired

Internal

4365
4366

Figure 25.7/4 (sheet 2 of 2): Process Insert_GPRS_Subs_Data_Stand_Alone_HLR

2548

2549

macrodefinition Wait_For_Insert_Subs_Data_Cnf
Macro in the HLR to receive and process the MAP_INSERT_SUBSCRIBER_DATA confirmation

WF_ISD_Cnf1(1)
Signals to/from the left are to/from the VLR

Wait_For_ ISD_Cnf

MAP_INSERT_SUBSCRIBER_DATA_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error User Error, Data Error Service unsupported in VLR? No OK Yes Abort

MAP_ CLOSE_ req

Error

Yes Ignor e? No

Replace service in VLR? No

Yes

HLR internal action

OK

Replace_Service

4367
4368

Figure 25.7/5: Macro Wait_for_Insert_Subs_Data_Cnf

2550

2551

macrodefinition Wait_For_Insert_GPRS_Subs_Data_Cnf
Macro in the HLR to receive and process the MAP_INSERT_SUBSCRIBER_DATA confirmation

WF_IGSD_Cnf1(1)
Signals to/from the left are to/from the SGSN

Wait_For_ IGSD_Cnf

MAP_INSERT_SUBSCRIBER_DATA_cnf

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind

MAP_ NOTICE_ ind

Check_ Confirmation Provider Error User Error, Data Error Service unsupported in SGSN? No OK Yes Abort

MAP_ CLOSE_ req

Error

Yes Ignor e? No

Replace service in SGSN? No

Yes

HLR internal action

OK

Replace_Service

4369
4370

Figure 25.7/6: Macro Wait_for_Insert_GPRS_Subs_Data_Cnf

2552

2553

process Send_Insert_Subs_Data_HLR
Process in the HLR to send a MAP_INSERT_SUBSCRIBER_DATA request, independently of the invoking process

Send_ISD_HLR1(1)
Signals to/from the left are to/from the VLR or SGSN

MAP_INSERT_SUBSCRIBER_DATA_req MAP_DELIMITER_req

4371
4372

Figure 25.7/7: Process Send_Insert_Subs_Data_HLR

2554

2555

4373 4374

25.8 Request IMSI Macros

25.8.1 Macro Obtain_IMSI_MSC

4375 This macro describes the handling of the request received from the VLR to provide the IMSI of a subscriber (e.g. at 4376 Location Updating).

4377

25.8.2 Macro Obtain_IMSI_VLR

4378 This macro describes the way VLR requests the MSC the IMSI of a subscriber (e.g. at Location Updating).

2556

2557

macrodefinition Obtain_IMSI_MSC
Macro in the MSC to retrieve the IMSI from the MS and return it to the VLR

Obt_IMSI_MSC1(1)
Signals to/from the left are to/from the MS; signals to/from the right are to/from the VLR

MAP_ PROVIDE_ IMSI_ind

A_IDENTITY_ REQUEST_ req

Requested identity=IMSI

Wait_For_ IMSI

A_IDENTITY_ RESPONSE_ ind

A_CM_ RELEASE_ ind

MAP_U_ABORT_ind, MAP_CLOSE_ind

Set IM SI

Set User Error: Absent Subscriber

Error

MAP_PROVIDE_IMSI_rsp MAP_DELIMITER_req

OK

4379
4380

Figure 25.8/1: Macro Obtain_IMSI_MSC

2558

2559

macrodefinition Obtain_IMSI_VLR
Macro in the VLR to instruct the MSC to obtain the IM of the MS SI and handle the report of the result

Obt_IMSI_VLR1(1)
Signals to/from the left are to/from the MSC

MAP_PROVIDE_IMSI_req MAP_DELIMITER_req

Wait_For_IMSI

MAP_ PROVIDE_ IMSI_cnf

MAP_U_ABORT_ind, MAP_CLOSE_ind

Check_ Confirmation User Error, Data Error

Provider Error

OK

Aborted

OK

Error

Aborted

4381
4382

Figure 25.8/2: Macro Obtain_IMSI_VLR

2560

2561

4383 4384

25.9 Tracing macros

25.9.1 Macro Trace_Subscriber_Activity_MSC

4385 This macro shows the handling in the MSC for a request from the VLR to trace the activity of a subscriber.

4386

25.9.2 Macro Trace_Subscriber_Activity_VLR

4387 This macro is called during the handling of subscriber activity in the VLR to activate tracing if necessary.

4388

25.9.3 Macro Trace_Subscriber_Activity_SGSN

4389 This macro is called during the handling of subscriber activity in the SGSN to activate tracing if necessary.

4390

25.9.4 Macro Activate_Tracing_VLR

4391 This macro shows the handling in the VLR for a request from the HLR to activate tracing for a subscriber.

4392

25.9.5 Macro Activate_Tracing_SGSN

4393 This macro shows the handling in the SGSN for a request from the HLR to activate tracing for a subscriber.

4394

25.9.6 Macro Control_Tracing_With_VLR_HLR

4395 This macro shows the handling in the HLR to activate tracing in the VLR if it is required during a dialogue between the 4396 VLR and the HLR

4397

25.9.7 Macro Control_Tracing_With_SGSN_HLR

4398 This macro shows the handling in the HLR to activate tracing in the SGSN if it is required during a dialogue between 4399 the SGSN and the HLR

2562

2563

macrodefinition Trace_Subscriber_Activity_MSC
Macro in the MSC to mark the subscriber for tracing

Tr_Sub_Act_MSC1(1)
Signals to/from the right are to/from the VLR

MAP_TRACE_SUBSCRIBER_ACTIVITY_ind

Check_ Indication

OK

Error

Start Activity Tracing

4400
4401

Figure 25.9/1: Macro Trace_Subscriber_Activity_MSC

2564

2565

macrodefinition Trace_Subscriber_Activity_VLR
Macro in the VLR to star t tracing in the MSC if required

Tr_Sub_Act_VLR1(1)
Signals to/from the left are to/from the MSC

False

Subscriber tracing active True

MAP_TRACE_SUBSCRIBER_ACTIVITY_req

4402
4403

Figure 25.9/2: Macro Trace_Subscriber_Activity_VLR

2566

2567

macrodefinition Trace_Subscriber_Activity_SGSN
Macro in the SGSN to star t tracing if required

Tr_Sub_Act_SGSN1(1)

False

Subscriber tracing active True

Start activity tracing

4404
4405

Figure 25.9/3: Macro Trace_Subscriber_Activity_SGSN

2568

2569

macrodefinition Activate_Tracing_VLR
Macro in the VLR to handle a request from the HLR to activate tracing

Act_Tr_VLR1(1)
Signals to/from the right are to/from the HLR

MAP_ACTIVATE_TRACE_M ODE_ind

Check_ Indication

Error No

OK

Subscriber known? Yes

Tracing supported?

Yes Tracing buffer full? No Yes

No

Set User Error: Unidentified subscriber

Subscriber tracing active:= True

Set User Error: Tracing buffer full

Set User Error: Facility not supported

MAP_ACTIVATE_TRACE_M ODE_rsp MAP_DELIMITER_req

4406
4407

Figure 25.9/4: Macro Activate_Tracing_VLR

2570

2571

macrodefinition Activate_Tracing_SGSN
Macro in the SGSN to handle a request from the HLR to activate tracing

Act_Tr_SGSN1(1)
Signals to/from the right are to/from the HLR

MAP_ACTIVATE_TRACE_M ODE_ind

Check_ Indication

Error No

OK

Subscriber known? Yes

Tracing supported?

Yes Tracing buffer full? No Yes

No

Set User Error: Unidentified subscriber

Subscriber tracing active:= True

Set User Error: Tracing buffer full

Set User Error: Facility not supported

MAP_ACTIVATE_TRACE_M ODE_rsp MAP_DELIMITER_req

4408
4409

Figure 25.9/5: Macro Activate_Tracing_SGSN

2572

2573

macrodefinition Control_Tracing_With_VLR_HLR
Macro in the HLR to activate tracing in the VLR

Ctrl_Tr_VLR_HLR1(1)
Signals to/from the left are to/from the VLR

False Subscriber tracing active in HLR True

True Subscriber tracing active in VLR False

No Subscriber in HPLM area? N Yes

OK

MAP_ACTIVATE_TRACE_M ODE_req MAP_DELIMITER_req

Wait_For_ATM_ Result

MAP_ACTIVATE_TRACE_M ODE_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd,

Check_ Confirmation

MAP_ CLOSE_ req

OK Subscriber tracing active in VLR:= True

User Error, Data Error Subscriber tracing active in VLR:= False

Provider Error Subscriber tracing active in VLR:= False

Error

OK

Error

4410
4411

Figure 25.9/6: Macro Control_Tracing_With_VLR_HLR

2574

2575

macrodefinition Control_Tracing_With_SGSN_HLR
Macro in the HLR to activate tracing in the SGSN

Ctrl_Tr_SGSN_HLR1(1)
Signals to/from the left are to/from the SGSN

False Subscriber tracing active in HLR True

True Subscriber tracing active in SGSN False

No Subscriber in HPLM area? N Yes

OK

MAP_ACTIVATE_TRACE_M ODE_req MAP_DELIMITER_req

Wait_For_ATM_ Result

MAP_ACTIVATE_TRACE_M ODE_cnf

MAP_ NOTICE_ ind

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd,

Check_ Confirmation

MAP_ CLOSE_ req

OK Subscriber tracing active in SGSN:= True

User Error, Data Error Subscriber tracing active in SGSN:= False

Provider Error Subscriber tracing active in SGSN:= False

Error

OK

Error

4412
4413

Figure 25.9/7: Macro Control_Tracing_With_SGSN_HLR

2576

2577

4414 4415

25.10 Short Message Alert procedures

25.10.1 Process Subscriber_Present_VLR

4416 The VLR invokes the process Subscriber_Present_VLR when the mobile subscriber becomes active. The general 4417 description of the short message alert procedures is in subclause 23.4 of the present document.

4418

25.10.2 Process SubscriberPresent_SGSN

4419 The SGSN invokes the process Subscriber_Present_SGSN when it receives a Page response, a GPRS Attach request or 4420 a Routing area update request message (3GPP TS 24.008 [35]). The general description of the short message alert 4421 procedures is in subclause 23.4 of the present document.

4422

25.10.3 Macro Alert_Service_Centre_HLR

4423 The HLR invokes the macro Alert_Service_Centre_HLR when Service Centre(s) are to be alerted.

4424

25.10.4 Process Alert_SC_HLR

4425 It is an operator option to resend the MAP_ALERT_SERVICE_CENTRE request to the SMS-IWMSC if the alert is 4426 unsuccessful. The number of repeat attempts and the interval between them is also an operator option. The service 4427 centre address should be purged from the MWD list if the alert is consistently unsuccessful.

2578

2579

process Subscriber_Present_VLR
Process in the VLR to report to the HLR that the subscriber has becom reachable e

Sub_Pres_VLR1(1)
Signals to/from the right are to/from the HLR

No MNRF set? Yes

MAP_OPEN_req MAP_READY_FOR_SM_req MAP_DELIMITER_req

Receive_ Open_Cnf

Vr Perform MAP Vr dialogue

OK Wait_For_ HLR_Response

Error

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_READY_FOR_SM_cnf

Check_ Confirmation User Error, Data Error, Provider Error

OK

Clear MNRF

4428
4429

Figure 25.10/1: Process Subscriber_Present_VLR

2580

2581

process Subscriber_Present_SGSN
Process in the SGSN to report to the HLR that the subscriber has becom reachable e

Sub_Pres_SGSN1(1)
Signals to/from the right are to/from the HLR

No MNRG set? Yes

MAP_OPEN_req MAP_READY_FOR_SM_req MAP_DELIMITER_req

Receive_ Open_Cnf

OK Wait_For_ HLR_Response

Vr, Error

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_READY_FOR_SM_cnf

Check_ Confirmation User Error, Data Error, Provider Error

OK

Clear MNRG

4430
4431

Figure 25.10/2: Process Subscriber_Present_SGSN

2582

2583

macrodefinition Alert_Service_Centre_HLR
Macro in the HLR to alert all Short Message Service centres with entries in the MWD list

Al_Serv_Ctr_HLR1(1)

All MWD list entries processed? No

Yes

Alert_SC_HLR

4432
4433

Figure 25.10/3: Macro Alert_Service_Centre_HLR

2584

2585

process Alert_SC_HLR
Process in the HLR to alert a Short Message Service centre Wait_For Repeat_Ti m er_ Expiry

ASC_HLR1(1)
Signals to/from the right are to/from the SM S-IWMSC

Internal

Repeat timer expired

MAP_OPEN_req MAP_ALERT_SERVICE_CENTRE_req MAP_DELIMITER_req

Receive_ Open_Cnf

Error

OK Wait_For_ Alert_SC_ Response

Vr Perform M Vr AP dialogue

MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_i nd

MAP_ NOTICE_ ind

MAP_ALERT_SERVICE_CENTRE_cnf

MAP_ CLOSE_ req

Check_ Confirmation

User Error, Data Error, Provider Error No Remove SC address from MWD list? Yes

OK

Yes Repeat attempt? No

Remove SC address from MWD list

Start repeat timer

Wait_For Repeat_Ti m er_ Expiry

4434
4435

Figure 25.10/4: Process Alert_SC_HLR

4436 4437

Annex A (informative): ASN.1 Cross-reference listing and fully expanded sources

4438 The ASN.1 Cross-reference listing and the fully expanded ASN.1 sources of the MAP protocol are provided for 4439 information at http://www.3gpp.org/ftp/Specs/archive/29_series/29.002/ASN.1/

2586

2587

4440

Annex B (informative): Void

2588

2589

4441 4442

Annex C (informative): Message Segmentation Mechanisms

4443 Various segmentation mechanisms are in use to overcome the problem where a MAP parameter carried in an Invoke, 4444 Result (or Error) component is too long to fit into a single SCCP UDT message. These mechanisms are:

4445

C.1 SCCP segmentation

Signalling Connection Control Part, Signalling System no. 7 ITU-T recommendation (07/96) Q.711 to Q.716 (White Book SCCP).

4446 Instead of one UDT message several XUDT messages are used according to 4447 4448

4449 This mechanism may be used for all MAP messages. If no segmentation mechanism at the TCAP or MAP level is 4450 available, this is the only remaining possibility. 4451 This mechanism has no impact on the MAP provider level and above; the MAP provider sees the parameter as being 4452 sent in a single segment. 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463

It should be noted that not all SCCP transit nodes (world wide) currently support the transfer of XUDT messages. Therefore XUDT messages may be lost without notice, depending on the route the message takes. The routes which successive messages take between two end points can differ because of load balancing. It is therefore recommended that this mechanism is used only for: a) messages which do not cross PLMN boundaries (when the PLMN operator ensures that all SCCP transit nodes within his PLMN support White Book SCCP) b) messages with low priority i.e. loss of the message does not result in serious misoperation. It should be noted that the decision whether or not a message crosses PLMN boundaries needs to be taken at the MAP application level; it is therefore based on the message's operation code rather than on the SCCP called party address, i.e. only messages which never cross PLMN boundaries due to the type of message (SendIdentification, SendRoutingInfo without OR, AnyTimeInterrogation, ...) can be regarded as not crossing PLMN boundaries.

4464

C.2 TCAP segmentation

C.2.1 Empty Begin
In a dialogue with AC version >1 the first forward message (Begin) must contain a Dialogue Portion. Instead of sending the Dialogue Portion and the Component Portion in the first forward message, an empty Begin (i.e. without a Component Portion) is sent, followed (after successful dialogue establishment) by a Continue message which can carry a longer Component Portion since no Dialogue Portion is present in the second forward message.

4465 At the TCAP level the following segmentation mechanisms are available:

4466
4467 4468 4469 4470

4471
4472 4473 4474 4475

C.2.2 Empty Continue

In a dialogue with AC version >1 the first backward message (Continue / End) must contain a Dialogue Portion. Instead of sending the Dialogue Portion and the Component Portion in the first backward message, an empty Continue (i.e. without a Component Portion) is sent, followed by a Continue/End message which can carry a longer Component Portion since no Dialogue Portion is present in the second backward message.

4476

C.2.3 TC-Result-NL

4477 A Result component may be segmented into one or several Result-Not-Last components followed by a Result-Last 4478 component. As specified in subclause 15.6.3, the MAP user parameter shall be split so that each segment is compatible 4479 with the type defined for the parameter of the result of the associated operation.
2590

2591

4480 Note that this segmentation mechanism runs the risk that the message carrying the Result-Last component arrives 4481 before the message carrying a Result-Not-Last component which results in failure. The use of SCCP class 1 "Sequence 4482 guaranteed", which raises the chance of in sequence delivery, is recommended.

4483

C.3 MAP Segmentation

C.3.1 Invoke without explicit indication
An Invoke component may be segmented into several Invoke components. These may be sent in burst mode (in which case SCCP class 1 is recommended) or in acknowledged mode. The receiving node does not get an indication of whether or not more segments will be received, so it must not close the dialogue. The MAP user parameter shall be split so that each segment is compatible with the type defined for the parameter of the invoke of the associated operation.

4484 At the MAP level the following segmentation mechanisms are available:

4485
4486 4487 4488 4489

4490
4491 4492 4493 4494

C.3.2 Invoke with explicit indication

An Invoke component may be segmented into several Invoke components sent in acknowledged mode. Each component contains at the MAP level an indication of whether or not subsequent components will follow. The receiving node terminates the dialogue when the last component is received. The MAP user parameter shall be split so that each segment is compatible with the type defined for the parameter of the invoke of the associated operation.

4495
4496 4497 4498 4499

C.3.3 Result
A Result (last) component may be segmented into several Result (last) components sent in acknowledged mode where a new (empty) Invoke component serves as an acknowledgment. The last segment is not acknowledged. The MAP user parameter shall be split so that each segment is compatible with the type defined for the parameter of the result of the associated operation.

2592

2593

4500 The following tables show the applicability of the mechanisms described above: 4501
Parameter ResumeCallHandlingArg SCCPsegmentation allowed

AC Version 4:
Empty Begin not allowed Empty Continue n.a. TCResultNL n.a. Invoke without indication not allowed Invoke with indication recommended Result n.a.

4502 4503
Parameter InsertSubscriberDataArg SendIdentificationRes PrepareHO-Arg PrepareHO-Res ProcessAccessSignalling-Arg ForwardAccessSignalling-Arg PrepareSubsequentHO-Arg PrepareSubsequentHO-Res SendAuthenticationInfoRes ProvideSubscriberInfoRes AnyTimeInterrogationRes AnyTimeModificationRes AnyTimeSubscriptionInterrogationRes noteSubscriberDataModifiedArg SendRoutingInfoRes MO-ForwardSM-Arg MT-ForwardSM-Arg

AC Version 3:
SCCPsegmentation risky allowed allowed allowed allowed allowed allowed allowed risky allowed allowed allowed allowed allowed allowed risky risky Empty Begin not allowed n.a. not allowed n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. n.a. not allowed n.a. recommended recommended Empty Continue n.a. not allowed n.a. recommended n.a. n.a. n.a. n.a not allowed not allowed not allowed not allowed not allowed n.a. not allowed n.a. n.a. TC-Result-NL n.a. not allowed n.a. not recommended n.a. n.a. n.a. not recommended not allowed not recommended not recommended recommended recommended n.a. recommended n.a. n.a. Invoke without indication recommended n.a. not allowed n.a. not allowed not allowed not allowed n.a. n.a. n.a. n.a. n.a. n.a. not allowed n.a. not allowed not allowed

Invoke indica

n.a n.a n.a n.a

n.a n.a n.a n.a

n.a n.a

n.a

n.a n.a recomme n.a n.a n.a

4504 4505
Parameter InsertSubscriberDataArg SendIdentificationRes SendAuthenticationInfoRes ForwardSM-Arg PrepareHO-Res SCCPsegmentation risky allowed risky risky allowed

AC Version 2:
Empty Begin not allowed n.a. n.a. recommended n.a. Empty Continue not allowed not allowed not allowed n.a. recommended TC-Result-NL n.a. not recommended not recommended n.a. not recommended Invoke without indication recommended n.a. n.a. not allowed n.a. Invoke with indication n.a. n.a. n.a. n.a. n.a.

Resu

n.a. not allowe not allowe n.a. not allowe

4506 4507
Parameter InsertSubscriberDataArg SentParameterList SCCPsegmentation risky risky Empty Begin n.a. n.a.

AC Version 1:
Empty Continue n.a. n.a. TC-Result-NL n.a. recommended Invoke without indication recommended n.a. Invoke with indication n.a. n.a. Result n.a. not allowed

4508

2594

3GPP

2595

4509 In the tables above the keywords "recommended", "allowed", "risky", "not recommended", "not allowed" and "n.a." are 4510 used as follows: 4511 "recommended" 4512 indicates that the normative part of this specification explicitly specifies the use of this mechanism for the parameter in 4513 question; 4514 "allowed" 4515 indicates that the normative part of this specification allows the use of this mechanism for the sending node and 4516 mandates support of this mechanism for the receiving node; 4517 "risky" 4518 indicates that the mechanism is "allowed".However, the use of this mechanism for the parameter in question may result 4519 in serious misoperation because SCCP transit nodes are not guaranteed to support XUDT messages. 4520 "not recommended" 4521 indicates that the normative part of this specification does not explicitly specify the use of this mechanism for the 4522 parameter in question. 4523 "not allowed" 4524 indicates that the normative part of this specification implicitly prohibits the use of this mechanism for the parameter in 4525 question. 4526 "n.a." 4527 indicates that the mechanism is not applicable for the parameter in question. 4528

2596

3GPP

2597

4529

Annex D (informative): Void

2598

3GPP

2599

4530 4531

Annex E (informative): Change History

SMG# 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 TDoc N2-99227 N2-99578 N2-99233 N2-99269 N2-99650 N2-99250 N2-99628 N2-99677 N2-99228 N2-99585 N2-99515 N2-99520 N2-99548 3C99-468 N2-99519 N2-99461 N2-99583 N2-99676 3C99-206 N2-99906 N2-99908 N2-99910 N2-99934 N2-99936 N2-99938 N2-99952 N2-99956 N2-99964 N2-99A19 N2-99A45 N2-99B57 N2-99C27 N2-99C78 N2-99D06 N2-99D33 SPEC 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 VERS 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.0.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 REV PHAS CAT SUBJECT NEW_VERS WORKITEM E A002 3 R98 A Use of E interface 3.1.0 A003 R98 B Introduction of TIF-CSI for Call 3.1.0 Deflection A004 R98 A Clarification in ASN.1 encoding of O3.1.0 CSI and T-CSI A005 R98 C Introduction of MSISDN in USSD 3.1.0 operation A006 R98 A Modification of the O-CSI ASN.1 3.1.0 structure A007 R98 A Adding of MAP_DELIMITER_req to the 3.1.0 Status report operation A008 R98 A Correction to the Purge MS "Detailed 3.1.0 procedure in the HLR" A009 R98 A Adding of MNP-indicator to the SRI ack 3.1.0 A010 R98 F New subscription options for call 3.1.0 forwarding A011 R98 C Adding the support of ANSI SCCP 3.1.0 which is required in North America (World Zone 1) A012 R98 A Introduction of 3-digit MNCs correction 3.1.0 A013 R98 F Export of NAEA-CIC 3.1.0 A014 R98 D Clarification to text to identify how the 3.1.0 LSA data relevant in the current VPLMN can be determined A015 R97 F Alignment with 04.80 3.1.0 A016 R98 A VBS data 3.1.0 A017 R98 F Introduction of Data Missing error to the 3.1.0 Resume Call Handling A018 R97 F Removal of 3-digit MNCs 3.1.0 A019 R98 A Corrections of mapping from MAP 3.1.0 service to TC service A020 R98 B Introduction of UUS service to Resume 3.1.0 Call Handling 021 R99 A Clarification on VLR CAMEL 3.2.0 CAMEL Phase 2 Subscription Info 022 R99 A Clarification on 3.2.0 CAMEL Phase 2 DestinationNumberCriteria 023 R99 A Removal of TDP-Criteria from RCH 3.2.0 CAMEL Phase 2 025 R99 A Various corrections related to GGSN3.2.0 GPRS HLR Interface. 034 R99 A Update Location handling for GPRS3.2.0 GPRS only subscription 035 R99 A Correction of OP & AC definitions for 3.2.0 GPRS NoteMS-PresentForGPRS 036 R99 A Removal of redundant information from 3.2.0 UUS RCH 026 R99 A OR capability IE in PRN 3.2.0 TEI 024 1 R99 A GMSC-CAMEL phase 2 support IE in 3.2.0 CAMEL Phase 2 PRN 028 R99 A Alignment of 29.002 with 02.67 3.2.0 eMLPP 029 1 R99 B Non-CAMEL IST implementation 3.2.0 IST 027 2 R99 B Addition of the information elements 3.2.0 Pre-Paging and the ASN.1 definitions for Prepaging 042 R99 A Clarification on 'Supported CAMEL 3.2.0 CAMEL Phase 2 Phases' in ISD ack 044 R99 A Editing error correction on VLR 3.2.0 SoLSA capabilities 043 1 R99 A Addition of exception handling to the 3.2.0 GPRS CancellationType 046 R99 A Clarification of LR-REJECT cause 3.2.0 TEI corresponding to RoamingRestrictionDueTo UnsupportedFeature 047 R99 Clarification of returning the MSISDN in 3.2.0 MNP SRIack CR

05

N2-99D35

29.002

3.1.0

2600

3GPP

2601
SMG# 06 06 06 06 06 06 06 06 06 06 06 06 TDoc N2-99G06 N2-99G18 N2-99G50 N2-99J88 N2-99K12 N2-99K24 N2-99K52 N2-99K58 N2-99K60 N2-99L20 N2-99J52 N2-99J92 SPEC 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 VERS 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.3.0 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 N2B00043 6 N2B00031 9 N2B00046 1 N2B00037 5 29.002 29.002 29.002 29.002 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 3.3.1 048 059 063 066 079 080 083 084 086 087 089 090 094 095 099 100 101 102 103 104 105 107 110 1 1 5 1 2 1 1 2 1 2 1 CR 033 032 070 075 077 069 060 045 050 073 074 068 REV PHAS CAT SUBJECT NEW_VERS WORKITEM E 3 R99 C Introduction of the Super-Charger 3.3.0 Super Charger Concept in TS 29.002 2 R99 C Introduction of White Book SCCP in 3.3.0 TEI MAP R99 A Addition of GGSN number for the 3.3.0 GPRS SRIforGPRS 1 R99 B Introduction of Follow Me 3.3.0 Follow Me R99 A Use of SSN for GPRS 3.3.0 GPRS R99 A Correction of the USSD procedure in 3.3.0 USSD & Follow Me the HLR. 1 R99 C MAP Impacts for Location Services 3.3.0 Location Services (LCS) 4 R99 B Authentication Enhancements 3.3.0 Security 5 R99 C QoS-Subscribed field modification 3.3.0 QoS enhancements 1 R99 C Introduction of CAMEL Phase 3 in 3.3.0 CAMEL Phase 3 3GPP TS 29.002 R99 D Restructuring of MAP Location 3.3.0 TEI Management Procedures for the Circuit Switched Domain R99 B Update of SDLs to support Super3.3.0 Super-Charger Charger New version created to fix a CR 3.3.1 implementation error 5 1 4 5 4 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 B B B B C F A B D A F B C C B C B F B F C D B Introduction of Multicall Alternative solution for ALR MNP Database Mismatch Addition of the FTN-AddressString Correction of SS Invocation Notification for CCBS Corrections to ATSI, ATM, NCSD Privacy notification/verification for call related privacy class Addition of CS Allocation/retention priority Editorial cleanup of 29.002 Correction of LSA information Security interworking between release 99 and pre-99 MSC/VLRs Improving GPRS charging efficiency QoS-Subscribed field enhancements RANAP support on the E-interface UMTS Authentication Support of 3G Handover, including Multicall Introduction of Service Area Identification Clarification on Authentication Info Retrieval Addition of UMTS security to MAP B interface Re-Synchronisation Info Introduction of additional service parameters for inter-system handover Removal of architectural information from clause 4 Introduction of Authentication Failure Report 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 Multicall CAMEL phase 3 MNP Call Forwarding Enhancements CAMEL Phase 3 CAMEL Phase 3 Location Services (LCS) QoS enhancements TEI SoLSA Security GPRS QoS enhancements Handover Security Multicall TEI Security Security UMTS Security Handover TEI Security

N2B00045 29.002 6 N2A00002 29.002 3 N2B00004 29.002 6 N2B00014 2 N2B00014 4 N2B00010 0 N2B00006 7 N2B00011 3 N2B00012 0 N2B00032 2 N2B00019 1 N2B00046 6 N2B00037 2 N2B00038 0 N2B00033 0 N2B00024 4 N2B00032 4 N2B00028 1 N2000454 29.002 29.022 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002

2602

3GPP

2603
SMG# 07 07 07 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 08 09 09 09 09 09 09 N4000543 N4000539 N4000491 N4000540 N4000541 N4000744 TDoc N2B00035 7 N2B00047 0 N2B00047 2 N4000098 N4000094 N4000089 N4000073 N4000050 N4000100 N4000321 N4000068 N4000320 N4000209 N4000211 N4000357 N4000217 N4000326 N4000264 N4000392 N4000276 N4000349 N4000278 N4000378 N4000293 N4000294 N4000374 N4000407 SPEC 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 VERS 3.3.1 3.3.1 3.3.1 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.4.0 3.5.0 4.0.0 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 152 153 158 159 160 161 2 1 1 CR 111 112 113 115 117 118 120 121 122 124 125 127 130 132 133 134 135 138 139 141 142 143 144 145 146 149 148 4 1 1 1 1 1 1 2 3 REV PHAS CAT SUBJECT NEW_VERS WORKITEM E R99 B Use of MAP private extensions to 3.4.0 TEI implement region-specific requirements R99 A Prioritisation of MAP application 3.4.0 ASCI Phase 2 context related to VGCS/VBS R99 F Correction of SS-Codes for LCS 3.4.0 LCS 1 1 1 1 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R00 R00 R00 R00 R00 R00 R00 R00 F D A A A A F A F F F C C A F F A F A B F A A C D A F F A B Minor corrections to CAMEL3 NSDC/ATM/ATSI information flows Using DSD to delete CCBS-B from the subscriber Indication in PRN of support of Long FTNs QoS-Subscribed field enhancements Correction of introduction of additional service parameters for inter-system handover Proposed information flow on NSDC CAMEL Subscription Info Clarification to GMLC List definition Optionality of parameters in d-csi and in sms-csi Version 3 tags for handover messages Correction of version handling at dialogue establishment Various corrections and/or cleanup to 29.002 Correction of errors in Figure 25.1/1: Macro Receive_Open_Ind Addition of charging characteristics per PDP context Clarification of SAI-ack segmentation procedure Indication of unsupported position method Clarification for ReportSMDeliveryStatus operation Addition of a parameter in the subsequent Handover from UMTS to GSM with Multicall Editorial correction to MSC-A handover SDLs Use of NAM parameter with MAPINSERT-SUBSCRIBER-DATA service between HLR and SGSN Addition of state attributes in Forward group call signalling New user error target cell outside group call area in MAP Prepare Handover message Correction to the description of MAPMO-Forward-Short-Message service Changes to MAP for secure transport of MAP messages Version 4.0.1 created to allow inclusion of automatic update of Annexes A and B and of section 17 Clarifications for secure MAP transport Generalization of version handling text in clause 18.2.4 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 3.5.0 4.0.0 4.0.1 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 Core Network Security TEI TEI Handover Security Security CAMEL Phase 3 CCBS CF enhancements QoS enhancements Handover/Relocation CAMEL Phase 3 CAMEL Phase 3 LCS CAMEL Phase 3 Handover TEI TEI TEI TEI Security LCS GPRS Multicall Multicall GPRS ASCI ASCI TEI Security

Deletion of informative Annexe C

Aligning 29.002 with 25.413 (UTRAN Iu Interface RANAP Signalling) AUTS and AUTN parameter length

Clarification on Authentication Failure Report ack

2604

3GPP

2605
SMG# 09 09 09 09 09 09 09 09 09 10 10 10 10 10 10 10 10 10 11 11 11 11 11 11 11 11 11 11 11 11 TDoc N4000666 N4000777 N4000788 N4000747 N4000750 N4000736 N4000772 N4000751 N4000779 N4000912 N4000908 N4001069 N4001071 N4000921 N4001073 N4001076 N4001089 N4001095 N4010036 N4010276 N4010033 N4010198 N4010058 N4010287 N4010375 N4010261 N4010465 N4010360 N4010361 N4010362 SPEC 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 VERS 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.0.1 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.2.0 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 4.2.1 CR 163 174 176 178 180 182 184 186 188 166 191 193 196 198 200 208 211 212 206 215 217 222 224 231 232 234 236 246 247 248 1 1 2 2 1 2 1 1 1 3 1 2 1 1 REV PHAS CAT SUBJECT E 1 R00 A Correction on Location Information 2 1 1 2 R00 R00 R00 R00 R00 R00 R00 R00 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 A A A A A A A A A A A A A A A A A A B A B A B B B B A A A Optionality of parameters in GPRS-CSI Correction to QoS indication Clarification of use of Radio Resource Information Correction to MSC-A handover SDLs Removal of LSAIdentity from NoteMMEventArg LCS Support for CAMEL Phase 3 Correction to MSC-A handover SDLs Clarification for segmentation of D-CSI and SMS-CSI Corrections and clarifications for USSD procedures on the HLR - gsmSCF interface NEW_VERS 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.1.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.0 4.2.1 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 WORKITEM CAMEL phase 3 CAMEL phase 3 LCS Handover TEI CAMEL phase 3 LCS TEI CAMEL phase 3 USSD CAMEL phase 3 USSD Handover Handover Handover Handover CAMEL phase 3 Handover LCS ODB enhancements Multicall LCS GPRS R97 LCS LCS SS7IP SEC1-EHCS Camel 3 CAMEL 3 CAMEL 3

Corrections of ISD data structure for CAMEL phase 3 USSD Corrections for Follow Me GSM to 3G Handover: MAP parameter Target Cell ID ASN.1 description of targetCellId IMSI in MAP_PREPARE_HANDOVER Alignment of the Target RNC-ID Export of GSN-Address data type Transport of long RANAP messages on MAP-E interface Automatic update of annexes A and B Correction to LCS application context Add parameters to ISD and SRI for GPRS to handle ODB for PS Correction to maximum number of RAB's PS domain support for LCS Release 4 Failure of Update GPRS Location when HLR is not reachable Extension of call related privacy class for LCS Release 4 Maximum number of LCS Clients MAP over IP according to SIGTRAN Requesting node type in authentication set request Adding EXPORT definition for LSAIdentity Removing duplicate parameters from ss-CSI Correction to description of SSCSI in HLR to VLR information flow

2606

3GPP

2607
SMG# 11 TDoc N4010365 N4010393 N4010428 N4010446 N4010484 N4010728 N4010730 N4010733 N4010735 N4010739 NP010247 SPEC 29.002 VERS 4.2.1 CR 250 REV PHAS CAT E Rel-4 A SUBJECT NEW_VERS 4.3.0 WORKITEM Handover

11 11 11

29.002 29.002 29.002

4.2.1 4.2.1 4.2.1

252 258 260

Rel-4 Rel-4 Rel-4

A A A

11 12

29.002 29.002

4.2.1 4.3.0

262 239

1 4

Rel-4 Rel-4

A A

GSM to UMTS handover: addition of MAP parameter RNC ID Clarification of the use of multicall bearer information Adding EXPORT definition for GeographicalInformation Failure of Authentication Parameter GPRS when HLR is not reachable Correction to D-CSI Addition of selected UMTS algorithm indication to the handover procedures Addition of allowed GSM algorithms indication to the handover procedures Addition of allowed UMTS algorithm indication to the handover procedures Addition of selected GSM algorithm indication to the handover procedures Addition of radio resource list to the handover procedures Addition of GSM channel type and GSM chosen channel indications to handover procedures Add support in MAP for all shapes defined in 23.032 Correction to description of RNCId parameter Correction to Encryption Information and Integrity Protection parameters Essential drawbacks on services due to introduction of SuperCharger function Introduction of selected Rab-id to the Process Access Signalling operation Mistake in the definition of Authentication Failure Report Application Context Add support in MAP for Ellipsoid Point Security Header modification Additional Parameters in Authentication Failure Report MS presence notification procedure for LCS Component level granularity of protection Corrupted headers fixed Clarifications on long forwardedto numbers

4.3.0 4.3.0 4.3.0

Multicall Camel 3 GPRS R97

4.3.0 4.4.0

CAMEL 3 Handover

12

29.002

4.3.0

241

Rel-4

4.4.0

Handover

12

29.002

4.3.0

244

Rel-4

4.4.0

Handover

12

29.002

4.3.0

245

Rel-4

4.4.0

Handover

12 12

29.002 29.002

4.3.0 4.3.0

254 256

2 3

Rel-4 Rel-4

A A

4.4.0 4.4.0

Multicall Handover

12 12 12

N4010787 N4010633 N4010635 N4010767 N4010741 N4010673 N4010551 N4010778 N4010785 N4010783 N4010790 N4010840

29.002 29.002 29.002

4.3.0 4.3.0 4.3.0

264 270 272

3 1 1

Rel-4 Rel-4 Rel-4

A A A

4.4.0 4.4.0 4.4.0

LCS Handover Handover

12

29.002

4.3.0

279

Rel-4

4.4.0

TEI

12

29.002

4.3.0

283

Rel-4

4.4.0

Multicall

12

29.002

4.3.0

285

Rel-4

4.4.0

SEC

12 12 12 12 12

29.002 29.002 29.002 29.002 29.002 29.002

4.3.0 4.3.0 4.3.0 4.3.0 4.3.0 4.4.0 4.4.1

266 168 267 268 289 5 3 3 2

Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4

A C C F F

4.4.0 4.4.0 4.4.0 4.4.0 4.4.0 4.4.1 4.5.0

LCS Security SEC1 - EHCS LCS1 SEC1

13

29.002

290

Rel-4

TEI4

2608

3GPP

2609
SMG# 13 13 13 13 13 TDoc N4010929 N4010930 N4010958 N4010970 N4010976 N4011017 N4011019 N4010845 N4011031 N4011043 N4011285 N4011198 N4011074 N4011091 N4011094 N4011097 N4011227 N4011173 N4011175 N4011177 N4011190 N4011209 N4011211 N4011262 N4011273 N4011437 N4011433 SPEC 29.002 29.002 29.002 29.002 29.002 VERS 4.4.1 4.4.1 4.4.1 4.4.1 4.4.1 CR 291 292 295 302 306 REV PHAS CAT E 1 Rel-4 F 2 2 2 Rel-4 Rel4 Rel-4 Rel-4 F F F A SUBJECT NEW_VERS 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 WORKITEM LCS1 LCS1 LCS1 SEC1-EHCS CAMEL3

Corrections for Deferred MT-LR Clarifications on SupportedLCSCapabilitySets Corrections on the introduction of LCS for PS domain Additional SGSN related values to Access Type Addition of data type definitions to EXPORT statements for the usage in CAP Minimum MAP application context for intersystem MSC handover from GSM to UMTS Minimum MAP application context for intersystem MSC handover from UMTS to GSM Correction on the SDL of NW initiated USSD operations Editorial Clean up Clarification on LCS parameters in MAP Handling of linked operations in the MAP protocol machine Corrections on the SDL diagrams for LCS Indication of deletion of CSI in Notify Subscriber Data Change Correct length of AddGeographicalInformation

13

29.002

4.4.1

307

Rel-4

4.5.0

Handover

13

29.002

4.4.1

309

Rel-4

4.5.0

Handover

13 13 14 14 14 14 14 14 14 14 14

29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002

4.4.1 4.4.1 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0

277

Rel4 Rel-4 Rel-4 Rel-4 Rel-4

4.5.0 4.5.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0

TEI

313 314 316 318 320 322 324 325 331 1 1

A F F A A A A F A

LCS1 TEI4 LCS1 CAMEL3 LCS Handover Handover TEI4 TEI

Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4

Clarify encoding of RNC Id Clarify encoding of RANAP parameters in MAP Clarifications on long forwardedto numbers Clarification of methodology for maintaining data consistency in Supercharger Addition of RAB ID to Prepare Handover procedure Correction to the Allowed GSM Algorithms parameter Correction of references CUG-Info is not exported from 29.002 Clarification on NSCD when data is withdrawn Clarification of sending CAMEL information in stand alone ISD case Correction of the priority for SRI for LCS ASN.1 correction Handling of MNRR in the HLR & SMS-GMSC
Minimum MAP application context for G2G inter-MSC handover

14 14 14 14 14 14

29.002 29.002 29.002 29.002 29.002 29.002

4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0

334 336 337 339 341 343 1

Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4

A A F A A A

4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0

Multicall Handover TEI4 CAMEL3 CAMEL phase 3 CAMEL phase 3

14 14 14 14

29.002 29.002 29.002 29.002

4.5.0 4.5.0 4.5.0 4.5.0

344 347 349 354 2 1

Rel-4 Rel-4 Rel-4 Rel-4

F A F A

4.6.0 4.6.0 4.6.0 4.6.0

LCS1 CAMEL TEI4 Handover

2610

3GPP

2611
SMG# 14 14 14 14 15 15 15 15 15 15 15 16 16 TDoc N4011439 N4011423 N4011394 N4011381 N4020300 N4020013 N4020266 N4020068 N4020248 N4020183 N4020250 N4020530 N4020622 N4020641 N4020746 N4020750 N4020318 N4020333 N4020499 N4020511 N4020743 N4020408 N4020410 N4020468 N4020476 N4020483 N4020485 SPEC 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 VERS 4.5.0 4.5.0 4.5.0 4.6.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.1.0 5.1.0 CR 359 360 364 355 368 373 381 386 390 403 407 428 453 1 2 1 2 1 4 REV PHAS CAT E 2 Rel-4 A 1 Rel-4 Rel-4 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 Rel-5 F A B B A B A A A A A A SUBJECT NEW_VERS 4.6.0 4.6.0 4.6.0 5.0.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.2.0 5.2.0 TEI TEI-4 CAMEL phase 3 TEI5 CAMEL4 CAMEL3 LCS1 TEI4 TEI4 TEI TEI4 LCS1 Multicall WORKITEM

Alignment of parameter lengths with those prescribed in 08.08 Aligning the security header elements with TS33.200 Syntax error in the ATM result and ATSI result LCS Capability Handling for UEs Collective CAMEL Phase 4 CR Inclusion of complete ODB data in ATSI and NSDC Introduction of the Requestor ID Correction to AC version of gprsLocationInfoRetrievalContext Incomplete description of Restore Data parameters Clarification on CODEC-Info ODB alignment LCS: error handling if shape not supported by GMLC Addition of Radio Resource List to the Forward Access Signalling operation Clarification on Resume Call Handling Clarification on SendAuthenticationInfo Addition of Service Handover parameters to MAP Handover messages Check of NAM and Requesting Node Type on receipt of SendAuthenticationInfo Handling the MNRR flag in the HLR & SMS-GMSC Clarfication of introducing Session related and unrelated class Corrections on the introduction of LCS for PS domain Corrections in SS-code chapter Clarification of handling of MTSMS-TPDU-Type and SMS-TDP Clarify conditions to trigger restart of MTLR-Deferred procedure Corrections to the handling of Any Time Interrogation and Provide Subscriber Info Change PS-connected in PSPDPactive Triggering of gsmSCF for MTSMS-CSI Transferring the MS classmark & IMEI to the gsmSCF

16 16 16

29.002 29.002 29.002

5.1.0 5.1.0 5.1.0

460 440 446 2 1

Rel-5 Rel-5 Rel-5

A A A

5.2.0 5.2.0 5.2.0

TEI TEI Handover

16

29.002

5.1.0

398

Rel-5

5.2.0

TEI4

16 16

29.002 29.002

5.1.0 5.1.0

410 420 1

Rel-5 Rel-5

A A

5.2.0 5.2.0

TEI4 LCS1-PS

16 16 16 16

29.002 29.002 29.002 29.002

5.1.0 5.1.0 5.1.0 5.1.0

430 448 423 425

1 1

Rel-5 Rel-5 Rel-5 Rel-5

A A C A

5.2.0 5.2.0 5.2.0 5.2.0

LCS TEI CAMEL4 LCS1

16

29.002

5.1.0

414

Rel-5

5.2.0

CAMEL4

16 16 16

29.002 29.002 29.002

5.1.0 5.1.0 5.1.0

435 422 408

1 1 2

Rel-5 Rel-5 Rel-5

D F C

5.2.0 5.2.0 5.2.0

CAMEL4 CAMEL4 CAMEL4

2612

3GPP

2613
SMG# 16 16 16 TDoc N4020543 N4020608 N4020623 N4020703 N4020756 N4021001 NP020399 N4020841 N4021040 N4021041 N4021094 N4021047 N4020810 N4020809 N4021290 N4021418 N4021563 N4021573 N4021299 N4021294 N4021124 N4021153 N4021467 N4021194 N4021252 N4021264 N4021296 SPEC 29.002 29.002 29.002 VERS 5.1.0 5.1.0 5.1.0 CR 441 450 454 REV PHAS CAT E Rel-5 F Rel-5 Rel-5 C F SUBJECT NEW_VERS 5.2.0 5.2.0 5.2.0 TEI LCS CAMEL4-NMM WORKITEM

16 16 17 17 17 17 17 17

29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002

5.1.0 5.1.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0

421 436 437 462 465 470 471 479

4 2 3 2

Rel-5 Rel-5 Rel-5 Rel-5 Rel-5

B B F F F F A C

Correction of Object Identifiers for ASN.1 modules Enhancement to LCS in the PS domain Addition of Location Information GPRS to Note MM Event operation LCS: Codeword and Service Type Splitting of CAMEL phase 4 Compatible upgrade to ASN.1:1997 of 29.002 Introduction of GERAN classmark Clarification on Call Deflection Correction to the usage of "Roaming not allowed" error Clarifications on Send Identification Handling of partial implementations of CAMEL phase 4 Removal of ChargingNotification feature CR29.002-443 (rel5) on extensions to ATM for CAMEL control of IMS CR to 29.002 for the support of the MAP Si interface Correction to segmentation of OCSI and T-CSI ODB correction Addtion of reference number to deferred location request procedure Correction to the Service Handover parameters Description of MT SM delivery via two serving nodes Correction of handling of MTSMS in the SGSN ODB and CB for SMS Correction of IMEI check for SGSN Available codecs list and selected codec indication Clarification of the use of Requested CAMEL Subscription Info parameters Correction to RCH adding OCSI trigger criteria Additional MM-Code for MGCSI Additional handling of partial implementations of CAMEL phase 4

5.2.0 5.2.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0

LCS1 CAMEL4 TEI TEI Call Deflection TEI5 TEI CAMEL4

1 1 2

Rel-5 Rel-5 Rel-5

17 17

29.002 29.002

5.2.0 5.2.0

480 481

Rel-5 Rel-5

C B

5.3.0 5.3.0

CAMEL4 IMS-CAMEL

17 18 18 18

29.002 29.002 29.002 29.002

5.2.0 5.3.0 5.3.0 5.3.0

482 499 508 511 1

Rel-5 Rel-5 Rel-5 Rel-5

B A A A

5.3.0 5.4.0 5.4.0 5.4.0

IMS-CAMEL CAMEL3 CAMEL3 LCS1

18 18 18 18 18 18 18

29.002 29.002 29.002 29.002 29.002 29.002 29.002

5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0 5.3.0

516 442 474 475 486 489 490

2 3 2

Rel-5 Rel-5 Rel-5 Rel-5 Rel-5

A F F F F F F

5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0 5.4.0

Multicall TEI5 CAMEL4 TEI5 TEI5 TEI5 CAMEL4

Rel-5 Rel-5

18 18 18

29.002 29.002 29.002

5.3.0 5.3.0 5.3.0

495 496 497 1

Rel-5 Rel-5 Rel-5

F F F

5.4.0 5.4.0 5.4.0

CAMEL4 CAMEL4 CAMEL4

2614

3GPP

2615
SMG# 18 18 TDoc N4021383 N4021443 N4021524 N4021531 N4021260 N4021504 N4021567 N4021506 N4030234 N4030325 NP030068 N4030061 N4030063 N4030054 N4030301 N4030305 N4030287 N4030289 N4030297 N4030222 N4030692 N4030658 N4030638 N4030713 SPEC 29.002 29.002 VERS 5.3.0 5.3.0 CR 512 513 REV PHAS CAT E Rel-5 F Rel-5 F SUBJECT NEW_VERS 5.4.0 5.4.0 WORKITEM

Correcion of Codeword Handling Reference to TS 23.078 in TS 29.002 regarding handling of VMSC address is missing Editorial clean-up Introduction of the CHOICE element netDetNotReachable for PS-SubscriberState Addition of LCS Format Indicator to LCS Client ID Addition of V-GMLC Address to the Update Location and Update GPRS Location requests Addition of V-GMLC and HGMLC Addresses to the Send Routing Info for LCS response Addition of PPR Address to the Send Routing Info for LCS response Introduction of Call Barring for SMS in PS domain Clean-up of SMS procedures chapter Correction to interactions between CAMEL control of MO SMS and barring Incrementing ASN.1 module versions LCS diagnostic alignment Addition of LCS Capability Set 4 Correction to the definitions of Radio Resource List and BSSMAP Service Handover List Handover of Group Calls where MSC-B has bearer established Change of SS-Code List description for Insert Subscriber Data Missing of Continue Monitoring message in SDL 21.7_3.2 Alignment of TS 29.002 with TS 23.107 regarding QoS subscribed data Introduction of MSC Number as a new parameter in MAP-SENDIDENTIFICATION operation Additional SGSN Related Access Type Detach Addition of Positioning Data IE to Provide Subscriber Location and Send Location Report Provision of SDL diagrams and removal of redundant text in chapter 25 Removal of redundant text from 29.002 Chapter 23

LCS1-PS CAMEL4 TEI5 CAMEL4 LCS2 LCS2 LCS2 LCS2 TEI6 TEI5 CAMEL3 TEI6 LCS1 LCS2 Multicall TEI TEI TEI5 TEI5 LCS2 SEC1-EHCS LCS TEI6 TEI5

18 18

29.002 29.002

5.3.0 5.3.0

521 522

Rel-5 Rel-5

F F

5.4.0 5.4.0

18 18

29.002 29.002

5.4.0 5.4.0

491 517

1 2

Rel-6 Rel-6

B B

6.0.0 6.0.0

18

29.002

5.4.0

518

Rel-6

6.0.0

18-

29.002

5.4.0

519

Rel-6

6.0.0

19 19 19

29.002 29.002 29.002

6.0.0 6.0.0 6.0.0

509 524 545

3 3 2

Rel-6 Rel-6 Rel-6

C A A

6.1.0 6.1.0 6.1.0

19 19 19 19

29.002 29.002 29.002 29.002

6.0.0 6.0.0 6.0.0 6.0.0

526 528 529 533 1

Rel-6 Rel-6 Rel-6 Rel-6

F A F A

6.1.0 6.1.0 6.1.0 6.1.0

19 19

29.002 29.002

6.0.0 6.0.0

541 551

2 1

Rel-6 Rel-6

A A

6.1.0 6.1.0

19 19

29.002 29.002

6.0.0 6.0.0

559 563

1 1

Rel-6 Rel-6

A A

6.1.0 6.1.0

19

29.002

6.0.0

566

Rel-6

6.1.0

20 20

29.002 29.002

6.1.0 6.1.0

536 568

2 4

Rel-6 Rel-6

A A

6.2.0 6.2.0

20

29.002

6.1.0

574

Rel-6

6.2.0

20

29.002

6.1.0

595

Rel-6

6.2.0

2616

3GPP

2617
SMG# 20 20 TDoc N4030439 N4030682 N4030608 N4030647 N4030678 N4030609 N4030642 N4030601 N4031043 N4031053 N4030828 N4030922 N4031069 N4031057 N4031059 N4030785 N4030806 N4030815 N4030824 N4030951 N4031006 N40301038 N4031065 N4030953 N4030745 N4030747 N4030748 SPEC 29.002 29.002 VERS 6.1.0 6.1.0 CR 599 607 REV PHAS CAT E Rel-6 A 1 Rel-6 F SUBJECT NEW_VERS 6.2.0 6.2.0 WORKITEM

LCS Client external ID Provision of SDL diagrams and removal of redundant text in chapter 22 Addition of LCS capability sets to MAP_SRI_for_LCS response Enhancement of the CheckIMEI operation to retrieve the BMUEF Correction to naming of PRN parameter Addition of Privacy Check Related Action to Provide Subscriber Location request Transfer of UE-specific behaviour bitmap at handover Missing SMSs over MSC even if the MS is capable of such sending Correction to MAP Process Secure_MAP_DSM SDLs Correction of encoding description of Group-Id Reduce maximum length of LCS Requestor ID and LCS Codeword. UESBI -IU format Incorrect Charging with MNP Notification of the 2 BSG in case of Late CF with OR HLR Interrogation for SCUDIF calls Removal of tables in section 7.6 Correction of References Correction of wrong AC name in the table in 17.1.6 New LCS Service Types SS-Barring Category Add SGSN, GGSN, GMLC, gsmSCF, NPLR and AuC to network resource parameter Introduction of North American Interim Location Based Routing of Emergency Call Positioning Data for UTRAN LCS Provision of SDL diagrams and removal of redundant text in chapter 19 Provision of SDL diagrams and removal of redundant text in chapter 20 Provision of SDL diagrams and removal of redundant text in chapter 21 Removal of SIWF description
nd

LCS TEI5 LCS2 Late UE CAMEL4 LCS2 Late UE TEI5 MAP Security ASCI LCS2 LATE-UE CAMEL4 SCUDIF SCUDIF TEI6 TEI TEI6 LCS TEI TEI6 LCS2 LCS2 TEI5 TEI5 TEI5 TEI6

20 20 20 20

29.002 29.002 29.002 29.002

6.1.0 6.1.0 6.1.0 6.1.0

608 612 619 624

1 1 1 1

Rel-6 Rel-6 Rel-6 Rel-6

B A A F

6.2.0 6.2.0 6.2.0 6.2.0

20 20 21 21 21

29.002 29.002 29.002 29.002 29.002

6.1.0 6.1.0 6.2.0 6.2.0 6.2.0

610 633 584 664 657

Rel-6 Rel-6

A A A A A

6.2.0 6.2.0 6.3.0 6.3.0 6.3.0

2 1

Rel-6 Rel-6 Rel-6

21 21 21 21 21 21 21 21 21 21

29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002

6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0 6.2.0

647 616 660 614 644 649 648 654 671 650

1 3 2 3

Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6

A A A A D F D B D F

6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0

Rel-6

21

29.002

6.2.0

645

Rel-6

6.3.0

21 21

29.002 29.002

6.2.0 6.2.0

674 637 1

Rel-6 Rel-6

F A

6.3.0 6.3.0

21

29.002

6.2.0

639

Rel-6

6.3.0

21

29.002

6.2.0

641

Rel-6

6.3.0

21

29.002

6.2.0

642

Rel-6

6.3.0

2618

3GPP

2619
SMG# 21 22 TDoc N4030749 N4031098 SPEC 29.002 29.002 VERS 6.2.0 6.3.0 CR 643 677 REV PHAS CAT E Rel-6 D Rel-6 B SUBJECT NEW_VERS 6.3.0 6.4.0 WORKITEM

Deletion of redundant Annex D Enhancements for the Partial Implementation for "Change of position procedure armed with criteria" Collective CR for Rel-6 Enhanced Dialled Services Message Segmentation Mechanisms Addition of requestingPLMN-ID to Send Authentication Info Request Addition of CGI to LCS procedures Include v-gmlc parameter in RESTORE DATA MAP message Deferred MT-LR Area Event More spare bits for CAMEL4 enhancements Clarification on D-CSI segmentation MNP correction for prepaid charging Remove reduntant option for retrieval of routeing information in figure 21.2.3 Modification of description for conditions on inclusion of Positioning Data HSDPA impacts to MAP EXPORT data types to CAP (Change of position armed with criteria) Codec Modification/ Mid-Call Codec Negotiation after InterMSC Relocation Correction of Inter-MSC SRSN Relocation procedure Introduction of Presence Stage 3 (Ph, Pc and Pg) to the MAP interface Correction to Insert Subscriber Data message for LCS SS SCCP segmentation for Inter PLMN MAP message Inclusion of UTRAN Positioning Data parameter Include administrative restriction subscription parameter Add new Unavailability cause for SCUDIF CR implemented by fault Removal of R-GMLC Address MO-LR Service Identity support

TEI6 TEI6

22 22 22

N4031135 N4031274 N4031315 N4031372 N4031373 N4031365 N4031132 N4031163 N4031342 N4031338 N4031108 N4031317 NP030533 N4040310 N4040193 N4040249 N4040333 N4040328 N4040327 N4040284 N4040340 N4040171 N4040182 N4040322

29.002 29.002 29.002

6.3.0 6.3.0 6.3.0

687 648 703 2

Rel-6 Rel-6 Rel-6

B D B

6.4.0 6.4.0 6.4.0

EDCAMEL TEI6 TEI6 LCS2 LCS2 LCS2 CAMEL4 CAMEL4 MNP TEI5 LCS2 HSDPA TEI6 OoBTC OoBTC PRESNC LCS TEI6 LCS2 TEI6 SCUDIF TEI6 LCS2 LCS2

22 22 22 22 22 22 22

29.002 29.002 29.002 29.002 29.002 29.002 29.002

6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0 6.3.0

680 696 702 686 692 676 695

2 2 2

Rel-6 Rel-6 Rel-6 Rel-6 Rel-6

F F B A A A A

6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0

2 1

Rel-6 Rel-6

22

29.002

6.3.0

679

Rel-6

6.4.0

22 22

29.002 29.002

6.3.0 6.3.0

689 704

Rel-6 Rel-6

A F

6.4.0 6.4.0

23

29.002

6.4.0

668

Rel-6

6.5.0

23 23

29.002 29.002

6.4.0 6.4.0

670 701

2 3

Rel-6 Rel-6

A B

6.5.0 6.5.0

23 23 23 23 23 23 23 23

29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002

6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0 6.4.0

708 709 711 717 720 721 724 725

2 1 2 1 2

Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6

F F F B A F F B

6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0 6.5.0

Rel-6

2620

3GPP

2621
SMG# 23 24 TDoc N4040267 N4040520 N4040585 N4040600 N4040601 N4-04732 SPEC 29.002 29.002 VERS 6.4.0 6.5.0 CR 726 731 REV PHAS CAT E 1 Rel-6 B Rel-6 F SUBJECT NEW_VERS 6.5.0 6.6.0 WORKITEM

24

29.002

6.5.0

735

Rel-6

24 24

29.002 29.002

6.5.0 6.5.0

736 737

Rel-6 Rel-6

F F

24

29.002

6.5.0

734

Rel-6

24

N4040736 N4040929 N4041021 N4041128 N4041272 N4041477 N4041662 N4041683 N4041684 N4041685 N4041641 N4050212 N4050369 N4050430 N4050444 N4050446 N4050463 N4050467 C4050737

29.002

6.5.0

718

Rel-6

25 25 25 26 26 26 26

29.002 29.002 29.002 29.002 29.002 29.002 29.002

6.6.0 6.6.0 6.6.0 6.7.0 6.7.0 6.7.0 6.7.0

739 743 732 747 752 746 757 1 2 2

Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6 Rel-6

B D B F F B F

CAMEL4 SCUDIF notification during active call for prepay Introduction of North American Interim Location Based Routing of Emergency Call Modify IMEI parameter usage definition in MAP-PSL and MAP-SLR Addition of SAI-Present indication to the LCS procedures Clarification on the use of MSISDN parameter for Follow Me functionality Add Additional V-GMLC parameter in MAP-SRI-INFOFOR-LCS Addition of IMEISV to Update Location Procedure for ADD function Export of UU-Data data type Wrong SDL flow page implemented Pre-Paging Resource Optimization Incorrect Implementation of CR 731 Correction to the service response parameters of ATI Introducing VGCS/VBS ciphering Clarification about returning authentication data for a subscriber (GSM or UMTS) LCS Capability Handling for UEs Enable NA-ESRD Provision from a GMLC for E911 Location in North America SMS Fraud countermeasures Management Based Activation Impacts Addition of LAI to SendIdentification Request Subscribed Charging Characteristics Addition of TCAP-Handshake for MO-ForwardSM Introduction of Hop Counter for Send Identification Rel-6 trace management additions to trace activation and deactivation procedures Pseudonym indicator support in MO-LR Correction to Trace parameters to allow trace at the BM-SC

SCCAMEL LCS2 TEI6 LCS2 TAI6 LCS2 TEI6 TEI6 TEI6 TEI6 LCS2 TEI6 SECGKYV TEI6 TEI6 LCS2 TEI6 OEM-TRACE TEI6 TEI6 TEI6 TEI6 OEM-Trace LCS2 OAM-Trace

6.6.0

6.6.0 6.6.0

6.6.0

6.6.0

6.7.0 6.7.0 6.7.0 6.8.0 6.8.0 6.8.0 6.8.0

26 26

29.002 29.002

6.7.0 6.7.0

748 753

1 1

Rel-6 Rel-6

F F

6.8.0 6.8.0

26 27 27 27 27 27 27

29.002 29.002 29.002 29.002 29.002 29.002 29.002

6.7.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0 6.8.0

740 749 761 760 759 745 738

2 1 1 1 1 2 8

Rel-6 Rel-6 Rel-6Rel-6 Rel-6 Rel-6 Rel-6

B B F F C B F

6.8.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0 6.9.0

27 28

29.002 29.002

6.8.0 6.9.0

763 769

2 1

Rel-6 Rel-6

F F

6.9.0 6.10.0

2622

3GPP

2623
SMG# 28 28 28 TDoc C4050832 C4050895 C4050784 C4051013 C4051295 C4051333 C4051334 C4051368 C4051336 C4051775 C4060320 C4060295 C4060315 C4060378 C4060434 C4060318 C4060041 C4060250 C4060011 C4060813 C4060499 C4060680 C4060706 CP060522 C4061047 SPEC 29.002 29.002 29.002 VERS 6.9.0 6.9.0 6.10.0 CR 770 766 765 REV PHAS CAT E 6 Rel-6 F 2 1 Rel-6 Rel-7 F B SUBJECT NEW_VERS 6.10.0 6.10.0 7.0.0 WORKITEM

29 29 29 29 29 29 30 31 31 31

29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002

7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.1.0 7.2.0 7.2.0 7.2.0

771 776 772 773 777 780 783 794 790 787 2 1 1 2 2 2 1 1 1

Rel-7 Rel-7 Rel-7 Rel-7 Rel-7 Rel-7 Rel-7 Rel-7 Rel-7 Rel-7

F B B B B A A A C C

Full RANAP support of network initiated SCUDIF Clarification on the use of Access Restriction Data parameter Addition of CollectInformation procedure to OfferedCAMEL4Functionalities ASN.1 module version update Enabling the Providing of Velocity Support of talker priorities and talker identity presentation Delivery of SMS to voice group call CS data Mobile Terminating calls from PSTN Correction on misalignment with stage 2 for Location Services Addition of UMTS Trace parameters to handover procedure Addition of UMTS Trace parameters to handover procedure Removal of MAPsec material
addition of "supported RAT types indicator" during location/routing area update

TEI6 TEI5 CAMELR7 TEI LCS-7 EGCS EGCS TEI7 TEI6 TEI6 TEI6 SEC7-TCAP TEI7 LCS3 LCS7 TEI7 TEI7 TEI TEI7 TEI7 LCS7 TEI7 SEC7-TCAP TEI7 VGCSflex

7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.2.0 7.3.0 7.3.0 7.3.0

31 31

29.002 29.002

7.2.0 7.2.0

792 781

1 3

Rel-7 Rel-7

B C

31 31

29.002 29.002

7.2.0 7.2.0

788 789

Rel-7 Rel-7

F F

31 31

29.002 29.002

7.2.0 7.2.0

801 786

Rel7 Rel-7

C F

32

29.002

7.3.0

0808 2

Rel-7

32 32 32 33 33

29.002 29.002 29.002 29.002 29.002

7.3.0 7.3.0 7.3.0 7.4.0 7.4.0

0803 0814 0817 0818 1 0805 1

Rel-7 Rel-7 Rel-7 Rel-7 Rel-7

F F F F B

Addition of Periodic Location Feature Support New LocationType for the notification based on current location of target UE SMS Relay Application Context Names for Version 1 Precision on segmentation of MAP GPRSSubscriptionData parameter Improvements to VGCS Call Establishment Addition of Authentication Domains in MAP Send Authentication Info List of MSISDNs and Basic Service Code for MAP Any Time Subscription Interrogation. Correction of LCS parameter for emergency call usage SSN for FFN Removal of MAPsec material Removal of ASN.1 Expanded Source Interoperability between VBS/VGCS and RANflex

7.3.0 7.3.0

7.3.0 7.3.0

7.3.0 7.3.0

7.4.0

7.4.0 7.4.0 7.4.0 7.5.0 7.5.0

4532

2624

3GPP